[Janmaarten De wit]

Such a shame, right now it feels like driving a Ferrari with 3 wheels…

I hope they fix it in the next update.

CS5.5 had minor problems with MP as using it on a MacPro compared to CS6 .(dont know about the Windows version)

—-
http://www.janmaartendewit.com
—-
Motion Graphics Designer/ Editor/ Camera Operator
—-
Amsterdam, Netherlands

[Janmaarten De wit]

Since one month I’m working with a new system. (windows)
Our MacPro’s became to slow even with a GTX 570 upgrade.

We use it for heavy 4k/5k post work and Resolve.

The case is that it hangs very often on when rendering MP.
Means hanging on 2 of xxx frames or ‘Initialising background process’.

The system has 96gig of ram and 24 virtual cores (2x 6core Xeon)
Set to 3 gig per core I stil have a huge amount of ram for the overall program.

I’m very unhappy because a lot of times a cannot take profit from the system’s power.

Any more takes to make this more reliable?

—-
http://www.janmaartendewit.com
—-
Motion Graphics Designer/ Editor/ Camera Operator
—-
Amsterdam, Netherlands

[Janmaarten De wit]

My best findings are, based on your comments.

Native edit .r3d in Premiere.
Post shots and time remapped shots as DPX on the timeline.

XML export from Premiere.

And than working with a .r3d / DPX mixed timeline in Resolve?

Is this the best setup?
A straight XML with speedchanges ect are giving problems in Resolve.

Any advice is welcome 🙂

—-
http://www.janmaartendewit.com
—-

[Janmaarten De wit]

Wow thanks for the fast response.

So I just need to set the monitor and export from Resolve to Rec 709.

The reason I work with a DPX export from Premiere CS6 is that there are some shots who have been trough post production.
(I added some stars in the sky and removed a leg from a tripod)
If I render these shot to .r3d they turn out grey.

Now the timeline in Premiere consist of .r3d and post shots in Animation codec.

Still I got the feeling this is not the best workflow…