Not all mp3's are created equal!
I found we had problems with supplied mp3's which had all sorts of
garbage in the tags which seemed to have been watermarked by one or more
mp3 encoders/players between the source and rdimport. Various encoders
have various patterns. Copious use of characters which are easily
interpreted as commands is the one consistency. If they did import; the
audio would be short.
I wrote a script which set all tags [ there are two varieties ones that
go in the front and ones that go on the tail ] to null, except artist
and title which were set from the filename.
The filenames were cleaned up using another script that hooked out
spaces and characters that upset rdimport.
rdimport would then import 99% without error. The ones that failed were
mostly encoded in bizarre formats.
I did run a resampling script on tracks with edits which cleaned up some
of the failures.
The scripts and the tag editing software were run on my production machine.
I have since discovered that there is a program called mid3v2 which can
zap all tags and the occasional graphic.
|sudo apt-get install python-pip;sudo pip install mutagen|
If you give the mp3 audio files a good de lousing they should import OK;
if they don't resample with lame
lame -V5 --vbr-new --resample 44.1 "$1" "resample/$1"
tip: tell rdimport to get metadata from filename [eg: --metadata=%a-%t]
and it won't go ferreting in the tags.
I still recommend clearing out the junk. I have had problems with
promotional copies of songs provided by well known record companies.
This may be an avenue for undesirable payloads .
Clean up on your hackenabox and upload to your server.
regards
Robert
On 27/02/16 02:27, Rob Landry wrote:
I built a Rivendell machine for WZBR AM 1410 a couple years ago when
that station moved from Brockton to Boston, MA; it's been running
flawlessly. Last month, however, my client decided to lease the
station 24/7 to a third party, and had me move the machine to the
transmitter site where its function would be to run a top-of-hour ID
on top of programming that would be coming from the broker's new
studio via Internet stream.
The broker's new studio isn't ready, so he's been feeding the station
from somewhere in California. The stream has been dropping out a lot,
so I suggested he give me his audio files and I'd load them into the
Rivendell machine and play them from the transmitter site until his
studio is ready.
His audio files are all MP3's, alas, but I rdimported them all last
night and put them on the air about three hours ago.
At the end of each cut, I hear an electronic buzz for five to ten
seconds just before the transition to the next cut. I don't know
what's going on, but I'm guessing it has something to do with the
transitions. I've tried fiddling with the crossfade times and using
"play" instead of "segue" transitions, but nothing seems to answer.
Just now, I heard a clean transition, but it happened about four
minutes into a supposedly 17 minute cut. Looking at Edit Markers, the
cut is in fact only four minutes long; somehow Rivendell got bad
information from rdimport.
I believe a good many of these cuts are shorter than Rivendell thinks
they are. Is there a way to fix this other than manually through Edit
Markers?
Rob
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
--
Robert Jeffares
Communication Consultants
The Wireless Station 1530kHz
Big Valley Radio
Radio Spice
Raupo Radio 1170kHz
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
