similar to: opus_multistream_encode_float not working in libopus 1.1

Displaying 20 results from an estimated 400 matches similar to: "opus_multistream_encode_float not working in libopus 1.1"

2014 Jun 04
2
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
2014 Jun 04
3
opus_multistream_encode_float not working in libopus 1.1
> > 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
2018 Sep 10
15
[7.0.0 Release] rc3 has been tagged
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
2014 Jun 04
0
opus_multistream_encode_float not working in libopus 1.1
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
2014 Jun 03
0
opus_multistream_encode_float not working in libopus 1.1
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
2014 Jun 21
1
opus_multistream_encode_float not working in libopus 1.1
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
2014 Jun 04
4
opus_multistream_encode_float not working in libopus 1.1
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
2014 Jun 04
0
opus_multistream_encode_float not working in libopus 1.1
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
2014 Jun 04
3
opus_multistream_encode_float not working in libopus 1.1
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 <
2014 Jun 04
0
opus_multistream_encode_float not working in libopus 1.1
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.
2014 Jun 05
0
opus_multistream_encode_float not working in libopus 1.1
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
2014 Jun 05
0
opus_multistream_encode_float not working in libopus 1.1
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
2012 Oct 19
3
How to cross-compile opus-tools?
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
2013 May 17
1
Windows Pathnames with spaces in Puppet file directive
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 =>
2018 Sep 21
2
can't build/run after adding lib to Fibonacci example, even reverting the complete llvm tree does not help
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
2013 Dec 17
0
1.1 Much slower on Raspberry Pi
Hi Stuart, you are compressing it at 6kbit/s. Then, then SILK mode is probability used and the Silk mode is much faster than CELT. Do you also some figures at 64kbit/s? It is strange that Opus 1.1 got slower in the Silk mode - may the speech/voice selection adds some overhead. I would be interested in seeing the performance of the 64 kbit/s in both Opus 1.0 and Opus 1.1. With best
2002 Jul 13
0
libvorbis make and spec fixes
I had to change the following to get the 'make distcheck' to work and to be able to build the rpms with 'rpm-build -tb *.tar.gz' I also added a test in libvorbis configure.in to detect older ogg versions (check for oggpack_writealign) and print a meaningful error. I also updated the .spec-file with dependencies on libogg-1.0 Thanks for great work everyone! /noa -- begin:vcard
2015 Apr 02
1
Opus multi-stream/surround: Audio corruption on decoded content
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
2013 Dec 16
4
1.1 Much slower on Raspberry Pi
I have just started trying Opus with a view to using it in a project. I am interested in embedded hardware and tried it on the Raspberry Pi using the raspbian distro. The version of libopus in the repos is 0.9.14. I installed this and tried encoding 2 minutes of speech from a librevox recording. It managed this at a respectable pace for complexity 10: Skipping chunk of type "LIST",
2013 Dec 17
0
1.1 Much slower on Raspberry Pi
Resampling to 48khz speeds them both up but the disparity is about the same: 2.609 to 3.69. Best Regards, Stuart Marsden On 17 December 2013 17:04, Stuart Marsden <stuartmarsden at finmars.co.uk>wrote: > Christian, > > Complexity 0, 6kbps: > > 0.9.14 Speed 5.204 > 1.1 Speed 5.218 > > A slight win on that run but they vary enough to say about the same. At >