hey Multiman,
thanks so much for getting back. I got confused by the terminology (pressure)
I installed MIDIOX which showed me what I did wrong
HOWEVER I GOT IT WORKING - thanks to your guys help!
it just requires a weird work around:
problem:
for a 4 slice setup the set up would be in theory value0 -> slice1, value 2 -> slice 2, value 4 -> slice 3… and so forth.
this does only trigger slice 1 though for some reason and I blame the octatrack as quneo spits out the correct data as expected
solution (which would only work for 4 slices max and a sample chain not containing more than 4slices - maybe it works with 8 too - haven’t tested):
value0 -> slice1, value 18 -> slice2, value 36 -> slice3, value54 -> slice4
I always need a gap big enough between the values for the slices. (value18 triggers slice2 BUT if I had value20 ->slice 3 the OT would randomly trigger sl3 when triggering sl2. again, quneo spits out the correct data as expected
this still makes me a happy chap as it does what I intended and quneo in general is awesome and it is for me a huge leap as I now can trigger multiple tracks/slices at the same time . I guess the max number of slices is reduced to 8 though (due to the needed value gaps - which I couldn’t be arsed testing yet… however with quneo some sort of performance mode for the OT is possible and I’m working on a template (tedious!)
I made sure quneo only sends CC+value, note on, note off, (and for some reason another CC+0 - I couldn’t get rid of that one…and latch and return value doesn’t work as expected)
ELEKTRON: please make this work with midi notes or make the OT respond to CC better so we wouldn’t need to custom tailor sample chains short in order to make this working
again - thanks so much for your help!