Peter Chamberlain wrote:Coasterghost wrote:I would like to see the ability to disable making proxies in real time when you record, and to be given the ability to encode proxies in post after you record, if it’s an option in the media browser.
What is the workflow that drives this request?
I don't have a need for proxies and my system can handle ProRes just fine. If I need to send a copy after the fact for instance to someone else, having the additional ability to make proxies in post would be a good alternate. I currently as a mainly one man band, have no need for the collaborative features, nor would I need to send the raw footage to anyone unless it was a client asking in which, I already have 2TB of cloud storage for that very thing.
In my particular use case, I do cover a few multiple day events such as conventions and trade shows yearly in the travel media industry, as well as my other projects, and sometimes being under hectic schedules I can forget some of my gear. During these multiple day events, the space does add up quick and not being able to at times being able to dump the storage after that day does happen. And given the portable SSDs max at 4TB for the solutions that this forum would likely have such as the Samsung T7, if you aren't able to dump the media, the storage can be seen as a premium. I can easily product 12 hours of raw content in 3-4 days by myself without getting secondary camera operators, with the main bulk of it all being done in 3 days.
Also, while the gain can be seen as marginal, it will provide additional recording time. Doing some 422HQ Napkin math:
422HQ Recording time for max 3500GB (rounded up to the nearest mbps)
24FPS ProRes (600Mbps) and Proxy (6Mbps): 720 Minutes
ProRes Size:3240GB Proxy Size:259.2GB Total: 3499.2GB
Minutes added to ProRes without Proxy: 57 Minutes to a total of 777 Minutes at 3496.5GB
30FPS ProRes (709Mbps) and Proxy (7Mbps): 623 Minutes
ProRes Size:3312.803GB Proxy Size:186.9GB Total: 3499.703GB
Minutes added to ProRes without Proxy: 35 Minutes to a total of 658 Minutes at 3498.915GB
60FPS ProRes (1372Mbps) and Proxy (8Mbps): 324 Minutes
ProRes Size: 3333.96GB Proxy Size: 155.52GB Total: 3489.48GB
Minutes added to ProRes without Proxy: 16 Minutes to a total of 340 Minutes at 3498.6GB
When this is scaled down to for example, with ProRes 422, we could see an increase of recording time at 22 to 77 Minutes from the current 422 and Proxy setup. Even if we were to choose too 422LT, we could see an increase of recording time at 93 to 562 Minutes without automatic proxy recordings.
And given how a lot of us will use our favorite apps, such as BM Camera, for things like vacations and family affairs as well, where we are able to run and gun, that savings without proxies can add up quickly.
Overall for my use case: I rarely have the need for proxies and having the ability to toggle it, can give us additional recording time. Additionally, having the ability to do it in post, would allow for us to make them, if needed post while away from our workstations.
Also given in the nature of how users are also reporting that recordings are hit or miss on being CFR or VFR, as I shared in that thread:
Coasterghost wrote:Uli Plank wrote:As others reported, sometimes it is CFR, but you can't rely on it.
Thinking about this, I wonder if part of the issue is that we don’t have the ability to disable proxies. It could very well be taxing the SoC because it’s technically rendering two videos at once and we all know that H265 can be hungry on a GPU/CPU on resources to encode. The dual encoding in combination with the reporting that Apple is aware of the SoC running hotter than expected, we could be seeing the issue of thermal throttling that is affecting the performance and thusly the frame rate. I think that would explain that shorter clips seem to be at 24fps to generally be CFR,
I’ve been able to consistently get at least with shorter clips, CFR at 24fps and my 30FPS, I tend to generally get 30fps with VFR at 31, but it can vary between 28-31fps. I do think that a 30fps CFR is possible, but would love to see a toggle in the app to disable proxies for if we choose to.
- James F.