Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
markusw90010395
Explorer
markusw90010395
Explorer
Activity
May 14, 2019
12:12 PM
The update just showed up. Yes, grid scrolling is improved. The movement is closer to being fluid now. From what I can tell the jumps between screen updates got reduced. It updates more frequently now, which is closer to the appearance of a smooth scrolling movement. But we can still see the jumps which leads to a slight jitter-effect. I am very grateful for the improvement but also for the promise that one day this problem will be fully fixed.
... View more
May 14, 2019
11:55 AM
I don't see an update - my latest version is still Lightroom CC 2.2.1
... View more
Apr 25, 2018
03:10 PM
2 Upvotes
I have run this test After Effects Performance Test File on Vimeo on my iMac Pro, 8-Core 3.2 GHz, 64 GB RAM, Radeon Pro Vega 64 Conclusion: the previous version of AE renders quite a bit faster than the new one from April - at least as far as this test ist concerned. After Effects (CC 2018) 15.0.1 - 4 min 51 secs After Effects (CC 2018 - April) 15.1 - 6 min 6 secs (!!!) I was also monitoring how AE is using the cores of my processor while going through this test render. Even though all cores are being used, overall CPU usage is only 62%. Exporting with Media Encoder on the other hand uses all cores almost at full capacity.
... View more
Apr 05, 2018
11:08 AM
Thanks. I'll just switch to 1-pass from now on.
... View more
Apr 05, 2018
10:57 AM
Thank you, thnord. You are right. Hardware encoding does work on the iMac Pro. Here's what's weird (and why I initially thought it was not supported) 1) H.264, VBR, 1-pass = Hardware accelerated 2) H.264, VBR, 2-pass = Software only What could be the reason for that?
... View more
Apr 04, 2018
07:10 PM
2 Upvotes
Thanks for shedding some light onto this. Every owner of a new and expensive iMac Pro is a bit disappointed when it comes to Adobe CC products and their lack of multi-core CPU support. And now we're finding out that our expensive hardware also doesn't support H.264 hardware-based encoding in Adobe Media Encoder. This is just another piece of news none of us likes to hear.
... View more
Apr 04, 2018
10:27 AM
It answers my question, Rameez. It does not help me understand why "Intel® Xeon® Processor E3 family, introduced in 2011, supported H.264 hardware-based encoding for the first time." Supposedly Xeon processors have had H.264 hardware encoding support since 2011...
... View more
Apr 03, 2018
09:01 PM
But Adobe's "what's new" page specifically mentions Macs running 10.13 with "supported hardware". Which hardware is supposed to support that feature, remains a mystery.
... View more
Apr 03, 2018
06:40 PM
I am curious - does anyone know which Macs have hardware acceleration for H.264 encoding in the just released updated version of Media Encoder. My screenshot is from my 8-core iMac Pro, which for some curious reason does not qualify...
... View more
Apr 03, 2018
09:56 AM
1 Upvote
Adobe is about to release all new CC updates today for this year's NAB show in Vegas. Maybe we'll see some improvements in performance. I am waiting for the updates to become available and to try them on my iMac Pro (8-core, 64GB, 16GB). Adobe is featuring MACS-only in all of their PR videos demonstrating new features and workflows. You'd think they'd make sure their apps perform really well on these stylish machines. Is anyone attending NAB this year? Would be a great opportunity to talk to Adobe and ask them what's going on with their lack of support for the multicore iMac Pro and - let's not forget - the upcoming totally redesigned Mac Pro, which will also feature powerful multi-core CPUs.
... View more
Jun 09, 2017
01:31 PM
Thank you, I’ll give this a shot. Markus
... View more
Jun 09, 2017
01:24 PM
I’ll try that when I have a second. It’s worth a shot. I am a recent Premiere Pro convert - so my question is - does Premiere play nicely with clips being replaced? In other words, what’s the best workflow for transcoding material without losing any of my work?
... View more
Jun 09, 2017
01:15 PM
So here's the latest development: I just tested bars and tone in a sequence and output that as a ProRes quicktime. No color or gamma shift. So it has to do with the material I am using. I know that material was exported from a Final Cut Pro 7 system as a ProRes file and given to me. Maybe that's where the problem lies...
... View more
Jun 09, 2017
12:55 PM
2 Upvotes
Hi Neil, I really appreciate your most recent comments. And I thank you in advance for trying to help me with this. If the iMac’s GPU is the problem, that would be impossible to solve (other than getting a different machine). I do know that a lot of my colleagues in various companies around town use iMacs as their “professional editing systems” - especially with Premiere Pro. Here’s what I did experiment with: I switched my project to all 3 rendering engines that are available to me - OpenGL, Metal and Software only - and I exported a master quicktime with each engine. It was the same gamma shift result outside of Premiere. Wouldn’t “Software Only” take the iMac’s GPU out of the equation? I am aware of the Quicktime Player as being not up to professional standards. But I am seeing the exact same behavior with TIFF exports. Now that has nothing to do with Quicktime. Something in the Premiere Export/Render engine that doesn’t play nicely with my setup. - I do not have any of these problems with After Effects exports - also as ProRes Quicktime Movies. Markus
... View more
Jun 09, 2017
12:04 PM
25 Upvotes
Neil, I am using a 5K Retina iMac for my very high-end professional editing work, as do many of my other highly priced colleagues in town (Los Angeles). My work shows up on the big screen as well as on all networks and the internet. So naturally, my iMac's display is fully and professionally color calibrated and it's anything but an "amateur" system. As Apple said this week - "professionals love our iMacs:... What I and many others are experiencing has nothing to do with calibration. If the same thing looks drastically different inside Premiere and outside of it - I could be viewing this on a 100 dollar cheap monitor and it's still the same problem we're dealing with. So please don't lecture me about professional standards. That's not helpful at all. And you dismissing Quicktime as not professional is also very ill informed. I have been working with all the top post and finishing houses here in L.A. for 18 years, and all we've been ever used to transfer high-end footage is PreRes Quicktime Movies. Markus
... View more
Jun 09, 2017
08:26 AM
5 Upvotes
I know this is a topic of major frustration for many of us - washed out colors and a very visible gamma shift when exporting out of Premiere Pro. From what I have seen on this forum, people post all kinds of solutions / explanations as to what could cause this problem. Many people think it' a Quicktime problem, some say it has to do with video card drives, or with checking "render as linear color space" or not. I just did a round of major testing on my iMac running OS 10.12.5 and the latest version of Premiere Pro CC 2017 - and I have to say - nothing I do fixes it or makes any difference. Whatever I export - and that's the key here - Quicktime movies, TIFF sequences, stills - EVERYTHING has a washed-out gamma shift and desaturated colors. When I take a screenshot of my media within Premiere Pro - colors and gamma of the resulting PNG are exactly as I see them in Premiere. If go through the EXPORT function and export a still image - the colors are faded and the gamma is washed out. And it doesn't matter what is clicked in the export window - maximum depth, linear color space... nothing makes a difference. Here is another interesting thing I found - when I reimport these washed-out exports (stills or quicktime movies, doesn't matter), inside the Premiere Pro world they look perfectly normal. When I import the same washed-out exports into Final Cut Pro X, the washed out colors and gamma stay. So there must be something in these exports (hidden tags?) that Premiere adds and that it then uses to display the media correctly. Unfortunately every other app in my Mac universe doesn't do the same and is off dramatically. The problem is - I can't just stay inside Premiere Pro. I have to send tmy cuts out and share them with clients. I need them to see what I see inside Premiere Pro. Does anyone on the Adobe side have any insight into this? This issue has been going on for years on this forum. I cannot believe that we are still nowhere close to a solution. Thanks in advance for any hint. Markus
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices