GH5 Premier Pro fix for GH5 10 bit to be released "very shortly."

S

Steve Ogden

Well-known member
https://forums.adobe.com/message/9642312#9642312

text of message:

We wanted to update you on the current status of the Media Cache workflow.

We have an update to Premiere Pro CC 2017.1 (11.1.x) in the pipeline that will be released very shortly. It will include additional measures to safeguard the Media Cache workflow beyond what’s already released with 11.1.1. It’s an update highly recommended by the Premiere Pro team.

The most important change is that only media cache files of a known file type (such as *.pek, *.ims and *.cfa) will be deleted according to the cache management preference. The folders they are in will remain on the system. Additionally, the Media Cache management will be off by default – a lot of users have requested to switch to an opt-in model, and that’s what it’s going to be moving forward.

This next update will also include a number of performance improvements and bug fixes in other areas, and it will include support for the 10 bit formats of the Panasonic GH-5.

Stay tuned for more info which we’ll post to the blog:
https://blogs.adobe.com/creativecloud/tag/adobe-premiere-pro-cc/?segment=dva
 
It seems to work now in the latest version.

However 8 bit full range video from the Panasonic is still interpreted as Rec.601 by Premiere Pro. 10 bit full range works OK and is correctly interpreted as Rec.709.
 
Last edited:
Thanks for the report, Cary. Can you tell me specifically:

For 8-bit full range video from the Panasonic, is it interpreted with the BT.601 matrix just for MP4? What I remember from my testing is that MOV files were interpreted with the proper BT.709 matrix and the problem was only for MP4 files.

For 10-bit full range video files, are they now interpreted as full range? MP4 and MOV? In previous versions of Premiere, they were interpreted as video levels instead of full range.

Same question for 6k photo mode files.
 
balazer said:
Thanks for the report, Cary. Can you tell me specifically:

For 8-bit full range video from the Panasonic, is it interpreted with the BT.601 matrix just for MP4? What I remember from my testing is that MOV files were interpreted with the proper BT.709 matrix and the problem was only for MP4 files.
Click to expand...
You are correct, the MOV files are interpreted correctly. It is interesting because for both the MP4 and MOV containers the pixel format is described as yuvj420p.


balazer said:
For 10-bit full range video files, are they now interpreted as full range? MP4 and MOV? In previous versions of Premiere, they were interpreted as video levels instead of full range.
Click to expand...
Not sure what you mean. The way Premiere works is that it scales both legal video levels and full range into float 0..1. With a result that BTB and WTW for video levels can be resp. negative and > 1, which is a good thing!
However unfortunately many operations in Premiere still clip data outside of 0..1.

I did test the 10bit levels of V-Log-L with MP4 and they are correct in Premiere.
 
Last edited:
Yeah, Premiere's handling of levels is inconsistent with almost every other NLE out there as I've recently discovered with my LUTs in Resolve, which I've just migrated to.

I much prefer Resolve's way of allowing you to assign the levels at the clip itself.

I'll be updating my LUTs to fix this inconsistency soon, as it means a lot of non-Premiere users have actually been having their levels clipped by the LUT when it shouldn't be.

It's one of many reasons I'm kicking Premiere to the curb going forward (subscription ad infinitum being another).

Cheers,

Paul :)
 
visceralpsyche said:
I much prefer Resolve's way of allowing you to assign the levels at the clip itself.
Click to expand...
Yes, that offers great flexibility.

But it comes with a bit more work because Resolve is not very good at interpreting the correct levels.
For instance GH5 V-Log L is incorrectly interpreted at video levels so one needs to explicitly set clips to data levels.
 
This is odd. I shot a 4K 10bit commercial with the GH5 on Monday and edited it just fine in Premiere yesterday (before the update) with no problems.
I shot in VLOG at 30fps 4K 10bit. Wonder why I didn't have any trouble?
 
Perhaps someone could help me with a quick question.

I recently downloaded some GH5, 10-bit footage (as described by the poster) and quickly brought it into adobe premiere pro CS6 to find it playback with absolutely no problem.

Am I crazy? Or is something else at play here? Is this a problem that only affects CC?
 
PaPa said:
Perhaps someone could help me with a quick question.

I recently downloaded some GH5, 10-bit footage (as described by the poster) and quickly brought it into adobe premiere pro CS6 to find it playback with absolutely no problem.

Am I crazy? Or is something else at play here? Is this a problem that only affects CC?
Click to expand...


Same here! See my reply directly above yours. So confused. LOL
 
Interesting article Star. Forgive me but I fail to see any relationship between the thoughts discussed there and the topic of this thread?
 
Wondering if anyone could chime in on this? Curious to know how I have no issue importing a 10-bit gh5 clip into pp cs6 without issue?
 
PaPa said:
Wondering if anyone could chime in on this? Curious to know how I have no issue importing a 10-bit gh5 clip into pp cs6 without issue?
Click to expand...

I doubt a lot of people are still using CS6.

If I had to take a guess I would say it is because Adobe uses different decoders in different versions and perhaps the one in CS6 adapts better to the 10bit. You should also make sure it is actually showing up as 10bit. When GH5 footage first came out the 10 bit files worked fine in Premiere but the 10bit didn't look much better than 8bit which was the source of that horrible Cinema5D article. Adobe updated Premiere which then cause the 10bit files to not work. So it is possible you may be able to load 10bit files in CS6 but they may get decoded as if they are 8bit.
 
I am using CS6 and I have loaded a V-Log clip recorded with the GH5 and Atomos Shogun in 10bit/Avid DNxHR. It is indeed recognizing the 10bit file.
 
PaPa said:
Wondering if anyone could chime in on this? Curious to know how I have no issue importing a 10-bit gh5 clip into pp cs6 without issue?
Click to expand...

Part of the issue was that levels weren't mapped correctly in full range files (when 0-255 luminance levels is set in the camera's menus). Not sure if the new version actually fixed that. Anyway the issue is avoidable by selecting 16-235 or 16-255.

And have you verified that the files are imported with 10-bit precision? That's not an easy thing to test.
 
PaPa said:
I recently downloaded some GH5, 10-bit footage (as described by the poster) and quickly brought it into adobe premiere pro CS6 to find it playback with absolutely no problem.

Am I crazy?
Click to expand...
No, you're not crazy, that's just one reason many of us stick with stable production tools with well-earned track records.
 
Thomas Smet said:
I doubt a lot of people are still using CS6.

If I had to take a guess I would say it is because Adobe uses different decoders in different versions and perhaps the one in CS6 adapts better to the 10bit. You should also make sure it is actually showing up as 10bit. When GH5 footage first came out the 10 bit files worked fine in Premiere but the 10bit didn't look much better than 8bit which was the source of that horrible Cinema5D article. Adobe updated Premiere which then cause the 10bit files to not work. So it is possible you may be able to load 10bit files in CS6 but they may get decoded as if they are 8bit.
Click to expand...

I've spent a bit of time trying to figure out how I can even tell if CS6 is treating it as 10 bit. Ii've tried looking at the file properties, but to no avail.
 
PaPa said:
I've spent a bit of time trying to figure out how I can even tell if CS6 is treating it as 10 bit. Ii've tried looking at the file properties, but to no avail.
Click to expand...
Increase the contrast or make other big changes, do you start to see stripes in the waveform? If so your footage might be handled like 8 bit.
 
You must log in or register to reply here.
Back
Top