Final Cut Pro X / Compressor problem

Hi, I have a Panasonic HDC-SDT750 and have imported a video to Final Cut Pro X 10.0.5
I have sent the video to Compressor 4.04 and used presets for apple tv 3G - 1080p
Everything went fine except that some parts of the .m4v are like these very bad YouTube videos where you cannot see anyhting, like
theres some fog over the picture.
Can anybody help me, please?

Export to media and look at the file. Is it OK?
Can you answer this please?
Your original media is 720p and you're blowing it up to 1080p? Don't do that.

Similar Messages

  • Urgent! Help, how to deal with m2ts file in Final Cut Pro or Compressor...

    Dear All:
    Please help me solve this urgent issue, I've got source that came with the mpeg-2 Transport Stream (48min content @ 3.42GB size) format , but both my Final Cut 6.0.6 and Compressor 3.0.5 can not open this type of file, is there any way that I can transcode this m2-ts file into a Final Cut Pro and Compressor readable format with the highest quality possible? And how to do it?
    Thanks in advance.
    Kevin
    Message was edited by: Kev C

    hey, Thanks David, actually, I used MPEG Streamclip prior to post this massage, the problem is that my
    MPEG Streamclip 1.9.2 can't correctly open this m2ts file (it says it can not read the file size...) and I also tried using VLC to transcode it, but with no luck, I can not find the right video and audio format to come out with QT playalbe file. Let me try ClipWarp to see if it works.
    Kevin

  • When sending job from Final Cut Pro to Compressor using local QCluster

    When sending job from Final Cut Pro to Compressor by way of Share and using the local QCluster, the audio renders, but the video errors out saying something along the lines of Can not locate file.
    If I use 'This Computer' it works fine.
    What gives?
    Fresh install of OS and FCS.
    Thanks!

    I'm just learning the intricacies of Compressor and Qmaster myself, but I have learned that when you use Qmaster you can not share directly from FCP. You must export a Quicktime movie (reference movie seems to be fine) and input that to Compressor. This is only an issue when using Qmaster, as you've seen.

  • Final cut pro to compressor

    Hi, I am having trouble exporting a sequence from Final Cut Pro to compressor. When I export, FCP creates a new bizzarely named project, and generates an alert that "A file of that name already exists". Compressor then opens and appears normal, except that the preview window isn't able to show anything because "Final Cut Pro is busy". I then submit the batch and it promptly fails because of an error generated by FCP. What is going on? Someone help.

    Try this: Select your sequence in the FCP browser; then choose File/Export Using Compressor. Compressor will open, choose your settings and destination, and hit submit. Batch Monitor will then open, and you can monitor your progress.
    It sounds like Compressor doesn't know which file you are trying to have it export.

  • Failed to send my project in final cut pro to compressor

    I tried to send my project in final cut pro to compressor but when I go to file then see send to compressor it will not let me click on "send to compressor". I checked but none of my files are missing or anything and the project is only 4 minutes long. This has happened to me once before and it completely crashed my computer. I had to start out fresh which was a horrible process. CAN SOMEBODY PLEASE HELP?! (URGENT)What might I have done wrong that this happens? In the picture below, this happens and I have no idea why that is.

    I suspect it's a FCP X issue rather than a Compressor issue.
    Will FCP export a master file? Make a short section with the range tool and find out.
    Tri reseting the zoo's preferences. Hold down the option and command keys when you launch to reset.
    Russ

  • Problem exporting from final cut pro to compressor

    Hi,
    I'm trying to export to compressor from Final cut pro, but every time i do so, I keep getting the same error message 'Selection contains no media' but it does. It will export to Quicktime fine. I'm only trying to export to compressor so I can save it as an mp2 file.
    I'm using FCP V5.0.4
    Compressor V2.0.1
    Mac OS X V10.4.8
    Also on previous versions of FC I could output to Mp2 and it would include the chaper markers, my last sucessfull project, it did not.
    Any help would be greatfully recieved.
    G5 Single Processor 1.8   Mac OS X (10.4.8)  

    Philip:
    Check this old thread:
    http://discussions.apple.com/thread.jspa?messageID=1106846&#1106846
      Alberto

  • Final Cut Pro 7 & Compressor

    I am trying to complete a project which I recorded on a Sony EX1R HD Camera. For the purpose of this project, I had to shoot in SD Format, which put the files in a .avi wrapper. However I was able to import directly into Final Cut Pro 7 and edit as normal.
    When the editing was finished, I exported the quicktime movie from Final Cut and imported it into Compressor where I added the normal 90min SD DVD Pal setting.
    The problem that I am now experiencing is that as the DVD plays some of the scenes, the image jitters. I do not have any slow motion filters in the footage in Final Cut Pro.
    I have tried creating a couple of DVD's and the problem is still there, but not always on the same clips.
    Regards

    I'll wager it's the AVI format causing this... But a fix might be to export your sequence to a ProRes QT then compress... just use "file/export/QT movie, check on "self contained" and set the settings to be the same size and frame rate you're sequence is using, but set the compression to be using ProRes QuickTime instead of the AVI format it is.
    Jerry

  • Should I Render Video-Audio in Final Cut Pro or Compressor?

    The last time I read-up on this it was concluded I should trash/empty all my FCP project Audio/Video render files, then Export FCP>Compressor for best quality Mpeg2 and Audio compression.
    What is current, render both in FCP6 or trash all and let Compressor 3.0.5 do it all?
    Or it doesn't matter anymore?
    Basic workflow:
    Sony PD150, SD 4;3 into Final Cut Pro 6.0.5 Timeline.
    Work on video and audio filters for adjustments.
    Export to Compressor?
    I am then bringing the Best Quality 90 min MPEG-2 and DolbyDP2 into DVD Studio Pro.
    Thanks...

    I did it both ways and can't see any difference.
    The only reason I revisited the question is because my first, second and third MPEG2 runs through Compressor 3.05 (using both methods) looked like krap — very blotchy in areas and pixely halos around moving subjects.
    They were unusable (like Compressor 2x was) so I was worried.
    For some reason the problem cleared and it looks acceptable now.
    I don't think it makes any difference which method you use is my conclusion.

  • Final Cut Pro 7, Compressor, or Quicktime X do not recognize MobileMe

    I'm having issues uploading my movies from Final Cut Pro, Compressor, or Quicktime X to MobileMe. For both FCP and QT X, when I "Share" using MobileMe, it says that either my Username or Password is wrong. I know for a fact it's not because I can use them to login here or on iTunes. It worked before, but now after I did a Pro Application software update, it doesn't let me. I'm not certain that's the direct problem, though. When I try with Compressor, it just tells me it failed uploading.
    I tried using both "username" and "[email protected]"
    If I use "[email protected]" it says there is some sharing error which I never heard about.
    How can I fix this problem, or is anyone else also experiencing this bug?
    BTW, every thing else works fine.
    Thank you.

    Have you tried the full login including "@me.com or @mac.com"? This seems to work as far as FCP or compressor "recognizing" the MobileMe account. Yet when I do it through compressor, even though it says the job is done and all is well it never actually uploads it to MobileMe. It seems to work fine through FCP though.

  • Final Cut Pro X crash problem on export.

    Hello. Okay so I am running Final Cut Pro X Version 10.0.6 on a Late 2011 Macbook Pro 13-inch with 2.8 GHz Dual Core i7 processor, 4GB RAM. At the time of the export I am not running any other applications.
    I had begun exporting in 1080p HD with Apple Pro Res 422 (HQ) which kept repeatedly failing. However having lowered this to 720p HD with both 1280 x 720 and 920 x 720 resolution, and changing Apple Pro Res 422 (HQ) to H.264, I am still without luck on my export.
    The export runs for a while before completely freezing up and crashing Fina Cut Pro X entirely, at the moment it gets to around 41% before crashing.
    I get a report telling me that it crashed on Thread 26. Here is a copy of the Thread 26 crash in case anyone out there can understand this:
    Thread 26 Crashed:: com.apple.helium-render-queue-exec-unit-gpu
    0   com.apple.Motion.effect                 0x000000010ac03411 PCVector4<double>& PCMatrix44Tmpl<double>::transform<double>(PCVector2<double> const&, PCVector4<double>&) const + 13
    1   com.apple.Motion.effect                 0x000000010ac03388 bool PCMatrix44Tmpl<double>::transformRect<double>(PCRect<double> const&, PCRect<double>&) const + 352
    2   com.apple.Motion.effect                 0x000000010abf4d05 -[FFMotionEffect newImageAtTime:duration:withInputStream:context:downstreamPT:channelOffset:roi: ] + 885
    3   com.apple.Flexo                         0x0000000100796141 -[FFStreamVideoEffect newImageAtTimeIgnoringCache:duration:context:downstreamPT:roi:] + 1521
    4   com.apple.Flexo                         0x00000001007a3fdb -[FFStreamVideo newImageAtTime:duration:context:downstreamPT:roi:] + 779
    5   com.apple.Motion.effect                 0x000000010abf358e -[FFMotionEffect newNodeAtTime:duration:withInputStream:context:downstreamPT:outputPT:outputData :roi:] + 2852
    6   com.apple.Motion.effect                 0x000000010abf4b7b -[FFMotionEffect newImageAtTime:duration:withInputStream:context:downstreamPT:channelOffset:roi: ] + 491
    7   com.apple.Flexo                         0x0000000100796141 -[FFStreamVideoEffect newImageAtTimeIgnoringCache:duration:context:downstreamPT:roi:] + 1521
    8   com.apple.Flexo                         0x00000001007a3fdb -[FFStreamVideo newImageAtTime:duration:context:downstreamPT:roi:] + 779
    9   com.apple.Flexo                         0x0000000100738cae -[FFHeliumEffect newImageAtTime:duration:withInputStream:context:downstreamPT:channelOffset:roi: ] + 1422
    10  com.apple.Flexo                         0x0000000100796141 -[FFStreamVideoEffect newImageAtTimeIgnoringCache:duration:context:downstreamPT:roi:] + 1521
    11  com.apple.Flexo                         0x0000000100d2906b -[FFAnchoredObjectSegmentedVideoStream newImageAtTimeIgnoringCache:duration:context:downstreamPT:roi:] + 795
    12  com.apple.Flexo                         0x00000001007a3fdb -[FFStreamVideo newImageAtTime:duration:context:downstreamPT:roi:] + 779
    13  com.apple.Flexo                         0x00000001007a3fdb -[FFStreamVideo newImageAtTime:duration:context:downstreamPT:roi:] + 779
    14  com.apple.Flexo                         0x0000000100795ddd -[FFStreamVideoEffect newImageAtTimeIgnoringCache:duration:context:downstreamPT:roi:] + 653
    15  com.apple.Flexo                         0x0000000100d2906b -[FFAnchoredObjectSegmentedVideoStream newImageAtTimeIgnoringCache:duration:context:downstreamPT:roi:] + 795
    16  com.apple.Flexo                         0x00000001007a3fdb -[FFStreamVideo newImageAtTime:duration:context:downstreamPT:roi:] + 779
    17  com.apple.Flexo                         0x00000001007a3fdb -[FFStreamVideo newImageAtTime:duration:context:downstreamPT:roi:] + 779
    18  com.apple.Flexo                         0x0000000100af3a3b -[FFPlayerScheduledData customHGRenderQueueJobCallback:] + 2571
    19  com.apple.Flexo                         0x000000010073a754 -[FFHGAsyncCustomJob _runCallback:] + 148
    20  com.apple.Flexo                         0x000000010073ab87 customJobNotifyFunc(HGRenderJob*) + 119
    21  com.apple.Helium.HeliumRender           0x00000001030de3e6 HGRenderJob::CallNotifyFunc() + 54
    22  com.apple.Helium.HeliumRender           0x0000000102fdbf47 HGRenderExecUnit::RunLoop() + 231
    23  com.apple.Helium.HeliumRender           0x0000000102fdbe54 StartRenderExecUnitFunc(void*) + 20
    24  libsystem_c.dylib                       0x00007fff8e8477a2 _pthread_start + 327
    25  libsystem_c.dylib                       0x00007fff8e8341e1 thread_start + 13
    Can anyone please please help me solve this problem? This is highy urgent.
    Thanks in advance.

    It's Thread 21.  Focus on that and ask around about that crash. 

  • Final cut pro and compressor

    I have a FCP project that I have been working on for a year and have made DVD's from through compressor. Suddenly when I open compressor it states that there are no files associated with this project.
    Another user suggested I trash the preferences, but am loath to do this incase it makes things worse as I'm not very clued up on some of the systems functions.
    Please help
    CB

    If you've been on the project for more than a year, it must be legacy Final Cut Pro and not FCP X.
    This is the FCP X forum - you should ask this question in the Final Cut Studio forum:
    https://discussions.apple.com/community/professional_applications/final_cut_stud io
    Andy

  • Export a Final Cut Pro XML file problem about translation issue

    When I export the final cut pro xml file, there is always translation issue like that 'Transition <....> not translated, Cross Dissolve used instead.'
    Most of the transition type can cause the translation issues except the wipe and cross dissolve.
    Is there any body knowing the reason? Is that OK?
    By the way , I am using the trial version of cs5

    Hey Ani_,
    I've been working with Adobe products for a long time and typically when you come across an error that has anything to do with a XML file export problem its due to things such as effects you may have added in, color corrections, cross fades or any type of video transitions between clips. Remember your work flow should be
    Import your footage into Premiere Pro
    Name your clips (helps find things later on)
    Place clips on time line in the order you wish (ONLY MAKE CUTS don't add anything, transitions color effects nothing)
    Then once your clips are all placed on the timeline in your correct order you then EXPORT> Final Cut Pro XML
    Now you can bring this into other programs for color grading or whatever else your going to do.  You will notice you have no errors on the export.
    Once your done doing what your doing to the clips in another program (for example: Divinci Resolve color grading) you can then export them back to your main project then add your effects and transitions.

  • Final Cut Pro 'dropping frames' problem

    Hi. I have a macbook, version 10.6.8 - I am trying to use Final Cut Pro version 6.0.6 and am having problems with the 'dropping frames' issue. I know you can get rid of the message, but does anyone know how to solve the problem, as when it comes to exporting the film I won't be able to? Is my mac too small/old to use this version of FCP? If so, is there anything I can do to rectify that? (that doesn't involve buying a new mac!)
    Any suggestions would be great.
    Thanks.
    Vicki

    #12 Dropped frames on capture/playback
    Shane's Stock Answer #12:  Dropped frames on capture/playback
    http://docs.info.apple.com/article.html?artnum=58640
    1) Do not capture to your main system drive.  Since it is busy reading the operating system and application files, it will intermittently drop frames during capture.  Capture to a separate internal drive, or external hard drive (firewire and eSATA for example).
    2) Deactivate any anti-virus/filesaver software, including Norton and Virex.  For some reason these programs think that the large files created when you capture media are in fact caused by some sort of virus, and they try to prevent this.
    3) Check the format of the drive you are capturing to. It should be Mac OS Extended, journaling off. If it isn't, copy your files from it and re-initialize it.  If it is any other format, you will encounter problems. If not at first, then eventually.
    4) Trash the FCP preference files.  Use PREFERENCE MANAGER to do that, available here:
    http://www.digitalrebellion.com
    5) Make sure that the hard drives you are capturing to are fast enough to handle the footage being captured to it.  A regular firewire 400 drive cannot capture uncompressed HD, or even uncompressed standard definition.  A RAID array of drives might be in order for these formats.

  • Final Cut Pro X effects problem

    Hi all
    I have two computers with Final Cut Pro X 10.0.9, on these two computers the effects will not show when I skim over them in the thumbnails, and if I apply them to the clip, they don't show at all. If I try applying one of the generated texts FCP crashes, and I have to quit the programme.
    The problem seems to be the same as described here, but the solution does not work.
    https://discussions.apple.com/thread/4971527?tstart=0
    On one of the computers that do not work, I do not have the XAVC/XDCAM Plug-in by Sony (PDZK-LT2) installed. The other mac has the plug-in installed, but deleting it, does not solve the problem.
    Is there anybody out there, who could have another solution to the problem?
    Thank you for your help.
    best
    Mathilde

    The FCP X sound effects were an additional external download and were not kept in the FCP X application.
    You probably need to re-download them.
    In the FCP menu at the top left of your screen you will see the download link.

  • Would I still be able to fun Final Cut Pro with no problem with the new 13"

    My old MBP has "NVIDIA GeForce 860M GT with 128MB" and the new 13-inch MBP has "NVIDIA GeForce 9400M graphics" I don't really know what "GT" means, but the more expensive MBP's listed have it, so I'm guessing it's pretty good. I was wondering if I'd still be able to fun Final Cut Pro quickly if I got the new 13-inch MBP.
    Back in 2007, the guy at the Apple store said I'd have to get a MBP instead of a MB if I wanted to fun FCP correctly, and now both the MB and MBP use the same graphics chip, so I'm wondering if FCP will still function correctly on the new 13-inch MBP?

    Eric wrote:
    Incorrect about what? I never made any statements, just questions. According to the Apple store, the Macbook and 13-inch Macbook Pro both use the same chip, which is the only statement I made. And which is why I'm wondering if the new 13-inch MBP can even handle FCP since the MB can't (according to the guy in the Apple store).
    Actually, your original question was formed as part of a statement:
    now both the MB and MBP use the same graphics chip, so I'm wondering if FCP will still function >correctly on the new 13-inch MBP?
    And that's the part that BoyHowdy pointed out that you are "a little incorrect" about. While it's true that they both have an onboard 9400M graphics chip, you are overlooking the fact that the 15" & 17" MBPs also have the much more powerful and dedicated 9600M GT graphics card. This is not an insignificant difference. Final Cut Pro, not to be confused with Final Cut Express (not you, others have confused the two), requires a dedicated card which the 15" & 17" MBPs have in the form of the additional 9600M GT, but the 13" still lacks.
    The specs on the Final Cut Pro page are a little confusing because while it says it *will not work* with integrated graphics, it specifically refers to Intel, and does not mention Nvidia. However, it still says it requires an AGP or PCI Express card, which the 9400M is not.
    My feeling is that even if it runs, the performance of Final Cut Pro on that system will be unacceptable, and will ultimately drive you mad. It really pushes the graphics systems hard, and despite their vast improvement over the pathetic Intel onboard graphics systems, the 9400M is still pretty anemic for high end work. You're better off saving a little more money and getting the low end 15" model. Not to mention, the extra screen real estate makes a huge difference with the very crowded Final Cut Pro UI.

Maybe you are looking for