Prores 422 24p- is it really 23.98?

I cannot find definitive information as to whether or not prores 422 24p is in fact 24 p or 23.98. In the audio/video windows setting it states to use this preset (24p) when working with 23.98 material.??????
Final Cut 7.03
Thanks so much!

Steve-
Thanks for your reply, the movie inspector says 24fps.
My confusion comes from the FCP window that says to use the 24p setting to work with 23.98 material.
cheers

Similar Messages

  • Black frame on ProRes 422 multicam export

    No issues when watching a project in PP but when exporting within PP get a random black frame in export. Re exported several times and black frame would move to different parts of the video. Tried flattening cams, no fix. Previosuly to issue -- updated CC 2014, CUDA driver update. Music Video had 5 cameras, 1 track of audio. - have some effects in the project like blurs with dissolves.  Plays back beautifully, h.264 files were fine. Just when exporting final version to client did this occur. Tried new sequence, no difference.  Only fix was a ProRes 422 HQ file. Really didnt need HQ, standard was what was requested.  footage is native canon dslr 7D and 5D footage. Any ideas? Also, weirdly I have to change the default codec from GO Pro Cinema to ProRes 422. I'm sure there are a million variables but wanted to see if anyone had stumbled on this and had a suggestion.
    New Mac Power book with 1 TB ssd.
    Maxed ram and gfx.
    External FW800 drive.
    latest update to PP CC 2014
    ProRes 422 1920x1080
    generic QuickTime profiles for 1080
    don't have specific settings handy

    #1 - You shouldn't be using ProRes HQ. All you are doing is doubling the amount of space the footage takes up. HQ is really meant for 2K footage or higher...stuff projected on a BIG screen. If this is going to DVD...SD DVD or BluRay, then regular ProRes will be your best option.
    #2 - Are you looking at this footage on an HDTV? That is the only way to really tell what your footage will look like. Because the way FCP shows the footage, and QT shows it, are different. QT typically brightens the picture so that it will be viewable on most monitors. BUT, if you choose the FCP COLOR COMPATIBILITY in the QT preferences, it will show you what FCP shows you. And if this is too dark, then you need to color correct it to be how you want it to look. BUT! You cannot judge what the footage will look like on a computer monitor. It is VASTLY different that what an HDTV, or regular TV, will show you. You need to get the signal to the HDTV (HD capture card) and then color correct the footage to look the way you want it to look.
    #3 - Avoid HQ. Seemed like it needed repeating.
    Shane

  • HDV to ProRes 422?

    I've got a 90 minute movie to cut.  2/3'rds of the original material was shot with a Sony HDV camera 60i.  The other third is XDCam (HQ), also 60i.
    I'm trying to figure out a protocol.
    The film is aimed at some kind of theatrical distribution, festivals for sure, possibly a network airing.  (It's an engaging subject, and very nicely shot, despite the older format).
    Anybody done this?  And might you have some recommendations?
    Do I 'optimize' on my import?  I notice FCPX optimizes the HDV to ProRes 422 (not HQ), but at 60i.  Is there a way to set a different optimization?
    Should I bother with a proxy when the original was only HDV (now being optimized to ProRes on import)?  The system I have at hand here seems to be fairly robust.
    Or.  Should I edit the HDV original?  And then just output in whatever codec seems appropriate (when I've done some more research)?
    Any suggestions would be most appreciated.
    Ben

    Thank you guys, very helpful.
    And Tom, this is all footage that was captured in FCP7, mostly a long while back, except for the XDCam.  So the HDV was captured from the Sony camera, and the XDCam was the EX3, so straight from the cards (using FCP's capture transfer setup).
    Now I'm playing at switching the whole project over to FCPX.  Mainly because FCPX looks so intriguing.  And.  I had to do an emergency colour grading of an IMAX movie last week, for a test screenig ... working on their HD proxy cut.  I was going to do it in Colour, but I haven't used Colour in six months, and it's a daunting creature to get back into after long breaks.  I've been toying with FCPX for a couple of weeks, just a few minutes here and there, and tried the colour grading setup.  Wow.  In ten minutes I was up to speed.  We did an XML of their film (being cut in FCP7).  An hour later it was in FCPX.  And a few hours later I had a really really nice grade.  It blew me away.  Yesterday we did the 'real' grade in a relatively high-end studio.  Very good people.  Brand new hardware - with lots of nifty buttons and tools.  But I swear the end result doesn't look any different than what we got from FCPX.  In fact.  I'm toying with the idea of actually pulling the 4K into FCPX, and outputting it with MY original grade - just to make a comparison.  Now wouldn't that be intriguing.  And horrible, ultimately, for studios with such a huge capital outlay.  Then again.  It ain't the equipment.  The colourist was a total pleasure to work with, knew his stuff.
    Thank you very much for your help guys.
    Actually, there is still a question in my head.  I'm used to working in 24p.  This film is for theatres, festivals, even a network airing perhaps.  Is a 30 fps master going to work in those venues?  I seem to remember that the new digital projectors don't care what the frame rate is.  Have I got that wrong?  And does it matter whether my master is interlaced or progressive?  I hate the interlaced look - but I'm not sure what this footage is going to look like de-interlaced.
    And.  I'm going to do a lot of colour correcting on this show, and some modes special effects (possibly do those in Motion), but in a 'realist' sort of way; no green screen.  Just trying to make the whole look more cinematic.  But I'm not attached to the 24 fps thing.  Though 30 fps this stuff was SHOT like a film, it already looks cinematic.  But I'd love to somehow ameliorate the inevitable 'video' look of the medium.

  • Can't make a workable custom codec with ProRes 422 (HQ)

    I've only just now found that there is a Support Community for Compressor.  Wish I'd known sooner.
    I see my version of Compressor is 3.5.3.
    I've been on a little saga.
    I started out with the challenge of converting some MP4 files from a Blackberry Playbook into ProRes 422 (HQ) for editing in Final Cut. I used Compressor and the task looked fairly straight forward. I used the ProRes setting in the Compressor, converted my files and imported them into Final Cut. Video was fine but I soon found out that the audio needed rendering every time I put a clip into the Timeline. I went on-line to various chat rooms with this problem. Pretty soon a fellow was telling me that the ProRes 422 (HQ) setting in Compressor had "Audio Pass-through" as default and that this was the cause of my problem. Change it, he said, to "Linear PCM".
    It took me a fair while to figure out that the ProRes setting in Compressor did not allow itself to be modified and that I'd have to create a custom preset if I was to make these changes. I set about to do that. I was able to select "QuickTime Movie" and then in "Video/Settings" choose "ProRes 422 (HQ)", in "Audio", "Linear PCM". This did solve the audio problem. Now files imported into Final Cut did not need rendering. But another problem became evident.
    Whereas the ProRes 422 setting that came with Compressor in its summary page listed: "Width" and "Height" as "(100% of source)", the custom ProRes 422 (HQ) setting I'd just created has "Width" and "Height" as "320" and "240". In short the 19:9 aspect ratio of the original footage was lost. What I got both in the conversion and in Final Cut was a squished SD image.
    I've played like heck with Compressor trying to see if there was some place I could get this custom version of ProRes to correspond to the aspect ratio seen in the Audio Pass-through version that came loaded in Compressor. No luck. All very mysterious.
    My next step was to look to create another custom codec that would have the proper 1280 X 720 ratio. Turns out  "HDV 720p 30fps" does, so now I've been converting to that. Looks fine in Final Cut - proper picture and sound.
    I've been playing around a bit more and see now that I can create a custom setting using "Apple Intermediate Codec". I've tried it and it works too.
    So after all this, my question: Should I be using that codec instead? Or does it really matter what codec I use for editing? Is the only real issue what codec I decide to use to output?
    And while I'm at it: Does anybody have ideas why trying to create a custom setting with ProRes 422 (HQ) does not work - for my purposes at least.
    I must admit this converting codecs is pretty new to me. Hopefully with time this experience will get easier and clearer.
    John

    Setting a Compressor ProRes Custom Setting:
    1) Pick Apple ProRes 422...
    2) Drag the PreRes 422 setting to the Bach Window. You can only make a custom setting from the Batch Window...
    3) Select enable for the audio. Click on setting to make sure it is set right. Uncheck Allow Job Segmenting... Make sure Streaming is set to none*....
    4) Select the Geomenty tab... Pick Custom (16:9):
    5) Click Save As and name your custom setting...
    6) You new custom setting will show up in the Custum folder for later use:
    Another thing you can do is make Droplet of this custom setting. Menu... File... Create Droplet... Save the Droplet into a folder somewhere on your computer.
    A Droplet will start the transcoding automatically. Drag the Droplet onto a video icon and let it do it's job.
    * ProRes doesn't need the Fast Start setting. If this is set it will take almost twice as long to do the encoding. Same with Allow Job Segmenting using Qmaster.
    I did the above on the fly and hope everything is clear for you to understand.

  • FCP Apple PRORES 422 (HQ) setting-how to export?

    I am importing and dropping in scanned images from the storyboard into FCP and then importting and placing on the timeline some digital animated images which have been done in the format 1920x1080 24fps. They have been put through shake and we chose the setting Apple PRORES 422 (HQ) which I have then set the FCP settings to match that. Everything works fine in Final Cut but then when I export the timeline to make it into a Quicktime movie, the digital animated shots dont play properly, they like skip frames. Do you know anything about this and how I get it to play smoothly? I have tried everything I can think of and nothing is working!

    First off, ProRes HQ is VASTLY OVERKILL for converted flash video. That is for 10-bit high end formats. All you gain in using that over ProRes 422 is file size.
    Second, 640x432 is a non-standard frame size. 640x480 is more like it, but really, FCP would like to see 720x480. ProRes doesn't really work in RT with the dimensions you have.
    Convert the FLV to something like DV50 or just DV. but you have to get the right aspect ratio, or things will require rendering. Or better yet, get the MASTER footage, and not a flash video.
    Shane

  • Prorez 422 vs DVCPro HD for capture

    I am producing a television show and need to decide on a capture codec. Does it make a difference in capturing between Prorez 422 or DVCPro HD? I will be doing a lot of keying and intense colors as the show is for children. Also some CGI for backgrounds. I know you can convert the codec but is there an advantage in capturing in one or the other. I am shooting with Panasonic HVX200 output from the uncompressed HD component out.
    Thanks,
    David Perry

    I like ProRes. It is nice, but you may find certain 10bit rendering errors with FCP that don't show up in 8bit CODECs. Alpha channels from still graphics seem to be the worse problems. Also some of the transparency modes don't really work right in 10bit. This isn't really the fault of the ProRes CODEC, but appears to be a problem with FCP 6 and all 10 color spaces.
    If you don't plan many transparent graphics, ProRES is awesome and I would recommend you use if if you have an uncompressed feed coming from the camera.
    I would only recommend ProRes if you have AJA Kona hardware. Only the top Kona cards seem to support it fully. My LHe card supports it but most io devices don't.
    The color space of the ProRes is very very nice. I've pushed a scene from a Varicam (captured via SDI into the Kona) by about 3 stops recently and was able to recover it without anybody knowing. It was slightly more grainy, but still very usable. DVCPro would not have taken this kind of abuse.

  • Does CC 2014 eliminate the need to have Final Cut Pro and/or Compressor installed to access Apple ProRes 422?

    Hello:
    Just today, I was working on a Mac system that does not have any of the applications that I would have expected to need to have installed in order to do more than just decompress movie files compressed with Apple ProRes 422.
    I was expecting to have to install Final Cut Studio 3, Final Cut Pro X, Compressor 4, and/or QuickTime 7 with the QuickTime Pro key; however, none of those applications are installed and I am able to create custom QuickTime Apple Pro Res422 Sequences in Premiere Pro as well as export using Apple ProRes 422.  After Effects and Adobe Media Encoder also show all the Apple ProRes variations.
    Does CC 2014 eliminate the need to have Final Cut Pro and/or Compressor installed to access Apple ProRes 422?  Is it something happening on the OS or QuickTime level that would affect CC or CS6 in the same way?
    I've done a web search, but haven't really come up with anything other than older articles about needing to have FCP installed (and I typically work on systems with Final Cut Studio 3 installed as well as CS6, CC, or CC 2014).  If more detailed information is available, it would be great to be able to read up on it.
    The system is a 21.5-inch iMac running Mac OS X 10.8.5, QuickTime Player 10.2, and Adobe Premiere Pro CC 2014 (8.0.0 - I know an update is available for PrPro, but it's not my system to make that change).
    Thanks in advance,
    Warren Heaton

    Hi Emil:
    I use ProRes all the time as well, but I have Final Cut Studio on my workstations.
    I had not come across MindPower009's YouTube video.  That explains how ProRes could be showing up without FCP or Compressor.
    So, the answer to my question would be, "No, CC 2014 does not eliminate the need to have Final Cut Pro and/or Compressor installed to access Apple ProRes 422; however, if you are willing to be in violation Apple's terms of use, you can install the ProRes codecs anyway."
    Even though MindPower009's YouTube video comments claim "FREE and LEGAL", it's clear from both the Apple download page and the ProRes codecs installer that Apple expects you to own at least one of their applications.
    Thanks again for the link!
    -Warren

  • Adobe Media Encoder CC: Can I export to Apple ProRes 422 on a Mac?

    Hi folks,
    I tried to find some information about it, but couldn't really find a definite answer on this.
    Unfortunately, my Mac is getting fixed  as we speak, so  I can't try this out either...
    I want to convert mxf files (XDCAM HD 422 1080i 50, 50 Mbit/s with multiple Audio channels) to Apple ProRes 422 using Adobe Media Encoder CC.
    Simple question: Is that possible or do I need to look for a different workflow/converter?
    Thanks for your help!
    Jens
    PS: OS is Mavericks...

    Hi DataWrangler,
    Thanks for posting on Adobe Forums.
    Please download proress presets for Adobe Media Encoder from here : http://www.adobe.com/support/downloads/detail.jsp?ftpID=5411
    Please update if this helps.
    Regards,
    Sandeep

  • Apple ProRes 422 HQ needs rendering, but it shouldn't.

    Sequence Settings (hereafter called the master sequence) are:
    Apple ProRes 422 (HQ) 1920 X 1080 24p 48khz preset.
    Frame Size: 1920 X 1080 (HDTV 1080i 16:9)
    Pixel Aspect: Square
    Editing Timebase: 23.98fps
    Compressor: Apple ProRes 422 HQ
    Audio: 48khz/16-bit
    Footage is:
    Apple ProRes 422 (HQ)
    Frame Size: 1920 X 1080
    Pixel Aspect: Square
    Editing Timebase: 23.98fps
    Compressor: Apple ProRes 422 HQ
    Audio: 48khz/16-bit
    Data Rate: 19.5 MB/sec
    I need to put a timecode window burn on the entire movie for a web clip. So I exported a ProRes master as a QuickTime movie using the sequence settings. I then imported that clip and slipped it into a new sequence with identical settings (hereafter called TimeCode burn sequence) and was surprised to see the red render bar across the entire sequence.
    As an experiment, I exported a brief (one minute) clip from the same master sequence. I then slipped that clip into my TimeCode burn sequence and it does not need rendering (it shouldn't).
    I shouldn't have to render the Master clip first, only to have to re-render it once I but the window burn on. The movie is 30 min. long and the file size is 34GB. Is there a file size limit on ProRes HQ clips that don't need rendering? Why don't the shorter clips from the same sequence need rendering. I don't understand this. Very time consuming.
    EDIT: I will probably end up using the Timecode Generator option in Compressor, so please don't suggest this, as I am aware of it. I want to figure out this mystery.
    Message was edited by: Mr. Landers
    Message was edited by: Mr. Landers

    No, you're absolutely correct to use HQ. Just checking.
    The Red footage is has 4:4:4 subsampling, so HQ's the way to go.
    If you generally use Recompress All Frames on Export then you probably know that it's pointless to render your timeline before an Export, since your Render files won't be accessed. Unless you need to work in that same sequence with the timecode - but, you could just use your exported master for that.
    I know the recompress all frames option is probably overkill for a sequence with only one effect, but I'm also thinking about drive space. With those huge Red files, your render files have to be eating up quite a lot of it.
    So, I'm suggesting that you don't need to render this sequence before exporting. Just export the unrendered sequence with Recompress All Frames. That saves you the space the render files would be taking up.

  • Browser showing Compressor as Apple ProRes 422.

    I am working with HD clips from a Canon using AVCHD codec so I am wondering why my Browser, Compressor column shows Apple ProRes 422. Keep trying to find something in the manual or online video tutorial but no luck. Does this have something to do with how the Setup was handled and should some settings be changed?

    I wish I could answer your question but I sort of don't understand it. When I open my Log and Transfer window there is no option I can find to select preferences on Transferring. I don't see anything like this in my User Preferences, System Settings, Easy Setup, (this is the only place I can find the Apple ProRes 422 codec) Audio/Video Settings window - Sequence Presets and Capture Presets.
    Could it be I had selected the ProRes 422 in Capture Presets at one time because in the Summary window of Capture Presets states "Use this preset to capture from an HDV device and transcode to Apple ProRes 422." and FCP remembers this every time it deals with this HD information?
    Thank you very much for your help. I have been using FCP ever since V1 came out but even with a three day class and video tutorials I get really lost sometimes.

  • ProRes 422 & Premiere Pro CS5.5.2 Playback

    I am a long-term user of CS5
    Recently started using ProRes 422 footage, (LT in order to keep file size a little smaller). The footage is taken from a Ninja2 via the HDMI of a Sony HVR Z5.
    I do a lot of post work on my projects and the native mpeg2 8 bit from the HVR would not hold out too well. Apart from that, I had no previous performance issues using mpeg 2 files.
    Now the ProRes 422 footage in the preview window and in the timeline of PremPro is stuttering and won't play smoothly for more than a couple of seconds at a time. This has become progressively worse as the timeline has grown.
    I use a single video track (I don't stack or nest) and often use 4-5 audio tracks ( 24bit .WAV) plus a stereo channel from the Ninja2. Audio settings within the project are 32 bit floating.
    Average Data Rate of the ProRes (LT) Video File is 8.9 MB/s. Source Audio is 48KHz 16 Bit.
    Edit Workstation system (exclusive, no other use):
    Triple Channel 24GB 1600 RAM
    i7 970 (Hex) 3.2GHz
    Nvidia GeForce GTX 580
    MB Gigabyte X58 (No Overclocking)
    SSD OS & Programs
    4 x 500 GB Sata2 Caviar Black RAID 0 media scratch disk and cache (Software RAID - no hardware controller). The RAID is striped at 128Kb.
    1 x 1TB Sata2 Caviar Black project files
    CPU Temps 44-46 C
    System Temps 41 C
    Graphics Temps 58-60 C
    Disk Temps 30-40 C
    The disk access times during playback are often less than 5 ms. Quick Bench (8MB zone) test gives RAID 0 Average Read Time of 642 MB/s, Random Access Time of 14 ms, and Burst Speed of 3411MB/s. CPU Utilisation is 2%. CPU system usage is fairly low as is the RAM demand with 50% often unused. 18Gb of RAM is allocated to Adobe programs (After Effects & Prem Pro) with 6GB available for other things.
    I am using no external monitor interfaces.
    The ProRes footage is imported into Prem Pro and the sequence setting is automatically created by dragging the ProRes file into the New Item folder.
    The project sequence created by Premiere Pro is AVCHD 1080i Square Pixels 1920 x 1080, Upper Field First 25 fps (PAL) which is correct for me in the UK.
    This works out fine as I have additional footage from a Sony NX5 which is AVCHD and happy with those sequence settings - I get smooth playback from the NX5 in both the preview window and the timeline. The resulting timeline bar colour is Yellow for both footage. If the Pro Res footage is rendered on the timeline (green bar) playback is fine. The render codec is by default I-Frame Only MPEG.
    At the start of the project, the playback seemed fine, but now I am about 35 minutes in and the whole thing has ground to a stuttery conclusion.
    The footage in the preview window scrubs and jogs fine, but plays for about a second or two then stutters, as does the timeline. I would expect my system to easily handle the Pros Res footage - but it doesn't.
    Any similar experiences out there?

    1. With that much footage, I might set previews to render to my output size, so as to cut down on final render time.
    2.  112gb!  Holy Crap!  I hope you're on a fast RAID drive with that!  Otherwise saying you're headed up $*it creek without a paddle doesn't quite cover it... ...more like drowning in the $*it ocean. 
    With that much information you're almost always better off utilizing a rendered file rather than relying on your dynamic link.  If playback is choppy, you need to be able to render to a drive that isn't "Busy" while you're playing from it.  I've found that using separate RAID for my main project file, and my original or AE assets allows me to render out the previews to a non-busy drive, making the output faster, and the playback faster when reading it.
    Dynamic linkage is great... ...if you're going to be making more changes to that piece, leave it as is and play it back, if not, RENDER THE EFFECT, or RENDER A WORK AREA set to the clip you're editing.  If you're done for the day, render the whole damned thing and leave it until you come back.  Rendered effects will play back faster than active process effects (renders are already in the video, set into it as if native to it; active process edits aren't in the video, they are applied as it is played back, and require more processing so they slow things down), and when you come back from lunch or from home, you'll have a freshly rendered slate to preview.  This means you'll be able to show off for the client by morning.  Need a Web-capable rendering for a status update you're sending to a client, DUPE the sequence, change the preview on the DUPE to match some web capable settings with smaller frame height\width resolution and compress the hell out of it.  Youtube can play it back pretty well, and vimeo also, and you'll be able to upload it in 2-4 hours (if your system is archaic like mine, smaller video outputs great).  Personally, I've found comps with AE to be a pain when trying to link and playback.  Render a work area around the comp if you're going to play it back.  IF you want to preview a whole section, Dupe the Sequence and use the Dupe to NEST the SECTION (create a trim or edit mark at the beginning and end of the section you wish to preview, select everything between the markers, right click and select nest), and you can use AME to render a small preview file, so you don't interrupt the rest of your work.
    I work with more sound quality constraint than video, and the sound quality has to be real, while the video does not need to be perfect (doesn't mean I don't damn well try; I've really just begun my journey into this world, and have only begun to use prores, but found some pitfalls to experiment and solve).  I start with whatever I'm given, go to prores, edit with a prores proxy preview at ¼ the input size, and render out once just to get started.  The effects values are applied to the preview in playback, easing the playback stutter, and allowing me to work fluidly on a laptop mac with an intel core2 2.16ghz with a geforce gfx card at 256mbvram and 4gb of system ram, with (hardware hack) 2 internal drives each at 1tb, one for main use, and one for housing my project files.  Using an old esata express card raid box, I get great speed from the playback by storing the previews on RAID, while all the other files are housed on my secondary internal drive.  With multi cam AV, you need to be able to store the main clips on different drives, or on a raid store (ideally on separate RAID stores) in order to play them back while cutting them together.  However, once cut, you should render out the preview in it's entirety, and start your other edits from that point.  Then you can render just the effects and still get great playback.
    If you don't see Prores in your preview box, get the AME prores presets from the adobe site, and you can place them by hand into your app (the folder should be the EncoderPresets folder in the program files on windows, on mac open the .app by right click and select show package contents>contents folder>settings>EncoderPresets and paste the .epr files there by hand).  Then open up premiere and you should be able to use prores proxy for your previews and export.  I like to export to prores and then use handbrake to export to x264 with --fake-interlaced set up so I can use it as a transcode for Encore.  Just keep your blu-ray data rates under 35mbps and you should be fine.

  • Can Not Import Apple ProRes 422 HQ Files Into Color

    I am able to navigate to the files I want to import and they then show up in the Setup window, but when I highlight a clip and then select the Import button, nothing happens. What am I doing wrong? These clips are from a Canon 7D and then converted to Apple ProRes 422 HQ.

    Check your "Shots" bin to see if they are importing, but are not in the timeline window. They could be importing, but simply aren't where you expect them to be. The timeline preview doesn't adapt, so it could simply be a matter of zooming or scrolling around to find them.
    If they really, really aren't importing, then its likely some kind of hiccup in the conversion that COLOR doesn't like. When you select the clip in the COLOR browser it is identified and may or may not qualify for import. What is COLOR interpreting the media to be?
    Is your timeline locked?
    jPo

  • Prores 422 clips not working

    I cant import prores 422 clips into my editing software, or play them in quicktime
    error message for final cut : 'file error: 1 files(s) recognized, 0 access denied, 1 unknown'
    error message for after fx: 'after effects error: file 'filename.mov' cannot be imported - file of type "MooV" are not supported.
    - I have set easy setup in final cut to prores 422, still didnt work
    My specs:
    Final cut pro 7
    After effects cs3
    quicktime 7.6.4
    any help would really be appreciated,
    thanks,
    goron

    your solution was somewhere on the money,
    i recopied the files and it seems to be working fine
    thanks

  • Final Cut 7 stuttering playing prores 422 LT

    Specs:
    Mac Pro early 2008
    Dual quad core 2.8
    8GB RAM
    Lion 10.7.5
    Now that that's out of the way...
    This is really frustrating.  I have a project that's about 1TB in total, all in prores 422 (LT).  From the time I launch FCP, I have about 5 or 10 minutes, give or take, before every clip starts skipping and stuttering to the point of unusability.  I've checked everything I can think of.  I'm not taxing my RAM, CPU, or HD.  My scratch drive is a 2TB internal drive dedicated to scratch, so there's nothing else using it.  I've tried shutting off everything else on my system but that doesn't help either.  The only way I've been able to fix it is to restart FCP, but then it all just happens again.  I've tried copying clips to other HDs when it starts happening, but I get the same result regardless.  When it's working, I'm able to play a 2 angle multiclip perfectly, with the HD transferring at about 45 MB/s.  Single clips usually are about 23 MB/s, but when it starts stuttering, Activity Monitor says it barely is able to go above 15.
    Any ideas?  This is driving me nuts.

    I don't know the make of the camera at the moment, I'll find out today and update that later.  Here's a picture of my sequence settings:
    I finished cutting this piece in Premiere (with no issues whatsoever) and exported an XML so I can prepare an FCP sequence to deliver.  The SECOND I imported the XML back into FCP, it was stuttering all over the place as bad as it ever has.
    I have no idea what to think here.  I can play higher bit rate video in FCP without issues, but this particular format/codec is just a nightmare.  I think I can also rule out the camera because I tried taking other video from another project and transcoding it to match these settings and it gave me the same issues.

  • ProRes 422 and AIC import on MacBook Pro

    I need to import 24p from a Canon HV20 and remove the pulldown in Compressor. There is technical note in the Knowledge Base on how to do this using ProREs 422, but the system specifications for ProRes 422 are a dual Xeon chip (Mac Pro), Can I either use ProRes 422 on a Macbook Pro or can I use another intermediate such as AIC?

    Yes, the technical specs say that you can easily use ProRes 422 on a MacBook Pro but they seem it indicate that capturing it may be a problem. I have been online with Apple and they say that I can use a different intermediate but not Pro Res 422 - has anyone tired using PropRes 422 on Macbook Pros?

Maybe you are looking for