Downgrade Back to v0.9.3

[macevanscb]

I WAS a very happy user of HandBrake v0.9.3 for the last year.
I just stupidly upgraded to v0.9.4 and am really angry.
First, all of my two dozen presets are completely broken and will have to be replaced.
Second my framerate at the same settings I used before is HALF what it used to be.
I can't find my original download for v0.9.3.
Please tell me where I can download v0.9.3 for Mac OS X 10.5 PPC so I can get back to where everything was working properly.

[TedJ]

We no longer make Handbrake 0.9.3 available for download from this site, although there are many sites that still have it.

http://mac.oldapps.com/handbrake.php

Be aware that we no longer offer support for this release.

[derez]

Thanks so much for the link. I've been tearing my hair out trying to get the new version to work, but I give up. First of all, if I try to drag the "constant quality" bar beyond the preset setting, which is something like 60%, video will not play at all. If I keep it at 60% it will work, but quality isn't as good as it used to be. Because back then 100% worked. And I always used it.

I mostly use Handbrake to make videos that end up on YouTube, and when using this version, all clips end up stuttering. Like it pauses for a second every other second. Unbearable to watch. Video will not "stutter" before I put it on YouTube, so something happens with it when YouTube converts it, I guess. Some videos I made last year ended up stuttering like that, but now it's happening with whatever I through at it. So glad to get the old version with this link. Now I can get back to business as usual.

[nightstrm]

You do know 100% doesn't equal passthru quality, right? There is a reason the presets don't go higher than 60... Honestly anything above 62-65% is a complete waste of bits.

[derez]

Well, something made the settings on the 9.4 version look bad. The 9.3 version I had figured out. This new version isn't cooperating with me at all.

[lothargores]

I too had to go back to 0.9.3. The movies do look good (Excellent) on the MAC (in iTunes and on QuickPlayer) but they all look terrible on the AppleTV (Very pixelated).

[Rodeo]

I too had to go back to 0.9.3. The movies do look good (Excellent) on the MAC (in iTunes and on QuickPlayer) but they all look terrible on the AppleTV (Very pixelated).

