Highlighted

Premiere CC 2018 Playback Delay after pressing the Play button

Community Beginner ,
Oct 25, 2017

Copy link to clipboard

Copied

In previous version of Premiere when i Press Space it starts immediately playng.

In CC 2018 it starts after nearly 1 second with MERCURY ON and immediately if disabled.

Z620 32GB K4000 

CPU: DUAL 2640

iNSTALLED VARIOUS VERSION OF GRAPHIC CARD DRIVERS.

INSTALLED ON A FRESH INSTALLED WINDOWS AND AGAIN THE SAME THING.

IT DOES THIS WITH ANY FILE FORMAT OR SEQUENCE TEMPLATE.

PLEASE!

Message was edited by: Moderator

This issue is now fixed on my system with the 12.0.1 update to Premiere. Thanks Trent Happel​ and team!

Views

28.1K

Likes

Translate

Translate

Report

Report
This conversation has been locked.

Premiere CC 2018 Playback Delay after pressing the Play button

Community Beginner ,
Oct 25, 2017

Copy link to clipboard

Copied

In previous version of Premiere when i Press Space it starts immediately playng.

In CC 2018 it starts after nearly 1 second with MERCURY ON and immediately if disabled.

Z620 32GB K4000 

CPU: DUAL 2640

iNSTALLED VARIOUS VERSION OF GRAPHIC CARD DRIVERS.

INSTALLED ON A FRESH INSTALLED WINDOWS AND AGAIN THE SAME THING.

IT DOES THIS WITH ANY FILE FORMAT OR SEQUENCE TEMPLATE.

PLEASE!

Message was edited by: Moderator

This issue is now fixed on my system with the 12.0.1 update to Premiere. Thanks Trent Happel​ and team!

Views

28.1K

Likes

Translate

Translate

Report

Report
Oct 25, 2017 0
118 Replies 118
Adobe Employee ,
Oct 25, 2017

Copy link to clipboard

Copied

This issue is being investigated. Thank you.

Likes

Translate

Translate

Report

Report
Oct 25, 2017 2
New Here ,
Oct 28, 2017

Copy link to clipboard

Copied

I am having difficulty playing the video (HD 1080p) ever since I upgraded from CC 2017 to CC 2018. Need a quick solution.

I have a iMac 27" 2013, 3.5 Intel Core i7, Memory 32GB,

NVIDIA GeForce GTX 780M 4096 MB

Likes

Translate

Translate

Report

Report
Oct 28, 2017 1
New Here ,
Dec 11, 2017

Copy link to clipboard

Copied

Is this serious? Can Adobe try their updates with a professional video editor before launch it? This delay when pressing Space is inadmissible. Still not working.

Likes

Translate

Translate

Report

Report
Dec 11, 2017 1
Community Beginner ,
Dec 22, 2017

Copy link to clipboard

Copied

Did you find the solution to this problem?

I have the same issue, but only in one project. Other projects work fine (all projects are shot with the same equipment and settings), but one project has this playhead delay for 1-2 seconds. None of the rendering (in and out; audio) doesn't help. It is impossible to edit like this... Need help.

Likes

Translate

Translate

Report

Report
Dec 22, 2017 0
Community Beginner ,
Dec 22, 2017

Copy link to clipboard

Copied

No!

Adobe is not saying anything about this!

Didn't find a solution!

Likes

Translate

Translate

Report

Report
Dec 22, 2017 0
Adobe Employee ,
Jan 02, 2018

Copy link to clipboard

Copied

Hi ElvisB,

No!

Adobe is not saying anything about this!

Didn't find a solution!

Did you contact our agents yet? File a case with us. Here's how: FAQ: How do I contact Adobe Support? Please work with them in solving your case.

That said, your issue may be "project specific" and not a bug. Project issues like this can be described as "corrupt project files." If you have updated a project across a major new version of Premiere Pro, it is subject to such corruption.

Personally, rather than updating a project file, I import existing project files to brand new projects when carrying a project forward. That seems to produce much less of this unexpected behavior than updating the file.

Thanks,
Kevin

Likes

Translate

Translate

Report

Report
Jan 02, 2018 0
Community Beginner ,
Jan 04, 2018

Copy link to clipboard

Copied

-Brand New Project

-Various Projects

-Various timelines

-Various video and stills too

-Same timeline as video

As i can say they are various graphic cards that have this problem. I asked around and freelancers with K4000 are having the same problem.

As i sad in the beginning i tried more than 5 different drivers for my k4000.

And a fresh installed Windows

Tried the new k4000 in another pc and the same happend.

2017 and above versions of Premiere worked super.

Likes

Translate

Translate

Report

Report
Jan 04, 2018 1
New Here ,
Mar 15, 2018

Copy link to clipboard

Copied

My system was working fine on monday then on tuesday Microsoft released a Spectre/Meltdown patch which I'm sure has to do with this since it is known that the patch slows system performance. I didn't see my chip on the list of affected chips but I may be missing something (i5-6600).

https://support.microsoft.com/en-us/help/4090007/intel-microcode-updates

Now I'm having this issue everyone else is having in 12.0.1. I have a project file where clicking play on the playback window or pressing space bar on the timeline does nothing. Clicking around the timeline is very slow. Starting a new project and adding video works fine. What info can I submit to Adobe to help narrow down this bug?


Windows 10 64-bit

i5-6600

GTX 960 391.01 - WHQL released Mon Feb 26, 2018

32GB RAM

Samsung 960 Pro 256GB OS latest firmware

Samsung 950 Evo 500GB Media Cache latest firmware

Source media on external seagate 4TB 7200rpm drive

Likes

Translate

Translate

Report

Report
Mar 15, 2018 0
New Here ,
Jun 11, 2018

Copy link to clipboard

Copied

Im having a lot of lags during playback... Already tried everything mentioned before... Win 10 / GPU 1080p ti 11gb / CPU Ryzen 1950x / 32 gb Ram... Rushs are : 1080 p - H264 / 25 fps

Any idea how to solve this? It's almost impossible to work properly with so many lags during playback...

Thanks in advance.

Likes

Translate

Translate

Report

Report
Jun 11, 2018 0
Community Beginner ,
Sep 11, 2018

Copy link to clipboard

Copied

I can confirm this issue is not fixed in v12.1 Kentos. Here is a link to my Tweet I just made containing a video showing the problem. I also realized after shooting the video if I unlink the video tracks from the audio tracks and delete all the audio tracks playback is instant and scrubbing is instant with no issues. It looks like the problem has to do with the audio device initializing on playback, something is hanging it up for a few seconds but once it start playing it's fine. I have a Yamaha MG10XU Audio Interface. I tried MME and ASIO with the same level of lag and even tried switching to the RealTek internal audio stack on my motherboard and the same thing happens.

Can I attach a debugger and reproduce this for you with a break point or telemetry of some kind so you can figure out which API is hanging the stack? It's also causing lots of not responding issues when playing back and stopping rapidly like double tapping the space bar and sometimes it locks completely and won't return and I have to kill and restart.

Tweet with Video

https://twitter.com/Barnacules/status/1039759419955920896

Likes

Translate

Translate

Report

Report
Sep 11, 2018 0
Explorer ,
Sep 12, 2018

Copy link to clipboard

Copied

Having similar issues, wish they'd figure something out. Thought it was Intel turbo boost or the RAM being set to XMP but that only worked for two mins after disabling it. I have a sneaking suspicion it has to do with the audio interface. I've used both an M Box and Saffire (firewire 400) rack unit. There is a delay in selecting menus, playhead stutters across the timeline, slow response on scrubbing and it gets slower as time goes on in the project.

I'm not overclocking, and XMP is disabled as well.

Specs:

Asus X299 Deluxe

Intel - Core i9-7940X 3.1GHz 14-Core Processor

