I think i might have been not clear enough - I meant that container is absolutely Off-topic here, as we need *just* audio in vorbis (which ends up in files with .ogg extension). The confusion arise, because .OGG is sometimes used as a container (but, nowadays, it's rather good habit to store audio-video containers as .ogv), but what interest us for Orecch' is, in any case "plain" .ogg file of vorbis-encoded audio.

Hm, but I wasn't talking about advanced parameters for gstreamer, I just mean't parameters given to encoder (vorbis or whatever). But I may be talking nonsense here, as I'm not familiar with gstreamer too - so, let me ask you a question:
How do you encode captured audio into <whatever>? Are there some build-in encoders in gstreamer and you're using it, or you just pass result of whole pipeline to Vorbis encoder? If the latter, it's where I mean those advanced parameters should be passed.

If, OTOH, gstreamer handles everything (inc. encoding), I'm sure it also passes commands to encoder via gstreamer plugins (correct me if I'm wrong), and I would be pretty surprised, if gstreamer wouldn't allow to pass some additional parameters to encoder.

I think it would be very useful feature - for example, I'm quite experienced with codecs, formats, and audio parameters, but I don't have a clue about gstreamer, let alone being able to construct it's pipeline (for anything). That's why I would like Orecch' to handle all those things (and dbus, and so goes on), but let me pass some parameters to encoder itself.

AIUI, video that we get (and send) during video call, is already compressed for sending through internet (either by us if talking about what we send, or by another party, so we receive compressed one already). So a way to just plain save what we got (and final result of what we send, just before sending it into vast plains of net), could be all we need.

But, I agree, that it doesn't sounds like priority functionality in Orecch'.

/Estel

// Edit

Hey, thanks a lot for putting me into credits Even more thanks, for putting SPX as default encoding options - this small, brilliant codec really deserves it. NFC why someone could get idea that "it doesn't work well on windows", btw? Leaving alone fact, that windows is hardly a mark for quality (well, ext* also doesn't work "well" in windows ), Speex works well on my windows machine since day 1 (of Speex public releases). I can hardly even imagine, how some recorder audio file may "not work well" on some OS...

// Edit 2

Would it be possible, to allow choosing quality (either 8 kHz or 16 kHz, IIRC) for speex?