Yesterday

• 46 hours ago

  issue 12 (src/SerialUlaw.cpp ]) commented on by news.observer   -   Work around for systems that don't have cfmakeraw

  Work around for systems that don't have cfmakeraw
• 46 hours ago

  issue 12 (src/SerialUlaw.cpp ]) reported by news.observer   -   src/SerialUlaw.cpp won't compile on Cygwin due to lack of cfmakeraw. Patch follows. Doug ~/darkice-0.20.1/src $ diff SerialUlaw.cpp.patched SerialUlaw.cpp.original 87,89d86 < #ifndef __CYGWIN__ < #define HAVE_CFMAKERAW 1 // not in Cygwin ... < #endif 232,245c229 < < #ifdef HAVE_CFMAKERAW < // The easy way < cfmakeraw( &ts ); < #else < // The hard way < ts.c_iflag &= ~( IGNBRK | BRKINT | PARMRK | ISTRIP < | INLCR | IGNCR | ICRNL | IXON ); < ts.c_oflag &= ~OPOST; < ts.c_lflag &= ~( ECHO | ECHONL | ICANON | ISIG | IEXTEN ); < ts.c_cflag &= ~( CSIZE | PARENB | CRTSCTS ); < ts.c_cflag |= CS8 | CREAD | CLOCAL ; < #endif < --- > cfmakeraw(&ts);

  src/SerialUlaw.cpp won't compile on Cygwin due to lack of cfmakeraw. Patch follows. Doug ~/darkice-0.20.1/src $ diff SerialUlaw.cpp.patched SerialUlaw.cpp.original 87,89d86 < #ifndef __CYGWIN__ < #define HAVE_CFMAKERAW 1 // not in Cygwin ... < #endif 232,245c229 < < #ifdef HAVE_CFMAKERAW < // The easy way < cfmakeraw( &ts ); < #else < // The hard way < ts.c_iflag &= ~( IGNBRK | BRKINT | PARMRK | ISTRIP < | INLCR | IGNCR | ICRNL | IXON ); < ts.c_oflag &= ~OPOST; < ts.c_lflag &= ~( ECHO | ECHONL | ICANON | ISIG | IEXTEN ); < ts.c_cflag &= ~( CSIZE | PARENB | CRTSCTS ); < ts.c_cflag |= CS8 | CREAD | CLOCAL ; < #endif < --- > cfmakeraw(&ts);

Last 30 days

• Dec 28, 2009

  issue 11 (failed to write to ring ruffer) commented on by marcel.hecko   -   crashed today in the morning again with the same message : failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer

  crashed today in the morning again with the same message : failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer failed to write to ring ruffer
• Dec 25, 2009

  issue 9 (Error on make) commented on by maredzki   -   I am having the same issue during 'make' trying to install darkice-0.20.1: Linux oreo 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.1-4ubuntu8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8)

  I am having the same issue during 'make' trying to install darkice-0.20.1: Linux oreo 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.1-4ubuntu8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8)
• Dec 23, 2009

  issue 9 (Error on make) commented on by cees.vanegmond   -   I did a clean install of Ubuntu 9.10 server edition (options Ubuntu server and Open SSH enabled during installation). Meanwhile i'm switched back to Ubuntu server 9.04 without probs.

  I did a clean install of Ubuntu 9.10 server edition (options Ubuntu server and Open SSH enabled during installation). Meanwhile i'm switched back to Ubuntu server 9.04 without probs.
• Dec 22, 2009

  issue 11 (failed to write to ring ruffer) commented on by marcel.hecko   -   ok, downloaded and installed today: DarkIce 0.20.1 live audio streamer, http://code.google.com/p/darkice/ Copyright (c) 2000-2007, Tyrell Hungary, http://tyrell.hu/ Copyright (c) 2008-2009, Akos Maroy and Rafael Diniz Using config file: /etc/darkice/darkice.cfg Using JACK audio server as input device. Using POSIX real-time scheduling, priority 98 Registering as JACK client darkice-4271 start command: screen -l -d -m /usr/local/bin/darkice -c /etc/darkice/darkice.cfg there is also `rotter` running in the background

  ok, downloaded and installed today: DarkIce 0.20.1 live audio streamer, http://code.google.com/p/darkice/ Copyright (c) 2000-2007, Tyrell Hungary, http://tyrell.hu/ Copyright (c) 2008-2009, Akos Maroy and Rafael Diniz Using config file: /etc/darkice/darkice.cfg Using JACK audio server as input device. Using POSIX real-time scheduling, priority 98 Registering as JACK client darkice-4271 start command: screen -l -d -m /usr/local/bin/darkice -c /etc/darkice/darkice.cfg there is also `rotter` running in the background
• Dec 22, 2009

  issue 9 (Error on make) commented on by raf...@riseup.net   -   I cannot reproduce this error in my system. Can anyone confirm if this error persist? Or should I close this ticket?

  I cannot reproduce this error in my system. Can anyone confirm if this error persist? Or should I close this ticket?
• Dec 22, 2009

  issue 11 (failed to write to ring ruffer) commented on by raf...@riseup.net   -   Can you please try darkice from svn trunk?

  Can you please try darkice from svn trunk?
• Dec 22, 2009

  r464 (added missing commits to changelog and new authors to author...) committed by raf...@riseup.net   -   added missing commits to changelog and new authors to authors

  added missing commits to changelog and new authors to authors
• Dec 22, 2009

  r463 (Patch by Sergiy <piratfm@gmail.com>: implement sample rate ...) committed by raf...@riseup.net   -   Patch by Sergiy <piratfm@gmail.com>: implement sample rate conversion for all codecs using libsamplerate, and keeping internal aflibConverter as fallback

  Patch by Sergiy <piratfm@gmail.com>: implement sample rate conversion for all codecs using libsamplerate, and keeping internal aflibConverter as fallback
• Dec 18, 2009

  issue 6 (DarkIce: DarkIce.cpp:1140: can't open connector [0]) commented on by eclauset   -   I'm having the same problem. it worked fine before a recent reboot. wxyc@wxyc-mp3encoder:~$ sudo darkice DarkIce 0.20.1 live audio streamer, http://darkice.tyrell.hu/ Copyright (c) 2000-2007, Tyrell Hungary, http://tyrell.hu/ Using config file: /etc/darkice.cfg Using OSS DSP input device: /dev/dsp Using POSIX real-time scheduling, priority 98 DarkIce: DarkIce.cpp:1187: can't open connector [0] config file: # this section describes general aspects of the live streaming session [general] duration = 0 # duration of encoding, in seconds. 0 means forever bufferSecs = 5 # size of internal slip buffer, in seconds reconnect = yes # this section describes the audio input that will be streamed [input] device = /dev/dsp # OSS DSP soundcard device for the audio input sampleRate = 44100 # sample rate in Hz. try 11025, 22050 or 44100 bitsPerSample = 16 # bits per sample. try 16 channel = 2 # channels. 1 = mono, 2 = stereo [icecast2-0] bitrateMode = cbr format = mp3 bitrate = 128 quality = 0.8 server = audio-mp3.ibiblio.org port = 8000 password = xxxx mountPoint = wxyc.mp3.ipv4 name = WXYC description = WXYC, University of North Carolina Chapel Hill url = http://audio-mp3.ibiblio.org:8000/wxyc.mp3 genre = alternative public = no

  I'm having the same problem. it worked fine before a recent reboot. wxyc@wxyc-mp3encoder:~$ sudo darkice DarkIce 0.20.1 live audio streamer, http://darkice.tyrell.hu/ Copyright (c) 2000-2007, Tyrell Hungary, http://tyrell.hu/ Using config file: /etc/darkice.cfg Using OSS DSP input device: /dev/dsp Using POSIX real-time scheduling, priority 98 DarkIce: DarkIce.cpp:1187: can't open connector [0] config file: # this section describes general aspects of the live streaming session [general] duration = 0 # duration of encoding, in seconds. 0 means forever bufferSecs = 5 # size of internal slip buffer, in seconds reconnect = yes # this section describes the audio input that will be streamed [input] device = /dev/dsp # OSS DSP soundcard device for the audio input sampleRate = 44100 # sample rate in Hz. try 11025, 22050 or 44100 bitsPerSample = 16 # bits per sample. try 16 channel = 2 # channels. 1 = mono, 2 = stereo [icecast2-0] bitrateMode = cbr format = mp3 bitrate = 128 quality = 0.8 server = audio-mp3.ibiblio.org port = 8000 password = xxxx mountPoint = wxyc.mp3.ipv4 name = WXYC description = WXYC, University of North Carolina Chapel Hill url = http://audio-mp3.ibiblio.org:8000/wxyc.mp3 genre = alternative public = no
• Dec 14, 2009

  issue 11 (failed to write to ring ruffer) reported by marcel.hecko   -   Darkice crashes after a few days claiming many lines of "failed to write to ring ruffer" We are broadcasting 3 different outputs of different bitratio, the input is from jack source. What version of the product are you using? On what operating system? DarkIce 0.20.1, Ubuntu Feisty Please provide any additional information below. [general] duration = 0 bufferSecs = 10 reconnect = yes [input] device = jack_auto sampleRate = 44100 bitsPerSample = 16 channel = 2 [icecast2-0] bitrateMode = abr format = mp3 bitrate = 96 server = stream.xxx.org.uk port = 8000 password = xxx mountPoint = xxx_high.mp3 name = xxx description = xxx url = http://www.xxx.org.uk genre = music public = yes [icecast2-1] bitrateMode = abr format = mp3 bitrate = 32 server = stream.xxx.org.uk port = 8000 password = xxx mountPoint = xxx_low.mp3 name = xxx description = xxx url = http://www.xxx.org.uk genre = music public = yes [icecast2-2] bitrateMode = abr format = mp3 bitrate = 16 server = stream.xxx.org.uk port = 8000 password = xxxx mountPoint = xxx_punk.mp3 name = xxx description = xxx url = http://www.xxx.org.uk genre = music public = yes /usr/local/bin/jackd -Z -v -d oss -r 44100 -p 4096 -w 16 -i 2

  Darkice crashes after a few days claiming many lines of "failed to write to ring ruffer" We are broadcasting 3 different outputs of different bitratio, the input is from jack source. What version of the product are you using? On what operating system? DarkIce 0.20.1, Ubuntu Feisty Please provide any additional information below. [general] duration = 0 bufferSecs = 10 reconnect = yes [input] device = jack_auto sampleRate = 44100 bitsPerSample = 16 channel = 2 [icecast2-0] bitrateMode = abr format = mp3 bitrate = 96 server = stream.xxx.org.uk port = 8000 password = xxx mountPoint = xxx_high.mp3 name = xxx description = xxx url = http://www.xxx.org.uk genre = music public = yes [icecast2-1] bitrateMode = abr format = mp3 bitrate = 32 server = stream.xxx.org.uk port = 8000 password = xxx mountPoint = xxx_low.mp3 name = xxx description = xxx url = http://www.xxx.org.uk genre = music public = yes [icecast2-2] bitrateMode = abr format = mp3 bitrate = 16 server = stream.xxx.org.uk port = 8000 password = xxxx mountPoint = xxx_punk.mp3 name = xxx description = xxx url = http://www.xxx.org.uk genre = music public = yes /usr/local/bin/jackd -Z -v -d oss -r 44100 -p 4096 -w 16 -i 2
• Dec 12, 2009

  issue 9 (Error on make) commented on by slebourdon   -   Finally i manage installing darkice on my system with a trivial apt-get install darkice There is an ubunutu multiverse maintened package : https://launchpad.net/ubuntu/+source/darkice for karmic it gives : Package: darkice Priority: optional Section: sound Installed-Size: 360 Maintainer: Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com> Architecture: i386 Version: 0.19-1ubuntu3 Depends: libasound2 (>> 1.0.18), libc6 (>= 2.4), libfaac0 (>= 1.26), libgcc1 (>= 1:4.1.1), libjack0 (>= 0.116.1), libmp3lame0, libogg0 (>= 1.0rc3), libstdc++6 (>= 4.4.0), libtwolame0, libvorbis0a (>= 1.1.2), libvorbisenc2 (>= 1.1.2) Suggests: darksnow Size: 124384 Description: Live audio streamer DarkIce is an IceCast, IceCast2 and ShoutCast live audio streamer. It takes audio input from a sound card, encodes it into mp3 and/or Ogg Vorbis, and sends the mp3 stream to one or more IceCast and/or ShoutCast servers, the Ogg Vorbis stream to one or more IceCast2 servers. DarkIce uses lame as a shared object as its mp3 encoder, and the Ogg Vorbis as its Ogg Vorbis encoder. Homepage: http://darkice.tyrell.hu/ Original-Maintainer: Jochen Friedrich <jochen@scram.de>

  Finally i manage installing darkice on my system with a trivial apt-get install darkice There is an ubunutu multiverse maintened package : https://launchpad.net/ubuntu/+source/darkice for karmic it gives : Package: darkice Priority: optional Section: sound Installed-Size: 360 Maintainer: Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com> Architecture: i386 Version: 0.19-1ubuntu3 Depends: libasound2 (>> 1.0.18), libc6 (>= 2.4), libfaac0 (>= 1.26), libgcc1 (>= 1:4.1.1), libjack0 (>= 0.116.1), libmp3lame0, libogg0 (>= 1.0rc3), libstdc++6 (>= 4.4.0), libtwolame0, libvorbis0a (>= 1.1.2), libvorbisenc2 (>= 1.1.2) Suggests: darksnow Size: 124384 Description: Live audio streamer DarkIce is an IceCast, IceCast2 and ShoutCast live audio streamer. It takes audio input from a sound card, encodes it into mp3 and/or Ogg Vorbis, and sends the mp3 stream to one or more IceCast and/or ShoutCast servers, the Ogg Vorbis stream to one or more IceCast2 servers. DarkIce uses lame as a shared object as its mp3 encoder, and the Ogg Vorbis as its Ogg Vorbis encoder. Homepage: http://darkice.tyrell.hu/ Original-Maintainer: Jochen Friedrich <jochen@scram.de>
• Dec 12, 2009

  issue 9 (Error on make) commented on by cees.vanegmond   -   Same situation (Darkice 0.20.1, ubuntu 9.10, gcc 4.4) and issue here . Tried also 0.18/0.19 without luck. Looking forward for the fix.

  Same situation (Darkice 0.20.1, ubuntu 9.10, gcc 4.4) and issue here . Tried also 0.18/0.19 without luck. Looking forward for the fix.
• Dec 09, 2009

  issue 10 (Code review request) commented on by raf...@riseup.net   -   the patch.

  the patch.
• Dec 09, 2009

  issue 10 (Code review request) reported by raf...@riseup.net   -   From: Sergiy" <piratfm (AT) gmail (DOT) com> Hi, again. Here is patch for vorbis-encoder, that implements sample-rate conversion through libsamplerate. At the hearing it noticeably cleaner than aflibConverter. Please, test it, if it's really better, I will implement it also for aac/aac+ too. Also at line 122 of patched src/VorbisLibEncoder.cpp you find, that quality set to SRC_SINC_FASTEST, but you can try SRC_SINC_BEST_QUALITY - it's slower, but high frequencies is not so degrade as with faster methods.

  From: Sergiy" <piratfm (AT) gmail (DOT) com> Hi, again. Here is patch for vorbis-encoder, that implements sample-rate conversion through libsamplerate. At the hearing it noticeably cleaner than aflibConverter. Please, test it, if it's really better, I will implement it also for aac/aac+ too. Also at line 122 of patched src/VorbisLibEncoder.cpp you find, that quality set to SRC_SINC_FASTEST, but you can try SRC_SINC_BEST_QUALITY - it's slower, but high frequencies is not so degrade as with faster methods.

Older

• Dec 04, 2009

  r462 (updated old darkice website links) committed by raf...@riseup.net   -   updated old darkice website links

  updated old darkice website links
• Dec 01, 2009

  issue 8 (ALSA recording unreliable with Envy24 cards) changed by raf...@riseup.net   -   Patch applied in r461.

  Status: Fixed

  Owner: raf...@riseup.net

  Patch applied in r461.

  Status: Fixed

  Owner: raf...@riseup.net
• Dec 01, 2009

  r461 (patch for alsa driver, by cladisch - closes ticked #8) committed by raf...@riseup.net   -   patch for alsa driver, by cladisch - closes ticked #8

  patch for alsa driver, by cladisch - closes ticked #8
• Dec 01, 2009

  issue 9 (Error on make) reported by slebourdon   -   What steps will reproduce the problem? 1. ./configure 2. make What is the expected output? What do you see instead? Error on compilation : g++ -DHAVE_CONFIG_H -I. -O2 -pedantic -Wall -g -O2 -MT SerialUlaw.o -MD -MP -MF .deps/SerialUlaw.Tpo -c -o SerialUlaw.o SerialUlaw.cpp SerialUlaw.cpp: In member function ‘virtual unsigned int SerialUlaw::read(void*, unsigned int)’: SerialUlaw.cpp:296: error: ‘perror’ was not declared in this scope make[2]: *** [SerialUlaw.o] Erreur 1 make[2]: quittant le répertoire « /tmp/darkice/darkice-0.20.1/src » make[1]: *** [all] Erreur 2 make[1]: quittant le répertoire « /tmp/darkice/darkice-0.20.1/src » make: *** [all-recursive] Erreur 1 What version of the product are you using? On what operating system? Darkice 0.20.1, ubuntu 9.10, gcc 4.4 Please provide any additional information below. gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.1-4ubuntu8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8)

  What steps will reproduce the problem? 1. ./configure 2. make What is the expected output? What do you see instead? Error on compilation : g++ -DHAVE_CONFIG_H -I. -O2 -pedantic -Wall -g -O2 -MT SerialUlaw.o -MD -MP -MF .deps/SerialUlaw.Tpo -c -o SerialUlaw.o SerialUlaw.cpp SerialUlaw.cpp: In member function ‘virtual unsigned int SerialUlaw::read(void*, unsigned int)’: SerialUlaw.cpp:296: error: ‘perror’ was not declared in this scope make[2]: *** [SerialUlaw.o] Erreur 1 make[2]: quittant le répertoire « /tmp/darkice/darkice-0.20.1/src » make[1]: *** [all] Erreur 2 make[1]: quittant le répertoire « /tmp/darkice/darkice-0.20.1/src » make: *** [all-recursive] Erreur 1 What version of the product are you using? On what operating system? Darkice 0.20.1, ubuntu 9.10, gcc 4.4 Please provide any additional information below. gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.1-4ubuntu8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8)
• Dec 01, 2009

  issue 8 (ALSA recording unreliable with Envy24 cards) commented on by cladisch   -   Hardware parameters are set and fixed in the order in which the various snd_pcm_hw_param_set_xxx functions are called. So, if set_period_time_near set the period time to one quarter of the _desired_ buffer size, but if the _actual_ buffer size set by set_buffer_time_near is smaller due to hardware limitations, the goal of having four periods per buffer is not met. Calling set_periods_near sets only the ratio between period time and buffer time. This means that the period time is set at the same time with the buffer time (when set_buffer_time_near is called), and that the period time is one fourth of the _actual_ buffer time. (The same effect could by accomplished by moving the call of set_period_time_near after the buffer_time call and using the actual buffer time returned by that, but using set_periods_near better expresses the intention.) The only difference between old and new code is on hardware that does not support the desired buffer size. In this case, the old code would try to use a fixed period size, which would result in less or more than four periods per buffer, while the new code always tries to use four periods, which results in shorter or longer periods.

  Hardware parameters are set and fixed in the order in which the various snd_pcm_hw_param_set_xxx functions are called. So, if set_period_time_near set the period time to one quarter of the _desired_ buffer size, but if the _actual_ buffer size set by set_buffer_time_near is smaller due to hardware limitations, the goal of having four periods per buffer is not met. Calling set_periods_near sets only the ratio between period time and buffer time. This means that the period time is set at the same time with the buffer time (when set_buffer_time_near is called), and that the period time is one fourth of the _actual_ buffer time. (The same effect could by accomplished by moving the call of set_period_time_near after the buffer_time call and using the actual buffer time returned by that, but using set_periods_near better expresses the intention.) The only difference between old and new code is on hardware that does not support the desired buffer size. In this case, the old code would try to use a fixed period size, which would result in less or more than four periods per buffer, while the new code always tries to use four periods, which results in shorter or longer periods.
• Nov 30, 2009

  issue 8 (ALSA recording unreliable with Envy24 cards) commented on by raf...@riseup.net   -   Can you please explain me why do you use other alsa function, and if this patch may put other soundcards recording under any risk of malfunctioning? If it offer no risk, I can apply the patch to trunk.

  Can you please explain me why do you use other alsa function, and if this patch may put other soundcards recording under any risk of malfunctioning? If it offer no risk, I can apply the patch to trunk.
• Nov 25, 2009

  issue 8 (ALSA recording unreliable with Envy24 cards) reported by cladisch   -   When using the ALSA source with an Envy24-bases sound card, there are dropouts and noise in the data. The reason is that this hardware has a strict limitation on the buffer size (1/4th of a second at 22 kHz), so the period size that is chosen is almost as big as the actual buffer size, i.e., the application has almost no opportunity to read data before an overrun occurs. This can be solved by not trying to set a fixed period size; see the patch.

  When using the ALSA source with an Envy24-bases sound card, there are dropouts and noise in the data. The reason is that this hardware has a strict limitation on the buffer size (1/4th of a second at 22 kHz), so the period size that is chosen is almost as big as the actual buffer size, i.e., the application has almost no opportunity to read data before an overrun occurs. This can be solved by not trying to set a fixed period size; see the patch.
• Nov 15, 2009

  darkice-0.20.1.tar.gz (Darkice 0.20.1) file uploaded by raf...@riseup.net
• Nov 15, 2009

  r460 (I forgot to put rc.darkice in the EXTRA_DIST, so make dist c...) committed by raf...@riseup.net   -   I forgot to put rc.darkice in the EXTRA_DIST, so make dist created a tarball missing the rc.darkice

  I forgot to put rc.darkice in the EXTRA_DIST, so make dist created a tarball missing the rc.darkice
• Nov 14, 2009

  darkice-0.20.1.tar.gz (Darkice 0.20.1) file uploaded by raf...@riseup.net
• Nov 14, 2009

  r459 (0.20.1 released) committed by raf...@riseup.net   -   0.20.1 released

  0.20.1 released
• Nov 14, 2009

  r458 (preparing for 0.20.1 release) committed by raf...@riseup.net   -   preparing for 0.20.1 release

  preparing for 0.20.1 release
• Nov 14, 2009

  r457 (start/stop/restart/status script for darkice by Niels Detten...) committed by raf...@riseup.net   -   start/stop/restart/status script for darkice by Niels Dettenbach

  start/stop/restart/status script for darkice by Niels Dettenbach
• Nov 14, 2009

  r456 (start/stop/restart/status script for darkice by Niels Detten...) committed by raf...@riseup.net   -   start/stop/restart/status script for darkice by Niels Dettenbach

  start/stop/restart/status script for darkice by Niels Dettenbach
• Nov 11, 2009

  issue 6 (DarkIce: DarkIce.cpp:1140: can't open connector [0]) commented on by tubularluggage   -   I don't understand what the error message is, is it the connector to the sound device or to the server?

  I don't understand what the error message is, is it the connector to the sound device or to the server?
• Nov 11, 2009

  issue 7 (make fails with ubuntu 9.10 g++ 4.4.1) commented on by a.beinartas   -   Thank You! It was a very quick fix. checked out svn and darkice now compiles perfectly!

  Thank You! It was a very quick fix. checked out svn and darkice now compiles perfectly!
• Nov 11, 2009

  r455 (backported trunk fix for gcc 4.4) committed by raf...@riseup.net   -   backported trunk fix for gcc 4.4

  backported trunk fix for gcc 4.4
• Nov 11, 2009

  issue 1 (CoreAudio patch) Status changed by raf...@riseup.net   -   patch now in branches/darkice-macosx

  Status: Accepted

  patch now in branches/darkice-macosx

  Status: Accepted
• Nov 11, 2009

  issue 7 (make fails with ubuntu 9.10 g++ 4.4.1) Status changed by raf...@riseup.net   -   fixed.

  Status: Fixed

  fixed.

  Status: Fixed
• Nov 11, 2009

  r454 (fix compilation for gcc >= 4.4) committed by raf...@riseup.net   -   fix compilation for gcc >= 4.4

  fix compilation for gcc >= 4.4
• Nov 11, 2009

  r453 (initial coreaudio patch) committed by raf...@riseup.net   -   initial coreaudio patch

  initial coreaudio patch
• Nov 11, 2009

  issue 7 (make fails with ubuntu 9.10 g++ 4.4.1) Owner changed by raf...@riseup.net   -   I'll fix it as soon as possible.

  Owner: raf...@riseup.net

  I'll fix it as soon as possible.

  Owner: raf...@riseup.net
• Nov 11, 2009

  r452 (darkice branch to better support macos x) committed by raf...@riseup.net   -   darkice branch to better support macos x

  darkice branch to better support macos x
• Nov 11, 2009

  darkice-0.20.tar.gz (Darkice 0.20) file uploaded by raf...@riseup.net
• Nov 10, 2009

  darkice-0.20.1.tar.gz (Darkice 0.20 Re-Released) file uploaded by raf...@riseup.net
• Nov 10, 2009

  issue 7 (make fails with ubuntu 9.10 g++ 4.4.1) reported by a.beinartas   -   I can not compile darkice no more on ubuntu 9.10 witch uses g++ 4.4.1. make fails with: Util.cpp: In static member function ‘static char* Util::fileAddDate(const char*, const char*)’: Util.cpp:311: error: invalid conversion from ‘const char*’ to ‘char*’ make[2]: *** [Util.o] Error 1 I tried both 0.19 anf 0.20 versions. I think it's g++ problem but do not know how to fix it...

  I can not compile darkice no more on ubuntu 9.10 witch uses g++ 4.4.1. make fails with: Util.cpp: In static member function ‘static char* Util::fileAddDate(const char*, const char*)’: Util.cpp:311: error: invalid conversion from ‘const char*’ to ‘char*’ make[2]: *** [Util.o] Error 1 I tried both 0.19 anf 0.20 versions. I think it's g++ problem but do not know how to fix it...
• Nov 05, 2009

  issue 4 (Darkice compile fails on Ubuntu 9.04) commented on by david.often   -   I cannot thank you enough for addressing this! Your turnaround time is also very impressive (seriously! for a free resource, a couple months to code, test and release is awesome) so thanks again. I LOVE THIS PRODUCT!

  I cannot thank you enough for addressing this! Your turnaround time is also very impressive (seriously! for a free resource, a couple months to code, test and release is awesome) so thanks again. I LOVE THIS PRODUCT!
• Nov 05, 2009

  darkice-0.20.tar.gz (darkice 0.20) file uploaded by raf...@riseup.net
• Nov 05, 2009

  r451 (version 0.20 released.) committed by raf...@riseup.net   -   version 0.20 released.

  version 0.20 released.
• Nov 05, 2009

  r450 (more cosmetic changes for 0.20) committed by raf...@riseup.net   -   more cosmetic changes for 0.20

  more cosmetic changes for 0.20
• Nov 05, 2009

  r449 (preparing for the new version) committed by raf...@riseup.net   -   preparing for the new version

  preparing for the new version
• Nov 05, 2009

  r448 (small cosmetic fixes for 0.20 version) committed by raf...@riseup.net   -   small cosmetic fixes for 0.20 version

  small cosmetic fixes for 0.20 version
• Nov 05, 2009

  issue 6 (DarkIce: DarkIce.cpp:1140: can't open connector [0]) commented on by raf...@riseup.net   -   where is the darkice.cfg you used?

  where is the darkice.cfg you used?
• Nov 05, 2009

  issue 4 (Darkice compile fails on Ubuntu 9.04) Status changed by raf...@riseup.net   -  

  Status: Fixed

  Status: Fixed