Mister_Rece
djdad wrote :
I said Traktor, the software that comes with your controller
Mister_Rece wrote :
(how to re--install traktor kontrol S2 MK2)
I said Traktor, the software that comes with your controller
never had any software for it I had brought it from a friend a couple of years back
Posté Fri 20 Sep 19 @ 5:50 pm
kradcliffe
If you've not changed anything at all and it's just stopped working then it looks like your controller is faulty.
Posté Fri 20 Sep 19 @ 6:28 pm
Nicotux
Just before to blame hardware, take a look at "Device Manager" to see whrenever windows didn't disabled the device by itself because of too many failure
Posté Fri 20 Sep 19 @ 6:53 pm
Don Moir
Your original post was not entirely clear, but I took it to mean when you updated it stopped working while it worked before the update.
If that is what we have to go on and it is the ONLY thing that changed, then of course that is the first suspect and not the frekin hardware. Something could have been changed by you or automatic but don't know that. There could be some incredible coincidence where the hardware broke some time after it was working and when you ran after doing the update, While that is unlikely anything can happen.
You have the assume the update caused the problem with what we have to go on. All the responses so far except one suggest something else.
The very first response should have been this: ( both 1 and 2 - these 2 things can generally help to isolate a problem faster than anything else - always do the simple things first )
1) fallguy menioned roll back - if this fails try next step (you did this and you still have the problem)
2) When you do an update and run again, sometimes it no longer works like is has been all along. Sometimes this is because they may have added new options for something and they have changed what you have been doing along to some new default. Flat out stupid. What other changes we don't know... So it could be the settings file has changed and why the roll back still has a problem. So save your current settings file first... It will be useful to determine the actual problem if it is the problem. Then delete your current setting file. Now try again.
If either of these don't fix the problem, then you will need to look further.
Even if something fails to connect, sometimes the program can get more more information about the failure, but that information does not typically get displayed by VDJ.
If that is what we have to go on and it is the ONLY thing that changed, then of course that is the first suspect and not the frekin hardware. Something could have been changed by you or automatic but don't know that. There could be some incredible coincidence where the hardware broke some time after it was working and when you ran after doing the update, While that is unlikely anything can happen.
You have the assume the update caused the problem with what we have to go on. All the responses so far except one suggest something else.
The very first response should have been this: ( both 1 and 2 - these 2 things can generally help to isolate a problem faster than anything else - always do the simple things first )
1) fallguy menioned roll back - if this fails try next step (you did this and you still have the problem)
2) When you do an update and run again, sometimes it no longer works like is has been all along. Sometimes this is because they may have added new options for something and they have changed what you have been doing along to some new default. Flat out stupid. What other changes we don't know... So it could be the settings file has changed and why the roll back still has a problem. So save your current settings file first... It will be useful to determine the actual problem if it is the problem. Then delete your current setting file. Now try again.
If either of these don't fix the problem, then you will need to look further.
Even if something fails to connect, sometimes the program can get more more information about the failure, but that information does not typically get displayed by VDJ.
Posté Sun 22 Sep 19 @ 12:52 am