Your system spec is important as well, and keep an eye on the performance meter of Reaper too a bit. Give one or two of these formats a try and see how they fare. You can produce Quicktimes with either Quicktime Pro(File/Export in the Quicktime Player) or programs like Super. Those codecs compress the picture better, but also cost more CPU to play back and take longer to seek to picture. If you're just mixing and composing, you can do with larger seek speeds, and use codecs like XVid or H264(x264 for AVI and h264 for Quicktime). Give Quicktime DV, Quicktime PhotoJPeg or Quicktime MJpeg a try if you want to edit sound to picture. all the codec nonsense has never made a bit of sense to me.ĭid you do this in the middle of playback, or when transport was stopped ? These guys are brave (or asking for punishment) messing with this video stuff. i tried rendering from that point and got the message 'not rendering, eta infinity'. i started skipping around in the timeline and lost video stayed on a single frame and wouldn't budge. playback seemed ok the first time around. the file info says ms-cram (no idea what cram represents), 30 fps. I believe the codec is microsoft video 1. I have to stop and start playback again to get the video running. Interleave, duration : 24 ms (1.20 video frame)Īlso when skipping in the video, REAPER doesn't update the video anymore. Writing library : VirtualDub build 32809/releaseįormat_Settings_ModeExtension : MS Stereo I guess it's because FFmpeg in REAPER isn't multithreaded? In MPC-HC (using ffmpeg-mt from latest ffdshow ) it uses just 20% CPU. The following video used ~40% CPU here in REAPER (on Intel Core 2 Duo E6700). ![]() Turn off picture reordering when exporting the Quicktime, and this does not happen at all. With standard H264 Quicktimes, which have an i=frame distance maximum of 24 frames, AND have picture reordering enabled, that does happen. In the H264 videos with a maximum I-Frame distance of ten frames(you set set that up in the encoder of the Quicktime Player and anywhere else I suppose) this doesn't happen. Click anywhere in the video file, then click to the right by a few frames. The video does not follow the playhead for Quicktime H264 videos if the cursor is moving by single-clicks forward by small increments such as two or four frames. edit- Test with both RGB and other available colourspaces if that made a difference. When I turn it off, the crashes do not happen. When I drag and drop these files in to the timeline from outside Reaper, they'll import fine the next time I touch them in the Media Explorer of Reaper itself. Those files are the ones that produce the crashes when selecting them in the Media Explorer of Reaper as well, though not consistently either. ![]() Video playback on some Quicktime-Mov/PhotoJPeg(high) files (23.976 and 25 fps) files seems to produce funky colours. It crashes.ĭrag and drop it from anywhere else, and it imports properly. ![]() FPS : 23.98 (23.976 also selected in session)ĭrag and drop a video file of this configuration in to the timeline with the Media Explorer of Reaper(Autoplay and Start on Bar ON).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |