Midi assign problems with Liveslice 1.45

[bassic dave]

Hello, ive got a big problem guys!
I have a live set set up in ableton live that uses liveslice as a critical component. I had the old version of liveslice all midi mapped to my trigger finger perfectly, but the mapping in 1.45 is buggy. When i map the parameters and click "save all settings as default" and then go back to the main window the new liveslice does not remember the assignments.
To add to the madness i also deleted my old liveslice version
If I cant make this work im gonna be on stage with a spoon and a washboard, any help is much appreciated!

[R.A.W.]

i just checked this in eXT and Live6.0.7 and i can't reproduce that.
i suggest you check in the LiveSlice folder, if the liveslice.ini and liveliceeffect.ini are set to read-only for some reason.

[ohm]

just drop me an email and I'll send you the old version 'till the issue is sorted out. Also: to help debugging please be as specific as possible: what parameters are not saved? You could also try moving / renaming the liveslice.ini and livesliceeffect.ini files completely.

[bassic dave]

Wow thanks for the quick reply.
Specifically event parameter types do not map at all with midi notes, have not check midi cc's yet. I did check my midi channel and my midi device to make sure all was good. Also when i add a controller and select arrange=all and whatever track number, it does not hold the track number when i go back to the main screen. I did notice that what it does is bump the track number up by one, so if set it to control track 1 when i go back to the main screen it will be controlling track 2. When i go back to settings sure enough track 2 is there. I have compensated for this by selecting track 3 when i want to control track 4 and so on...
also midi learn is not working.
Ill try moving the .ini files later on today. Overall im very impressed with the update though, great work and many thanks!!!

[ohm]

I did find and fix a bug in the midi configuration: if you click [add controller] it's automatically defined as a "randomize" track parameter, however, you have to select the parameter (randomize) manually to actually make it work, otherwise the midi controller will not work.
Was that your bug perhaps? It only affected the random track parameter...

[ohm]

nailed the "wrong track id" bug as well. Are you sure midi learn doesn't work for you? you can see the correct channel / type / note is set right?