Ronny.G

@msmcleod - I wanted to kindly ask if the project I sent has already been examined and if the bug has been confirmed. Many thanks again

Thanks Mark! sent message...

yesterday I carried out several further tests to try to identify which function is responsible for the problem (the drum map or the step sequncer?) . After these tests that unfortunately made me waste a lot of time, to me it turns out that the function responsible for the problem is the drum map. The drum map that is created using the drum map manager simply doesn't work, the assigned ports and channels are simply ignored in the case of CCs being sent. Using, for example, other tools to check the messages trasmitted it clearly shows that, when using a drum map, CC data are always sent to the "first" saved channel on the drum map even if it is not used and CC are assigned to another channel! Also ports are ignored, not only midi channels, if you have two ports that use the same midi channel (that is correct in the purpouse of create a custom drum kit from several MIDI devices, that can use the same midi channel but are on different ports) the same CC message is transmitted on both even if you want to send it to only one port! and so on...at the end of the matter the functionality is broken. If you use the step sequencer without creating a drum map, which is not very easy to do because even in this case small bugs (temporarily solvable) pop up when assigning tools and channels, the routing of CC's seems correct. As soon as you create the drum map... disaster! Of course it's practically useless to use the step sequencer (or drum grid) without a drum map but at least you can understand that the problem is in the drum map and its virtual ports. What can be done to elevate this problem as bug and so be fixed in the next release? if someone, like kindly User 905133 did, could also do some small tests in order to confirm the bug I think it could be useful in order to elevate the problem to "bug". Many thanks to all

Probably yes, I think that is the same problem. It become evident more or less in every situation where the drum map virtual ports are used and CC's assigned to different channels. Like I said before (I have edited my post later) the bug is already visible if you even have only ONE instance of a softsynth (TTS-1, Kontakt, don't matter) loaded with two instruments assigned obviously to two different MIDI channels. After the configuration of the two drum map notes (1 port / 1 synth out / 2 MIDI Channels) try to add some CC's message on one row of the drum map grid or the step sequencer and this CC message (in our example CC10:Pan) will be sent to ALL MIDI channels and so ignoring the channels assignement. The entire controllers pane function of the drum grid or step sequencer for me is unusable at this state as the drum map don't "route" correctly from the virtual ports to the the "real" ones assigned. If I have to create a separate MIDI track for each drum sound when I have to use CC's, what's the point of having this controller pane on drum grid or step sequencer? also this defeat the purpouse of the drum maps... What I find strange is that a bug evident like this (I presume it's a bug) didn't had noticed before. No one tried for example to send a different pan CC or another CC message to two different drum sound on two different midi channels using drum grid or step sequencer using the drum maps virtual ports before? very strange

Hi to all, I have a strange problem with the step sequencer, in the manual there is written: I have streamlined the "case" for a better understanding of the problem itself with only two instances of TTS-1 Synth on two different ports with the standard drumset loaded on midi channel 1 and a midi track on the project. Port 1/Channel 1 - TTS-1 Synth - 15360 Preset Rhythm - Standard Set Port 2/Channel 1 - TTS-1 Synth - 15360 Preset Rhythm - Standard Set Drum map manager (example): (56) Cowbell - channel 1 - Out port Cakewalk TTS-1 1 (50) High Tom - channel 1 - Out Port Cakewalk TTS-1 2 Step sequencer: on first row Cowbell (56) - Out port Cakewalk TTS-1 1 - channel 1 on second row High Tom (50) - Out port Cakewalk TTS-1 2 - channel 1 I create a basic sequence on the first row (cowbell) adding also using the controller pane a CC10:Pan message, however if I play the sequence the CC10:Pan from Cowbell is applied also on High Tom that is on another port and instance of the TTS-1 synth in drum map manager (even the midi share led indicate this, however they are on different ports...) UPDATE: I have tested again today (also changed CbB version) and for me the bug with step sequencer is even worse... it happens also even with only one instance of a virtual synth (I have tested with Kontakt) loaded with two different instruments, so 1 port and 2 different midi channels. Drum map configured. If I apply a controller pane message like CC10:Pan only to the first row instrument it is applied also to the second row instrument. In my case in Kontakt I can see the two instruments pan sliders that are moving together...it seems to me that the midi channel is ignored like an "Omni mode" for the control change messages. Definitely there is something that doesn't work correctly. I have done a lot of test but I still haven't understand why this happens? a bug or I have not understand something? You have seen this problem before? Many thanks to all for your help

Thank you for your help Heinz and James

Hi, I'm trying to write chords progressions directly in CbB and I found a reference about this script in the old forum...however the cakewalkproaudio Yahoo group is gone. I would like to try this CAL script that will create chords (including strumming). Someone still have this script? Many thanks to all