EyeTV HD To iPod/AppleTV mp4 Workflow
I am wondering about real-world examples of the added performance of a Mac Pro (4GB/2xdual-core) versus an iMac (2.8 4GB/dual core).
For example:
- I decrypt my retail dvd collection.
-Then I use dvdshrink to remove the trailers/warnings etc and choose one language.
-Then I use handbrake to convert the vob's to an mp4 file. I create one AppleTV file
-Then I create an iPod Touch file.
Since converting the files with handbrake is what takes the most amount of time, there will likely always be other things running (decrypting, etc...)
I wonder how fast it takes for a MacPro to convert a DVD via handbrake, versus the fastest iMac?
I'm dealing with off air ATSC HD broadcast recordings done with EyeTV. My workflow goes like this:
1. Use
Epguides.com to add Season-Episode-Year codes to the episode names.
2. Edit out commercials.
3. Place in Toast 8 with compression set on minimum - max quality. Toast 8 can use up to 4 cores. Encode & Burn DVD Image (command D).
4. Open Image in the all NEW
Handbrake 0.9.1. You only need to make ONE mp4 file that will play on both all iPods and AppleTV. The key is to use maximum dimensions allowed so they interpolate up well to an HD screen as well as down to the iPods.
Picture Settings... and CROP at:
624 x 352 for HD
544 x 400 for SD - Uncheck Keep Aspect Ratio
Fast Deinterlace
1Kbps bit rate
H.264 iPod @ 29.97 fps NOT same as source which doesn't work.
I target one hour prime time (net around 42±1 min) at 350MB (half a CD) which is a little over 1Kbps. Make sure you always use the ENTER key when you put a value in those Target and bit rate boxes. Otherwise they won't take - bug in HB.
I target movies at 700MB which may be well under 1Kbps. On any iPod that will look fine. On AppleTV it will look acceptable but it depends on the movie if that is acceptable for YOU.
I NEVER rip with Handbrake from a DVD - only images I make with Toast - that would included from DVDs before using Toast first. File —>Save As Disc Image... (command+D)
Handbrake uses all 4 cores and I'm told can use all 8 cores of that kind of MP.
jasonvp said:
Slight correction on that point. The "cache flushing" you're referring to is due to the operating system, not the hardware. Tiger isn't very good with a multi-core system because it takes active threads and bounces them around between cores. Any time a thread is moved, any memory cache built up for it is flushed.
Supposedly, Leopard won't do that. It'll keep threads "stuck" to cores.
The point being, regardless of what hardware you have, if you run Tiger on it, you're going to have the same problem.
Thanks for that note about Leopard fixing the flush problem with existing 8 core Mac Pros Jason. Good news.