That red frame discussion

So i have been dealing with red frames for about a year and a half now -
- In Premiere pro CC and early CC 2014 versions, .MXF footage used to red frames and relink badly on multi spanned clips if the sidecar files were detected by premiere. This was a major bug because your edit would now relink to bad timecode. The handling for that was deleting any kind of metadata before importing your .MXF files. this worked 99% of the time for me - did not get much bugs after that.
- Skip to what i believe was the 8.0.0 version, and most importantly the 8.0.2 - i do not have re link issues, however red frames appear on export nearly everytime. With the media encoder log you can see how much red frames you have, but no timecode and its still a pain in the *** to double export(correcting the red frames on the first export file).
- From the few adobe employee posts i have read, the way to counter this is - import the card while maintaining the structure, then import footage via the Media browser. This should technically handle any bugs. I have not tested this yet, however i already know that sometimes i get mxf files without card structure(director's sometimes create their bins at the Mac OS X Finder level)
Im hoping adobe fixes this issue ASAP - i undestand that red frames are only an indicator of a bigger problem, but this problem is making me consider converting all my footage to prores before import, thus turning my premiere pro cc in FCP 7.

Hello Adaptat1on,
- From the few adobe employee posts i have read, the way to counter this is - import the card while maintaining the structure, then import footage via the Media browser. This should technically handle any bugs.
With the release of Premiere Pro CC 2014.2 (8.2), we believe we have solved the "red frames" issue with .mxf files.
If you are working with an earlier version of Premiere Pro or have updated a project file from a previous version of Premiere Pro to 8.2, you might still see them.
The method of importing these files is correct as you outlined above. Copy the SD card to your HD, then import via the Media Browser.
I have not tested this yet
However, this is precisely the right way to import footage coming from a camera's SD card.
However i already know that sometimes i get mxf files without card structure(director's sometimes create their bins at the Mac OS X Finder level).
I would communicate with your colleagues and inform them of how you would like your footage prepared. You should state that you will be saving them money by doing so as you won't have to troubleshoot red frames issues which could still occur with raw .mxf files even in 8.2. Tell them turn around time will be faster, as well. They will listen to you when you speak their language (saving them time and money gets their attention quickly).
Im hoping adobe fixes this issue ASAP - i undestand that red frames are only an indicator of a bigger problem
All our fixes are in 8.2. Please create new projects in version 8.2, ingest the footage correctly, and you should have no trouble with red frames. If you do, please file a bug report and send me a PM.
This problem is making me consider converting all my footage to prores before import, thus turning my premiere pro cc in FCP 7.
That's certainly an alternative, but I'd try the method previously outlined before doing anything rash like transcoding. That said, certain cameras produce beautiful pictures but create files which perform poorly in Premiere Pro. I'm most frequently tempted to transcode Canon footage, as that gives my Mac Book Pro the most trouble.
Hope this info helps.
Thanks,
Kevin

Similar Messages

  • How to detect red frame in a series of images using web cam?

    hey i am a new use of lab view(8.2 n 8.6).kindly ca any1 help me out in red color detection in a series of frames being capture by a usb web cam.i have done the grabbing thing but dont knw what to do now.plz help me out. basically i hve to do the following things:
    1 )the camera is continuously making video
     2)the moment a red color or red frame comes across the camera the camera is programmed such that it will capture that red frame. and display that captured frame
    plz hep me out.i need serious help.
    i am attaching a vi that is grabbing the images and then xtracting the red color info n thn displyaing its intensities rows and coumn wise on a graph.here i have used a guassian surface to locate the red color.
    Solved!
    Go to Solution.
    Attachments:
    giving intensity of red color.vi ‏78 KB

    hey,i have made the code plz chk it and do rep soon as ma project sbmission date is very near =((
    i am snaping an image from the web cam then comparing it with the red colored jpg image made in paint.
    the jpg image is converted  to give input image to imaq match vi.but after the comparison it gives the same output.
    on the front pannel the snapped image is displayed,the red colored image that is converted in to its respective pixels is displayed and the image that is obtained after cheking the image in the draw fails vi...the pic converted to pixels is all the time displayed.and the pass/fail icon always denotes one pass led on..plz chk the code =((.
    also can u provide me some guide line for using thr hough transform for the red color detection in lab view..i dont have to import the matlab code..i have to purely make it using the lb view libraries.
    also one more request pl rep me regularly as i really need your golden piece of advice for ma success.
    thnx
    Attachments:
    picture to image(BY ME).vi ‏102 KB
    untitled.JPG ‏3 KB

  • RED FRAMES ON PREMIERE PRO 8.1 CARAVAN ON PROJECTS THAT WERE FINE BEFORE

    I am having this RED FRAMES issue now, never heard of this problem until now. And its happening inside projects that had been ok since a few months back when I finish them. I just went in to export again some of the sequences and now the red frames are all over like a plague. Its Canon footage from an XF300. Ive deleted media cache files, digital rebellion house clean, and now that I want to restart premiere it keeps on crashing while loading the media files, I relaunch again and it loads some more files a bit further until if finally stops crashing after 3 -4 times. I tried then the solution that somebody stated: offline clips, delete media cache, save project, close project, link again, and the red frames were gone from the timeline, but they did show up in the exported movie!! I need to deliver this to client this Monday!! Is there any fix to this? I been using this project for a few months exporting movies with no problem until now, but I haven't changed anything in the project. What caused it? What should I do to fix this asap. Please help! Im running of Premiere Pro 8.1 Caravan OSX 10.9.2 I need to deliver movie to client asap im pulling my hair.

    Hi Somu cena,
    Welcome to Adobe forums.
    You can install the 8.2 update directly. Please check what's changed and fixed in both the updates from the below links.
    Premiere Pro CC 2014.1 Release | Premiere Pro work area
    Premiere Pro CC (2014.2) Release | Premiere Pro work area
    Regards,
    Vinay

  • Getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

    getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

    i solve my red frame problem. originally my project was done in premiere pro cc 2014.2 & i render in Encoder cc 2014. in newer version i get lots of red frames. i complain a lot to adobe customer support . they said they know the issues but they couldn't solve. I was so tired from adobe customer support. one of the worse customer services i had. My friend got the mac pro & e got premiere pro cc 7.2 version. i convert all my footage mxf to mp4 in encoder cc 7.2 version and i succeed. i don't get any red frames.
    So i think the problem is in adobe encoder cc 2014.2 version. newer version.

  • Red Frames - Version 7.2.1

    I know there have been a lot of discussions about red frames in CC, I think I've read them all and tried every solution, here's my situation in case there is something that I missed.
    I work with many long (2 hour plus) .mov files with the AVdn codec and  after an upgrade to CC on Friday these files now have red frames every 5 minutes or so (maybe more) when opened in anything CC.
    I'm using 7.2.1, have tried deleting my media cache, have tried opening, closing, reopening, restarting, exporting, copying, pasting, and nothing works. 
    Is there a solution that I missed BESIDES the following:
    Re-exporting all my files with a different codec and using Media Encoder CS6
    Rolling back to a prior version

    Hi William,
    Can you update Premiere Pro to Premiere Pro CC (7.2.2) or CC 2014? That should solve your issue.
    Thanks,
    Kevin

  • I had completed my iDVD project and burned a disc. It worked great! Then someone messed with the project and put a red frame around the opening screen. Now when I burn the project, it no longer has the opening frame. How can I fix?

    I had completed my iDVD project, a Wedding Slideshow with pictures and music, and burned it on a disc. It worked great! Then someone messed with the original project on my computer and clicked around and put a red frame around the opening screen that has the Wedding theme with music. Now when I burn the project to make more DVDs, it burns but no longer has the opening frame. It immediately opens to the iMovie slideshow. How can I fix so I can burn the entire project with opening frames?

    As Bengt suggested make a disk image of the successfully burned DVD using Disk Utility. Then you can burn copies any time you need one.
    In the future once you have the project as you want it save it as a disk image via the File ➙ Save as Disk Image menu option.  This will separate the encoding process from the burn process. 
    To check the encoding mount the disk image and launch DVD Player and play it.  If it plays OK with DVD Player the encoding was good.
    You can then burn it to disk with Disk Utility at the slowest speed available to assure the best burn quality.  Always use top quality media:  Verbatium, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
    OT

  • Red frames popping up after upgrade to media encoder cc

    I'm having some issues with Media Encoder CC. My workflow is AMA SxS card (footage is in XDCAM HD 1080/50i) into Avid Media Composer 6, edit, and export as XDCAM HD 1080/50i mxf file into a watch folder that Media Encoder picks up and converts to SD mpeg2 (its the way the TV stations want it) that file is then ftp'd using Media Encoder. It used to work fine with Media Encoder CS6, but since I upgraded it keeps giving me red frames (cant read frame errors) usually just before or after there is a cut in the footage. I've resorted to transcoding the footage in Avid to DNxHD 120 after editing and that seems to resolve the issue, but it's just an extra step that adds loads of time to my workflow.
    Avid Media Composer 6
    Adobe CC
    HP EliteBook 8760w
    Windows 7 64bit

    The whole point is that I dont want to transcode into DNxHD at all, DNxHD is the extra step. The can't read frame errors are also very inconsistent in Media Encoder CC.  I might export a file and it gives me a few red frames (can't read frame errors) but if I then take the same file and rename it they sometimes work.  I've tried uninstalling and reinstalling but that hasnt helped...

  • Red Frames and .mxf read failures PP CC 2014 8.1 update. Oct 6.  Anyone else see the new update fail? Any suggestions?

    Hi,
    I cut 9 hours worth of broadcast video in PP CC 2014 8.0. (The yellow interface.) I had no issues. It was all great. For some reason, before I exported the finished cuts for broadcast, I updated the Adobe CC 2014 suite to v1.8.0.447 (PP has the blue interface). I feel stupid. I broke my own rule of not updating software until the projects you work on are done. Now I can't open this project without Red Frames in my timeline and in my exports. I have been reading about this Red Frame that seemed to first appear in PP CC 7. (Maybe even as early as 2006) I never had the problem then, I run Premiere Pro everyday.
    My Issue seems to be a bit different than most of the issues that have read. I have cleared the cache, & I have ditched the preview files. This did not fix it as stated it would in previous forum posts.  I have moved the footage location from a server to a local thunderbolt SSDrive and renamed the folders and re-linked the video footage. Still Red Frames.
    What is odd, is when I boot up the project and after all media has loaded, it looks like it is going to work for a few minutes. I get happy and scrub the timeline checking for the red frames, hoping the problem solved when I cleaned the cache etc.. Everything seems to be fine, audio synch, picture, lower thirds and graphics all appear fine. Then the red frames appear over time, and by 5 minutes after scrubbing, I see mostly red frames. Audio is still there though. Even weirder, is that when I resize the height of the video track, the red frame comes and goes with no real pattern.  The clip preview picture flickers with the red frame. The red frames export through through Premiere and through a Media Encoder cue which say .MXF read error so I'm hooped. ( it does render the video, but has the red frames )
    I run a Mac Pro;
    OSX Yosemite 10.10
    3.5 GHz 6-cor Intel Xeon E5
    16 GB Ram
    AMD FirePro D500 3072 MB
    Canon XF-305
    .MXF files
    1080p 29.97
    5 Cam Multicam Seq.
    Adobe CC 2014
    Version 1.8.0.447
    released on October 6, 2014
    I am noticing something interesting with my source footage folders. I am getting some .mxfindex files with really long names, like temp files almost, that don't go away. I still get Red Frames after deleting them, clearing cache, changing drive locations and file and folder names and relinking. When I delete these long files the software wont boot the project very well and crashes a few times before it opens, still with red frames. This problem with this project occurs on every computer (4)  in the studio, which are the same as mine, we all updated at the same time. 
    Files look like this:
    What happened in that update? Is there a fix for this? Any suggestions? If not, Is it possible for me to roll back my whole CC 2014 version to 8.0?  I am terrified to open any other of our projects... I am under time pressure and am starting to do the re-edit of this in CS6 which seems to run flawlessly, but because of Adobe's RIDICULOUS FAIL in backward compatibility, I can not open this project in anything but PP CC 2014. 120 hrs of lost editing will certainly have me scratching my head about continued use. Any suggestion, links or information would be appreciated.
    Thanks .

    Hi 5neaky c,
    5neaky c wrote:
    For some reason, before I exported the finished cuts for broadcast, I updated the Adobe CC 2014 suite to v1.8.0.447 I feel stupid. I broke my own rule of not updating software until the projects you work on are done. Now I can't open this project without Red Frames in my timeline and in my exports.
    You should still have a Premiere Pro CC 2014.0.1 (8.0.1) project file available to you by default. Can't you go back to that version and complete your project? That's what I'm recommending those having this problem do.
    5neaky c wrote:
    I have been reading about this Red Frame that seemed to first appear in PP CC 7. (Maybe even as early as 2006) I never had the problem then, I run Premiere Pro everyday.
    As long as you ingest the footage via the Media Browser and do not update the project file, you shouldn't have issues like this. I have heard complaints in new projects with Premiere Pro CC 2014.1 (8.1), so I have reopened a previously closed bug.
    5neaky c wrote:
    My Issue seems to be a bit different than most of the issues that have read. I have cleared the cache, & I have ditched the preview files. This did not fix it as stated it would in previous forum posts.  I have moved the footage location from a server to a local thunderbolt SSDrive and renamed the folders and re-linked the video footage. Still Red Frames.
    If this is not working, please complete your project in Premiere Pro CC 2014.0.1 (8.0.1)
    5neaky c wrote:
    What is odd, is ...
    Everything seems to be fine...
    Then the red frames appear over time….
    Yes, I've seen this with another customer's updated project.
    5neaky c wrote:
    I am noticing something interesting with my source footage folders. I am getting some .mxfindex files with really long names, like temp files almost, that don't go away. I still get Red Frames after deleting them, clearing cache, changing drive locations and file and folder names and relinking. When I delete these long files the software wont boot the project very well and crashes a few times before it opens, still with red frames. This problem with this project occurs on every computer (4)  in the studio, which are the same as mine, we all updated at the same time.
    Sometimes, deleting sidecar files can help the situation but not always. It looks like you are having trouble when deleting them.
    5neaky c wrote:
    What happened in that update? Is there a fix for this?
    A bug that was fixed for red frames in 8.1 was somehow broken by the time we shipped this version. We have reopened the bug, but currently, there is no fix.
    5neaky c wrote:
    If not, Is it possible for me to roll back my whole CC 2014 version to 8.0?
    Yes, see my blog post here: Install a previous version of any Creative Cloud application
    Included in the post is a patch for Premiere Pro CC 2014.0.1 (8.0.1).
    5neaky c wrote:
    I am under time pressure and am starting to do the re-edit of this in CS6 which seems to run flawlessly, but because of Adobe's RIDICULOUS FAIL in backward compatibility, I can not open this project in anything but PP CC 2014.
    Thanks .
    You can always try exporting a FCPXML for backward compatibility, but for complex sequences (like multicamera), this isn't always an option. There aren't many NLEs providing backward compatibility, sorry. Feel free to request that, if you like, here: http://adobe.ly/feature_request
    Thanks,
    Kevin

  • Premiere CC 7.1 - Red frames in playback and export

    Having some problems after the 7.1 update.
    In a variety of projects, on a variety of footage, we're experiencing random fully red frames (#ff000). Sometimes there are 1-2 frames in a clip, and occaisionally it's 80%-90% of the frames in a clip (this is less frequent). It has never been all of the frames of a clip.
    This happens:
    - On an undrendered timeline (you'll be watching an edit and you'll see a red frame - if you scrub back to it it'll still be there)
    - On a rendered timeline
    - In exports
    Red frames that are visible on a timeline, are sometimes carried through to the export and sometimes not. Sometimes an exported file will display red frames that were not present on the timeline.
    Red frames seem to be based on clips, not sequence frames. For example, in one of my exports, I had video footage with a lower third graphic over it. In one frame of the export, a red box appeared over the graphic, but the main shot was not affected.
    This has happened to the following types of footage:
    - .MTS (from C100)
    - .MXF (from C300)
    - ProRes 422 MOV
    - ProRes 4444 MOV with alpha channel
    Fixes that seem to work:
    - If an export has red frames, re-export. Watch the new one like a hawk. Repeat until you get lucky.
    - If a clip on a timeline has red frames, force a re-render via a Crop filter or similar
    - Quit Premiere and reopen it
    System/environment details:
    - OSX 10.8.5
    - Premiere Pro CC 7.1
    - Mercury Playback Engine Software Only
    - Often (always?) I-Frame Only MPEG sequence settings
    - Much (all?) of the footage we've been working with has been on AFP shares via GigE with MTU of 9000
    I haven't been able to confirm yet:
    - Whether this ever happens with locally stored footage
    - Whether this ever happens when Queueing to media encoder (rather than Exporting from Premiere)
    - Whether changing to a QuickTime Desktop based sequence setting resolves the issue
    Is anyone else experiencing this issue? It's frutstratingly un-testable, since it seems to happen at random. We'll continue to gather data points though and see if we notice any other trends.
    Edit: Added additional system context

    the error also appears with PRORES 422 files, but only after a certain amount of source data from prores 422 clips is processed / read
    i made a test comp in AE with only one gigantic prores 422 source clip (8000 pixels x 1000 pixels @25fps) and the error first appeared at around 1500 frames read from the source file (equalling a few GB of source read and processed). after the red frames error appears once, the erroneous red frames appear more often but never in the same place when rendering the same comp several times)
    i also made a test comp containing only a few full HD prores 422 clips (1920 x 1080, @25fps), there the error appeared only seldom (but still randomly). so it can be that a broader user base never experiences this erroneous behaviour at all.
    i also made a testcomp containing about 40 full HD prores 422 clips (each 1920 x 1080, scaled down to 10% in size and distributed all over the comp so i can see them all at once). the erroneous red frames appeared within the first rendered frames!! obviously, many qt files had to be open and read in parallel, and so the error appeared from the very beginning of the rendering / export.
    i suspect that the AE / PR applications open a RAM buffer for each open prores source file they need to read, and that this buffers somehow becomes compromised when it overflows and when buffer resize / buffer clear / flush operations take place.
    of course i tested all sorts of RAM assignents for MP rendering (1GB per core, 2GB, 4GB, 6GB) and i rendered with several different settings of how many cores and ram should be available to other tasks. but the error always appeared. randomly.
    --> fact in AE is, that nearly all MP renders / exports using prores clips as source files contained the bad red frames. when rendering without the MP option on (but of course up to 20x slower) so far i never experienced this error (of course always after fresh restarts once the error appeared)
    PLEASE FIX THIS ASAP
    mac pro 2011, 12 cores, osx 10.8.5, 64 GB ram, angelbird SSD, ati hd radeon 5770 1GB

  • Red Frames in Playback and Export

    After finding out that others have had this problem and found solutions, I expected the solutions to work, but no luck so far.
    I am working with HDV 1080i60 footage in Premiere Pro CC 7.2.1 on OS 10.9.1. When I play my footage through the source window (by double-clicking it in the Project window) or on a sequence timeline, I see intermittent red frames - a lot of them. The red frames persist through export, leaving me with no way to edit this footage except to transcode it to a different format - presumably with an encoder other than Adobe Media Encoder.
    Adobe, you have posted possible solutions for other people with this problem, but obviously it persists. What's the nex step?

    LFedit, my red frames do not appear only on cross dissolves. They appear during normal playback in the source monitor as well as in the program monitor AND in the small preview area in the project window.
    I've seen posts about this problem from the end of 2013, but I'm glad to know I'm not the only still experiencing trouble. I've already submitted a bug request to Adobe. Please do the same, LFedit. The more people report it, the more likely Adobe will pay attention.

  • Another weird media issue - red frames at the end of h.264

    Tested with CS6 and CC, bunch of media exported using h.264 wrapped in MOV or MP4, this media plays fine in QT player, Windows Media Player, Media Composer, Sorenson Squezze, CatDV, Flame, Smoke, and any other app I try, but in any CC or CS6 app, the last frame is a red frame, which also takes time to show up if you park right in that frame, and some times crashed the app.
    Something else is while any other app not from Adobe reports movies to have for example 300 frames, Adobe apps will report to have 301... I can repeat this on any machine I test.
    Can provide a movie for testing too.
    V.

    here is:
    https://www.yousendit.com/download/bWJyS3hjNDJUMFBFdzhUQw
    open it with QT player and switch it to show you frames not time, you will see it says 60 frames (0 to 59) and there is no red frame,  open it with any CC or CS6 app and you will see 61 frames, last one red. This is not very noticeable in Premiere Pro CC when playing, but if you park on the last frame you will see it, After Effects gets pretty slow and not responding for a few seconds when you park on the last frame.

  • Red frames in export with version 7.2.1

    Sometimes when I export a material appears in any part of the video a red frame. Would i like to know what to do to solve my problem?
    I have a MAC PRO OS X 10.8.5 and i'm using premiere pro cc 7.2.1.
    Thanks!!

    Hi William,
    Can you update Premiere Pro to Premiere Pro CC (7.2.2) or CC 2014? That should solve your issue.
    Thanks,
    Kevin

  • Red frames in 7.2 (7.2.0 or 7.2.1) when playing .mxf files

    I have an iMac (mid-2011) with the 6970M card (officially not supported but capable of OpenCL) and a new MacBook Pro with the GT 650M card (officially blessed by Adobe, which is why I bought the computer).  In 7.2 (either 7.2.0 or 7.2.1) red frames have popped up in seemingly random places when I play .mxf files.  When I rolled back to 7.1 on my iMac, the red frames disappeared.  I have checked this issue on your forum and tried deleting both the cache and the preview files; neither have worked.  Unfortunately for me, my major job for the last half year entails working strictly with .mxf files.
    I am wondering if you are planning any fix for this issue, which seems quite major as it is occurring on two different machines with two different video cards.  If it weren't for the fact that the problem continues into exporting, I'd live with it, but the export issue makes it unusable in a professional environment at present.

    Hi Peter,
    Thanks for getting back to me!
    the 5k media is 5120 x 2700 and are red r3d files, at a 8:1 redcode compression. Also 5120 x 2560 is the same.
    I have a Blackmagic Ultrastudio 4k (1st generation) feeding a sdi signal to a flanders Scientific monitor, and also a Panasonic HDTV via HDMI.
    The quality looks the same across the Program monitor, flanders monitor and the HDTV.
    i have been editing in 1080p sequences - mainly the red r3d 1080p, but have also used the blackmagic sequnce settings plus many more and am observing the same issue.
    As a test i rendered out a short clip at the 5120 x 2700 at full res to prores, imported the prores clip back into premier and resized into a 1080p sequence, playback res set to either 1/4, 1/2 or even full the clip enlages full size in the program monitor to full size but as soon as i pause playback it looks normal. so i dont think its a r3d issue but more a resolution scaling issue on playback. Purley for testing purposes i also tried a 1080p clip in a very low res sequnce at 640 x 360 and obsereved the same issue. 1080p clip in 1280x720 and 1024x576 seemed fine. This issue is a bit different to the above problem of 1/4 res not looking as good as it did but i think the problem is related.
    so it seems that either my system has an issue or a strange bug in the update, DaVinci Resolve is working as normal so i can only assume its a bug ??
    Thanks for your help with this,
    Tim

  • Captivate 7 not showing the red frame when recording a slide

    I've been using the "Record Additional Slides" button since Captivate 5, and never run into this problem: the red frame that lets you define what you want to capture is not displaying. When I try to record, Captivate captures a portion of the software window, and the desktop. How can I force the red frame to display?
    Thank you for your help!
    Heloisa
    *** By the way, it is happening when I run Captivate from my Apple computer. I just tested running Captitvate on my parallels machine, and the frame does show up.

    Hello,
    Just to clarify, the problem (no red frame while recording slides) happens only on the Apple version of Captivate. It runs fine on my parallel machine, however I am running a trial version there. My license is for the Apple platform. I'm concerned because my trial period will expire soon. the weird thing is that the Captivate that I have in my machine at home does not present this behavior. Only the one in my work machine.
    The project resolution is 930px x 697px
    This is the 14th module that I am developing for a training suite.I have never encountered this problem before. It all started after the Maverick's fiasco
    So do  you think I should uninstall Captivate and start a brand new install? I tried changing the name of the folder but that didn't help much.
    Thank you!
    Heloisa
    *****I just uninstalled and re-installed Captivate 7 7o my apple machine, but the problem persists. ;(

  • Imported MPEG has red frames, how do I solve this?

    Hi,
    I've been playing with Premiere and just create the final movie on something I'm working and I happened to notice that almost at the end, there's a red frame in the video. What's up with that?
    I play the original MPEG2 file in Windows Media Player (it was created with muvee Autoproducer and I'm doing editing in Premiere) and there's no red frame at all. But after importing it into Premier, there's a red frame.
    Possibly more... How do I find all these red frames and what should I do to fix them?
    I don't understand why they are red if the original doesn't have any...

    Well, I read something about it that it was some kind of error yes and that I could see it on the events window, however, no errors were reported.
    I found another document page at the Adobe site that talked about 3.2.0 update to Premiere (which I though I had, but I didn't) and that this update introduced these red frames and bla bla (but I has having them before the update). Anyway, I did the update, deleted all the cache files, opened the project, the files index was recreated and the red frame gone (at least on the frame I saw it before).
    I'm going to produce a new output and then I'll just have to check for those red frames.
    Maybe with this update and if the events window is really empty, maybe there are no errors (red frames) at all.
    I hope...
    Thanks for the input though.

Maybe you are looking for

  • Dysfunctional customer support

    Inclined to Investigate other software I was rather proud of using Adobe Creative Software for my creative photography and (more avocational) creative graphic design workflows. I was happy to use the acknowledged industry standard and impressed with

  • Pkg's made by PackageMaker from Xcode4.2 stopped working after Mountain Lion 10.8.1 upgrade!

    We have some pkg's that used to install fine across Snow Leopard, Lion and Mountain Lion. Those pkg's were made from PackageMaker that came with Xcode4.2. Since last week's Mountain Lion 10.8.1 upgrade, the pkg's preflight/postflight scripts stopped

  • K7N2-ILSR not installing windows XP

    I got this board well over a year ago and have tried working on it off and on;  Of course it is in one of my backup computers.  Now, when I first bought it, "secondhand" from a guy online, I found it to be frustrating to work.  I had never owned and

  • HT201177 i am having problem with my camera on my mac book

    i bought iphone 4's for me and my wife and now the camera on my macbook isn't working. does anyone think this is related?

  • Oracle Maps javascript client

    Hello, I'm trying to integrate the Oracle Maps client into a web page that will run on a different host and a different app server than OC4J. First of all, is it possible? Do I understand correctly that if I copied the sampleApp.html to a diffenent h