borfo

Wow... You can use the humanizer, echo, and LFO on incoming MIDI on the two channels that Seq1 and Seq2 are set to - and LFO and echo can be enabled/disabled by starting and stopping the V4L playback. This is awesome. Thanks again. Edit: beer.

Wow. That's great - it works perfectly. Thanks so much for making that happen. I've been looking for a device to do that for ages - the MI Midipal comes close, but only listens on one channel. This will make a lot of really cool stuff possible for me - thanks!

Hm... I didn't see the LiveForceToScale parameter in SESSIONS/DEF_V4L/MBSEQ_C.V4, so I added it at the end of the file. I'm not sure if it's having any effect. Now, the V4L seems to receive MIDI on channels 1-4 (doesn't seem to receive or forward notes on channels above 4), forces the notes to scale, then outputs all the notes on whatever the channel of the currently selected Sequence - eg: MIDI keyboard sends on Ch 3, Seq1 is selected, MidiCH for Seq1 is set to Ch. 9. All midi notes received from the keyboard on Ch 3 are forced to scale, but they are sent out of the V4L on Ch. 9. What I would like to do is have the V4L receive MIDI on all 16 channels, force all the notes to scale, then output the notes on the channel they were originally received on. eg: MIDI note is received on Ch. 11, it is forced to scale, then sent out on Ch. 11. Another note is received on Ch. 4, it is forced to scale, then sent out on Ch. 4. Etc. Is that possible?

Cool - that's great. It will forward all incoming midi on all channels with that setting?

Is it possible to set the V4L up so that it takes incoming midi on all channels, applies force-to-scale to all channels, then forwards all channels onwards on the channel each note was originally received on, with the force-to-scale applied? Since I've built a Seq V4, I'm not using my V4L much anymore, but it would be great to put it at the end of my midi chain as a force-to-scale device (I've got some randomizers and other note-processing things chained in after my seq v4)... Unfortunately, it seems the V4L only forwards notes on the midi channels selected for the two sequences, and drops all other notes. Is there a setting I'm missing somewhere that could do what I'm looking to do?

Cool... Thanks!

I'm assuming you're making Ilmenator's 4x16 pcb? I'd be interested in a PCB that fits standard tact switches, but I think those marquardt switches would make it a bit too expensive for me. They're definitely pretty switches though.

Cool. Thanks. In case anyone finds this thread looking for BLM_SCALAR_Port numbers, here's the relevant section: DEFAULT = 0x00, MIDI_DEBUG = 0x01, USB0 = 0x10, USB1 = 0x11, USB2 = 0x12, USB3 = 0x13, USB4 = 0x14, USB5 = 0x15, USB6 = 0x16, USB7 = 0x17, UART0 = 0x20, UART1 = 0x21, UART2 = 0x22, UART3 = 0x23, IIC0 = 0x30, IIC1 = 0x31, IIC2 = 0x32, IIC3 = 0x33, IIC4 = 0x34, IIC5 = 0x35, IIC6 = 0x36, IIC7 = 0x37, OSC0 = 0x40, OSC1 = 0x41, OSC2 = 0x42, OSC3 = 0x43, OSC4 = 0x44, OSC5 = 0x45, OSC6 = 0x46, OSC7 = 0x47, SPIM0 = 0x50, SPIM1 = 0x51, SPIM2 = 0x52, SPIM3 = 0x53, SPIM4 = 0x54, SPIM5 = 0x55, SPIM6 = 0x56, SPIM7 = 0x57

Cool - Store hasn't been working for me. I wasn't sure whether that was a bug or whether it was something on my end. I'll try again once the next release comes out, and I'll also try entering the settings directly into the GC.V4 file. Thanks. How are the BLM_SCALAR_Port numbers calculated? Is that documented anywhere?

Yeah, I did that - specifically: - set osc_remote 3 192.168.11.102 - set osc_local_port 3 8000 - set osc_remote_port 3 8000 - set osc_mode 3 1 - set blm_port OSC3 - store USB works without issues (although I have to hardcode the connection into the MBSEQ_GC.V4 file on the SD card), but ethernet/OSC doesn't seem to work. The V4's ethernet connection is working fine. t's not too much of an issue since I can use USB, but I thought I'd check if anyone else has the ethernet connection working before I try troubleshooting it anymore.

Out of curiosity, does anyone have the Lemur BLM working over ethernet? It's working fine on USB for me now, but I still can't get it to work over Ethernet.

Be careful that your wiring is right before connecting them. Apparently VFDs can blow pretty easily if you send voltage to a data pin. - they're drop in replacements for the standard displays used with a Seq V4, except pins 15 and 16 are not connected. You can use the standard cable, just make sure that it's oriented the right way, and pin 15 and 16 are not connected. I had some strange problems with mine to begin with - not sure what the issue was, but for a while only one of them was working with my Seq V4. A second one mysteriously started working a bit later on. I bought 3, and still, only two of the three work. Using the factory test points, it seems that all three are fine, working displays - I'm still not sure what the issue is. But two of them work, which is all I need for now, so I stopped trying to troubleshoot the issue.

it's not clear what the model number is on these ones, but it's probably the same one that I've got. Two CU40025-UW6J's are working fine in my Seq V4. They really look great, and they respond very fast. FYI, Noritake seems to put these displays on sale fairly regularly for 1/2 the listed price on http://noritake-vfd.com/ - my 40x2's were about $23 each + shipping.

Oh, right... That makes sense - it does look like they're all the same switch rather than a differentiatable matrix. ...yeah, probably not worth bothering with clickable encoders then. Thanks.

Looking at the schematic here: http://www.midibox.org/dokuwiki/lib/exe/fetch.php?media=wilba_mb_seq:wilba_mbseq_pcb.pdf It doesn't look like they share a connection... But I'm not really sure how this button matrix works from a technical/electronic standpoint, so I could easily be wrong about that.

The PCB seems to have holes for switch connections on the encoders, but the encoders SmashTV sells aren't clickable. I'm probably going to build a second Seq V4, and I'm wondering whether I should use clickable encoders. Are they supported by the Wilba frontpanel? If so, what do they do by default?

Thanks - that's funny, I hadn't noticed that the BLM already switches to a force-to-scale mode - looking at the lemur implementation a little more carefully, it's clear that it does. That's great. It looks like the whole BLM goes into force to scale mode for all tracks whenever force to scale is enabled on the mode page for any single track - is that correct?

I'm thinking of writing a raspberry pi/2xnovation launchpad implementation of a Midibox Seq BLM. I'm thinking I'd use processing in the raspberry pi to emulate a larger set of buttons on the novation launchpads - 2 LP's would be an 8x16 array with two extra vertical rows and one extra horizontal row. I'd use the second vertical row for a variety of "shift" and modifier buttons which could move the area displayed on the 8x16 LP matrix - default would be to display the top 8x16 section, pressing a modifier would display the bottom 8x16 section. Is it possible to implement a larger button matrix? Like, would MIOS support a 32(vertical)x16(horizontal) matrix? If so, I could set up my software to emulate (and use modifiers to page through) a larger vertical space. I've found the BLM user manual page and the document at (root)/trunk/apps/controllers/blm_scalar/README.txt Is there any other BLM documentation hidden away anywhere that I should look at? What files in the MIOS source code contain the BLM input/output handlers? [edit: turns out I'm an idiot and didn't realize that the BLM already has a force to scale mode. Disregard this last part.] Also, is there any way (via MIDI) that I could ask the Seq V4 whether force to scale is enabled, and which scale is being used? I think it would be useful to implement a BLM where only the notes in the selected scale are shown (for non-drum tracks) - this would make better use of the vertical space (you could display more than two full octaves on a 16x16 grid). If you could just ask the Seq what scale is being used, you could calculate which notes should be shown. This would be a feature I'd add to my BLM implementation later, once I had the basic functionality working - not something I'd do right away. Implementing this might be even easier if you could send a midi request to the Seq v4 and have it return a message that somehow encoded the notes that are available in the selected scale - not the MIDI note numbers, but a reference to the note names - eg: D, E, F♯, G, A, B, and C♯ for the scale of D major, and you could calculate the midi note numbers from that, without having to know the scale.

Cool. I'll take them then (both data knobs) - I'm in Toronto, Canada.

Cool. Thanks. If it's easy to do at the same time, it might also be useful to add the ability to modify all tracks with one NRPN too - I'm thinking things like transposing, forcing all tracks to scale, or disabling effects on all tracks at once. I'm really impressed with this sequencer, by the way. Great work.

I've just finished building one of these awesome things... TK, you've really made a great device. Congratulations and thanks. I'm having a great time figuring it out, but I thought it would probably speed things along to meet up with someone who's been using one for a while and knows their way around the device. If anyone's in Toronto and wouldn't mind meeting up to show me around the device by playing with it for an afternoon or something, that would be great. I've built a bunch of MIDI DIY projects, so if we did it at my place there would probably be a few devices you might be interested in trying out, too. I'm downtown, close to Spadina station.

Looking at the CC implementation document, I doubt this is currently possible, but no harm in asking I guess. /trunk/apps/sequencers/midibox_seq_v4/doc/mbseqv4_cc_implementation.txt http://www.svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fdoc%2Fmbseqv4_cc_implementation.txt&peg=1325 Instead of having to specifically select a track to modify via the NRPN MSB, I think it would be useful to be able to send an NRPN that modifies whatever track(s) are currently selected on the Seq V4's track buttons - looking at the CC implementation document, it seems you can send a value of 0-15 in to select a track. Would it be possible to add the ability to send an MSB value of 16 to tell the Seq V4 to modify whatever track(s) are currently selected? Seems like this would enable some interesting external MIDI control interfaces. Is this possible now? ...I'm assuming it's not. How easy would this be to implement?

Are those two different types/sizes of small encoder knobs? I'm interested, but I think I'd rather have the 16 step encoder knobs be the same...

I have asked him. No response yet. Thought someone else might know.

Does anyone know if there's a parts list anywhere for the STM32f4 MIDI I/O Board that's available to order from SmashTV?