M635 J520

I haven't been able to participate too much in @truecuckoo 's excellent #jamuary2017, sadly. (Even though I have a close to a million of quirky drafts on various tapes from my OP-1. (It's amazing how it's such an idea generator that instead of finishing something it is way easier to just get a new idea and start following that instead. (I'll have to find a way around that one day. (But I digress.)))) This time I sat down in front of Cubase and started playing around with some new soft synths I haven't tested too much before -- Xpand2, SynthMaster, and the Kontakt library Solid State Symphony. I ended up with this stadium pop thing here. With @simsmi we will probably rearrange it and add some lyrics (on "Alternative Facts"!) and record a @1bisHill version one day, methinks. But, for now, since this is a weekend for finishing things, this is what it is -- a pompous cliché-ridden thing with the catchy name of "Jamuary2017 #29". Enjoy. ---- ...

The other day a friend and I experimented with connecting his excellent monotribe (with the miditribe extension) to my Cubase to see if we could record the MIDI-signals coming from it. For Science! This made me realize that, being a MIDI-noob, I hadn't understood how MIDI worked in Cubase, and none of my google searches seemed to help either, since being a MIDI-noob, I probably didn't have the right vocabulary to specify the searches with. The thing is that the 'tribe is supposed to send the synth MIDI on CH 1 and the drums on CH 10. We added two midi tracks in cubase and selected the channels we wanted in the track info. Like so: This did not work, as we got a mix of drums and synths at once all over the place. Interesting, but not right. To try to understand this we created a default project with 16 MIDI tracks, one per channel, and lo and behold all MIDI was sent to all channels. OK. We figured we needed to filter out just the channel needed per channel so we ad...