monokinetic

Aha, OK thanks for the clarification.

Hi, It's great this is going to happen finally. But I would like to make sure I understand: Have you sent the PMs already? So far I have nothing, but sent you a PM today to make sure I'm registered! Are you shipping from inside Europe? (there are new tax laws in my country and packages from outside EU take up to 3 months in customs!!) Thanks in advance David [edited] because I forgot the quote

Hi, It's great this is going to happen finally. But I would like to make sure I understand: We need to register by 12th June. So do we just send you a PM to say "I want to register"? Are you shipping from inside Europe? (there are new tax laws in my country and packages from outside EU take 3 months in customs!!) Thanks in advance David

aha OK thanks for confirming it! Interesting idea with the G/T buttons. I already have Track-Select on a bookmark :) @TK: I know there is not many of us with the V3 panel, but it might solve this problem if the GP > Assign/Trigger page allowed you to select the trigger layer currently being edited. I have a feeling this worked at some point, because on that page you can "choose" a trigger by pressing the A to H buttons i.e. it starts flashing. David

Hi nuke, Thanks for the reply. But I think I can see that my original question was not clear enough. I should also mention that I use a MBSeqV3 front panel and not the MBSeq V4 panel i.e. no trigger layer buttons.... Anyway, I have done more testing and here is the process I'm following: Track 1 set to a normal note track (i.e. with 256 notes, 4 ParL and 8 TrgL), I can use the trgsel page (page 4) in a bookmark to select the trigger layer to be edited. No problem. Track 2 set to a drum track, which as I mentioned in my first post, should have 2 trigger layers. But when I use the trgsel page to select a trigger layer I get only the 16 drum sounds (BD SD CH and so on). If I remember correctly, in MBSeqV3 I could use "Menu > Assign (Trigger on V4 panel)" and press the GP button below a trigger layer to switch to a trigger layer (I thought that's why it flashes?). But currently with Beta41, it seems it is not possible to edit the Trigger B layer in this way, as far as I can see. So is there another way to select the trigger b layer on a drum track? David

Hi I'm playing around with programming some rhythms today and would like to check something: My track is set to "Drum (64/2*64)" which AFAIK has 2 trigger layers. I go to the trigger select page, set R.G. to layer B. Then I press the GP button below to select this trigger layer (i.e. it starts flashing), I thought then it is possible to edit the trigger layer. But it seems that when I press Edit to make the changes I'm still on the TA:Gate layer! Is there some other way of selecting to edit all of the steps trigger B layer that I'm missing? in On non-drum tracks I can edit the trigger using the trigger view mode, but this seems to do nothing on drum tracks, even if in theory they have 2 triggers. Any ideas? Thanks in advance David

OK I understand, I had not thought of that use case. I worked in technical support for 4 years, I know how vital a clear description is :wink: :frantics: As ever your explanation and support is amazing. I will check out and try during the week. Cheers Thorsten!

TK: the bookmarks function is really amazing, thanks! I have a V3 front panel still, so accessing some newer pages which are from V4 has always been tricky for me. Now the bookmarks function solves any problems with that, hurrah! However, this evening I have found some strange things with the track select page. When entering the track select page, track 1 is selected. As soon as I press to select another track 1 is deselected. Is that expected? I normally use the track select page to select more than I can access by my 4 track buttons and would imagine that the currently selected track should remain selected and the group of selected tracks be added to using this page. More a suggestion than a problem. Next, what seems to be wrong to me is that I then press 3 and 4, this selects each track as expected. But when I press 5 to add to the group of selected tracks, tracks 2, 3 ,4 become deselected! A similar thing happens when trying to entering the track select page then pressing 13, 14, 15, 16, 12, 11, 10, 9 in that order to select them. Then pressing 16, 15, 14 to deselect, works fine. But pressing 13 deselects also 12, 11, 10, 9! It seems that track 1 in each block of 4 tracks is the cause of the problem, but that's just my guess. Just thought I would mention this behaviour, not a major problem but a bit weird :) David ps I should mention that I have my MB_SEQ_HW.V4 file quite customised to match the V3 generation panel. I can post it if you would like to take a look.... oh and I'm running beta 41.

Hi, sorry to resurrect the thread after a month but I wanted to say thanks to Hawkeye for the idea of using the MBSeq virtual USB as a MIDI interface. I don't know why but it never occurred to me, super useful! Also there's a few points I thought I could add to: No the versions of Cubase and Logic I use both do not support syncing to external MIDI Clock. AFAIK the main reason for this is that MIDI Clock is not high resolution enough to easily sync their audio engines to. On the other hand, MIDI Timecode is still supported as an external sync source by the majority of DAWs. This is a higher resolution form of sync. @TK: I would be interested if MBSeq could be setup to transmit MIDI Timecode. Would this get us tighter sync between MBSeq and DAWs? I much prefer the idea of MBSeq being master of sync in my studio than any computer :) David ps: I think with this question it may not be so necessary. As far as I understand it, the nodes represent physical MIDI ins and outs. Each of these carries 16 MIDI channels, so you shouldn't run out separate channels for your synths. In fact with the list of nodes set up as you listed in your post, you would have 16 * 4 = 64 channels, I think :) Hope that helps...

Ooooh, that sounds helpful :) Can I assume you could run it on a 15V PSU? You could always .zip the file. I'm pretty sure that should upload... David

Hi Tom, I found this page a few years ago. It's by a guy who built a MBFM: http://web.t-online.hu/gyurek/midibox.htm#oscillator I have not used it myself, but the schematic seems simple to try. David

Aha, ok in that case: <very_nice_voice> nILS I for one would love to have a PCB layout of a stereo MicroSwinSID using through hole Atmel 88</very_nice_voice> :thumbsup: Cool, glad to be of some help! You could always hook up both later on for more fun....

By the way do you guys know that Swinkels has released a newer SID emulation called Micro SwinSID? The main differences seem to be using a newer Atmel chip, which enables a higher sample rate, and now the output is direct from the chip - no DAC required (the TDA is getting harder to find unfortunately). There is an informative review here: http://ilesj.wordpress.com/2010/11/21/micro-swinsid-an-avr-based-sid-replacement/ I know that Swinkels was active around here at one point, so maybe we could ask if the Micro SwinSID might be useful to us? I for one would be interested in a PCB and pre-burned chip bulk order :) David

TK, sorry to drag this back up - but I came across a piece of relevant info. I was recommended that if you want to get the best performance from Computer to iPad Wifi connections that you should use an Adhoc Wifi network setup directly between Computer and iPad. This eliminates the wifi router from the chain, routers are well known for adding latency apparently. Just thought I would mention it as another possible way to solve this. David

Cool, I was hoping to test it this weekend but am still waiting to upgrade to 4.2. At the very least I can hook up a 5x5x5, excellent news. Does the 4x4 use bus power (i.e. does it have an external PSU)? If not then I found iPad is quite fussy about powering external USB devices, I tried a few sound cards. The best solution seems to be using a powered USB hub, my iPad was picking up most things I used after that. Obviously with MBSeqV4 this wouldn't be necessary as the Core32 has it's own power on board. In fact do you have a Core 32 to plug in and test? That would really interest me ;) I'm imagining having a simple Core32 + SDcard board connected to the iPad USB being used as a control surface for MBSeqV4.....

Well my Czech isn't perfect but essentially it's very positive build report, at the end he concludes that it would be nice to have the model with 8 SIDs and CV but this sammich will keep him happy for now. I'm glad to see a Czech midiboxer :)

Works absolutely fine for me, thanks a million - I'm off to play with this beast finally :D David

Thorsten, As always you are a gentleman :) That's interesting. I guess I manage to be the first for once :D Thanks a million for such a quick turnaround. I will try and compile it tomorrow and let you know my results. Cheers David

Hi all, I have pretty much finished the upgrade of my older MBSeq to MBSeq V4 now, but for some reason I am getting quite unreliable button presses. Sometimes when I press a button it toggles the step setting randomly, other times I get the expected functionality, sometimes it makes no difference. I'm sure the front panel is mechanically functional as this hardware ran fine on MIOS8, and the problem suddenly affects all buttons. I installed the terminator on both DIN and DOUT SRIO chains ( good tip Hawkeyes!), but unfortunately no change in behaviour. My guess is that Core32 is more sensitive to button quality and my buttons are pretty average quality (still looking forward to that MBSeq V4 pro panel group buy :thumbsup: ) On MIOS8 I would have played with the #define DEFAULT_SRIO_DEBOUNCE_CTR 32 setting. But on MBSeq V4 I don't see a way to tweak the button debounce in the hwconfig file. The only place I found a setting related to debounce (of the front panel rather than the BLM) is in the project.lss file and I'm not sure if I should be tweaking that :) Any suggestions? Cheers David

Hurrah, I have got the DIN and DOUTs working perfectly now. Silly me, I had mixed the SC and RC lines :blush: I will reply to myself just to finish this off. There should not be any resistance on SI, I should have double checked the schematic before posting. Still making noobie mistakes after 8 years here, ah well :hmm: Case closed! Cheers David

Ok, now I know what you mean :D I must admit I don't have the termination on either chain, I know it was recommended at one point with MBSeq3, but I had already put mine in the box by the time I realised! I will give it a try tomorrow though, thanks for the pointer. Hasta la vista! David

Hi Thorsten, thanks for the info. Ok, I had a feeling this was probably not too helpful. I'm a bit stuck and I was trying to come up with other things to test :) Aha, from memory I think there was also resistance between some of the SI/RC pins, but I forget exactly which. So I will install R31 again and test exactly where I was measuring the resistance tonight. Well, to be more specific each time I turn on, a random set of LEDs is lit. No buttons on my front panel or encoder seem to make any difference i.e. I cant change any parameters on the LCD and the GP buttons do not toggle LEDs on or off. I guess my next step is to put R31 back and post here exactly which pins have the resistance. Any other suggestions? Edit: update is that with R31 back in, on the Core32 board J8/J9 (with nothing else plugged in) I can measure 220 Ohm from VD to SC, RC and SO. But nothing on SI. I checked and the IDC socket SI pin is definitely soldered correctly, so I guess it must be something between the SI pin and the R31. Any ideas what could cause it? Cheers David

Aha :) but terminate what? The DIN/DOUT chain? If so then can you point me towards where this is described, I don't see it anywhere on ucapps.de.... is this a new thing? My DIN/DOUT chain has been working as is for over 3 years now.