Transitions glitches on export with GPU activated

First of all, I'm fairly new to PP as I just switched from the FCP suite in the recent wind of change.
In PP CS5.5.1 I experience glitches on some of my film dissolves when I export with the Mercury Playback Engine GPU activated.
The source footage is AVHCD 1080 in a 720p timeline as I need the reframing possibilties and I export to H.264 720p.
If I export the same sequence many times, the glitches does not happen systematically on the same transitions all the time. If I turn the GPU acceleration off, it seems to resolve the issue but if it is an accepted practice in the PP community or if I encounter a bug due to my setup.
Any of you guys experienced this or know if there is a fix for that? I searched the forums but could not find an answer apart from "turning MPE off should resolve the issue".
Here's my set up:
PP 5.5.1 on OSX 10.7
GTX460
i7 2600
16GB RAM

I do have a hacked GPU and it could be a factor but I don't think so since everything is performing flawlessly and enjoying the GPU Boost! I read on the forum that there's some incompatibility between GPU accelerated MPE and the new 32 bits linear color processing: http://forums.adobe.com/message/3939400#3939400 but it involves more cross-fades transparency to 0.
So I'm still wondering if anybody else is experiencing these type of glitches...?!

Similar Messages

Bridge CS4 color management only works with GPU active

When I turn hardware acceleration off (by selecting software rendering in Bridge advanced preferences) Bridge color management disappears and on my wide gamut display I get cartoon color thumbnails indicating that CM isn't working. With GPU rendering on and Bridge restarted, CM works as it should.
It seems that Photoshop requires hardware acceleration with the "color compensation" option checked under the Performance/Enable OpenGL Drawing/Advanced settings preference.
Is color management now only functional with OpenGL acceleration enabled? I can find no help documentation for the advanced OpenGL Drawing settings. What a huge can of hardware worms this is turning out to be.

I wouldn't think that Bridge needed the GPU for CM, yet bypassing the GPU turns off CM in this installation.
I'm still confused about what you indicate in the Photoshop CS4 thread on OpenGL.
Chris Cox, "A few questions about OpenGl acceleration" #14, 11 Nov 2008 7:31 pm
I interpret your comment as suggesting that disabling color compensation in the PS CS4 GPU debugging features should disable CM in Photoshop, but it doesn't, it just makes it unreliable in displaying images post profile conversion in my tests. I'm probably missing some nuance here.

FCP transition glitch

FCP transition glitch when exporting to Quicktime. When played in Quicktime the transition skips back a frame.
Dual 2.7 Ghz Power PC G5 Mac OS X (10.4.8)

did you cut a small section out of a single clip and then transition from one side back to the other? If so, your transition is grabbing onto handles from the previous side of the clip. Ifyou trim off some of the second clip it could solve the issue.

Motion Transition Glitch - DVDSP 3

