TK.

MIDIbox SEQ V4 Release + Feedback

1,425 posts in this topic

Great work TK!

I love your Update-Sundays :smile:

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

That´s indeed very usefull.

It improves workflow a lot beause

i don´t need to change the mapping of my master keyboard

if i want to play another instrument.

Perfect!

Have a nice evening!

Marxon

Share this post


Link to post
Share on other sites

Thorsten, thanks! Second improvement is great.

Share this post


Link to post
Share on other sites

Thanks goes to Daemonik - he added this feature! :)

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

It makes a boatload of sense to my workflow too.  I'm forever changing midi channels on the master keyboard (which takes a number of key presses)... Now I can just change tracks on the sequencer  :smile:

 

Excellent modification.

 

Cheers,

 

Arkay.

Edited by Arkay

Share this post


Link to post
Share on other sites

I was using Midipal with dispatcher app between keyboard and MbSEQ for fast channel switching. Now it's free for another good things =)

Share this post


Link to post
Share on other sites

Hi Midiboxers,

i could not figure out whats is the difference between

destination "track" and "sel. track".

Maybe someone can explain it to me?

Thanks a lot

Best regards

Marxon

EDIT:

RTFM! ;)

Now i know the difference...

Edited by Marxon

Share this post


Link to post
Share on other sites

Ooops, sunday again!

So it's time for the weekly release ;-)

 

MIDIboxSEQ V4.074
~~~~~~~~~~~~~~~~~

   o "SD Card connected" message not displayed after boot anymore, instead only 
     when the SD Card is exchanged

   o whenever the ALL function is active, you can now directly select the steps
     which should be modified with the GP buttons (LEDs will show the selection pattern)

   o the ALL function has been enhanced:
     - press & hold the ALL button and move the encoder of the already selected step
       (marked with >...<) to change all steps to the same value (like before)

     - if ALL button not pushed (but active), move the encoder of the already selected step
       (marked with >...<) to change all step values relatively (like before)

     - NEW: if ALL button is active (regardless if pushed or not), and the encoder
       of an unselected step is moved, the editor will generate a ramp between the
       selected step and the moved encoder.
       This feature has been borrowed from Sequentix Cirklon - thanks for the inspiration! :-)

     The "selected step" can either be changed with the datawheel, or it will be
     changed if the ALL function isn't active (as before)

 

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

I think I messed up something in my SeqV4 (STM32):

:sad:

 

A few days ago I succesfully uploaded from 4.065 to 4.074. I updated both the bootloader and the application and everything seemed fine.

 

But just tonight I noticed that none of the IIC Out ports were no longer seen by the Core. The "*" symbol appeared next to all 4 of them.

I thought that before opening the machine to look for a hardware fault, I would check that it wasn't caused by the newly uploaded version 4.074 of the application. So I uploaded 4.065 again and the IIC ports came back to life. So now I have my IIC ports working fine again, but MIOS Studio is reporting an error every time I try to upload the application or the bootloader. No matter which version I try to upload it all seems to start fine, the Seq LCD's show Bootloader mode for some seconds, but then it just reboots and MIOS Studio shows the message: "Upload aborted due to error #14: Invalid SysEx command"

 

Now I see that I probably did something silly and maybe Bootloader 1.012 + v4.065 is not a good combination.

This all happened using MIOS 2.4.4 on OS X 10.8.3

 

So I'd really like to know if there is a way to fix this and get the USB uploads working again or will I get stuck on 4.065 forever?

 

Thank you all very much!

 

And someone with 4.074 and IIC Out ports installed should check if they work. :smile:

Edited by vcfool

Share this post


Link to post
Share on other sites

When I ran into similar issues combining an older application with a newer bootloader, this helped me to fix it:

if you uploaded an old application by accident which isn't compatible to the new bootloader, you've two possibilities: either stuff the "Boot Hold" jumper J27 on your MBHP_CORE_STM32/MBHP_CORE_LPC17 module, reconnect the USB cable and reopen MIOS Studio to get direct access to the bootloader, or upload the application via traditional MIDI IN1/OUT1

taken from this thread:

I used the second option and it fixed it.

Share this post


Link to post
Share on other sites

Thank you so much!

I knew I did something stupid that I shouldn't have done.

 

MIDI uploading worked fine. I plugged my GM5 and upgraded to v4.074 successfully again. Nice.

:smile:

 

And now the 4x IIC_Outs are no longer recognised by the Core.

:sad:

Share this post


Link to post
Share on other sites
And now the 4x IIC_Outs are no longer recognised by the Core.

 

Fortunately I was able to reproduce this! :)

 

It happens due to a compiler change which generates faster code - too fast for the STM32 IIC driver!

Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_075_pre1.zip

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Hi,

i might have discovered a bug in V4.074.

In Phrase Mode, the sequencer always plays bar 1 of a certain track (not all the tracks) twice before moving on to the next bar.

So if a track has 4 bars, it plays bar 1-1-2-3-4-1-1-2-3-4-...

Weird

 

Is this a common problem?

 

Best Regards

Dijf

Share this post


Link to post
Share on other sites

Could you please enter "track 1" in the MIOS terminal, and post the output here?

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Hi,

 

I just tried the above v4.075pre1:

 

The Seq seems to find the IIC outs. No more "*" appears next to them and I can see the the IIC out activity on the MIDI Monitor page.

But still, there is no actual data coming out of the IIC Ports physical outputs.

 

Thanks again for the ultra-fast support!

Share this post


Link to post
Share on other sites
Hi, this is the result.
and oh yes, i discovered i still have OS 4.073..
 
