Displaying 20 results from an estimated 400 matches similar to: "API for checking whether the encoder is in DTX (PR #107)"
2019 Apr 08
3
API for checking whether the encoder is in DTX (PR #107)
Thank you Mark.
I agree and have now updated the pull request with a new commit, addressing
your comments.
Please take a look.
/Gustaf
On Fri, 5 Apr 2019 at 11:41, Mark Harris <mark.hsj at gmail.com> wrote:
> On 2019-04-01 3:37, Gustaf Ullberg wrote:
> > Hi everyone,
> >
> > Some time ago, I sent a pull request
> > <https://github.com/xiph/opus/pull/107>
2019 Apr 05
0
API for checking whether the encoder is in DTX (PR #107)
On 2019-04-01 3:37, Gustaf Ullberg wrote:
> Hi everyone,
>
> Some time ago, I sent a pull request
> <https://github.com/xiph/opus/pull/107> to the Opus github page.
> Jean-Marc asked me to post it to the mailing list so everyone can have a
> look at it.
>
> You can find the description and code changes below. Please let me know
> if you have any questions or
2017 Jul 06
1
Suggested patch, opus_encoder.c, decide_dtx_mode()
While porting opus 1.2.1 to esp32, my compiler had a grumble (error) about
possible use of uninitialized variables in decide_dtx_mode()
Existing code:
--------SNIP---------
/* Decides if DTX should be turned on (=1) or off (=0) */
static int decide_dtx_mode(float activity_probability, /* probability
that current frame contains speech/music */
int
2019 Apr 10
2
API for checking whether the encoder is in DTX (PR #107)
Yes, good point. I added the checking of prev_mode for Silk DTX to avoid
using stale data from the Silk state.
The PR is updated, and I'm attaching an updated patch.
/Gustaf
On Tue, 9 Apr 2019 at 12:42, Mark Harris <mark.hsj at gmail.com> wrote:
> On 2019-04-08 4:55, Gustaf Ullberg wrote:
> > Thank you Mark.
> >
> > I agree and have now updated the pull request
2019 Oct 30
5
Q: Bandwidth vs. bitrate
Hi!
I have some MP3 audio material which is basically speech with some background noises, essentially > 120Hz and < 5kHz.
I had the idea to reduce the file size by recoding the material to Opus at 56kbps. Unfortunately the result is a file sampled at 48kHz much larger than the original.
I hope you agree that it does not make sense to create a file larger than the original (MP3). Of course
2019 Oct 31
1
Antw: Re: Q: Bandwidth vs. bitrate
Hi!
Useful advice, thanks! Actually I had been using foobar2000 to recode, because it just makes it so easy to convert multiple files while keeping the metadata (I confess, I'm a "tagger"). But it's easy to miss some encoder option when being presented some default suggestions in a dialog form...
Apart form that I always had the impression that Opus could be quite smart
2015 Feb 24
2
Questions regarding OPUS_APPLICATION_AUDIO vs OPUS_BANDWIDTH_NARROWBAND
I have an audio device whose 'driver' gives me Opus encoded frames using
OPUS_APPLICATION_AUDIO and max bandwidth set to OPUS_BANDWIDTH_NARROWBAND.
How does Opus encoder decide the center point of the 4K bandpass filter?
Is it done frame by frame?
--
Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2019 Dec 04
0
Bugfix for OPUS_GET_IN_DTX
We (WebRTC) found a bug in the current implementation of
OPUS_GET_IN_DTX and I just created a pull request for a fix on the
Opus GitHub page. It would be great if maintainers could take a look.
https://github.com/xiph/opus/pull/156
Patch attached.
Best regards
Gustaf
>From the PR:
The current implementation of OPUS_GET_IN_DTX does not properly handle
the case when only the middle channel is
2016 Aug 26
2
[PATCH 9/9] Optimize silk_inner_prod_aligned_scale() for ARM NEON
Created corresponding unit test, and the optimization is bit exact with C
function.
---
silk/SigProc_FIX.h | 7 ++-
silk/arm/arm_silk_map.c | 12 ++++
silk/arm/inner_prod_aligned_arm.h | 58 +++++++++++++++++++
silk/arm/inner_prod_aligned_neon_intr.c | 66 ++++++++++++++++++++++
silk/enc_API.c
2001 Nov 04
8
Connection problem
I've got a test lab set up and im having problems connecting.
The first problem is that it takes it a couple of tries before it actually
connects the two machines.
It complains about bogus data and after trying for a minute or so it
connects.
kill -USR1 shows that they are connected
kill -USR2 only shows the local subnet, not the remote
I've tried these versions without any luck:
cvs
2017 Dec 16
0
[PATCH] opus_defines.h: disable restrict with gcc < 3.4
With gcc-3.3, building opus fails with the following error:
In file included from silk/float/pitch_analysis_core_FLP.c:38:
celt/pitch.h:53: error: invalid use of `restrict'
This is because __restrict is broken with gcc < 3.4. See:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6392
Therefore, disable restrict with gcc versions older than 3.4.
---
include/opus_defines.h | 6 +++++-
1 file
2016 May 05
2
VDPAU DEINTERLACE
NVIDIA G98
mesa-dri-drivers-11.2.1-2.20160501.fc22.x86_64
(incl. mesa commit 38fcf7c)
vdpauinfo | grep -i deint
DEINTERLACE_TEMPORAL y
DEINTERLACE_TEMPORAL_SPATIAL -
https://cgit.freedesktop.org/vdpau/libvdpau/tree/include/vdpau/vdpau.h#n3420
#define VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL ((VdpVideoMixerFeature)0)
/**
* \hideinitializer
* \brief A
2016 May 09
2
VDPAU DEINTERLACE
On 09.05.2016 19:37, Ilia Mirkin wrote:
> Mesa only supports the non-spatial temporal deinterlace (deint=3). I'm
> guessing that due to some unfortunate issues, you're no longer getting
> hw accelerated video decoding. Check in vdpauinfo to make sure that
> it's indeed showing the relevant codec as supported. If not, you can
> turn that back on by updating to mesa
2015 Oct 22
3
[PATCH] win32: only use dllexport when building DLL
If building a static library, marking symbols as dllexport causes them
to be exported from the final executable. For example, run
objdump -x opus_demo.exe on a --disabled-shared build and look for the
export table; there should not be one in a normal Win32 .exe file, but
when linking static libopus, the exe exports all of the opus_* public
functions.
Use the libtool-defined DLL_EXPORT flag to
2014 May 19
3
Opus DTX issue report
Hello:
We noticed that opus reconstructed noise is pulsing with a 400ms pattern when dtx is enabled in silk mode. This is independent of the background noise level and is found with speech + non-speech period test files as well as variable level noise-only test files. This issue can be reproduced with opus v1.1 using this command:
./opus_demo voip 16000 1 25000 -dtx input.bin
2006 Jan 17
2
Recommended GUI for Speex
Hi all,
I have recently added Speex support to my app (http://sbooth.org/Max/) and
am in the process of creating a GUI for the user to control the codec
parameters. I am new to Speex and as such I am not really sure which
parameters are more important than others, and deserve prominent
placement, etc. Is there a recommended GUI for people to follow or use as
an example?
Stephen
2004 Aug 06
2
--dtx alone does nothing?
I'm running a:
for band in n w u
do
for quality in 0 1 2 3 4 5 6 7 8 9 10
do
for complexity in 3
do
for vad in "" "--vad"
do
for dtx in "" "--dtx"
do
echo speexenc -${band} --quality ${quality} --comp ${complexity} ${vad} ${dtx} input.${band}.wav
2016 May 09
0
VDPAU DEINTERLACE
Mesa only supports the non-spatial temporal deinterlace (deint=3). I'm
guessing that due to some unfortunate issues, you're no longer getting
hw accelerated video decoding. Check in vdpauinfo to make sure that
it's indeed showing the relevant codec as supported. If not, you can
turn that back on by updating to mesa 11.2.2, or downgrading your
kernel to 4.2 or earlier. (The issue only
2004 Aug 06
2
DTX in speech
Hello,
I am trying to use the DTX feature of speex to tell if the user is
speaking. I have VBR, DTX and VAD turned on, but the function
speex_encode always returns a non-zero value. It is my understanding
that it should return a zero value when the encoder detects silence?
Could anyone give me any clues to help figure out why this isn't working
for me? I am using the 1.13 version of speex on
2004 Aug 06
1
Frozen upper spectrum in WB VBR CNG
Jean-Marc Valin (jean-marc.valin@hermes.usherb.ca) wrote:
>
> > I've been using Speex in my voice-over-IP program on Win32, in
> > wideband (16kHz) mode. I just starting using VBR recently and
> > have run into something that might be a problem within Speex:
>
> Are you turning on DTX in addition to VBR? Also, what version are you
> using. As of 1.0, DTX is