Great idea. I'd not considered that workflow but I shall use it in future! Mike
________________________________ Mike Cox Managing Director The Rosetta Group Ltd Email: mike@rosetta.group<mailto:mike@rosetta.group> Website: www.rosetta.group<http://www.rosetta.group> Phone: 01983 229 229 [https://www.rosetta.group/wp-content/uploads/2019/06/rosettaGroup-logo-transparent.png]<http://www.rosetta.group> Have a look at our new cloud phone system at www.rosettatelecom.com<http://www.rosettatelecom.com> See our payment options and pay online by clicking here Pay online<http://www.rosetta.group/payment> On 12/02/2020 13:49, David Klann wrote: Hi Mircea, On Wed, 2020-02-12 at 06:26 -0500, you wrote: Hi! Is there a way to handle with this ? I mean, If you import 30 songs via rdimport, in the MUSIC group, and you want .csv file with only these 30 songs, to import in M1 or Powergold, how do you proceed? My workaround is to go through an intermediate group, say MUSICADD and then move them into MUSIC. Somebody else ? I actually prefer this workflow (import audio tracks into a "staging" group, then manually move to MUSIC [or wherever]). It gives the "music director" a chance to fine-tune markers (especially Segue), double check metadata, and give one final check for airplay suitability. Importing directly into MUSIC makes all this a bit more ... I guess, dicey? But I am a technician who favors "database cleanliness" over lots of other things, so maybe I'm not the best judge of day-to-day radio station workflows. :) ~David Klann _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org<mailto:Rivendell-dev@lists.rivendellaudio.org> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
