[slo]

Hey All, I'd like to report a successful build. I enjoyed building this great sequencer as it took me to new areas in DIY and I want to thank TK and Smash TV for the great service to the community. I used switches from Digikey, they stood above the PCB but still topped out @ 5mm. It worked first time with no problems from the documentation, except maybe the jumper section needs tweaking. Two things I noticed. #1 The tempo is global when in master mode and is applied to all patterns saved. Is this normal for a stand alone seq? can we have individual tempos saved with the pattern? #2 I see no easy way to delete a note from a track. Again thank you for a really fun project.

George

[TK.]

Great that you got it working first time!

Yes, it's normal that the tempo is not part of the pattern, because usually it would be disturbing if the tempo changes when you are switching to another pattern.
Is this really important? I'm sure that most users wouldn't like this option.

In order to delete a note of a track, just enter the Trigger page and disable the step.
The same can be done from the Step and Live Recording page.

Best Regards, Thorsten.

[loderbast]

i am really happy with my seq v4Lite.

there is one small feature i miss though.
it would be great to have a midi clock divider when in external sync mode.

could be choosen when holding down Master Button and choose divider with the GP buttons (1= normal, 2 = /2, 3= /3, ...) for example.
this would be great for slow chord progressions and stuff.

i have no idea about programming, but i imagine it would not eat up a lot of cpu and is relatively simple to implement.

please think about it, TK

edit:
it also could be saved globaly, like the tempo, so it would not interfere with the data structure of the patterns

This post has been edited by loderbast: 29 January 2012 - 17:37

[TK.]

MBSEQV4L is based on the MBSEQV4 firmware, accordingly all features which are described in the MBSEQ User Manual are available, but most of them are just not accessible... ;)

When you search for "clock divider", you will notice that such a function is already part of the firmware.
The parameters are stored in the patch structure, individual dividers can be selected for each sequence (resp. even for each track), and Triplet dividers are supported as well.

Making them accessible is a good idea, but I doubt that the double-usage of the Master button is practical, because you will toggle between Master/Slave mode whenever this button is pressed.
This means in other words, that your sequencer will switch to another tempo (or even stop if no MIDI clock is received) whenever you press the Master button to change the divider settings.

So, which button would be better suitable?
Or would you prefer to replace one button which normaly isn't used (like RecArm) by this function, configurable in the HWCFG file?
And which divider presets should be assigned to the 16 GP buttons?

Best Regards, Thorsten.

[loderbast]

nice, that it is already implemented.
i saw in the seq v4 manual it is even possible to make it faster than the master.

i think it is not the best sollution to have to change the config file.
maybe it is possible to do it this way:

use the tap tempo button (hold tap tempo + one of the 16 gp buttons) to set divider.

the seq v4l would recognize this as the first tap for tempo also, but this could be cancelled, as soon, as a gp button is pressed while tap tempo is hold down.

it might be usefull for some people, to also be able to use this to make it faster than the master, but having original tempo at gp1 would be the most induitive i guess. because with the fx (lfo etc.) it is the same thing (gp1 = off)

so i suggest:

gp1= original external tempo, gp2= *2, gp3 = *4, gp4 = /2, gp5 = /4, gp6 =/8, ...

[cit]

that sounds nice

[TK.]

MIDIbox SEQ V4L.056 is available:

MIDIboxSEQ V4L.056
~~~~~~~~~~~~~~~~~~

   o the step lengths (clock divider) can now be configured in new "Tempo" page
     (press Tempo button)
     Following step lengths are available:
     GP button 1..7: 64th, 32th, 16th (default), 8th, 4th, 2th, 1
     GP button 9..15: 64T, 32T, 16T, 8T, 4T, 2T, 1T (triplets)
     The tracks will be automatically re-synchronized to the measure on divider changes.

Best Regards, Thorsten.

[gomiboy99]

Thanks TK!
Another excellent update. The BPM and step display works too.

Tim..

[loderbast]

Awsome! thanks a lot TK.

[MikePig]

Hi,

Is it possible to set the note duration (gate length) in step recording mode ?

Regards

[TK.]

Yes!
The gate length will be determined with the note duration that you are playing.
Play the note(s) short: short gatelength
Play the note(s) long: long gatelength

It isn't possible to modify the gatelength from the user interface, but you can just record the step again with the desired gatelength.

Best Regards, Thorsten.

[ellocoyugo]

hello tk,

