TK.

MIDIbox SEQ V4 Release + Feedback

1,470 posts in this topic

4 hours ago, TK. said:

New major enhancement available for MBSEQ V4+ users - up to 32 CV channels and gates! :-)

-> http://www.ucapps.de/mios32/midibox_seq_v4_096_pre6.zip


   o Only for MBSEQV4+: support for up to 32 CV outputs (and corresponding gates).
     Means: up to 4 AOUT modules can be chained.
     Tested with MAX525 (and midiphy Eurorack Expander), but should also work with TLV5630 based AOUT_NG
     The additional CV outputs can be accessed with MIDI port CV2..4.

   o AOUT port has been renamed to CV1..CV4

   o Utility Page, GP Button #11 now changes to the CV Configuration Page

Best Regards, Thorsten.

Wow, amazing! Are the CVs distributed out on J19, so the same RC1 channel or is RC2 used as well to double the transfer rate? What is the maximum data rate?

Is there a functional way to use all 32 CVs with only 16 tracks? Polyphonic tracks?

While you are in the code, maybe an extra request from Andrew:

http://midibox.org/forums/topic/21161-trigger-outs-4ms/#comment-184712

 

Is it possible to set (or preset) the drum trigger length to something longer? This is already available for the clocks but I couldn't see an easy way to do it for triggers.

 

 

4 hours ago, TK. said:

still relevant or just a quick idea?
Will lead to some effort at my side... therefore I would only add this if other people find it useful as well

Best Regards, Thorsten.

I find the proposal too cryptic. It would IMO be more intuitive to display more information on the FX page/menu.

Share this post


Link to post
Share on other sites
4 minutes ago, latigid on said:

Wow, amazing! Are the CVs distributed out on J19, so the same RC1 channel or is RC2 used as well to double the transfer rate? What is the maximum data rate?

The data update rate is only 35 uS for all 4 modules, so no need to make it more complicated :)
That's also the reason why I enabled all 32 channels by default, it doesn't make a big difference.
Using a second CS line wouldn't help, because SPI transfer time would have to be consumed anyhow.
 

Quote

Is there a functional way to use all 32 CVs with only 16 tracks? Polyphonic tracks?

With channel 9-13 you can route note and velocity value to two CV outs - in this case you need all 32 outputs.
But you can also route CCs of a track to the CV outs (starting at CC#16 as far as I remember...)

Quote

Is it possible to set (or preset) the drum trigger length to something longer? This is already available for the clocks but I couldn't see an easy way to do it for triggers.

Actually I looked into this, but there is a technical problem.
The 64 drum triggers are currently cleared with each SRIO update cycle, this was very pragmatic and effective and especially doesn't consume resources (counters) and CPU time (processing the counters)

For individual delays I would have to implement counters for each trigger, and this is very costly.

And for a single delay we would potentially run into the problem, that each mS a new trigger could reset the counter, leading to "stretched signals" for all triggers for which the configured time already passed...

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Update to the 1ms delay: I could "pipeline" the triggers, this way we could get a cheap pulse stretcher.

Is there the need for more than 4 mS (= 3 pipeline stages)?

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Thanks for the clarification on the CV channels. I could see a usecase for four modules if the velocity function was added, which I didn't remember BTW! This could add some expression, e.g. as a mod source mixed into a VCA -- great! And the accent trigger on the spare gates is awesome.

For the drum triggers, I figured it was a code issue, as the clocks are easy to calculate in advance. In the meantime I think Andrew implemented a pulse stretcher in hardware, but if it is not too much effort I'm sure more software flexibility would be welcomed. Besides, we have the option of the standard trigger length, which I guess is one "step" long?

Best,
Andy

 

Share this post


Link to post
Share on other sites

Based on my experiences with MB808 the trigger width is crucial, therefore I can fully understand Andrews request that a digital option is desired.

The "pipeline based approach" is working fine, we can now adjust the width from 0 (=off -> gate function) to 10 mS

   o DOUT_1MS_TRIGGER in the MBSEQ_HW.V4 file has been replaced by a configurable trigger width which
     can be adjusted in the CV Configuration Page with GP13 now

-> http://www.ucapps.de/mios32/midibox_seq_v4_096_pre7.zip

It would be great if everybody could help to test this new firmware version, regardless if the new CV features are used or not (I hope that nothing else is broken!)

I would like to create a final v4_096 release, because v4_095 is from last december, and it started to smell! ;-)

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

hello everyone

 

testing new release ,all works great!

 

two suggestions:

could DIVIDER be on a separate button?for example like MIXER.

and could SOLO function mute also all other LFO's?

 

kind regards

 Kaz

Share this post


Link to post
Share on other sites

Hey Everyone, 

I'd love to be able to sequence the modes of the harmonic/melodic minor scale a little easier. Just as the modes of the major scale are numbered from cc12-18, it would be great if the modes of the melodic minor, harmonic minor or even harmonic major were listed consecutively. I'm often befuddled trying to find these scales in the scale list. 

Harmonic Minor Modes:

Melodic Minor Modes:

Harmonic Major Modes:

Thoughts?

please and thank you! legends!

 

Share this post


Link to post
Share on other sites

I'm just trying to compile the git master. It fails:

project_build/core/seq_cv.o: In function `SEQ_CV_IfSet':
D:\Temp\midibox_seq_v4/core/seq_cv.c:154: undefined reference to `AOUT_IF_MaxChannelsGet'
collect2.exe: error: ld returned 1 exit status
make: *** [project_build/project.elf] Error 1

Did I miss something? I'm compiling for LPC1769 / Midibox v4.

EDIT: Sorry, I forgot to switch to the new MIOS32_PATH for my environment variable. Everything is fine.

Best regards,

rio

Edited by Rio

Share this post


Link to post
Share on other sites
On 14/09/2019 at 8:58 PM, TK. said:

-> http://www.ucapps.de/mios32/midibox_seq_v4_096_pre7.zip

It would be great if everybody could help to test this new firmware version, regardless if the new CV features are used or not (I hope that nothing else is broken!)

I've just had a chance to test this with 2 x AOUT_NG boards and I think I've came across a bug.

The shift register that is assigned to CV_GATE_SR2  in the HWCONFIG file will only trigger once and then remains on. 

I thought I had a hardware problem initially but after some trouble shooting I'm pretty confident its a software problem, either user error or a bug. The reason this is that I swapped the CV_GATE_SR assignment for SR1 and SR2 in the hardware and the problem is always present Shift Register assigned to CV_GATE_SR2.

Both of the AOUT_NG boards are working correctly.

Share this post


Link to post
Share on other sites
On 22/9/2017 at 8:51 AM, eptheca said:

I have a BLM 16x4 connected to my SEQ V4.

Would it be possible that on Drum tracks each drum instrument had its own track showing and that it was possible to jump to the next 4+4+4 instruments with the up&down buttons for example. I think this would be great for editing the drums.

If I understand it correctly, this is possible with the BLM 16x16+X ?

Cheers, Hal

 

HI,
I was wondering if this function would be possible, to be able to have the different drum tracks displayed at the same time
on the 16x4 BLM. This would make it possible to see and edit BD, SD and HiHats side by side and would be great a great addition.

Best
Frank

Share this post


Link to post
Share on other sites

Hello, I hope that I am posting in the right place (my first post in the forum!). I am having a blast with the midibox seq4 but I would like to submit my humble request for what would be such a fun feature: implement scala microtonal .tun support to relay by some wizardry to my synthesizers! Thank you!

Share this post


Link to post
Share on other sites

dear Midi Maniacs

just little idea

in FX Panel one page with ECHO on/off (toggle or momentary) as buttons and lets say ECHO time or repeats as potis for each channel

 

hope you like it

bests

  Kazik

Share this post


Link to post
Share on other sites

Hi,