That's caused by weighted p-frame prediction and will only happen if you don't use the AppleTV preset (which specifically disables weighted p-frames so that the movie doesn't look pixelated on the ATV). Note that the AppleTV Legacy preset will not work on the ATV either.

[macevanscb]

Mac.OldApps.com only had v0.9.3 or v0.9.1.
Neither of those versions match what I had before installing v0.9.4 blew it away.
Is it possible that I was running v0.9.2???
TedJ ... can you please tell me of a site where v0.9.2 resides??????

[rpb]

I also reverted to 0.9.3.

I tried 094 with lots of different settings with the highly recommended "Constant Quality" (RF19, RF19.5, RF20, RF20.5, RF20.75, RF21 and so on) but either the files are way smaller than I had them in v093 (and have a quite bad picture quality) or they are getting unpredictably big (double size by switching from RF20 to RF19.5).

I found it more logical to calculate a "homemade" factor for each pixel: e.g. 640px * 480px = 307200 pixel * my factor 4 = 1,228,800 -> Average bit rate 1250 kbps and so on. Depending to the desired quality I sometimes use factor 6 for HQ or factor 3 (when the source material is low quality...)

The CQ "Speed improvement" of 094 doesn't matter much to me, but the new interface with the separate picture windows is complicated. Also the preview window does not work properly with anamorphic settings.

But what I find worst is that selecting a new track always resets all video, audio and subtitle settings. v094 takes me too much time and causes too much mistakes when I want to set up a big batch for the night.

Sorry guys, but v094 is not "The egg of Columbus" for me.

[nightstrm]

I also reverted to 0.9.3.

I tried 094 with lots of different settings with the highly recommended "Constant Quality" (RF19, RF19.5, RF20, RF20.5, RF20.75, RF21 and so on) but either the files are way smaller than I had them in v093 (and have a quite bad picture quality) or they are getting unpredictably big (double size by switching from RF20 to RF19.5).

I found it more logical to calculate a "homemade" factor for each pixel: e.g. 640px * 480px = 307200 pixel * my factor 4 = 1,228,800 -> Average bit rate 1250 kbps and so on. Depending to the desired quality I sometimes use factor 6 for HQ or factor 3 (when the source material is low quality...)

The CQ "Speed improvement" of 094 doesn't matter much to me, but the new interface with the separate picture windows is complicated. Also the preview window does not work properly with anamorphic settings.

But what I find worst is that selecting a new track always resets all video, audio and subtitle settings. v094 takes me too much time and causes too much mistakes when I want to set up a big batch for the night.

Sorry guys, but v094 is not "The egg of Columbus" for me.

Don't worry, our feelings aren't hurt.

[dynaflash]

/me goes to google " The egg of Columbus " ....

[baggss]

I too had to go back to 0.9.3. The movies do look good (Excellent) on the MAC (in iTunes and on QuickPlayer) but they all look terrible on the AppleTV (Very pixelated).

That's caused by weighted p-frame prediction and will only happen if you don't use the AppleTV preset (which specifically disables weighted p-frames so that the movie doesn't look pixelated on the ATV). Note that the AppleTV Legacy preset will not work on the ATV either.

So am I understanding that anything ripped that didn't use the ATV Preset (when ripped with 0.9.4) will look bad on an ATV then?

[nightstrm]

I too had to go back to 0.9.3. The movies do look good (Excellent) on the MAC (in iTunes and on QuickPlayer) but they all look terrible on the AppleTV (Very pixelated).

That's caused by weighted p-frame prediction and will only happen if you don't use the AppleTV preset (which specifically disables weighted p-frames so that the movie doesn't look pixelated on the ATV). Note that the AppleTV Legacy preset will not work on the ATV either.

So am I understanding that anything ripped that didn't use the ATV Preset (when ripped with 0.9.4) will look bad on an ATV then?

If weightp=0 wasn't present, then yes.

I blame Apple for not updating the AppleTV codebase from 10.4.8 (or 10.4.7, I can't remember).

[dynaflash]

So am I understanding that anything ripped that didn't use the ATV Preset (when ripped with 0.9.4) will look bad on an ATV then?

Well, the built in presets in 0.9.4 are updated accordingly. hb will disable weightp on any baseline preset automatically ( read ipod/iphone and universal presets ) . It will additionally add weightp=0 to the atv preset ( which is not baseline). So, any custom presets for atv need to have "weightp=0" added to them as the atv is the only device we know of that can play main profile but not support weightp. Otherwise what nightstrm said.

[nightstrm]

So am I understanding that anything ripped that didn't use the ATV Preset (when ripped with 0.9.4) will look bad on an ATV then?

Well, the built in presets in 0.9.4 are updated accordingly. hb will disable weightp on any baseline preset automatically ( read ipod/iphone and universal presets ) . It will additionally add weightp=0 to the atv preset ( which is not baseline). So, any custom presets for atv need to have "weightp=0" added to them as the atv is the only device we know of that can play main profile but not support weightp. Otherwise what nightstrm said.

Good point, forgot about the weightp being disabled automatically with the baseline presets.

[baggss]

So am I understanding that anything ripped that didn't use the ATV Preset (when ripped with 0.9.4) will look bad on an ATV then?

Well, the built in presets in 0.9.4 are updated accordingly. hb will disable weightp on any baseline preset automatically ( read ipod/iphone and universal presets ) . It will additionally add weightp=0 to the atv preset ( which is not baseline). So, any custom presets for atv need to have "weightp=0" added to them as the atv is the only device we know of that can play main profile but not support weightp. Otherwise what nightstrm said.

So if I make that change to my custom presets, how will this impact video played from an iPod (5G, Classic or iPhone) to a TV?

My custom presets are pretty simple and are tailored to give me the best quality and still maintain the most compatibility. I don't have an ATV yet, but that will be changing shortly and I'd like to know what I need to go back and re-rip with 0.9.3 to get ATV to look good again....

[Rodeo]

My custom presets are pretty simple and are tailored to give me the best quality and still maintain the most compatibility. I don't have an ATV yet, but that will be changing shortly and I'd like to know what I need to go back and re-rip with 0.9.3 to get ATV to look good again....

I'm not sure what you mean by "re-rip with 0.9.3". Doesn't sound a good idea IMO.

If you are encoding with a baseline profile preset, note that handBrake 0.9.4 automatically disables weightp if it detects bframes=0 in your x264 options string, since weighted p-frames prediction is a main profile feature and a recent addition to x264 (the idea is that most people would forget to disable it and end up with a main profile encodes, so it gets automatically disabled). So you won't need to re-rip baseline profile encodes.

[dynaflash]

My custom presets are pretty simple and are tailored to give me the best quality and still maintain the most compatibility. I don't have an ATV yet, but that will be changing shortly and I'd like to know what I need to go back and re-rip with 0.9.3 to get ATV to look good again....

baggss, what exact advanced opt string does you're preset used that you ripped encodes with for 0.9.4 ? Paste it here. If its baseline you do not have to worry and you're 0.9.4 encodes will work fine.

Shortcut: If you're custom preset works on a 5 or 5.5 G iPod I already know its baseline so you are good to go for the atv since hb automatically kills weightp on anything baseline, no need to mod presets.

[baggss]

My custom presets are pretty simple and are tailored to give me the best quality and still maintain the most compatibility. I don't have an ATV yet, but that will be changing shortly and I'd like to know what I need to go back and re-rip with 0.9.3 to get ATV to look good again....

baggss, what exact advanced opt string does you're preset used that you ripped encodes with for 0.9.4 ? Paste it here. If its baseline you do not have to worry and you're 0.9.4 encodes will work fine.

Shortcut: If you're custom preset works on a 5 or 5.5 G iPod I already know its baseline so you are good to go for the atv since hb automatically kills weightp on anything baseline, no need to mod presets.

level=30:bframes=0:cabac=0:ref=1:vbv-maxrate=2500:vbv-bufsize=2000:analyse=all:me=umh:no-fast-pskip=1:psy-rd=0,0:subq=6:8x8dct=0:weightb=0:mixed-refs=0

So I think I have nothing to worry about when I get my ATV....

[dynaflash]

level=30:bframes=0:cabac=0:ref=1:vbv-maxrate=2500:vbv-bufsize=2000:analyse=all:me=umh:no-fast-pskip=1:psy-rd=0,0:subq=6:8x8dct=0:weightb=0:mixed-refs=0

So I think I have nothing to worry about when I get my ATV....

Methinks you would be correct. Carry on.

[rpb]

/me goes to google " The egg of Columbus " ....

It's a German saying for a very good solution which is surprisingly simple...

[jediracer]

I also went back to 0.9.3.

[dynaflash]

For those of you that for whatever odd reason go back to 0.9.3 after having launched 0.9.4. . Remember to update you're built in presets once back in 0.9.3. 0.9.4 would have done it when you first ran it and there are significant changes which are not compatible when using 0.9.3 again.

[doctor-frog]

Right. So, just to confirm (because I really don't want to have to re-rip my whole DVD library again!),

I have just finished ripping my DVD movies using 0.9.4's Apple Universal pre-sets (x264 option string: "cabac=0:ref=2:me=umh:bframes=0:8x8dct=0:subq=6:weightb=0"), with no tweaking of settings or customising or other cute stuff - just click and rip. I've been doing this in anticipation of the Apple TV that Father Christmas will have in his bag for me (but with the idea of occasionally putting a film on the iPhone, too). if I'm reading you correctly, the presence of "bframes=0" should automatically turn off weighted P-frames ... so I should be all right and not have to go back and do the whole dang thing over again come Christmas Day?

[mattnad]

I'm also downgrading. I find the new interface cluttered with a less efficient gui. I now have to manage floating windows for preview and must do live preview to see effective changes in settings (like deinterlace) But the big issue are hangs and crashes that didn't happen with the older version (and yes I redid my presets in the new version). I appreciate the hard work of the developer community here but 0.9.4 is not quite fully baked.