I've written a perl program called DJ In A Box that does on-the-fly
re-encoding of MP3 data and sends it to a shoutcast server.
It uses LAME (with --decode) to decode the data and then sends that data to
another process for each bitrate that uses LAME to re-encode it (a variation
on 'lame - -').
It basically does this:
1. fork 24k process
2. fork 56k process
3. 24k process open2's 'lame - -'
4. 56k process open2's 'lame - -'
5. main process figures out song to play
6. main process forks lame --decode on song
7. repeat 5 & 6 ad nauseum
The problem is, the encode processes die after about 4 hours, with no
apparent error messages. Because of the long time between failures, I have
yet to be able to do some real accurate timing out of this, but I thought I
would ask in the meantime:
Are there any hard-coded limits that would cause buffers or counters to
roll-over after a long period of continuous encoding?
If anyone could point me in the right direction, I'd appreciate it. I don't
know C well enough to really be able to figure out what's going on in the
code (it's on the list of things to do :).
Thanks,
Ben
--
Ben Reed a.k.a. Ranger Rick ([EMAIL PROTECTED])
http://defiance.dyndns.org/ / http://radio.scenespot.org/
Now playing on Defiance Radio: Listen by David Holmes
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
