Playlist Transfer Workaround

64 views
Skip to first unread message

tbus...@gapdigital.com

unread,
Nov 18, 2016, 12:10:46 PM11/18/16
to Soundminer Users Collective
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

Nathaniel Reichman

unread,
Nov 21, 2016, 10:50:51 AM11/21/16
to tbus...@gapdigital.com, Soundminer Users Collective
I’m a huge playlist user and find them absolutely essential for episodic work, especially music editing. I like your metadata solution. Our team simply copies the (4) files in Application Support when moving a database. Clunky, but effective. We’ve never had any problems with playlists when adding media to databases, so maybe I don’t fully understand your problem.

Nathaniel Reichman
Supervising Producer – Re-recording Mixer

Google Voice (rings all phones): (518) 966-2226 | iPhone (Messages/Facetime): (917) 921-3446
Skype: NReichman | Manhattan studio landline: (212) 989-9500


--
You received this message because you are subscribed to the Google Groups "Soundminer Users Collective" group.
To unsubscribe from this group and stop receiving emails from it, send an email to soundminerfor...@googlegroups.com.
To post to this group, send email to soundmi...@googlegroups.com.
Visit this group at https://groups.google.com/group/soundminerforum.
For more options, visit https://groups.google.com/d/optout.

tbus...@gapdigital.com

unread,
Nov 21, 2016, 11:38:12 AM11/21/16
to Soundminer Users Collective, tbus...@gapdigital.com, reic...@mac.com
Hi Nathaniel,

Spot on... If you're adding new sounds to the existing DB, everything stays put.  In my case though, I've added a significant amount of sounds and collectively made quite a few metadata tweaks to the point where if felt like a good idea to rescan the SFX Library.  Hence, the need to wrestle around the playlists.  

And with multiple seats of SM, and the need to scan fresh from other rooms (so that paths are accurate) tying the playlist framework into the metadata means I have the ability to build the playlists in other rooms.


Todd
Reply all
Reply to author
Forward
0 new messages