3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Burning a project to Blue Ray Disk using FCPX
- djnav4
-
Topic Author
- Offline
- Junior Member
-
- Im still the same cool dude but much more mature now since I've been married for the last 10 years. Im a man with goals that will move me forward. No time for child hood games . Life is short and I want to enjoy what I have. I have a wonderful family and
Less
More
28 Sep 2012 02:46 #14577
by djnav4
Burning a project to Blue Ray Disk using FCPX was created by djnav4
I finished a 35 min HD project using FCPX and now I want to burn a Blue Ray Disk when I check the summary and the size of the disk is only 8gigs how do I get it over 20gigs using a 25gig blank Blue Ray Disk or is this the size Im gonna get for the disk size and 35 minute length I just thought It would be more than 8gigs
Please Log in to join the conversation.
29 Sep 2012 01:41 #14591
by dgwvideo
Creating history....one edit at a time !
Replied by dgwvideo on topic Re: Burning a project to Blue Ray Disk using FCPX
The size will depend on a lot of things, namely the project size and settings you used to encode for DVD. 8 Gigs is well larger than standard DVD, so it's probably correct based on your project and encoding. Just burn it and see how it looks.
Creating history....one edit at a time !
Please Log in to join the conversation.
29 Sep 2012 05:21 #14595
by cseeman
Replied by cseeman on topic Re: Burning a project to Blue Ray Disk using FCPX
Consider that at that duration and file size you'd be getting about 90 minutes, a feature film, on a Blu-ray disk. Your size sounds about right if not a little on the large size.
Keep in mind that you can only push the data rate so high before it hits a wall and as you get closer to that wall there's usually diminishing returns on the quality improvement.
You'd be targeting an ideal bit rate, not file size..
To use a loose analogy, imagine a professional baseball player who at 225lbs is a great power hitter. Would your objective be to push him to 450lbs, at which put he'd have lots of fat, be overweight and the power would be replaced with a reduction in the ability to maneuver. More is not not better. More can be too fact. More can mean a data rate too high for some disc players to handle.
Your aim is not to fill the disk but find the optimal data rate for the content.
Keep in mind that you can only push the data rate so high before it hits a wall and as you get closer to that wall there's usually diminishing returns on the quality improvement.
You'd be targeting an ideal bit rate, not file size..
To use a loose analogy, imagine a professional baseball player who at 225lbs is a great power hitter. Would your objective be to push him to 450lbs, at which put he'd have lots of fat, be overweight and the power would be replaced with a reduction in the ability to maneuver. More is not not better. More can be too fact. More can mean a data rate too high for some disc players to handle.
Your aim is not to fill the disk but find the optimal data rate for the content.
Please Log in to join the conversation.



