Music: Practice & Theory Stack Exchange is a question and answer site for musicians, students, and enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm looking to improve my workflow for adding new music to my Traktor collection. I want to improve on how Traktor is configured, how I have set up my hard drive's folder structure and how I process the new music from purchase all the way through to beatgridding.

Currently, my HDD folder structure is like this:

 - Main Traktor directory somewhere on HDD
   - Collection directory (contains all fully prepped music)
   - Preparation directory (contains un-gridded music)
     - 'No tags' directory (contains un-tagged music)

My workflow for processing new music is like this:

  1. Music is purchased on Beatport and fetched in bulk with Beatport Downloader.
  2. I move it into my Traktor\Preparation\No Tags folder.
  3. I use MP3 tagging software to edit the file names and ID3 tags as I see fit.
  4. When I'm done tagging, I move the music up one directory, to the Traktor\Preparation folder.
  5. I open Traktor and start analyzing all music in the Traktor\Preparation folder.
  6. I tweak the beatgrid of all tracks, and insert my desired cue-points for all tracks (Load cue-point, and positions of breaks, drops and outro's for visual reference when mixing). This is probably the most time-consuming step in my workflow, but has proven to pay off when mixing improvised or with little preparation for a gig.
  7. When done beatgridding, I move the music out of the Preparation directory into the Traktor\Collection folder. At start-up, Traktor's consistency check finds missing tracks, and I re-link them to the tracks which are now in the Collection directory.
share|improve this question

closed as primarily opinion-based by Dom, Shevliaskovic, kurto, Jason W, MrTheBard Mar 19 '14 at 17:54

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

Code block Markdown doesn't seem to show up on this SE. – Marc Dingena Mar 14 '14 at 22:20
Code blocks get parsed by jTab (guitar tabulature, holdover from a merge with the Guitar SE site) -- use a <pre></pre> block to get un-parsed, fixed display text. – Dave Mar 14 '14 at 22:22
@Dave that worked, thanks. – Marc Dingena Mar 14 '14 at 22:23
In my opinion, this question is likely on-topic. However, it might be a better fit for, which is focused on music software as one of its sub-topics. – Kevin Mar 18 '14 at 4:23
Sound.SE is a bit unstable right now since it is the result of a relatively recent site merge--chances are they're still figuring themselves out. Migration is generally not advisable for sites still in beta for that reason. – NReilingh Mar 21 '14 at 5:52

Browse other questions tagged or ask your own question.