[MIDIbox SEQ V4 Release + Feedback]

Hi there,

sorry to ask this, but i am absolutely uncetain about this:

Is it possible to have one of this neat little USB midi Keybords (e.G. Korg microKEY 25) directly connected to the SEQ V4?? via USB or has a PC to be inbetween??

Thanks

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

As long as only a single value should be handled this way, I could add this to the firmware without much effort.

But once you want to change multiple values (also triggers) and take over them by releasing the EDIT button, the effort would be too high.

Your choice? ;)

Best Regards, Thorsten.

Hi, I was just thinking of one single value for only one step

and if it would only work for note and chord number it would be sufficient for me, that would avoild "disharmonics" during editing

I think an editbuffer for serveral values would be some overkill

Happy to hear that it would be not much effort and Thanks a lot if you could add it :-)

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

HI,

I am already curious about the next features :smile:

and i also have one in mind, may be you like it, and perhaps it is feasible:

I guess it would be nice if a parameter change with a GP encoder in edit mode would

NOT be applied immediately AS LONG as you hold the edit (or slect?) button depressed.

By this way you would not hear the scrolling through the note values during live editing if desired.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Sorry to report, but it seems that with V52 the MIDI in ports of the STM32 Core are not longer working:

-MIDI Messages will not be recognized recorded or forwarded by the SEQ

-No respond to the query Function of MIOS Studio when connected over MIDI

Turning back to V51 -> everything works perfect again.

by the way, i get the following error Message in MIOS Studio after upload:

[1505.753] Init DHCP

[1508.934] [sEQ_FILE_HW] ERROR: no space separator in following line:

[1509.064] Init DHCP

But I guess it has nothing to do with the Problem as I get the message als with V51 which causes no problems with the MIDI ins

Best Regards

Gridracer

[Alternative USB MIDI Driver for WINDOWS 7 64bit]

Btw.: which bootloader version are you currently using - was the "error code 10" also reported by older versions, or is this a new issue?

the problem occured the first time with mios32_bootloader_v1_005 but I installed midibox_seq_v4_047 successfull with it. But that was in one run after insatlling the new bootloader without

disconnecting my box or shutting down MIOS_Studio_2_2_2.

I noticed the problem when I wanted to update to mios32_bootloader_v1_006 and midibox_seq_v4_048

which I now run after upload via MIDI but the ERROR 10 Problem remained also with this version.

Only the KORG driver helped, i hope it is not just temporal.

Best Regards

Gridracer

[Alternative USB MIDI Driver for WINDOWS 7 64bit]

Just wanted to report how I solved the problem that my Win7 64itb PC suddenly did no longer recognize my MIDIbox SEQ (stm32) propperly:

When connecting my SEQ via USB for SW upload my PC displayed in the device manager that the device is not working propperly (error code 10)

And as a result I could no longer select my box in MIOS Studio.

All de and reinstallisation and change of the USB ports had no succes.

What did the Job for me was the following:

1. I downloaded this driver from KORG:

PC: KorgUSB-MIDI_DRV_PC_1_13r6.zip (2.2MB)

LINK

2. I installed the package (to have access to the files)

3. Then i started the device manager and manually changed the driver for my midibox by choosing the "KORGUM64.INF" file from the Installation folder of the

Korg package as driver file and then choosing "KORG MIDI Device" as device

4. Then i started MIOS studio which now displayed ports a,b,c,d where i chose a for midi in and out

5. :twitch: now it works again and even the query function can now be called unlimited times without getting stuck

Which had to be solved by typing "help" in the command line severeal times to get the core to respond again when using the generic windows driver

I have no clue if this Fix works only specific for my PC but this might be a hint for others with similar problems.

Best regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Yuhu, beyond BETA! Just updated MIOS Studio, bootloader and application everything worked excellent!

Thanks!

And now its time to do some "testing" ;-)

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Thanks for the hint nuke,

sounds like "sync to measure" is activated...i still have v43 installed, so can´t proove...

but sync is not activated.

edit: or maybe "global loop" is on?

I am talking about the global loop function which is not working propperly with other progressions than forward.

I use the mode "Selected Track/Step View"

Best regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Hi, I noticed some minor issues:

1.

The LOOP function seems to mess up the PROGRESSION:

FORWARD -> everything OK

BACKWARD -> only OK if tracklength <17, otherwise only step 1-16 will be played when LOOP is activated regardless of Tracklength (direction OK it plays backwards)

