Hello!

neroAacEnc didn't support large file under Linux. I try to encode file temp.wav with size 2,261,120K bytes but neroAacEnc report error:
ERROR: could not open WAV file

The command is:
# neroAacEnc -br 48000 -2pass -if temp.wav -of temp.aac

My configuration:

# neroAacEnc --help
Nero AAC Encoder
Copyright 2008 Nero AG
All Rights Reserved Worldwide

Package build date: Sep 17 2008
Package version: 1.3.3.0

# uname -a
Linux localhost.localdomain 2.6.18-92.1.10.el5 #1 SMP Tue Aug 5 07:42:41 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

Hmm, that's the error you get when fopen() fails... do smaller files work properly?
Normally I would say, try adding -ignorelength to the command line, but I guess that will not help much (you should try it anyway ).


And on a sidenote, neroAacEnc creates files in the MP4 container, so you probably should not call them .AAC as players will get confused about that.

Small files works great! I encode all of my xvid videos collection to h.264 and almost all files encoded well, but files with great than 2gb can't open.
-ignorelength options also didn't help. I try it before your post and almost all combination of options.

I think that problem in integer types in neroAacEnc so encoder can't open files larger than int32.

I also submit support ticket about that error to nero ag from nero.com site.

If you need any tests I ready to do.

Thanks.

http://en.wikipedia.org/wiki/Large_file_support

http://www.suse.de/~aj/linux_lfs.html

I suppose the neroAacEnc is a 32bit executable.

It's not really a problem in the Nero AAC Encoder (for which Nero doesn't offer any support, so your support ticket will probably not get answered), but in the underlying file system.
I will check for next version if we can add large file support.

You don't need a 64bit application to read a "large file", simply because the encoder does not need to have it all in memory.

Since the message is that it cannot open it, and menno suggests this in in the fopen call, it may have to do with the fopen call itself, and its structures.
This can be, since you usually can ask for the length of the file, and that usually returns an int.
(and note that int is still 32 bits in 64bits applications)

Well, the 2 gig / 4 gig restriction seems typical of fopen with regular 32bit binaries.

True, but for that, there are new methods, which don't require to compile in 64 bits (actually, the link to wikipedia you provided dealt with this briefly)

http://www.mkssoftware.com/docs/man3/fopen.3.asp