[ 190.303] track 1
[ 190.305] Track Parameters of G1T1
[ 190.305] ========================
[ 190.306] ParInstruments 1
[ 190.306] ParLayers 8
[ 190.306] ParSteps 128
[ 190.306] TrgInstruments 1
[ 190.306] TrgLayers 8
[ 190.306] TrgSteps 128
[ 190.306] EventMode 0 (Note )
[ 190.306] #     |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |    |
[ 190.306] Name 'SynthP600                                                                       '
[ 190.306] TrackMode 1 (Normal)
[ 190.307] TrackModeFlags 3 (Unsorted: on, Hold: on, Restart: off, Force Scale: off, Sustain: off)
[ 190.307] MIDI_Port 0x20 (OUT1 )
[ 190.307] MIDI_Channel 0 (#1)
[ 190.307] DirectionMode 0 (Forward)
[ 190.307] StepsForward 0 (1 Steps)
[ 190.307] StepsJumpBack 0 (0 Steps)
[ 190.308] StepsReplay 0
[ 190.308] StepsRepeat 0 (0 times)
[ 190.308] StepsSkip 0 (0 Steps)
[ 190.308] StepsRepeatSkipInterval 3 (4 Steps)
[ 190.308] Clockdivider 15 (16/384 ppqn)
[ 190.308] Triplets 0 (no)
[ 190.308] SynchToMeasure 0 (no)
[ 190.308] Length 15 (16 Steps)
[ 190.308] Loop 0 (Step 1)
[ 190.308] TransposeSemitones 0 (+0)
[ 190.308] TransposeOctaves 0 (+0)
[ 190.309] MorphMode 0 (off)
[ 190.309] MorphDestinationRange 0 (1..16)
[ 190.309] HumanizeMode 0 (Note: off, Velocity: off, Length: off)
[ 190.309] HumanizeIntensity 0
[ 190.309] GrooveStyle 0
[ 190.309] GrooveIntensity 0
[ 190.309] TriggerAsngGate 1 (A)
[ 190.309] TriggerAsngAccent 2 (B)
[ 190.309] TriggerAsngRoll 3 ©
[ 190.309] TriggerAsngGlide 4 (D)
[ 190.309] TriggerAsgnSkip 5 (E)
[ 190.310] TriggerAsgnRandomGate 6 (F)
[ 190.310] TriggerAsgnRandomValue 7 (G)
[ 190.310] TriggerAsgnNoFx 8 (H)
[ 190.310] DrumParAsgnA 0 (None )
[ 190.310] DrumParAsgnB 0 (None )
[ 190.310] EchoRepeats 0
[ 190.310] EchoDelay 7 (  8 )
[ 190.310] EchoVelocity 15
[ 190.310] EchoFeedbackVelocity 15 (75
[ 190.310] EchoFeedbackNote 24 (+0)
[ 190.310] EchoFeedbackGatelength 20 (100
[ 190.310] EchoFeedbackTicks 20 (100
[ 190.311] LFO_Waveform 0 ( off )
[ 190.311] LFO_Amplitude 192 (64)
[ 190.311] LFO_Phase 0 (0
[ 190.311] LFO_Interval 15 (16 Steps)
[ 190.311] LFO_Reset_Interval 15 (16 Steps)
[ 190.311] LFO_Flags 0 (Oneshot: off, Note: off, Velocity: off, Length: off, CC: off)
[ 190.311] LFO_ExtraCC 0
[ 190.311] LFO_ExtraCC_Offset 64
[ 190.311] LFO_ExtraCC_PPQN 6 (96 ppqn)
[ 190.311] NoteLimitLower 0
[ 190.312] NoteLimitUpper 0
[ 190.312] # Parameter Layer Assignments:
[ 190.312] ConstArrayA 0x01 0x03 0x04 0x09 0x07 0x01 0x01 0x0b 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01
[ 190.312] # CC Assignments:
[ 190.313] ConstArrayB 0x01 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x1e
[ 190.313] # Constant Array C:
[ 190.313] ConstArrayC 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.313] # Parameter Layers:
[ 190.313] Par 0x000   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.313] Par 0x010   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.314] Par 0x020   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.315] Par 0x030   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.315] Par 0x040   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.315] Par 0x050   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.316] Par 0x060   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.316] Par 0x070   0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c 0x3c
[ 190.316] Par 0x080   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.317] Par 0x090   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.317] Par 0x0a0   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.318] Par 0x0b0   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.318] Par 0x0c0   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.318] Par 0x0d0   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.318] Par 0x0e0   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.319] Par 0x0f0   0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[ 190.319] Par 0x100   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.320] Par 0x110   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.320] Par 0x120   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.320] Par 0x130   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.321] Par 0x140   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.321] Par 0x150   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.322] Par 0x160   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.322] Par 0x170   0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47 0x47
[ 190.322] Par 0x180   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.323] Par 0x190   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.323] Par 0x1a0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.323] Par 0x1b0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.324] Par 0x1c0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.324] Par 0x1d0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.324] Par 0x1e0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.325] Par 0x1f0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.325] Par 0x200   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.326] Par 0x210   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.326] Par 0x220   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.326] Par 0x230   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.326] Par 0x240   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.327] Par 0x250   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.328] Par 0x260   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.328] Par 0x270   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.328] Par 0x280   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.328] Par 0x290   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.329] Par 0x2a0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.329] Par 0x2b0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.329] Par 0x2c0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.330] Par 0x2d0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.330] Par 0x2e0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.331] Par 0x2f0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.331] Par 0x300   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.331] Par 0x310   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.332] Par 0x320   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.332] Par 0x330   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.332] Par 0x340   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.333] Par 0x350   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.333] Par 0x360   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.334] Par 0x370   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.334] Par 0x380   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.334] Par 0x390   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.335] Par 0x3a0   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.335] Par 0x3b0   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.335] Par 0x3c0   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.336] Par 0x3d0   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.336] Par 0x3e0   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.336] Par 0x3f0   0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17 0x17
[ 190.337] # Trigger Layers:
[ 190.337] Trg 0x000   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.337] Trg 0x010   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.338] Trg 0x020   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.338] Trg 0x030   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.339] Trg 0x040   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.339] Trg 0x050   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.339] Trg 0x060   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.340] Trg 0x070   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.340] Trg 0x080   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.340] Trg 0x090   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.341] Trg 0x0a0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.341] Trg 0x0b0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.341] Trg 0x0c0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.342] Trg 0x0d0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.342] Trg 0x0e0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.342] Trg 0x0f0   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[ 190.343] done.
Edited by DIJF

Share this post


Link to post
Share on other sites

@DIJF: is this really the track which behaves faulty? Because it seems that it doesn't play any step...

 

@vcfool: could you please try this version:

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

 

It has been compiled with the "old" compiler version (official MIOS32 toolchain) - I've the impression that it works better than the newer gcc

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Yep, now it works.

I just made a quick test and the IIC Outs work nice with v4.075pre2.

 

Thanks again.

Share this post


Link to post
Share on other sites

Very nice! :)

 

So - V4.075 is officially released now:

MIDIboxSEQ V4.075
~~~~~~~~~~~~~~~~~

   o MBHP_IIC_MIDI working properly again on a STM32 core (issue was caused by a compiler change)

   o Track event configuration page: if a parameter layer is configured for CC,
     Pitchbender or Program Change, it's now possible to send the event manually
     by pressing one of the GP buttons below the controller configuration (GP10, 11, 12, 13)

   o MIDI remote keyboard function now also deactivated when Note On with velocity 0 received

 

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

So I know this may be asking too much but a feature I've been wanting a lot lately is a "flatten" function. Once I get something crazy going with the direction, length, etc parameters I often want to dub that down to another track. Essentially just being able to record one track to another would work fine for this, but having the ability to set a length and hit a button that just does it would be great.

 

Any thoughts?

 

Thanks,

 

Luke

Share this post


Link to post
Share on other sites

It could work this way:

- Export the track into a MIDI file.

- Import back from the MIDI file to another track

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Great idea! Ill try this tonight. Thanks

Share this post


Link to post
Share on other sites
It could work this way:

- Export the track into a MIDI file.

- Import back from the MIDI file to another track

 

Best Regards, Thorsten.

 

Gave this a shot last night and couldn't get it to work quite right. I don't see an option for selecting a track to import the file back into. It always imports to G1T1, even if  I have a different track selected when I do the import. Any ideas?

 

Thanks,

 

Luke

Share this post


Link to post
Share on other sites

You are right, the import function always starts at the first track (because it allows to import multiple tracks)

I've currently no elegant solution for this, because an optional single track import would require to overwork the import page.

 

I can do this sooner or later... but until then please use this (cumbersome) workaround:

- store your patterns (main page: press SAVE)

- export the track into a MIDI file

- import the MIDI file

- export track 1 again, but this time as a preset: MENU->EVENT, PRESETS (GP14), Save as new Preset (GP11)

- restore your patches (e.g. with OPEN in the main page)

- load the preset into any track from MENU->EVENT, PRESETS

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites
So I know this may be asking too much but a feature I've been wanting a lot lately is a "flatten" function. Once I get something crazy going with the direction, length, etc parameters I often want to dub that down to another track.
Personally I just copy tracks that I like and then modify the copies. I was wondering what your goal was with this? I'm interested what different outcome you were looking for that a copy wouldn't achieve.

TK, one thing that Luke's post got me thinking about: quite often I'm using a track which is set as an arpeggiator and play a certain set of keys that generate a great pattern. Problem is, next time I send any more MIDI to the track I lose that great pattern and can't remember or replay those last notes! Generally I always record the output of MBSeq because of this. I was wondering if there would be some way to address this in the sequencer itself? Maybe a way to grab the last set of notes the arpeggiator received and paste them into another track? Or to freeze an arpeggiator when you are happy with what it's generating?

Anyone else found ways around this?

Dave

Share this post


Link to post
Share on other sites

Thanks TK, I understand that it would be a pretty big change. Ill give the method you described a shot, and there is also always recording to another sequencer and back to the mb. 

 

Has the possibility of routing a track output to another tracks input ever come up? Is that at all possible?

 

Dave, copying really won't do what I want here. If you make a sequence that is an off number of notes and has some other modifications on it and have it play along something more rigid you will hear parts that really work well together and parts that really don't. The good parts are not always directly repeatable at least in an easy way.  If you record a long section of this you can pull the good parts out and sequence those as phrases. It's a great way to create variations. An easy way to try it is to record a long pass of this into your daw and then record it back to the midibox. 

 

Luke

Edited by lukas412

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