Serato DJ Pro General Discussion
Midi mapping issue with rotaries encoders
Talk about Serato DJ Pro, expansion packs and supported hardware
Midi mapping issue with rotaries encoders
dj_spark
3:13 PM - 14 August, 2015
Hello,
I have a weird bug with Serato DJ and my Pioneer DJM T1
Behavior :
The items 'Loop Size' 'Library Scroll' 'beats' are mapped to rotaries encoders with a data type nammed 'relative - 2's complement'.
Issue :
But from time to time this setup will skip and get the data type back to 'absolute' which would make them act strangely.
Action :
So I need to edit the mapping and change again the data type of these items.
Note :
- it breaks in any layer or combo using these encoders
- if I'm locking the XML files into read-only mode this doesn't happen
Guess :
The software is rewriting part of the midi xml code of the user preset but I still don't know what will toggle that. And yes I'm always using the latest version and had this issue since I own this mixer.
It's interesting to see that since the 1.7.5 it only happens randomly.
On 1.7.4 (or older) it would be trigged each time I was launching the software.
Regards.
I have a weird bug with Serato DJ and my Pioneer DJM T1
Behavior :
The items 'Loop Size' 'Library Scroll' 'beats' are mapped to rotaries encoders with a data type nammed 'relative - 2's complement'.
Issue :
But from time to time this setup will skip and get the data type back to 'absolute' which would make them act strangely.
Action :
So I need to edit the mapping and change again the data type of these items.
Note :
- it breaks in any layer or combo using these encoders
- if I'm locking the XML files into read-only mode this doesn't happen
Guess :
The software is rewriting part of the midi xml code of the user preset but I still don't know what will toggle that. And yes I'm always using the latest version and had this issue since I own this mixer.
It's interesting to see that since the 1.7.5 it only happens randomly.
On 1.7.4 (or older) it would be trigged each time I was launching the software.
Regards.
dj_spark
4:36 PM - 26 August, 2015
I still have issue even when I'm locking my midi files into read-only mode.
There is always an auto-save file that is created an which is resetting my rotaries encoder and is over riding my created files.
I simply have deleted the latest auto-save that was created to see if it will get back. My xml midi files are still locked.
There is always an auto-save file that is created an which is resetting my rotaries encoder and is over riding my created files.
I simply have deleted the latest auto-save that was created to see if it will get back. My xml midi files are still locked.
&Midge
7:38 AM - 27 August, 2015
This is a very frustrating bug!
One that I've reported and spent hours working with the Serato team on in the public betas and support tickets. They are aware of this issue and I hope they will fix it soon.
Guys, when will this be fixed? please!
One that I've reported and spent hours working with the Serato team on in the public betas and support tickets. They are aware of this issue and I hope they will fix it soon.
Guys, when will this be fixed? please!
dj_spark
3:45 PM - 28 March, 2016
Did it get fixed into 1.8 and above ?
I'm asking because I can't run these for now (IGP issues).
I'm asking because I can't run these for now (IGP issues).
To participate in this forum discussion please log in to your Serato account.