PINGPONG+PENDULUM -> does not work at all with LOOP only step 1-16 will be played when LOOP is activated regardless of Tracklengt (even direction is wrong, it plays forward)

RANDOM directions -> only OK if tracklength <17, otherwise only step 1-16 will be played when LOOP is activated regardless of Tracklength (direction OK it plays randomly)

2.

Regarding the EDIT screen on a CHORD Track:

The PARAMETER LAYER "CHORD" displays the Chords as expected, but the PARAMETER LAYER "VELOCITY" displays a note Value instead:

Example: Layer CHORD shows "G/3" on a step, switching to VELOCITY "C-3" is displayed

Not sure if this is Intension? Are those the root notes of the chords?

3.

The SCRUB function causes the stopped sequencer to start, this makes it impossible to use this Function to scroll through ones own track to find this damn one wrong note for example ;-)

Best regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Wow, still impressed by the speed of your support :-)

Thank You!

Best regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Hi there,

I had to recognize that i am not able to open sessions anymore with BETA43:

If I try to open a session I always get the message "Changed to session xxx"

xxx is the session that was opend last under BETA42 regardles what session i try to open.

So I am stuck with the Session i last worked on with BETA42.

When I change back to Beta 42 everything works well again.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Hi TK,

it seems that "midibox_seq_v4_0beta43.zip" contains the old hex file for Beta42.

(at least for STM32)

Best regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Just gut to go updating to Beta 42 :)

But first i will have a closer look on the copy function.

View PostGridracer, on 30 May 2011 - 23:53, said:

and on the Copy function the selection, of the lowest step to copy, by use of the leftmost encoder does not work.

Instead the leftmost encoder affetcts the highest step to copy what the rightmost encoder should do, and still does.

Sorry, I wasn't able to reproduce this

After having a closer look on the misbehaviour of the copy function,

I noticed that the failure only occures under certain circumstances:

(Condition A, B and C have to be fulfilled)

A. Track length has to be longer than 16. (other track configuration parameters seem to have no influence)

B. The position indicators of the highest and lowest step to copy have to be

on different step views eg.: <13>-<24>

(if both indicators are on the same step view everything works fine eg.: <17>-<24>)

C. Finally but most important: The highest step to copy has to be changed once before the selection routine of the

lowest step starts to mess up.

(so if you always set up the lowest step to copy first before you ever change the

highest setp to copy, the effect will never show up)

So her a cenario to provoke the bug:

1. Have a track with Length=32

2. Call copy function (steps to copy should be initially 1-32)

3. Change the highest step to copy from 32 to a value higher than 16: 24eg.

4. Try to change the lowest step to copy-> the leftmost encoder will

change the highest step to copy instead of the lowest.

Hope you can reproduce it now.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

I will add mutes for these parameter layer assignments as well, shouldn't be a big task, and it seems to be useful

:) :)

in the meantime i noticed an issue with the Move and Copy function:

They will work only correct on Step View 1-16

Beyond Step 16 Move wont do anything at all,

and on the Copy function the selection, of the lowest step to copy, by use of the leftmost encoder does not work.

Instead the leftmost encoder affetcts the highest step to copy what the rightmost encoder should do, and still does.

Hope my description is not too confusing.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

HI,

just while messing around with the different parameter layers and having great fun, i noticed that not all of them are mutebale

like Note and Pitch are, would it be possible to have also Prob,Delay,Roll,and Roll2 mutable??

Would add some flexibility and be a quiet obvious thing i guess.

Here I am not so sure about, just a proposal for discussion:

I could even think of having the Velocity and Length layer mutable causing the Track to play with the default values of an initialized Track.

And if you think even further, What about having the Trigger Layers mutable? Perhaps by toggling between the

Parameter Layer mute screen and a new Trigger Layer mute screen by using the Select button (while you hold the Mute button depressed)

But all of this options (regardless of technical feasable)or not could make Mute handling too complex and confusing, but on the other hand

there would be no need to use them and handling would be just the same as it is now.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

....Beta42.... already curious about it, now doubt that it will be exceeding expectations ... :-)

But the reason for my post is something different,I would like to propose a littel but i think useful improovement on the Delay function:

Would it be possible without too much effort to have also a delaytime of "0" ? by this we would get someting like the "Harmonize" function of the RM1X and RS7K Sequencer for free.

If you wold use it with an note offset.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

I'm also with 8 global views, 8 session specific views,

my personal preference would be 1-8 global and 9-16 session specific.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Very nice !! :)

