Sebastian Mares
Oct 31 2006, 09:38
Hey guys!
Wanting to test foobar2000's "Convert to Album Images with Cuesheets or Chapters" function, I encoded a WV+CUE file to MP4 using the Nero Digital encoder, Target Quality, Q0.40. The file plays back fine in foobar2000, but with QuickTime, it sounds like a flanger effect is on. Is this a bug?
Regards,
Sebastian
QUOTE(Sebastian Mares @ Oct 31 2006, 07:38)

Hey guys!
Wanting to test foobar2000's "Convert to Album Images with Cuesheets or Chapters" function, I encoded a WV+CUE file to MP4 using the Nero Digital encoder, Target Quality, Q0.40. The file plays back fine in foobar2000, but with QuickTime, it sounds like a flanger effect is on. Is this a bug?
Regards,
Sebastian
Is it because Q0.40 encodes as HE-AAC? Don't think QuickTime supports this. Higher Q will switch to LC-AAC automatically.
Q 0.4 is not HE-AAC. It provides bitrates around 130 kb/s.
QUOTE(tycho @ Oct 31 2006, 16:55)

Is it because Q0.40 encodes as HE-AAC? Don't think QuickTime supports this.
HE-AAC is fully backwards compatible with LC-AAC.
Of course, given this thread, it's possible QuickTime doesn't even support AAC properly at all.
Sebastian Mares
Oct 31 2006, 10:54
Sebastian Mares
Oct 31 2006, 11:20
I also posted a lossless version of the source. Could someone please encode and test with QuickTime? I would like to exclude my PC for causing this problem.
Seems like a problem in QuickTime, iTunes plays it correctly.
I'll try to get someone at Apple to look at it.
Sebastian Mares
Nov 2 2006, 08:38
I think this is weird - doesn't iTunes rely on QuickTime for decoding?
QUOTE(Sebastian Mares @ Nov 2 2006, 15:38)

I think this is weird - doesn't iTunes rely on QuickTime for decoding?
It only did for .MP4 files, but not anymore it seems. Or there is something wrong with QuickTime after the decoding.
Time for a thread resurrection
Someone from Apple looked at the file. It seems that there is a discrepancy between the given length of the stream (written inside the file) and the sum of all sample lengths. This makes quicktime go into some sort of "I have to fix this" mode by guessing that there had been some sort of edit.
This is a bug we fixed a while ago in our encoder, should be fixed with the next release. Most players probably just use the stream length as info for the user and don't check it with the samplelengths. Seems that Quicktime is a bit more advanced.
loophole
Jun 27 2007, 07:36
Ahh good I experienced this too under OS X using wine to run the cli encoder - ended up using VLC to play back. When will this find it's way into the free command line encoder?
Sebastian Mares
Jun 27 2007, 09:29
Thanks for the update menno.
menno,
I've been experimenting with Nero's (Feb 12 2007 v. 1.0.0.2) encoder. I also own Nero 7 Ultra Edition which has its own version of the encoder (May 11 2007). When I encode files with the 2 different versions, I am getting 2 different file sizes and bitrates.
What are the differences between the freeware CLI version and the plugin included with Nero 7 Ultra Edition?
Thanks,
John
Sebastian Mares
Jun 27 2007, 15:26
Sorry, but what does this have to do with the Nero and QuickTime incompatibility that this thread is about?
OT: The guys @ Apple are pretty quick. Solving this problem only took 8 months.
QUOTE(Sebastian Mares @ Jun 27 2007, 17:26)

Sorry, but what does this have to do with the Nero and QuickTime incompatibility that this thread is about?
Sebastian, you're right about that. I apologize for the OT post.
John
QUOTE(loophole @ Jun 27 2007, 15:36)

Ahh good I experienced this too under OS X using wine to run the cli encoder - ended up using VLC to play back. When will this find it's way into the free command line encoder?
We plan an intermediate release for the 64 kbps test soon (this will only encode at 1 -q value). Full release will hopefully be possible not too long after that.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.