[MIDIbox SEQ V4 Release + Feedback]

Yes, this is how the algorithm is working.

If I wouldn't handle it this way, Track 1 would stay selected even if you want to select another track exclusively

I don't want to change this, as the page is essential for people who want to quickly select between tracks in different groups (single-selections)

OK I understand, I had not thought of that use case.

Thanks for giving me the right order of selections!

I worked in technical support for 4 years, I know how vital a clear description is :wink:

I was able to reproduce the problem.

I guess that it's related to the SEQ_UI_CheckSelections() function:

/////////////////////////////////////////////////////////////////////////////

// Should be regulary called to check if the layer/instrument/step selection

// is valid for the current track

// At least executed before button/encoder and LCD function calls

/////////////////////////////////////////////////////////////////////////////

s32 SEQ_UI_CheckSelections(void)

{

  if( ((ui_selected_tracks >> (4*ui_selected_group)) & 0xf) == 0 )

    ui_selected_tracks = 1 << (4*ui_selected_group);


  u8 visible_track = SEQ_UI_VisibleTrackGet();


  if( ui_selected_instrument >= SEQ_PAR_NumInstrumentsGet(visible_track) )

    ui_selected_instrument = 0;


  if( ui_selected_par_layer >= SEQ_PAR_NumLayersGet(visible_track) )

    ui_selected_par_layer = 0;


  if( ui_selected_trg_layer >= SEQ_TRG_NumLayersGet(visible_track) )

    ui_selected_trg_layer = 0;


  if( ui_selected_step >= SEQ_TRG_NumStepsGet(visible_track) )

    ui_selected_step = 0;


  if( ui_selected_step_view >= (SEQ_TRG_NumStepsGet(visible_track)/16) ) {

    ui_selected_step_view = 0;

    ui_selected_step %= 16;

  }


  if( ui_selected_step < (16*ui_selected_step_view) || 

      ui_selected_step >= (16*(ui_selected_step_view+1)) )

    ui_selected_step_view = ui_selected_step / 16;


  return 0; // no error

}

The first check ensures, that for the case that no tracks are selected in the current group (anymore), the first track of the group will be automatically selected.

In MBSEQ V3 this missing check was leading to confusion (somebody thought his sequencer crashed since no values could be changed in the edit page anymore).

I will improve the track selection, so that a valid group is determined for the scenario that you gave me!

Best Regards, Thorsten.

:frantics: As ever your explanation and support is amazing. I will check out and try during the week. Cheers Thorsten!

[MIDIbox SEQ V4 Release + Feedback]

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.

[MBSEQ usb out to daw --> out daw to usb midi interface --> out to synths]

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:

Does cubase have midi clock in sync? I would love to use the mbseq as master for this.

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

TK can we get more nodes please?

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...

[MBCV Gates - 5V to 12V here's a circuit]

I tried and it told me I wasn't allowed. I searched but no luck. I designed a PCB (based on a MFOS design) for a Gate buffer/comparator to boost MBCV gates to 12V for modular stuff. It has 8 gates and gives you 8 triggers too. I'd love to share. It's 1 sided with a few jumpers so you can etch it @ home :thumbsup:

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

[oscillator from a crystal]

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

[SwinSID - a pin compatible alternative to the SID chip]

That's exactly what I was referring to when I said:

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:

thanks for posting this useful information, monokinetic! very useful indeed, as this makes decision easy for me.

Cool, glad to be of some help! You could always hook up both later on for more fun....

[SwinSID - a pin compatible alternative to the SID chip]

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

[Virtual MIDIbox SEQ V4 for iPad]

Since iPad and the Simulator (running on a MBP) communicate with MBSEQ via WiFi, I know that this is neither a MBSEQ issue, nor a protocol issue - it's either related to several Juce layers, or to the slow iPad CPU, or to the slow network interface of the iPad.

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

[Virtual MIDIbox SEQ V4 for iPad]

Last weekend I tested the iPad with iOS 4.2 + iPad Camera Connection Kit+ midi monitor app + gm5x5x5, and...

IT WORKED!!! , ok... just tested moving things on the app, the gm5x5x5 leds shine away like a christmas tree, I'll have to test midi input too later.

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.

(tried also with a m-audio midisport 4x4, no go)

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.....

[sammichSID Prototype]

I HAVE NO IDEA WHAT THAT GUY IS SAYING ON THAT PAGE

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 :)

[Debounce in MIOS32]

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

David

[Debounce in MIOS32]

Thorsten,

As always you are a gentleman :)

nobody complaint about this yet, accordingly it seems that most users don't need button debouncing at all.

That's interesting. I guess I manage to be the first for once :D

However, it's supported by Beta32 now:

http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2FCHANGELOG.txt

Thanks a million for such a quick turnaround. I will try and compile it tomorrow and let you know my results.

Cheers

David

[Debounce in MIOS32]

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

[Core 32 J8/J9 strangeness]

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.

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?

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

[Core 32 J8/J9 strangeness]

the missing termination is probably not the reason for your trouble, but it is documented here: http://ucapps.de/midibox_seq/mbseq_v4_din.pdf

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

[Core 32 J8/J9 strangeness]

Hi Thorsten, thanks for the info.

