HandBrake

The updated version doesn't crash. Thanks!

I am, however, still getting the loud noise at the start of videos that I mentioned in this post.

jbrjake wrote:Using deinterlace and decomb together is STRONGLY not recommended.

That was a mistake on my part... I meant to write detelecine and decomb.

I haven't had a chance yet to try updating HandBrake, but I will later today and let you know if it works.

SVN 2773 of HandBrake is crashing for my every time I try to encode. I'll select a title on a DVD to encode and click "Start" and then HandBrake will quit. It will also quit if I try to start items in the queue. There are no Mac OS X error messages about the program quitting unexpectedly, ...

I've been seeing this problem (or a different problem with the same symptoms) on many versions of HandBrake (including 0.9.3) with multiple DVDs, and it still persists with the SVN 2592 release. I'm currently using the 64-bit version of HandBrake on a Mac Pro running 10.5.8. My DVDs are all ripped w...

I too have seen content that still shows combing with "Decomb". The best option for such content would be to use custom "Decomb" settings that are more aggressive than the default. Unfortunately (as has been shown in other threads), custom "Decomb" doesn't seem to work ...

I was going to try out some custom decomb settings, since Boy Meets World still has some interlacing with the default decomb. The problem I'm seeing is that when decomb is set to custom, no deinterlacing happens whatsoever (even when the custom decomb has the same parameters as the default decomb, w...

Try starting with the Universal Preset and bumping the Constant Quality up to 62%. That's what I do and my encodes look and play great on my 24" 1920x1200 LCD monitor and iPod touch. File sizes can get large, but that's what my 1.5TB hard drive is for.

http://www.kerstetter.net/

It fixes the Disappearing Chapters bug, and also appears to apply the date correctly now (before, the date would be a day off for me). And Windows users finally have a tagging solution.

Hmm... that's strange. I made a custom preset with decomb on and "Use Current Picture Filters" selected, and it works for me.

van wrote:I just committed r1867 which should let HB handle DV video inputs correctly. Let me know if it works for you. Thanks.

Works perfectly for me. Thanks a lot, van!

Thanks from me too, Van!

The right half of a converted DV file is lime green when converted with HandBrake Snapshot 3. (It appears lime green in the preview window as well.) The left half looks fine. Here's a screenshot and my activity log: http://eddierise.googlepages.com/oreo.png [16:35:43] macgui: Handbrake Version: svn1...

Here's the activity log for an encode that has dark video in QuickTime: [16:17:21] scan: preview 7 [16:17:22] scan: preview 8 [16:17:22] scan: preview 9 [16:17:22] scan: preview 10 [16:17:22] scan: 10 previews, 720x480, 23.976 fps, autocrop = 6/14/0/0, aspect 16:9, PAR 32:27 [16:17:22] scan: decodin...

jbrjake wrote:And is this with, or without Perian installed?

Both, for me. My HandBrake Snapshot 3 encodes look identical in Quicktime whether or not I have Perian installed.

I use Decomb+Detelecine for cartoons. Detelecine by itself is all that's needed for most of my cartoons, but some (aka Futurama) mix Interlaced and Telecined content. So by using Decomb, HandBrake will deinterlace only when needed.

I am noticing the exact same thing with all my encodes with Snapshot 3. They look fine in VLC, but are very dark in Quicktime.

Yes. That's why I put it on the change set in the snapshot 3 announcement: - Better gamma in QuickTime through the use of the COLR MP4 atom Sorry about that. I can't find whether the atom is inserted automatically to encodes in Snapshot 3. Because if it is, Quicktime is still darker than the DVD so...

I am hoping the COLR atom or something gets worked into the software soon. Any chance of that? I am hoping for a 1-click solution before I spend a month of nights going nuts with video editing! It's just waiting for testers: http://forum.handbrake.fr/viewtopic.php?f=4&t=6352 Has the COLR atom m...

rhester wrote:I only use the CLI version - that may make the difference. :/ Which platform GUI are you using?

Rodney

I'm running the GUI version of HandBrake Snapshot 2 for Mac OS X Intel. More specifically, the version available at this URL.

And HB can do 16:9 anamorphic at 640x480 physical with ease, just like Apple. We give you the choice. Rodney I didn't realize this was possible in HandBrake, because I don't see a way to choose 640x480 physical on 16:9 anamorphic on the Mac version (Snapshot 2). I have a 16:9 source, but when I sel...

iTunes automatically downloads two version when you buy an hd tv show: an hd version 720p (1280x720) and another standard definition (720x480 anamorphic, for iPod and iPhone). You are looking at the wrong one :P Strangely enough, the standard definition shows are actually stored as 640x480 (not 720...

853x480? That is not HD, but rather what I would get doing an full anamorphic encode from a dvd. So technically you could make a preset that has the specs of an "iTunes HD TV show" from a dvd. Now there is a chance that I downloaded the standard version as trying to download from the HD p...

It was removed due to a bug. It may/may not make a re-appearance. jbrjake fixed that bug here (at least, his fix worked for me), but he said that Slowest might not reappear in the GUI due to ffmpeg changes that were coming. By ffmpeg changes, was he talking about the new Decomb setting in the HandB...

I did a test encode which worked perfectly for me on my Intel Mac. I didn't get a segfault this time, and I'd gotten segfaults every time when I tried to use mcdeint with used the official 0.9.2 CLI release. Thanks jbrjake. Any chance the "slowest" deinterlace setting will be back in the M...

I'm surprised - you get the pixelization without setting VBV settings? Looks like vbv is being set. vbv-maxrate=2500:vbv-bufsize=2000 Yeah, I didn't want to turn off VBV altogether because these files are for my iPod 5G and I'm afraid they would stutter too much. I just tried a 2-pass encode (same ...