Traktor Pro 4 Load delay

Hello

I recently upgraded to Traktor Pro 4, the day of release. I have used this new software with my S4 MK3 controller at three gigs since the release of this update, so I've had the chance to test it out in a live situation.

The one issue I am having, that takes away from the flow of my set, is the loading times for tracks. In Traktor Pro 3, If I stop a deck and load a track, there is absolutely zero delay loading this track into a deck from when I press STOP on that deck. As for Traktor Pro 4, If I press stop on a deck thats playing, I have to wait at least one second before loading a track, otherwise it flashes "Cannot load into deck thats playing" even though the deck has stopped. I always have "Loading only into stopped deck" turned on, for safety reasons.

Will this be fixed in future releases?

Tagged:

Best Answers

  • Ejub Petrovac
    Ejub Petrovac Member Posts: 42 Advisor
    Answer ✓

    I'm not using the "load only into a stopped deck" option but I can confirm that TP4 loads the songs slightly slower (part of a second) than TP3 and I'm pretty sure it's because of the "load as a stem" or "load as a track" options.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 2,997 mod
    Answer ✓

    The 1 second delay introduced only happens on a new qml loading command with x1mk3, s2mk3, s3 and s4mk3.

    You can remove it (change it) by hand in the qml code. The options available are:

    • Return it to the old code (with only a single load type, stem or track, selected in Preferences→Loading, no delay). → Straightforward.
    • Change it to a custom function with a custom delay. → Complicated.

    You can read up on both in my discussion here:

    Note: The OP may have observed something completely unrelated to the controller code.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 2,997 mod
    edited January 20 Answer ✓

    This concerns only the 1 second delay that Ejub Petrovac observed for TP4.

    In the file '…\Traktor Pro 4\resources64\qml\CSI\Common\ExtendedBrowserModule.qml' (note: for macOS the subfolder 'qml' may be found in a different place) in line 114 you will find this:

    Wire { from: "%surface%.browse.encoder.push"; to: "browser_load_gestures.input" }
    

    Replace this with

      // Wire { from: "%surface%.browse.encoder.push"; to: "browser_load_gestures.input" }
      Wire { from: "%surface%.browse.encoder.push"; to: TriggerPropertyAdapter { path: "app.traktor.decks." + deckIdx + ".load.selected"; output: false } }
    

    This will revert to the single load type from TP3. If you have generated stem version of stereo tracks in Traktor, with this you will only load the version which you have selected in Preferences→Loading (not the alternate version).

    Make a safety copy of the file before changing it up. Better yet, make a safety copy of the whole qml folder.

    Edit: I corrected my coding mistake.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 2,997 mod
    Answer ✓

    So, i made a syntax mistake.

    I wrote (and you copied faithfully):

      Wire { from: "%surface%.browse.encoder.push"; to: "load.selected" }
    

    This is wrong…

    It should have been this:

    Wire { from: "%surface%.browse.encoder.push"; to: TriggerPropertyAdapter { path: "app.traktor.decks." + deckIdx + ".load.selected"; output: false } }
    

    I am sorry for the confusion.

    Please test if it works now.

    🦋

Answers

  • This content has been removed.
  • This content has been removed.
  • This content has been removed.
  • Martiniix_NI
    Martiniix_NI Customer Care Posts: 362 mod

    This can be related to the buffer size, how much buffer size are you allowing?

  • Ejub Petrovac
    Ejub Petrovac Member Posts: 42 Advisor
    Answer ✓

    I'm not using the "load only into a stopped deck" option but I can confirm that TP4 loads the songs slightly slower (part of a second) than TP3 and I'm pretty sure it's because of the "load as a stem" or "load as a track" options.

  • Heisenberg
    Heisenberg Member Posts: 390 Pro

    Exactly because now Traktor are waiting to see whether to click or double click.

    You can change it so that a single click loads the standard song; here at least for me everything is normally fast.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 2,997 mod
    Answer ✓

    The 1 second delay introduced only happens on a new qml loading command with x1mk3, s2mk3, s3 and s4mk3.

    You can remove it (change it) by hand in the qml code. The options available are:

    • Return it to the old code (with only a single load type, stem or track, selected in Preferences→Loading, no delay). → Straightforward.
    • Change it to a custom function with a custom delay. → Complicated.

    You can read up on both in my discussion here:

    Note: The OP may have observed something completely unrelated to the controller code.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 2,997 mod
    edited January 20 Answer ✓

    This concerns only the 1 second delay that Ejub Petrovac observed for TP4.

    In the file '…\Traktor Pro 4\resources64\qml\CSI\Common\ExtendedBrowserModule.qml' (note: for macOS the subfolder 'qml' may be found in a different place) in line 114 you will find this:

    Wire { from: "%surface%.browse.encoder.push"; to: "browser_load_gestures.input" }
    

    Replace this with

      // Wire { from: "%surface%.browse.encoder.push"; to: "browser_load_gestures.input" }
      Wire { from: "%surface%.browse.encoder.push"; to: TriggerPropertyAdapter { path: "app.traktor.decks." + deckIdx + ".load.selected"; output: false } }
    

    This will revert to the single load type from TP3. If you have generated stem version of stereo tracks in Traktor, with this you will only load the version which you have selected in Preferences→Loading (not the alternate version).

    Make a safety copy of the file before changing it up. Better yet, make a safety copy of the whole qml folder.

    Edit: I corrected my coding mistake.

  • DJLeonMusk
    DJLeonMusk Member Posts: 5 Member

    This fix worked with the inital relase of TP4, but does not with newest version (4.1.1) After modifying the code, tracks to not load at all using controller (load button does nothing). Is there a workaround?

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 2,997 mod

    Which controller are you using?

    Please upload the modified file so we can find out what's wrong.

  • DJLeonMusk
    DJLeonMusk Member Posts: 5 Member

    Here is the file I modified

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 2,997 mod
    Answer ✓

    So, i made a syntax mistake.

    I wrote (and you copied faithfully):

      Wire { from: "%surface%.browse.encoder.push"; to: "load.selected" }
    

    This is wrong…

    It should have been this:

    Wire { from: "%surface%.browse.encoder.push"; to: TriggerPropertyAdapter { path: "app.traktor.decks." + deckIdx + ".load.selected"; output: false } }
    

    I am sorry for the confusion.

    Please test if it works now.

    🦋

Back To Top