[CS4] Red frame on active cam during multicam?

CS4
I'm trying to find what it means when working in multicam mode, to have a red (instead of yellow) frame appear around the active camera
in the multicam monitor.
And a litte bit of an aside here:
I searched the forum on `red frame multicam', `red multicam', and finally just `red'.  But found no help on this question.
I wonder why one cannot get to the `advanced' search tools, without first trying the plain search... which appearantly searches all forums.
Then once you've gotten to the advanced search there is the nasty nightmare list to choose which forum to search from.  It appears to be in no known order and is impossible to search with the page search tool (Ctrl-f).   Really a bad setup.  And even then still didn't find an answer.

HarryPutnam wrote:
CS4
I'm trying to find what it means when working in multicam mode, to have a red (instead of yellow) frame appear around the active camera
in the multicam monitor.
And a litte bit of an aside here:
I searched the forum on `red frame multicam', `red multicam', and finally just `red'.  But found no help on this question.
I wonder why one cannot get to the `advanced' search tools, without first trying the plain search... which appearantly searches all forums.
Then once you've gotten to the advanced search there is the nasty nightmare list to choose which forum to search from.  It appears to be in no known order and is impossible to search with the page search tool (Ctrl-f).   Really a bad setup.  And even then still didn't find an answer.
As Gilda Radner would say `nevermind'  I found the information by searching the PDF on `Whole words only' using `red'
It means the frame is recording

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 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

  • Out of Sync after Red Frames

    I'm capturing HD footage from an FX1 camera into my computer. Each clip is appx. 1 hour long (the length of a MiniDV tape). Almost every clip has red frames, after which the audio is always out of sync. Yet when I play the clips in Windows Media Player they are comletely in sync. How can I get Premiere Pro CS4 to play these same clips in sync, the way Windows Media Player does?

    I only use new tapes and I clean the heads on the FX1. But that is not the answer to the question I asked. How can I get my very expensice Ppro CS4 to play the clips in sync, the same way my free Windows Media Player plays the same clips in sync?.

  • Multcamera monitor - problem selecting active camera

    I am using PremPro CS4 on a Win7-64 bit quad Intel quad core machine with 8GB of DDR2 1066 RAM but this problem has occurred earlier when I was still using XP-32 bit.
    It seems that after a time, my Logitech wireless mouse is working fine in everything other than when trying to change the active camera view in the multicam monitor.  I have to hit the left button repeatedly to eventualy get the change that I want.
    I have the current and correct driver, and have confirmed that this happens with both a wireless and wired Logitech trackball type mouse.
    Has anyone had this issue and if so, is there a work around as it really extends the time it takes to do the edit.
    Frank
    Australia

    I tried the keystrokes, Curt, but it was pretty much the same both in the
    numeric keypad and the general keyboard..
    It seems intermittent and not consistent at all.  This is at the end of a
    VVEEERRRYYYY long complicated multicam edit since what was supposed to be 90
    miutes took 3 hours and the tape use and camera synch was all over the
    place.
    But it certainly is driving me to distraction.
    Thanks for the response.
    Frank

  • 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

  • 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.

  • Red frames in Sequence/Exports

    Hello. I'm experiencing red frames (some longer than others) within my timeline and on exported files. Sometimes they wont be on the timeline but appear in the export file and vice versa. I'm using XAVC-L codec from my Sony FS7 camera in a AVCHD 1080p timeline. I'm trying to export to H264 .mov files. This happens in both Premiere and by going through Media Encoder.
    Specs:
    Premiere Pro CC 2014.2 Release 8.2.0 (65) build
    (New) Mac Pro Late 2013
    2.7 GHz 12-Core Intel Xeon E5
    32GB RAM
    AMD FirePro D500
    OSX 10.9.5

    Hi,
    Have you tried exporting to a different format? I would suggest so.
    You can also try to change the Video Renderer to Mercury Playback Engine software only under File > Project settings > General
    Thanks,
    Rameez

  • Random red frames appearing in CS3

    I've been using PP CS3 for a few weeks now and I have encountered a strange problem that I didn't see in PP2: random red frames appearing in the project.
    Sometimes the red frames are visible when reviewing the project on the timeline (before rendering), and sometimes they show up only after exporting the project to AVI or to flash via Adobe Media Encoder. I'm using MPEG files from Sony hard-drive cameras.
    At first I thought it was an issue with my new laptop, but the problem is also occurring on my desktop computer. Both computers have duo-core 2.2 ghz processors and 512mb dedicated memory video cards and 2 mb of system memory.
    I am quite disheartened because I feel I wasted nearly $300 on an upgrade to CS3. I have Googled this problem extensively and haven't found a viable solution. Can anyone help? Thanks.

    Not counting HD material, my general understanding is that Premiere is designed to work with SD material where each video frame is complete, not the type of file where 1 frame is complete, and several following frames are simply code which describe changes from the preceeding frame (ie-DV AVI Type 2 files... and not the Type 1 files produced by Windows Movie Maker, and certainly not the AVI files using the divX codec)
    Read here to see
    Why NOT to try and edit an MPEG
    Whatever Premiere does with MPG on the timeline is simply an afterthought... not a design feature (again, this is MY understanding, from reading this forum, and is not based on any inside knowledge of Adobe programming)
    If you simply must edit MPG files, you might look at different products
    Edit MPEG with
    Premiere Elements
    or
    WOMBLE
    or direct from DVD with
    Movie Edit Pro
    Otherwise, do as suggested and convert the files to DV-AVI Type 2

  • How do I change my light setting of camera during chat?

    People comments me while chatting that my background light is dark while chatting using Mac Pro, how do I change my light setting of camera during chat or facetime??/

    Using FaceTime http://support.apple.com/kb/ht4319
    Troubleshooting FaceTime http://support.apple.com/kb/TS3367
    The Complete Guide to FaceTime + iMessage: Setup, Use, and Troubleshooting
    http://tinyurl.com/a7odey8
    Troubleshooting FaceTime and iMessage activation
    http://support.apple.com/kb/TS4268
    Using FaceTime and iMessage behind a firewall
    http://support.apple.com/kb/HT4245
    iOS: About Messages
    http://support.apple.com/kb/HT3529
    Set up iMessage
    http://www.apple.com/ca/ios/messages/
    Troubleshooting Messages
    http://support.apple.com/kb/TS2755
    Setting Up Multiple iOS Devices for iMessage and Facetime
    http://macmost.com/setting-up-multiple-ios-devices-for-messages-and-facetime.htm l
    FaceTime and iMessage not accepting Apple ID password
    http://www.ilounge.com/index.php/articles/comments/facetime-and-imessage-not-acc epting-apple-id-password/
    Unable to use FaceTime and iMessage with my apple ID
    https://discussions.apple.com/thread/4649373?tstart=90
    For non-Apple devices, check out the TextFree app https://itunes.apple.com/us/app/text-free-textfree-sms-real/id399355755?mt=8
     Cheers, Tom

  • Red frames on the movie exported

    Hi, I exported a project to MPEG2 blu-ray (source XMF files, camera Canon XF100), and I have several red frames within the movie. It's almost unusable. I have tried to do media cache cleaning, re-rendered the effects, but still without success. I work on Macbook Pro with OSx Yosemite. Premiere is 2014.2 v8.1 Caravan build 8.2.0.
    Could someone have experienced this issue?
    Does Adobe have a fix?
    In the meanwhile, I prefer downgrade to CS6, that is rock solid. The problem is the waste of time to start from zero, because the project isn't down-compatible. This is a crazy way by Adobe to handle a downgrade!
    Bye

    Hi, I still have the issue. I'm using Premiere Pro 2014.2 v8.1 Caravan 8.2.0 (65) build, on Macbook Pro, half 2012, Yosemite 10.10.2. Several red frames in the output exported (MPEG2-bluray) from MXF source (Canon XF100). After several export try, the red frames still remain, but they are located in different positions. I confirm that the same clip exported using Premiere CS6 (and also using Premiere CC 2014.0 v8.0) are OK, without red frames!!! The big issue for me is that the project cannot be opened by previous Premiere releases, and I lost weeks of work!!!
    Adobe, any news? I'm available to give you all the information you ask to test the case.

  • MXF decode errors and red frames in exports

    Ever since upgrading to Premiere Pro release 2014.2 (8.2.0 (65) Build) we've been having problems with random red frames appearing in our exports.  These errors are always associated with our Sony PMW-200 media files (.mxf files.)  Red frames during editing happen very rarely, but are usually present in our exports.  For short form work re-exporting the sequence will work sometimes, but may cause red frames to appear elsewhere...  For long form work we've adopted a very lengthy work-around to fix the errors after exporting.
    Phone support recommended deleting the media cache files, but we've tried that and the problem still exists.  This problem is happening with new media that has been imported since the upgrade as well as old media that we imported before the upgrade.  We're editing with many mixed media files all in their native codec and the only media files that get flagged with decode errors are the .mxf files.
    We edit a large volume of work daily and this problem is a huge setback in our confidence with our exports as well as Adobe products.
    For the record were editing with Mac Pros that are about a 3-5 years old with OS X 10.8.5 and an Xsan shared storage system.  We have a Cloud for Teams subscription and all our software is updated frequently.
    Any thoughts would be helpful.  Personally I would love to escalate this problem to a higher level support team.
    Regards,
    Eric

    I have the same problem running Adobe CC on high-end PCs. - My business is smalish, but this leads to having a rather big impact on my confidence.
    MXF-files from Canon C300 and Sony FS7 platforms.
    - With FS7 footage I've had the frames appear throughout a clip with perfect distance (16 frames apart) - when applying Denoiser 2 from Red Giant. - The plugin simply stopped the frames from appearing on a random basis.
    - I've also experienced that when the error was present, dissolves became cuts.
    - I've tried to isolate software/hardware rendering, but it does not seem to change anything to select one over the other.
    I try work around it by rendering uncompressed sections of the timeline and replace it where it works, and then try again and again. - Very time-consuming and cumbersome.
    Best
    Torsten
    Denmark

  • 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

  • ACTIVATION Error during phase MAIN_SHDRUN/ACT_UPG

    Hello Experts,
    I am facing an activation error during upgrade o ECC 6.0 EHP 6 in shadow instance.
    ERROR: Detected the following errors:
    # F:\SUM\abap\log\SAPA702EPU.UAS:  3 EDT012XActivate table "PTRV_UTIL_VPFPS_VPFPA_P" 3 EDT402 Append structure "PTRV_VPFPS_VPFPA_P_APPEND" appended to table "PTRV_UTIL_VPFPS_VPFPA_P" 1EEDT963 Field "TIME_DURATION" in table "PTRV_UTIL_VPFPS_VPFPA_P" is specified twice. Please check 2WEDT135 Flag: 'Incorrect enhancement category' could not be updated 3 EDT013 Table "PTRV_UTIL_VPFPS_VPFPA_P" was not activated 1EEDO519X"Table" "PTRV_UTIL_VPFPS_VPFPA_P" could not be activated  3 EMC738XActivate view "V_T706S_EHP" 1EEMC560 Field "T706S"-"D2100" does not exist 1EEMC560 Field "T706S"-"EXCHANGE_DATE" does not exist 1EEMC560 Field "T706S"-"TRIP_BREAK_CNTRY" does not exist 3 EMC742 View "V_T706S_EHP" was not activated 1EEDO519 "View" "V_T706S_EHP" could not be activated
    ...skipped 13 more lines. Please see ACTUPG.html for more information.
    SAPup_troubleticket.log
    This trouble ticket was created by SAPup on 20140801092425
    SAPup broke during phase ACT_UPG in module MAIN_SHDRUN / Shadow System Operations: SPDD and Activation
    Error Message: Detected 5 errors summarized in 'ACTUPG.ELG'
    Calling 'F:\SUM\abap\exe/tp' failed with return code 8, check F:\SUM\abap\log\SAPup.ECO for details
    tp used shadow connect
    ACTUPG.ELG:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in F:\SUM\abap\log\SAPA-10202INPOASBC.UAS
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8">
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPA702EPU.UAS
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       3 EDT012XActivate table "PTRV_UTIL_VPFPS_VPFPA_P"
       3 EDT402 Append structure "PTRV_VPFPS_VPFPA_P_APPEND" appended to table "PTRV_UTIL_VPFPS_VPFPA_P"
       1EEDT963 Field "TIME_DURATION" in table "PTRV_UTIL_VPFPS_VPFPA_P" is specified twice. Please check
       2WEDT135 Flag: 'Incorrect enhancement category' could not be updated
       3 EDT013 Table "PTRV_UTIL_VPFPS_VPFPA_P" was not activated
    1EEDO519X"Table" "PTRV_UTIL_VPFPS_VPFPA_P" could not be activated
       3 EMC738XActivate view "V_T706S_EHP"
       1EEMC560 Field "T706S"-"D2100" does not exist
       1EEMC560 Field "T706S"-"EXCHANGE_DATE" does not exist
       1EEMC560 Field "T706S"-"TRIP_BREAK_CNTRY" does not exist
       3 EMC742 View "V_T706S_EHP" was not activated
    1EEDO519 "View" "V_T706S_EHP" could not be activated
       3 EDT014XActivate dependent table "/MRSS/T_CUP_OBJECT"
       1EEDT242 Field "FIELD_DESCRIPTIONS": Component type or domain used not active or does not exist
       2WEDT183 Field "INSTANCE"-"/MRSS/IF_CUP_OBJECTS": Reference type used is not active
       1EEDT005 Nametab for table "/MRSS/T_CUP_OBJECT" cannot be generated
       3 EDT015 Dependent table "/MRSS/T_CUP_OBJECT" was not activated
    1EEDO519 "Table" "/MRSS/T_CUP_OBJECT" could not be activated
       3 EDT014XActivate dependent table "T706S"
       1EEDT963 Field "TRIP_BREAK" in table "T706S" is specified twice. Please check
       3 EDT015 Dependent table "T706S" was not activated
    1EEDO519 "Table" "T706S" could not be activated
    1 ETP111 exit code           : "8"
    SAPA702EPU.SID
    ent tables)
    2WEDO549 "View" "V_TWGVALE" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWH01" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0100" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0200" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0250" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0260" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF501" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF600" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF8003" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWLOF" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWMWQ" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWPC_COLHEAD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWPC_COLHEAD_C" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWRF2" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWSD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWTFMA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWZLA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TXW_AD01D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZB0W" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZB6D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZBABG" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZBABGZB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZD0B" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZD0BI" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZD0BW" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZE02" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZE03D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZONE_M" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZPAB3" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZT01" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZT01D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZV04" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_UEBER" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_USCOMP" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_USCOMPA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_USR_NAME" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VGNVA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VGNWA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_BUK" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GE" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GFL" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GR" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GRA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_WE" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIOB01" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIOB02" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIOB03" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VITXT" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VLBLTD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VLTD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VTDST" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VTSPLS" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WBEW" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WCUSDOC_RELA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WITH_CTNCOT005" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFBA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFBB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFKC" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFRA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFRB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFZA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFZB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFZUC10" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRBLA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRGLA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRGLB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRLBA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRSZ" was activated (warning for the dependent tables)
    2WEDO549 "View" "WB2_V_VBRK_WBGT" was activated (warning for the dependent tables)
    2WEDO549 "View" "WB2_V_WBRK_WBRP" was activated (warning for the dependent tables)
    2WEDO549 "View" "WB2_V_WBRK_WBRP2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVAP" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVHE" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVITX" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVJ" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVM1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVN1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO3" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO4" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO5" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO6" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO7" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO8" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO9" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOA" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOC" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOD" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVODX" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOE" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOF" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOI" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP0" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP3" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP4" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP5" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP6" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP7" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP8" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVPN1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVPU1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVW" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVWA1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVWA2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVZ1" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWM_VSNACH_LIKP" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_DLR_BR" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_DLR_PROOR" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_EMGAR_DC" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_USR_DISTR" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_WORKBY" was activated (warning for the dependent tables)
    2WEDO549 "View" "ZZLIB_V_HKTK" was activated (warning for the dependent tables)
    2WEDO549 "View" "ZZLIB_V_LIFNR_C" was activated (warning for the dependent tables)
    1 ED0301X*************************************************************************
    1 ED0306       "Final log"
    1 ED0322 End phase  "006" ***********************************************************
    1 ED0320XStart phase "007" **********************************************************
    1 ED0306       "Statistics on Activated and Deleted Objects"
    1 ED0301 *************************************************************************
    1 EDO601XNumber of objects to be activated............:  "35325"
    1 EDO605 Objects not activated........................:  "4"
    1 EDO606 Activated objects with errors in dependencies:  "4"
    1 EDO604 Objects activated with warning...............:  "5531"
    1 EDO603 Successfully activated objects...............:  "29786"
    1 EDO602 Number of objects to be deleted..............:  "128"
    1 EDO608 Objects not successfully deleted.............:  "0"
    1 EDO607 Successfully deleted objects.................:  "128"
    1 EDO609 Tables/views with DROP/CREATE................:  "0"
    1 EDO610 No. of them marked for DROP/CREATE: "0"
    1 EDO611 Not marked for DROP/CREATE: "0"
    1 EDO620 Number of nametabs to be deleted.............:  "0"
    1 EDO622 Successfully deleted nametabs................:  "0"
    1 EDO621 Nametabs that were not successfully deleted..:  "0"
    1 ED0301X*************************************************************************
    1 ED0306       "Statistics on Activated and Deleted Objects"
    1 ED0322 End phase  "007" ***********************************************************
    1 ED0302X=========================================================================
    1 ED0314 Mass Activation
    1 ED0302 =========================================================================
    1 ED0327 Process..................: "defnsv1466_14_59636"
    1 ED0319 Return code..............: "8"
    1 ED0313 Phase 001..................: 00:00:13 (Take Over Switch-Dependent Objects)
    1 ED0314 Phase 002..................: < 1 sec. (Deletion of objects: 1th call)
    1 ED0314 Phase 003..................: 00:00:47 (Berechnung der Abhängigen:)
    1 ED0313 Phase 004..................: 00:15:00 (Object Activation)
    1 ED0314 Phase 005..................: < 1 sec. (Puffer Sync für Abhängige refTo ...)
    1 ED0314 Phase 006..................: < 1 sec. (Final log)
    1 ED0314 Phase 007..................: < 1 sec. (Statistics on Activated and ...)
    1 ED0309 Program runtime..........: "00:16:01"
    1 ED0305 Date, time...............: "01.08.2014", "09:23:55"
    1 ED0318 Program end==============================================================
    1 ETP155 ACTIVATION OF DD-OBJECTS
    1 ETP110 end date and time   : "20140801092355"
    1 ETP111 exit code           : "8"
    1 ETP199 ######################################
    4 EPU202XEND OF SECTION BEING ANALYZED END OF ACT_UPG =====================================================
    Please suggest.
    Regards,
    Alok

    Hi Divyanshu,
    thanks for your prompt reply,
    As per the error occurred, PTRV_UTIL_VPFPS_VPFPA_P is the table but when I check in SE16 its saying PTRV_UTIL_VPFPS_VPFPA_P not a table its a STRUCTURE
    In SE11 its saying "PTRV_UTIL_VPFPS_VPFPA_ "does not exist.Check name.
    Here it is not taking full name of table "PTRV_UTIL_VPFPS_VPFPA_P".
    Pl suggest.
    BR,
    Alok

  • 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...

Maybe you are looking for