# How to prepare a playlist for Stems in Traktor with DJ Nimi Canonical: https://dj-nimi.web.app/en/blog/traktor-batch-stems-guide/ Language: en DJ Nimi | 2026-09-25 | Updated: 2026-09-30 Queue Stems requests from inside Suite: set up Accessibility and the shortcut, select the first row, enter the row count and check results in Traktor. ## How can you prepare a Traktor playlist for Stems without repeating every click? DJ NIMI Traktor Suite lets you send Stem-generation requests for the tracks in a playlist from one screen. Traktor still does the audio separation and manages its own processing queue. The Suite automates the repeated keyboard actions: request generation for the current row, pause briefly, then move to the next row. You do not have to wait for each audio file to finish before requesting the next one. This guide describes the integrated workflow in the current Mac release, rather than the older helper that tried to recognize tracks on screen. Start with a short playlist containing music you actually want to use with Stems. A useful vocal, a distinctive drum part or a bass line you want to replace during a transition gives the preparation a clear purpose. Sending an entire collection before listening to a few results can leave you with a large processing queue and files you never use. The Suite saves repetitive input; it does not improve Traktor's separation algorithm or decide whether the extracted parts will sound good in your set. ## What should you set up before the first run? Keep a backup of your Traktor collection and settings. The Suite uses the Generate Stems keyboard command supplied by its basic EQ and Stems mapping. If that mapping is already installed, you can skip installing it again. Otherwise, close Traktor, install the shortcut from the Suite and read the summary of any conflicting assignments. Then reopen Traktor. The preparation shortcut is Control+Shift+F12; verify that it works on a test track before trying a longer playlist. The optional performance keyboard profile is a separate choice and does not include Stem generation. Replacing your keyboard mappings with that profile can therefore leave the preparation shortcut unavailable. Check the mapping you actually have installed instead of repeatedly starting the queue when nothing happens. Installation and preparation also require different application states: close Traktor when changing its settings, but keep it open when sending generation requests. The Suite does not replace a Traktor license or add native Stem generation to a version that lacks it. ## How should you select the playlist and starting track? Stop every deck, turn off Cruise and stop recording before running the preparation queue. Open the intended playlist, clear the browser search and select only its first track. Make sure keyboard focus is on the track list rather than a text field or another panel. The sequence depends on moving down through that list. A search filter, an unexpected starting row or a changed sort order can cause the submitted rows to differ from the playlist you intended to prepare. Enter the exact number of visible tracks that you want the run to cover. The Suite does not automatically identify the selected playlist, count its rows or verify each title. If you enter too few rows, part of the list will remain unrequested. If you enter too many, the sequence may reach the end and send further requests from an unintended state. Use a small test list first so you can observe selection movement and confirm that Traktor accepts the shortcut on your setup. ## Which macOS permission does the integrated tool need? Allow DJ NIMI Traktor Suite under Accessibility in macOS System Settings. This permission lets the application send the keyboard actions used by the preparation workflow. The integrated Stems tool does not need Screen Recording permission and does not launch a separate helper application. Instructions for an older screen-recognition helper do not describe this version. If permission is missing, follow the application's guidance and check the entry for the Suite itself rather than granting access to unrelated programs. Keep the distinction between permission and successful processing clear. Accessibility allows the input action; it does not confirm that the shortcut is installed, the right row is selected or Traktor has finished separating a track. After enabling access, test a short run and watch what Traktor does. There is no need to upload your music to DJ Nimi or create an account for this workflow. Traktor performs the audio processing on your computer, while the Suite handles the repeated requests. ## What happens after you start the queue? The tool sends the generation shortcut, waits for the configured interval and advances through the playlist. The default interval is one second between tracks. This pause spaces out the input actions; it is not an estimate of the time required to separate a song. Traktor may continue processing for much longer after the Suite has sent the last request. Watch Traktor's own progress display to understand the state of the audio work. Leave Traktor in focus while requests are being sent. Do not click another row, change the sort order, type into search or open a different playlist during the run. The integrated workflow does not read track names to correct a changed selection. Switching to another application stops new requests instead of continuing to send commands to an unrelated window. Once the request sequence has ended, inspect Traktor before assuming that all the files are ready to load and play. ## Does the tool skip tracks that already have Stems? No. It sends a request for every row included in the run, including tracks that already have Stems. Traktor may regenerate those files and use additional processing time or storage. The Suite does not inspect existing output to decide which rows to skip. This is an intentional simplification of the workflow, so choose your playlist with that behavior in mind. If you only want to prepare certain tracks, create a smaller list containing those tracks before starting. Repeated entries deserve the same attention. If a playlist contains the same recording more than once, the Suite can submit it more than once because it follows rows rather than identifying unique audio files. Do not interpret the request count as the number of different songs processed. Inspect the playlist beforehand and remove unwanted duplicate entries from the preparation list if appropriate. You do not need to delete your original audio or existing Stem files just to make the queue run. ## What does the progress counter actually mean? The counter shows requests sent, not completed Stem files. Reaching the end of the displayed count means the Suite has finished its input sequence. It does not certify that Traktor accepted every request, completed every job or produced usable separation for every recording. This distinction is especially important with a large playlist, because sending the commands can be much faster than processing the audio. Keep Traktor open and check its own queue after the Suite finishes. Verify a few completed tracks by loading their Stem versions and listening to the parts. A file that exists can still contain audible separation artifacts, and a request that was sent may need attention in Traktor. Check the actual result instead of relying only on a counter or a disappearing progress indicator. For an important set, review every part you plan to use in a transition. The queue reduces repetitive preparation; listening remains the test of musical usefulness. ## What should you do if the run stops or the selection changes? Bring Traktor back to the foreground and inspect the selected row and processing queue. Do not restart blindly from the beginning: some requests may already be queued or finished. Identify what still needs preparation and make a short remaining-work playlist if that is clearer than continuing inside a long list. Start a fresh run only when the starting row, visible count and focus are clear. The tool does not automatically reconstruct where a changed playlist should resume. Stopping the Suite prevents new requests. It does not necessarily cancel jobs already submitted to Traktor, which has its own processing controls. Check those controls if you need to stop audio processing as well. If the shortcut produces no visible response, test it on one track and check the mapping and Accessibility permission. If row movement is unreliable, stop and inspect browser focus before trying again. Repeatedly restarting a long run can create duplicate work without resolving the original input problem. ## How should you plan processing time and disk space? Separation time depends on your Mac, the length and content of the tracks, and Traktor's workload. A one-second request interval does not mean a song takes one second to process. Start with a handful of tracks and observe your computer before choosing the size of a larger batch. Keep the relevant drives connected and avoid putting the computer to sleep while Traktor is processing. The Suite's request count is not a benchmark for audio-generation speed. Check free space on the volume where Traktor stores generated files and leave room for temporary work. The integrated queue does not provide the older helper's per-track storage estimate or output verification. Existing Stems may be regenerated, so include that possibility when planning a run. Keep the original recordings available and verify file locations before moving a collection to another drive or computer. Copying a playlist alone does not necessarily copy every audio file that playlist references. ## How do you turn the completed Stems into a useful set? Listen to the sections you intend to mix: vocals during sparse passages, drums around fills and bass during the handover between tracks. An artifact that is unobtrusive in the full recording may become obvious when its part is isolated. Rehearse the transition at a sensible listening level and keep the original track available as a fallback. Preparing more files is useful only when those files give you musical options you understand and can control. DJ Nimi built the Suite to make preparation more convenient, while leaving Traktor responsible for generation and the DJ responsible for the musical decisions. It is independent experimental software for Mac, provided free and used at your own risk. The central download page contains the current installer, requirements and acknowledgement before downloading. Read those details, test a small playlist and expand after checking the results. A good first session ends with a few verified, useful tracks rather than an unexplained counter covering your whole library. ## DJ NIMI Traktor Suite Preparing tracks in Traktor for your next set? DJ NIMI Traktor Suite brings together Hot Cue and Stem preparation tools, keyboard mappings and track-title display fixes. Read the installation guide and check compatibility before use. Experimental, unofficial software, provided as is. Back up your collection and settings independently. Use at your own risk; no guarantee of compatibility or recovery. DJ Nimi accepts no responsibility for loss to the extent permitted by law; statutory rights remain unaffected. macOS 14.2+ · Version 1.5.3 · Not notarized by Apple. Prepare before a performance, never during one. [Download for Mac](https://dj-nimi.web.app/en/download/) - [Native Instruments — Stem generation and playback](https://docs.native-instruments.com/ni-tech-manuals/traktor-pro-manual/en/advanced-usage-tutorials) ## Does DJ Nimi’s tool separate the audio itself? No. It sends Stem-generation requests. Traktor performs the audio separation and manages its own processing queue. ## Must Traktor be open for batch preparation? Yes. Install the shortcut with Traktor closed, then reopen it. Stop all decks, Cruise and recording, clear search and select only the first track in the playlist. ## Does the integrated tool need Screen Recording or a separate helper? No. Allow DJ NIMI Traktor Suite in macOS Accessibility. The integrated tool does not need Screen Recording or a separate helper app. ## Does the tool skip tracks that already have Stems? No. Every row in the run receives a request, including tracks with existing Stems. Traktor may generate them again. ## Does the counter show completed files? No. It counts requests sent. Check Traktor’s progress and listen to the results to confirm completion and musical suitability. ## How long does the tool wait between tracks? The default interval is one second between requests. This spaces out input actions; it is not the processing time of a song. The tool does not wait for each file to finish before requesting the next. ## What happens if I switch apps or stop the tool? Switching apps stops new requests. Jobs already submitted to Traktor may continue. Inspect the queue and selected row before restarting. ## Does the tool count tracks and check storage automatically? No. Enter the exact visible row count and check free space separately. The integrated queue does not verify track names, completed output or storage requirements for each song.