I'm relatively new to DVDSP, but I've successfully used the Menu Transition feature on a number of occations. I find it much easier and much faster than building my own transitions, especially when dealing with large numbers of menus. This is the first time that I've run into trouble.
I recently authored a project with 7 menus. 6 of the menus were "motion" menus comprised of a .pct bacground file and a .pct overlay file with an .AC3 audio track. These 6 menus were set to loop after the audio track finished playing. The 7th menu was a true motion menu with an .m2v background and a .pct overlay and again with an .AC3 audio track. This menu was set to pause on a still at the end of it's run.
I built and formated the project without incident and it played back correctly on all test systems (MAC, PC, Set-top). After reviewing the check disk the client requested that menu trasitions be added. I added the transitions and built and formated the project (after checking the disk in the simulator) reusing the original build folder. Upon review of the disk, I was shocked and confused when I discovered that rather than the motion dissolve transition that I expected to see inbetween menus, I was instead seeing seemingly random sections of my 7th motion video menu. I attempted to delete the build folder and and rebuild the disk from scratch, but to no avail. Same problem.
I was successful in solving the problem by doing three things (I'm not sure which was responsible for fixing the glitch) by saving the project under a different name (and building it in a different build folder), by removing and reapplying all of the transitions, and by removing and replacing (with the same files) the .m2v and .AC3 files from my motion menu.
Now that I've solved my own problem (during the course of writing this post), I guess that my question has become: Has anyone else encountered this particular glitch and is there a way for me to avoid it in the future?

I've tried to follow the steps in the Building an Alpha Transition, but it says that you need 2-3 different files, but no mention on exactly how to make those.
I exported from motion and have a file named Trans1-Animation NTSC Alpha.mov but I think I still need to create other files. All the tutorials that I can find show how to do this in After Effects but none explain how to create the need files from motion.
Is there a tutorial that explains the process in motion?
Powermac G5, Final Cut Studio Mac OS X (10.4.6)

Crossfades glitch on export

Hi, I was wondering if anyone has had any joy with the following problem I can't seem to get my head around.
After exporting high definition footage with Quicktime Compression some of the cross-fades have glitches.
The only way to describe this is the fade starts ok, then halfway through stutters and restarts. This does not occur in DV and seems to be a random occurrence. I have tried re-rendering, moving in and out points and it keeps happening.
When exporting with other formats such as mpeg the glitches do not occur.

If this problem is occuring when viewing your movie after export from FCP (but the transition looks ok when viewed within FCP), try the following...
In Quicktime Player, Preferences, General make sure that "Enable Final Cut Studio color compatibility" is checked.
Frank

Error message ''Disk Full' when trying to export with CS6, works fine in 5.5

I get an error message when I try to export media in Premiere CS6 that I don't have in CS5.5
I use export media for a AVCHD 60fps sequence with a few photoshop images on top of the main track. In the export settings I choose ''match sequence settings'' which gives me a .mpeg I- frame, 1920 x 1080 P, 60fps, quality 50, and a I tick the ''use maximum render quality'' check box at the bottom.
It used to work fine but now I get a message: Disk Full where there is 1.5 TB free on the disk?
I have the exact same sequence made in Premiere Pro CS 5.5 and it exports fine.
It started to act weird after I used the queue for the first time and it went to the CS6 encoder.
Since I used that once and it gave me that message for the first time, even when I try to do the same thing directly in Premiere CS6 , I always get the same error message.
Question 2, is there a place to change the settings from 50 to 100 for the quality of this export profile?
By the way I can export with other profiles without problems but this setting is the only one that I've seen that lets me keep my 60 frames per second in the export
process. (Example: I can export this sequence in the H.264, 1920 x 1080, 30fps, high quality preset, using the maximum render quality in CS6)

Hi Guys,
Thanks for the input but if you read my message correctly and until the end I already can export to other settings and I want an answer to this problem. There's no logical explanation to why this suddenly wouldn't work with the same sequence that it used to do fine with and that CS 5.5 handles fine.
As I said earlier this is the only setting that lets me export my sequence with the 60 fps, that I know of, for further and easier manipulation. As my main camera provides me with these 60 fps I'd really like to be able to have them left in that transition phase and, no, I'm not gonna give up until I know, really, what's going on and solve that problem. If this is a bug it needs to be fixed, if not I want to know what's happening.
Also there's no answer to my question 2: Question 2, is there a place to change the settings from 50 to 100 for the quality of this export profile?
So for you experts out there the question is still hanging.

Videos export with purple/green artifacts/splotches/flashes with Media Encoder CC but export fine with Premiere Pro CC?

I use Premiere Pro CC to edit videos, and videos render fine when I export through Premiere Pro, but when I try to use Media Encoder CC, the video exports with weird splotches of green/purple artifacts all throughout. It almost looks like the video is glitching and having a seizure of green and purple. No idea why this happens. Could anybody help me? I use Media Encoder to export bulks of videos at a time through its queue feature, which is why I prefer to use Media Encoder for video exporting.
Please and thanks.
Specs:
Motherboard: MSI® Z87-G45 Gaming [Red on Black color] 2x SLI/CrossFire
Processor: Intel® Core™ i7 4770K 3.5GHz/3.9GHz Turbo 8MB L3 Cache HD 4600
Memory: 16GB Corsair® Vengeance™ DDR3-1600 1.5V (2x8GB)
Graphics and GPGPU Accelerator: AMD R9 295x2
Power Supply: 1300W EVGA
Operating System: Microsoft Windows 7 Home Premium 64-bit

Mitch,
I was hoping that you and others might have some insight as to whether the purple and green artifacts / splotches seen in the attached screenshots (taken from 4 consecutive frames here but occurring through the entirety of the clip) could possibly have resulted from exporting video with ~ Premiere Pro CS5 or 6 ? As seen below, these splotches alternate back and forth between purple and green in every consecutive frame. I was also hoping that someone might know if this is a relatively common type of artifact and how it is caused.

Having major issues with Adobe Media Encoder (AME) - exporting with weird image flickering/colour anomalies, crashing regularly, freezing during encode...!

Hi Guys
I am having some real issues with Adobe Media Encoder (AME) at the moment. It appears that I am unable to encode an h.264 for Vimeo from a Premiere Pro Project file at the moment without at least some weird image issues that are not supposed to be there. These include weird flickering, colour changes, artefacts etc. This is if I am lucky...often I am unable to get the process to complete as the application either crashes and tells me there has been a problem or it simply freezes and I have to force quit the application and often restart my machine.
The problem seems to not to just be with h.264 for the web encodes but also with BluRay h.264 as well. As yet I haven't seen if there is a problem with MPEG-2 for DVD so I will check this out too!
Does anyone else see this happening or does anyone know what might be the problem?
I thought the Premiere Pro project might have been corrupt so tried a different project but the same issues were happening here too.
Any help would be really gratefully received.
Cheers
EDIT - I have just found this online which is exactly the problem I am having! Thanks a bloody bunch Apple! 10.9.3 causing headaches for Mac Pro users | MacIssues
Message was edited by: Alex Cameron

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

Transitions don't work with tracks

For some reason transitions don't work for me when I have them on tracks. For instance, Ive set a "dissolve" transition to occur at the end of Track 1 as it moves to Track 2. Instead, it simply jumps to the next track with no transition. Transitions seem to work with menus no problem, but once a track is involved, they stop. Im using DVDSP 4.
Anyone have any insight?

Hmm... you \can do this if you really need to... but you have to do a bit of jiggery pokery.
Take the last frame of your footage in the first track and open it in photoshop. Export it as a still image and take it back in to DVDSP, and add it to the very end of the video in the track. Adjust the length of it to be about 3 seconds and highlight it, and now add the transition you want.
The length is critical - the transition needs to take place using some of this image as the material. If you use a short transition you can use a short span for the image. If you don't, you need to extend the image. What this means is that your user will see the still for longer than necessary if you get this wrong.

Creating PS Network header with one activity

I need to create to a projekt the network header with one activity. so I want top proceed the following coding:
     CALL FUNCTION 'BAPI_PS_INITIALIZATION'.
      CALL FUNCTION 'BAPI_BUS2002_CREATE'
        EXPORTING
          i_network = gs_network
        TABLES
          et_return = et_return.
      CALL FUNCTION 'BAPI_PS_PRECOMMIT'
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        IMPORTING
          return = es_return.
        CALL FUNCTION 'BAPI_PS_INITIALIZATION'.
        CALL FUNCTION 'BAPI_BUS2002_ACT_CREATE_MULTI'
          EXPORTING
            i_number    = ls_number
          TABLES
            it_activity = gt_activity.
        CALL FUNCTION 'BAPI_PS_PRECOMMIT'
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          IMPORTING
            return = es_return.
But I get an Runtime Error with "MESSAGE_TYPE_X" because the PRECOMMIT was not successful.
Has anyone an idea how to handle that ??
thx a lot
Edited by: Rob Burbank on Nov 18, 2009 9:42 AM

DATA: lt_return   TYPE TABLE OF bapiret2,
        l_wa_return TYPE bapiret2.
CALL FUNCTION 'BAPI_PS_INITIALIZATION'
CALL FUNCTION 'BAPI_BUS2002_CREATE'
    EXPORTING
      i_network = pi_wa_aufnr
    TABLES
      et_return = lt_return.
READ TABLE lt_return WITH KEY type = 'S'
                       TRANSPORTING NO FIELDS.
IF sy-subrc = 0.
    REFRESH lt_return.
    CALL FUNCTION 'BAPI_PS_PRECOMMIT'
      TABLES
        et_return = lt_return.
    READ TABLE lt_return WITH KEY type = 'S'
                       TRANSPORTING NO FIELDS.
    IF sy-subrc = 0.
      READ TABLE lt_return INTO l_wa_return INDEX 3.
      pc_aufnr_new = l_wa_return-message_v2.
    ENDIF.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      IMPORTING
        return = l_wa_return.
ENDIF.
this is the sample code to create network & to get the network number created

Mac OS not recognizing DVD with Lightroom Active

Has anyone found that a DVD is not recognized by Mac OS when Lightroom is active? Once I load the DVD to export images, it's not in Finder or the desktop. I've checked my DVD preferences in Mac OS and tried "Ask me" or "Open another application (Lightroom)." The only workaround is to kill Lightroom, load the DVD, then reopen Lightroom. Does anyone have a fix for this?

>Does your computer see a blank DVD when inserted with LR active
Yes... Mac Pro w/ Leopard 10.5.2.
Are you running any Western Digital software for external drives? I had a problem with it a version or so ago, and had to uninstall it to make blank media behave properly. Haven't messed with it since and haven't had any problems.

Have functional difference with GPU acceleration and software processing of Mercury Playback Engine?

Used Decklink SDI and Premiere CS6 to testing.
I have a question~Have functional difference with GPU acceleration and software processing of Mercury Playback Engine?
(Can GPU acceleration export same used 59.94i external monitor export?).
IN specification，Is it need“software processing”？ whether other restrictions?
If Anyone know please tell me.
thank you.

Thank you for your help, and sorry about didn't make it clear.
Use Decklink SDI and Premiere CS6 to test.
In GPU mode of Mercury Engine, the signal form SDI is 1080i, but even fields will be missing.
Take a simple test:
Make quick slide for reproduce animationin in quadrangle(1080i 29.97), but it can't paly smooth and same gone to 30P.
If in Software mode, the action can be smooth.
Although use Software mode can be ok,but if GPU does not realize,it will take long time to render.
system info:
macpro 10.8.1
premiere cs6.0.2
blackmagic driver 9.6.4
GTX285
sequence of premiere
Presets/blackmagic/8bit YUV/interlace/59.94i
Have any problems with my System or the GPU mode can no external monitor output in 59.94?
IN specification，Is it need“software processing”？ whether other restrictions?
thank you!

CS4 When default transition will not insert with Ctrl-d

I've hit a snag today I hadn't seen before.
With two clips on the timeline, clip1 has the end trimed back 1 second, clip 2 has the beginning trimmed forward 1 second, so there is plenty of 'fat'.
Now with time head on the joint of those two clips, Ctrl-d will simply not insert a default transition.
In the past when this has happened its [b] ALWAYS [/b] been because 1 or the other side was not trimmed enough to accomodate the transition.
None of that is true this time. Default trans is set to 47 frames and I have 60 frames trimed (in all), and it is evenly trimmed.
What else might cause inserting the default trans to fail?
Oh, by the way the default audio transition inserts as expected with C-Shift-d.
I thought to check the short-cuts and make sure I hadn't set Ctrl-d to something else but since we do NOT have any way to quickly search with that dialog, I gave up after a few minutes... it would take 3 days of 12 hrs shifts to find it. But I'm nearly certain I haven't done that.

It sounds like you do have adequate Handles (that's the "fat"), and Jeff has probably nailed the issue - Track not Targeted, but another little glitch can be if the two Clips to not quite butt up to each other, i.e. a tiny gap between them. If, when you do Target that Track, you still cannot do Ctrl+D, check for a gap between the two Clips.
Good luck,
Hunt

PP 2014 CC - R3D files - Random Green frames with GPU GTX970

Hello
I am struggling with a problem when reading & exporting frames R3D files from a Red epic Dragon. Within the app, in a timeline, certain frames will randomly have a heavy green hue. Green frames will also show up in exported image sequences. PP is using CUDA on Windows 7 and I have a NVIDIA GTX970 with the latest CUDA & driver. I do not have this issue when exporting with the CPU.
It seems that the GTX970 is not validated yet so this could be a legitimate bug, so I am sharing this info for those looking to buy this card.

Problem fixed!
Someone from the Adobe support team instructed me to change the renderer to software only mode. This can be changed under File>Project Settings>General. More specifically, I changed it from Mercury Playback Engine GPU Acceleration (Open CL) to Mercury Playback Engine Software Only. I deleted the old render files and reexported without any further issues.
Success!

Help Needed : Video Glitch after exporting from Premiere Pro CC

Hi all ,
            I have been experiencing this issue for sometime now. I occasionally encounter a video glitch after exporting a video from Premiere Pro CS6 or CC. Sometimes it happens in my NLE timeline , which I have to remove the affected clip that has the glitch/flicker problem from my bin and re-import the clip from my original source, which solves the problem.
             However , the worst part is when the glitch/flicker happens when I have already exported the video when everything seems fine in the timeline of Premiere . My sequence settings do match with the clip . This issue happens intermittently as I always have to hope for the best when the video exports.
Here is an Example of what I mean, the glitch/flicker happens at 3:28 of the music video.
             Hopefully those who have the same issue can share how to troubleshoot this problem . Thank you.
Regards,
Elias Lo

what i did was install final cut pro. I dont have an answer for this but it finish my problem , how i came up with this idea well i have the new mac pro cilinder that looks like a trash can 64gb memory and all the toys to work fast but again the mov files cannot be seen in the desktop cause premiere and mac and windows and all this ******** they fight about , and i also have your problem big time o pn every export.
i have instal final cut onmy older slower imac and i can see everything and the export are perfect
so i just did that and its perfectly fine basicaly final cut does something that makes ur computer and adobe read all kinds of files frames format.   i try to explain this to this adobe premiere enginners but they just say uuuuhhhhh

Transitions glitches on export with GPU activated

Similar Messages

Maybe you are looking for