In my last email to them i pointed out 2 things that i needed addressing:
a. Using a PSU does not cure the problem . Please disregard this as relevant advice.
b. Disabling Midi Out does work but could i have a reason why this works and whether this is to be / can be fixed.
I havent had an answer yet.
I will forward your Ticket and keep on at them.
I can see where the are coming from with the thing about the USB post not supplying enough power , that could be cured by a PSU but i dont know why disabling Midi Out solves this. Maybe someone can enlighten me (i bet nem0nic knows). But i dont know why this only affects Traktor after the Hot Plugging update ?
Can we say for certain that using a PSU does not solve this 100% ?
I know its going round in circles but i need to know.
It would be nice to be able to have visual feedback on my controller like I used to on all previous versions of Traktor, yeah.
I don’t see how it can be related to what they’re saying because this was never an issue before something changed in 1.1 (I think, it’s difficult to work out because there isn’t a proper changelog for the app). People have bought power adaptors are still able to reproduce the error. The last two pages in the Technical issues forum has more clues than support have generated as yet, check it:
I gave up on it for a bit tbh, but I figured that as the product was in a development phase now would be the time to start up again. It’s obviously a problem for a significant number of users with VCIs, time to get fix up.
I really appreciate your help on this issue K. We’ll get to the bottom of it.
until now we could not reproduce this freeze in combination with the VCI100. I
would recommend to give the external power supply a try.
Best!
Frank, Native Instruments Support Team[/quote]
After pointing out to him that people who had bought power supplies still had the same problem when the app was put under stress, he came back with this suggestion.
If there was another app that did what I wanted it to I would have jumped ship by now.
Please Karlos, use all the powers at your disposal.
As i pointed out in a PM to Jack, I was also able to crash TPro fairly regularly (always less than a couple of minutes of playing) with 4 decks and a dedicated beat phase monitor on a button for each deck while playing with the jog or even the crossfader. I still think though this is too much of a complicated setup to submit a ticket for (leaves to much room for uncertainties) and I didn’t have a chance yet to check if my power supply or Midi-Out off change anything.
What I read in another forum is from a user that had a VCI100 and switched to a Xone1d and claims that since then, the problem has vanished. I’m not sure about the credibility of this info though since it might just have less MIDI traffic… So please PLEASE put this in the “rumour” bin but not anywhere else…
If they gave out advice saying ‘Don’t do this, it makes Traktor crash’ then I would say fair enough, don’t log a call. But they don’t. Maybe with your input (and your German language skills )we might be able to get somewhere with this.
Hijacking the thread here for a bit…
My conclusions so far is:
-The problem is NOT an 1.1 update bug. (I had enabled some LED’s to flash on beat at the same time as the 1.1 update was released - this was the problem)
-The problem is due to the fact that to many midi-out messages is flooding the usb-whatever(buffer?).
-Disabling MIDI-out solves the problem (but how fun is that?).
After pulling my hair enough times I decided to try to provoke the “freeze” by flooding the VCI with MIDI-out messages by toggeling a lot of leds using the jog wheels… this gave me an insta-freeze… BUT… when I tried the exact same thing with my budget-backup-cheap-controller (dj-tech iMix)… it won’t cause a freeze… sure the sound will slow down to a point where it almost souns like the freezing sound, but as soon as I stop punishing the controller everything goes back to normal.
My conclusion is that this is VCI related. (To avoid it, just don’t use that many LED toggeling buttons/functions or at least not at the same time)
IF that’s the case, it would be really cool if you can put that flooder in a package that can be sent to Vestax, a) for confirmation b) since the 1.4 is in the works…
Thanks Autonic that adds another dimension to all this. However i still want to hear if NI have made any progress.
Ill put what you have said to them and see if it can be tested. Have you already mentioned that to NI ?
It does help explain why disabling Midi out is working for some people.
It only ever started being an issue for me with the 1.1 update, and I didn’t make any major changes to my tsi when it was released. You sure it’s coincidence?
I can’t be certain that update 1.1 DID NOT cause this problem… but I can be certain that the MIDI-out overflow error only occurs when using the VCI and not my other controller.
To provoke the crash I’ve set it up like this:
I’ve mapped an “Effect Unit 1” toggler that is activated by my jog wheel - which means that setting the jog wheel into spin causes it to disable/enable the “Effect Unit 1” on the mixer extremley fast (switching on and off multiple times per second).
Then I set about 10 LED’s to be activated when the “Effect Unit 1” is in state ON and spin the jog. The LED’s starts flashing intensly for about half a second and then the “freezing problem” occurs and traktor stops responding (until I unplug any USB device or reboot).
When I preform EXACTLY the same thing with my DJ-tech iMix (low budget backup controller) traktor seems to be slowing down (as if you were to pitch a song down to 1% of original speed) as long as I keep spinning the jog wheel. As soon as I release it everything speeds up again and no freezing occurs.
If this were the fault of the 1.1 Update then my logic tells me that it should affect any MIDI-device the same way - which it clearly doesn’t.
If anyone would be interested in stress-testing their controller of a different brand with MIDI-output madness it would be great.
Hey guys, got some good news from NI today. They’ve been liasing with Vestax regarding this issue (at last!), and I’ve been asked to do an export of my system info. Looks like they’re taking this seriously now.
Thanks again to Karlos and anyone else who’s been busy behind the scenes.
I just wondered if using any MIDI tool (not Traktor) feeding the VCI was used, just to make sure on which side the problem is. Of course I can map the lights in Traktor and already with beat phases, you get crashes fairly quickly.
Definately good news that the big guys are talking to each other! That should get NI the right device (if they don’t have it already) so it’s just a matter of giving them a TSI that maxes out on the LEDs…
I thought about doing that with last weekend but ran out of time before I had it working the way I wanted it to. In any case, Kudos to Karlos () for pushing on this so much!
Any word about Traktor Freeze (while using VCI-100) from NI?
I had some major freezing going on this weekend as a result of a new mapping which included much more LED action than I normally use.
Also (in this particular post) I noticed folks not mentioning the Traktor VCI-100 “Hang” on startup screen issue. Surely this is also bundled with the midi problems the VCI seems to suffer from with Traktor.
Personally I am convinced this has nothing to do with TPRO updates. This issue has been affecting me since Traktor implemented “Plug & Play”, which happened somewhere in the T3.4 era.
I have found the solution for the “hang on startup screen” issue (simply not turning on the VCI prior to starting Traktor), but I thought I would mention it since I believe it is in the same ballpark as the gereral midi issues the VCI-100 and Traktor are having with each other.
I really would like to not suffer from this issue…any word…anyone?
Which version of Pro are you on. I know for a fact that there has been a ton of work done (in conjunction with Vestax) to make v1.2 work with the VCI on these issues.
Are you taking part in the Public Beta Testing of v1.2 ?
Yes just downloaded the Beta tonight..and Ive been using TPro at home only with all the most up to date versions since day 1, just so I can keep track of the changes and be familiar with all the new features and setup. But IMO TPro has been a Beta Test all along…lol
In the state Traktor Pro is (and has been since day 1) I have no intent on using in a live situation…not yet at least. Not so much for stability issues cause I believe its stable…but for all the new features it has, we have to compromise all this other small stuff that was working flawlessly in T3.
Im not against the changes…just wish it wasnt at the cost of bla bla bla
Guess im getting off topic here.
Im saying that yes I have 1.2 beta and I will continue to test it with the VCI for deck freezing issues, however im using T3.4 to DJ live and was hoping for NI to give official word about what the acual issue is, and perhaps an answer as to how to deal with it within T3.4
hey guys…
i am just getting started…and same sh** with audio kontrol 1 and vestax 100
sooo i used your advice
disabled midi in and out but only for die kontrol1, dont really need this kontrol buttons anyway… and it works fine without this freeze
before i had ALWAYS a freeze on pushing the loop button
so it´s maybe this releationship between kontrol midi buttons and vestax buttons
and if i need buttons my keyboard and oxygen do the job
)we might be able to get somewhere with this.