- About me
- Broadcast editor, FCPX convert and founder of the Final Cut Pro Talent Registry at fcptalent.com
- No friends yet
- No joined groups.
Doug Suiter replied to the topic 'ProRes Banding in Quicktime Player - Not in Motion or FCPX' in the forum.Hi all - sorry the tone of this thread went a little south for a moment there.
I'd like to reset this conversation at this point because I think it's really important. I'm not up against a deadline, I'm just trying to get to the bottom of a troubling issue.
What we have is
• Motion seems to be unable to export a gradient in PreRes422HQ that PreRes422HQ has been demonstrated to be able to handle (so this is not a limitation of ProRes issue)
• Open the export in QT, After Effects, Premiere and all show the banding.
• Open the export in FCPX (high quality playback) or Motion and the banding is no longer there.
Here is a link to a copy of the Motion5 project so anyone who want to participate can and we all have the same gradient.
PS - I am posting this in the FCPX forum and not Motion because the trouble is common to both apps (sharing the same render engine) but I am using Motion to demonstrate it because it's the clearest example.
H.264 is a variable bit rate codec deep down, and the "bit rate" you set is only an average.
If you create an H.264 Mov it states in the compressor options that you can set a bit rate limit (using the Restrict to" option)
If you can restrict the bit rate, and if final final size is simply bitrate*time then you should conceivably be able to limit the final file size. And if you can do that, I see no reason why it isn't an option.
Doug Suiter replied to the topic 'ProRes Banding in Quicktime Player - Not in Motion or FCPX' in the forum.The actual size is 1920x1080 and that was not the display size in QuickTime.
Really? ...scaling from 1920 horizontal to 1888 is going to produce artifacting that prevents you from seeing how clearly different the two rendered gradients are? That doesn't seem reasonable.
ProRes has its limitations, especially 422 and HQ. 4444 might work better.
I'm looking back at your comments.
The explanation is that the bit depth isn't sufficient for that fine a gradient.
I have demonstrated that is clearly is, yet your still saying "ProRes has its limitations, especially 422 and HQ. 4444 might work better."
This is not a ProRes limitation.
Anyway I'm kind of done with this. Have a great day,
I'm sorry you're "kind of done with this". It seems to me to be fundamentally important and a possible major issue.
Doug Suiter thanks user 'simonpwood' in the forum message ' ProRes Banding in Quicktime Player - Not in Motion or FCPX'.
Unless your codec uses an averaged bit rate algorithm, such as H.264 which is not a fixed rate codec.
Agreed - that's why i specified "at least for fixed bit rate codecs"
what specific codec does the client need?
It's web delivery. An H.264 MOV seems appropriate.
Doug Suiter created a new topic ' ProRes Banding in Quicktime Player - Not in Motion or FCPX' in the forum.I just spent three hours troubleshooting an issue with Banding GFX coming out of Motion 5 to use with FCPX.
VERY long story short: If I open the renders in Quicktime banding is visible in areas of shallow gradient. By default the renders open in Quicktime and for hours I tried to trouble shoot the export process. However, I found by accident that if i brought those renders into FCPX or Motion, the banding was non-existant and on the same files that showed banding in QT. I did have to set playback to High Quality in the FCPX playback preferences but there are no such preferences in QT.
I guess what I'm asking is - what on Earth is going on here? Any theories or even better - knowledge?
PS - if your interested here are some images of a simple gradient as a demo of what I mean... They are large for clarity.
In all I agree that the best approach for ideal results would be to manually tweak all settings. However, I do think there is some value in an option (at least for fixed bitrate codecs) for compressor to optimise for output using your basic formula " x megabits per second times y seconds = total number of megabits... convert megabits to megabytes..."
I have a client with compressor who wants to export to as close to 100 Meg as possible. She basically wants to set a target file size, possibly a canvass size and have compressor (or another application) take care of the rest.
I have always manually created preset and have never used this approach and am having difficultly answering her as to if it's possible and if not why not. Any suggestions?
Hi all - just making some Motion titles for an ongoing FCPX project for a client. I would like to create titles with embedded audio so that when the client applies the titles an audio sting comes with it. I have tried including audio in the Motion Project where I am creating the title, so far without success.
Is this possible?
Doug Suiter thanks user 'ronny courtens' in the forum message ' Duplicating for Archiving loses Keyword Collections'.
Doug Suiter created a new topic ' Duplicating for Archiving loses Keyword Collections' in the forum.Hi all - I am very much looking forward to improved media Management coming to FCPX as I am sure it must (specifically the option to duplicate project with used media and handles)
In the meantime I still have to archive and am having some trouble. At the moment I take my master project and duplicate it using the "only used media:" option. The trouble is not all keyword collections seem to make it all the time.
At first I thought "well I mustn't have any clips with those keywords in my final project" but on closer inspection that wasn't the case.
For example, I have a clip call THE PROJECT with the keywords FROM DVD and TV SHOWS. I have a few seconds of it in the final edit.
When I duplicate the project, I opt to create a new event with used media only. In the new event the clip called THE PROJECT is in there, and there is a keyword collection called FROM DVD is there but TV SHOWS is not.
EDIT AND SOLUTION: I have solved this issue even before I submitted it. However I thought I would post it here anyway since I already wrote it out - and the answer may help someone.
The answer is that I had been applying keywords to only sections of the clip - keywords which really applied to the whole clip . If that section was not used in the edit, the keyword didn't come across as part of duplicating used media. Sorted
Doug Suiter replied to the topic 'FCPX crashed, "Database Corrupted" error upon relaunch, all projects and events lost' in the forum.Awesome - thanks for reporting back too
Doug Suiter replied to the topic 'FCPX crashed, "Database Corrupted" error upon relaunch, all projects and events lost' in the forum.Hi The Tallest - Doug here from FCPTalent.com's twitter account.
Can you please clarify - do you to say all of your projects and events became corrupted at once and that and they have been moved to this new "Final Cut Corrupted Events" folder? Any chance of a screenshot of how all this looks in your finder?
My Forum Posts
ProRes Banding in Quicktime Player - Not in Motion or FCPX in Final Cut Pro X (FCPX) on Saturday, 25 May 2013 00:58
ProRes Banding in Quicktime Player - Not in Motion or FCPX in Final Cut Pro X (FCPX) on Friday, 24 May 2013 16:06
ProRes Banding in Quicktime Player - Not in Motion or FCPX in Final Cut Pro X (FCPX) on Friday, 24 May 2013 15:26
ProRes Banding in Quicktime Player - Not in Motion or FCPX in Final Cut Pro X (FCPX) on Friday, 24 May 2013 14:47
ProRes Banding in Quicktime Player - Not in Motion or FCPX in Final Cut Pro X (FCPX) on Friday, 24 May 2013 13:42
ProRes Banding in Quicktime Player - Not in Motion or FCPX in Final Cut Pro X (FCPX) on Friday, 24 May 2013 11:24
ProRes Banding in Quicktime Player - Not in Motion or FCPX in Final Cut Pro X (FCPX) on Friday, 24 May 2013 07:10