CORSAIR VENGEANCE LED 64GB (4x16GB) DDR4 3200MHz

EVGA GeForce GTX 1080 Ti SC Black Edition

Samsung 970 EVO 500GB - NVMe PCIe M.2 2280 SSD (OS)

Crucial MX300 2TB 3D NAND SATA 2.5 Inch Internal SSD (Cache)

Windows 10 Pro

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

jerryb20706886, can you take a screenshot of your Preferences - Audio Hardware screen?

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

Screen Shot 2018-09-12 at 11.08.55 AM.png

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

Robert Mead​ can you also screenshot your Preferences - Playback screen?

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

Screen Shot 2018-09-12 at 11.21.30 AM.png

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

Per AJA, your Audio Hardware preferences and Playback Audio Device should never be both set to AJA. I recommend the following settings which work for all 15 of my editors:

FYI Maximum Buffer Mode on AJA will give you the worst scrubbing performance. Minimum or Standard is recommended.

1.png

2.png

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

I don't have scrubbing issues with the maximum setting but I've set it to standard for good measure.  We'll see how it plays.  I need to have the AJA audio output because I'm cutting in 5.1.  The is my first major feature film in Premiere but I've had extensive use with AJA in 5.1 cutting in 2K with Avid no problem.  If I wasn't coming into this gig as a fixit editor I would be in Avid or DaVinci no question.  Premiere might be fine for commercials, music videos or short format programs but I'm continuously proven right that Adobe Premiere is not ready for primetime on the big stage of long form feature films.   Bummer.

And FYI: As a test just now I switched over to the Audio Preferences you suggested and I still have the performance issue with the start stop delay I was having with the AJA Device selected.  The only way I can correct the problem is by switching off Mercury Transit.  Then everything becomes lighting fast.  I can only deduct that Premiere can't handle outboard gear very well.

I appreciate you taking the time to try and troubleshoot this with me.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

Robert, does this delay occur if you start a brand new project, add bars and tone, add it to a sequence, and attempt to play it back?

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

Hi Jeff,

Yes it does.  I just now created a new project followed by creating bars and tone.  Then created a new sequence from the clip and the stop delay still occurs.  The play response time seems pretty good.  I'm not seeing the delay much honestly (but that is the same for both projects) but I'm getting about a 6 frame delay from when I push stop to when the playhead actually stops.  I'm sure you can imagine how difficult that makes surgical fine tune editing.  Especially when editing dialog.

Considering how messy the project I'm working in seems to me... the performance is actually not horrible.  The main issue is that I'm having is that stop delay.  I don't know enough about Premiere projects to understand all how the program is optimizing all it's reference material.  I have about 12TB of 2k proxy media and close to 100 hrs of footage.   And no, It's not a documentary... what a joke. 

Again, thanks for the attention.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

If you are experiencing this with bars and tone, then your issue does not lie with your media.

What about if you take your bars and tone and remove the audio track. Does the bars track only play back without delay?

I think you said if you turn off Mercury transmit the issue goes away. What if you detach your AJA device but leave Mercury transmit on, does the delay still occur? With and without audio on the timeline?

I'm just trying to get to the root of the issue here, I've heard of these issues before but I've been unable to duplicate this issue on any of my test machines nor on my editor's machines.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

Yes, I should've posted that here before:

If you leave the AJA IO 4K attached to the system and play the bars and tone with OR without audio in the timeline the delay remains.

No performance change.

If you detach the AJA box from the system and play the timeline with OR without audio in the timeline the and "LEAVE ON" mercury transit the problem will correct itself and the Start/Stop performance will be lightning fast just as it should be.

