I recently made a tweak to bashpodder and mailed it back to linc. He at least thought enough of it to add it to the user contributions page. The tweak changes bashpodder to work in a feed based directory structure, rather than a date based one. What irritated me about the standard method was that it created empty directories when there were no new releases in your feeds and that it didn’t collate released for each program in the same place. So I have to have an idea of when the program was released in order to find the release I want to listen to.
I understand that the empty directories thing was fixed by other user contributed patches, but the directory structure still niggled, so I tweaked away. 🙂 The resulting script is a whole 4 lines shorter than the proper version too! I also understand that podcasting is essentially ephemeral and that most people are just generally expected to want “new sounds” to listen to. Listening to old stuff again isn’t interesting for most people, but I enjoy doing so during my lunch breaks. Even with my patch I can still check the log to find if new releases have been downloaded. (I generally know this anyway, given the feeds to which I subscribe. My MP3 player is too small just to copy stuff onto willy-nilly. Only 128MB 🙁 )
Oh, and the Chris Moyles podcast is sampled at a 56kbps bitrate and my MP3 player won’t play that back. So I have to convert it via LAME in order to play it.
lame --mp3input -b 64 seems to do the trick.
I’ve also found out, care of Neil “blueGremlin” Ferguson that you can capture streaming Real Media files for later play back using
mplayer -dumpfile outputfilename.rm -dumpstream rtsp://host/file.rm. This is especially useful if you have people wanting to use these files, for example in education, but a corporate firewall blocks the RTSP protocol. It does mean doing the dumping from outside of work, which isn’t exactly good for the work/life balance.