<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent posts to news</title><link>https://sourceforge.net/p/audiotools/news/</link><description>Recent posts to news</description><atom:link href="https://sourceforge.net/p/audiotools/news/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sat, 09 Feb 2008 15:24:52 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/audiotools/news/feed.rss" rel="self" type="application/rss+xml"/><item><title>2.7 released, at long last</title><link>https://sourceforge.net/p/audiotools/news/2008/02/27-released-at-long-last/</link><description>Version 2.7 has taken quite awhile to get out the door, I'll admit.  Despite the few feature enhancements between this and 2.6, I finally got sick of all the little bugfixes piling up and decided to release it.

I'll try to get my Git repository hosted somewhere in the near future so people can get fixes or new features a bit faster if they'd like.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Sat, 09 Feb 2008 15:24:52 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd2fff7a070090e3e553c0ab5c6332418c5dec727</guid></item><item><title>Python and the Evolution of Python Audio Tools</title><link>https://sourceforge.net/p/audiotools/news/2007/12/python-and-the-evolution-of-python-audio-tools/</link><description>As I've transitioned Python Audio Tools from working primarily with audio metadata \(track tags, playback parameters, etc.\) to handling audio data itself \(FLAC decoding, track resampling, etc.\) I've come to better understand what Python is good at, and what it still struggles with.

Python is very good at reading in chunks of data, binary or otherwise, parsing them and doing some work with them.  It's proven to be fast, reliable and maintainable.

Python is not very good at doing lots and lots of little calculations.  ReplayGain playback only works because I can run it in its own thread, despite the simplicity of actually applying it.  FLAC decoding, resampling and ReplayGain calculation are all embarassingly slow, despite the use of profiling and C extension modules to speed up the process.

Since software that's too slow isn't practical, I'm going to need a new tactic in order to keep developing stuff that's useful.  I could develop bigger and better C modules to do that calculation work.  But if I'm doing all the heavy-lifting in C, Python becomes extraneous.  I could try to make Python itself much faster and submit some patches, but I suspect there aren't a lot of Really Obvious Speedups I could find.  I could try getting my code to run on a &amp;quot;faster Python&amp;quot; like PyPy, but that's some seriously experimental stuff I can't assume everyone will have.  I could wait around for hardware to become fast enough to give my Python implementations value, but I might be waiting a long time.

I will continue to ponder this problem.  Whether I can solve it and how will determine whether Python Audio Tools will ever evolve beyond their humble metadata-heavy origins into something with a wider purpose.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Wed, 05 Dec 2007 01:56:04 -0000</pubDate><guid isPermaLink="false">https://sourceforge.nete695722c1ac2f17f868fa1318388b78264cff660</guid></item><item><title>FLAC vulnerabilities and the Python Audio Tools</title><link>https://sourceforge.net/p/audiotools/news/2007/11/flac-vulnerabilities-and-the-python-audio-tools/</link><description>eEye Digital Security has issued a report listing 14 vulnerabilities in the libFLAC implementation.  See http://research.eeye.com/html/advisories/published/AD20071115.html

Since Python Audio Tools uses many of its own routines to handle FLAC and its metadata, I've taken a close look at this report to ensure I haven't missed any vital errors.  Fortunately, due to Python's design, the bulk of them simply do not happen barring any bugs in the Python interpreter and I shall explain why.

Vulnerabilities 1, 2, 3, 4, 7, 8, 9 and 12 rely on overflowing malloc\(3\) by assuming the FLAC decoder will allocate an excessive amount of memory at once prior to filling it.  My implementation essentially passes that size argument to Python's read\(\) function call, which doesn't implement large amounts of memory at once and cannot exceed the length of the file.

Vulnerabilities 5 and 6 rely on errors in image handling.  Python Audio Tools actually ignores all image metadata fields except when displaying such information via the trackinfo executable or choosing filenames.  The image data itself is fed to PyGTK which does the actual image rendering work.  Unless PyGTK contains any image parsing vulnerabilities, invalid FLAC image metadata should cause no harm.

Vulnerabilities 10 and 11 exploit FLAC external file capabilities via the '--&amp;gt;' MIME type.  Python Audio Tools does not support these \(nor have I ever seen such files in the wild\).  It will not download any external files.  I may implement this portion of the spec at some point, but it is currently nonfunctional and harmless.

Vulnerabilities 13 and 14 exploit FLAC's seektable.  Since Python Audio Tools does not use FLAC's seektable in any way, one would be vulnerable only if there are some bugs in the &amp;quot;flac&amp;quot; executable itself.

I hope this will ease any fears anyone might have about Python Audio Tool's FLAC handling capabilities.  But if anyone finds a possible exploit I may have missed, please contact me at once so I can fix the problem with timely bugfixes.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Tue, 20 Nov 2007 02:57:28 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7253c808eba49fe33805104375f51cc997df0929</guid></item><item><title>PulseAudio support added</title><link>https://sourceforge.net/p/audiotools/news/2007/11/pulseaudio-support-added/</link><description>I've extended trackplay to support both OSS and PulseAudio as output methods - PulseAudio being the default if present.  There's many advantages to this.  First, trackplay doesn't hog /dev/dsp and block all audio on the system.  Second, PulseAudio supports 32-bit floating point samples, so I don't have to dither high-definition audio anymore.  This saves a lot of CPU during playback.

