similar to: Bug #4

Displaying 20 results from an estimated 100 matches similar to: "Bug #4"

2001 Apr 06
1
OT: long - Replacing CD's?
> -----Ursprüngliche Nachricht----- > Von: David 'Superkind' Roden [mailto:superkind@uni-neukoelln.de] > Gesendet: Donnerstag, 5. April 2001 22:53 > An: vorbis@xiph.org > Betreff: Re: OT: long - Replacing CD's? was RE: [vorbis] New type of > copy-prot ected audio CDs are coming... > > Why? That 2nd part was perfectly demonstrated with the > MiniDisc. I
2001 Feb 27
1
libao compilation difficulty
Compiling libao on a system w/linux2.4.2 & glibc-2.0 (I think), I get an error. gcc -DPACKAGE=\"libao\" -DVERSION=\"0.6.0\" -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DHAVE_SYS_SOUNDCARD_H=1 -I. -I. -I../../.. -I../../../include -O20 -ffast-math -D_REENTRANT -fsigned-char -DAO_PLUGIN_PATH=\"/usr/local/lib/ao\" -c ao_alsa.c -fPIC -DPIC -o ao_alsa.lo In file
2001 May 11
1
Amplify Ogg files without decode/encode
> Just curious, is it possible to amplify Ogg frames without a decode/encode > cycle? I usually normalise before encoding all recordings for my radio > station, but I obtain some music from 3rd parties and it often need > normalising. I find this ability very useful for MP3s and it would be a big > handicap to me if Ogg can not. Add a comment into the ogg file :
2001 Mar 13
3
vorbis-utils features ;)
I've just started encoding some of my cd's to ogg with the new beta4-release, and noticed a few "bugs" .. [oggenc] (*) When using long filenames that make the "encoding.."-line not fit in one line, that line is repeated 1000 times on the screen (one for each .1 percent). That could be solved either by not including the filename on the updating line (but above or
2001 Jan 25
2
Systemwide default for ogg123
MoiN I thought you should be able to set system wide defaults for the output device of ogg123. The following patch will look for /etc/ogg123rc, if no ~/.ogg123rc can be found. So the user can still override the system defaults, but not every user needs to have an ~/.ogg123rc file. Ingo -- 16 Hard coded constant for amount of room allowed for
2001 Mar 10
0
patch to add device-option to ogg123 rc file
Below is a patch for vorbis-tools-1.0beta4 ogg123. It adds support for using the rc file (like /etc/ogg123.rc) for configuring the device-options. In addition, comments can be used (when they start a line). My ~/.ogg123rc: default_device=oss default_options=dsp:/dev/audio Please share your comments. Jeremy C. Reed http://www.reedmedia.net/ diff -u
2001 Feb 12
0
Configuring, compiling and installing ogg vorbis on Mandrake 7.2 (was Re: A Top Level README for the nightly CVS snapshot )
Hello, i had nearly the same problem when compiling libao (of nightly snapshot of 2001/02/10) >checking for artsc-config... /usr/bin/artsc-config >I don't know enough about KDE to know if this file is supposed to be >there without any of the kde-devel packages installed (if not, then I >have a Mandrake bug). If I move this file so it can't be found, make >and make install
2001 Feb 12
0
Configuring, compiling and installing ogg vorbis on Mandrake 7.2 (was Re: A Top Level README for the nightly CVS snapshot )
Hello, i had nearly the same problem when compiling libao (of nightly snapshot of 2001/02/10) >checking for artsc-config... /usr/bin/artsc-config >I don't know enough about KDE to know if this file is supposed to be >there without any of the kde-devel packages installed (if not, then I >have a Mandrake bug). If I move this file so it can't be found, make >and make install
2001 Mar 16
3
Patches for NetBSD
I submitted four new packages for the NetBSD pkgsrc collection: libao, libogg, libvorbis and vorbis-tools for 1.0beta4. The following is some of the patches needed for libao and vorbis-tools. Official Developers: When you receive patches or development suggestions can you please acknowledge them? (For example: "Noted.", "Thanks, but already done.", "Not necessary,
2002 Aug 14
0
automake 1.6 compatability patch
This patch cleans up the vorbis-tools Makefile.am files so they work with both automake 1.4 and 1.6. Some changes to configure.in were also needed in order to get things to work (and to fix some ac 2.50 issues). Please remove config.h from cvs as it is a generated file and empty anyway. automake 1.6 isn't really incompatable with 1.4, it's just more picky about you sticking to the rules:
2001 Mar 17
1
ogg123 man page location
mandir should default to $(prefix)/man, but there's no reason to mess with it since autoconf/automake will take care of it on their own just fine. Index: ogg123/Makefile.am =================================================================== RCS file: /usr/local/cvsroot/vorbis-tools/ogg123/Makefile.am,v retrieving revision 1.13 diff -u -r1.13 Makefile.am --- ogg123/Makefile.am 2001/02/19
2001 Apr 01
1
vorbis-tools compiling problem
Hello, I successfully compiled and installed; libao-0.6.0-1 libao-devel-0.6.0-1 libogg-1.0beta4-1 libogg-devel-1.0beta4-1 libvorbis-1.0beta4-1 libvorbis-devel-1.0beta4-1 as RPM's using the spec files included in the sources. (the RPM's available for download are for RPM 4 users, I guess?) Anyway, now I'm trying to compile vorbis-tools using the spec file included and I got the
2008 Jan 25
7
vorbis-tools 1.2.0 Release Candidate
I bumped the version number of vorbis-tools and am preparing it for an eventual release in a few days. A changelog of what's new may be found at [1]. Meanwhile, what's in SVN is a "Release Candidate" to find out if anything was broken since version 1.1.1. Report any (or lack of) problems you may find, so we'll be able to put out a new version of vorbis-tools. -Ivo [1]
2001 Feb 28
1
patches to beta 4 spec files
Hi, Attached are patches for the beta 4 distribution, fixing minor problems in RPM spec files. One question: are there any reasons not to include vorbiscomment in the vorbis-tools binary package? I've added the long-awaited utility program into the revised spec file, but I wonder if it is a wrong change... Regards, -- KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp> diff -ru
2004 Dec 11
1
ogg123
I have vorbis-tools 1.1 (also tested on svn version), I have problem with play any ogg vorbis file as user rmrmg: [rmrmg@slack:~$] ogg123 ./av/lep.ogg Segmentation fault All works fine as _any_ other user. I have not any ~/.libao file. What can be the reason of my problem? Do you have any idea? -- . JID: rmrmg(at)jabberpl(dot)org | Wszystko jest trudne . mail: rmrmg(at)wp(dot)pl | przy
2002 Oct 05
2
ogg123 remote interface
Hi, I've been working on ogg123 to see if i could add a remote interface compatible with the one in mpg123. This remote interface is used mainly by mp3 players which use mpg123 as their backend. The reason i did this was that i have recently encoded some of my cd's in ogg vorbis format but wanted to keep using my favourite player (playmp3list,
2005 Nov 21
2
shorewall status
Hi I wonder if you can help... I have setup shorewall(2.2.3) under debian on a machine that has 4 network ports... the idea is that there is 1 WAN port, 1 DMZ port, and 2 LAN ports, 1 LAN port has static NAT setup for selected incoming connection from trusted sources, and the second LAN port I am trying to setup using masq NAT as it only requires outgoing connections, no incoming. the static NAT
2004 Sep 10
1
[Flac-users] missing vorbiscomment.h
Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
2004 Sep 10
1
[Flac-users] missing vorbiscomment.h
Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
2007 Aug 17
1
Detecting DTMF Tones from Muted app_meetme Participants
Hi, folks. I have a problem using Asterisk 1.2. I create conferences using app_meetme and Zap channels, and for every participant I run the script defined by AGI_BACKGROUND_SCRIPT to be able to listen and react to DTMF tones. As the docs tell me, when using the AGI background script one loses the ability to control the meetme conference via the command line so for muting conference participants I