the DIN/DOUT modules cannot be controlled without pull-up resistors, because pins are working in Open Drain mode, which means that they are switching between Vss (for logic-0) and high-impedance (for logic-1)

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 :)

Nothing to be worried about, you measured the resistance between VS -> any other component (e.g. chips) -> VD -> pull-up resistor

Aha, from memory I think there was also resistance between some of the SI/RC pins, but I forget exactly which.

The path between Vd->SC/RC/SI/SO is the interesting one.

So I will install R31 again and test exactly where I was measuring the resistance tonight.

It would be interesting what you mean exactly with "they don't work correctly" - what is the effect?

Are they not working at all (no LEDs enabled, no button event regognized), or do they behave randomly? Are LEDs even flickering, and/or do buttons trigger the wrong functions?

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

[Core 32 J8/J9 strangeness]

terminator :)

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.

[Core 32 J8/J9 strangeness]

did´cha install the arnold?

Err I'm not sure if I understand? Arnold?

[Core 32 J8/J9 strangeness]

Hi all,

While preparing to finish my upgrade to MBSEQv4 I have found a strange problem on my Core32 board. Currently I have my SDCard working, LCDs working, external power ready. But when I hooked up my DIN/DOUT boards they seem to not be working correctly. I got the same behaviour with or without a customised HWConfig file on my SDCard.

After lots of following cables and making sure I have the SC/RC/SI/SO lines connected correctly, I tried checking the Core32 J8/J9 connector to make sure R31 (the 4x220 Ohm SIL resistor) is working correctly. I found that something was very odd, I could measure 30k resistance between VS and SC/RC/SI/SO!

I removed the SIL resistor and found I have no resistance on the SC/RC/SI/SO lines.

I tested the SIL resistor now that I have removed it and it seems fine i.e. 220 Ohms from the dotted pin to each other pin.

Before I install a new 220 Ohm SIL resistor, I would like to ask if it would be worth trying the connection to my DIN/DOUT boards without the 220 Ohm SIL resistor installed? Or should I just install the new one and see what happens with that one?

Thanks in advance for any help.

David

[Is this possible to CV IN ?]

TK I would also be interested in a CV record function. If this was combined with an AOUT things could get very interesting. I can imagine recording control voltages from a softpot for example could be lots of fun, especially if the CV could be quantised :) From what you were imagining, would it be possible to record the CV as both a CC type track and a note track (maybe not the right term but i hope you know what I mean!). I think both would be useful, but the second option would obviously require a gate in to the core32.

Also I imagine we would have to put some overvoltage etc protection on whatever pin was used as the CV in if we wanted to interface to modular synth CVs. I'm sure you know how to do such a thing, but if anyone is interested the sequencer schematic here has a good example of protecting a microprocessor from too high/negative voltages.

http://www.acoupel.com/sequencer/schemas/ACS%20Sequencer%20schema.pdf

(Im adding one of these to my modular, lots of fun as well!)

David

[MIDIbox SEQ V4 Release + Feedback]

wow TK, you are unstoppable :)

as I'm still the only one who finds this topic interesting, it's low priority ;)

Well I for one am very interested in the OSC as I'm a Kyma user. Just have to finish that darn Ethernet board and I will start bugging you with support requests :D

[Virtual MIDIbox SEQ V4 for iPad]

Just did this touchOSC layout, added red/green leds on the first row of switches to check if that's the way to go...

Wow that was quick!

you need to use OSCulator or something to make this useful?

Well my understanding was that we could use this to test OSC going from the MBSeq to iPad. I don't see how OSCulator would be involved here?

The problem for me is that I still have not finished soldering my Ethernet for the MbSeq so I can't test it on the hardware. Hopefully during the week I can get it done.

Anyone else got an iPad + Ethernet enabled MbSeq apart from TK? :)

David

[Virtual MIDIbox SEQ V4 for iPad]

Damn, it is a shame that you are having problems with the iOS version, this would be a killer app for me.

I have tried pinging my iPad and I get similar average times to you. This seems strange though, I have been using OSCemote and TouchOSC to send OSC to trigger Kyma and I have not had any noticeable datatransfer problems, even when sending a large amount of data (ten fingers with X,Y position and other TUIO stuff) I haven't noticed any timing issues. I realise this is just sending data one way, but a quick Google shows iPads doing similar sequencer editors for Ableton and SuperCollider. Also I could mention that my initial problems with iPad and OSC were solved by updating my Asus wirless router to the latest firmware....

Just brainstorming here, but would it be worth trying a purely OSC based solution to see if the iPad is up to the job? I could quite easily create a TouchOSC layout with the required buttons, that might at least identify if it is a problem with the iPad hardware / Juce software.

Other than that I'm not sure what else could be worth trying....

David

[AC Sensorizer cable shield]

Hiya nILS,

Ok cool thanks!

David

[AC Sensorizer cable shield]

Hi,

I just finished my AC sensorizer. I will be using it with some pressure sensors mounted on a glove under my finger tips :)

I'm not sure if the 2.5 m cable going from the MIDI box running AC Sensorizer to my glove with sensors should be shielded or not? The cable is carrying 5v, ground + 4 outputs from the sensors back to the Midibox. If you think shielded is best, then do I connect both ends? I have a feeling that you usually just ground one end of shielding, but I'm not sure what's best in this case....

Thanks in advance

David