Conquistador.
acousmodHi Frits,
Podium actually doesn’t seem to like files which are bigger than 2 Go.
Can you bypass this limit in the next update ?
I’m preparing my work to be ready for : http://www.zynewave.com/forum/viewtopic.php?t=387 , but I can’t import some of my files (they work fine in Nuendo or Bidule).
Thanks.
ZynewaveI’ll check it out.
ZynewaveAfter doing some tests and searching the internet:
The 2GB limit is a restriction in the Microsoft routines I am using for writing chunks in Wave files. The routines simply will not write or read anything beyond 2GB. The wave file format theoretically allows file sizes up to 4GB, but to support this it appears I will have to write my own file routines for handling chunks in wave files. I found a discussion about this limit, which appears to be a problem in many applications:
http://www.hydrogenaudio.org/forums/index.php?showtopic=32422
From searching the internet, I found a couple of solutions to the 4GB file limit. One is the ‘Broadcast Wave Format’ which has a ‘link’ chunk that can associate several wave files into one continuous file. Another solution is the ‘RF64’ format, which is a modified wave file format, that can save >4GB in one file. The RF64 format can however only be read by applications that support it. I believe I read that e.g. Nuendo is supporting this format.
The conclusion is that there is some work involved in supporting this, so for now I’ll put it on the plan.
acousmodThe conclusion is that there is some work involved in supporting this, so for now I’ll put it on the plan.
Thanks for the researches, I will differ this project…
Concerning the format, I don’t know : I had forgotten to tell you that the files that I use are multichannel wave files which have been made with Nuendo and Bidule. In Bidule there is no option for the Broadcast Wave Format and in Nuendo the files result from a direct multichannel record, they are not saved from a bounce in Broadcast Wave format.
Perhaps that the WaveFormatExtensible have a direct support for files more than 2 Go ?
Do you use it or a regular wave file format ?
I know that Bidule automatically uses it.
ZynewaveIn the header of all wav files is a 32 bit value that tells the bytesize of the file. This number cannot be larger than 4GB. Bidule may support wave files larger than 2GB, but smaller than 4GB. The RF64 format is an extension of the wav format, where a 64 bit value is used to tell the bytesize of the file. The actual type of the wave file or the number of channels is unrelated to this problem.
acousmodBidule may support wave files larger than 2GB, but smaller than 4GB.
So do you think that Podium would be able to support too the 4GB wave files without having to program the support for other formats like Broadcast Wave or RF64 ?
4 GB is sufficient for me up to now 😉
ZynewaveSo do you think that Podium would be able to support too the 4GB wave files without having to program the support for other formats like Broadcast Wave or RF64 ?
Yes. That would be step 1. It is on the plan.
ZynewaveAnd a year later… (had to use search to find this topic 🙂 )
In the ongoing effort to optimize disk streaming, I have now replaced the Windows support routines I used for accessing Wave files with my own routines. Thus it is now possible to save standard wave files up to 4 GB.
I also did some further research on >4GB file formats. The format supported by e.g. Cubase/Nuendo and Sony products is using the Wave64 format. This is incompatible to standard Wave files and uses .w64 as file extension. Instead I chose the simpler solution that the ‘RF64’ format offers. This uses the format of a Wave file, but has an additional chunk in the file that specifies 64bit information needed to address beyond 4GB. It is therefore irrelevant for the user whether a wave file is larger or smaller than 4GB.
For technical background on the RF64 format:
http://www.ebu.ch/CMSimages/en/tec_doc_t3306-2 … -42570.pdf
Will be available in Podium 1.63.
PodianerThis sounds great. I never had such huge files, but for multi-channel waves, this will make a big difference.
Are there any other sides to the disk streaming that you are going to optimize?
Looking forward to 1.63
ZynewaveAre there any other sides to the disk streaming that you are going to optimize?
Plenty. This update of the wave file format support does not really optimize speed, but it is required for future optimizations.
acousmodExcellent news Frits !
This one will come perfectly in time for me for the export of a 29′ / 24 bits / 18 channels project.
Thanks a lot for your continuous works.
Conquistador@Zynewave wrote:
Are there any other sides to the disk streaming that you are going to optimize?
Plenty. This update of the wave file format support does not really optimize speed, but it is required for future optimizations.
Glad to read that disk streaming optimizations are top of the pile for now. It wil be great if I can finally rely on Podium for reliable playback again without dropouts. Thanks for looking into this. Definitely looking forward to 1.63.