HandBrake

Interesting - I don't have a 3GS so I could only go from user feedback.

I will assume High and update accordingly.

Rodney

They can do main, I don't think they can do high.

Rodney

It should sync all the way up to 29.97, BTW (but not a single frame/sec beyond that!).

Rodney

I guess this says it all about the ATV decoder (from the x264 changelog):

All weightp modes may cause minor breakage in non-compliant decoders that take shortcuts in deblocking reference frame checks.

Rodney

How strange. The whole point of weightp was that it was supposed to help fades. Urk. :/

Rodney

Haven't seen this particular manifestation, but it's almost certainly an overheating issue - the elegance of Mac case design seems to invariably lead to this under any sustained high CPU utilization scenarios (which apparently Steve believes Mac users never have use for).

Rodney

If you are compiling your own, you should compile both. On Windows, the GUI is only the presentation layer, and the CLI is the underlying engine - many bugfixes apply to one or the other but never both, so you must keep both up to date to take advantage of improvements and corrected defects. (Please...

-t 0 will return a title scan, from which you could use a bit of logic to derive the title list you want to convert (avoiding very short titles, etc).

I suspect, however, you may be reinventing the wheel here. This has been explored by various users many times already.

Rodney

Honestly, it would have been more helpful if you had simply tried my suggestion, because you are changing parameters seemingly at random and thus will find it very difficult to isolate root cause.

Rodney

0-1 is the encoding quality, which means eac3to doesn't support Nero's bitrate mode, only CQ.

As stated previously, Nero knows nothing about Dolby Pro Logic - if eac3to doesn't offer that downmix, it won't be possible with that toolchain.

Rodney

You didn't provide any logs, but I'm willing to bet you were using bitrate-constrained encodes on 0.9.2 (the default) and CQ/CRF-constrained encodes on SVN (the default). The two are apples and oranges - one is strictly limited by bitrate sacrificing quality, the other is limited to perceived qualit...

See if you still have audio playback problems using VLC as a player.

Rodney

NeroAACEnc definitely supports bitrates (in one or two passes), but does not do DPL(2).

You can use HandBrake to encode the video track to a crazy-low resolution and bitrate using the ffmpeg codec (to minimize time waste) and then pull out the AAC track and remux.

Rodney

You must decrypt your source first - make sure you have VLC 0.9.x+ in /Applications (not ~/Applications!) and make sure you have run it manually to view a DVD at least once to bypass Mac OS security restrictions.

Rodney

Try the latest development snapshot.

Rodney

Da Man wrote:While most people agree rhester's ignorance is amazing (in some circles it has been reported to be legendary), about AVI he is correct.

Wow.

Rodney

The latest mp4chaps does not exhibit the length issue when adding chapters to iTunes content. A fix is also in mp4creator's svn.

Rodney

AAC input is broken on Windows on 0.9.3. Give the latest development snapshot a try.

Rodney

The "glitchy symbols" you reported suggest DVD43 isn't doing the job.

Rodney

Joining content is a dicey business and impossible for VFR content. Chapters would have to be added after-the-fact with a tool like mp4chaps, assuming you have the original chapter data available in OGG format. Long story short, you are almost certainly much better off letting the thing encode throu...

If you aren't sure, use the GUI.

Rodney

Not sure what sort of guide you are following, but the first paragraph of the Windows documentation explains that you must decrypt the source DVD prior to encoding.

Rodney

Can we even get a hint? What version? Activity log?

Rodney

They talk about audio codecs but video containers - they clearly seem to support MPEG-4 video but it is not clear whether they support H.264.

I might recommend trying the iPod preset(s) first with single-chapter encodes and go from there.

Rodney

Are you having some sort of character set issue? The letter after "av" in your command line is definitely not an "i".

Rodney