Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

 
Conventions For Overcoming Riff/wave 32-bit Limit
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
njahnke
Posted: Apr 23 2013, 05:31 PM


Newbie


Group: Members
Posts: 2
Member No.: 24228
Joined: 17-September 08



having trouble finding discussion on this by searching the forum. i know that virtualdub writes pcm audio to avi files without being limited by the (2^32)-1 length limit in the riff header. then i can successfully read all of the audio data with other software such as ffmpeg. however i have less luck with avisynth's avisource() - the audio is cut off at the 32-bit boundary (something like 6 hours in for cd-quality stereo audio). does vdub simply write sequential 4 gb chunks? if so then that would explain the occasional incompatibility - some software doesn't look for more than one audio chunk. any insight on this would be appreciated. i'm not looking to solve a specific problem here, just curious what the conventions are and where incompatibilities arise. thanks.
 
     Top
phaeron
Posted: May 5 2013, 08:13 PM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



There's a base AVI segment and extension AVIX segments. I think in Avisynth you need an alternate import path to read the extended file, like OpenDMLSource or something like that (don't have the docs in front of me at the moment).
 
    Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
1 replies since Apr 23 2013, 05:31 PM Track this topic | Email this topic | Print this topic

<< Back to General Discussion