Wondering if any clever workarounds exist for moving Playlists. As outlined in the SM Docs, they are associated with a database. When that database is rebuilt (new sounds added for example) the Playlists do not move forward.
I believe the SERVER product will allow moving playlists. Large expense for this objective, but not ruled out... In the meantime, trying to create a workaround and wondering if anyone has attempted the same.
Here's the rather clunky workflow I have at the moment:
Use DB that includes playlists
Via the Admin Metadata Editor, add a "_____Playlist" name to an unused metadata field (I'm using "Tape") for all sounds in the playlist.
Embed meta data for selected Records
Repeat for all Playlists using distinctive playlist tags
Create New Database
Scan entire archive
Use Advanced Search to locate and populate via the tag created for each playlist
Create Playlist
Drag results into Playlist
For episodic and series work, the Playlists are very helpful and worth the effort. Interested to hear if I'm missing something in terms of workflow.
Thanks!
Todd Busteed
GAP Digital
SM v4.5Pro v224