[Peter Berg]

Any release notes about what has been changed since V9 Beta 3?

Would be nice to know what was fixed and improved.

-Peter

[Peter Berg]

I agree Craig that there are things in V8 that I like better. I do wish they would keep V8 going for awhile longer. Especially for people who are in the middle of big projects. I found a few bugs in V8 and another update to fix those would be nice.

But I was told they will have no more updates for V8 (unless we can convince them otherwise).

-Peter

[Peter Berg]

I wanted to report I am running into this problem as well.

I have some RED Epic footage. Although my footage is only 3K (well 3840×2160). Not doing HDR.

Footage was playing back great in Resolve 8. In 9 (Beta version 3) I can’t get realtime playback with audio on (getting 21fps). With the audio muted, it plays back great (24fps with green playback bar).

It’s a little frustrating. I am playing back a timeline with a Audio Chase Track linked to it (WAVE file, 16bit, 48khz).

Is there anything I can do to make this work? Like I said, Resolve 8 was working with this same RED footage and a Chase audio track. But 9 is having trouble.

Thank you,
Peter Berg

[Peter Berg]

Yes Please!

I have had a few clients give me color notes based on the computer LCD monitor. I have to remind them that the computer LCD is not calibrated and they should not be looking at it (doesn’t seem to stop them).

I have the clients behind me so they can see my computer screen in addition to the client video monitor.

A B&W option would be great and a dimming option would be nice too.

And can we get an option to duplicate a timeline! We have been asking for this option for quite awhile. I want to make a duplicate timeline that I can color with a totally different look sometimes!

Thanks!

[Peter Berg]

Rohit,

I did find a workaround. If I just load 1 MXF file from Resolve and do an Avid Mixdown (so it makes a new MXF file) that will allow me to work. Once I have the mixdown I just have to remove the Resolve MXF file from the media folder and then Avid is happy (since the MXF mixdowns that it makes have unique metadata it doesn’t get confused).

This does add a few extra hours to our workflow which is unfortunate.

-Peter

[Peter Berg]

Thanks for the replies guys.

We like Target mode most of the time because it just makes the workflow a bit easier. One graded flattened file that we can just drop in on top of our ungraded clips.

I find that Source mode works fine. It renders out all the source clips and they have the proper Reel/Tape name. Those will come into the Avid and there are no problems.

It’s just a Target mode thing. Although I have 2 Timelines with only 1 clip in each. When I render those in Target mode, the clips come in fine. Looks like the MXF renders are getting a Reel/Tape name associated with them. So if there is only one clip in a Timeline it almost treats it like source mode? But when there is more than one clip in the Timeline and you render as Target what metadata is getting written into the MXF file?

It does seem like they are getting the same ID and thus the Avid is getting really confused.

Although Rohit, I don’t think I did render in Source mode first. I’m pretty sure we only rendered out in Target mode for this project. Still getting this bug. Is there anything I can do to help figure this out? If the Resolve can give each Target mode render a unique ID, then I would think they would cause no problems in the Avid.

Will you still offer some new V8 updates? To fix small bugs and such? We are in the middle of some big projects and will not be going to V9 for quite a bit.

Thank you,
Peter

[Peter Berg]

Hi guys,

I was told that 5K Epic footage will not play realtime with 1 RED Rocket. Those files are too much for 1 Rocket to handle. So either use 2 Rockets, or take out the Rocket and hope your CPU can handle the decoding.

Not great news.. but I guess the files are just too huge.

-Peter

[Peter Berg]

Thanks Rohit. Is this different between the Mac and PC systems?

I do remember exporting H264 QT files from my Mac Resolve and don’t remember changing any settings. The QT files from the Mac Resolve didn’t seem to have this raised black issue.

So I did try the full range setting in the render window. While the black levels are improved, the still seem very ‘milky’. With the Auto setting they were VERY washed out, so this is in improvement. But it just does not match what my clients saw on my Panasonic Pro Plasma.

While I know a computer monitor is different than a video monitor, something still seems wrong. I checked the file on a few different computers and the black levels just look wrong. Even the black background on my computer desktop is darker than the blacks in my Resolve H264. When I did the grade, I made sure the blacks were at 0mv on my video scope.

Could there be something else going on? Is there a certain version of quicktime that you recommend? Also why would you render as video levels for a H264. Those are almost all the time viewed on a computer. How does the ‘Auto’ setting work for various renders?

Thank you,
Peter

[Peter Berg]

Great letter Philipp.

I hope they listen to their customers and improve the implementation.

-Peter

[Peter Berg]

I agree with Ernest. We are on Snow Leopard and it’s working great for us. Wish that Blackmagic would keep Snow Leopard as an approved OS if possible.

-Peter