I posted this in the Midiphy SEQ V4+ troubleshooting thread but after a bit of conversation, it seems the topic is better suited to this feedback thread, as it could be bug related. 

Original post for more details: 

Basically I've come across a couple issues:

1)  When removing the SD card while the SEQ V4+ is powered on, all of my push buttons become unmapped, losing matrix assignments, although the encoder turns do remain mapped. Since the MBSEQ_HW.V4 file is not reloaded upon SD re-insertion (according to the MBSEQ_HW.V4 section of the user manual at: http://www.ucapps.de/midibox_seq_manual_in.html), the push buttons remain unmapped and unusable until I reload the release package midiphy_rh MBSEQ_HW.V4 with MIOS Studio, issue reset command with MIOS Studio, or power cycle the SEQ V4+ with the SD Card installed.

 

2)  Exporting songs, tracks, groups, or patterns to .MID files (Utility -> Disk -> MIDI Files -> Export) causes a Hard Fault. Pretty much anything I try to export results in either a Hard Fault with an address such as "PC=0x08049b0c" or "08049b5e", or the unit will just freeze with the "Exporting G_T_ to /MIDI/___.MID" notification on the OLED screen. This requires a hard power cycle on the V4+. I provided an example session with basic generic patterns I whipped up, but the crash/freezing happens with any session, large, small, or freshly created. 

 

I guess I'm just curious if these two things happen to anyone else with a standard issue Midiphy RH V4+ w/VGT6 chip, or if it is specific to my build. 

Everything else seems to be working great.

 

MIOS Studio query data:

Operating System: MIOS32

Board: MBHP_CORE_STM32F4

Core Family: STM32F4xx

Chip ID: 0x10076413

Serial: #1D0027001851373337323532

Flash Memory Size: 1048576 bytes

RAM Size: 196608 bytes

MIDIbox SEQ V4+.095

(C) 2018 T. Klose

 

Thanks to everyone for their support and welcoming comments. I'm new to the Midbox forum and the Midibox universe, in general.

Example.zip

 

 

Share this post


Link to post
Share on other sites

Hi @TK.

I am having a blast with the Midibox and the cv expansion eurorack boards made by Midiphy. I was trying to get lfo working on a cv channel but it seems this can't be done at the moment? @Hawkeye had a check at the code and it seems that the current lfo is note based per step and can't be used for a lfo out to a cv channel i a nice flowing way. If this is possible i would really love to have this to get more fun with lfo's and CV to my eurorack in the future.
Maybe i am doing somehting wrong and it already can be done but at the moment i am scratching my head :)

Cheers,

Niels

 

 

Share this post


Link to post
Share on other sites

@lp1977thanks for the information! Problems are understood and fixed in:

http://www.ucapps.de/mios32/midibox_seq_v4_096_pre8.zip

@sis.tmjust tried at my side, it works!
(and sometimes I'm surprised what can be done without special consideration in the sources ;-)

  • assign track to CV
  • in LFO page, set the ExtraCC# to 16..23
    16 will send to CV channel #1, 17 to channel #2, etc - which means: with the CC number you can address the CV channel you would like to use as LFO output

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Yeah working perfect @TK. ;-) thanks for the tip, this makes my setup even more complete.

Cheers

Niels

Share this post


Link to post
Share on other sites

Thanks @TK.! That was a quick fix.

 

Question: Does/can the Midi Song Export honor the "Restart all Tracks on Pattern Change"? (Utility -> Options -> 5/33 -> enable)

If I do not enable this, in Song mode, the tracks with patterns that have random Step direction fall out of step alignment on the next change to a pattern with a Forward direction, for example,  since it just continues on to the next step after the last randomly chosen step from the previous pattern. 

Enabling it fixes the issue in Song mode, making all the tracks start at Step 1 on the next pattern, but I don't think this is reflected in the Midi Export.

Thanks!

Share this post


Link to post
Share on other sites

Thanks, @TK..  I exported with the option enabled and then again with it disabled and the state was accurately reflected each time in the output of the midi export. 

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