Lumetri in PPro

CC2014
Why does the application of  Lumetri>Sony FS700.itx  have the effect of flattening the image.  Seems to be back to front of what is expected and required for S-Log or any other footage.
dot itx  is the Iridas LUT  I believe.

Came to post the same thing. NEAT Video's de-noise plug in for After Effects was the cause of my problem as well. Odd, because I had the de-noise plugin installed before using any of the Lumetri Looks filters. I tried to shoot a night scene, saw how noisy it was, brushed of NEAT video and tried to de-noise it, didn't like the results, and then decided to just shoot in Daylight and use Lumetri for that nighttime look-and-feel.
So, NEAT was installed and working when I also had Lumetri working. But when I opened up the project today, I saw Lumetri Day4Night wasn't working at all, not even in the preview picture of the side-profile head in the Effects bin. Deleted NEAT (even though it was the AE version, and I'm using PP CC), restarted PP CC, and Day4Night was back to working fine.

Similar Messages

  • Lumetri Looks look very different between SG and PPro

    Trying to create Looks in SG and use them as an effect directly appled to a clip(s) in PPro.  Works just fine except what you see in SG is vastly different than what you get in PPro, color-wise.  The clips are 8 bit HDV so some banding issues can occur-to be expected if I 'push' to far.  But this is really different, i.e. what appears grayish in SG is really yellowish in PPro, colors very different.  Any ideas?

    First off there is a bug in the print dialog box with regards to the " proof" profile name and color preview. Make sure that if you change the proof set-up profile you also have to go to the proof set-up portion in the print dialog and re select the " current custom set-up" profile. This bug is completely adding to the confusing complexity of the print dialog box and is clearly in dire need of a complete overhaul.
    Make sure the "match print colors" is checked as well to display the correct output to your device.
    To answer your question...
    >How can I get the workspace preview to match the Print dialog preview (which matches the printout better)?
    In the proof set-up select the profile you want to apply in the " device to simulate" drop down. Select the rendering intent and if you want BPC as well. Make sure you select " Simulate paper color". Observe the preview and click OK.
    Go to the print dialog and select " Photoshop manages color" - select your custom printer profile as well as applying the same rendering intent that you selected in the proof set-up - and if you are using BPC as well. Again, make sure you have "match print colors" checked. Also make sure you are not managing color in the printer driver as this will just double manage color and makes things more confusing.
    Your working space preview in proof set up mode and your print dialog preview should match now - if not, go complain to Adobe about the retarded print features they offer...
    As far as I'm concerned, they are completely lost in development as of now.

  • Lumetri effect not working after 7.2.1 update

    The Lumetri effects applied to past sequences show up as Checkered patterns in the preview, when relinking the presets to the LUT when they are applied to a clip in a timeline the timeline freezes and displays black.  Basically all my prior sequences to 7.2.1 are non usable, Any thoughts?

    Don't know that it's connected ... but in the last "update" something somehow changed so that if I apply a LUT or Look in Sg that isn't already ALSO in the PPro Lumetri-effects folder, PPro can't 'see' that section of clip. Got the ol' red checker-board thing.
    Tried it with a couple other "looks" and yep ... they have to be in BOTH PPro and Sg program folder-trees or it's broken. Before ... anything I did in Sg showed up in PPRo without problem, and clearly ... a decent numbe of the LUT's and looks I'd used were only in Sg's folder-tree.
    So ... yea, got to learn where those two trees are and sort through copy/pasting everything in the Sg one into the PPro one. I'd asked a question of whether they also need now to be copied to Ae, got no answer from anyone. I guess I'll find that out later in the week when I get over there again.
    You'd think the "common folder" thing, used for quite a bunch of things by Adobe, would be the "natural" home for cross-program shared "tools", wouldn't you?
    Neil

  • Mask from Speedgrade via lumetri  in PProCC Bug?

    I create a mask in Speedgrade and want to use it in PProCC via Effects/Colorcorrect/ Lumetri.
    As long as the mask is inside the picturesize (speeedgrade) all is ok.
    As soon as the outer line from the mask mask goes outside the picture(speedgrade), the mask as an artefakt in PProCc on the left side.
    bg
    alex

    Thanks Dennis,
    Yes works now,
    just let you know that we had to upgrade both  Speedgrade and PPro.(checked on another worstation)
    Won`t upgrade PPro on currenttly workstation, because we are middle in a project.
    bg
    alex

  • Missing Lumetri filter in PP CC after upgrading to 7.1.0 (141)

    I have had some problem with the upgrade last week.
    I installed the upgrade, but after that my Multicam stopped working properly.
    I wanted to uninstall the upgrade since I still had a project to finish.
    The only way to do that was to use the Windows Restore points.
    However now I have a problem with my Lumetri filter.
    It does not show up in the effects anymore, and my existing projects show the following message in a pop-up :
    \\?\D:\BMPCC - Test\Untitled.prproj
    Video Filter missing:  AE.ADBE Lumetri
    The //?/ Could indicate that there is something wrong with the path, but I am not using any paths. Everything is on the local drives.
    The other thing is that the prefix is AE indicating After Effect, rather than Premiere Pro.
    I have tried a full uninstall of all Adobe products, use the CC Cleaner to remove any remnants, and re-install, but stil the same problem.
    Has anyone had a similar issue or have any clues on how to fix this issue.
    Thanks,
    Richard

    After chatting with Adobe Tech Support they directed me to uninstall again and install PP 7.0 via a download from their server.
    That solved the problem.
    Richard

  • Metadata issue in PPro - UserClipName populates in Metadata and won't go away

    I have P2 footage that is behaving oddly in PP - PPro CS6.  I am on a PC, using Windows 7 Professional.
    Footage was shot and archived onto our PC last summer - as is our typical process - and a PP project was started. It was left dormant till now - 6 months later.  I am the new editor tasked with finishing this edit. 
    I began by organizing assets in the project and then reviewing all files to identify what I have to work with - this step includes logging info into the metadata (as I typically do).  I noticed that the UserClipName was appearing in the SHOT metadata item - I wanted to use SHOT for the Shot number, so I replaced the UserClipName that was in that field with the Shot Number, and I made other additions to the Metadata in the appropriate fields.  I saved the project often during this process.  I closed the project.  I then tried to open another project in PP and nothing opened.  I tried to open just the program, and nothing opened.  I then logged out of my user account, and then re-logged in.  I tried to open PP and it opened fine.
    I opened other PP projects to see if I could see the UserClipName in the SHOT item (or anywhere) in the Metadata window - and I did not see it.  I also did some test changes to the metadata to see if I could replicate the same issue with the program not opening - changed metadata, save, close - and no problems with opening PP.  I created a new project in PP for the above footage in question, imported it, and there was the UserClipNames in the SHOT metadata field.  I did not change any metadata - just saved and closed, and was able to reopen PP.  I then tried to add data to the Metadata, save and close - I was not able to reopen PP.
    I have imported this footage in various ways - thru the media browser; click and drag from finder window; double click from within the Projects panel then browse to the files; using cntrl-I - and each of these methods was with a clean (new) project.  No love.
    I also tried to convert this footage directly in Encoder as well as through Prelude (which just takes it to Encoder) into three different formats - P2; Quicktime; H.264 - then created new projects in PP. No love.
    What I know is that I can work in the project fine (as far as I can tell so far) as long as I do not touch any metadata.  That is a bummer for me - but, oh well.  But the fact that this issue exists concerns me -I have no assurances that I will I be able to complete this edit successfully.  Fortunately it is only a short PSA, ... and for extra help, I will make my offerings to the Edit-Gods to help get me through to the end without any further issues. 
    I would love to hear if anyone out here has any suggestions on what might be going on - and ideally a solution.  I am okay with appeasing the Edit-Gods - but I would prefer to have more solid solution.
    Sali

    Hi Sali,
    I began by organizing assets in the project and then reviewing all files to identify what I have to work with - this step includes logging info into the metadata (as I typically do).  I noticed that the UserClipName was appearing in the SHOT metadata item - I wanted to use SHOT for the Shot number, so I replaced the UserClipName that was in that field with the Shot Number, and I made other additions to the Metadata in the appropriate fields.  I saved the project often during this process.  I closed the project.  I then tried to open another project in PP and nothing opened.  I tried to open just the program, and nothing opened.  I then logged out of my user account, and then re-logged in.  I tried to open PP and it opened fine.
    Thanks for your post.
    Let me see if I understand you. You say that the text string, "UserClipName" was in the "Shot" metadata field. By replacing that text string with the a shot number in the Shot metadata you began to have unexpected behavior, such as, not being able to reopen a project. Logging out of your user account, then logging back in allowed you to then open the project. Is that correct? That's pretty odd, for sure.
    I opened other PP projects to see if I could see the UserClipName in the SHOT item (or anywhere) in the Metadata window - and I did not see it.  I also did some test changes to the metadata to see if I could replicate the same issue with the program not opening - changed metadata, save, close - and no problems with opening PP.
    Sounds like you have hit a bug with P2 footage and Premiere Pro CS6. There is a closed bug in our database, but the state may been triggered with subsequent changes to your system, or the like. The bug also may not have been completely fixed with your particular kind of P2 media.
    As I understand it, the issue has to do with how XMP metadata is interpreted by Premiere Pro. I do not believe there is a workaround for this issue other than not changing that particular metadata field. Perhaps you can use a different field, like Comment or Description, for shot number.
    What I know is that I can work in the project fine (as far as I can tell so far) as long as I do not touch any metadata.  That is a bummer for me - but, oh well.  But the fact that this issue exists concerns me -I have no assurances that I will I be able to complete this edit successfully. 
    I really hope you can get through this project. Let us know if you hit any more issues along the way.
    Thanks,
    Kevin

  • Dynamic link confusing two separate AE compositions in PPro from different projects

    I am using CS5 Master Collection for Windows 7 (64 bit) on an HP Pro desktop (Intel core 2 duo, 6Gb RAM). The tower has two hard drives installed (no RAID). CS5 is installed on the original C drive along with the OS, but the working files, footage etc are all on the larger, secondary F drive.
    I am working on a DVD project consisting of several seperate PPro projects. Each project has been colour corrected in AE using dynamic linking. Recently two of my projects suddenly became mixed up, by which I mean the video (not the audio) from one AE composition in one project has taken the place of another in another project. The clip remains the same length, but the link apears to be referencing the wrong clip during playback. Interestingly, there are two clips on the track above the affected clip that fade out and in at either end, during the dissolves between clips, the correct footage plays. It is only when the clip plays by itself that the problem occurs. The next clip also has the same error, though the problem only occurs for half the clip and then suddenly corrects itself. Just to be clear, All clips have been rendered, there are no more than two video tracks on the sequence, and I have tried replacing the composition from the asset menu (in which the clip plays back correctly), but the problem remains in the sequence.
    I hope that descrition is clear enough. My guess is some kind of file path error in the dynamic link, perhaps due to the separate hard drive. But I really wouldn't know. I'm very pressed for time right now and I'd prefer not to go against workflow and re-edit a new composition in AE, I would also like to understand what is going on in case it happens again.
    Any help with ths problem would be appreciated,
    J

    Thanks Colin, I tried what you suggested with both the AE Project that it should be referencing and the AE project it is erroneously referencing but both failed to fix the issue. Its as if a hidden clip were laid over the top of the one I want to play. Frustrating.
    Date: Mon, 24 Oct 2011 19:47:03 -0600
    From: [email protected]
    To: [email protected]
    Subject: Dynamic link confusing two separate AE compositions in PPro from different projects
        Re: Dynamic link confusing two separate AE compositions in PPro from different projects
        created by Colin Brougham in Premiere Pro CS5 & CS5.5 - View the full discussion
    It's not the comps that are the problem; it's the project file names themselves. You can have all the comps in a project named the same thing, and it'll be fine, but naming projects incrementally is an issue. After Effects includes a versioning function (Save and Increment) that will create a new AE project file with a serial number, e.g. AE Project 01, AE Project 02, etc. This is all well and good if you're just working in After Effects, but Dynamic Link gets confused and will usually start looking at the later project file for comps. That will just create a big mess, as you've found. Changing the names of the project files won't help things relink automatically properly, but it can help you fix things. Make all your DL AE comps offline in your Pr projects, and name your AE projects in a manner that is not serial (give them more random names). Select your offline AE comps, and right-click > Link Media, and point to the new AE project. Things should link up correctly then--but if they don't, you'll just have to remove all the AE comps from your Pr project, reimport the comps from the newly-named AE project, and replace them. It's a pain but it'll probably just keep getting worse if you don't.
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/3988711#3988711
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/3988711#3988711. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Premiere Pro CS5 & CS5.5 by email or at Adobe Forums
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • How to import 12 different PPro files into one Encore file to make DVD

    I'm trying to create a DVD with 12 different lessons on it.  I have created 12 Premiere Pro CS4 files (each is a slideshow lessons with narration) and I want to bring them all into one Encore file.  I can send one file to Encore via Dynamic Link - but when I open another PPro file and try to send it to the same Encore folder - it erases the file I put in there previously.  Maybe I'm going about this all wrong - I really don't know.  Please Help.

    Hi Stan,
    Thanks for the reply.
    Since I wanted to get the DVD finished asap - I jumped right into PPro CS4 without going through a learning process first.
    When I said "file" I meant one of the 12 or 13 different PPro projects that I saved to my Desktop...each lesson is different - so I made and saved each lesson separately and placed each of them in a different folder.  Each lesson only has one "sequence" (and I'm not sure what "sequence" means yet).
    These are basically PowerPoint lessons with narration - each lesson containing anywhere from 25-75 pictures or text slides.
    When I opened up one of the lessons in PPro and sent it via DL to Encore - that was fine.  It created an Encore file.  When I opened up the next PPro file and tried to DL to that same Encore file - it appeared to delete or do away with the first file I had sent there.  I could DL each of the 12 or 13 files - but only to its own Encore file.  I couldn't figure out how to get them all into the same Encore file.  But thanks to all the help on this forum - there are now 13 little videos that I can import into the same Encore file.  And that's amazing.
    Thanks for the encouraging words that this project might all fit on the same DVD (I was worred because the files add up to 107 minutes - and I the DVD holds 120 minutes (I think).  I was assuming that after I created a menu and added a picture for the background in the title page, etc., that it would all add up to too much information for one DVD).
    I'll let you know how the DVD turns out.
    Thank you very much.
    ph

  • How to set up a server for PPro editing (and AE finishing)?

    Hello everyone,
    I may be a bit offtopic with this question, but at the same time it's really related to PPro.
    I never worked in any post-house facility, and I come from a very indy background, so I never had a chance to see any edit suite hook up to a server.
    I am wondering how great it is, how it could help our projects? And also what are the basics to know, the stuff to avoid when you're a newbie like me (in term of server network settings)?
    Right now, we're running 3 Mac Pros to edit our projects. They are all connected through Gigabit ethernet.
    Our workflow involves that all Mac have the entire footage in there own drives. We're using the network only when importing new content to copy it on the 2 other Machines.
    We found out that if we use Mac #1 to open a PPro project contained within Mac #2 drives (as well as the footage), it's okay but the performances are not as great as opening a project in its own drives.
    So we try to copy (move) the projects in the right Mac before to work on it. Of course, everytime, we have to relink everything if we don't want Mac #1 to read the footage from Mac #2…
    When it come to big projects, with lots of Red footage, it is a pain, and we usually end up using only one master machine for the edit, and it's only when it comes to finish in AE that we really start to split the project onto the 3 platforms.
    So this is where the idea of a server comes in mind. Mac #1 would work on a project A, then when moving to work on project B, Mac #2 could open project A and keep working on it - no relink: the project AND the footage are all on the server.
    That is my basic idea. Sound simple, but really I have no idea if it really works. Is it something I can really do on a server?
    How the server really helps to keep the performance? If I see PPro's performance lowering down when accessing projects and footage from our actual simple network, is it going to be better accessing the same datas from a dedicated server.
    I'm looking at the Mac Mini server with Lion Server. What Lion Server does that Lion OS doesn't do already?
    I know, it sounds like completely newbie questions, but I honestly have no idea.
    Can a Mac Mini with Lion Server serve the 3 Macs running Snow leopard? Or do we need to update them?
    My idea is to use Pegasus thunderbolts for storage drives, plugged in the Mac Mini, then plug all the 3 Mac into the Mac Mini, with what I believe should be Gigabit Ethernet…
    Am I right? A least a bit? What did I miss?
    Thanks in advance for sharing your knowledge guys
    Julien

    If you are going DIY route, this is your only option: http://magazine.creativecow.net/article/build-your-own-affordable-san-that-iworksi
    However that probably won't work with RED footage.

  • PPro engine for video playback question

    Joe mentioned in another thread that Encore 2.0 uses "PPro engine ... for video playback, instead of DirectShow". Does this imply that Encore DVD requires a CPU with the SSE2 instruction set like PPro does? Thanks.

    Yes.

  • Export video with Lumetri effects - 2 to 3 videos render fine, after that flickering, colored frames

    After I spent 45 minutes waiting to be transferred to to right department with the support chat, only to find out technical support isn't available during the hours I called, I am going to try this outlet to get some advice:
    I have about 50 video files to export, each 20 seconds to 2 minutes long. They all have Lumetri effects on them (I suppose that's what causes the problem).
    I can render 2, maybe 3 videos without problems. The next one might be fine for a while, but then all I get is strobelight frames, flickering, and different color frames. One time I even received a blue screen of death. I restart Media Encoder, add files to the queue, same thing happens. 2 - 3 will work, after that it exports garbage.
    I am using Premiere Pro CC to edit the video, Media Encoder CC to export it.
    The original footage is HDV 50i - 1440 px by 1080px - 1.333 pixelr ratio.
    Besides some dip to black and cross transitions the only other effect is a title layer with some static color effects on it, and 2 Lumetri effects (warm midtones and dream 1).
    I thought at first maybe it is because I encode in FLV, 1800 mbps, but also when I used uncomressed AVI with the same settings as the original footage the same problem occured.
    I have two ATI radeon HD 6950s 1GB in my pc hooked together with cross fire, 16GB ram, the project file is on a SSD, the raw footage on a HDD. AMD Phenom II x4 processor with 3.4 GHz.
    OS: Windows 7 64bit.
    I did update to the latest GPU driver last night - that didnt fix the problem.
    Since I noticed the fans becoming quite loud during rendering, I did put two Ice packs from the freezer on top of the case and pulled it away from the wall a little bit to allow for better cooling (and it did stay a lot cooler with the ice packs).
    I do also get funky looking frames inside Adobe Premiere after trying to watch the footage with the Lumetri filter for a while. I'll have to restart the program and it'll work fine.
    Any suggestions what I could do? Settings, or something? I dont want to attend to my machiene for so many hours, importing 2 video files at a time, having to review each of them for errors. I'd rather set it up once, and let them all render...

    @Peter Garaway:
    Thanks for the response.
    I use two Lumetri effects:
    Warm Midtones
    Dream 1
    Both applied directly to the clip of raw footage which is in the sequence that gets exported. There is actually one sequence, where I fixed some of the footage putting it into another sequence first, then the sequence into the final sequence that gets exported.
    All my clips have both Lumetri effects applied to them. The flickering took place randomly, but it would definitely get worse the more I attempted to render (the first 2 to 3 no problems, on the 3rd or 4th maybe a few flicker seconds in the middle, any more would be 100% flickering - if any flickering or only like a green solid...)
    Now Shrishti from tech support insisted the problem was within the sequence. And that kind of made sense, because once we successfully rendered one sequence, there would be no more trouble rendering it a second time, even if the program was already in flicker mode. And also for some reason while we were playing around with it when one sequence failed, even after restarting Media Encoder, it would fail again afterwards.
    However last night after it failed I would just try again, doing 2 at a time and it would be successful.
    Now I say it failed, but of course no errors no nothing... Just as in the result didn't look the way it was supposed to.
    Also I want to mention that especially when I kept it running after it failed (meaning you leave it runnning, producing only garbage) the fans of my computer kept running louder and louder. Not sure if it was the GPU or CPU. Rigth now it keeps rendering in Software mode and the fans are barely louder than under normal usage.
    I use the AMD catalyst driver which I downloaded from here:
    http://support.amd.com/us/gpudownload/windows/Pages/radeonaiw_win8-64.aspx
    While Shrishti was trying a couple of different settings at one time the screen went dark, as it came back on there was a message coming from the windows tray, saying the display driver had crashed, but recovered. One time I also received a bluescreen message, which I will try to attach to this post.
    well i guess it doesnt have too much information on there other than... what is that? a memory address?
    This happened I believe after the first attempt with the updated driver (I updated from 13.3 to 13.4 )

  • Ppcs5 on win 7 (64bit)  runtime error message when starting PPRO

    Just installed cs5 on a dell win 7 64bit machine, and when I start ppro cs5 I get an error message that says "Runtime Error!.... this application has requested the Runtime to terminate it in an unusal way...
    On a different machine (win 7 (64 bit), I don't get the error message.  Anyone else experience this issue and know how to resolve... is it an Adobe problem or a Microsoft problem?

    Did you got any error while installation ?
    Please right click and launch Premiere as an administrator ...

  • Lack of Capture Preview in PPro CS5 Using A/D Blackmagic Multibridge Eclipse

    Hi all,
    Intersting issue here...just purchased and  configured a new Blackmagic Multibridge Eclipse I/O box.  SO far so good  in terms of up/down conversion etc., but having a bit of an issue  establishing a connection with our Sony PVW-2800 Betacam Deck.  I have  gone through the Blackmagic manual etc. and we have all of our settings  adjusted correctly in PPro and do get an auditory/visual preview on our  true-color LCD monitor/external audio mixer.  It is hte lack of visual  in the PPRo capture window that is the problem.  Remote deck control is  funcitoning fine, and we are able to click the red record button and the  timecode does start rolling, but when record is stopped, no clip pops  into the set project bin.
    What am I missing here?  Device Control is set to Blackmagic, format is NTSC 4:3 and DV.  Let me  know if you need any more specifications.  Maybe this is still a  Blackmagic problem...but with some trial/error it seems to point to  PPro.  We are able to succesfully capture using Blackmagic Express.
    Thanks for the feedback,
    Lindsay

    What do you have the input in the Blackmagic control panel in windows control panel set to? Is it set to SDI, Component, HDMI, Y/C, or Svideo?
    Eric
    ADK

  • List of problems in PPRO CC 2014 I've encountered

    Suggested by Adobe Care to post here.
    Issues in PPRO
    -General encoder issues where a render will stop part way through without a detailed description of whats happened.
    -Play head in the timeline becomes unstable when scrolling with the mouse - timeline bounces around when zooming in.
    -Red flash frames have been appearing when using the multi cam feature. Clearing the cache does nothing and restarting computer/PPro fixes for a short moment but the red flash frames always come back. The red frames appear in the render as well if rendering straight out of PPRO. Ways to counter the red flash frame is to import the sequence into AME and render that way.
    -PPRO occasionally believes a file is frozen and will not play it properly or render it out. source file is fine and plays without a problem and even renders/encodes no problems when put into AME. Even if you remove the file from PPRO and then relink it, PPRO still believes that the file is frozen/unplayable. The work around is to transcode the file in AME to something else and replace the source file in PPRO.
    -When zooming into the timeline the green audio waveform often disappears and then comes back after a moment. Bit difficult to pin point a specific beat to cut when the waveform is gone.
    -Using masks with multiple effects for one video file will often cause the program viewer to make the video appear as though it has shifted partially off the screen to the right and down. Turning off the effects will bring the video back into the center of the program viewer.    
    -Can no longer copy or move multiple files in multiple bin at the same time. Previously I could select a file in 'BIN A' and a different file in 'BIN B' at the same time and move them together to 'BIN C' but now I have to moves each file individually.
    -Importing bulk R3D or MXF folders with spanned clips no longer registers that the clips are spanned which means there are lots of extra folders with multiple duplicate clips getting imported. There is a work around where you can import the spanned clips properly but involves individually importing only one target folder at a time. Which is incredibly time consuming when you have a very large number of folders all with spanned R3Ds. Previous versions of CC prior to 2014 allowed bulk importing of spanned clips via the top folder had zero issues.
    Issue in AE/AME
    I have also encountered a strange issue when exporting a video using AME which was added from AE.
    -I rendered a file from PPRO using AME which had zero issues - no flash frames. Imported it into AE and ran some Noise reduction over it and then added it to the media encoder so I could encode it as H.264 -  The project in AE with NR had no flash frames. Once AME was finished with the render I played back the newly created file and noticed a flash frame where a single frame of video from the 5 min mark had been dropped right into another part of the video 7 mins down the line. The AE project had one file in the timeline and on further inspection did not have any random single frames floating around which would have caused the issue.
    Cheers,
    James

    Hi Kevin thank for replying,
    The projects have all been built brand new in the most recent versions of PPRO and AE.
    PC
    i7 3930K
    Windows 8.1
    32GB Ram
    GTX 580 3GB
    A lot of HDD space available
    Premiere Pro CC 8.1 All abode software is up to date according to the Creative Cloud manager
    Nvidia drivers up to date
    -Source footage mainly Canon XF300 MXF 1080P footage, R3Ds when running into batch import spanned clips issue occasional DSLR Canon footage.
    -Error messages -  Error compiling movie - Mostly has had to do with PPRO thinking a clip is frozen as mentioned in the post above but has also occurred recently when exporting a project conststing of MXF and DSLR footage colour graded with colorista all running with in a multicam setup.
    -Errors are generally sporadic in nature but PPRO freezing has become more constant with each update.
    - Most of my issues are during editing, some of which have been detailed in previous post.
    -3rd Party plugins for PPRO - Colorista and twitch from video copilot. both of which have been updated this year for CC 2014. AE has trapcode, a waveform plugin and other Video Copilot plugins installed, Trapcode was only installed a couple of days ago, after the recent issues.
    -Avid codec pack is installed for DNXHD encoding
    -Errors happening while editing, and on export.
    Dont have any videos or screenshot examples.
    If you need anymore clarification let me know, basically what I want to know is if uninstalling and re installing PPRO and AE is my only option or if there is a standard reset and reconfigure scenario I can look at doing. I suspect the batch importing issue along with the inability to grab multiple files from different bins at the same time is potentially a missing feature issue while the rest are bugs. 
    Once again thanks for getting back to me.
    Cheers,
    James

  • FCP 6 XML file has inexplicable failure to open in PPro CC.

    Hello,
    I'm trying to open an XML from FCP6 and I keep getting the often mentoned "This project appears to be damaged, it cannot be opened".
    Now the odd thing about this, was that it was actually just a trial run as a colleague has not got time to learn PPro and is still larking around with FCP. We are trying to become familiar with how we shall cope with XDCAM media. FCP will have to encode the media into a form that FCP can read. He is using XDCAM Transfer from within FCP.
    I wanted to check how I will have to relink the media to my non-encoded XDCAM media. (The answer to this question is simple, but frustrating - I have to re-link it manually - I think)
    So I gave him one XDCAM file, with its standard file structure and asked him to make a single sequence with one or two cuts. Then to export a version 4 XML.
    Nothing we do will make this blasted XML file work. He has provided me with three different XML files. None of them work.
    However, when I boot up an old HD, with FCP6 on it and use the same XDCAM media, I can export a version 4 XML that opens in PPro CC without problem.
    So where is this annoying problem occuring?
    I have even read through 80 to 100 lines to the XML to see what difference there are. I can't be bothered to look further.
    Hope someone can help.
    Thanks,
    Anthony @ Antimatter Films

    Might be faster for him to learn PP after all.
    http://www.adobe.com/products/premiere/for-final-cut-pro-users.html

Maybe you are looking for