BR - LiveSlice 1.22 in SONAR 4 using DirectiXer

[JamminFool]

hi,
noob here re:LiveSlice so forgive me for not having the right lingo, etc.

there is a problem with the new 1.22 version when using it in SONAR (version 4.04) with DirectiXer adaptor.

i'm not even sure exactly how to describe it other than to start with it didn't do it in the previous 1.20 version,

specifically, when a loop in loaded and the transport in SONAR is started, the track in the arranger suddenly shows an altered view of the slices (either extremely zoomed or unzoomed or ?) and the track plays at a very low pitch when triggered the midi controller or the SONAR sequencer track.

note that prior to running the SONAR transport, the track in the arranger in LiveSlice played correctly.
but as soon as you run the SONAR transport, the above "pitch shift" occurs. i haven't been able to tell exactly what is happening, as i am not familiar enough with the details of LiveSlice yet to be able to track it down.

but i know it's a problem since this does not occur in the LiveSlice 1.20 release.

let me know if there is anything i can further test or check to help track this down.

[R.A.W.]

go to liveslice's settings page, there are some default mappings, e.g. note D3 on midi-channel 1 setting random pitch, CC 1 on channel 1 setting the pitch.
most likely you got midi-messages going to liveslice which alter the pitch, and when pitching down, the wav-data becomes "stretched" to represent the pitch.

[JamminFool]

go to liveslice's settings page, there are some default mappings, e.g. note D3 on midi-channel 1 setting random pitch, CC 1 on channel 1 setting the pitch.
most likely you got midi-messages going to liveslice which alter the pitch, and when pitching down, the wav-data becomes "stretched" to represent the pitch.

i'll check it of course, but note that this does not occur under the exact same circumstances when using 1.20.

in other words, the only variable is the new version of liveslice.

[R.A.W.]

did you delete the *.ini when replacing the old version?
if you did that perhaps could explain this cause that activates the default-settings, while perhaps you removed the mappings in the previous version.
i already answered a similar post in the instruments section here at kvr and it was exactly the midi-stuff that did the pitching, so i'm very confident that this is the same here and not a bug in liveslice.

[JamminFool]

go to liveslice's settings page, there are some default mappings, e.g. note D3 on midi-channel 1 setting random pitch, CC 1 on channel 1 setting the pitch.
most likely you got midi-messages going to liveslice which alter the pitch, and when pitching down, the wav-data becomes "stretched" to represent the pitch.

ok. some more info.

you were right about the settings. when i removed the default "CC 1 on channel 1 setting the pitch" assignment, the problem went away in version 1.22.

this implies two things:
1) that the SONAR transport is sending CC 1 info on channel 1
2) that the bug was not in version 1.22 but rather in version 1.20 (by NOT responding to this assigment).

ok. i just tested this and indeed the bug was actually in version 1.20 NOT responding to this assignment. it is actually FIXED in 1.22.

so i will need to change the default assignment for use in SONAR.

anyway, thanks for the heads-up on this setting. just learned something!

i will need to do some more testing regarding whether sending CC1 is intended behaviour by SONAR or whether it is somehow related to DirectiXer (i'm guessing it's by design).

[R.A.W.]

glad that it worked out.. and a good info for other users with SONAR.

[ohm]

I just downloaded the sonar 4 demo to check this out.
I loaded midi monitor, added a midi part, started playback and received: 1 pitch bend value 0, 1 modwheel value zero and one CC#64 value 0. Does this every time playback starts apparently - I fail to see the benefits of this, but that's beside the point.

I will make a note about this in the manual. I should probably remove the default mapping of the mod-wheel too, to prevent this surprise from happening. I heard from a Project5 user that it sends out modwheel value 64 when playback starts... why can't they leave the modwheel to the left hand of the user, that's what it's for isn't it?

well, important thing is that it works

[JamminFool]

I just downloaded the sonar 4 demo to check this out.
I loaded midi monitor, added a midi part, started playback and received: 1 pitch bend value 0, 1 modwheel value zero and one CC#64 value 0. Does this every time playback starts apparently - I fail to see the benefits of this, but that's beside the point.

thanks for verifying.

I will make a note about this in the manual. I should probably remove the default mapping of the mod-wheel too, to prevent this surprise from happening.

both good ideas.

why can't they leave the modwheel to the left hand of the user, that's what it's for isn't it ...

totally agree!

well, important thing is that it works

thanks for the sanity-check.