Troubleshooting - Simple. Screen. Recorder - Maarten Baert's website. Last modified: Sat, 2. Dec 2. 01. 4Refresh. Some codecs (e. g. H. 2. 64) are 'not installed'Some distributions will omit codecs that have patent issues, but allow you to install them as a separate package. For Ubuntu, this can be done by running: sudo apt- get install libavcodec- extra- 5. Can't open output file" error. This error indicates that the output file could not be created. Common causes are: The output directory does not exist (i. You don't have permission to write to the output directory. Your hard disk is full."Can't write header" error. This error indicates that ffmpeg/libav (the underlying video and audio encoding library) failed to initialize the output file. VirtualBox was initially offered by Innotek GmbH from Weinstadt, Germany under a proprietary software license, making one version of the product available at no cost. Use DOSBox. If you have an old DOS application that isn’t working properly in Windows — likely an old DOS game like the original DOOM games — you can run it in. Common causes are: You have selected a codec that is not supported by the container (for example, you tried to use the VP8 video codec with the MP4 container). Your hard disk is full. Weird glitches (horizontal lines, missing objects) when using the NVIDIA proprietary drivers. Here's a screenshot of the bug appearing in Minecraft: link. Luckily there is a simple fix. Go to the NVIDIA driver settings and disable 'allow flipping'. I've only seen this issue for the NVIDIA prorietary driver, but it may also apply to other drivers/vendors. Alternatively, switch to Open. GL recording. This issue will only appear when you use an Open. GL based compositing window manager (Compiz, Mutter, KWin with effects enabled, ..) or when you run a fullscreen Open. Collaborative Computational Project Number 14 (CCP14) For Single Crystal and Powder Diffraction (Freely Available Crystallographic Software for Students and Academia).GL application and you try to record it without Open. GL recording. I'm pretty sure the cause is a race condition inside the X server, where the server tries to take a screenshot of the screen while at the same time the NVIDIA driver flips the front and back buffer. The result is a screenshot of the back buffer (which is in the process of being redrawn) rather than the front buffer. Open. GL recording doesn't work: the application size is not recognized. If your application is 3. Steam, most Windows games running through WINE), and you have a 6. Simple. Screen. Recorder libraries. More information can be found here. If this doesn't solve the problem, you may need to do something special to get the right environment variables to the program that you want to record. For example, Steam games need some special settings. Try running the program from a terminal, and look for lines like this: [SSR- GLInject] Library loaded (6. SSR- GLInject] [GLXFrame. Grabber 1] Created GLX frame grabber. SSR- GLInject] [/dev/shm/ssr- channel- maarten/video- 1. Created video stream. SSR- GLInject] Open. GL version = 4. 4 (4. NVIDIA 3. 43. 3. 6). SSR- GLInject] [/dev/shm/ssr- channel- maarten/video- 1. If you don't see any lines starting with [SSR- GLInject], the library is not loaded, which means the program didn't get the right environment variables. If the program is started through a wrapper script, you should try to run the actual program directly, without the wrapper script. If you do see lines starting with [SSR- GLInject], but not the one with GLXFrame. Grabber in it, the application is probably not an Open. GL program. If you do see lines starting with [SSR- GLInject], including the one with GLXFrame. Grabber, but it still doesn't work, please send me a bug report. Open. GL recording is experimental, so it is possible that it doesn't work yet for all programs. Slowed- down, out- of- sync audio when recording the speakers with Pulse. Audio. When this happens, you will usually get the following error message: Warning: Audio input is more than 5% too fast, video and audio will be out of sync. The cause is a bug in Pulse. Audio. The issue has been fixed and the fix should arrive in some future version (probably 4. For now, you can work around the bug by modifying the file /etc/pulse/daemon. After doing this, you should restart Pulse. Audio (or just reboot). These values will force Pulse. Audio to use the same sample rate at all times rather than switching between 4. Hz and 4. 80. 00 Hz (which will trigger the bug). Some users have reported that sound recorded through Pulse. Audio is still buggy even after applying this workaround, so it appears that there is more than one bug in Pulse. Audio that can cause this issue. I haven't been able to reproduce this myself though. If you are unable to fix the problems with Pulse. Audio, consider using JACK instead. No sound when recording the speakers with Pulse. Audio. If no sound is recorded, make sure the monitor channel is not muted. To do this, go to the "Input devices" tab in Pulse. Audio Volume Control, select "Show: All input devices" and make sure the "Mute audio" button of the monitor channel is not enabled. Comments. Write a comment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |