huge bug:traktors 12 activation switches dont work

as example load "reverse grain" and press "on" on the modul.
then save the preset and load it again.
after loading, the switch is off.

this is a bug and makes the traktors 12 effects really unusable.
this bug is since years and I mentioned it several times.
because it is a huge bug but no big programming it should be fixed very fast not within years.

 

here you can see the switches which are buggy:

 

please someone can test this and can CONFIRM this?? I really cant understand that there is NO reaction since years about that neither from the developers nor from other users!

 

Are only those 5 switches you pointed red not saving state in the preset, or all of them?

I will try and replicate this - I cannot find this bug in the bug tracker, so in case of it happening over here too, I will enter it in the database then.

 

Sort of a guess here...
Could it be that these are designed this way? Those buttons, on those particular effects, are all something of a "start taking the sample now" button. I mean, you certainly could just turn in on an leave it on but these sample and loop type effects aren't typically used that way. I am not saying it shouldn't be able to save the states of those switches just that maybe the design didn't see it being turned on and left on but more likely automated at specific points.

Anyway, the effects are far from useless due to this. As a simple workaround, in your project, simply automate the position of the switch at the beginning of the project. EASY! Of course, if you are doing something real time, like just playing or DJ'ing, then you will have to click them on but I still think "useless" is quite an exaggeration.

HTH
J.L.

 

If I step through presets with many traktors 12 effects and want to test these, I dont want to turn on each of them first...

The same in a live situation with ableton.

And automation is also not possible. Just save and restart and the automation is not working.

@evildragon: just the pointed switches.

And please enter also the container knob bug explained in the other thread.

 

Hmmm... The automation works here. I am using Cubase, though.

 

please save and restart the project first, then try it again, automation works no more!

 

I saved the project and reloaded it. Then, also saved the project, exited Cubase and restarted then reloaded the project. I just now reloaded that test project from the other day and it is still working.
Could be a difference between Cubase and Ableton, but the automation works here...

 

I must correct: Here it works too now! But If I use the container plugin to automate many switches and rename the container device switch, first it is displayed on the automation track header, but after saving and restarting it has its default name in the host but the new name is still in guitare rig.

Ok, automation is working, but if you use the standalone version and you want to switch through presets in a live situation or if you want to test presets with traktors 12 devices, they are all off. this is no advantage, you can argue what you want, it is a bug.

 

It's not a bug if it's by design... But that's yet to be confirmed by NI (if it's by design). I can reproduce this and I entered it in the tracker. Let's see what happens.

 

thank you evil dragon!

could you reproduce the other issue with the container controler automation too? Here the little instruction how to reproduce:
1.rename a container controler
2.automate it in your host
3.save and re-open your project with the container controler automation
4.and voila, the automation name is turned to default!

By the way,name changes, which were made after generating the automation in the host are also not taken over.

 

I think that's up to the DAW to handle...

 

Yes, but as example if I use the macro knobs of Massive, the name is displayed right in the automation header after saving and restarting. So the principal function of the DAW is working. It is a Guitare Rig Bug, because there it is not working after restart.

 

Got a reply about buttons not saving in presets - that behaviour is intended by design, so it's not a bug and won't be fixed.

 

and why it is working at first and then not after saving and restarting the host? I do not understand how this cannot be a bug...

"by design" is like as example: "not possible to have more finer steps because the automation system is working in the MIDI standard" ---> this is no bug, this is "by design"

but if something is not working as expected, this cannot be "by design". there is always a bug fix possible because it must be a bug.

 

"By design" here means it works exactly as NI intended it to work. It won't be changed.

 

Hello EvilDragon, I contacted Native Instruments and this bug is in the bug tracker and will be fixed. Also the container knob bug, where the name is not displayed after restart.

And no it is not by design, it is absolutly not logic... Because if you make presets with many traktors 12 effects as example and save them, after reloading, all the switches are off and you must turn them on before working with them! This is no nice behaviour for live situations if you want to switch a preset! So REALLY NOT by design, my friend