search for: opus_custom

...oking at how to run Opus at 44.1K. I have flexibility in the frame sizes of the unencoded audio, and packet sizes on the RF link. So, I was digging through the code, and I didn't see any attempt to measure in realtime the actual audio rate (makes sense, since this codec can work offline too). Opus_custom seems to be needed if you have a certain frame size constraint with low latency. I don't have that. I can use the stock frame sizes ( 120, 240, 480, 960, 1920, and 2880 sample/frame). My conclusion is that I could set up Opus for 48K (stereo), and in reality run it at 44.1K, as long as I use...

...rue ... and since Opus lowpasses at 20 kHz, if you run it at 44.1 you will always be lowpassing at 18 kHz, and you will never get grade-A quality no matter how many bits you spend. Ah yes, it low passes below Nyquist, so that's a thing. Though, 18KHz might be acceptable. > > And with Opus_custom is all that stuff recalculated? > > Yes, opus_custom adjusts its model to match the specified samplerate and frame size. So if one keeps the frame size stock (e.g. 480 samples, etc.) would it minimized the adjustments it makes? > > If I do need to go to opus_custom, it seems that i...

...13 06:23 PM, Marc Lindahl wrote: > So, I was digging through the code, and I didn't see any attempt to > measure in realtime the actual audio rate (makes sense, since this > codec can work offline too). What do you mean by "measure in realtime the actual audio rate"? > Opus_custom seems to be needed if you have a certain frame size > constraint with low latency. I don't have that. I can use the > stock frame sizes ( 120, 240, 480, 960, 1920, and 2880 > sample/frame). > > My conclusion is that I could set up Opus for 48K (stereo), and in > reality r...

...he actual audio rate (makes sense, since this >> codec can work offline too). > > What do you mean by "measure in realtime the actual audio rate"? Meaning using the CPU clock via time() to calculate the realtime data rate. Nevermind, it's a red herring. > >> Opus_custom seems to be needed if you have a certain frame size >> constraint with low latency. I don't have that. I can use the >> stock frame sizes ( 120, 240, 480, 960, 1920, and 2880 >> sample/frame). >> >> My conclusion is that I could set up Opus for 48K (stereo), an...

...quot; just "custom sample rate and frame size". I'll dig further now that you've pointed me in a direction. Thanks, -a On 7/6/15, 6:18 PM, Jean-Marc Valin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I believe what you want is called Opus custom (OPUS_CUSTOM in the > code). With that you can compile only the contents of the celt/ > directory and use it like the old CELT. > > Jean-Marc > > On 07/06/2015 06:48 PM, Andrew Lentvorski wrote: >> Is there a configuration or compile flag that lets me disable the >> SILK portion...

Is there a configuration or compile flag that lets me disable the SILK portion of the codec and use CELT only? I could have sworn that there is something, but I can't seem to find it in the mailing list archives. The application here is that I am attempting to update from the old CELT codec to OPUS. Unfortunately, the CELT codec was running *very* close to the CPU (MIPS32--80MHz) limit

...s: The option -DFORTIFY_SOURCE=2 should be -D_FORTIFY_SOURCE=2, as the macro has a leading underscore. In the autotools build it defines this if it is not already defined (m4/ax_add_fortify_source.m4). When custom modes are not enabled, the cmake build is nevertheless installing the include file opus_custom.h. This file is specific to custom modes and should only be installed if custom modes were enabled. It appears that the documentation is not being built or installed by the cmake build; the autotools build builds and installs the documentation by default unless configured with --disable-doc. The...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I believe what you want is called Opus custom (OPUS_CUSTOM in the code). With that you can compile only the contents of the celt/ directory and use it like the old CELT. Jean-Marc On 07/06/2015 06:48 PM, Andrew Lentvorski wrote: > Is there a configuration or compile flag that lets me disable the > SILK portion of the codec and use CELT only? >...

On Wed, Apr 10, 2019 at 5:30 PM Marcus Asteborg <xnorpx at outlook.com> wrote: > Hi Mark, > > Thanks for the feedback. > > By default CMake is building the static library in debug, to get other > things one has to explicit turn it on. > > Hi, By default CMake uses the "empty" build, which is used in combination with the environment variables CFLAGS and