Thanks Mike.
I'd been beating my head against RDCatch to get some sort of wildcards to
work with no luck.
Using separate dropboxes for each program is a really good idea.  Much
easier all around.
I've already got some dropboxes in place for various announcer-produced
content.  Just need to expand the idea.

Thanks
Jeffrey

On Wed, Jul 7, 2021 at 4:29 PM Mike Carroll <[email protected]> wrote:

> RDCatch won't work for this, specifically because it doesn't handle
> variable file names very well. We use Rivendell's dropbox facility instead,
> with separate download folders for each program. The dropbox events can
> then set to look for a fully generic file name (*.mp3 for example) and not
> worry about the messy parts of the file name.
>
> Dropboxes are managed on a per-host basis in RDAdmin.
>
> Note that there are two file mask patterns in a dropbox definition: one
> for the location and name of the file to ingest ("Path Spec") and another
> one that specifies pieces of information that can be extracted from the
> file name ("Metadata Pattern"). The name/location mask can have
> generic-match characters in it.
>
> Mike
>
> On Wed, Jul 7, 2021 at 1:22 PM Jeffrey Blair <[email protected]> wrote:
>
>> We have just installed our PRSS Satellite Receivers (XDS-PRO) after
>> moving to a new facility.  Before the move we were using Enco and file
>> ingestion was working through a dropbox configuration.  Now that we are
>> with Rivendell (thank goodness!) I wanted to configure file ingestion
>> through RDCatch.  Is this the best way to go?  Maybe just use Dropbox to
>> monitor a mirrored folder?  How do I handle the fact that cutID numbers and
>> portions of the CDLongName change with each program?
>>
>> So I ask the braintrust...what is the best way to handle ContentDepot
>> file ingestion into Rivendell?
>>
>> Thanks
>> Jeffrey
>>
>> *Jeffrey Blair*
>>
>> Production Manager/Announcer
>>
>> *KMFA Classical 89.5*
>>
>> 512.472.8160 | [email protected] | kmfa.org <http://www.kmfa.org/>
>> _______________________________________________
>> 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

Reply via email to