When I double click on them and look in properties it is telling me that the device is working properly but it is just a High Definition Audio Device from Microsoft, not RealTek, as it is on the laptop that is working correctly, but I cannot see any way to change this. When I look in Recording devices the recording devices do not seem to be not active (a red downwards facing arrow as opposed to a green tick on the laptop I have that is working properly). If I change this it doesn’t appear to make any difference. By right clicking on the speaker on the right of the quick launch tool bar at the bottom of windows and clicking on sounds, I then double click on the headphones that are highlighted green and go into Advances in Default format it gives me the option to change the SR and bit depth, but I am not sure what this is for exactly. When I reduce the SR in the bottom left hand corner of Audacity to 109200 it will start to play the file but then stop a fraction of a second in. When I look in Device Manager in Audio Inputs and Outputs, it tells me the Realtek High Definition Audio :This device is working properly. I have tried the earphones in both jacks and there is still the same problem. I always import and export the files as I need to change the name of the file to contain the bat species that is present within the file. But I didn’t think these would be required when only playing back calls. However I can not see any options to choose anything in Recording device and recording channels. So I have updated this and now I can see MME in Audio host and Microphone (RealTek High definition) in Playback Device (speakers). I checked out the RealTek sound card and it hadn’t been updated since 2010. Please check the playback device settings and the project sample rate. When I go to play a file using the play at speed button, (with playback speed at 0.16) I get the following pop up:Įrror while processing sound device. I have now downloaded Audacity on a computer and another laptop. I have been using Audacity on a laptop and have not had any problems with playback. I am using Audacity to look at Bat acoustic WAV files (upto 6MB), so very high frequency, short files. With V-Sync off, the frame rate of the game can go above the maximum of the display (and the chosen recording FPS in Screenflick) which can steal precious GPU processing power away from Screenflick.I am using a 64 bit operating system. When recording video games or other programs with high performance OpenGL graphics, make sure the game has V-Sync turned on. The lowest quality setting uses quite a bit less CPU than the highest setting at the expense of some quality, which may not matter in your case. See the Advanced tab in Screenflick's prefs and adjust the quality slider down a bit to affect how much CPU power is needed. Adjust the recording quality in Screenflick's preferences.The smaller the area, the less work Screenflick needs to do resulting in higher recording rates. Use the the smallest screen area you can in the recording.Make sure non-essential background processes using the CPU or hard drive are not running (such as Time Machine, Spotlight, etc).There are three key factors to improving recording performance in Screenflick. How can I get better recording performance? If it does have a setting, set it to "Screenflick Loopback" while recording. Check the program's preferences just in case. A third option which doesn't always exist, is that the program playing audio may have a preference setting for which audio device to play audio to.(After the recording ends, don't forget to change the system output device back to your speakers.) Before starting the program, go into System Preferences and change the system output audio device to "Screenflick Loopback" manually, start the program which will play audio, and then start the recording in Screenflick when you're ready.(The system output device will be Screenflick Loopback and the program will therefore use it.) Launch the program which plays the audio after you start a Screenflick recording.What needs to happen is the program playing audio needs to decide that it should play that audio to the Screenflick Loopback device, rather than your speakers. Some programs unfortunately will play all audio over a specific output device determined when the application launched rather than always using the current system setting which can lead to problems like this. When you start a recording with system audio turned on, Screenflick switches the system-wide default audio output device to the "Screenflick Loopback" virtual audio device, which Screenflick then uses as an input to record audio from. Why isn't audio from this application being recorded?
0 Comments
Leave a Reply. |