QT conversion workflow

Hi
I want to create an Automator workflow for the following task.
My current workflow for converting a constant number of movie files is as follows.
Export movie from FCP (that won't change)
Automator workflow from here...
When the movie is exported it is then converted to an MP4 file then I have to Apple A to select it, then Apple 2 to double the size, then Apple E to export the new file as an Apple hinted movie. (thats the part where I could do with the Automation)
The first conversion (from QT to MP4) is done from a Compressor droplet but its when the file is an MP4 that I want an Automator script is convert the file to Apple Hinted movie.
In Automator I have selected Get Specified Movies then added Export Movies. There are format options there but only for iPhone etc. Is there a way to specify say the Apple Hinted movie format.
Is the above possible with Automator?
Any help will be appreciated.
Thanks

not really. I generally make mpeg2 program streams but I would start with a very small amount, like .90 or something. I have used the gamma a few times and I find that it's pretty sensitive, so don't go overboard. It may differ depending on your output codec as well... possibly...
there is no waveform in Compressor, because it is not meant to be a color correcting app, but you can get a pretty good "eye" from the preview window. The right side shows your estimated output, and the left side shows the original. Compare the two until it looks good.
The other thing, you can set in and out points in the timeline of the preview window. So select only five or ten seconds of the highest contrast area you can find in your video, and compress that. You will definitely have to do some trial and error here, but at least each trial will only take seconds to compress. Once you find the setting you like, mark it down somewhere, or make a new custom preset, and then get rid of your in and out points and submit again.
Good luck!

Similar Messages

  • Best Practice for Conversion Workflow

    Hello,
    I'm converting video files from our "home grown" virtual media reserve to iTunes U. Some of the files are in RM format, some are already compressed .mov's (not H.264) and some I have the original DV files for.
    Anyone out there have a best practice for converting these file types for posting to iTunes U? I have Final Cut Studio (Compressor), QT Pro and Squeeze available to me.
    Any experience you have with this would be helpful.
    Thanks,
    Jeana

    For converting old files to a podcast compatible video and based on the machine you have, consider elgato turbo.264. It is a fairly priced "co-processor" for video conversion. It is comprised of an application and a small USB device with a encoder chip in it. In my experience, it is the fastest way to create podcast video files. The amount of time that you will save will pay for the device quickly (about $100). Plus it does batch conversion of any video that your system currently plays through QuickTime. it has all the necessary presets and you can create your own. It has a few minor limitations such as not supporting (at this moment) enhanced podcasting features such as chapter markers and closed-captions but since you have old files for conversion, that won't matter.
    For creating new content, the workflow varies a lot. Since you mention MP3s, I guess you are also interested in audio files. I would stick with GarageBand, especially if you are a beginner plus it supports enhanced podcasts.
    In any case the most important goal is to have the simplest and fastest way to go from recording to publication. The less editing the better. To attain that, the best methods will require the largest investments. For example, for video production the best way is to produce the content live so when you finish recording it is only a matter of encoding and publishing. that will require the use of a video switcher that can ingest at least one video camera and a computer output to properly capture presentation material. That's the minimum. there are several devices that can do this for you. Some are disguised PCs and some connect to a PC for tapeless recording. You can check the Tricaster, which I like but wish it was a Mac and not a Windows Xp PC. Other routes may include video mixers from manufacturers like Edirol, Pansonic or Sony connected to a VTR or directly to a Mac for direct-ti-disc capture. I f you look at some of the content available in iTunes U, you will see what I explain here. This workflow requires preparation and sufficient live support but you will have your material ready for delivery almost immediately after the recorded event. No editing required. Finally, the most intensive workflow is to record everything separately and edit it later, which is extremely time consuming.

  • NTSC/PAL conversion workflow

    After years of working with hardware converters (the best of which I don't have available to me anymore), I'm now always playing with various software conversion methods. I know Compressor 2 works okay but is terribly slow, the Nattress filters are good and faster and I've just started playing with JES Deinterlacer which seems useful.
    Anyways, a co-worker here with an Avid and Procoder says he can capture as NTSC (DV or whatever) and just export a PAL MPEG to make a PAL DVD without an additional conversion step. I havent' looked at his results yet, but he said it looks fine and didn't take much longer than if there had been no conversion.
    So I started wondering why you can't do this with Compressor. And actually, it seems you can. Edit in FCP in one format, then create a custom MPEG-2 preset in Compressor in the other format and work just as you would otherwise. I just did this once and it worked fine though there seems to be quite a bit of jaggies when viewed on my cinema display. I don't have a multi-standard monitor in front of me right now, though I will later and will check it there.
    So, the question is, what technically is the difference between this method and using a better (but slower) converter like Nattress or Compressor 2 Format Converter and what sort of quality difference should I expect? And does anybody know how Procoder compares using this or other workflows?
    I work at a large university and occasionally need to do these things. Normally we're originatin in DV and usually just outputting to DVD, so often there's no need for a DV to DV conversion.
    Thanks much to Graeme or anyone that has any insight into this.
    Doug

    Hi Graeme. Thanks for the response. But do you know what the difference is between those low Compressor 2 settings and just changing a basic MPEG-2 preset to PAL? Know what I mean? Is it even necessary to do the whole "Advanced Conversion" step in C2? Its so quick and easy just to change the MPEG-2 setting to PAL, but I haven't had time to test how it compares to using Advanced Conversion, either at low or high quality. With alot of what I'm doing, the source media looks terrible anyways, so I don't need a perfect conversion. Just something decent and fast preferably.
    I shamefully admit I still haven't tried yours except to demo, but I will one of these days when I have a few dollars or have a huge load of conversions to get through.
    Doug

  • Kona 3 Down Conversion Workflow

    I have just set up an online system for a project shot on Digibeta and HDV. I am in the process of doing an edit on my offline suite which involves 3 tracks shot on Digibeta and 1 track on HDV 1080i. I captured the digi's in DVPAL and downconverted the HDV straight out of the deck into DVPAL which has all worked perfectly.
    My question is: when I come to online the final edit, I want to down convert the HDV into the same format as the Digibeta 10bit uncompressed. I have literally never used the Kona 3 card before, and I do not own a HDV or Digibeta Deck to experiment with.
    Can I use the Kona 3 to down convert the HDV footage on capture, or do I have to send it thru the card to a digibeta deck via SDI output?
    Can anybody suggest a workflow to me please? Especially before I hire the decks in.
    I am also not sure with Kona settings to use when down converting the HDV to match the Digibeta.
    Thanks in advance!
    Simon

    Hi,
    as this is actually a Kona 3 question you might try the Kona forum here:
    http://forums.creativecow.net/cgi-bin/newviewposts.cgi?forumid=98
    which is full of kona specific good advice
    I also found that direct questions to AJA via their support page:
    http://www.aja.com/html/support_contact.html
    usually provided my answers.
    hope this helps
    peter

  • Hierarchical entities view in Manage Workflow

    Hi! In my 9.3.1. planning application users with Administrator role can choose between hierarchical and flat views of entities in the Manage Workflow screen but users with Interactive User role only see entities in the flat view with no option for hierarchical view of entities. Is it a standard limitation of Hyperion Planning or is it fixable? I would be very grateful for any ideas!
    Edited by: user10129034 on 19.05.2009 9:47

    Refer to the following conversation:
    Workflow query

  • AVCHD Conversion

    I am currently shooting SD, but am researching moving to HD.
    So far, my research has concentrated on HDV, since that seems to be PRE7's preferred HD format. But truth be told, I'd rather use flash or HDD storage than the miniDV tapes that HDV requires.
    So let's say I went with  AVCHD. Not being a masochist, I don't want to edit AVCHD directly, so I started investigating AVCHD conversion programs. Based on 2 options presented by Steve in a January post:
    AVCHD Upshift. If I understand correctly, this will
    Transfer my AVCHD footage from my camera to my computer
    Optionally de-interlace 1080i footage
    Create a MPEG .m2t file for editing
    Voltaic HD. Again, it seems like it:
    Doesn't actually do a transfer from camcorder to harddrive
    (Optionally?) de-interlaces 1080i footage
    Creates an AVI file for editing
    Dang. As usual,  I ended up with more questions that when I started. And here's where I need help...
    Is MPEG .m2t the same thing as HDV?
    If a converter (e.g. Voltaic) doesn't actually transfer the files from camcorder to hard drive, how would I do that? PRE?
    What's the best way to split the AVCHD files by timecode? Would I use HDVSplit on the .m2t files created by AVCHD Upshift? What about the AVI files created by Voltaic HD... would I just run Scenealyzer against the huge AVI file?
    Is de-interlacing required/desired? Is the conversion tool the best place to do this, or should I leave it interlaced and let PRE handle it upon output? I'm assuming my final output would be BluRay, but so far nobody in my family has BluRay so I might be forced to (temporarily) create SD DVDs somehow...
    Given a choice between converting AVCHD to HDV(?) or AVI, which would PRE7 be happier with?
    What about quality? It seems like HDV is king. Some people say AVCHD is equivalent (or close or better), but it seems like AVCHD quality can vary more widely than HDV based on what camcorder you're using. Also, would converting AVCHD to HDV (or AVI) result in quality issues?
    I've also seen several interwebs posts saying AVCHD is more the consumer-targeted format, while HDV is more pro/prosumer-oriented. I don't care about that so much, but I would like to create the best videos I can with the least problems.
    Whew! Sorry for so many questions, but they all seem related. Let me know if you think they should be separate posts???

    Thanks, Paul.
    I'm sorry if I'm being dense, but I still don't get what happens if I define the project as AVCHD > 1920x1080 and then try to add AVCHD  assets that have been "Upshifted". An Upshifted video will be 1920x1080 m2t file (correct?), so...
    It seems like an AVCHD PRE project would have the right pixel dimensions (1920x1080) but be expecting the wrong file format (m2ts AVCHD).
    While a HDV PRE project would have the wrong pixel dimensions (1440x1080) but be expecting the right file type (m2t).
    So... what would happen if I defined a AVCHD project and added a correct dimension / wrong format Upshift file?
    And what would happen if I defined a HDV project and added an incorrect dimension / correct format Upshift file?
    If I understand correctly, and HDV project would accept the file, but constantly have to render it (red line over clips) due to the incorrect dimensions? Would that rendered file end up "stretched" (or compressed, not sure), or would it be OK?
    Still not sure what an AVCHD project would do. Would it constantly have to render due to the incorrect format?
    And what would be a better rendering... the HDV converting the pixel dimensions, or the AVCHD project converting the file type?
    Your trial idea is good, but the problem is that if I get an AVCHD camcorder, and can't find a suitable conversion/workflow, I'd be stuck trying to natively edit AVCHD - which would not be good! I'd have to return the camcorder. I know an HDV camcorder would work. But I like the idea of the AVCHD workflow, so I'm leaning that way but definitely nervous
    Thanks so much for your patience!!

  • 16:9 sequence becomes 4:3 QT movie

    I'm using FCPHD 4.5 with 16:9 DV footage (720x480 anamorphic)
    I edit my sequence in FCP in 16:9 (Pixel aspect is NTSC CCIR 601 and Anamorphic is checked) and do an Export/Quicktime Movie (DV NTSC 48 kHz Anamorphic)
    I open the resulting file in QT Pro and it is displayed as 4:3.
    Same if I open the file in FCP.
    I have in the past opened this kind of file and have had it display correctly.
    It seems like if I add a filter or text generator, this is when the problem begins. (and won't go away)
    Any ideas?

    sad to say but it seems to be a bug in the way FCP writes the file header info, metadata or whatever it is.
    In particular, this issue has actually gotten worse from 4.x to 5.x. At least with FCP 4.x, if you exported a QT Movie, then (re)imported it into your project, the clip would be recognized as anamorphic. No such luck in FCP 5.x.
    Just so I don't confuse anyone, QT Player never has recognized the anamorphic flag in a QT Movie. That is, File > Export > QuickTime Movie or Final Cut Pro Movie (for those who remember FCP 3). But at least FCP used to. Now even that doesn't happen...
    try using MPEG Streamclip ... works a treat. take any 4:3 clip and "Export to Quicktime..." press the Options button and change it to 16:9. let the exporter write the file, and then open it in QT (ta da!) go ahead and open it in FCP too, check the clip properties ... still 4:3 frame size but note that the anamorphic flag is checked
    As you're no doubt aware, this mimics the File > Export > Using QuickTime Conversion workflow so long as the machine in question has QuickTime 7.1 (down to the ability to select Aspect Ratio and Scan Mode) and results (like QT Conversion) in both QT & FCP recognizing the anamorphic nature of the clip.
    Now, I bring all this up (that I know you're aware of) because you state in a few posts that exporting via QT Conversion causes all frames to be recompressed and that's a big no-no. Can you share the basis of that claim?
    My understanding is that with QT conversion - so long as the key details (codec, frame rate/size, scan mode, etc) are identical to the settings of your sequence) - no (re)compression takes place. What I've read is that it's essentially the same thing as exporting a self-contained QT movie, except with better metadata information (true display size, associated applications, etc).

  • The metadata edits may be saved in the Cloud but the server processing after the wait will not complete.

    I have a library of uploads in the Cloud about 1/25 of max limit for my Match acct. It refuses to update the status inside iTunes while it updates several versions behind as it pushes my uploads to the mobile devices. It has a threshold?! First, the check items to upload would be a problem. After gertting a majority of matching done - Nada, spins for days.

    All my Cloud activity, now, happens on an additional desktop OS laptop, and not my macmini server proper smart playlist library where reside all the orginal files - it just sticks on Waiting!? Today I Learned » if there is a conflict in the Cloud, then anything uploaded as a .wav: status is matched as an iTunes Plus setting, uploaded designation is treated/converted as a MPEG-4 audio file - only on the Cloud files - which I have never had in my conversion workflow . I wish a monitor would reply b4 I hit the jump to Spotify.

  • Podcast 29

    George Jardine kindly invited email responses to his latest fine podcast. I thought I would share with you my words to George:
    George,
    I thoroughly enjoyed your latest podcast with the movers and shakers and found the general nature of the conversation quite encouraging. Thanks for the effort you have put into the podcasts and also for pushing the raw/jpg issue.
    Regarding the raw/jpg issue I felt that the conversation centered on the ingestion of files in an event style workflow, where the jpg is the primary image and the raw file is a backup in case something goes wrong, or some files require special attention. While this is one aspect of the raw/jpg issue there are others.
    The team seems to be thinking primarily about workflow, and not so much about the needs of long term digital asset management. Mark (?) did mention that the future needs of photographers are more important than legacy issues because they will be taking more photos in the future. While this may be true, we should not discount the needs of users who have tens and hundreds of thousands of images in both raw and jpg formats that they want to move into the Lr library to manage in a DAM. In this case, the jpgs (or TIFF or PSD) represent a conversion done pre-Lr, and we do not want to lose track of these non-parametric conversions.
    Another aspect of image workflow that seems to be continually discounted by the team is the need to leave Lr to work in another application and return to Lr. I know there was considerable conversation about round tripping to photoshop, but the issue is much larger than that if one plans to use Lr as a DAM. For many photographers, the last step in their workflow is to save the final conversion as a jpg. The jpg is good enough for most applications (web, printing, viewing on a monitor) and is much more space efficient than plugging up your drive with TIFFs. So, all raw files that have round tripped to another application logically need to come back to Lr to be tracked in the library and perhaps be further used within Lr (web publishing, printing, slide shows). As you mentioned in the podcast, some form of auto-stacking would be logical to keep the round tripped file with the raw original.
    So, the current implementation of Lr is probably workable if the goal is to provide an efficient file conversion workflow for the majority of users that work exclusively with raw. However, if the goal is to also provide a high quality DAM for the user then all files types supported by Lr have to learn to co-exist. It is that simple, and the right thing to do.
    Keep up the good work George!
    Regards
    Rory hill

    John,
    The appeal of LR has been rightly focused on 'doing it all in one place' by Adobe, at least as a marketing theme. That really is where its innovativeness--at least on the Windows side--lies. But, if you go to market with that theme, you are stuck with that expectation from buyers.
    My perception of it having tested LR exhaustively for its workflow effectiveness through the Betas and now 1.1 is that Develop itself is 95% there, but the connections to and through Library are where it is significantly deficient and needs to be brought up to at least the prevailing standards of a basic DAM--not one with advanced bells and whistles--just basics, like a comparable file I/O feature set found on basic DAMs, like Iview, or Idimager to use obvious examples, one SQlite based and one not.
    Certainly handling wav files, doing images of 10 k, etc is beyond basic, and it is simply unreasonable to expect Adobe to put any of those refinements near the top of the list. If they come, so much the better, but getting the basics (a whole, integrated set of them) in there now is what the LR team is facing--at least judging from posts on this forum.
    I am not sure what you mean by, "But I wouldn't breathe too much more fire on the raw+jpeg issue." ???
    That issue is fundementally basic to a workflow efficient photographer's DAM, and it has become a 'symbol' of LR's principal problem at this point in its development--missing, standard, basic features that photographer's require. The industry standard is that files with same names but with different extensions are seen as distinctly different. It simply does not make sense to depart from that convention. It is a missing ,basic, expected, feature.
    From the threads on the forum one can relatively easily perceive that the majority of the complaints that occur over and over are 'basic features' issues--ones that users expected to see there from their experience with other DAMs, other photographic editing and managing applications.
    Were we nearer in time to the beginning of the digital photographic era--five years ago, for example--even with its shortcomings LR would seem like Manna from Heaven. But we are not. There are a lot of experienced, knowledgeable shooters out there (and not just professionals)--many of them Adobe users from way back--with large and well organized collections and archives that simply expected a better, more workflow efficient, more basically complete, set of DAM tools well integrated with Develop.
    It was after all Adobe's advertising and other product hype that set up that expectation.

  • Quicktime file open problem: preventing a masterpiece debut movie!!!

    Hi all,
    I am trying to edit some video footage I shot with a Sony miniDV Camcorder some time back. Part of the reason I bought my first mac (20" iMac duo intel) was to be able to make a short movie from this footage which I could never do on my old, tired rubbish PC. Imagine my disappointment when I tried to open the files with iMovie and they didn't open, just got an error message.
    The files are listed as XXXX.mpg and they have size (multiple GB each). Also I downloaded VLC and they play fine in that. But I really want to get them into the Apple movie making software. It appears, if they can't play in Quicktime, they can't be edited in iMovie.
    Originally, I used a PC Software package called "Ulead Videostudio 8", to get the files off the camera and into mpg format. Thats the only other background I have....
    Can anybody please help! (Its such great footage too, was a charity sponsored classic mini rally around Europe and ending up in Italy, called (surprisingly!) "The Italian Job".
    BUT it was in 2004! Help me realise my dream of a fantastic 10minute movie to impress my friends and family!!!
    Thanks, Chris

    I originally got the film off the camera via Firewire using VideoStudio 8 (one of the few pieces of affordable software I could find on the PC that would read the Sony's file format). I then saved it into its current form using this software.A bit of information that was too important to leave out. In any case, the DV compression format is more or less the standard for editing at the "frame level" on a computer. Any of the usual Mac editors will capture your DV data from your camera via FireWire from within the application.
    This of course, brings up another question. Do you still have the original tape? If so, then the best approach would be to re-import the data directly to editor. This would, of course, reduce the loos of quality associated with your previous conversion to the more "lossy" MPEG format, as well as, any additional loss in having to convert back to a "native editing" format and then on to your delivery/distribution format for the final product.
    If you don't have the original tape, then you would have to go the conversion route to do any major amount of precision editing and this brings up a secondary question -- When you say "MPG" here, are you referring to MPG as MPEG-1 or MPEG-2 files? Files produced on PC platforms often use MPG as a general extension for any MPEG-1/2 audio and/or video format combination. If the files are MPEG-1 A/V, then the MPEG-2 component is not required for MPEG Streamclip but your quality will have just taken another hit due to the conversion workflow.

  • What is the best kids camera for iMovie '08? Flip or, say, IXUS/Elph?

    My kids love creating video clips and the old camera they use is beginning to fall apart and I'm trying to figure out what to replace it with.
    USER BRIEF: The goal is simplicity and ease of use, so iMovie '08 fits the bill. Video and audio quality are of secondary importance. They do want to be able to crop their clips and string them together into a movie.
    I was on the verge of buying a Pure Digital Flip camera but I've discovered a rash of threads in various forums describing problems importing Flip video files into iMovie 8. I don't really want to get my kids involved in a video conversion workflow if it can be avoided.
    The other option is to buy a regular compact digital camera with a movie option. We have a Canon IXUS 70 (a SD1000 Digital Elph in the USA) that produced acceptable clips that iPhoto imports automatically. iMovie '08 trawls the iPhoto library for clips than can be used as fodder for iMovie projects. Pretty easy, I wonder if there are any drawbacks.
    So, my questions are: is the Flip an attractive option in an iMovie '08 environment? Or should I give my kids a regular compact (and if so, are any of the major brands using codecs that are more or less iMovie-friendly than others)?

    Here are some known issues:
    My MAC Updater downloaded the new QT 7.4.5 on 5 Apr 2008. I have been making movies in iMovie, and then posting them to YouTube. In the beginning I uploaded the movies as MOV files but soon discovered AVI files (larger file and longer time to upload) had more clarity when viewed on YouTube. Once the new QT 7.4.5 downloaded all my AVI files had picture, but no sound! I downloaded the Perian component as posted in QT discussions. The sound returned to the AVI files. However, when I Exported an AVI movie from iMovie the picture quality was worse than the MOV movie. There is something wrong with the new QT 7.4.5 when working with AVI, my AVI movies look terrible. These AVI files were all downloaded from my Ultra Flip Video camera with Flip’s codec 3vix. Flip is aware of this problem and acknowledged it last Friday. Flip says Apple is aware of the problem.
    My MAC PowerPc G4 has performed well in the past two months when working with the Flip Video camera. So, at Flip Video’s suggestion I upgraded the operating system to OS 10.5 from OS 10.4.11. Flip Video says their camera works with OS 10.5. Once OS 10.5 was uploaded I soon discovered that iMovie 08 would not operate on my PowerPc G4, 1.86 MHz. The speed requirement for iMovie 08 is 1.9 GHz.
    At this point of “spinning my wheels for nearly a month” with this Flip Video camera, I decided to purchase a new iMac. On May 2, 2008, I walked out of the Apple Store in Walnut Creek with the new iMac 20-inch: 2.66GHz. Now the Flip video camera should work and all my video problems solved. However, this was not to be.
    When I attempted to Import Flip Video AVI and MOV files into iMovie 08 the files were “grayed out” and would not Import. None of my previous Flip Video files would Import. I tried making new Flip Video movies, they also would not Import into iMovie 08.
    At another Apple Store, the tech suggested I download the previous version of iMovie HD. I did this and with hours of working through the different Export options I was able to create movies to post again on youTube. However, the picture quality of the newer iMovies has never approached the quality of my last post before QT 7.4.5 downloaded. Remember my problems started with QT 7.4.5. Well, my new iMac came with QT 7.4.1, I have not Uploaded QT 7.4.5 and won’t until Flip Video fixes this problem.
    Examples of my Flip Video movies can be viewed on youTube at: sffoggydays. The last video with excellent picture quality was posted 6 Apr 2008 titled “A Day at the San Francisco Zoo, Chapter Nine, L-Taravel Ride to BART.” This video was made in iMovie and Exported before QT 7.4.5 downloaded. All the youTube Flip Videos made after 6 Apr 2008 have poor picture quality.
    It is time for Flip Video camera to stop “passing the buck” to Apple. When manufactures of operating system such as Apple and Microsoft create newer and upgraded systems, it is the responsibility of the manufactures of applications to redo the programs for operating on the new systems. Here is where Flip Video is not accepting this responsibility to Mac users of their camera. The Flip Video application/codex/drivers need to be updated in order to fix the following problems:
    - No sound on AVI files in QT 7.4.5
    - No Import of AVI and MOV files in iMovie 08
    - Poor picture quality for youTube in Export of iMovie HD
    I like my Flip Video camera, want to continue making movies for youTube, and recommending the camera to others. The Flip Video camera people need to fix these problems for Mac users.
    I am still making Flip Video of my grandkids.

  • Canon 5D Mark II data rate drop

    Trying to work in the original source format H.264 with clips from Canon 5D Mark II in FCP to show off the excellent resolution of the cam's video format.
    Everything looks great in the exported self-contained QT movie (aka FCP Movie) of video clips only--data rate nice and high at 42.xx mbits/sec. Then I add text clips, and the data rate (and resulting footage quality) plummets to 20.xx mbits/sec or lower depending upon how much text I've added and whether the text overlays footage clips.
    Sequences where I've not added any text retain the original data rate of the source files (42.xx when played back in QT) and look fantastic. But those with text get as blocky as the data rate drop involved.
    Any idea why FCP is doing this to these Canon 5D H.264 sequences when text is added??
    Mary Lynn

    Yes, thank you both for your responses. Quite familiar with ProRes conversion workflows and H.264 delivery, etc.
    What we are trying to do is show clients precisely what the footage looks like right out of the Canon 5D, which is pretty fantastic. FCP will actually create a sequence that matches the 40 mbits/sec long GOP H.264 right out of the digital SLR cam, and will maintain the data rate and great quality in exported self-contained QT movies consisting of hard cuts between multiple clips...that is until text is added.
    But it looks like for now we'll just have to transcode and show clients that instead. (Although hopefully future versions of FCP will allow us to edit Canon's 5D variant of H.264 natively!?)
    Thank you again for your responses!
    ML

  • Editing with Canon 5D Mark II Problems

    Hello fcp experts,
    I shot a short film on 5D and I did not know that I should convert the raw files to Apple ProRes 422 in Compressor and then edit it on final cut pro.
    I already edited the raw files in fcp. and I started adding fades and outline texts. then I rendered them and exported it. That's when I realized that the color of the video changed whenever there was subtitle or fades.
    Is there any way to fix this or do I have to convert all the files to Apple ProRes 422? (I did start) Is there any short cut to this?? Please help!!!

    sorimsanim wrote:
    I followed this guideline I found online and it said to set in and out points on the raw files in Compressor.
    I've never heard of this being done in any of the conversion workflows I'm aware of, and it seems like a waste of time. The amount of drive space you'll save will be negligible - if saving space is the reasoning behind it. Reconnect to the ones without in and out points.
    +And could you tell me the exact settings after conversion? It should be Apple ProRes 422, right?+
    If that's what you converted them to, then yes.

  • ITunes store movies & chapters

    I purchased a movie from the iTMS the other day to see what kind of compression settings it used. Of course it was H.264, but the data rate was a little slower than I expected (about 1600kbps), and I can't see what the audio data rate is. I'm going to assume 128kbps. I also noticed that the movie had chapter markers! Cool!
    So, a few questions.
    1. Does anybody know what the audio data rate is? How can I tell (I have QT Pro).
    2. The movie is 640x480. Wouldn't they want to use a higher data rate? Like 2000-2500 kbps?
    3. I'm backing up all of my DVDs using mactheripper and handbrake. But neither one (afaik) let's me save the DVD chapters. Is there a way to automatically keep them in my compressed movie?
    Thanks!
    G5 Dual 2GHz, 3.5GB RAM; PB 17 1.5GHz, 1GB RAM,    
    G5 Dual 2GHz, 3.5GB RAM; PB 17 1.5GHz, 1GB RAM,    
    G5 Dual 2GHz, 3.5GB RAM; PB 17 1.5GHz, 1GB RAM,    

    I tried MetadataHootenanny114 today explicitly for the chapter markets, but wasn't too impressed for 2 reasons:
    I was generally satisfied with a small limited number of chapters on short clips but was disappointed when I tests them in a complete movie containing 20 markers. Source movie was roughly 6 seconds shorter than the converted movie so there was some "slippage" of markers as the movie progressed. (Can probably live with manually adjusting these if I cannot come up with a better conversion workflow.)
    The chapters were listed as 'chapter1', 'chapter2', etc.
    This is the default for manual insertions and the default found on DVDs from which markers are extracted. If you prefer a more meaningful "description," simply replace the default or extracted text with your own entries.
    The .mov file I saved it as had a choppy playback in iTunes (not metahoot's fault) when the controller was displayed. This was a 720x304 movie playing at 2600kbps. Somewhere around 1.7GB. However, the original .mp4 movie without the chapters played back just fine.
    Have not noted this problem but then, I stayed within the specifications stated by Apple. While the number of macroblocks contained in a 720 x 304 matrix block is less than 1200 (i.e., only 855), the 720 width exceeds the stated maximum of 640 pixels for the H.264 "low-complexity" profile and exceeds the specified maximum of 1.5 Mbps. In addition, the same is true for an MPEG-4 conversion if that was used here. Of course, iPod compatibility may not be of primary importance here. Have noted however, that plyback in iTunes appears to change depending on whether or not an imported clip meets the "low-complexity" specification -- a somewhat puzzeling development.
    From my understanding, .mp4 won't play with chapters, so I saved the compressed .mp4 as a self-contained .mov file from QT Player Pro.
    Have managed to get H.264 "low-complexity" 480 x XXX and 640 x XXX aspect ratio clips to play in iTunes but not when sync'd to the iPod. Have been unable to get 320 x XXX aspect ratio "low-complexity" (have to check whetherthese were actually "low-complexity Movie to iPod" files), H.264 "baseline," or MPEG-4 encoded files to play chaptered in either iTunes or on the iPod.
    The other difference was that the chapters in iTMS .m4v movies had thumbnails!
    Interesting. Have yet to see/analyze an ITMS file. (Was waiting for a "freebie" to be offered.) Will have to see if "enhanced" chaptering options are applicable here.
    What is Apple using to compress their movies?
    A good question. Was disappointed that they still haven't fixed the H.264 "latency" problem. Most of my longer test clips created by the QT "Movie to iPod" option yesterday had data rates in excess of that allowed by iTunes for syncing to the iPod or chapter playback in iTunes. Process seemed hit or miss depending on content. (Will have to drag out more source files and see if that will improve things.) Have already requested access to "low-complexity" profile be added to the "Movie to MPEG-4" export option in a manner similar to the current "baseline" profile alternative.

  • Is there any way to add chapter markers running Mavericks? Is there a reason they have been stripped out the new OSX?

    Is there any way to add chapter markers running Mavericks? Is there a reason they have been stripped out the new OSX?

    Is there any way to add chapter markers running Mavericks? Is there a reason they have been stripped out the new OSX?
    Depending on your choice of workflows, it appears you can still
    1) Add chapter marks manually with QT 7 Pro,
    2) Add chapter markers graphically using GarageBand,
    3) Use a video editor to set chapter markers graphically,
    4) Use a DVD conversion/burning app to set specific or add equi-interval chapter markers, or
    5) Use a media/device player that adds playback only chapter makers when no chapter track is embedded within the file.
    What kind of chapter markers are you referring to here? Mine are not "stripped out" during normal use but can be automatically removed during various conversion workflows.

Maybe you are looking for