-
Normal? Can’t Play ProRes HQ on MacbookPro 2.66 wo rendering
Is this normal?
When I drop a ProRes HQ clip onto the timeline, I receive no message asking me to change sequence settings to match, yet the clip shows RED bar in the timeline when RT settings “Playback Video Quality” is to “High”. When set to “Dynamic” I get a gray bar, but I’ll get dropped frames or studdering — playing back from the internal drive or the external RAID. (All this is without the IO HD connected.)
Mac OS X 10.5.7
2.6 GHz Intel Core 2 Duo MacbookPro
4GB RAM
FCP 6.0.6
QT 7.6.2
AJA IO HD
all software is updated as of 7-30-09.
2 WiebeTech eSata Drives, RAID 0
(AJA Whack Test Write=154MBs, Read=142 MBs)
Apiotek Extreme Dual eSATA II ExpressCard -
27 Replies
-
For the MacBook Pro, yes it is normal. It will play in real time on a Mac Pro.
Steve Eisen
Eisen Video Productions
Board of Directors
Chicago Final Cut Pro Users Group -
This is because ProRes422 HQ is running at an average bit rate of 220 Mb/s and your drives are running at an average of 150 Mb/s.
This means your drives aren’t fast enough for ProRes422 HQ.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
In most instances HQ is way overkill. Is there actually a good reason you are using ProRes HQ? What precisely is your reasoning?
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.
-
“This is because ProRes422 HQ is running at an average bit rate of 220 Mb/s and your drives are running at an average of 150 Mb/s.
This means your drives aren’t fast enough for ProRes422 HQ. ”
That doesn’t sound quite right to me. True, ProRes HQ is about 25-30 MBs which would be approximately 220 Mb/s. But my drives are running at 142 MBs which would be approximately 1136 Mb/s, not 150 Mb/s. My drive speed should be WAY overkill for any ProRes codec. A single eSATA drive (70 MBs) should be more than sufficient to play ProResHQ.
SO, is it really true that MacBookPros can’t playback ProRes HQ?
Is that because of the processor (duo vs quad-core)? or because of the speed of the drive?I’m using HQ because I wanted the cleanest signal in order to pull a key and do some significant color correction with the best possible outcomes.
-
[Jeff Coleman] “I’m using HQ because I wanted the cleanest signal in order to pull a key and do some significant color correction with the best possible outcomes. “
I can play back HQ on my ole 2.33 GHz MBP. Are you sure yor timeline is ProResHQ and the footage is actually ProRes HQ?
Jeremy
-
I was about to jump in here and say that I could also play ProRes HQ on my laptop too…oh, wait, I just did.
Yeah, I have no problems, and this footage is playing from my CalDigit VR eSATA drive. I haven’t even attempted to play it back via FW800. But it works on my 2.4Ghz MBP.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
[Jeff Coleman] “I’m using HQ because I wanted the cleanest signal in order to pull a key and do some significant color correction with the best possible outcomes. “
Read Gary Adcock’s white paper on ProRes. HQ is essentially overkill unless you are working with 2K files. Alchemy just doesn’t work, you cannot turn lead into gold, and making bigger files won’t make your video any better.
And, you’re looking at the entire hard drive issue from the perspective of meeting the minimum required, or “how can I get away with the least expense possible and still do the job.” Only in a perfect world does hard drive throughput actually equal the statistics you expect — there are numerous factors that increase overhead and diminish throughput. And, there is hardly ever a time when extra performance from a hard drive sub-system goes to waste. So, overkill on a hard drive sub-system is hardly ever overkill at all.
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.
-
Yes. The timeline and footage is ProResHQ. I even dropped some bars and tone into the timeline, exported it, then reimported with the same resulsts from either media drive source.
seems like this should’ve been easy.
Do you all have the latest software and MBP firmware? -
[Wayne Carey] “This is because ProRes422 HQ is running at an average bit rate of 220 Mb/s and your drives are running at an average of 150 Mb/s.
This means your drives aren’t fast enough for ProRes422 HQ.”
Whoa Wayne, watch your ‘B’s! The HQ codec at 1080 runs at 220 Megabits per second (Mb), where his RAIDed drive has 154 MegaBytes (MB) of throughput. There are 8 bits in every byte, so 220Mb/s would equal 27.5MB/s. His storage is definitely fast enough to keep up with the throughput required (assuming everything is working properly), even if his array was 80% full he should still be able to get at least 60-70MB/s.
Try capturing some footage in the regular ProRes422 and see if your computer has the ability to play it back realtime. I would say your system should be able to play back a single layer no problem, maybe the HQ footage is just a bit too much.
-
You’re right… I’m sorry I’m working on several things at once.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com
Reply to this Discussion! Login or Sign Up