search for: opus_multistream_encode_float

I just recently found that opus_multistream_encode_float is returning -1 (OPUS_BAD_ARG) with the libopus 1.1 build but works just fine with the libopus 1.0.1 and libopus 1.1-beta builds. I tried using opus_multistream_encoder_create and opus_multistream_surround_encoder_create. Tried with coupled and uncoupled quadraphonic and uncoupled stereo encodes....

On 2014-06-02 11:51 PM, Alpha Thinktink wrote: > Have there been changes to the meaning or handling of the parameters > for either of the mentioned functions? Hmm. There shouldn't have been between 1.1-beta and release. I guess you can't tell us which argument is bad because the win32 binary is stipped. Have you tried compiling it yourself? -r

On 2014-06-04 12:47 PM, Alpha Thinktink wrote: > 1>------ Build started: Project: opus, Configuration: Release Win32 ------ > 1> fatal: Not a git repository: 'C:\My Documents\Opus\win32\..\.git' > 1> The syntax of the command is incorrect. > 1> The system cannot find the path specified. > 1>C:\Program

On 2014-06-04 1:25 PM, Alpha Thinktink wrote: > Ok, this seems contradictory to the output that the build log is > telling me. The log is showing a fatal error and the build doesn't > succeed. You're right. Doesn't work on the libopus-1.1 source tarball. Sorry about that! -r

Finally got it to compile and attach the MSVC debugger. It fails at the following: if ((!st->variable_duration && 400*frame_size != st->Fs && 200*frame_size != st->Fs && 100*frame_size != st->Fs && 50*frame_size != st->Fs && 25*frame_size != st->Fs && 50*frame_size != 3*st->Fs) || (400*frame_size <

Alpha Thinktink wrote: > max_data_bytes=-11 That value is passed in by you. I also don't think passing such a value would have worked in earlier releases. It indicates the size of the buffer you are passing to the encoder to receive the encoded output.

On Wed, Jun 4, 2014 at 4:41 PM, Alpha Thinktink <alphathinktink at gmail.com> wrote: > > >> max_data_bytes=-11 > This can happen with multistream cbr if the bitrate is set too low, to a value that would allow less than 4 bytes per stream, per packet. What bitrate are you using? Perhaps you set it to a value in kb/s instead of b/s. -------------- next part -------------- An

In debugging I saw: opus_multistream_encoder.c line 760 if(!vbr) max_data_bytes = IMIN(max_data_bytes, 3*st->bitrate_bps/(3*8*Fs/frame_size)); max_data_bytes after this code becomes -2 where as before it was 10200. I suspect it was because st->bitrate_bps was set to -1000 to indicate Auto bitrate. I imagine Max bitrate (-1) has a slightly similar effect. then in the same c file

Hi, I just checked in a fix for the bug you reported. Let me know if it works. Cheers, Jean-Marc On 05/06/14 12:41 AM, Alpha Thinktink wrote: > In debugging I saw: > opus_multistream_encoder.c > line 760 > if(!vbr) > max_data_bytes = IMIN(max_data_bytes, > 3*st->bitrate_bps/(3*8*Fs/frame_size)); > > max_data_bytes after this code becomes -2 where as

On Wed, Jun 4, 2014 at 4:31 PM, Timothy B. Terriberry <tterribe at xiph.org> wrote: > Alpha Thinktink wrote: >> max_data_bytes=-11 > > That value is passed in by you. I also don't think passing such a value > would have worked in earlier releases. It indicates the size of the > buffer you are passing to the encoder to receive the encoded output. Actually, I'm

> Have you tried compiling it yourself? I just installed git for the first time and downloaded all of the latest source code packages directly from the site. I'm getting the following every time I try to (re)build any of the projects: 1>------ Build started: Project: opus, Configuration: Release Win32 ------ 1> fatal: Not a git repository: 'C:\My

> > This is as expected. The build system is trying to get a git revision > string out of the source tree to compile in for reference. If you're > building from a downloaded source .zip, there won't be any git > information available and it will fall back to the hard-coded release > string. That's why the error isn't fatal to the build. Ok, this seems

...and so on. Ahh, I see. Thanks for the explanation. It's sort of the opposite of what I'd expect. I'd expect mapping[stream_index] = vorbis_index, but it's actually mapping[vorbis_index] = stream_index. And so I guess that means that the interleaved audio samples you pass into opus_multistream_encode_float() should always be in Vorbis order, and mapping[] just tells the encoder how to package them in the streams? Brendan

...two mono streams over network with RTP. I think I'm right when I create an OpusMsDecoder with opus_multistream_decoder_create (48000, 2, 2 ,0 ,mapping, NULL) where mapping is: unsigned char mapping[2] = {0,1} isn't it ? Next, i need to encode data which I get from jack (float) so I use opus_multistream_encode_float(enc, data, 480 , encodedData, MAX_DATA) Then I send it using RTP. My question is how can I make the opposite in the client. I created my decoder with m_decoder = opus_multistream_decoder_create (48000, 2, 2 ,0,mapping,NULL) and unsigned char mapping[2] = {0,1}; Currently, I can read my RTP packe...

I get reliable crashes if I create a 6-channel encoder using opus_multistream_surround_encoder_create(). If I use opus_multistream_encoder_create() instead and pass in the same parameters that opus_multistream_surround_encoder_create() sends out (streams = 4, coupled_streams = 2, mapping = {0, 4, 1, 2, 3, 5}) I don't get the crashes. I notice that opus_demo.c uses

...it seems backwards if you're thinking about encoding. It may help to think of it as opus_multistream_surround_encouder_create() returning what you have to pass to the decoder to understand the stream configuration. > And so I guess that means that the interleaved audio samples you pass into opus_multistream_encode_float() should always be in Vorbis order, and mapping[] just tells the encoder how to package them in the streams? I believe that's correct, yes. -r

Hey everyone, I've added Ogg Opus support to my Adobe Premiere plug-in here: http://github.com/fnordware/AdobeOgg Now I'll add Opus support to me WebM plug-in too. I've got this Opus stuff mostly figured out, but I have a few questions. Here's one: What do the numbers in mapping mean? I see that opus.h refers to the Vorbis channel mapping order, so does mapping in Opus take

...reference to `ogg_stream_flush' /home/user/source/opus-tools/src/opusenc.c:746: undefined reference to `ogg_stream_packetin' /home/user/source/opus-tools/src/opusenc.c:750: undefined reference to `ogg_stream_flush' /home/user/source/opus-tools/src/opusenc.c:796: undefined reference to `opus_multistream_encode_float' /home/user/source/opus-tools/src/opusenc.c:814: undefined reference to `opus_multistream_encoder_ctl' /home/user/source/opus-tools/src/opusenc.c:815: undefined reference to `opus_encoder_ctl' /home/user/source/opus-tools/src/opusenc.c:864: undefined reference to `ogg_stream_packetin...