Nice to see you switching to Bitwig! You are the type of power-user that can bring the devs a lot of meaningful feedback especially for the live playing aspect.
So much really good information packed in here! Really appreciate the quality and depth of your tutorial videos, just as much as the quality and depth of your music! You are a positive force in the world and a blessing to the music community!
I was using Cubase Pro (up to v12) on Windows before, but this channel and Martins music made me buy the full Version of Bitwig and switching entirely over to Linux. A whole new life, thanks to Martin. :)
Hi Martin, glad to see you switched up to Bitwig. It does not make me regret to let go Ableton. I still miss the live midi capture, though.... but the rest is wonderful and the grid... oh wow.
I noticed the Bitwig MIDI Program Change device also has a modulation icon. Would it be possible to 'misuse' that? I see there are also some note modulators so maybe it would be possible to convert specific notes (or expression values) to 'modulation' into specific program changess? Afaik the Send Now can not be automated/modulated but maybe with Auto Send active you can still get the MIDI data out at the intended moment. The Note Grid can do all sorts of crazy stuff but afaik there is no grid module for program changes. But i imagine you could program very specific note/expression values which possibly can be used to modulate the program changes as descibed. Polarity appears to be quite creative with the Grids, maybe drop him a line. I do agree, this is a bit of an omission in Bitwig, MIDI is indeed fundamental to electronic instruments. Why support CV and not MIDI essentials like inserting MIDI events (hexadecimal code blocks for my part) into a note (or even audio) sequence?
55:03 Possible workaround (can't test, don't have synths that react to program changes) would be to also automate the "Auto Send" macro, where you enable it at the start of the clip and deactivate it before its end. I believe this only makes auto sending active when you trigger the clip, and *should* deactivate it before the clip stops, therefore not sending the program change message. It's a hack, but it might work. I'm guessing Bitwig's excuse for the behavior is that automation clips have an initial value that all parameters reset to when the lane is inactive? I have noticed that this is what happens with knobs as well when I use automation.
I had the same idea. But with that workaround the program change message would be sent every time the clip starts. When I changed the parameter of the sound on the synthesizer, it would reset to the saved state then. A bird told me, that there will be an update regarding the program change issue soon.
Hey Matin - Have you thought about the Circuit Tracks? It can double as a pad and knob midi controller with four tracks of midi and It has basically 32 knbs (32 separate #cc numbers - (4 lanes of 8 knobs each) that can quickly be set up across all your instruments,efx, etc. And the pads are additional control like the launchpad pro3.
Not necessarily, it doesnt have to be used as a groovebox.Many also use it as a midi controller and hardware sequencer. I like it better than the the launchpad because its a more compact and ulitarian design and the extra knobs are great but, ya, it wouldn't work for your bitwig for launching loops, patters, etc.. I use it with my Maschine MK3 which launches all my clips/patterns/loops@@MartinStuertzer
Wonderful tutorial. Bitwig should give you the tools you need to switch between the patches and effects easily. I hope they are watching and provide a solution. May I add that I want the option whenever Bitwig has an update, that the previous version is overwritten. I know their argument that they want the previous version as a backup for live performance, but I don't live perform. So, give us the option to have just one Bitwig version installed. Back to the video: I learned so much again. Thanks for sharing.
Like I mentioned in our discussion yesterday: it is very complicated. :) I wish developers gave that problem more attention. Such a simple thing as switching patches should be easier.
I told Bitwig the midi program change doesnt work and their support says they have no other complaints about this jsut recently in fact. I have emails to prove it all. It doesnt work for me either while FL studios midi program change does. So it cant be my hardware. Glad to hear you say it too. I know what the difference may be. Bitwig sends the 3 program changes simultaneously instead of each part one at a time. (Program, MSB, LSB). I even discussed with Yamaha who invented midi and said the problem must be Bitwig.
I had a similar experience when I talked to them in Berlin on Superbooth. It is sad, that Midi has no priority in their team. Also, they are very confident, that their way to handle program change messages is good. But at least I have found a workaround.
What script did you use for the midi fighter twister when you were using Ableton still? I remember you used it similarly but I'm not seeing a twister sister version for Ableton. Thanks for the streams!
@@MartinStuertzer Thanks for replying! Good to know. During one of your ableton performance walkthroughs it seemed that you had the Midi Fighter set up in similar fashion of having one knob scroll through track and another for scrolling through the effects. Was I mistaken, and if not, how would I go about that setting it up? Appreciate you!
Regarding the question about Native Support of the Midi Fighter Twister at ru-vid.comcgdTDZ89X4E?si=o0J9ljrAghmnH2m-&t=1662 on my Bitwig Essentials there wasn't. The DJ Tech Tools appeared only after I installed the Twister Sister script (which works great but takes a little while to install and a little Googling will be required on things like how to define a "PATH" in Windows). Thanks for showing this script Martin.