saving to single files per track

[elieserdejesus]

Ezee, single file per track is possible and a usefull feature. If we genearte a single file Jamtaba users can import these files in every DAW to mix the jam. I think the best option is put a check box to "[ save single file per track ]" or not, so we keep the current code and add the "single file per track" feature.

[elieserdejesus]

@pljones commented in #444 (comment)

I think it would also be possible to have a writer that had a single WAV per track, too, which might be more useful to non-Reaper users. However, this would have to change where the audio data comes from - i.e. before encoding for local and after decoding for remote. I'd probably need a while to work out how much change was needed to see if this was a realistic idea...

@pljones , I think is better just send the remote ogg vorbis data to the new "WaveFileWriter" (the current approach), this new writer can decode the ogg and save to wav file. No need to change other places.

Get the raw local audio is more trick, it's necessary add some code.

[jonjamcam]

I think is better just send the remote ogg vorbis data to the new "WaveFileWriter" (the current approach), this new writer can decode the ogg and save to wav file. No need to change other places.

@elieserdejesus @pljones I like this idea for compatibility with other DAW, but I have to raise concerns that .ogg files are lossy compression, contrary to traditional wav files (if this is the intended format to use) that are not compressed at all.

This is important issue because you do not get any more quality out of a lossy file unless you do some kind of post processing, which is not the case discussed here, but the file size can be ten or more times bigger.

So I suggest two options in this case:

1.- create "lossy" wav files (keeping the compression and using wav as a header only).

2.- keep .ogg file extension and create full length audio files.

IMO option 2 is the best one for compatibility. An .ogg file with wav header may not be recognized by some DAW.

Get the raw local audio is more trick, it's necessary add some code.

Well this is the best option because you get the data before the compression and in this case the sound will be perfect for mixing later.

[elieserdejesus]

@jonjamcam

2.- keep .ogg file extension and create full length audio files

I like this idea. It's simple to implement, but I'm not shure if other DAWs like .ogg files. I never tried import ogg in another DAWs. I suppose DAWs are ogg compatible, but I'm not shure.

At moment the local audio is passed to JamRecorder after encoded in ogg vorbis format. If we decide generate big oggs the easy approach is just keep the current design and "concat" all ogg encoded local audio in a big ogg file.

I think the compressed audio quality it's not a real issue for the local audio because all the remote tracks will be ogg vorbis encoded. So, if we have 8 remote ogg vorbis encoded streams mixed with 2 raw local streams the quality difference will be not noticeable.

My vote is to keep the current design and just join the ogg pieces in big ogg files, and use this approach for both local and remote audio.

[jonjamcam]

I've tested importing .ogg files in reaper only with no problems.

It looks like cubase (cubasis?) is compatible too:
http://www.steinberg.net/fileadmin/files/PRODUCTS/Apps/Cubasis/Cubasis_Help/MEDIA.html

http://www.steinberg.net/index.php?id=83&L=1

Studio one accepts ogg files too for import:

http://www.soundonsound.com/sos/apr10/articles/studioone.htm

I think the compressed audio quality it's not a real issue for the local audio because all the remote tracks will be ogg vorbis encoded. So, if we have 8 remote ogg vorbis encoded streams mixed with 2 raw local streams the quality difference will be not noticeable.

In my own experience that varies depending on the instrument. For drums (specifically cymbals) if you have a raw, uncompressed files the sound is very different during mixing. The stereo image of high frequency sounds is degraded considerably using low bandwith lossy compression in the case of old RENINJAM (Jamtaba's quality is much better and since using it this is not a big problem anymore).

My vote is to keep the current design and just join the ogg pieces in big ogg files, and use this approach for both local and remote audio.

Me too 👍