Assuming I don't stumble across anymore bugs, PulseAudio and ReplayGain will be the focus of a 2.6 release.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Sat, 10 Nov 2007 20:31:12 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netbebde81eafdb4a6c9a75af679b06aa0ec6acde41</guid></item><item><title>ReplayGain support improved</title><link>https://sourceforge.net/p/audiotools/news/2007/11/replaygain-support-improved/</link><description>I've been really picky about adding proper ReplayGain metadata during track creation/conversion, right from the first versions of Python Audio Tools.  The trouble is, I've never actually done anything with it.

But thanks to all the infrastructure work I did for PCM conversion, I've been able to build a ReplayGainReader wrapper for PCMReaders \(similar to the PCMConverter wrapper\) and basic ReplayGain support for trackplay\(1\) literally came together in about half an hour.

Though I haven't added peak support yet, I'm surprised how easy it was to implement.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Sat, 03 Nov 2007 23:13:17 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta1fcdde65c30cb36572c6296366e641cd64a0c9c</guid></item><item><title>libcdio 0.79 released</title><link>https://sourceforge.net/p/audiotools/news/2007/10/libcdio-079-released/</link><description>If you've had any difficulty extracting audio from difficult CDs, it might be worthwhile to upgrade to libcdio 0.79 which features numerous bugfixes.  I've encountered no errors using it with Python Audio Tools and should be a worthwhile upgrade.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Sat, 27 Oct 2007 17:34:27 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net49691275399bfd19a8d79f135a78daa4e5bdea85</guid></item><item><title>PCM conversion work-in-progress</title><link>https://sourceforge.net/p/audiotools/news/2007/10/pcm-conversion-work-in-progress/</link><description>High-definition, multi-channel audio is one of those features Python Audio Tools supports, but I'm pretty sure isn't widely used.  Right now, a lot of the lossy codecs will choke on PCM streams with lots of channels and bits and big sample rates.  I've already got channel culling and bits-per-sample scaling working well enough, but resampling will be another story.

I could use a high quality external resampling library and make hi-def audio ubiquitous throughout the tools.  But when most people are only interested in CD-quality, that's the very definition of an obscure dependency.

So, I can either include a library, compacted into a Python C module so that there'd be nothing new to download.  Or, I could build a Python-based one.  I'm leaning toward the latter, since it'll give me an excuse to learn something.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Tue, 09 Oct 2007 17:52:42 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netb0e0c76bee42b10d512dfe5e2090bb1b480a9a3b</guid></item><item><title>oddball RIFF WAVE chunks now supported</title><link>https://sourceforge.net/p/audiotools/news/2007/09/oddball-riff-wave-chunks-now-supported/</link><description>Most of the time, .wav files are thin wrappers around a big blob of PCM data.  However, it's possible to stick non-PCM chunks in .wav files and not break anything.  Some fancy audio editing tools have been known to do this, for example.  But since Python Audio Tools previously routed all audio through PCM streams, those chunks would get lost during any conversion.

That's not entirely lossless.

Therefore, I've short-circuited the conversion to/from RIFF WAVE files to ensure those chunks are kept by the formats that support them - namely FLAC 1.2.1, WavPack and RIFF WAVE.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Fri, 28 Sep 2007 14:58:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta33d3e32492d332dc19c4b28e05f4f12ddf0f71a</guid></item><item><title>.flac, .mpc and .ape overhauls</title><link>https://sourceforge.net/p/audiotools/news/2007/09/flac-mpc-and-ape-overhauls/</link><description>There's been a few developments in the world of audio formats, some of which will need a bit of coding on my part to support.

Rumors of an update to the FLAC format have been floating around for awhile.  Turns out it's a minor update to the partitioned Rice which won't be difficult to support.  I'll be updating my FLAC decoder and documentation once I can test out the changes on real files.

Musepack Stream Version 8 is also in beta testing.  I'll need to update my documentation and Musepack recognition code for that, too.  Hopefully it'll have some portable tools this time around, too.  I've never gotten mppdec to work on PPC and I hate leaving formats untested on big-endian machines.

Finally, mac-port is back on SourceForge.  I'm still leery of supporting it after the licensing mess the last time.  But if it sticks and I can provide links to it, I'll turn Monkey's Audio support back on again.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Tue, 25 Sep 2007 13:31:15 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net64258a0cad8fde3a4fbb579dac629bd8e96271dd</guid></item><item><title>metaflac's return</title><link>https://sourceforge.net/p/audiotools/news/2007/09/metaflacs-return/</link><description>I'm in the final testing phase for Python Audio Tools 2.4 and just now noticed that FLAC files created via streaming PCM data have no SEEKTABLE metadata blocks.  This doesn't appear to be a big deal since players like &amp;quot;xmms&amp;quot; have no trouble seeking through FLAC files without SEEKTABLEs, but I would like to have them added at create-time.  Therefore I'm bringing back the &amp;quot;metaflac&amp;quot; binary requirement.  I don't expect this will cause any inconvenience since you'll want &amp;quot;metaflac&amp;quot; around anyway for ReplayGain support.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Langenberger</dc:creator><pubDate>Tue, 18 Sep 2007 19:16:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd95a1532b399d9d6e984b95be2b2b20ceb45bf08</guid></item></channel></rss>