You can create a scheduler code called "Unclassified" and make it the default scheduler code for the new imported carts.... then you can use Rdlibrary to select all the carts with the "Unclassified" scheduler code and classify them.
2012/1/16 <[email protected]> > I do not want to create a filename.sc when I do a mass-import of songs. I > rather use RDLibrary to listen to the songs and classify it. So make it > optional, not mandatory. > A visual indication (color/marker) that a song does not have a schedule > code would make this easier. > On a side note: I would really like to be able to use the schedule-codes > in RDLogedit (as a filter). > > Stephan Fijneman > > > > On Mon, Jan 16, 2012 at 6:46 AM, Fred Gleason <[email protected]> > > wrote: > >> On Jan 15, 2012, at 20:01 53, Luigino Bracci wrote: > >> > >>> The scheduler codes are a great feature; in our case, we want to use it > >>> in the music groups for identify the genre of each song. But the > >>> operator can forget to specify the scheduler codes in the music groups, > >>> because they aren't required. So, it would be nice if the administrator > >>> can specify in RDAdmin, that the carts on a group must require (or not) > >>> at least one scheduler code. > >> > >> So what happens for carts that are created automatically (e.g. via > >> dropbox) when this attribute is enabled? A default scheduler code? > > > > 1. have the code configurable per dropbox? > > 2. require the creation of a filename.sc to go in alongside of > > filename.wav/mp3 in and dropbox set to import to groups with forced > > scheduler codes. pullt the code from the matching filename.sc file? > > 3. ??? > > 4. Profit. > > (Sorry,,, could... not... resist...) > >> > >> Cheers! > >> > >> > >> > |-------------------------------------------------------------------------| > >> | Frederick F. Gleason, Jr. | Chief Developer > >> | > >> | | Paravel Systems > >> | > > > > all the best, > > > > drew > > -- > > http://freemusicpush.blogspot.com/ > > _______________________________________________ > > Rivendell-dev mailing list > > [email protected] > > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > > > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
