Відео

We are working on a tutorial about how to manage in general :D, but if you join our Discord you can learn much more stuff about this topics

Please join our Discord, you can find many information's there

Android devices have only 10 Bit 420 HW encoding

MotionCam can record even 120fps, if the phone allows it!

@@MotionCam Also in HEVC 422 10 bit?

Hello, any external ssd should be good enough (eg: Samsung T7)

Hello, yes ofc :), you can check our Demo Version

was full sensor and resized to 8k timeline

Totally get what you're saying! These shots are on a tripod because we wanted to show what the footage can really do at its best. MotionCam isn’t trying to be a point-and-shoot app like the iPhone. It's more for people who want full control and are willing to put in a bit of effort to get cinematic results. That said, we do support recording gyro data, so if you’re shooting handheld, you can stabilize your footage in post using tools like GyroFlow. It takes a little more work, but the payoff is massive: you get both smooth motion and the insane quality of RAW video. MotionCam’s really about giving creators the tools to push boundaries. It’s not for every use case, but for those who want more, there’s always a way to make it work-and the results are worth it. 😊

Stabilization is based on OIS, you can try the. demo version to see what works or not. Cheers

@MotionCam Does Galaxy Watch work with MotionCam?

@@blizzforte284 I dont know, you can test yourself :) (with Demo version)

Stabilization is given by OIS module (is hardware)

@MotionCam So it's the same as stock app stabilization? What about opening and controlling the app and recording video with the Galaxy Watch5 Pro?

​@@blizzforte284not possible

If you refer to xiaomi aperture, not possibile officially due to camera api limitation, but with root is possible yes

OIS functionality depends on the specific device! MotionCam is designed for users who want full control over their content. For those looking for a point-and-shoot experience, the stock camera app is more than sufficient. Cheers!

Please join our Discord.

Only Samsung can make that happen :D

Join us on Discord, Cheers

Hello, it got improved. Thanks

In time we will be able to have active noise reduction filters, and we will do :D

This clip is HDR

@@MotionCam ah it's loading in HDR on my laptop now. Wasn't on phone. Usually does even on phone

I wouldn’t say there’s a definitive 'best' - both devices handle HDR very well, but their workflows differ significantly. It really comes down to the user’s needs and preferences. One approach might suit a more automated, out-of-the-box experience, while the other provides more flexibility and control, which may appeal to those who prefer fine-tuning their results. Each has strengths depending on the scenario and the user behind the camera.

Yes it does

Hello, yes it does

Noise reduction is applied regardless of motion or stillness

@@MotionCam Yes I mean it's impoved the pixel quality that where the area won't move, for example the buildings, as the comparison the raw footage has uniform noise distribution

Raw storage is not reduced by any form... ( You capture the stream as it is)

@@MotionCam I saw there are significant chromatic aberration at the high contrast area in the MotionCam footage, so I guess it's recorded in storage reduction mode （by skipping 2 lines of 3) , haven't using the full resolution mode to reduce the chromatic aberration.

@@MotionCam Hopefully one day we could have pixel binning raw mode by combine 3x3 pixels by CPU on the cell phone in realtime

Hey thanks, don't forget YT re-encode and highly compress this uploaded footage :)

not far from each other, will share sources today

you can try Demo version

Oneplus 8 pro and oneplus 11

@MotionCam Thank you very much.

Hey, what device?

V4 development just started, more info will be announced on Discord

@MotionCam thank you!!

For that it is best to join our Discord, and hop on the ride ;)

@MotionCam thank for the answer I will join it 🙂

MotionCam is sold only on Google Play

Appreciate the feedback! Just to clarify - this is HDR footage, so it’s best viewed in an HDR environment to fully see the differences. The video’s purpose is to highlight the processing differences rather than being a polished final grade. Since UA-cam compresses and discards a lot of details, the footage was pushed a bit to make those differences more visible. Thanks for your interest - we’ll be sharing the source files soon if you'd like to take a closer look!