Thank you Jeff because doing this exercise I NOW HAVE CONFIRMED this issue (for me at least is a direct link to the AJA box itself.

I have 3 devices in a Thunderbolt daisy chain attached to the system.  The AJA IO 4K and 2 8TB Thunderbolt Drives.  The AJA box being the closest to the machines in the chain.

The only element I couldn't take out of the equation on the Mac AND PC side was that the interface to both machines is Thunderbolt 3.  The AJA box and drives are all Thunderbolt 2 running through the Apple Thunderbolt 2 -> Thunderbolt 3 adapter.  I momentarily thought the adapter could have been the issue but IT IS NOT.

Attaching the Thunderbolt 2 drives through the adapter without the presence of the AJA box fixed the start/stop delay problem.  (Running the project file locally with the drives worked perfectly) Unfortunately this still isn't a solution for working with a director and cutting in 5.1.  But at least it's been narrowed down.  I don't know if it is on the Adobe side or the AJA side but these two devices are not gel'n together

Running the latest version of AJA software and Premiere.  This should be addressed.

I might try rolling back the AJA software at some point to see if that remedies the problem.  The just recently had a major update so who knows.

My apologies for the long rant about this but hopefully this will help someone that might be in the same configuration.

System this was testing on as follows:

AJA IO 4K

AJA control panel 14.2.1.5

Macbook Pro 2016 15"

2.9 i7

16gig RAM

PC:

i7 - 8 Core

32gig RAM

1080 TI AMP Graphics

ThunderboltEX 3 PCI Card

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

If you remove the Thunderbolt drives from the daisy chain does the start/stop delay occur? Just your Mac/PC with the AJA device attached?

Are you running the latest firmware on your IO4k? (Firmware, not software). This can be checked in the AJA ControlPanel under the Firmware tab.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

CORRECTION

Ohh-kay:

Well I was correct before by saying the AJA box is indeed part of the problem but I believe the problem truly lives in Adobe Premiere. 

I have rolled back my AJA software and flashed the proper (current per version) firmware for each software version and the Start/stop delay still remains.  Even when taking other Thunderbolt devices out of the chain and using the AJA project solo with a local project testing just Bars and Tone - with and without audio.  The delay still remains.

Testing both rolled back software and firmware for AJA on Avid and FCPX work flawlessly with the transport controls. 

Jeff, I've got nothing left.  This must be a communication hiccup in Premiere, no?

This is indeed a pesky little bug that AJA or Adobe should look into.   I need to go back to work... with my delay.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

I know this is a long shot but do you have any spare Thunderbolt cables? Could be worth a test to try the AJA device with a different cable.

Also, does the same issue manifest on both your Mac and PC environments?

One last thing to try would be to install Premiere CC2017 and see if the same issue occurs there. I found the latest version of CC2017 was extremely reliable and worked almost 100% as expected. I'd be curious to know if this AJA delay issue is prevalent in the 2017 version of Premiere. This would at least narrow down the troubleshooting if it works fine in 2017.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Contributor ,
Sep 12, 2018

Copy link to clipboard

Copied

hell, sometimes I cannot resist answering.

If someone is an ACP , i expect him/her to be honestly answering based on known facts.

I for myself am struggeling with exactly the same issues , nearly everyone has since the release of 12.x.

I got in very close contact to officials who told me stories ...... I better not commenting any of these.

I've spent the last 5 days totally investigating everything possible with these issues, based on one of our planned tech specs.

here they are:

HP Z4 G4

Intel XEON 6 core

NVidia P4000

32gb Ram

AJA Io 4K plus / BlackMagic - different boxes (all TB3)

Intellimix 2

some other person her on the forum was trying for month now to convice everyone, that all of these issues are bound to hardware weakness.

Look at my specs.

And .. it is exactly as everyone here descibes it.

WITH OR WITHOUT the I/O-box , playbutton---hughe delay, then stuttering playback.

repositioning the cursor in the sequence and immendiately pressing PLAY.....annoying delay and totally stuttering !

It is absolutely obvious that the calculation and filling of the playback cache ist faulty since they invited the additional "hardware support". Since then the mercury cuda or metal or... does not work anymore.

One result is correct: The problem lies in accessing different devices for audio and video...in my case for "voice over" video over AJA , and audio over Intellimix.

It is one of the oldest problems, editingsystems had, since the very first beginning 26 years ago....synchronsation of 2 different devicedrivers (especially under windows / OSX is not so affected by that).

I tried everything - 5 long days - then tried to go back to 12.0.1 .

In this particular case it does not help solving my problems .

Then went back to the CC17 version from Nov2017 .... and ....same machine ....no changes ....same drivers .....

buttery smooth playback ... everything works fine ... voive over is working.... some minor problems with the HEVC codec (maxbe I can solve them tomorrow.

besides many more 12.x related problems I can give everyone a proven advice:

working as a TV/broadcast professional with necessary HD-SDI In/Out , and going on air by playing out through HD-SDI...defenitely stick to the latest 11.x version of premiere pro . That one works with I/O boxes from AJA as well as with Blackmagic (DNxIO).

If you are working for customers where the delivery is filebased , and your monitoring is made by hdmi/displayport - computermonitors , and your voiceover-workflow consists on USB-devices like a shure-mic or a usb audiomixer like the intellimix, then you can install up to the 12.0.1 version.

If you are only playing for socialmedia videos and stutters are no showstopper for you, as well as the lost ability to use some of the actual cameracodecs, then you are the most welcome customer for adobe ... a so called "early adopter".

So please don't tell us again that it might be the reason of some dedicated hardware or driver ..... prove it...or go back to the above mentioned versions and prove it yourself.

If someone of you is attending the IBC .... go to adobe ...try to get honest answers..... what ever happened ...we are only interested in one answer..

"when will you be able and willing to provide us with an again full working version !? "  .. I for myself lost the confidence that they are willing to change their current strategy  ... and therefore ..I changed the system successfully.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

megacinn  wrote

If someone is an ACP , i expect him/her to be honestly answering based on known facts.

What is your definition of a "known fact?" I don't know what about my answers you don't consider "honest" but just FYI the forum ACPs do not work for Adobe. We are simply users of the software who want to help other people on the internet. I don't have any special insider knowledge other than through my personal experience with their software. Troubleshooting these types of issues, there is no one-size-fits-all response. This playback play/pause issue you are experiencing? I don't have it. Neither do any of the 15+ editors I work with. It's hard for me to help troubleshoot when I can't duplicate your issue but I can at least suggest things that have worked in the past.

As for your issue, I would ask the same thing I asked Robert:

If you create a new project, add bars and tone to a new sequence, do you experience the delay?

What about with your external devices (AJA) disconnected?

What about with Mercury Transmit disabled?

If, for example, the delay is gone with the AJA disconnected but you DO when you have it connected, I think we can safely surmise that there is either an issue with the AJA device or with the protocol that connects to the AJA device. Being able to narrow down the possibilities helps with troubleshooting and if you go through the official Adobe tech support, this information would be extremely valuable.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

Jeff,

I don't know the ins and outs of the code or anything... but I just rolled back to CC2017 (the latest last version) and then rolled back my 200mb+ project file so I could open and re-save in CC2017.  Low and behold... everything is fixed. 

Exact same configuration as before.  Nothing has changed in the lineup.  Drives and AJA (using the latest control panel and firmware) not running like lighting in Premiere 11.1.2

I'm not a software engineer but I think anyone struggling with hardware issue might be better off rolling back as I just did.  The last 20 mins of editing has been a breath of fresh air and what I expect from a professional NLE.

I cut theatrical features for a living and this is my first real experience on the pro stage with Adobe Premiere.  The last several week transitioning my team along with the studio techs have been tough. Now with this simple rollback it seems at least what started this whole trial and error has been resolved.  I didn't realize you could roll back a project file so easily.

In the end we never truly fixed it, we just went to a earlier version.

The start/stop is now on par with Avid and DaVinci in CC2017 11.1.2.

Many thanks to you Jeff for pushing me for more answers I would've typically blown off in favor of continuing to work, even though I was struggling in my technique and was miserable.

The nice thing is if Adobe releases a update I just try it out without losing time, if it's not fixed I'll just keep going in CC2017.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 1
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

Glad that's working for you Robert. For what it's worth, the 15+ editors I work with are still working on CC2017. I upgrade my personal machine with every Adobe update for testing purposes and I have not yet given the green light to update our editors to 2018. I am not a fan of early adoption, nor do I like Adobe's pressure to update as soon as they release a new version. Too many things get broken and stay unfixed. CC2017 works great and CC2018 holds no essential features. I would not be surprised if my team stays on CC2017 for the next few years. It certainly looks like that's going to be the case.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Explorer ,
Sep 12, 2018

Copy link to clipboard

Copied

how do you rollback a project file?

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

Mac or PC?

Two different methods.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

I've actually tried every single possible combination of settings in the audio hardware screen including ASIO and MME. So a screen shot won't do any good since they all show the same problem even when RealTek is selected or Yamaha.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Community Beginner ,
Sep 12, 2018

Copy link to clipboard

Copied

I would like to roll back but all my current projects are on the new stuff and won't convert backwards unfortunately.

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Adobe Community Professional ,
Sep 12, 2018

Copy link to clipboard

Copied

How do I 'downgrade' an Adobe Premiere Pro project file to open in older versions? - Video Productio...

Make sure you make a copy first, but the link above will take you to a page documenting how to mod your project so you can roll-back PP like you said you'd like to. Let us know how the older PP works for you...

Likes

Translate

Translate

Report

Report
Sep 12, 2018 0
Contributor ,
Sep 13, 2018

Copy link to clipboard

Copied

@ Jeff Bugbee

look at the next part of the thread ..directly right after mine.

What helped Robert Mead ?

rolling back to an older version...that is exactly what I tried to say.

Look at nearly every thread regarding issues since 12.1.x

Nearly every time there is a ping-pong with ...ah humm your hardware ...weak...have you tried to disable....and then after days of desperately fumbling ...the solution is .... it is not the hardware....roll back to version 12.0.1 or older .....without any changes to the system ...everything is fine again.

We all are watching this forum since a very long time, hoping to find help and solutions...many are new and under timepressure...so these of us , who have read so many articles and their results, should take this as learned awareness and give it to others.

The reason why I'm so upset about this is no personal thing against anyone.

It is the experiences I had the last month with adobe itself (in person).

I've got the feeling that those who should know better, trying to spread "comercial interpretations" of the totally faulty actual softwareversion wasting our money and time.

And answering precisely to your question:

yes , the behaviour is always ..regardless with connected or disconnected AJA-IO or BlackmagicIO.

Working without mercurytransmit makes premiere useless, because every external device will be cuttoff in that case ..therefore not tested.

my conclusion ... it is the changed playback-cache and the "hardwaresupport" in general (see other thread ... no GPU-hardware-Support).

if going back to an older version...and everything is fine again...what other could be the preception ?

I definitely will not offend you in any way , but I'm noticing some writers here , where I am not sure how "motivated" they are .

so, let's help others as good as we can ..especially if adobe is not doing a good job. 

(in my case it is 50% a very close decision to stay on the adobe path /away from avid or forget the premiere trouble--back to avid  , the other 50% have already moved to resolve).

Likes

Translate

Translate

Report

Report
Sep 13, 2018 0
Adobe Community Professional ,
Sep 13, 2018

Copy link to clipboard

Copied

megacinn  wrote

look at the next part of the thread ..directly right after mine.

What helped Robert Mead ?

rolling back to an older version...

Scroll up. That's exactly what I recommended him to do right before your post.

megacinn  wrote

Nearly every time there is a ping-pong with ...ah humm your hardware ...weak...have you tried to disable....and then after days of desperately fumbling ...the solution is .... it is not the hardware....roll back to version 12.0.1 or older .....without any changes to the system ...everything is fine again.

If you've read anything I've posted, I've already said my team is still using CC2017. But when a user comes here, using CC2018, I'm not going to simply tell them to use 2017, I'm going to at least make the attempt to get 2018 working for them. And yes, in order to troubleshoot, you have to go through multiple avenues to get to the root of the issue, disabling devices, changing settings, etc. That isn't a problem, that's standard troubleshooting procedure.

megacinn  wrote

yes , the behaviour is always ..regardless with connected or disconnected AJA-IO or BlackmagicIO.

Working without mercurytransmit makes premiere useless, because every external device will be cuttoff in that case ..therefore not tested.

This is simply false. Mercury Transmit does not cut off "every eternal device." It will simply not allow you to send video to an external monitor. Your source and program windows will work just fine and you can edit just fine. "Making premiere useless" is hyperbole at its absolute worst. If you don't want to find out what's causing the issue, by all means, stop testing.

megacinn  wrote

my conclusion ... it is the changed playback-cache and the "hardwaresupport" in general (see other thread ... no GPU-hardware-Support).

I have no idea what you are trying to say here.

megacinn  wrote

I definitely will not offend you in any way , but I'm noticing some writers here , where I am not sure how "motivated" they are .

Is this an implication that some posters are getting kickbacks for using this forum? Where are you getting this from? What evidence do you have that supports this theory? At this point I can't tell if you are trolling or actually believe this stuff.

megacinn  wrote

so, let's help others as good as we can ..especially if adobe is not doing a good job. 

(in my case it is 50% a very close decision to stay on the adobe path /away from avid or forget the premiere trouble--back to avid  , the other 50% have already moved to resolve).

Is that not what we're doing here? Trying to help? I'm certainly not posting here to argue with people about my intentions for posting here.

As for whether or not you you stay with Adobe, that's your choice. Bringing that up on a user to user forum is utterly useless as no one here is even remotely affected by your decisions. By all means, move to Avid or DaVinci. If that means you will post your disgruntled rants on their forums instead of this one I'm all for it.

Likes

Translate

Translate

Report

Report
Sep 13, 2018 0
Explorer ,
Oct 28, 2017

Copy link to clipboard

Copied

you can switch to Mercury play back engine software only from CUDA

it will be faster when you are working on the timeline

but get slower on colour grading

Likes

Translate

Translate

Report

Report
Oct 28, 2017 1
New Here ,
Oct 29, 2017

Copy link to clipboard

Copied

This feature was available in CC 2017, but don't see it in CC 2018 for the Mac. 

Likes

Translate

Translate

Report

Report
Oct 29, 2017 0
Explorer ,
Oct 29, 2017

Copy link to clipboard

Copied

I have the same problem, including stuttering on audio and/or video every 2-3 seconds. As much as I like the new version, I can not work in these conditions  and I also reinstalled  the old version until the issue is fixed. Even in Media Browser the same occurs.

When I switch to Mercury Software mode the delay problem is no more but the stuttering remains.

In cc2017 didn't encountered these issues.

My system is:

GPU GTX 470 1,2GB

CPU i7 6850k

RAM 48GB

PS: I just replaced my GPU with a GTX 970 4GB and the problems persists. Soon I will do a reinstall to the OS (Windows 10 Pro) maybe something is wrong in current installation (although I freshly installed the OS on the Fall Creators Update release day)

Likes

Translate

Translate

Report

Report
Oct 29, 2017 0
New Here ,
Oct 30, 2017

Copy link to clipboard

Copied

If I use Mercury Open CL the delay is constant (half sec) but if I change to Mercury Software Only then working with no delay. I think, the problem is the Premiere CC Open CL propulsion.

Sorry for my bad English..

Likes

Translate

Translate

Report

Report
Oct 30, 2017 0
New Here ,
Nov 05, 2017

Copy link to clipboard

Copied

Same issue occurring here. CC 2017 playback is instant when using spacebar or the play icon, but there is a 0.5 to 1 second delay when performing the same function using CC 2018. Nothing has changed in my PC specs and the Premiere preferences are identical.

Likes

Translate

Translate

Report

Report
Nov 05, 2017 0