Silly me, I clicked reply which makes it reply to the last person that sent an 
email in the same thread instead of replying to the group. 😖

> On Oct 26, 2017, at 10:08 PM, Matthew Chambers <[email protected]> 
> wrote:
> 
> I’d be curious how a person could use this feature to generate a log into not 
> one large file but say, hour long blocks to distribute for rebroadcast. That 
> way the end station can import them and play their legal ID at the top of the 
> hour between the :59:50ish long audio files if one created their log that 
> way. 
> 
> What I’m thinking is that I could generate a log for say a 4 hour show with 
> voice track markers in it based on clocks I create in Rivendell, then use the 
> log-editor to record and segue the voice tracks and then render the thing and 
> upload it for radio stations to download and import. 
> 
> Matthew A. Chambers
> 660-346-0703
> 
> Day job 1
> Director - Macon County Office of Emergency Management
> 101 Washington St, Macon MO 63552
> 
> Day job 2
> M Chambers Communications Engineering
> Broadcast Engineering and Icom 2-Way Radio Sales & Service
> 
> Side job
> Firefighter - Atlanta Volunteer Fire Department
> 
> Night job
> Co-host Macon Tiger Football on True Country KLTI 93.3, 102.7, 106.5 FM and 
> 1560 AM
> And online at kltiradio.com
> 
>> On Oct 26, 2017, at 9:28 AM, Lorne Tyndale <[email protected]> wrote:
>> 
>> Fred,
>> 
>> I admit that those are good questions, XML may not be the best format. 
>> Embedding the information in the audio file may not be the best option. 
>> I prefer to have an external file generated for a number of reasons, it
>> could be a text file (or CSV or something similar).
>> 
>> My main thought would be the ability to generate an output report
>> similar to a playout report which could be included with the rendered
>> audio file (in the situation where you are rendering to a file).  That
>> way for example if I put together a 2 hour program that is to air on
>> another station I can render it to a file and send both the audio file
>> and a track list file to whomever I am sending it to.
>> 
>> I do see how some of that information can be gathered with the --verbose
>> option and then it is possible to do a database lookup to pull any
>> additional track / cart information that I might want to include in my
>> track list.  I'm just looking to see if there is a more elegant option.
>> 
>> Lorne Tyndale
>> 
>> 
>> 
>> 
>>>> 
>>>> An XML file would probably make the most sense for this - similar to the
>>>> XML files that can be generated with RDExport.  
>>> 
>>> I agree that generation of a separate manifest file containing the details 
>>> you mention would make a lot of sense.  Embedding it into the audio file 
>>> begs the question of how to structure the containing data chunk.  To just 
>>> say ‘XML’ is not a sufficient specification; what DTD should be used?  Are 
>>> there any tools out there already that are capable of reading such data?  
>>> We could just write the whole thing as a text block (say, into the TagText 
>>> structure of a CartChunk), but are there other, more structured, formats 
>>> that would make more sense?
>>> 
>>> Cheers!
>>> 
>>> 
>>> |----------------------------------------------------------------------|
>>> | Frederick F. Gleason, Jr. |              Chief Developer             |
>>> |                           |              Paravel Systems             |
>>> |----------------------------------------------------------------------|
>>> |  You can never tell which way the train went by looking at the       |
>>> |  tracks.                                                             |
>>> |                                              -- Kramer's Law         |
>>> |----------------------------------------------------------------------|<hr>_______________________________________________
>>> 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
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to