David, There has been quite a number of improvements in rdimport with the newest releases and it is much better then it used to be, but it still at times can run into issues. The fact that there are a lot of poorly created mp3's floating around and a lot of software that creates files that are like an mp3 but which only partially comply with the format. These types of things can make it challenging to create something that'll work with everything 100% of the time.
Keep in mind that Rob's post started with: > I built a Rivendell machine for WZBR AM 1410 a couple years ago when that Rob's working with an older build of Rivendell. It is entirely possible that the files in question might import okay on the latest 2.11.0 build. > Um, so if there's a way to "fix" VBR or "improper" MP3 files before > importing them with rdimport, how come rdimport can't do that work for > us? Has anyone looked at the transcoding method inside > utils/rdimport/rdimport.cpp? Is it worth taking the time to improve > rdimport? > > ~David > > > On 02/26/2016 09:18 AM, Lorne Tyndale wrote: > > I've run into stuff like that too, usually it is an issue with the MP3 > > not necessarily meeting the standard format for mp3's, but being "close > > enough" to play on most players. It can also be the vbr stuff as > > suggested. > > > > You could try running the mp3's through mp3val before importing and see > > if it finds issues. To test, just try running mp3val on some copies of > > the original files and see if it finds problems. > > > > Otherwise - as suggested - it might be easiest to uncompress the files > > before importing. > > > > > > > >> > >> 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 > >> > >> -- > >> Я там, где ребята толковые, > >> Я там, где плакаты "Вперёд", > >> Где песни рабочие новые > >> Страна трудовая поёт.<hr>_______________________________________________ > >> Rivendell-dev mailing list > >> Rivendell-dev@lists.rivendellaudio.org > >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > _______________________________________________ > > Rivendell-dev mailing list > > Rivendell-dev@lists.rivendellaudio.org > > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iF4EAREIAAYFAlbQcIYACgkQZtxZ++32cNgSPgEApf2CGGH7qYoZnsyxaRjzeB75 > E9/pauW5HuOSvEARFW8BAJy0+JHad8AkZ/F3qNV1+BcwF6NASjJc4usoYvPJoZ32 > =Vc8/ > -----END PGP SIGNATURE----- _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