Я подумал, что он сводил картинку под айфон :)

When I mention chroma in the context of raw, I'm referring to the color detail and separation between channels, not chroma in the YUV sense (since, as you correctly pointed out, raw is RGB-based). The term 'chroma' here is more about visualizing color purity and channel independence. To display chroma details, I use a custom DCTL in DaVinci Resolve that isolates the color information by subtracting luminance from each RGB channel. This technique highlights the differences in how each color channel carries information. The reason this comparison is relevant in raw vs. iPhone video is because iPhone footage (or other log-compressed videos) often undergoes heavy chroma subsampling and aggressive denoising, which can blur fine color details. Raw data, on the other hand, preserves more native sensor information without this subsampling, allowing for clearer separation between red, green, and blue channel details. So while it's still RGB, the way each channel retains or loses color information is different between processed log video and raw. This visualization helps reveal how much color data is retained or smeared, exposing compression artifacts or the 'painterly' effect you sometimes see in compressed footage.

@@MotionCam Thanks a lot for the detailed answer!

@@MotionCam One more question if I may. If you substract luminance from the RGB channels you get colorful but very flat image. However, your version is contrasty, is there any other processing you do here? It doesn't seem like a simple contrast adjustment.

@@AttilaBakosArt Good catch! When isolating chroma by subtracting luminance from RGB, the resulting image tends to be flat because chroma, by nature, has much lower amplitude compared to luma. To address this, we applied a non-linear remapping of chroma data into the luma channel. The process works by redistributing the magnitude of chromatic differences in a way that exaggerates smaller variations while preserving larger ones, which prevents weaker chroma signals from disappearing into the shadows. Essentially, it’s like stretching chroma detail into the luma domain for clearer visual separation. This remapping uses a perceptual scaling curve rather than a simple contrast boost. A linear adjustment would raise the entire chroma range uniformly, but that wouldn't emphasize the subtle shifts we're interested in. By applying a curve, areas with minimal chroma information stay closer to their original values, while regions with significant chroma differences are amplified. This produces the higher-contrast appearance you're seeing, even though the underlying chroma data remains the same. In practical terms, this lets us inspect how much chroma information survives processing (or is discarded), making artifacts and discrepancies between different capture methods much easier to spot.

@@MotionCam I appreciate the effort you put in your answers very much, and again, thanks a lot! I built my own DCTL a long time ago for the same purpose but I only analyse the Cr and Cb channels in grayscale with added linear contrast. I tried to convert them back to RGB with a fixed luma value, but as we discussed, the image was too flat and I couldn't figure out a clever way for a better visualization. Your method is very pleasing, I'll try to do something similar.

Dont worry :) iPhone 16 Pro is a great device (out of the box, easier workflow, etc;)

Looking forward on next x200u

Is more about RAW than the device ;)

I believe more people own the S24 Ultra than the Xiaomi 14 Ultra, suggesting that more raw video comparisons would benefit them.

Lets see what s25 series brings ;) ​@@adamsmite6744

​@MotionCam Correct. It's entirely about post processing or no post processing. Post processing takes control away from the user. This is perfectly acceptable for general users but less desirable for creatives who want to be in control of their image. The bigger sensor of the Xiaomi will have nearly a negligible effect on the final output. The tiny differences won't even be processed by the eye of a general audience.

​@@matthewhartman7176yeah, I agree but on larger screen or Tvs and monitor I definitely see it.

Thanks, we will do after V4 is out

@@MotionCam seems v4 is rumbling，really looking up to it

Image quality is not filmmaking, it's a fraction of the equation. There are masterful films created with subpar image quality. Just setting the expectation and definition of "filmmaking" correctly so that ppl can learn more about the craft itself as a whole.

By the time Apple reaches there we might as well shift to 8K Bayer 100FPS with a 12bit linear ADC 😀🤞

As you should, each device has its own advantages, noise was removed in post. Thanks