1080p Handbrake settings for new Apple TV?

[shortcut3d]

Here's mine, though I only do the initial ripping under Win7.

- Rip with AnyDVD HD
- Extract video / audio / subtitles with ClownBD
- Convert the subs with BSup2Sub
- Mux everything back in with mkvmerge

I then do then encode with HB on my iMac. For a much more detailed explanation, have a look here.

HTH....

Here is my work flow for Apple / Microsoft mixed environment:

- DVDfab Blu-Ray Ripper mkv.remux preset with subtitles to idx files (you can enable Intel Quicksync for faster remux)

- MKVmerge GUI to remux the subtitle tracks into the mkv created by DVDfab (different source and destination drives will increase speed)

- Handbrake Apple TV 2 preset (720p) or High Profile preset (1080p)

----------

I used your High Profile CQ RF18 suggestion - and it worked flawlessly - and played perfectly on AppleTV - however it will not play on my iPad 3 - are there specifications that are different for iPad 3 that would cause this to not play?

The bit rate is probably too high, you can try toggling between Strict and Loose as sometimes that helps playback compatibility. However, it's likely the content is causing too high a bit rate at RF18 for the iPad.

 

[pheenix11]

A guy on the handbrake board posted the following results:

I made some test encodings with the blu-ray movie "300" and the 3 presets Normal, High Profile and AppleTV 2.
Settings: 1920x800, Cropping 0,0,140,140, Anamorphic Strict, Large File Size enabled, Decomb&Detelecine Off.
Here are the results:

Constant Quality RF:19
- Normal: 12.2 GB (Encoding Time Hour:Min rounded - 3:45)
- High Profile: 12.7 GB (26:15)
- AppleTV 2: 13.2 GB (10:45)

Constant Quality RF:20
- Normal: 10.2 GB (6:45)
- High Profile: 10.7 GB (11:00)
- AppleTV 2: (still encoding)

I'm not seeing the benefit of the High Profile present. Long encode times and no file size savings.

 

[rayward]

I'm not seeing the benefit of the High Profile present. Long encode times and no file size savings.

I think the benefit is a higher bitrate than the ATV2 preset will allow. This will mean a better image quality in the HP version when the picture gets "busy" with detail or action or both.

 

[Wrathwitch]

Pardon my noobish-ness, but why not just use: Air Video?


http://www.inmethod.com/air-video/index.html

Then you don't have to convert anything, it will just stream from whatever drive or directory you choose, or am I missing something here?

 

[mic j]

Pardon my noobish-ness, but why not just use: Air Video?


http://www.inmethod.com/air-video/index.html

Then you don't have to convert anything, it will just stream from whatever drive or directory you choose, or am I missing something here?

Possibly lack of Dolby Digital 5.1 and stuttering on Blu Rays streamed over a network?

 

[atandon]

A guy on the handbrake board posted the following results:



I'm not seeing the benefit of the High Profile present. Long encode times and no file size savings.

What kind of machine is that guy using. Those encode times are enormous.
I typically average 4 hours using the high profile preset with RF==18

I use a 27 inch imac with a 2.93 Ghz i7

 

[rayward]

What kind of machine is that guy using. Those encode times are enormous.
I typically average 4 hours using the high profile preset with RF==18

I use a 27 inch imac with a 2.93 Ghz i7

For 1080p? It takes 2-4 hours to do a 720p encode using the same machine as you.

 

[Los]

What kind of machine is that guy using. Those encode times are enormous.
I typically average 4 hours using the high profile preset with RF==18

I use a 27 inch imac with a 2.93 Ghz i7

Same here, I however have a Mac Mini Intel i7 Quad-core @ 2.0GHz.

The encodes are pretty fast but I start in the morning and cue them up to encode while I'm here at work. When I get home they're all done.

 

[mic j]

What kind of machine is that guy using. Those encode times are enormous.
I typically average 4 hours using the high profile preset with RF==18

I use a 27 inch imac with a 2.93 Ghz i7

I use a 2.66 Ghz MBP duo. I can confirm those long rip times.

 

[pheenix11]

I use a 2.66 Ghz MBP duo. I can confirm those long rip times.

Yeah me too. High profile is brutal.

 

[Wrathwitch]

Possibly lack of Dolby Digital 5.1 and stuttering on Blu Rays streamed over a network?

No need to get snotty about it, I did inform the readership that I was new to this, and it was a genuine question.

But thanks for the answer... sheesh...

 

[dynaflash]

I use a 2.66 Ghz MBP duo. I can confirm those long rip times.

of course. comparing encode times from a coreduo and an i7 is ... ridiculous.

 

[khollister]

Same here, I however have a Mac Mini Intel i7 Quad-core @ 2.0GHz.

The encodes are pretty fast but I start in the morning and cue them up to encode while I'm here at work. When I get home they're all done.

I have both a 3.33 hex MP and a Mini server going. While I get 3-3.5 hr encodes with High Profile/RF=18 on the MP, the Mini is running 5-6 hr.

 

[mic j]

No need to get snotty about it, I did inform the readership that I was new to this, and it was a genuine question.

But thanks for the answer... sheesh...

Not being "snotty", as I don't know the answer to that question. Thought maybe you or someone else might be able to clarify the app's capabilities.

Chill.

 

[knemonic]

A guy on the handbrake board posted the following results:



I'm not seeing the benefit of the High Profile present. Long encode times and no file size savings.

True, but the real question is the end quality. What did they say the difference in quality from Normal to High was is my question?

I have been doing High at rf20 and have been very satisfied (averaging 6 hour encodes) with 5-6gb per 2 hour movie (Rum Diary was weird though, ended up being 9gb).

I am really curious why theirs were so big, 300 has some portions that are dark, which should have been under 10gb.

 

[heliocentric]

The more grainy the film the bigger the encode I think.

 

[knemonic]

The more grainy the film the bigger the encode I think.

But wasn't 300 like all digitally filmed, because it was basically all CGI?

 

[heliocentric]

But wasn't 300 like all digitally filmed, because it was basically all CGI?

From what I remember of 300 (apart from the six packs) it's very grainy. But I think that was added to it in post production for artistic effect.

 

[shortcut3d]

Grain does add a lot to the final file size. Sucker Punch is also grainy and unusually high for its size. The source of the grain does not matter either, so an older movie like House of Flying Daggers where the Blu-ray quality is low vs Sucker Punch where the grain is post production both create equally large files. My solution was to leave House of Flying Daggers at 720p since its not very good source material. Dark movies also tend to be much smaller so for instance Drive is tiny for a 1080p encode vs Rango. Of course length has a significant impact so movies that are long like Avatar are huge!

I find the 200-500MB savings using High Profile preset over Apple TV 2 worth it. That's a tremendous savings in a large library.

FWIW, DVDfab apparently fixed the issues with Intel Quick Sync so I will test video quality results later. Last, I used Quick Sync I was getting over 100-120fps 720p vs 24fps 720p. This would really take the pain out of 1080p encodes.

 

[kobyh15]

I ripped using makeMKV and used the ATV2 preset to encode Step Brothers on DVD. It works perfectly on the ATV but will not play on my iPad 3. Any suggestions?

 

[MarkG21]

I ripped using makeMKV and used the ATV2 preset to encode Step Brothers on DVD. It works perfectly on the ATV but will not play on my iPad 3. Any suggestions?

By not playing on the iPad 3, do you mean that you are not able to put the movie on the iPad or do you have the movie on the iPad and it doesn't play?

Are you able to play the movie in iTunes (on your computer, not the ATV or iPad)?

 

[kobyh15]

By not playing on the iPad 3, do you mean that you are not able to put the movie on the iPad or do you have the movie on the iPad and it doesn't play?

Are you able to play the movie in iTunes (on your computer, not the ATV or iPad)?

I just dragged the file off of my desktop to iTunes. The movie played on my computer through iTunes. The ATV3 was able to play it via home sharing just fine. I was able to sync the movie to my iPad with no problems and it showed up in the video app, but when I went to play the movie on my iPad a dialogue box popped up and said "Cannot play movie".

 

[Los]

I have both a 3.33 hex MP and a Mini server going. While I get 3-3.5 hr encodes with High Profile/RF=18 on the MP, the Mini is running 5-6 hr.

I am definitely getting about 4 hour encodes on my end using the High Profile with an RF of 18, or lower actually. I've pushed it to 14.50 and still get around 4-5 hours of encode time.

It may have to do with the movie, I know Tron: Legacy was the only one that lasted 5 hours and 30 mins or so.

Anyways, I'm playing around with the High Profile setting and decided to do a 4 reference frames and 4 B-Frames instead of the default 3 to see if I could get smaller files, and I am, but it's taking a bit longer to encode now. Not that much though.

I'll report how big of a difference it was when the encode finishes.

 

[rayward]

Grain does add a lot to the final file size. Sucker Punch is also grainy and unusually high for its size. The source of the grain does not matter either, so an older movie like House of Flying Daggers where the Blu-ray quality is low vs Sucker Punch where the grain is post production both create equally large files. My solution was to leave House of Flying Daggers at 720p since its not very good source material. Dark movies also tend to be much smaller so for instance Drive is tiny for a 1080p encode vs Rango. Of course length has a significant impact so movies that are long like Avatar are huge!

Weirdly, I have found that black and white movies end up with relatively very large file sizes. Young Frankenstein and Dr. Strangelove both took forever to encode. I'm assuming it's to do with the intentional grainy look of both movies.

 

[dynaflash]

Young Frankenstein and Dr. Strangelove both took forever to encode. I'm assuming it's to do with the intentional grainy look of both movies.

Young Frankenstein is a bitrate balloon, extremely grainy. Grayscale is not the same as actually clean dark simple scenes with little complexity. yes, grain will balloon bitrate and file size whether it be just old or whether its post production (ala 300).