Flash frame in nested sequence won't go away

When I open up the sequence to play it, it's fine. When the sequence itself is played, It flashes over the first part of her sentence, then cuts in as she's saying a particular word.
I dont show that there's anything to be rendered. I've done everything i can think of, including exporting and hoping that would fix it, closing out fcp and reloading the project, etc.
Anyone ever run into this?

Are you saying that your nested sequence is starting at a later point than the inpoint of the first clip contained within it? A nested sequence can be trimmed just like a regular clip, so you may just need to drag its in-point to the left (or perform a slip-edit).
If this is not the problem, you could certainly have a phantom render file (this happens most often with nested sequences). You can usually kill it by forcing FCP to re-render that section of the timeline. There are a billion ways to do this–my favorite is selecting a clip (or range of clips) located on the section of your timeline where the phantom is hanging out, then hit Ctrl-B twice to toggle their visibility on and off. A fresh re-render of that timeline section should confirm that your phantom has finally been released to render file heaven.
Zap
Dual 2 GHz PowerPC G5 Mac OS X (10.3.6)

Similar Messages

Red flash frames on C300 sequence exports

Still no fix for this widely noted issue, Adobe?
I'm currently trying to get a job completed and the process of getting anything out of Premiere is absolutely painful...
I have tried all the suggested solutions - trashing preferences and media cache files. I saw somewhere that removing any clips that are a different codec to your footage (in this case it's MXF files from a C300) fixed the problem. Tried switching hardware GPU acceleration off. None of these things have worked. I've had to export the sequence several different times and then stitch these exports together in a new sequence (skipping out the numerous red flash frames, of course) just to get a clean export out. Pitiful.
I can see reports of this happening over a year ago - why hasn't it been fixed? I think it's pretty scandalous that this hasn't been sorted - Premiere is advertised as being able to handle these camera formats natively...well, it can't right now for me if using the native camera files results in issues like this.
Has anyone found any other work arounds that I haven't noted above?

Hi Mark,
According to the "about Premiere Pro" window, I am on 8.2.0 (65) build.
I have had the same issue exporting out of both Premiere and Adobe Media Encoder - the build of AME is 8.2.0.54.
Adam

How do I get a lip sync flash frame sequence to encode properly

I built a flash frame sequ
ence in Premiere. It is 2 seconds long with the
first two frame white and the remaining time black
frames. This is repeated for 1 minute. If I encode it in non-compressed AVI it is correct. If I use
MPEG2 or H.264 to build a transport stream, I see two white frames
as I would expect,then black frames for the rest of the sequence. Over 15 seconds, I will start to see three frames, gray, white and gray again. Eventually, the white or gray frame starts two frames later than it should. I built this as a 720P/60 sequence with non-drop frame timecode. I have tried all I frames and the same issue occurs. The GOP structure does not seem to have an effect. There is no audio in this stream. It as if it cannot handle the quick and short transistion from white to black. There are some advanced settings for MPEG 2 but I cannot see where they are explained in the Premier help document. I need this stream to measure latency on a piece of video equipment.
Thanks
Ralph

Bill,
Your answer gave me a hint to what was happening. I'm fairly new to Premier and took for granted that the preset I chose at the begining of the program would carry through to the sequence, wrong! I found another discussion that talked about resetting the properties of a sequence. I expanded the project box a little and saw that it said my sequence was 59.94 frame rate not 60. I followed the instructions on the other discussion. File, new sequence, general, editing mode, and frame rate. The frame rate was set to 59.94 not 60. I reset it to 60, closed all the menues and deleted the original 59.94 sequence. The new sequence I just created shows a 60 Hz frame rate. I exported my lip sync project as an MPEG 2 transport stream and it was correct according to our MPEG analyzer.
Thanks again for the help.
Ralph

Flash-Frames in Quicktime?

Greetings. I'm exporting a sequence from Final Cut Pro (The project was shot in HDV) to a standard-def Quicktime. I have noticed in the final QT that there are a couple of flashframes in the video. I double checked the sequence, and they are not there, just in the QT file.
Any advice?
Many thanks in advance.
G5 Mac OS X (10.4.8)

did you export using compressor or qt conversion? I would use compressor to do your conversion. look under the advanced formats to select your desired standard def setting. also what can happen is you may have a field that is a flash "frame" i.e. field 2 may be the culprit and you won't see that in your sequence due to the frame based nature of FCP. if you import the standard def conversion you did into a timeline with the appropriate settings and you don't see the flash frames it's due to the frame based situation, if you do see them it's a corrupted conversion. try compressor

Nesting Sequences strange behaviour

Hey guys,
....just recently discovered nesting sequences...D'Oh!
I find that if I nest sequences two or three layers deep sometimes get strange random frames from other seuences occuring in the sequence I'm viewing.
Could this be system performance related? I'm not exactly working with a powerhouse here. In fact I get the SPOD if I put the razor to this sequence.
new to nesting - love the concept

Sarah, to help the knowlegable users here please advise which model G5 iMac you have & include this info in your system info preference by clicking on the "My Settings" link in the right hand column.-->
This way, you won't have to keep repeating yourself and the knowlegable users will be able to provide you with the correct trouble shooting information/solutions if the problem is your computer.
Also, it will be helpful if you will advise which version of Word, Photoshop you have, which email program & the type of printer you are using.
Thank you.

Premiere CC 2014.2 crashes when rendering or (rendering effects) In and Out SEQUENCE for playback in a Nested Sequence

I have 4 internal HDD and an External. No matter where I assign Media Cache Files or Media Cache Database Premiere crashes within 100-300 frames in a Nested sequence. I am trying to move the caches around, deleting them, restarting a fresh nested sequence... nothing! I cannot get the short film done because of it. I have even formatted my hard drive and started fresh thinking that solves the problem, but it still remains. Anyone know what I can do?
Running Windows 7 64 on Bootcamp.
Quadro 4000
32GB Ram
dual xeon quad core

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

Flash Frames On Incoming Video

I have the strangest problem with flash frames I've ever seen. Whenever I make a cut at a scene change in my footage I get a flash frame on the incoming cut. I immediately assumed it was a field so I lopped off the first frame and... no luck. I actually have to tim off the first 3 to 4 frames! to rid the cut of the flash.
My sequence of events: I ripped supplied footage from DVD using Handbrake & de-interlacing into an progressive, Mpeg4 file. Then, using Compressor, rendered it into a progressive, ProRes 422 HQ Quicktime. However, the ProRes 422 HQ Quicktime had this bizarre brightness change when I hit play in FCP6. It was annoying so I used compressor again to transcode the ProRes 422 files into progressive H.264 Quicktimes. They seem to play & edit fine... except for this issue. Unfortunately, this issue is a showstopper. There's no way I can continue to edit with this media doing this.
I've searched the forum for similar posts but none of the problems ever seemed solved, and certainly none of the solutions suggested are working for me; I've trashed preferences, trashed rendered files & re-rendered them, etc. I have zoomed in to verify that there are no extraneous frames. Also, if I import the ProRes 422 Quicktimes and edit with them, they don't seem to have this flash frame issue.
Anybody else seen or heard of this issue? Why would an errant field exist across 3-4 frames? Anybody have any suggestions? Any and all help would be greatly appreciated.

Handbrake is the wrong tool for this...MPEG STREAMCLIP or DVDxDV Pro are the better options. I use DVDxDV...REALLY good with non-Hollywood movie type DVDs. Can extract to DV or Uncompressed...whatever you need. MPEG-4 like H.264 isn't meant to be used as an editing codec, it is designed for final delivery. That might be why you are getting the odd flash frames...the way it is compressed.
As for ProRes brightening...that means that your system needs to reduce the quality of the image in order to play it back without dropping frames...that is one symptom. Another is really low quality playback. To see what you really working with it is good to have a capture card and external monitor connected so you can tell what things really look like...as the computer monitors are playing back a low res proxie.
Shane

Time remapping / slow motion extremely jumpy with nested sequence!

I have just finished the rough-cut of a ceremony when I went back to add effects-- slow motion, color correct, etc. only to find that ANY time-change is jittery-- extremely jittery, like it's skipping frames.
For trial purposes I created a new timeline with only one video clip placed multiple times. I reduced one to 50% with frame-blending, the other 50% with NO frame-blending and the final using time re-mapping with frame-blending. At 50% I don't expect fluid movement, but they are all acceptable... Until I put a different timeline in the timeline (I think it's a "nested sequence").
When speed is slowed on ANY nested sequence it is jittery. Whether it is a single nested sequence or a multi-camera sequence, it jumps.
Has anyone else had this problem?! Is this a bug? I never noticed it until this wedding. I am using CS3 and I cannot afford the time to re-edit this ceremony with 2.0.... Unless I have no choice.

