On Tue, Jan 17, 2012 at 8:31 AM, Fred Gleason <fr...@paravelsystems.com> wrote: > On Jan 16, 2012, at 18:08 41, drew Roberts wrote: > >> iirc, the suggestion was to make this an option on setting up a drop >> box or on setting up a group. Probably the group. > > Why not both? The group setting is the initial default, which can be > overridden by the dropbox setting. The dropbox setting is the default for > for its context, which can be overridden by individual imports. > > >> So if a group was to >> be forced to have a code, (or the droppbox) then you would need such a >> file, if not, you would not. Does that work? > > Why not make it part of the metadata pattern, so codes could be specified as > part of the filename, just like any other metadata? The only place this > might get slightly tricky is when multiple codes are desired. In that case a > special 'inter-code' separator could be specified, resulting in something > like: > > <title>_<artist>_<code 0>^<code 1>^[...]<code n>_<album>_<label>.wav > > in this case, '_' would be the usual field separator, and '^' would be the > code separator. > > This also avoids some potential race conditions that could bite with > scenarios involving multiple files.
It all sounds fine to me. I don't have this need myself at this time. I was just trying to offer a possible approach to the person who made the request. > > Cheers! > > > |-------------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | all the best, drew -- http://freemusicpush.blogspot.com/ _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
