Log in

View Full Version : Which AAC encoders support simultaneous encoding?


MOverride
14th September 2009, 04:35
I've just moved up from a P4 HT to a brand spanking-new Core i7. I'm quite impressed with how much faster it is with encoding, especially when I'm running on three cores at once.

However, while x264 will happily encode on three cores at once, NeroAacEnc won't--the resulting AAC files are trash, either no audio or static.

Is this a problem with how MeGUI invokes NeroAacEnc, or with the latter's own behavior? Is there a multiple-invocation-safe AAC encoder supported by MeGUI?

Thanks for any information you can provide!

MeGUI: 0.3.1.1051
NeroAacEnc: 1.3.3.0

RunningSkittle
14th September 2009, 12:22
use search!
foobar2000
or http://forum.doom9.org/showthread.php?p=920811#post920811
etc

MOverride
15th September 2009, 00:58
use search!
I tried and didn't come up with any useful results.

foobar2000
or http://forum.doom9.org/showthread.php?p=920811#post920811
etc
Huh. So it probably is MeGUI's fault, if LameXP supports NeroAacEnc properly. Unfortunate.

Thanks for the information.

Doom9
15th September 2009, 23:43
the way I read that linked thread is that it's a frontend that allows for parallel encoding of separate files - the same can be achieved using worker threads in megui.

and the output has probably something to do with filters.. it's one of the most common problems with megui (not that it's megui's fault though.. )

LoRd_MuldeR
15th September 2009, 23:55
the way I read that linked thread is that it's a frontend that allows for parallel encoding of separate files

Exactly :)

RunningSkittle
16th September 2009, 12:48
yes, trying to encode multiple audio sources just errors out in megui. it only does this with nicaudiosource. if you force decoding with directshow it works again :)

MOverride
17th September 2009, 23:34
and the output has probably something to do with filters.. it's one of the most common problems with megui (not that it's megui's fault though.. )
It's possible, though given that this happens to me on a fresh Windows install with no DirectShow filters installed beyond whatever AviSynth, MeGUI, and VLC bring along for the ride (no codec packs or anything like that installed), there's very little chance to avoid filter issues if that's the problem.

Maybe something in the AviSynth script that MeGUI assembles isn't threadsafe... That would suck.

MOverride
18th September 2009, 00:01
Maybe something in the AviSynth script that MeGUI assembles isn't threadsafe... That would suck.
And it seems to be the downsampling to stereo, since when I turn that off it works fine. Hmm. Well, thanks for sending me down the path of thinking to try turning off the filtering options, doom9, even if I don't have a fix in hand. :)

(No, DirectShowSource isn't one for me, since that... well, it either takes forever or it just locks up at "Preprocessing" with no useful log entries to debug. Hard to tell.)

click2
21st September 2009, 05:54
Megui's preprocessing takes a while (with no progress bar), but it gets there in the end. Are you sure it's locking up?

MOverride
21st September 2009, 23:10
Megui's preprocessing takes a while (with no progress bar), but it gets there in the end. Are you sure it's locking up?
I let it preprocess for a half-hour, which is about five times as long as it takes to do a complete file (preprocess and process) without "Force DirectShow" checked. That sure looks like a hangup to me...