Personally I enable desktop audio recording in OBS using Loopback, a very powerful and cool audio routing app - but it's also rather expensive if all you want it for is desktop audio recording ($99 + tax). That's another benefit of iShowU Instant: it includes a special driver for recording your desktop audio as you screen record. One potentially big downside of OBS recording on macOS is that there's no built in way to record the desktop audio. It also has easy-to-use and good looking keyboard and mouse reporting, You can set all that up in OBS as well, but it requires more work and investigation on the part of the user. IShowU Instant is easier for a new user to get going though, and if you really want ProRes, it's definitely the best option - despite the VFR. I've been screen recording in OBS to DNxHR HQ for some months and it works very well. If you want to use OBS, then set ffmpeg to encode in DNxHR. If you want ProRes, buy and use iShowU Instant Advanced (macOS only) If you want that, prores_ks is the only option - meaning it will max out the CPU, which probably isn't tenable for screen recording. Unfortunately, the "prores" encoder can't handle 444 encoding, so it doesn't support ProRes 4444. Example output file: Code: Select all General ![]() So if you want to record ProRes 422HQ with OBS, it seems you'll need to ignore the advice to use _ks and use the default encoder instead. I've never tested the differences in IQ personally. The reason I first chose prores_ks is that the ffmpeg Wiki says it gives the highest quality output (remember that the ffmpeg ProRes encoders are reverse-engineered, they don't use the original Apple code). I wonder why they do VFR - it surely can't be because the hardware can't keep up, because as you say it's using hardly any resources.Īh, regarding OBS and ProRes, I found that if you use ffmpeg's "prores" encoder, instead of "prores_ks", CPU usage is more reasonable. But yeah the auto reencode is fine I guess. Shame iShowU is VFR, I hadn't noticed that (when I was using it I was recording at 60 FPS and putting it on a 30 FPS timeline in Resolve, so I guess that was automatically taking care of that for me). Or yes, another decent option on macOS is to buy iShowU Instant Advanced and get native ProRes 4 encoding, which will be 'true' ProRes. Here's the DNxHR output file from OBS - confirmed as CFR 60FPS: Code: Select all General I don't know why ProRes canes the system so hard. Very manageable resource usage with DNxHR. If you want advanced OBS recording I would recommend sticking with DNxHR as per my earlier screenshot, because I know that works well.īy comparison, here's me using OBS to record UHD 60 FPS with 24bit PCM, in ProRes 422HQ: When I just tested ProRes in OBS it did work, however it used 100% of all CPU cores and OBS gave its "Overloaded" warning. Profile 3 is ProRes 422 HQ profile is 0 (Proxy) to 5 (4444XQ). You will need to manually configure it though, eg for ProRes you'd need Video Encoder = "prores_ks" and Encoder Settings = "profile=3 pix_fmt=yuv422p10le". Then it will look like my earlier screenshot. ![]() Recording -> Type -> change from Standard to "Custom Output (FFMPEG)" I'd also point out that I have limited SSD storage so large transcodes can present a problem for me. Would any of these differences account for the ease of editing the new footage? And excuse my ignorance (for I am an amateur) but I have no idea what GOP is. ![]() mp4), the frame rate is twice as high (56 fps vs 30 fps) and the data rate is also nearly double (26Mbps vs 15 Mbps.) Both are recorded with h.264. Looking at the capture properties I notice three differences: it is in a. Quicktime recorded the footage I needed (shift-cmd-5) and I was able to scrub through it without issues. ![]() I did get this to work, but by skipping both OBS and the capture device. In no way do you need to polute the planet further by using an external capture device. OBS records straight to ProRes just fine if you want that. As with everything, you just need to know what you are doing. The comment about OBS / recording is non sense. Transcode to ProRes or something for editing. Peterjackson wrote:It's probably just very long GOP due to static on screen content.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |