Re: lagging lib support
On Saturday 19 January 2002 11:07, Ed Sweetman wrote: It seems that freeamp is not playing nicely with the oss implimentation that the latest alsa 0.9.x lib has. I've traced it to that point. next would be seeing if any other apps do. From the libao README: The OSS emulation in ALSA deviates from the OSS spec by not returning immediately from an open() call if the OSS device is already in use. Instead, it makes the application wait until the device is available. This is not desirable during the autodetection phase of libao, so a workaround has been included in the source. Since the workaround itself violates the OSS spec and causes other problems on some platforms, it is only enabled when ALSA is detected. The workaround can be turned on or off by passing the --enable-broken-oss or --disable-broken-oss flag to the configure script. You might have some luck comparing libao's fix to the freeamp source. John ___ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
Re: lagging lib support
On Friday 18 January 2002 10:57, Ed Sweetman wrote: I check out the cvs in hopes of finding some more up to date support but it doesn't ever seem to be that much better if at all than the releases. Alsa 0.9x has never been supported, despite being out for months, even simple programs such as ogg123 support it. libao (which ogg123 uses to handle output) has only supported alsa0.9 fairly recently. The problem is the APIs have changed significantly between 0.5 and 0.9, and there is little in the way of documentation for 0.9 at this stage (which is one of the biggest problems with ALSA, IMO). John ___ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
Re: Track numbers for MP3s
On 14 Mar 2001 00:11:35 -0800 Colin Marquardt [EMAIL PROTECTED] wrote: Isaac Richards [EMAIL PROTECTED] writes: If you don't have track numbers with your files named that way, try deleting your metadatabase and searching again.. should show up. MusicBrainz had a fun little bug where it would strip off track numbers during a lookup previous to the most recent release. Oh, exactly that was it. That is fine now, thanks. One other thing... since ID3V2 can handle arbitrarily long strings too, it is probably much better to use that for submission to Musicbrainz. What would I use, however, to *create* ID3v2 tags? id3lib/id3v2 from sourceforge? Does it really work? A few months ago, I heard that id3lib wasn't really up to speed yet, and it seems there hasn't been a new release since then... I've found that id3lib is fairly horrible. Have a look on CPAN for a perl library or two that handles them. I've used one of them at home for a re-encoding project and found it as easy to use as any other perl module. One of these days I'll convert it to python. John ___ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
