Pad octave/semitone not saved or recognized from 2.8.5 to 2.8.6?

I noticed today that on one project made on an earlier version of Maschine that I had some sounds assigned to pads in a group that had their root note moved up or down a few semitones and I recorded and played the pads accordingly in a pattern to create a melody.

The latest update, 2.8.6 seemed to have ignored that completely and all the pads are on the same octave again. On 2.8.5 when you played back the recorded pattern you could hear each sounds adjusted semitone, in 2.8.6 the sounds all have the same octave.

I had to go back and re-record my patterns again in 2.8.6 using the same above method and for some reason it worked. So perhaps something with the way octave/semitone changes are saved in 2.8.5 vs 2.8.6? Has anyone else run into this yet? I'm afraid to go back to other projects now and see what changed?

 

Hey kaotik78.
Sounds like a major pain. Sorry for the inconveniences. I'll raise this one with the development team and have this investigated.
Can anyone else confirm?

 

Perhaps I can try to reproduce but it depends on how you transposed those Pads, there's more than 1 way of doing it. How exactly did you change the root note?

 

I assigned some sounds to pads in a group and in keyboard that had their root note moved up or down a few semitones and I recorded and played the pads accordingly in a pattern to create a melody.

Currently on 2.8.6 a moment ago:
I started a new project, browsed for a sound, assigned it to a pad in a group, set my pattern and length, hit semitone - a few times till the pad sounded like what I was after, pressed record and pressed the pad to record a rhythmic pattern. When I went to playback what I had, the sound was adjusted according to the semitone - I had adjusted.

I've also tried a variation where I have adjusted the semitones -/+ while recording by pressing a pad while recording and also pressing the semitone -/+ buttons and when finished the playback recorded the pad hits as well as the semitone adjustment.

I then saved the example, closed Maschine down, restarted and loaded the previous project and then played it back. There was no change unlike what I had experienced in 2.8.5.

It appears to be a one off actually as when I went to reproduce it from 2.8.5 with a new track and moved it to 2.8.6 it was not evident.

I'm not sure what is saved in the *.mxprj file so perhaps something got corrupted during some point and just happened to coincide with the update?