first of all big thanks to the Ean and the DJTT crew for constantly improving the controller mapping.
However the problem described here
is still unsolved and hasn’t changed a bit with the introduction of the 3_5 mapping (including the “fixed” mapping).
I can rule out my hardware or software environment as my setup is running more than rock solid with all other applications and hardware (e.g. other midi controllers). Even a fresh install with different OSes doesn’t make a difference.
I’m really disappointed because buying the SE-controller, the new overlay and Traktor Pro adds up to a nice little amount of money. But frankly speaking: zero hours of usage for several hundred bucks?!
So I really would like to know if there will be a solution as otherwise I just end the disappointed “project” and get rid the controller and software. Thanks!
Please don’t take my mac comment as a comment like this. I am a pc user so am not being the norm mac pusher. I do however appreciate that they clearly handle midi better so thats why my suggestion was made.
I sold my last Mac 1997 and never looked back and never will.
I agree the Mac has some advantages but the disadvantages outweigh them big time. But let’s not go into philosophical discussions as we all know there never will be a mutual agreement and understanding amongst Mac and PC users.
The whole thing is supposed to be a fun thing to distract me from work and other hardships.
My PC is streamlined and as I’ve mentioned everything else (DAW apps, office apps, email etc.) is running smoothly. Even a “virgin setup” with a minimum of processes running gives me the same results. And if you take a look at my PC specs you will notice that processing power etc. is not an issue.
As I’ve stated in the original thread the “Bomes & Loopbe”-way is no solution for me. I find this totally unacceptable as I’m not a big fan of workarounds (as they just don’t solve the problem).
Yet you are asking for a workaround for a problem that is a result of your configuration (agreed, you have little control over the fact that a PC does not handle midi “flooding” very well).
As a Mac user, I feel your pain on most things that are “PC only”.
I’m sure that DJTT are working on it, but again there is only so much they can do without stripping functionality.
I’m sorry to say but you sound like a typical Mac “fanboy” to me.
your answer doesn’t help to find a solution. it’s rather the kind of feedback that is not appreciated.
and talking of “PC only”: we could discuss for the rest of the year about things that work only on a PC and not on a Mac.
Problems like this suck, but its not like DJTT has tried to hide these issues. Plus there is a work around, which unfortunately requires additional software. Moreover if you are seeing no use for the equipment without the TSI .. then I do not know what to really say. I mean seriously .. zero hours of usage?
Agreed on the argument, it is useless. Both have strengths and weaknesses.
As for the midi flood, this is what I read on the Midi Monitor when I press and release the FX Type button:
13:11:05.231 From Vestax PC-CONTROLLER Note Off 1 G4 0
13:11:06.281 From Vestax PC-CONTROLLER Note On 1 G4 127
13:11:06.281 From Vestax PC-CONTROLLER Control 1 Celeste/Detune Depth 87
13:11:06.281 From Vestax PC-CONTROLLER Control 1 Phaser Depth 64
13:11:06.281 From Vestax PC-CONTROLLER Control 1 Data Button +1 0
13:11:06.403 From Vestax PC-CONTROLLER Note Off 1 G4 0
As you can see, there are 5 commands in the same millisecond.
The Route FX looks similar, but with only 4 commands in the same millisecond:
13:14:43.414 From Vestax PC-CONTROLLER Note On 1 A#4 127
13:14:43.414 From Vestax PC-CONTROLLER Control 1 Data Button -1 105
13:14:43.414 From Vestax PC-CONTROLLER Control 1 Non-Registered Parameter LSB 64
13:14:43.414 From Vestax PC-CONTROLLER Control 1 Non-Registered Parameter MSB 0
13:14:43.545 From Vestax PC-CONTROLLER Note Off 1 A#4 0
Could you do the same and see which one is causing the jump? Theoretically there should be a discontinuity between the command times at the “bottle neck”.
I’m not “accusing” DJTT - not at all. I certainly appreciate their work and I think I have expressed that on a couple of occasions.
However it is frustrating as I can’t do anything to change the situation (whereas when my PC is broken or something like that I know how to reinstall an OS, change a hard drive etc.) and I rely on the good work of DJTT.
I bought the SE and the overlays to take advantage of the DJTT .tsi because they are the best. But with the current limitation it’s really impossible to use the controller. Hence “zero hours”. Thing is I have very little time to tweak the .tsi-file myself and had hoped to find a well thought-through .tsi from DJTT.
The timestamp shows milliseconds since device has been opened. So if I read this correct it’s more like 4ms rather. But I have no idea if this is a good or bad value.
I don’t think the 4ms it takes to go through the pattern is a problem. If you could see a 10ms jump between any of the grouped 5 notes, this would indicate a problem. But as they steam through quickly, this should not be the problem.
First rule of testing is to ask a question you know the answer to (and you prove yourself right or wrong). Here it was more of a shot in the dark as I did not know what to expect. I was thinking that if we could isolate the amount of midi messages it takes to start screwing things up, we might get somewhere. But rather it seems just that the midi and sound are fighting for processor time and this causes an interruption in the audio stream.
Does the problem go away if jack up the latency? This is also not an acceptable solution, but one that will again lead to fault isolation.
There are probably a bunch of sparkies laughing at a mechanical guy trying to figure out micro processors, but hey, I’ll learn something.
Just a spot of light humour. Didn’t mean to offend. Each to their own. 