New Beta out Today?

[Adam Hendershot]

I’m getting the same 7-8fps that others seem to be getting with pro-res HQ output. This is with a Mac pro 2.66ghz 12-core with Windows under bootcamp. Source footage is uncompressed QuickTime 1080/23.98. Osx on the same machine is around 25fps.

Just for comparison, the other format we export to regularly, mxf 115, gets around 37fps in Windows and only 21 in Osx.

[Vladimir Kucherov]

Around 8 fps was what I was getting but I wasn’t sure if this was because I was reading/writing media on the same drive, as opposed to a RAID.

So the slow render is just a pro-res on windows issue it seems?

[Gabriele Turchi]

i am on it for the new forum , but how we setup a pro forum without having accessional user jumping In ? maybe the user have to be accepted and monitored by the administrator ?

i rally wish that the Dav team could understand how this Lite thing is transforming everything into a Mess , not good for their name either , for their support , for the forums etc…

I strongly wish that new update will be called “Resolve DI , or PRO or something like that , and will be targeted a higher price

Also : one note about this beta : red have new SDK and new RR driver for a while , resolve did not changed that for a while even now that is in Beta… there are BIG bugs reported (by myself directly to them for sure and on the forum ( like the fact that resolve automatically replace matching TC shot on the timeline without giving the C conflict and so loosing grade etc.. (i suggested a “quick fix ” adding a config page setting that stop (under user choice ) the resolve auto replacement behavior …) …. 3 beta come out , no fix ….

I am pretty optimistic that they are cooking something big for the NAB … but we need fixes now ,and the problems is that Now sooo many are complaining about soooo many things (lite issue etc..) that more important things gets forgotten …

g

Davinci Resolve Control Surface
MacPro
Cubix desktop 4
2 Red Rockets
GTX470+GTX470+GTX285
24GB RAM
HP Dreamcolor
Panasonic 58PF Plasma

[Lee Niederkofler]

Another vote for a pro Forum!

lee

[Gabriele Turchi]

maybe BMD should set it up and invite Us in (or we can ask them to be invited )

so they can monitor what we are talking about without having hundreds of thread about asking “”what cheap mac is necessary to run Lite”” or “”when the tangent element will be supported””” or threads about people offending other people “”EGO fights “”…

g

Davinci Resolve Control Surface
MacPro
Cubix desktop 4
2 Red Rockets
GTX470+GTX470+GTX285
24GB RAM
HP Dreamcolor
Panasonic 58PF Plasma

[Mike Most]

The auto replace behavior is driving me nuts, too. I’ve probably lost at least 2 hours on a major network television series because of it. It’s especially annoying because you can’t have two sessions open at the same time. In my case, the show in question is supplied as an Avid MXF mixdown and we get multiple mixdowns over the course of a few days as large numbers of VFX shots are integrated by the editors. We have to use Color Trace to recover all previous corrections, and whenever we get an individual updated shot, the auto replace nonsense forces me to actually open the previous session, save a still with the correction (losing any dynamics in the process), re-open the new one, and reapply the correction by importing the still or opening the previous session in the Gallery. Not only that, it sometimes puts the new shots in the wrong place, and I don’t always discover that until it’s played out.

However you look at it, the auto replace stuff needs to be a user choice at the very least.

[Gabriele Turchi]

i agree , i am pretty sure that track down the wrong behavior is a mess , but add a setting in the config page the BLOCK the auto replace is a CONCERN that should be addressed before add ProRes on Windows …we are all loosing hours (but mainly grades that sometimes needs to be Re done ) because of that

g

Davinci Resolve Control Surface
MacPro
Cubix desktop 4
2 Red Rockets
GTX470+GTX470+GTX285
24GB RAM
HP Dreamcolor
Panasonic 58PF Plasma

[Mike Most]

It shouldn’t be and probably isn’t either/or. Adding ProRes on Windows was probably somewhat straightforward, particularly if they’re using the ffmpeg open source version (which is probably the case, given that it doesn’t write 4444 at this point). Fixing the auto replace behavior is a change in the internal code.

Personally, I’d like to see the ProRes integration on Linux ASAP…..

[Dmitry Kitsov]

Thank you, Adam.

[Dmitry Kitsov]

Thank you, Vladimir