Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
You don't really need native OSX support for BD movie playback to do what we are trying to do here.. which is ripping / encoding. It already has all the support it needs for raw access to BD drives. Native BD movie playback is a different problem to solve..

I'm just saying more devs will start to develop ripping apps on the mac side once it's supported natively. Right now, this is the only one that you can use on a mac. I'd say we will see a few as soon as bluray support is added, maybe even an anydvdhd port to the mac side..:D
 
If you really wanted chapter markers using AnyDVD HD, you could run eac3to on the .m2ts file to pull the chapter info out to a text file, and then use Subler to attach it to the Handbrake encode output file (this is basically my workflow for most Bluray discs).

Yeah, I understand that. But it's a lot more convoluted than just BRD > Make MKV > HB. The simpler the better, I'd say.
 
So just catching up on this thread, and just wondering.. why all the excitement about this program? Is it because it's native OSX?

I have 50+ BD titles ripped and encoded with AnyDVD-HD + Handbrake, been doing this for almost a year now.. AnyDVD handles everything beautifully, have yet to encounter a title it can't handle. Yes, I have to boot up my Parallels VM.

The fact that MakeMKV can't handle BD+ makes it useless to me - probably about 25% of my titles are BD+. I am glad that we're starting to see OSX options in this space, but this program still has ways to go before I leave AnyDVD for it..

Just curious...what program do you use in-between to make your AnyDVD HD rip readable by Handbrake?
 
Just curious...what program do you use in-between to make your AnyDVD HD rip readable by Handbrake?

I use tsMuxeR in the middle. I use it to rip the 'main feature' M2TS file onto my hard drive, while down-converting TrueHD/DTS-HD audio to AC3/DTS tracks.

This is all done in one step. The beauty of AnyDVD is that operates at a file system driver level.. So it dynamically strips the encryption in the background, making the clear text BD content accessible to tsMuxeR.

With AnyDVD, you could even go straight to Handbrake encoding step, without fist ripping the title to the disk. But I like ripping it down to my disk first, this way I can queue multiple encodes in Handbrake over night. And tsMuxeR lets me preserve 5.1 audio for TrueHD titles.
 
I use tsMuxeR in the middle. I use it to rip the 'main feature' M2TS file onto my hard drive, while down-converting TrueHD/DTS-HD audio to AC3/DTS tracks.

This is all done in one step. The beauty of AnyDVD is that operates at a file system driver level.. So it dynamically strips the encryption in the background, making the clear text BD content accessible to tsMuxeR.

With AnyDVD, you could even go straight to Handbrake encoding step, without fist ripping the title to the disk. But I like ripping it down to my disk first, this way I can queue multiple encodes in Handbrake over night. And tsMuxeR lets me preserve 5.1 audio for TrueHD titles.

Ahh..so you're still using TsMuxer in between.

I just thought you're only using AnyDVD and then straight to Handbrake, as you mentioned on your post.

It would be nice to just rip the BD or HD-DVD with AnyDVD then straight to Handbrake without using TsMuxer in between.

Thanks for the clarification.
 
Ahh..so you're still using TsMuxer in between.

I just thought you're only using AnyDVD and then straight to Handbrake, as you mentioned on your post.

It would be nice to just rip the BD or HD-DVD with AnyDVD then straight to Handbrake without using TsMuxer in between.

Why? tsMuxeR doesn't add any extra time or additional steps to the rip process. I rip with tsMuxeR in one step and then straight to Handbrake. AnyDVD just runs in the background.

But technically, if you don't care about 5.1 audio, you could skip tsMuxeR & ripping part altogether, and go straight to Handbrake encoding. Handbrake understands M2TS containers just fine.
 
I'm just saying more devs will start to develop ripping apps on the mac side once it's supported natively. Right now, this is the only one that you can use on a mac. I'd say we will see a few as soon as bluray support is added, maybe even an anydvdhd port to the mac side..:D

Now THAT I'd like to see. But I doubt it will happen, this has been raised many times on SlySoft forums, and they have no intention to port to Mac OS.

Even in Windows world, AnyDVD is the only tool right now that decrypts BD+. This is NOT a trivial thing to do - SlySoft has a lot of smart people working on this.
 
Now THAT I'd like to see. But I doubt it will happen, this has been raised many times on SlySoft forums, and they have no intention to port to Mac OS.

Even in Windows world, AnyDVD is the only tool right now that decrypts BD+. This is NOT a trivial thing to do - SlySoft has a lot of smart people working on this.

They would be much smatter if they developed for Mac OS X also, as many of us would buy their product. Right now they have no intention of porting it over though.
 
DoFoT9 it has been a while since I used Virtualisation for Windows as I have a Windows PC now :D

I could try later if I get time :)
 
DoFoT9 it has been a while since I used Virtualisation for Windows as I have a Windows PC now :D

I could try later if I get time :)

i take it thats a good thing. dont worry about doing it, it doesnt really worry me. i doubt the difference would be THAT much as most of the work is involved in disk I/O.
 
good to know though, how much longer % wise does it normally take using virtual?

How much longer compared to what? I only use Parallel/VM to do the ripping part with AnyDVD/tsMuxeR. The encoding part is done "natively" by MacOS/Handbrake.

Obviously, the encoding is the step that takes the longest. The ripping takes about 30-45 minutes for a typical BD title. I don't think it would be any faster with this MakeMKV app, or any other "native" OSX app. The ripping process is primarily constrained by disk I/O, so the VM doesn't add much if any overhead here.

Which is why I never understood why people obsess so much with "native" OS-X solution for BD ripping.. The only slight inconvenience with Parallels/AnyDVD approach is booting up the VM, which takes a minute..
 
How much longer compared to what? I only use Parallel/VM to do the ripping part with AnyDVD/tsMuxeR. The encoding part is done "natively" by MacOS/Handbrake.

Obviously, the encoding is the step that takes the longest. The ripping takes about 30-45 minutes for a typical BD title. I don't think it would be any faster with this MakeMKV app, or any other "native" OSX app. The ripping process is primarily constrained by disk I/O, so the VM doesn't add much if any overhead here.

Which is why I never understood why people obsess so much with "native" OS-X solution for BD ripping.. The only slight inconvenience with Parallels/AnyDVD approach is booting up the VM, which takes a minute..

I really just think that the problem for most folks is the degree to which they end up having to do multiple steps in Windows in order to get it done. And, if that person is either fairly unfamiliar w/ Windows, or just gets easily annoyed with the way Windows does things, a one-step process in OS X just feels 'easier.'

For example, when I started archiving my HDDVD's and BR's, I ended up trying a few different apps before I ended up settling on Clown_BD w/ AnyDVD running in the background. Some of the different apps require different components to be installed, and there can be some painful little quirks in the various apps that end up confusing/annoying someone who doesn't have the time or interest in putting in a great deal of effort.

That being said, the variety of available options on the Windows side is incredibly helpful.
 
How much longer compared to what? I only use Parallel/VM to do the ripping part with AnyDVD/tsMuxeR. The encoding part is done "natively" by MacOS/Handbrake.
i was talking about natively in XP (bootcamp or on a normal PC) compared to a VM on OSX. :cool:

Obviously, the encoding is the step that takes the longest.
haha i know that!

The ripping takes about 30-45 minutes for a typical BD title. I don't think it would be any faster with this MakeMKV app, or any other "native" OSX app. The ripping process is primarily constrained by disk I/O, so the VM doesn't add much if any overhead here.
in my experience on my laptop, i have been able to achieve about 10MB/s max copy rate from VM to another HD, compared to the 30MB/s i experience normally. big diff to me.
 
.m4v file made with handbrake will not play

Hey guys,

I've been keeping up with this thread for a while decided to take the plunge myself.

I recently purchased a BD drive for my mini, installed it, and am using MakeMKV to rip BD's. No problems there.

However, I am having issues with recoding full length movies. I downloaded the most recent build of handbrake (which took care of a sound issue I was having). Unfortunately, when I try to recode Transformers using the normal preset, as this will play on my playstation 3, the resulting file is not recognized as a movie.

Interestingly, when I stop the recode a few minutes in, the resulting file works fine. Also, some of the smaller titles on the disk (such as movie trailers) work just fine with the preset too.

Is there some sort of limit to the mpeg 4 container that is causing this to happen? Can anyone make any suggestions as to what is going wrong? I must admit, I don't know much about video specifications and recoding, so any advice is much appreciated!

Thanks!
 
Hey guys,

I've been keeping up with this thread for a while decided to take the plunge myself.

I recently purchased a BD drive for my mini, installed it, and am using MakeMKV to rip BD's. No problems there.

However, I am having issues with recoding full length movies. I downloaded the most recent build of handbrake (which took care of a sound issue I was having). Unfortunately, when I try to recode Transformers using the normal preset, as this will play on my playstation 3, the resulting file is not recognized as a movie.

Interestingly, when I stop the recode a few minutes in, the resulting file works fine. Also, some of the smaller titles on the disk (such as movie trailers) work just fine with the preset too.

Is there some sort of limit to the mpeg 4 container that is causing this to happen? Can anyone make any suggestions as to what is going wrong? I must admit, I don't know much about video specifications and recoding, so any advice is much appreciated!

Thanks!

I'm sure i will be corrected if i'm wrong, but I beleive your issue is due to the large file size of your Transformers movie. PS3 will only accept a file size up to 4Gb as the hard disk will be formated in FAT32. This is why movie clips and smaller files play.
 
I'm sure i will be corrected if i'm wrong, but I beleive your issue is due to the large file size of your Transformers movie. PS3 will only accept a file size up to 4Gb as the hard disk will be formated in FAT32. This is why movie clips and smaller files play.

I suspected that this was one issue, however it doesn't explain why my mac wouldn't recognize it as a movie file.

Does anyone know if it has to do with the "large file size" checkbox in HB? I'm trying again with this selected to see what happens.

Thanks again.
 
What do you mean by this? Please be specific.

Sure. I created a .m4v file using HB. After HB finished, the file would not open. I tried to open it with QT, which gave me a message something like (i'm not at home so I cannot check this) Quicktime cannot open this file - this file is not a movie file. Furthermore, when attempting to add it to iTunes, itunes simply ignored it. It would not add to the library and itunes would not copy it to the itunes folder. Finally, when I checked "get info" on the file, under "more info," there was not any info that you would expect to see when looking at a movie file - no dimensions, codecs, duration, etc.

So clearly this file is not being recognized as a video file, although the extension is .m4v. Now just to figure out why.

Does this make sense?
 
Sure. I created a .m4v file using HB. After HB finished, the file would not open. I tried to open it with QT, which gave me a message something like (i'm not at home so I cannot check this) Quicktime cannot open this file - this file is not a movie file. Furthermore, when attempting to add it to iTunes, itunes simply ignored it. It would not add to the library and itunes would not copy it to the itunes folder. Finally, when I checked "get info" on the file, under "more info," there was not any info that you would expect to see when looking at a movie file - no dimensions, codecs, duration, etc.

So clearly this file is not being recognized as a video file, although the extension is .m4v. Now just to figure out why.

Does this make sense?

OSX looks at more than just the file extension to determine what a file is. My bet is that the encode was > 4GB in length, so it was truncated. Checking "Large File Size" should resolve the problem, but might not be compatible with the PS3.
 
OSX looks at more than just the file extension to determine what a file is. My bet is that the encode was > 4GB in length, so it was truncated. Checking "Large File Size" should resolve the problem, but might not be compatible with the PS3.

Thanks for the info. This confirms my suspicion. I guess I'm well on my way to being a video pro! ;)

I'll have to figure out another way to get it on the PS3.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.