Yes, with the caveat that the automatic ripper is one place where our
documentation lags the current implementation.
#!/bin/bash
LOCKFILE=/opt/wmfo/import/import.lock
cd /var/import/automatic
if [ -f ${LOCKFILE} ]
then
echo "Lockfile is in place."
exit 1
fi
touch ${LOCKFILE}
find /var/import/automatic -mmin +60 -name *.wav -exec
/usr/local/bin/rdimport --verbose --fix-broken-formats --autotrim-level=-60
--delete-source
--metadata-pattern=\%a\!\&\%t\!\&\%l\!\&\%u\!\&\%e\!\&\%c.wav MUSIC \{\} \;
rm ${LOCKFILE}
Thanks,
Nicholas Andre
Operations Director
WMFO Medford
On Sun, Feb 1, 2015 at 12:13 PM, Andy Sayler <[email protected]> wrote:
> Hi Bill,
>
> Most of our code is on GitHub: https://github.com/wmfo. What's not on
> GitHub can be found on the subpages on the Wiki under
> https://wiki.wmfo.org/Operations/Code/Automatic_CD_Import_System.
>
> And as Nick pointed out to correct my original post, we're actually
> ripping straight to wav at the moment and encoding metadata into the
> filenames due to issues getting Rivendell to read metadata properly form
> flac files on import.
>
> -Andy
>
> On Sun, Feb 1, 2015 at 9:52 AM, Bill Putney <[email protected]> wrote:
>
>> Andy,
>>
>> Sounds like you folks are in the early adopter classification. Is any of
>> the code base sharable? ;)
>>
>> Bill
>>
>>
>> On 2/1/15 8:28, Andy Sayler wrote:
>>
>> Hi Bill
>>
>> We've been using a MF-Digital RipStation 7601-XDP for years:
>> https://wiki.wmfo.org/Operations/Music_Department/Ripper-7601XDP. That
>> said, it looks like that model has now be discontinued in favor of their
>> more-complex multi-drive models. Prior to the 7601-XDP, we used a Recordex
>> RX100PC:
>> http://www.allprosound.com/catalog/product-details-discontinued~fprodid~7201.htm.
>> It has also now been discontinued.
>>
>> We use MF Digital's RipStation software with the 7601-XDP. Prior to
>> that, we used dbPowerAmp's batch ripping module with the RX100PC. Both sets
>> of software supports metadata lookups via MusicBrainz, etc, and spit out
>> rejected CDs (e.g. one's with no metadata) to a separate rejects pile where
>> we can review and manually rip them. We rip to flac and then have a set of
>> scripts that perform various filtering and classification operations, read
>> the flac metadata, convert the files to wav, and import them into
>> Rivendell. We've had to do our ripping from a Windows machine since Linux
>> autoripper drivers and software have been hard to come by. We rip to a
>> network share which is then accessed via a Linux machine running nightly
>> cron jobs kicking off the import system. See
>> https://wiki.wmfo.org/Operations/Code/Automatic_CD_Import_System for
>> details on the process.
>>
>> We currently have about 12 TB worth of music in our digital collection,
>> which translates to having ripped approximately 25,000 CDs over the last 5+
>> years. We're a Freeform station that used to have a very large and diverse
>> CD collection, all of which as been converted to lossless digital at this
>> point. We could not have done this without our auto-rippers. That said, we
>> have burned through a number of the rippers over the years. I believe we
>> went through two RX100PCs before switching to the RipStation 7601-XDP, and
>> we're on at least our second one of those. Ripping several hundred CDs per
>> week had generally only lead each ripper to last a year or two. Our rip
>> rate was higher early on, so the newer rippers have lasted longer since
>> we've finished ripping the existing collection and now only must rip the
>> 10s of CDs that come into the station each week. The biggest killer of
>> these devices for us has been slightly out-of-spec CDs that re a bit larger
>> then they should be, thus jamming the device and leading the gears
>> stripping or motors dying. Babysitting the rippers and quickly catching and
>> resolving such jams minimizes the damage they cause, but that kind of
>> subverts the point of an auto ripper in the first place.
>>
>> So my advice would be to look for a solution in the $500 to $1000 range
>> and plan on replacing it every few years. Buying extended warranties, where
>> available, may be beneficial if you know you'll be ripping a lot of CDs and
>> thus will likely break your ripper in the course of 1 to 2 years of
>> operation. You'll also need to plan to spend a little bit of time
>> coordinating various pieces of software to get everything from the ripper
>> into Rivendell since Rivendell doesn't have any native batch-ripping
>> support (or at least none that I know of or that interfaces with any of the
>> rippers we've used).
>>
>> Cheers,
>> Andy Sayler
>> WMFO Medford
>>
>> On Sat, Jan 31, 2015 at 9:25 AM, Bill Putney <[email protected]> wrote:
>>
>>> Now that robotic CD handlers have come down out of the stratosphere
>>> price-wise, I was wondering if anyone has experimented with one to rip
>>> material for Rivendell?
>>>
>>> I guess I see this happening on a Mac or PC outputting some metadata
>>> tagged intermediate file format that RDimport can deal with (like FLAC). It
>>> seems to me that Fred G. once told me that Rivendell could deal with
>>> metadata in Chart Chunk but I don't know of a ripper that really knows how
>>> to store stuff that way. Personally I'd be really happy to have 44.1
>>> Ksps/16 bit PCM Stereo files without any intermediate conversion but that
>>> seems to be problematic from the metadata transport perspective.
>>>
>>> The other question about automatic ripping is, does anyone know of a
>>> ripper that can make and exception list of the missing metadata? Since we
>>> have to deal with SoundExchange royalty reports, having an automated ripper
>>> rip 100 CD's with missing metadata creates a mess that's a hassle to clean
>>> up. I want to go look in each file to see if all the required the data is
>>> there. Better to have a .csv file that shows what metadata was collected
>>> and what's missing for the rip run. Then it's easier to go back and clean
>>> it up.
>>>
>>> I was looking at this handler from Acronova. Anyone have any others that
>>> are in the price range that has worked in a Rivendell importing scheme
>>> they've worked out?
>>>
>>> Acronova Nimbie
>>> <http://www.acronova.com/product/auto-blu-ray-duplicator-publisher-ripper-nimbie-usb-nb21/9/review.html>
>>>
>>> Bill
>>>
>>> _______________________________________________
>>> Rivendell-dev mailing list
>>> [email protected]
>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>>>
>>>
>>
>>
>
> _______________________________________________
> Rivendell-dev mailing list
> [email protected]
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
>
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev