Seems pretty simple to implement considering it is part of midi (cc 66 and 67). What I want moreso is for bitwig to process midi better or not at all, i.e. passing the midi stream directly to plugins, which it doesn’t seem to do. Please correct me if I’m mistaken
Hi @Ben1, welcome to Bitwish. I see you also have posted on https://www.reddit.com/r/Bitwig/comments/116kw4z/sostenuto_and_soft_pedal_in_bitwig/
Did you add the piano as a controller on Bitwig? Are you receiving MIDI notes when you play the keys? If you do, unless I’m missing something, CC messages shouldn’t be any different, regardless of the number.
Screenshots welcome. 
Thanks for the welcome, yes that’d be me though I tend to avoid reddit lol, this seems like a nice community! (I have chuckled already at the contention in a very interesting thread about parallel processing)
I should have said, the piano notes and sustain pedal are working fine, and the sostenuto and una corda are working in kontakt as a standalone but not as a vst in bitwig or studio one, definitely seems like a problem on my end but where the problem lies is where I’m lost. So as for bitwig I’m sure now it’s not their midi implementation and this thread is pointless but I’ll update if I find anything, lots of dead threads around the internet regarding sostenuto but no one ever seems to find answers
Cheers
1 Like
update: It does seem to be bitwig, or a least bitwig and my controller, I’ve found that in the controller tab in settings I can set a cc to the sostenuto and soft (but not sustain) pedals by midi-learning the pedal, so they are recognized, however in the main on a track I can for example add the midi module (blue icon like note effects or whatever) and set the sustain pedal to be a parameter and that is recognized fine but the other two aren’t. So it seems bitwig selectively recognizes the pedals in different contexts, which is troubling as I can’t see why it would do that, also almost as if by magic the pedals all work fine in studio one now… (sigh emoji)[why isn’t there a sigh emoji]
Will do a video to demonstrate in a bit
edit: Here is the video
Also I can confirm that with a midi monitor vst the two pedals are not being received, sustain is, so like I said in the original post bitwig seems to not be passing direct midi data. Since this seems to be specific to me I can’t say it’s a bug but it’s definitely an occurence
edit: finally got it, seems to be a bug with the generic controller script, switched to “keyboard + 8 device nobs” and that fixed it. Still seems to be a bug rather than user error though, as you’d expect a generic controller to work with generic midi CCs
Have you contacted Bitwig’s support? I’m afraid I can’t help you further, it goes above my skills.
Hi @Ben1 - I just joined here and found your post because I was looking for “cc64”. Did you contact Bitwig about your issues in the end? I’m curious because personally I have recently been frustrated with the way cc64 works. I know you commented that cc64 works OK as a real time controller, but what I was trying to do was record a piano performance and export it as MIDI. The cc64 was missing from the export. It wasn’t long before I realised that Bitwig treats cc64 as separate from the note information. In my view this is flat out wrong. Pedal events are exactly as important as notes and should be moved around with the clip and exported when MIDI is exported. Other DAWs do this correctly (I was a long time Cubase user before migrating).
I’m planning to add this to the wish list, assuming they haven’t fixed it in the new v5! I’m trying to find out whether they have before I post.
I think it’s pretty weird that pedal events are separated out from the notes. Perhaps there are some situations where you’d want that, but at the very least I’d like it to be a switchable option in that case. I’ll be honest, I hadn’t considered the other pedals, so thanks for the reminder!
1 Like