S4MK3 & S3: Community Performance MOD (qml coding)
Comments
-
Today I have to confess that I don't have the time or inclination.😛
tomorrow I'm celebrating my birthday and then I need 2-3 days to recover🤣 and then I can change that for you0 -
- I just started changing stuff in the files and looked what happened. I have got no other tips, except look at the code other people have produced and talk about it, preferentially with the original coder. I did this with Joe and Joe's screen mod as well as Aleix when modifying Aleix's Supreme Edition. I can recommend that mod in particular as a useful guide for doing very good and mod-frindly code. Very readable, clean, professional. Unlike my own creations (which are not always so clean and readable). I'm sure there are better methods, but that's mine.
- I am still refining the stem controls for the X1 mod, once that is finalized i plan on adding an StemControl- override to the FX knobs and buttons at the top of the S4 when in padsmode.stems, including softtakeover and superknob functions. I am sure this can be adapted to the mixer controls of the S3 mod.
For brightness to be OFF, you have use '!remix_muted_1.value' as a condition that enables the wire for the LED output only, not for the button toggle controlling the mute function, effectively splitting the input and output function into two separate wires.
Print the piece of code you have been modifying so far and i'll show you how, if you have trouble with this.
0 -
haven't had this specific issue but the advice is welcome, seems like the GUI is chugging when you have layered UI elements going and the S8 screens tries to read the gui as well. tho i'm not really sure why because this happens on the regular PC screen, the S8 screens are fluid.
i haven't had any crashes or chugging since then, it was a one-day thing apparently. my other soft-issues are more related to the custom mod im using but nothing gamebreaking :)
maybe reinstalling T3.4 with @Sau's mod alongside T4; might have something to do with it being more stable maybe, who knows ? :)0 -
i can see why you'd be annoyed yeah, especially if you hand-tag all your files yourself for peak organisation.
i would like to offer my perspective :
i stream all my music files (10K+) over the network hosted on a NAS, on multiple computers (laptop, desktops, NUCs) running different versions of Traktor. (depends if im at home or on a gig..)
Saving tags to files is a lifesaver for me because it saves me hours of re-analysing the files and rebuilding a collection. i don't even have to transfer said files to my pc, a single gigabit cable is enough for 2 decks of FLACs files and lots of bandwith to spare :)
I could probably also remote stream on a VPN tunnel via my phone LTE in a pinch, not having to worry about having my desktop up and running while gigging in the bushes. just some food for thoughts i wanted to share :)
nowadays i do backup my collection, but having tags on file managed from traktor was a godsend for me for about 10 years, i still have the original import date of every track in there since 2012 :)-1 -
The next Traktor update seems to involve a browser upgrade. The repeated need for the browser to recalculate the playlist sequence when sorted by anything other than # (or in any 'search' menu) is interrupting vital audio processes and should be, in my opinion, the most important thing to tackle. Let's all hope that this is what is being done right now…
0 -
@FloydianSound : I don't know what you're trying to tell me.
I don't really care what other people do with their files.
Or whether they use a server program.
I was able to undo the changes Traktor made to my files.
I honestly don't care what Traktor settings you prefer, it doesn't get me anywhere and that's not what I'm here for.in the future i'll keep my concerns to myself before i get bombarded like this again
0 -
WiP.
Remix Deck and Stem focus up next. Plan is to implement a Sttem/Remix overlay for the FX controls at the top.
I was thinking…
There are two separate ways to easily map buttons to Remix Slots/Cells. There is the S4Mk2/X1 way, with LOAD/PLAY/MUTE (for loops) and LOAD/PLAY/REARM (for one-shots) plus the SHIFT layer STOP/DELETE and the S4Mk3/F1 method, with the TRIGGER/RETRIGGER function (and a separate CAPTURE/DELETE 'modifier').
There where some requests from S4Mk3 users to re-implement the S4Mk2 method, but i've heard from other users unhappy with the X1Mk3 method, that they would like the F1/S4Mk3 method on their X1. What i am saying is that both method can work on both devices.
I would like some feedback on what users prefer. Exchanging one with the other method is quite a bit of work. Ideally, an easy way to capture loops is going to be a part of any solution.
This is a simplified explanation and there are, apart from a few more modules related to step sequencing, also all the basic commands to build a custom module.
I let this stand here for a week or two before starting work, so we can have a discussion.
What are your thoughts?
1 -
I don't quite understand your idea.😊
Can you explain it for someone who doesn't know s4 and f1?Which knobs and buttons do you want to use?
I'll have to take a closer look at the devices on YouTube😁
0 -
Have a look at the S4Mk2 manual and the S4Mk3 manual in the Remix Deck chapters to see the different workflows.
I've observed it as well, with several screens running. It's the reason i seldom use more than two D2's at the same time. And the option to turn the screens off (in the Performance Mod) was also born from those processing problems.
0 -
@pixel
I performed with your latest mod 2 days ago, I can report that stem mutes are not immediate. They have a small latency and after some point I had to mute them just a bit before the first beat of the bar in order to be precise. Is that caused by the hold option of those same pads? Is there any way to make it more responsive like it was before?0 -
The pads are equipped with a tap-and-hold option. The tap is triggered when the pads are briefly pressed and released again.
If the pads are hold pad and the encoder is turned, the values are changed.
If you don't like this, you can simply copy the standard S3 files back again.
but I don't think it's any different with the standard files0 -
I am not saying i am liking or disliking any of the options, but some users had preferences that i wanted to hear.
These are the NI modules and their functions. The first two are used by S4Mk3 and S3, The third one is used by the S4Mk2 and the X1 (adaptive primary (secondary) is the triple functions for the pads (secondary is with SHIFT).
The fourth is used by D2/S8, as well as the fifth, which is also used by S4Mk3 and S3.
RemixTrigger { name: "triggering"; channel: deckIdx; target: RemixTrigger.StepSequencer } triggering.1.capture triggering.1.trigger triggering.1.stop triggering.1.selected_cell RemixMixing { name: "mixing"; channel: deckIdx } mixing.1.mute mixing.1.volume mixing.1.filter RemixDeckSlots { name: "remix_slots"; channel: deckIdx } remix_slots.1.adaptive_primary remix_slots.1.adaptive_secondary remix_slots.1.volume remix_slots.1.compensate_gain remix_slots.1.fx_send remix_slots.1.fx_send_on remix_slots.1.filter remix_slots.1.filter_on remix_slots.1.pitch remix_slots.1.key_lock RemixDeck { name: "remix"; channel: 1; size: RemixDeck.Small } remix.1_1.primary remix.1_1.secondary remix.1_1 ---> LED remix.capture_mode.input remix.page remix.capture_source RemixDeckStepSequencer { name: "remix_sequencer"; channel: 1; size: RemixDeck.Small } remix_sequencer.1_1.steps remix_sequencer.1_1 ---> LED remix.sequencer.swing remix_sequencer.clear_selected_slot remix_sequencer.selected_slot_pattern_length remix_sequencer.all_slots_pattern_length0 -
i think the user meant the stem deck. there the pads have a dual function tap and hold butten, which is normal that the button only triggers when you release it, otherwise the hold can't work and that causes a short delay. my tip is to simply press the pads faster.
this is also the case with many standard functions of the S3, but this is normal. you could of course also set a variable true when you press a certain button, and a condition that if the variable is true, so and the hold function of the pads is deactivated and the tap is triggered immediately when you press it.
but i thought that would be annoying if you have to press so often0 -
I think it was about the delay after releasing the button. Maybe shorten the timer to 150ms or so. It was the same with the load button, so i shortened it from 1000ms to i think 250ms.
1 -
There is no delay, the button only sends when you release the button, that's normal, otherwise if I use the hold option the tap option will also be triggered.😆
1
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 65 NI News
- 807 Tech Talks
- 4.2K Native Access
- 16.9K Komplete
- 2.1K Komplete General
- 4.4K Komplete Kontrol
- 5.9K Kontakt
- 1.6K Reaktor
- 386 Battery 4
- 859 Guitar Rig & FX
- 438 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.9K Maschine
- 7.5K Traktor
- 7.5K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators