X1MK3: Community Performance MOD (qml coding)

13435363840

Comments

  • spinlud
    spinlud Member Posts: 24 Member

    That would be great 🔥

    I found that Traktor has not a consistent behaviour to number bars/beats when playback is stopped.
    For example when you are at exactly 1 bar (4 beats) from a cue point, sometimes it displays -1.4 other times -2.1. I think the correct one is -1.4 which is the value displayed when playback is active.

    To have a consistent behaviour in the controller (so that we always show the correct value regardless if playback is stopped or not) I have updated the code of the function "computeBarsBeatsFromPosition" in DeckScreen.qml which should handle position rounding errors reported by Traktor.

  • spinlud
    spinlud Member Posts: 24 Member

    Question: is it possible to have the controller starting on mixer page instead of fx page?

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod

    I'll have a look at it and compare it to my baseline (Aleix's SupremeMod beatcounter, adjust slightly by me for accuracy).

    Yes, but i won't do it for either mod. The first mod has a toggle to switch off mixer layout entirely. The second mod doesn't have the mixer layout at all. Pressing a button once or twice when setting up to go where you want the layout to go shouldn't be too much work. :)

  • spinlud
    spinlud Member Posts: 24 Member

    Ok, I just wanted to know if it is possible to do. Nice to hear that it is 🙂

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod

    Open the file '…\qml\CSI\X1MK3\X1MK3FXSection.qml'

    Close to the top is a property descriptor that stores the current layer state and what the default state (value) is. It looks like this:

    MappingPropertyDescriptor {
      id: layerProp
      path: module.propertiesPath + ".fx_section_layer"
      type: MappingPropertyDescriptor.Integer
      value: FXSectionLayer.fx_primary
      …
    }
    

    Change this part … :

    value: FXSectionLayer.fx_primary
    

    … to this:

    value: FXSectionLayer.mixer
    

    Mapping states like this (indicated by the full name of the path containing the word 'state') always reset to their default value when reloading the mapping or restarting Traktor.

  • spinlud
    spinlud Member Posts: 24 Member
  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod

    Here is an alternative approach.

    This line,

    path: module.propertiesPath + ".fx_section_layer"
    

    when resolved for 'module.propertiesPath' actually looks like this:

    path: "mapping.state.fx_section_layer"
    

    You can change the line, exchanging 'state' with 'setting', to make the mapping actually save the last used value, so that if you exit Traktor (or disconnect the controller), it will recall the last value next time you start Traktor.

    Like this:

    path: "mapping.setting.fx_section_layer"
    

    This way, you can have your controller always in the preferred state, even if your preference changes.

  • ikalejandro
    ikalejandro Member Posts: 2 Newcomer

    Hey, I've just created an account to thank you for your work on this mod.

    Also I wanted to report what I think is a bug on TP4.2.0 using the last beta of the minimal mod:
    When using 2 X1 it won't let me select other decks than A & B on both controllers (can't select C & D), so I can't use 4 decks at all.

    For reference I'm on MacOS Sequoia 15.6/Traktor Pro 4.2.0

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod

    Hold down the MODE button (for at least 1 second) to go back to setup and deck selection. This should really work, no matter which OS or TP version. I use TP4.2 with two X1's without a problem. Hope this solves it for you. Happy to hear you are using (and hopefully enjoying) the mod. :)

  • ikalejandro
    ikalejandro Member Posts: 2 Newcomer

    The issue started after upgrading to TP4.2, I've no problems with TP4.1.1

    I see the problem now, nothing seems to work in setup mode, turning the deck selection encoders do nothing, same for the buttons to select the settings, or to change the effect deck.

    Will try re-installing everything once again.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod

    The mod files have to go on top of the original files. Placing the mod files on top of other mod files will likely cause problems.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod
  • GabrieleC
    GabrieleC Member Posts: 1 Newcomer

    Is this mod compatible with Traktor Pro 4 version 4.2?

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod

    Yes. I am using it with 4.2.

    There is also a beta update which i am currently finalizing for a new version with customizable toggle for the beta features:

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 3,533 mod

    UPDATE: X1MK3 - Community Performance MOD Version 11 beta 3 TP 4.2.0 :

    New Features:

    • If deck is synced (and the global clock is tempo master), SYNC(Hold)+LoopEncoder(Turn) adjusts clock BPM.
    • Engaging Cue Monitor for one channel automatically deactivates Cue Monitor for the other three channels. This is a global effect for the software and works not just on the X1, as long as a mapping file for the X1 is loaded. A custom toggle for this behaviour is in setup (button 4 on the left side, mixer-block is pushed to SHIFT level)
    • BeatsToCue display instead of remaining time / elapsed time. Time display on SHIFT visible in the top left corner of KEY display.

    ToDo: BeatsToCue custom toggle not yet implemented. Default is a phrase length of 8 bars at the moment. Looking to make this value adjustable.

    Display format: Phrases.Bars.Beats

    An example of 64 beats before next cue point will display: "-2.8.4"

    @spinlud : Adjusted size, added phrases, adjusted for rounding error, removed unnecessary code. Have fun! :)

    @Orthomode : Minimal mod will get this when the last kinks are removed.

Back To Top