X1MK3: Community Performance MOD (qml coding)

Stevan · February 16

https://community.native-instruments.com/discussion/comment/211248#Comment_211248

I will need to use my solution since it works on any platform and I prefer mac because of there are less driver issues simply. I just think it is looking much cleaner when all decks timers start at the same time. Not sure what others community members would prefer but at least you made something that wasn't possible to do in Traktor before. I respect that and I'm glad that I could contribute to that idea.

I asked N(.I.) for timers like this for decades and they wouldn't deliver it so I'm glad and happy that we have you around!

Sûlherokhh · February 16

I'm glad we have YOU around as well, for so many years now and still going strong. :)

I've put the NI Blinkers back in for now and pushed the custom global timers on the back burner. The super knobs with volume/filter double function are my focus next, both for the S4 and the X1. I have to wrap my head around the softtakeover, which is a limited NI module as well, so i may have to design a customized version to have it work for two parameters at the same time.

I still wonder what makes mac not like my adjustments. Does it blink on the x1 but not toggle the sequencer steps? Or the other way around?

Stevan · February 16

https://community.native-instruments.com/discussion/comment/211410#Comment_211410

Nothing happens on macOS (Sonoma, M1 MBP). Traktor behaves like the qml folder wasn't even replaced with your custom one. I really hope you manage to fix the soft takeover -that is the main reason I haven made any mappings for the X1 Mk3.

Sûlherokhh · February 16

https://community.native-instruments.com/discussion/comment/211412#Comment_211412

Now that is interesting. Too bad i don't have a mac to test myself. To be investigated….

Not sure if a custom softtakeover will fix the overmapping issue, but who knows? :)

pixel · February 16

The TIMER-Type (qml-Engine) is for the c++ in the traktor.
i don't think mac has problems with qml, it doesn't make sense to me🙃

Maybe the Mac brings a different version of qml?

 import QtQuick 2.0

maybe try a higher version?

Sûlherokhh · February 16

Beta Update (TP4.1.1 V8 Beta 3):

[Stem Controls] : In stem overlay, the 4 FX knobs now control a Superknob. Left of centre turns down volume, right of centre controls high pass filter. Includes screen feedback, soft takeover and parameter reset when loading a new stem track. Remix decks remain untouched for now.

@Stevan : I introduced a super knob parameter which, when adjusted, controls the volume/filter parameters. I left the soft takeover modules untouched for now.

X1MK3_TP4.1.1_PerformanceMod_08beta3.zip

Please test and enjoy! 🦋

oviwan · February 16

Will you guys consider moving the code to GitHub?

Sûlherokhh · February 16

https://community.native-instruments.com/discussion/comment/211507#Comment_211507

Sure. The only caveat is that i never used GitHub and have to start from scratch in 'how it works' and all that. Do you know a good tutorial for total amateurs?

oviwan · February 16

This seems like a decent explanation:

https://youtu.be/Oaj3RBIoGFc?si=OC_NcOTFoEeo0m4x

pixel · February 16

https://community.native-instruments.com/discussion/comment/211510#Comment_211510

I wouldn't publish anything on GitHub anymore. It's funny when you publish something for free and 2 weeks later you see your app in the App Store with ads or even better, you have to pay for it.
So many stupid people use this site.
In my opinion, it's a business model for many people to take the code from GitHub, quickly change the “name” and make easy money.😝

Sûlherokhh · February 16

https://community.native-instruments.com/discussion/comment/211525#Comment_211525

Is that so? Anyone else know something about this? Either way, that would be a clear violation of NI contract, right?

oviwan · February 16

I don’t see how publishing your code on a forum vs a code repository changes the fact that you are publishing the code “for free”.

I believe GitHub makes your life easier when there is more than one developer contributing to the same codebase and it encourages collaboration.

The concern of people stealing your code from GitHub can be addressed by making your repository private. This way you control who has access to your code. Buy again I don’t see how this is a concern since the code is published here “for free” anyway.

I’m not trying to push you to share the code on a certain platform, I just believe it will make collaboration easier and improve code maintenance. I know I would benefit from this because it’s easier to review incremental changes and it would encourage me to contribute.

pixel · February 16

https://community.native-instruments.com/discussion/comment/211527#Comment_211527

back when I was still in the PSP scene. i always wondered if it was allowed to use system files, i.e. to upload modified files.
Software patch is actually allowed, because the user has to get the files and changes them himself.
in purely technical terms, NI could cause problems with the mods here.
you would have to read through the license conditions

Sûlherokhh · February 16

https://community.native-instruments.com/discussion/comment/211544#Comment_211544

Which is why i always put the caveat at the bottom on page 1. So far, all i did was keep users excited about NI controllers. They are not going to shoot themselves in the foot i guess. :)

oviwan · February 16

GitHub would be for developers only. You’d probably still want to publish releases here…

X1MK3: Community Performance MOD (qml coding)

Comments

Beta Update (TP4.1.1 V8 Beta 3):

Categories