Ursa Mini Pro 12K is here

When they hacked into Braw after it's release, they said they found evidence of downscales, which would make it easier to edit. I personally regard it's more compressed modes, like I regard prosumer camera codec. While wonderful, there are still a price like in most lossy compression. Except in this codec, doesn't just give you an impression of accuracy like with other codecs, it also gives an impression of speed. Just think of all those people who are going miss out configuring their $30k-$60k Apple Mac computer to do post.

... Just think of all those people who are going miss out configuring their $30k-$60k Apple Mac computer to do post.

Thank goodness I didn’t waste that much although it can be fun rendering at about 240 fps.

With the BRAW API, before the 2.0 version (adding support for the new 12K footages), you could get from your BRAW 4 resolutions : 1/1, 1/2, 1/4 and 1/8. It is important because if you choose 1/3 or 1/16 resolution for playback for example, it is not optimised (If 1/3 : 1/2 will be rendered and then the software (Resolve/PPro) will downscale it : so it takes more time than if 1/3 was directly generated from the BRAW API).

On the new 12K footages, these resolutions are 1/1, 2/3, 1/3, 1/6. So the minimum resolution you can get from the BRAW API on a 12K footage is 2048x1080 . So the same as if you were with a 4K footage and 1/2 Resolution.

We hope to get new resolutions choice from the BMD API, especially for those new BRAW 12K footages, to improve playback performances.

I tested in Premiere Pro OSX with :

• with the official Blackmagic RAW 2.0 Beta1 : https://www.blackmagicdesign.com/fr/support/
• with BRAW Studio 2.2 Beta1 : https://www.autokroma.com/blog/BETA-For ... Science-V5

Tested in Premiere Pro OSX (with the official Blackmagic RAW 2.0 Beta1, but also ), 12K takes time to render (like at least one second for one frame in Full Res, rendered on CPU only with my macbook from 2012 so not a good workstation but that was just for a test), so decreasing the resolution playback is needed if you are not using proxies, and 1/6 is not enough IMHO !

Hate to be that person but when will we see more footage from the 12k?
I’m about to preorder and I’ve been really hoping to see low-light and HDR environments.

Have you seen the other three clips from final hardware in a dark but lit studio Scenario on BMDs website ?

Everyone seems to miss them and not realise they’re there as part of the BRAW tab from the camera page.

JB

I have, and it’s really nice.
I’m just looking for something more non-setup I guess?

And just more stuff to play around with. Anamorphic, handheld, etc

With the BRAW API, before the 2.0 version (adding support for the new 12K footages), you could get from your BRAW 4 resolutions : 1/1, 1/2, 1/4 and 1/8. It is important because if you choose 1/3 or 1/16 resolution for playback for example, it is not optimised (If 1/3 : 1/2 will be rendered and then the software (Resolve/PPro) will downscale it : so it takes more time than if 1/3 was directly generated from the BRAW API).

On the new 12K footages, these resolutions are 1/1, 2/3, 1/3, 1/6. So the minimum resolution you can get from the BRAW API on a 12K footage is 2048x1080 . So the same as if you were with a 4K footage and 1/2 Resolution.

We hope to get new resolutions choice from the BMD API, especially for those new BRAW 12K footages, to improve playback performances.

I tested in Premiere Pro OSX with :

• with the official Blackmagic RAW 2.0 Beta1 : https://www.blackmagicdesign.com/fr/support/
• with BRAW Studio 2.2 Beta1 : https://www.autokroma.com/blog/BETA-For ... Science-V5

Tested in Premiere Pro OSX (with the official Blackmagic RAW 2.0 Beta1, but also ), 12K takes time to render (like at least one second for one frame in Full Res, rendered on CPU only with my macbook from 2012 so not a good workstation but that was just for a test), so decreasing the resolution playback is needed if you are not using proxies, and 1/6 is not enough IMHO !

Yes, that is what I was asking about. You really are rendering a 2k mpeg or something image (actually this sounds like something I wrote years ago. Pretty irrelevant anyway, as that is how wavelet codecs worked anyway) quickly on those laptops, like a proxy, not a 12k image. So, what is the real 12k recode time of changes. Are we going to be waiting at least 60 hours an hour of footage, to do a final version on some old laptop. How fast on a good laptop?

Did you read my entry about speed on a Mac mini with an eGPU?
If you can tell me precisely what you'd like to have rendered, like which of the demo clips, which effect at which resolution for output, I can test it.

BTW, the backlit shot of the 'angry young man' is showing chroma noise and minimal FPN only if I increase contrast in the dark parts to insane levels. Remember, it's a beta camera…

Thanks Uli

As a speed test, it's 12k, to see how slow outputting to a finale file is, graded however, it's mainly testing codec performance, so aslong as it thinks it has to recompress everything. We could probably extrapolate from the mini gpu's performance from there. I suspect it will be 10x+ faster than the laptop CPU. But is it possible to save to Braw yet?

I wonder if these systems do while you are still working behind the scenes frame processing yet, which would skew results too.

You can't save to BRAW, other than trimming. And you'd need to be more specific about grading, since that could be very simple, like one node, or very complex, like several nodes plus NR and more. The codec to save into doesn't need to slow things down significantly, one could save into ProRes instead of H.265.

Will it even be possible to render at 12K considering the GPU memory requirements? I suppose an integrated CPU/GPU would work since it can always use system memory (with a significant performance impact), but with a dedicated GPU we're already struggling at 4K sometimes. Throw some speed warp and noise reduction on there and watch it burn.

I know 12K won't usually be the delivery format. But what if you need to render out something at full resolution temporarily for VFX?

[Peter Chamberlain]

There are 48GB vram GPUs available and we have many projects rendered above 12k. Amusement rides for example, also in stereo3D.

When, where could we see those?

There are 48GB vram GPUs available and we have many projects rendered above 12k. Amusement rides for example, also in stereo3D.

When, where could we see those?

There are 48GB vram GPUs available and we have many projects rendered above 12k. Amusement rides for example, also in stereo3D.

It would be theme parks. So Disney and the like.


JB

All time best post, John! Kim walked into that one.

This guy has done an in-depth analysis of the ursa 12k and whyiencea need to have camera. He also talks about the color science. some of it goes beyond me. But very ineteresting

http://filmscientist.com/mblog/2020/07/ ... necessary/

link Corrected thanks to john Brawley

Ricardo Marty

That link is dead.

Just truncate the link after "mblog", you'll get there.

This guy won't win any awards for coloring grading. As always, the 'product' is only as good as the weakest link, the camera can get lost in it.

Correct link

http://filmscientist.com/mblog/2020/07/ ... necessary/

JB

Another observation, for those without a Mac: my Mac mini with an RX 580 eGPU with (humble, at todays standards) 8 GB is handling the 12K demo clips even in a 8K DCI timeline. It does not crash. No GPU memory full message!
I can use temporal NR without crashing. I can use Aperture Diffraction, another demanding effect, without crashing. Of course, it's crawling at snail speed, but it's stable. It stalls with both added, but no crash.

I'm nothing less than impressed.

When, where could we see those?

There are 48GB vram GPUs available and we have many projects rendered above 12k. Amusement rides for example, also in stereo3D.

Yes, when can we see the 16k-32k fullframe+ cameras Peter?

Uli, it would be a simple test of raw performance.

It's 12,288/6 not 12,288/3.

dur.jpg (74.02 KiB) Viewed 536 times

This is asswards as well.

bmrgbw.jpg (37.19 KiB) Viewed 536 times

Science.

Good Luck

Some rendering on above mentioned hardware:

4K DCI timeline, four nodes, one with temporal NR.
Rendered into 4K DCI ProRes 422 HQ, scaling and debayering (we'll need a new expression here) forced to max.

8K R3D source needs 0.6 sec/frame. 12K BRAW needs 0.3 sec/frame. Nuff said.

debayering (we'll need a new expression here)

-> demosaicing is the correct expression I learned from Hook.

well, i bit the bullet and preordered!
Super excited about this camera. hopefully it will arrive this month! (wishful thinking? haha)

I plan on moving to PL mount lenses with the SLR Magic APO Hyperprimes. They look great and i'm excited to try them out.

Will it even be possible to render at 12K considering the GPU memory requirements? I suppose an integrated CPU/GPU would work since it can always use system memory (with a significant performance impact), but with a dedicated GPU we're already struggling at 4K sometimes. Throw some speed warp and noise reduction on there and watch it burn.

I know 12K won't usually be the delivery format. But what if you need to render out something at full resolution temporarily for VFX?

With AMD Metal or OpenCL (and maybe even with a NVidia card running OpenCL, haven't tested it) it's no problem. CUDA is fast but also very memory hungry.

Adam, very excited for you! Nice to know my APO primes will get a workout on that camera. Really looking forward to your findings. Having some test results with people in addition to everything else will be sweet eye candy.

Some rendering on above mentioned hardware:

4K DCI timeline, four nodes, one with temporal NR.
Rendered into 4K DCI ProRes 422 HQ, scaling and debayering (we'll need a new expression here) forced to max.

8K R3D source needs 0.6 sec/frame. 12K BRAW needs 0.3 sec/frame. Nuff said.

As I suspected. Thanks Uli. Still need a reasonable system.

I was going to update a thread I started with a link about what it was talking about. But somebody removed it for no reason.

But here is a link you guys might enjoy:

viewtopic.php?f=14&t=119014

[CaptainHook]

Blackmagic RAW 2.0 Public Beta 2 is now live on the website with Resolve 16.3 Public Beta 2 and adds support for Windows

https://www.blackmagicdesign.com/support/

Blackmagic RAW 2.0 Public Beta 2 is now live on the website with Resolve 16.3 Public Beta 2 and adds support for Windows

https://www.blackmagicdesign.com/support/

Nice!

Blackmagic RAW 2.0 Public Beta 2 is now live on the website with Resolve 16.3 Public Beta 2 and adds support for Windows

https://www.blackmagicdesign.com/support/

Is that our 2020 resolve?
No resolve 17?