monokinetic

Wow TK that's brilliant! With Ctrlr, I got as far as scripting the switches in LUA and then had to focus on exams etc. I will certainly try it out this weekend when I'm in the studio and report back with any findings :)

I almost missed this point, wow cool! Do you think we could get into quantising external CV signals? That would be killer :D So my suggestion I've not seen in the thread yet would be to also support some analogue trigger in and outs, for example to sync external analogue LFOs, sequencers etc.

I've also been thinking about this. My main motivation is to be able to take iPad + a simple CORE / SDcard for a live set, so that I don't have to take out my whole MBSeq and risk it being damaged etc. I'd hate for all those hours of hard work soldering and building to be lost. Anyway, I spent an evening looking at the Sysex / CC remote files in the svn/docs directory. My conclusion was that the majority of the settings that we can edit using a front panel could be edited using Lemur / iPad and some clever sysex. The main challenge would be to actually create the Lemur template, something that I won't have time for until summer holidays.... If anyone makes some progress on such a template in the meantime I'd happily be a tester :) Oh and one other crazy idea I had was for a web interface to MBSeq. This could be interesting from a cross platform perspective. Lemur is iPad only at the moment, and I'm not so sure that they will port to Android. You could have nice features like a Ableton-esque grid view of all patterns showing their names, faders for the MixerMap settings etc. TK: I'm thinking out loud here, but would such a thing be theoretically possible?

Hi there, I also use a MBSeq3 front panel, and yes there are sometimes button functions that you may miss! I found the bookmarks features a great way to fix this. Press Menu + Select and you can program shortcuts to useful pages that you may not be able to access from the MBSeq3 front panel directly. Personally I have shortcuts to TrackSelect, StepSelect, ToggleSelect - that covers most of what I need. I think the manual or this section of the forum has TK's instructions of how to use the bookmarks....

Aha I may have caused confusion mentioning the MIDI interface. Sorry if I did. You can of course just use the WiFi functionality (there's a daemon for Lemur which you run on your computer and that does the magic of converting the WiFi connection to a virtual MIDI connection). And this functionality is great in the studio, you can sit where you like and jam on MBSeq, very cool! Anyway, just FYI: I tested the MIDI interface (M-Audio Uno) with cables going from iPad -> Camera Connection Kit -> M-Audio Uno -> MBSeq and that also works perfectly. Lemur immediately recognised the MBSeq! And the reason I wanted this is that I don't trust WiFi in a live situation (I had it cause terrible problems with wireless microphones in a gig last year). I never had MIDI cables do that :)

Confirmed working again over here, cheers TK!

TK, you beat me to it! I installed Lemur for exactly that reason 2 days ago and now you have it running already, that's just amazing :) I'm away from my studio for Christmas etc but the first week in January I will be rocking this out. I will also test it with my USB MIDI as well and let you know how that works. Cheers, this is a perfect end to 2011 David

Hello all, I think I may have found a problem with transmitting SysEx using MBSeqV4. I'm running version 4.054. I have the MBSeq set up to use the router function to send MIDI from USB1 > OUT1 and IN1 > USB1, because I wanted to send SysEx from my Mac to my MB FM while using the MBSeq but I just couldn't get the SysEx to work. So decided to monitor the SysEx coming out of the MBSeq and compare it to what my other MIDI interface - a MIDISPORT2x2 - sends. Here's the results: with MIDISPORT OUT A connected back to MIDISPORT IN A = [MIDI OUT][13:10:17:000042]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 06 08 00 1c 01 f7] [MIDI IN ][13:10:17:000052]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 06 08 00 1c 01 f7] with MBSeq OUT 1 connected to MIDISPORT IN A = [MIDI OUT][13:08:49:000819]: [MIDIbox SEQ V4 Port 1][f0 00 00 7e 49 00 06 08 00 1c 02 f7] [MIDI IN ][13:08:49:000833]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 7e 49 00 06 08 00 06 08 00 1c 02 f7] [MIDI IN ][13:08:49:000834]: [MIDISPORT 2x2 Port A][f0 1c 02 f7] I've tried this test with 2 different pieces of software now (Cubase 6 and Ctrlr v5), exactly the same behaviour. My guess is that something is wrong here. Any ideas? David

Hi Frankie ('tini actually), I haven't used JSynthLib on Mac OS Lion, but on my SnowLeopard (10.6.8) install I had to install the MMJ library to get sysex working correctly. TK has the MMJ link in his post at the top of the thread. Not sure if you have installed that yet? David

Hi Cutter, Maybe you have tried this info from the SammichFM guide already, but just in case you missed it: Have you got a multimeter? If yes, have you tried measuring for continuity between each SMD chip pin and the next part of the track on the PCB that is connected to it? i.e. to make sure that the solder joint is connecting the SMD chip's pin to the rest of the circuit. Have you checked for continuity between all the adjacent pins on each of the SMD chips? i.e. to make sure there are no shorts between the pins next to each other. For more info see Step 1.12 and 1.13 from the SammichFM building guide! :) David

Hi, I've been experimenting with MBSeq4.54 and phrase mode. I've been having a lot of fun with it, but can see some areas that might be enhanced and one slightly strange behaviour. 1: I really like the ability to set mutes on position 1, then the selected patterns on position 2. But it seems a shame that then position 3 and onwards cant be used in phrase mode. It would be nice to be able to have phrases be the 8 Positions long. I think this could make performing songs live more interesting because then phrases become more than 1 pattern long. Even more fun would be to have the actions like mutes, jump, mixer and so on, available as actions as well. This would enable things like: A1:Mutes, A2:Repeat 1st patterns x3, A3:Mutes, A4: Play fill x1, A5:Repeat 2nd patterns x8, A6: Jump > A1 :) 2: It seems that each time I load up the seq, the first time I hit the song button the right LCD shows something different than what I have stored on GP1. When I press GP1, or switch to any other GP then back to GP1, the correct patterns are shown on the right LCD. Is that the expected behaviour? 3: Could phrase mode have external MIDI CC control of which of the phrases is currently playing? I'd like to use another MIDI controller to set the current phrase while on the MBSeq Mutes page. Again would make playing live with the phrase mode more flexible IMO! David

gomiboy99, Due to the coolness of Wikis, you can see the history of the page edits here: http://www.midibox.org/dokuwiki/doku.php?do=revisions&first=20&id=wilba_mb_seq_pcb_bulk_order I'd suggest that you should be allowed to insert your name back in to the list according to this (the date is clearly shown and the order of user edits). But I think the admins / page owner should make any final decision on that! David (edited for clarity)

OK thanks for the clarification TK, sounds like you've thought of everything :) I'll go and sign up then! Cheers David

Aha OK maybe I wasn't clear enough, I want to know if there will be a drilled front panel covering the PCB as part of the box or not (similar to Wilba's front panel for the MBSeq full version). The reason I'm asking is that you can see on the photo that there are the 8 BC337 transistors in the right hand top corner of the PCB. These look almost as high as the buttons and I'm not sure how this will be handled. Hope that's clearer... David

Hi TK, This looks great, but before I sign up for a PCB I'm interested in the case that has been mentioned. Will this PCB sit behind an acrylic front panel, or will the buttons and LEDs be exposed? David

OK great, it's a new connection for me so just wanted to be sure! Just sent my order, thanks to you for offering this exciting new platform :) Wow, cool. One less thing to solder ;) Cheers Thorsten!

Oh they look lovely :) Great work TK! Before I send my order, is the MagJack the same one used on the MB_ETH from the group buy by Seppoman? David

Me me me! Wow thanks for that link, and by chance it's about 10 minutes from my Mum's house :)

Hi TK, thanks for clarifying. Would it be possible to request a switch to control this behaviour? It also raises another question from me: what is the purpose of the generate button in this case? Cheers David

Just sent payment :) Cheers for working on this

Hi, I have been using the random generator over the weekend and found something a bit strange: I thought on MBSeq3 that when you used the encoder to change the LayA / B / C parameter that you still had to press Generate to modify the layer. It seems on MBSeq4 that as soon as I move the encoder under LayA that my layer gets randomised. Is that normal? David

Aha, thanks a lot TK, that's very interesting. So it sounds like we already have the tightest syncing sequencer around :D Cheers David

I have been thinking about this and thought it would be better to keep the info in this thread rather than starting a new one. Anyway, I would like to ask: Would there be "better" sync between MBSeq and a DAW if MIDI timecode (MTC) was used? (I don't have any sync issues so far, but it would interest me if MTC would be tighter than Midiclock) If there would be an advantage to making MBSeq a MTC master, would it be possible to implement at some point? Cheers David

Sorry to drag this up again, but I was just wondering if there would be a chance of fixing this behaviour? David