TK.

MIDIbox SEQ V4 Release + Feedback

1,562 posts in this topic

Ok, I see.

 

Forget this option, it won't work properly without a lot of additional work at different places (not only seq_ui.c)... :-/

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

I understand - thanks nevertheless!

Share this post


Link to post
Share on other sites

Hello,

 

Somebody knows where is the BOM for the control surface?

I am lost concerning the connectors...and other few components...

 

Regards,

 

PK

Share this post


Link to post
Share on other sites

You mean Wilba's control surface design? It's over in the WIKI.

Share this post


Link to post
Share on other sites

Yes, but it still misses the J1, J2...

What is it schedueled for these?

Share this post


Link to post
Share on other sites

Ok, these would be

 

2x 2×5 dual row headers (for DIN/OUT connection to Core/ultracore and extension to optional button/LED matrix).
 

e.g. Reichelt part WSL 10G.

Edited by ilmenator

Share this post


Link to post
Share on other sites

Update Complete!

 

Hey there, I just like you to know that I am very, very glad and full of motivation to work with my midibox again.

Originally built in 2005, the "baby" has now made the next step.

It was updated from V2 to V4, which was not too difficult beside the hardware button configuration.

Encoders are no longer flickering due to the non-detended option and the amount of functions is just crazy.

 

Cheers

 

Michael

Share this post


Link to post
Share on other sites

Congratulations for the successful upgrade! :)

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Hi!

 

I have a feature request, which may or may not be doable. I would like to use one of my lre8x2cs boards with my Sequencer. I am using Wilba's panel and envision plugging the lre8x2cs into the J2 on the CS PCB. My request is whether or not we could have a setup page to assign the encoders and switches on the lre8x2cs to various parameters? My plan is to use the first 8 to control the CV outs that are controlling two of the sm2044 pcbs, and the other 8 for various things like LFO's and midi delay parameters. Would this be possible in some form?

 

Cheers,

Alex

Share this post


Link to post
Share on other sites

Hi Alex,

 

such a feature would require a some mapping tables which are very hard to maintain! :-/

(effort that I don't really want to spend by myself)

 

You could use a second core and run the MBNG firmware on it. It could send NRPN parameters to the MBSEQ: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fdoc%2Fmbseqv4_cc_implementation.txt

 

A direct access to the CV outputs is currently not provided via NRPN, but I could add this if you go this route.

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Thanks TK,

 

That sounds like a good option... I am in the process of switching from the STM32 to the LPC core on my sequencer due to never being able to get either of my AOUT_NG's to work with the core32... They work fine with the LPC.

 

In your suggested solution, would I be able to hook the AOUT up to the sequencer core? If so I can use my stm32 for the MBNG end, if not then I would get another LPC built... I would of course prefer to be able to use the STM32.

 

Thanks,

Alex

Share this post


Link to post
Share on other sites

Hi Alex,

 

yes, you can use the STM32 core for MBNG, and the LPC17 core for MBSEQ with AOUT.

It will be possible to access the AOUT channels directly via NRPN

 

In addition (but this is unrelated to your request, just a general informations for others), I'm planning a new routing option which allows to send MIDI events to the selected MIDI port/channel of the 16 tracks.

It will work the following way: if an external MIDI controller (such as MBNG) sends MIDI events to MBSEQ over channel 1, the events will be routed to the selected MIDI port and channel of Track #1

Channel 2 will be routed to the MIDI port/channel of Track #2, etc.

 

This will significantly simplify the integration of MIDI controllers and keyboards! :smile:

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Great, exciting!!! I got my LPC core hooked up to wilba's front panel, confirmed it works with jbdiver's aout/gate breakout PCB (except that gate 8 is gate 7 and gate 7 is routed wrong due to a difference between J5c on stm and j28 on lpc). I am getting a hardfault anytime I try to copy files to and from the sd card and my laptop... I only get the hardfault with the seq firmware and not with the NG. I am getting around it by inserting my SD card directly into my laptops sd port.

 

 

Cheers,

a

Share this post


Link to post
Share on other sites

I guess that it crashes when the MSD driver is activated, right? This could be related to a RAM consumption issue again.

 

You could use the MIOS Filebrowser instead, did you already try it?

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

The file browser works, but it isn't possible to upload multiple files or folders. That's why I went the other route, plugging my sd card into my laptops slot.

Cheers, alex

Share this post


Link to post
Share on other sites

A new release is available:

 

MIDIboxSEQ V4.071
~~~~~~~~~~~~~~~~~

   o if not in song mode, the Rew/Fwd buttons can now be used to select the step view.

   o the MIDI router provides the new destination "Track".

     If this destination is selected, incoming MIDI events will be routed to the
     MIDI port and channel of a track depending on the incoming MIDI channel number.

     Usecase: MIDI events, such as CC or Notes, should be sent from a master keyboard
     or MIDI controller to synths which are assigned to different port and MIDI channels
     in the track configuration.
     Just select the track with the MIDI channel on your keyboard/controller, the router
     will take care that the events reach the right destination.

   o it's now possible to send a CC when a track has been selected.
     This feature allows to synchronize the track selection with a DAW.
     It has to be configured in the MBSEQ_HW.V4 file (search for TRACK_CC in hwcfg/*/MBSEQ_HW.V4)

 

 

@Alex: sorry, your requested feature to control AOUT channels via NRPN needs some more time.

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

No worries!!! Take your time and thanks for the effort!

Cheers, Alex

Share this post


Link to post
Share on other sites

A new version is available:

 

MIDIboxSEQ V4.072
~~~~~~~~~~~~~~~~~

   o support for the "single_usb" option, which can be enabled with the
     bootloader update application V1.012 ("set usb_single 1")

     Use this option if you are working with a Windows PC which can't handle
     the 4 USB ports correctly (e.g. stucking MIDI, Filebrowser operations are failing, etc.)

 

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Quick question: I am trying to set up a track to output to 2 sources, and can't figure out how. Here is what I am trying to do. I am using the ssm2044 board, and controlling it through the AOUT_NG connected to my seq v4. I would like one track to control both cuttoff's and another track to control both resonance's. So track 1 would route to AOUT ports 1 and 3, and track 2 would route to AOUT ports 2 and 4. Is this possible? I'm running a stereo source through the ssm2044 and would find it much less cumbersome to be able to control it with 2 tracks as opposed to 4... If this isn't a feature already, would it be possible to add in the future?

 

Cheers,

Alex

Share this post


Link to post
Share on other sites

In the next version I will add the possibility to access all channels from a single track via dedicated CCs

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Great, thanks!!

 

alex

Share this post


Link to post
Share on other sites

I much appreciate the MidiRouter "Track" Destination introduced in V4.071

 

however I slightly changed the code for my purpose so that the router sends incoming midi to the port and channel of the currently selected track:

 

@Line 91 of seq_midi_router.c

 

else if( n->dst_chn >= 18 ) { // Trk
        fwd_port = SEQ_CC_Get(SEQ_UI_VisibleTrackGet(), SEQ_CC_MIDI_PORT);
        fwd_package.chn = SEQ_CC_Get(SEQ_UI_VisibleTrackGet(), SEQ_CC_MIDI_CHANNEL);
      }

 

I didn't investigate the code very deeply, and thus I have no clue of any possible conflicts nor reliability... but up till now it works for me!!!

I'm no programmer, so I'm far from adding this as additional option instead of replacing.

Maybe you programming-goddess can add this option in the future...

 

btw: with the above code, the compiler gives a warning... do I have to declare the Type of SEQ_UI_VisibleTrackGet() in SEQ_CC_Get(........)?

Share this post


Link to post
Share on other sites

You've to #include <seq_ui.h> to get the declarations.

 

The change could lead to issues with Note On/Off if you hold a note and change the track.

However, the "Live Play" function is doing exactly the same - and it remembers the open Note On commands to avoid hanging notes. It can even apply effects! :smile:

Just select Utility->Live (GP#11) to configure this function.

 

So, actually there is no need for such a (redundant) enhancement.

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Okay...Thanks

I have to admit, that I'm far from knowing all the functions of the SEQ V4

that is because it is simply so unbelievable AWESOME :hyper:  ...and I feel like a kiddy turning notes on and off :hyper:

 

however the mentioned redundancy makes sense, to me at least:

While in Live mode I've finished with programming Sequences and want to play with 'em

But with this option it's possible to quickly play notes from a keyboard during programming of a sequence...

 

Maybe I still didn't understand live mode completely.... ? I took some time last evening in learning all the functions but stuck in the track-direction-menu-page twiddling around till late in the night :sleep:  FANTASTIC......

 

Since this weekend spring time and barbecue season will finally start... I guess it's time for spending a beer or two to you TK!  

Share this post


Link to post
Share on other sites

Ok, for the case that it's really useful for other people, the enhancement is now part of the official release.

 

MIDIboxSEQ V4.073
~~~~~~~~~~~~~~~~~

   o bugfix for "single_usb" option

   o the MIDI router provides the new destination "Sel.Trk"

     Usecase: MIDI events, such as CC or Notes, should be sent from a master keyboard
     or MIDI controller to the MIDI port and channel of the currently selected track.

 

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now