Yes, I'm looking for the tags that get imported with the audio. Specifically, the Title. RDLibrary only shows that information for the first cut in the cart. And looking at mysql-workbench, it looks like there's a TITLE column under CARTS, but not under CUTS.

This gives me a list of the cuts inside the cart, but only the numbers. (010022_001, 010022_002, etc.)
select CUT_NAME from Rivendell.CUTS where CART_NUMBER = "010022"

This gives me the title of the first cut that was imported into the cart.
select TITLE from Rivendell.CART where NUMBER = "010022" ;

If I try to get TITLE from Rivendell.CUTS, I get an error message saying that there's no such column as TITLE.

So, if I want to keep the tags associated with a track, I have to import one track per cart. Is that correct?

Greg Avedissian



On 03/10/2016 11:51 AM, Mike Carroll wrote:
As Cowboy says, RDLibrary will show you most of the data.

The SQL statement "select * from rivendell.cuts where CUT_NAME =
nnnnnn_xxx" will dump all of the data that Rivendell has for cut #xxx in
cart #nnnnnn.  MySQL Workbench is your friend for things like this.

When you say "metadata", are you perhaps meaning data in the physical sound
files, such as MP3 tags?  AFAIK there's nothing in Rivendell to view stuff
like that.

Mike Carroll

On Thu, Mar 10, 2016 at 6:34 AM Gregory Avedissian <[email protected]>
wrote:

Is it possible to view metadata associated with individual cuts in a cart
that contains multiple cuts? Either through rivendell directly or through
mysql commands would suffice.

Thanks,
Greg Avedissian
_______________________________________________
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

Reply via email to