similar to: opus_multistream_encode_float not working in libopus 1.1

> 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

Dear testers, 7.0.0-rc3 was just tagged (from branch revision r341805). No further release candidates are currently planned, so this is a release candidate in the real sense: unless any serious issues surface, this is what the final release will look like. Please run the test script, share your results and upload binaries. Please also take a look at the release notes and other docs; small

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-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

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

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 Is it possible to cross-compile opus-tools with mingw and Ubuntu? So far I have done this:- # prepare $ mkdir $HOME/source $ mkdir $HOME/builds $ export PATH="$PATH:$HOME/mingw-w64-i686/bin" $ PKG_CONFIG_PATH="$HOME/builds/lib/pkgconfig" # Install ogg $ cd $HOME/source $ svn co http://svn.xiph.org/trunk/ogg $ cd ogg $ ./autogen.sh && ./configure

I have to change a file in c:\Program Files <x86>\MSBuild\Microsoft.Cpp\v4.0. I have tried various ways to encapsule the Windows path with spaces but to no avail. The following file { "\"c:\\program files <x86>\\MSBuild\\Microsoft.Cpp\\v4.0\\Microsoft.CppCommon.targets\"": ensure => present, source =>

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

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) x64 Native Tools Command Prompt for VS 2017 directory structure: test     llvm <-- git clone https://github.com/llvm-mirror/llvm, git checkout release_70       tools         clang <-- git clone https://github.com/llvm-mirror/clang, git checkout

Hello Everyone, I am using the opus 1.1 multistream APIs to encode a 5.1 surround stream on the server, stream it to client, decode it and capture the pcm data. I noticed that there was severe corruption/attenuation on one of the channels(specifically Back/Rear Right). This would appear to be the last channel in the stream. I am attaching an image of the PCM dumps from the original and the one

I realize this is probably the wrong list but since some of the principals this list deals with are similar in nature I figured it could't hurt. What I am looking to do: Provide a solution to either boot from a floppy disk, establish a network connection, give user the ability to run utilities such as fdisk and dd. as well as provide the same solution as a PXE bootable image. My

On Jan 6, 2014, at 11:54 AM, Ralph Giles wrote: > The first entry, mapping[0], > describes front left and contains the value '0', so that speaker is the > left channel of the first coupled stream. mapping[1] is '4', so the > front centre speaker is given the first mono stream. mapping[2] is '1' > so the front right speaker gets the right channel of the first

Hi, I don't understand how works the multi stream api in opus. I need to send 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