Now it's time to configure my private bookmark file!

I'm already done:

MY_BM.txt

[MIDIbox SEQ V4 Release + Feedback]

How about 16 memory slots to store the current UI settings

I really like this idea not becaus that I feel the need for it , but for a different reason:

SEQV4 has become a very very powerful tool, with increadible possibilities but also the complexity and the number and depth of

the menue pages has grown compared to SEQV3.

So I could think of the 16 UI Slots or snapshots as some kind of a cutomized "MENU" menu

which allows everyone to have his favorite pages just a GP Buttun push away.

I would remark that it wold be necessary to be able to name the different slots, due to my sieve like memory.

Perhaps by editing the corresponding .V4 file, no need to edit that on the box itsself for me.

And a second thing that I would like to propose is that I think it wold be useful to be able to decide if a Slot

contains the information which group and Track was selected or not.

I think it could be done by a configuration Parameter on the options page,

or by a flag in the config file, or simply by the fact that Slots 1-8 wont store this data and slot 9-17 will eg.

Hope this feedback helps a little.

display shouldn't automatically go back to the trigger view after 2 seconds anymore

:) Thanks for that.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Not a Bug this time I guess, but a short change request

regarding the parameter layer view of the roll parameter on drum tracks:

Is it a special intention that the roll values are only displayed for a few seconds before the

display switches back to show the triggers although the roll parameter layer is still selected??

Too much for me to remember ;-)

I would personally prefere it to work the same like on note tracks,

where the roll values stay on dispaly untill a different parameter layer is selected.

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Hi there, i did not notice anything unexpected since quite a while seems it's getting closer to "final" release ;-)

But yesterday i recognized that something little is wrong with the "move" function:

As long as tracklength is </=16 everything is ok, but when you move a step from one stepview to another something funny happens.

If you move the step forward a new step is created on the first step of the new step view e.g. 17 and the "cursor" position jumps to the eighth

step position of the new step view. If you move the step backward a new step is created on the last step of the new step view e.g. 16, the "cursor" position does not jump.

Hope i could explain it properly.

Best regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Great fun those "dotted delays" and the Export function comes really handy!

But could it be possible that the "store as" function in the sessions menu doesnt work any more since at least beta 31?

Or am I just messing up something?

When I enter a new name for the current session and press store, I get the message that all four patterns are stored,

but they are stored to the current sesion and no new session is created.

(Creating a new session or storing the current session with the according function still works fine)

Best regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

Oh shame on me, BETA 28 is working perfectly, but not my memory as it seems:

I just messed up to remind the correct assignment of the relative and absolute mode according to holding or not holding the button depressed....

So I was holding the All Button depressed and expecting the values to change relative and vice versa argh..

and so i also managed to write values to unset steps which suprised me later when setting their gate,

which lead me to think that this was caused when i used the ALL function on a different layer.

At the end, all just a simple user faiure.

I schould have checked before posting, sorry therefore

Best Regards

Gridracer

[MIDIbox SEQ V4 Release + Feedback]

o if the track plays multiple notes, gate is only cleared if

all notes are set to "---"

Tahnks a lot! Messing around with multiple note layers is real fun :-)

But sorry, just cant stop nagging:

I noticed that the All Button does no longer work relative when keeping it depressed and turning one encoder,

it now works always absolute. Ist there a reason for this nice feature being skipped?

And one proposal for the behaviour of the all button when several layers are assigned to NOTE:

It would be nice if the ALL function would only affect the currently selected layer and not all layers at once.

Best Regards,

always nagging Gridracer ;-)

[MIDIbox SEQ V4 Release + Feedback]

Hi,

I would like to propose some improvement of the handling in the case when you have assigned more than one layer to"NOTE":

At the moment, when you have assigened several layers to "Note"

and you have assigend note numbers on the same step on those layers,

(Which is really great for programming chords)

it occures that when you decrease the note number on ONE layer to "___" in order to deactivate that note,

the WHOLE STEP will be deactivated, with all the remaining notes on the other layers.

Ok, you can bring them back in by turning the encoder forth and back one dent on those layers.

But it would be really nice if the step would stay activated as long as ANY Layer contains a valid (note) value.

That would be a great wish from my side as i use multiple note layers a lot :)

Finally just to mention I noticed a cosmetic thing (may be already solved in beta 20+)

-For "probability" the encoder works inverted: CW increases, CCW decreases values

Best Regards

Gridracer