Hi Wil,
I have tried using both. Time remapping on the clip (not nested) works fine, so does 'speed change.' But both time remapping and speed change result in jumpy frames when applied to a nested sequenced clip.
I tried this on another (much lower system) and have found the same results. I am begining to think it is the footage but it seems odd that it is perfect when applied to a clip in the timeline but NOT to a timeline in the timeline (nested).
I am on vacation and do not have access to a faster machine until next late next week but for now I will try the export again to be sure Encore sees the same thing.
I am dumbfounded because I had been using 1.5, then 2.0 and now CS3 for weddings for years and have never noticed this. I have noticed it on the both the last project and now this current one.
I thought it could have been the original footage (or a camera problem except that the problems are not there until a nested sequence comes along. I will try moving the footage to my internal drive now and see what happens...
Thank you so far for giving me ideas.

Time remapping a nested sequence results in black/empty video

Hey!
I have a long sequence (47 minutes), which I wish to time remap (to increase the speed at certain Keyframes). I have therefore nested the sequence into a Master Sequence, where I perform the time remapping. However I experience what appears to be a weird bug: At a certain frame the video turns black/empty and stays that way - even though the original sequence still has video material.
It doesn't help splitting the clip (nested sequence) up in smaller clips and time remap those individually - the empty frames just appear earlier in each clip.
Export works fine
When I export the sequence as Media, the output seems fine however.
I hope, that you are able to help me or tell me, if I'm doing something wrong.
Thanks in advance!
Hardware info
I work on a MacBook Pro (Retina, 15-inch, Mid 2014).

it depends on how powerful the video card is, and how many accelerated effects are being used. it might slow you down a little, or alot. if you have an intel graphics, they arent very powerful to begin with, basically just good for browsing the web. however premiere tries to use them and they cause lots of problems. im not sure if its premiere or intel thats causing the problem, but they dont play nice together. if you have the nvidia version macbook, you might have opencl or cuda available in the renderer menu. if it was on opencl, could try cuda, or opencl if it was on cuda.

Finding your place in a nested sequence

Plop an ordinary clip in the timeline, move the playhead to a spot in the clip, double-click the clip in the timeline, and the clip pops up in the source monitor with the playhead at the same spot in the clip.
Place a nested sequence in a timeline, move the head to a spot in the nested sequence, double-click, and the original sequence opens up in the timeline window, but the playhead is not in the same place (it's where you left it the last time you were working on that sequence).
If I've got a nested sequence in a new timeline, is there any way to quickly assertain where the corresponding place on the original sequence is?
Thanks in advance!

Use the keyboard shortcut "M" to perform a Match Frame operation.
Nein!
Use Shift+T: Reveal Nested Sequence. It will open up the nest in a Timeline panel tab (if it isn't already) and park the playhead at the matching frame.

Framerate change to nested sequence of text clips?

Having successfully rendered a 25 frame project as a finished film with burned-in subtitles and other text. Now I wished to create a 29.97 NTSC version. I have attempted this by sending the complete rendered 25 frame film to Compressor and re-rendering as 29.97 ProRes 422HQ using Compressor and then re-rendering, again with Compressor, as mpeg2. I found that some of the previously successfully rendered text now appears (in the ProRes file) to be somewhat blurred and to be unstable and 'jittery' when over a light, moving background.
It occurred to me that the best solution might be to separate the background material, render this to 29.97 ProRes 422HQ without the titles and then to apply the sequence of title clips at the new framerate. Thus there is no framerate change to rendered text.
Having nested these text clips in my 25 fps project, if I paste these into my 29.97 project they come up out of sync (unsurprisingly). I have tried changing the speed of this nested sequence of text clips by 25/29.97 which (almost) worked in terms of fixing the timing but the image quality of the text seemed impaired.
Can anyone please suggest an alternative way of imposing a framerate change on an unrendered nested sequence of text clips? My aim here is clearly to avoid the need to adjust each clip's duration manually especially as some have 'motion' scrolling within them.
Thanks

It is entirely possible that you could find the font information and replace it.
Just keep in mind that the project files in CC are actually zipped.
Create a project with one clip and one title and then tear the project file apart to find the info you want to search on.
Then try it on a copy of your big project. It is tedious, but you might pull it off.

CS4.2 - Nested Sequence bug!...

I seem to have stumbled upon a bug in Premiere CS4.2 (it is probably present in all versions of CS4)
I am trying to build some professional looking transitions, but to accomplish them I am having to nest sequences (though it would be nicer if I could add effects to transitions themselves to avoid nesting [cough] Adobe[cough], or be able to use transparent video clips as adjustment layers)
Anyhow, 2 things: One, On my main timeline I have the Push Transition between two clips set to go from Top to Bottom (doesn't have an issue when going side to side)
Second, I have a photoshop file being used elsewhere on the timeline with a scale effect to use as a transition (going from 600% to 100% with no other motion).
(Both are having the same issue - below)
I have the Photoshop file and the Push transition on my main sequence which is then nested into another sequence so I could add a blur effect to the transitions, and then I have that sequence nested into a third sequence that is set to square pixels so I can output a quicktime to Youtube (the original 2 Sequences have a 1.21 widescreen aspect in case I want to go to dvd)
My issue is that on the Square Pixel Sequence both the Top/Bottom Push Trans and The Photoshop file seem to get pushed over revealing either a black edge or the track below it. (which only happens at these points in the timeline, the rest is fine)
But everything is fine in the other two sequences! So I'm not sure what's causing this issue other than a bug in Premiere.
Just FYI, I did also try turning all the effects off (except the Push transition), but that didn't change anything.
Thanks all for any help, (or a new CS4 update - wink, wink)
I hope this is clear enough.
Aza

There's a point that I don't understand, shouldn't a un-optimul workflow (using clips that require a lot of rendering power from the cpu and disk access) cause things to slow down or frames to drop?
Why would such a situation cause every frame to be played with cpu and disk access to spare but cause frames to be played in the wrong order? I've never encountered anything like this before.
There are no stuttering or gaps between frames, just frames being played as if the clips were in the wrong order.
Example:
Sequence A contains Sequence B then C
Sequence B: Clip 1, 2, 3, 4
Sequence C: Clip 5, 6, 7, 8
Playing from Sequence A: Clip 1, 3, 2, 4, 5, 6, 7, 8
Playing from Sequence B: Clip 1, 2, 3, 4
Playing from Sequence C: Clip 5, 6, 7, 8
Playing from Sequence A (again): Clip 1, 2, 3, 4, 5, 6, 7, 8
*Wait a while, do something else*
Playing from Sequence A: Clip 1, 3, 3, 3, 5, 6, 8, 7
(Different order happens)
No clips or frames were ever dropped.

Premiere Pro CC crashes because of volume keyframes in the nested sequence

Hello. Looks like there is a bug in the Adobe Premiere Pro CC 8.2.0(65) Build.
The problem is that Premiere crashes each time I have volume keyframes on the clips inside a nested sequence.
So I have one Master sequence and I put a Nested sequence in it. In the Nested sequence I have few subclips with volume keyframes on them. Premiere crashes each time as I roll the playback head over the Master's timeline with the Nested sequence in it. Everything works fine if i delete all volume keyframes on the subclips inside the Nested sequence.
I also noticed that there is no issues when I roll the playback head over these subclips(with or without keyframes) while I am in the Nested sequece. It only occurs on the Master's timeline and in any place.
Master Sequence is 1280x720. The Nested is 4k. Subclips mediainfo:
Format     : XAVC
Codec ID     : XAVC
File size     : 1.94 GiB
Duration     : 5mn 35s
Overall bit rate mode     : Variable
Overall bit rate                         : 49.7 Mbps
Video
ID     : 1
Format     : AVC
Format/Info     : Advanced Video Codec
Format profile     : [email protected]
Format settings, CABAC     : Yes
Format settings, ReFrames     : 2 frames
Codec ID     : avc1
Codec ID/Info     : Advanced Video Coding
Duration     : 5mn 35s
Bit rate mode     : Variable
Bit rate     : 48.0 Mbps
Maximum bit rate     : 60.0 Mbps
Width     : 3 840 pixels
Height     : 2 160 pixels
Display aspect ratio     : 16:9
Frame rate mode     : Constant
Frame rate     : 25.000 fps
Color space     : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.231
Stream size                              : 1.88 GiB (96%)
Color primaries                          : BT.709
Transfer characteristics                 : IEC 61966-2-4
Matrix coefficients                      : BT.709
Audio
ID                                       : 2
Format                                   : PCM
Format settings, Endianness              : Big
Format settings, Sign                    : Signed
Codec ID                                 : twos
Duration                                 : 5mn 35s
Bit rate mode                            : Constant
Bit rate                                 : 1 536 Kbps
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 KHz
Bit depth                                : 16 bits
Delay relative to video                  : 40ms
Stream size                              : 61.4 MiB (3%)

Hello. Looks like there is a bug in the Adobe Premiere Pro CC 8.2.0(65) Build.
The problem is that Premiere crashes each time I have volume keyframes on the clips inside a nested sequence.
So I have one Master sequence and I put a Nested sequence in it. In the Nested sequence I have few subclips with volume keyframes on them. Premiere crashes each time as I roll the playback head over the Master's timeline with the Nested sequence in it. Everything works fine if i delete all volume keyframes on the subclips inside the Nested sequence.
I also noticed that there is no issues when I roll the playback head over these subclips(with or without keyframes) while I am in the Nested sequece. It only occurs on the Master's timeline and in any place.
Master Sequence is 1280x720. The Nested is 4k. Subclips mediainfo:
Format     : XAVC
Codec ID     : XAVC
File size     : 1.94 GiB
Duration     : 5mn 35s
Overall bit rate mode     : Variable
Overall bit rate                         : 49.7 Mbps
Video
ID     : 1
Format     : AVC
Format/Info     : Advanced Video Codec
Format profile     : [email protected]
Format settings, CABAC     : Yes
Format settings, ReFrames     : 2 frames
Codec ID     : avc1
Codec ID/Info     : Advanced Video Coding
Duration     : 5mn 35s
Bit rate mode     : Variable
Bit rate     : 48.0 Mbps
Maximum bit rate     : 60.0 Mbps
Width     : 3 840 pixels
Height     : 2 160 pixels
Display aspect ratio     : 16:9
Frame rate mode     : Constant
Frame rate     : 25.000 fps
Color space     : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.231
Stream size                              : 1.88 GiB (96%)
Color primaries                          : BT.709
Transfer characteristics                 : IEC 61966-2-4
Matrix coefficients                      : BT.709
Audio
ID                                       : 2
Format                                   : PCM
Format settings, Endianness              : Big
Format settings, Sign                    : Signed
Codec ID                                 : twos
Duration                                 : 5mn 35s
Bit rate mode                            : Constant
Bit rate                                 : 1 536 Kbps
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 KHz
Bit depth                                : 16 bits
Delay relative to video                  : 40ms
Stream size                              : 61.4 MiB (3%)

Image in nested sequence does not let me export my project

Hello,
Here's my issue:
In my Premiere project, I have a "Master" sequence in which I have normal a/v files and two nested sequences, for the video intro and ending.
The problem is with the nested intro sequence, which is composed of several images that I've animated, plus sound. I've narrowed the source of the problem to one specific image in this sequence, which is 5760x3240. I've read in other threads that images larger than 1920x1080 can be a problem, but couldn't find further info.
What happens when I try to render my video in 1080p with this image in a nested sequence is the encoding fails with AME giving me this log message -
" - Encoding Time: 00:00:01
09/22/2014 10:45:46 PM : Encoding Failed
Export Error
Error compiling movie.
Unknown error."
When I try to render in 720p with the image in the nested sequence it works fine. When I take the image out of the nested sequence and just put it on the "Master" sequence it also renders just fine, even in 1080p.
So my question is - why can't I render my project if I have this image in a nested sequence, and if possible, how can I fix it?
Thanks in advance.

Hello again,
While trying to do what you told me I've come across something interesting. Apparently it's not only that one image that's responsible for the problem. Here's how I have it setup:
Premiere for some reason seems to have trouble rendering the still image "BG2.png" (1920x1080) AND the problematic 5760x3240 nested image at the same time. As "BG2.png" does not actually appear until later, I tried cutting it just before the point where it should appear. With that, AME was able to render the video until the point where "BG2.png" started, then it failed again. So I checked in the nested sequence and also cut the 5760x3240 image (because it appears briefly in the start of the sequence then has its oppacity set to 0, it wasn't a problem). So what I had was the 5760x3240 image cut after it appeared (instead of just turning down the oppacity) and BG2 cut before it appeared, that way those images didn't overlap in the master sequence. With that, AME was able to render it just fine. So I have no idea why, but those 2 specific images won't let my sequence render when they ocuppy the same time. Any ideas?

Does a nested sequence keep its render?

I have a nested sequence within my Main Sequence.
Within the nested sequence is Adobe Dynamic Linked clips to After Effects.
I cannot edit these while un-rendered.
If I take the hours to render the data within the nested sequence, and then when moving that sequence in the main sequence, will Premiere have to re-render the initial data?
Or, does it have a memory of the data that is rendered within the nested sequence so it won't be as graphic intensive?

Run a short test and see for yourself.

Flash frame in nested sequence won't go away

Similar Messages

Maybe you are looking for