[Jim Bachalo]

Sure Davinci Lite has a nicer interface…almost looks like Apple designed it, but I’m still struggling to get ’roundtripping’ to work with PPro.
Having to render in Lite to get your files back into Premiere is NOT roundtripping in my book. Unfortunately will continue to stick with CS5-CS6 until this gets ‘Resolved’

Local is the new global

[Jim Bachalo]

Thanks Joseph

yes still XML issues remain apparently.
Tried the latest version 8.2-1 but when trying to import the XML Premiere simply reports that there was a generic error.

if anyone can get this to work, would luv to hear from you!…otherwise am sticking with PPro-AE and Dynamic linking….not round tripping but at least it works.

Local is the new global

[Jim Bachalo]

Tried the beta version of Davinci Resolve Lite, according to this thread it SHOULD work
https://forums.creativecow.net/readpost/277/14302

but the last time I tried, the problem I had was importing my Premiere Pro XML into Davinci, could only see rgb static noise as previews on all my footage.

Local is the new global

[Jim Bachalo]

Yes I had the beta version, unfortunately all I see is visual rgb static when I import my xml from PPro:)

With the non beta version it works, though its not true roundtripping.

I can see the potential of a node based editor like Davinci, but starting to feel that you really need a maxed out system and hardware to make the best of it. Not sure it is really optimal for a mouse only interface.

For any colorist working on feature length material I can see the time savings, but not so sure those savings will be evident for short film (under 10 minutes) projects.

I’ll probably stick with my PPRO to AE dynamic link workflow for now.

As an aside, interesting to see that even the free version of Davinci renders out files in Prores 422 format.

Local is the new global

[Jim Bachalo]

ok have the PPro export to Davinci import working. My problem is getting the CC result back into Premiere. If I simply export the project from Davinci as XML, I get a generic error when I try and import the Davinci project XML back into PPro.

Can anyone tell me if you must render your file within Davinci if you want to bring it back into PPro?

There must be a round tripping workflow that works.

Anyone?

Local is the new global

[Jim Bachalo]

Thanks!
Yes I’ve found that compressors in Audition are your best friend. Also I prefere NOT to normalize but to amplify instead because normalizing 2 different tracks with different peaks will give you 2 tracks with different average volumes.
Also need to keep reminding myself to boost the gain as much as possible without clipping when I record to help minimize the noise floor.

I’ve gotten some quite amazing results using only an inexpensive lav, removing noise, adding some compression eq and reverb to bring back some room presence.

Local is the new global

[Jim Bachalo]

Nice font!
reminds me somewhat of interstate

Local is the new global

[Jim Bachalo]

Thanks Joe!
Someone else reminded me that Helvetica Neu (as a dfont) is included with any purchase of OSX since Leopard so will probably use that.

Local is the new global

[Jim Bachalo]

Guess I should know this but it’s been years since I was immersed in the world of page layout and typography.

So the Helvetica Neu family that gets preinstalled with OSX can be used on ANY commercial project? That is good news.

Local is the new global

[Jim Bachalo]

Thru some trial and error, isolating exactly where this was occurring, was able to resolve.
Outputting uncompressed the render consistently hung, but 1 frame later, enabling me to confirm where the issue was.

I’m using dynamic linking for most of my 6 minute sequence.
In AE, I am using an animation reset on 1 short 5 second clip. In that preset is an effect that only works up 16bpc. My project was in 32bpc. In addition, there was a yellow exclamation mark next to that one effect.
I disabled that 1 effect in the preset (rather than switching my entire project to 16bpc, did another render defining my work area just where my render was hanging, and it outputs fine!.

Moral of the story I guess is to pay attention to yellow exclamation marks! Though I don’t think this should have stopped my entire render chain. Pretty sure this must be a bug. Have lost several days trying to resolve this. And not only did this issue stop my render, I was required to do a force quit on both AME and Premiere to start again.

Local is the new global