Displaying 20 results from an estimated 100 matches similar to: "SPEEX_GET_QUALITY error"
2005 Jan 25
1
Is SPEEX_GET_QUALITY implemented ?
Hi All,
Almost all my question is in the subject. I have written the
following small program and I get an error message when I try to use
SPEEX_GET_QUALITY. This functionality seems not to be used in speexenc.c
or speexdec.c.
I would appreciate any hints.
best regards,
Alain Aubord
---------------------------test.c---------------------------------------
#include <stdio.h>
#include
2004 Aug 06
2
SPEEX_GET_QUALITY not working?
Hello everyone,
I'm finally beginning to use Speex for a project. As expected, the
implementation so far has been very easy and I am thrilled with the
capabilities and flexibility of Speex, especially the new features in
1.1. My efforts so far have resulted in a couple of questions:
1) I was interested in fetching the default quality setting for
narrowband:
2005 Feb 27
2
SPEEX_GET_QUALITY
To close debian bug #271052,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271052
I went ahead and did the following:
$ diff -u ../original/speex-1.1.6/libspeex/nb_celp.c libspeex/nb_celp.c
--- ../original/speex-1.1.6/libspeex/nb_celp.c 2004-07-15 01:16:52.000000000 -0400
+++ libspeex/nb_celp.c 2005-02-27 08:24:49.000000000 -0500
@@ -1746,6 +1746,21 @@
st->submodeSelect =
2004 Aug 06
0
SPEEX_GET_QUALITY not working?
> 1) I was interested in fetching the default quality setting
> fornarrowband:
> speex_encoder_ctl(_encodeState, SPEEX_GET_QUALITY, &value);
>
> Unfortunately, the above fails with libspeex 1.1.4. The console
> shows:
>
> warning: Unknown nb_ctl request: 5
Actually, I never implemented SPEEX_GET_QUALITY. It's not that usefule
anyway, but I might do it in the
2005 Feb 27
0
SPEEX_GET_QUALITY
Hi Maitland,
I think your solution is probably the best implementation you could do
for SPEEX_GET_QUALITY. However, unless you have something against that,
I think removing it would be better, as in many cases (e.g. VBR), the
call just doesn't make sense). This would of course break the API (not
the ABI), but given the fact that it was never implemented, any app that
uses it is already broken
2004 Sep 10
0
SPEEX_GET_QUALITY not implemented.
I am using Speex 1.0.4. I was very confused about why speex_encoder_ctl
with SPEEX_GET_QUALITY *always* failed, until I read
<http://lists.xiph.org/pipermail/speex-dev/2003-September/001896.html>
from a whole year ago!
Can SPEEX_GET_QUALITY be removed from speex.h and from the documentation
(or actually implemented, whichever is easier :)
Best!
Reed
2005 Feb 27
1
SPEEX_GET_QUALITY
On Sun, Feb 27, 2005 at 06:09:48PM -0500, Jean-Marc Valin wrote:
> Hi Maitland,
>
> I think your solution is probably the best implementation you could do
> for SPEEX_GET_QUALITY. However, unless you have something against that,
> I think removing it would be better, as in many cases (e.g. VBR), the
> call just doesn't make sense). This would of course break the API (not
2004 Aug 06
3
Decoding raw problem on OS X with 1.03
On Mar 29, 2004, at 5:05 PM, Jean-Marc Valin wrote:
> Can you try manually swapping the bytes on the raw output and see if
> you
> get something useful (I think by default wav is always little endian
> while raw is native endian)?
Well, my apologies. Apparently I got confused when trying all the
different formats and somehow skipped little endian.
The decoded raw file is in
2008 Dec 14
3
Wine fail to launch game in Steam
A few weeks ago I reinstall my laptop with Debian etch (upgraded to lenny), kernel 2.6.27.8, wine 1.1.10, fglrx v8.11 (ati x2300) and Steam api version v007
There is no problem to launch Steam.exe (`wine /path/to/Steam.exe &`). However, after Steam.exe startup, I can not launch Day of Defeat. No specific error displayed on the screen, the `Preparing to launch Day of Defeat' dialog popped
2004 Sep 13
0
Compile flags for sampleenc sampledec.
I suspect I am missing something basic but I do not seem to be able to get the sampleenc and sampledec programs to work together. I think I do not have a compile swtich of flag set correctly.
Backgound information:
1) 1.0.4 tar package 'make' worked and installed on a mandrake 10.0 linux
2) speexenc and speexdec appear to work fine.
3) testenc and testenc_wb work fine, though I
2004 Sep 15
0
Problems with sampleenc and sampledec
I suspect I am missing something basic but I do not seem to be able to get the sampleenc and sampledec programs to work together. I suspect the decode operation is failing, but I cannot find out why.
Backgound information:
1) 1.0.4 tar package 'make' worked and installed on a mandrake 10.0 linux
2) speexenc and speexdec appear to work fine.
3) testenc and testenc_wb work fine, though
2007 Dec 17
2
[LLVMdev] PointerType API Change
On Monday 17 December 2007, Christopher Lamb wrote:
> On Dec 17, 2007, at 1:22 AM, Torvald Riegel wrote:
> > Would it be possible to keep get() unchanged, with a default
> > behaviour, plus
> > a warning? Otherwise everybody (assuming everybody gets type void*)
> > will
> > have to update their LLVM passes, and either maintain two versions
> > of the
>
2008 Apr 11
1
Steam just keeps crashing, version after version...
So, steam doesn't seem to be working very well, (at least on my computer) with about the 10 latest wine versions. I'm running:
Kubuntu 7.10 on an old,
nvidia nforce2
amd athlon 2400+
nvidia fx5900xt with proper working drivers (glxgears gives me +5000fps)
512mb ram.
Here's console output:
alex at Burken:~/.wine/drive_c/Program Files/Steam$ wine steam
fixme:mixer:ALSA_MixerInit No
2007 Dec 17
2
[LLVMdev] PointerType API Change
Would it be possible to keep get() unchanged, with a default behaviour, plus
a warning? Otherwise everybody (assuming everybody gets type void*) will
have to update their LLVM passes, and either maintain two versions of the
passes or require their clients to use a certain LLVM version. Then passes
could be "address-space-safe" or not. If the default parameter value for
get() could
2007 Dec 17
0
[LLVMdev] PointerType API Change
On Dec 17, 2007, at 1:22 AM, Torvald Riegel wrote:
> Would it be possible to keep get() unchanged, with a default
> behaviour, plus
> a warning? Otherwise everybody (assuming everybody gets type void*)
> will
> have to update their LLVM passes, and either maintain two versions
> of the
> passes or require their clients to use a certain LLVM version.
AFAIK API
2008 Jun 23
4
Ubuntu, Counterstrike Source, crashes after loading a game
Hello,
Well, first let me say - I've looked in the APP database for this game. I've tried to trouble shoot everything I've read on the site.
Here's my system:
Ubuntu 64-bit 8.04
AMD 5800+
4gb of Winsor Ram
Nvidia 8500 GT
Intel onboard sound
Here's what's happening:
Whenever I load up a game on CSS, it crashes after a gun shot. You can walk around, and everything just
2014 Jan 30
3
[PATCH] drm/nouveau: set irq_enabled manually
Since commit 0fa9061ae8c ("drm/nouveau/mc: handle irq-related setup
ourselves"), drm_device->irq_enabled remained unset. This is needed in
order to properly wait for a vblank event in the generic drm code.
See https://bugs.freedesktop.org/show_bug.cgi?id=74195
Reported-by: Jan Janecek <janjanjanx at gmail.com>
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
Cc:
2014 Jan 29
7
[Bug 74195] New: Responsivity to input with vsync on is slower after update
https://bugs.freedesktop.org/show_bug.cgi?id=74195
Priority: medium
Bug ID: 74195
Assignee: nouveau at lists.freedesktop.org
Summary: Responsivity to input with vsync on is slower after
update
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
2014 Aug 24
2
[Bug 83021] New: Separate X screens --> Xvideo is vsynced to primary screen only
https://bugs.freedesktop.org/show_bug.cgi?id=83021
Priority: medium
Bug ID: 83021
Assignee: nouveau at lists.freedesktop.org
Summary: Separate X screens --> Xvideo is vsynced to primary
screen only
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux
2007 Dec 17
0
[LLVMdev] PointerType API Change
On Dec 17, 2007, at 2:51 AM, Torvald Riegel wrote:
> On Monday 17 December 2007, Christopher Lamb wrote:
>> On Dec 17, 2007, at 1:22 AM, Torvald Riegel wrote:
>>> Would it be possible to keep get() unchanged, with a default
>>> behaviour, plus
>>> a warning? Otherwise everybody (assuming everybody gets type void*)
>>> will
>>> have to update