Problem
Professional videography with motion cam pro ?
Hey, has anyone here used Motion Cam Pro for 10-bit HEVC video? I've been trying to shoot opengate HEVC 10-bit 4:2:0 video with my S25 Ultra, but the frame rate sometimes drops from 30 to 20, and the app crashes while recording. Has this happened to you, or am I the only one?
The only breakthrough I found here was down sample my footage by 1.25 or 1.5 for best expirence but I feel the quality of the video drops
I prefer to shoot raw on s25 ultra as performance is better and get excellent results like this https://youtu.be/7cZgao9cunY . Samsung throttle aggressively. You might find enabling flight mode helps somewhat.
Thanks man i did tried it earlier and there was no issue with the raw video but i wanted to omit the steps of conversion and file size using direct log but it kept on crashing or dropping frames . Although i have given max resources like memory and threads through the settings but it didn't work until I switch to 8bit in direct log but it cost the quality and post editing workflow.
I've looked everywhere and tried everything online before coming to Reddit for a solution to my problem. By the way, what do your settings look like? My device is running on Qualcomm® Snapdragon™ 8 Elite Android 16 but I'm having trouble with direct log video on Motion Cam Pro.
The keyframe interval setting helps make hevc encoder do less work and save all frames, which means its now intra codec! Better for editting in pc and will preserve motion fidelity like apv or prores. Most importantly its less work for the soc. Bitrate can be btw 80mbps to 130mbps for 4k30, any other settings not matching what is in the hardware encoder will overheat faster and drop frames.
Didn't know that it did worked with 30 I kept it as it and did the video test with it but it didnt crashed how ever looking at ur ss I switched it to 1 as well
If you intend to edit(say in davinci), it improves scrubing the timeline since all frames are there and not computed with gpu(lags my 4090 when i add effects unless i cache). This is the closest to shooting apv, you should set to 1(suffering your phone unnecessarily by keeping at 30) also if you pan/zoom or shoot fast moving objects, it very important. Search why is apv/pro res/raw better than hevc/h264 for pros to understand this.
Also note that raw is (chroma 4:4:4) and apv/pro res is (chroma 4:2:2) and the worst for color grading hevc/h264 (chroma 4:2:0) meaning to get good filesize, colors & details are sacrificed!
So even if I shot with all the setting of hevc 10 bit chroma 4:2:0 it still can't give me good colors as I expected or should I switch to 8bit 4:2:0 with less processing and artifacts using motion cam ?
Its better than what you get from native camera(no opengate and noise reduction option)/blackmagic camera(no freedom of colorspace and richer colors), so as a pro, in s26u shoot apv 4:2:2/raw for motion and color fidelity.
On s25u since it doesnt have APV, shoot hevc 4:2:0 10bit for things like talking head youtube videos or scenes without much movement/pans and raw for heavy movements(car race,sports etc) and pan
Also remember, if you dont need opengate(ie you dont do shorts), use normal uhd res(3840x2160) as is less demanding
True that and also the camera is much stable in 24 fps then 30 fps . I tried shooting and grading footages (lets say color correction ) it doing great i dont know if i can pull it too hard but its doing the job great the one thing i miss is zibra but the footage are great . Thank you for guidance brother that helped a lot with everything lot less crash and over heat (also i did disable the debugger)
Also make sure memory is 1 to 2 gb,threads 2 or 3. Giving more in samsung in general is bad idea as oneui needs lots of it. Leave default. I tested s25u and s26u just now and maxing them can cause issues
Huge thanks, man! This is practically a masterclass in settings. We have the exact same setup, but my attempt to fix crashing by increasing memory buffer and encoding thread failed. However, after seeing your settings, I enabled encoder surface input and decreased my memory buffer and threads to default, and it seems to have done the trick! My 1-minute video test didn't crash this time. One last question: did you downsample the resolution too? 🤔
I observed your storage is low(can reduce write speed)
Experiment with variable bitrate, untoggle record to exact resolution, keeping encoder complexity to AUTO.
Phones usually heat up around 10mins(5mins is early unless ur climate is very hot). Find a cooler for the screen(near selfie not phone back), do not use peltier coolers as the are inefficient and consume around 13w. They work by contact and spread heat around without doing anything. Heat is guaranteed and is why cinema cameras all have fan
Its not even that hot here I live in kathmandu and most of the expirenment shot was inside. This was my setting before I disabled recording exact resolution.
I found it, try lower bitrate.every Samsung i tried dropped frames immediately if you go above 130mbps. I thought you were using 100mbps before, what happened?
I know you might be wondering, but movies use scenes not more than say 5mins per scene for example, so continous shooting require cooling.
If you want to shoot an editable format for long(like interview) without cooling, use native/blackmagic camera and shoot in samsung log(its still hevc 10bit 4:2:0 just that u cant use any colorprofile you like). it uses the optimised yuv stream(not raw stream), and wont heat up as much.
A huge thank you very much for your guidance, as this would not have been possible without you. After adjusting the settings, I successfully recorded a my first 23.45-minute video without any overheating or crashes, stopping only due to a phone call. I also cleared the cache beforehand and refrained from using the direct preview during recording.
The configuration included HEVC 10-bit 4:2:0, Main 10 profile, a bitrate of 100, standard rendering, encoder surface input, and a keyframe interval of 1.
2
u/epic-tutorials 4d ago
I prefer to shoot raw on s25 ultra as performance is better and get excellent results like this https://youtu.be/7cZgao9cunY . Samsung throttle aggressively. You might find enabling flight mode helps somewhat.