first a big thanx from berlin to your great diy project and the perfect instructions. i just finish my first soldering of my life, hoping that it will run...
well normally it would be time to put the processor on the lpc core17- but for any reason a friend of mine and me ordered the wrong processor at wattenrot- it´s a 1200 not the needed ..69.
shit happens...
now we have two processor in stock. my question is, what you can construct else of the midibox projects or can they be reused for anything else of your projects??
a big thanx in advance 4 some inspirations. of course the original processor is ordered, hehehe

[cd_reloaded]

Hello TK,
as you can imagine, I didn't have much time recently to make some music. After I came back from Lanzarote I did have a lot of things to do, like playing emergenca band contest, caring about my daughter and my new girlfriend and so on and so on.
Finally I found some time to test my SEQs. And here is a little bug report (FW 0.55): All of my three SEQs have the same symptoms: After a few minutes of playing the realtime-record-mode doesn't work anymore. You see notes beeing recorded and the next time the position indicator comes around the notes just get deleted instead of beeing played. With notes that are beeing recorded in step record mode that doesn't happen. When you switch into realtime-record-mode the recorded notes immideatley get deleted. Do you understand what I'm talking about? What could be the reason for that strange behaviour?

PS: I just updated all SEQs to 0.56 and that bug still exists.

This post has been edited by cd_reloaded: 25 February 2012 - 22:33

[TK.]

ellocoyugo, on 25 February 2012 - 19:54, said:

well normally it would be time to put the processor on the lpc core17- but for any reason a friend of mine and me ordered the wrong processor at wattenrot- it´s a 1200 not the needed ..69.
shit happens...
now we have two processor in stock. my question is, what you can construct else of the midibox projects or can they be reused for anything else of your projects??
a big thanx in advance 4 some inspirations. of course the original processor is ordered, hehehe

Unfortunately I don't see a way to run MIOS32 on LPC12xx based microcontrollers, because they only have 8k SRAM which isn't enough to run basic services.
There could be a way to hack an USB->MIDI interface, but again due to the small SRAM it wouldn't fit my personal robustness requirements. ;)
Maybe you are able to sell it on the (german) http://www.mikrocontroller.net/ forum

cd_reloaded, on 25 February 2012 - 21:26, said:

Hello TK,

Servus!

Quote

Finally I found some time to test my SEQs. And here is a little bug report (FW 0.55): All of my three SEQs have the same symptoms: After a few minutes of playing the realtime-record-mode doesn't work anymore. You see notes beeing recorded and the next time the position indicator comes around the notes just get deleted instead of beeing played. With notes that are beeing recorded in step record mode that doesn't happen. When you switch into realtime-record-mode the recorded notes immideatley get deleted. Do you understand what I'm talking about? What could be the reason for that strange behaviour?

I can't reproduce this. :-/
It could happen if an incoming note hangs (e.g. MIDI cable unplugged) - the note would erase all steps.
In order to check if this is true, could you please check if this also happens if another keyboard is connected (or if the MIDI cable of the keyboard is removed)?
If it doesn't happen anymore, we know into which direction the analysis has to be continued.

Best Regards, Thorsten.

[ellocoyugo]

hello tk,

thank u 4 the information.have a sunny day.

best regards
aco

[cd_reloaded]

Hello TK,
I tested and tested and I found out that this strange effect happens, when a lot of midi-information comes together. e.g. when recording controller events.
And I can imagine that your theory about the hanging Midi-Note couldbe the reason. My Jx3P and my DW8000 tend to have hanging notes from time to time.
I will keep on watching that.
Thanks
btw. I love the SEQs and there is a little chance that we play at the "Lange nacht der Musik" again. Its not sure yet, but maybe ....

This post has been edited by cd_reloaded: 27 February 2012 - 11:12

[cit]

hi christian,

i think you have an old firmware. or you have to switch the in-out funktion off!

[cd_reloaded]

cit, on 28 February 2012 - 19:57, said:

hi christian,

i think you have an old firmware. or you have to switch the in-out funktion off!

Hi Cit,
I use the latest FW-Version. Maybe I should try to switch it off. I will continue testing ...

[TK.]

You should have mentioned this special setup earlier!

The reason is clear: two MIDI IN ports are receiving more data than a single MIDI OUT port could sent, this results into a "bottleneck" problem.
A possible solution is to add a large, software based FIFO for the MIDI OUT ports.

I will add it this weekend, it was on the agenda anyhow

Best Regards, Thorsten.

[cd_reloaded]

FIFO =

This post has been edited by cd_reloaded: 02 March 2012 - 19:24