Dear Adobe - still the same mess with IMACpro

[megacinn]

Dear Adobe

after all this annoying mess with version 12.1.x I just realized that there is a new version 13.0.

Even if my subscription is ending in about 3 weeks , and, as you know, I already switched to resolve, I wanted to give it a fair try.

Installing a separate instance of V13.0 ..opening a 12.0.1 project...everything seems fine.

As you might remember , we all had tremedous trouble using Imacpro's , so I expected that you adobe , used the last 6 month to fix at least the most critical issues .

These have been the QT-disaster and the 4K-HEVC disaster.

...exported 109sec of 4Kp30 material to the only avaliable HEVC option.....

...setting to VBR 1pas

...setting to "target bitrate : 13Mbit"  (maxbitrate still missing since 12.1  !?)

...setting to "hardware accelaration"

.. estimated filesize : 178 MByte (shown in your export window)

got -- 973MByte !!!! ( that is 71 Mbit/s instead of 13 Mbit/s)

if Patrick Palmer is anywhere here around ; I really appreciate a statement about this behaviour , because I personally communicated this problem (as many others) to adobe (and him) SINCE AT LEAST 4 MONTH NOW .

Dont bore us with explanations about what hardwareaccelaration is , and what not......I had plenty of time to investigate what exactly is behind the Intel-Accelaration and what cpu exactly is capable and why.

As well I know many facts what the difference is to the metal-based mercury playback and when is each one of them is in use.

So ... I want to have an offical statement whether you are working on fixing this , and when you can provide us with a fix.....

..else , everyone with an ImacPro be warned ...it seems that adobe is still not , and maybe will never be again a good choice in this combination.

before bothering asking for specs:

ImacPro

OSX 10.13.4

PremierePro 13.0

everything else ... default

[John T Smith]

This is a public forum with "some" Adobe staff participation, use the links below to make a report

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for feature requests or bug reports

-or Feedback forum https://forums.adobe.com/community/creative_cloud/desktop-app/content

[thnord]

Thank you for your report. We are able to reproduce the issue and have found that it only impacts systems running macOS 10.13. Users running macOS 10.14 are not affected. We will raise this issue with Apple directly. We apologize for the inconvenience. 

As an aside, you are correct: there is no way to set a max bitrate for hardware acceleration. This control is not made available to us by the OS.

UPDATE: We have found that in some cases the issue may be resolved by updating to macOS 10.13.6 so you may want to try that first.

[megacinn]

so , a few weeks later I just updated to the next version 13.0.1 in a very vague hope of getting this fixed.

Stupid of me...of course ...the problem still persists.

So this is the 5th update since the problem occured in april 2018.

Only for my interest .... will there ever be a fix or , are you waiting until all the customers with 12.13 have been gone away.

How shall we undestand your advice upgrading to 10.14? There are some others who did that and became many other problems.Then some adobe's told that this version is not certified for current use ?

Is it now an official proven advice upgrading to 10.14 (I read many other complaints about that OS (not only at adobe) or how can we expect to get that software ever to work ?

btw... for myself it's not so important anymore ... 11days left....

[R Neil Haugen]

Have you tried 10.14?

Neil

[megacinn]

......Have you tried 10.14?.....

did you ?

can you recommend it ?

what would be my benefit ? ... is it as much as performant as 10.13 or even better ?

is premierepro 13.0.1 officially supported for 10.14 ?

...an update of an OS is always a very risky and timeconsuming process. At the moment when I'm writing my results of testing something , it would be astonishing that I have experiences at the same time of another OS .

why should I update , before someone else can give me a proven advice doing so ?

[R Neil Haugen]

I'm on a PC, so no, I can't try it.

However, some other Mac users have found 10.14 works better within PrPro. And the engineer that responded earlier noted this is only reported with 10.13, does not happen in 10.14.

Caution in changing an OS is wise of course. I'm always bewildered by those who jump to new OS without watching for reports of troubles. So I don't fault your caution.

In another thread, a Mac user has determined that all his Mohave (10.14) rigs do some slightly different things with image color/contrast even output through Blackmagic external calibrated boxes than his High Sierra (10.13) rigs do.

Which is also troubling.

Neil

[thnord]

Just to add to the conversation: I did note that in some cases updating to 10.13.6 has been seen to resolve this issue so if you are hesitant to update to macOS 10.14 then that may be an option. Now, with that said, Premiere Pro 13.0 and higher are supported on macOS 10.14. So while I can't give you specifics about how your particular workflow will perform, I can tell you that it is supported.

[Mo Moolla]

got -- 973MByte !!!! ( that is 71 Mbit/s instead of 13 Mbit/s)

why should I update , before someone else can give me a proven advice doing so ?

Hehehe man u kill me. I can however only begin to understand your frustration with this. From what I have "overheard" this issue is trying to be addressed but there is no definitive solution as yet. I don't use iMacs but I have a few Mac Pros so I have been down this road before. Tried different GPU's, even changed CPU's from 2,4 to 3.06Ghz (have to admit it was a pet upgrade as well)...and bit rate and size outputs varied considerably. Apple touting ATI GPU's instead of CUDA support still bewilders the hell out of me and as for METAL...well, hmm let me remain calm and say nothing.

Good luck with Resolve Studio. Great for collaring but sucks as an NLE unless you have a seriously strong (yet again ATI) card. Still a bit finicky as a NLE in my opinion. Fusion effects rely very heavily on the GPU and if you aren't used to node based workflows its going to be a bit of a uphill. Best of luck and apologies for going slightly off topic.