Open mrglennjones opened 3 months ago
@mrglennjones Hey Glenn, thanks for the reminder. I implemented this morning but haven't got a chance to test. Let me know if it works for you if you get a chance. There should be new events for program change under the category MIDI port n
.
Also, you might want to delete dust/data/dreamsequence_dev/prefs.data
in Maiden as some things have changed in an update I pushed yesterday.
@dstroud hero! I'll get back to you
@dstroud hi mate, just tested this and the program change functions perfectly, only now its introduced a slight delay at the beginning of the in the loop.
This could of course be the jv1010 itself causing this.
Perhaps in addition to this looping event function, global program changes could be set at start up somehow, on preset load perhaps? (not looping)
All the best 👍
I forgot to also ask about Bank Select? Can we also send that? This also would give us much power. 🚤
@mrglennjones Oh, good point about Bank Select. Looks like that's not part of the Norns MIDI API but I'm sure it can be done.
I'm going to have to postpone this a bit as I wrap up the v1.4 update, then spend more time thinking about how to implement. It's a bit of a tricky one for reasons I won't get into now, but I think you have the right idea that we need some way of sending events outside of the song arranger loop. I'll let you know when I have an update!
It's no rush, thanks for looking into it 👍
@mrglennjones I just made an update that might get you what you need, although it's a bit of a workaround:
Firstly, I added new events: MIDI port n>>Bank select (MSB) and Bank select fine (LSB)
I can't have those be sent when loading a PSET, but you can achieve something similar by dedicating the first segment of the arranger to "configuration" events like Bank Select/Program Change before the song actually begins.
The trick is to use another new event, Song>>Arranger>>Next position
, at the end of your loop. Set the value to 2 and it will loop back to segment 2 instead of segment 1, bypassing the configuration events.
It's a little awkward since you'll have to move the Next position
event if your arrangement gets longer, and if it's a problem to start on segment 1 (like if you're syncing with other devices), you'll need to manually tell the arranger to jump to segment 2 at the start (hold down the key on row 5 when in the Song Arranger view on Grid and press K2).
Hope that makes sense- let me know if you have any questions or run into issues!
Hi dan, thanks again for tinkering with this. I'll get it tested this weekend and get back to you. 👍
Hi dan, this new version is magic, after playing around, I think it would be useful to have midi bank and program change within each of the chord,seq1,seq2,seq3,midi in. Under the midi channel, so we can set a default bank and patch there. (Which is sent when edited, and at pset load)
This will allow users to instantly audition their patches.
And then be sequenced with the events as you have already implemented
Glenn
Hello mate, we discussed this briefly on Lines but things get lost there sometimes.
I'm currently using a Jv1010 with dreamsequence, it would be handy if I could send program change commands along with a pattern or event so that each of the chord, seq1, seq2, seq3 could be set to individual patches
Love the new kit features btw, having drums along with chords and 2 sequences is fun 😁
All the best Glenn