[TK.]

Beta28 is available now; ChangeLog:

  o fixed bug in session load function which happened when no MBSEQ_GC.V4 file exists on SD Card

  o added new "udpmon <0..4>" terminal command which allows to monitor incoming and outgoing
    UDP packets, e.g. to debug OSC settings and/or to determine the port of incoming OSC
    packets.
    In MIOS Terminal, use "udpmon 3" to display all packets with port number >= 1024

  o now we have a special CV configuration page which allows:
    - to select V/Oct, Hz/V and Inverse curve for each CV channel
    - the slew rate 0..255 mV for each CV channel
    - the pitch range (for pitchbend events)
    - the gate polarity for each CV channel
    - to calibrate each channel
    - to set the DIN Sync Clock PPQN Divider and Pulse Width
    - AOUT Module Type (previously hard-configured in MBSEQ_HW.V4 file)

  o each CV channel has now an own notestack.
    This is especially nice if AOUT channels are controlled through the MIDI Router
    from an external MIDI keyboard (live)

Grizz: it would be very interesting if your AOUT_NG module is working with the new version, as I changed the interface timings to make transfers more robust.

Go to the new CV Configuration page and select AOUT_NG (rightmost item)
The new calibration feature will help you to explicitely set certain voltages for testing.
It's now also possible to re-connect the module during runtime.
Whenever you are doing this, select a different interface, and go back to AOUT_NG - this will re-initialize the chip

Best Regards, Thorsten.

[Gridracer]

Quote

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 ;-)

[TK.]

Welcome back!

Gridracer, on 10 October 2010 - 21:14, said:

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?

No, it neither has been skipped, nor it has been changed.
Could you please check that the BUTTON_BEH_ALL variable is set to 1 in your MBSEQ_HW.V4 file?

BUTTON_BEH_ALL          1

Quote

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.

it only affects the currently selected layer as expected/suggested.

Could you please describe me how I can reproduce this misbehavior with a freshly initialized track?
If it only happens with one of your already existing tracks, could you please export the track to a preset file and attach it to this thread?

Best Regards, Thorsten.

[Gridracer]

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

This post has been edited by Gridracer: 11 October 2010 - 18:07

[grizz]

TK, I just noticed that v28 is released so i will work on uploading it and testing it out with my AOUT_NG tonight.

I tested my SEQ and AOUT_NG with my bandmates setup this weekend.

Results: His AOUT_NG works just fine with my MBSEQ, and mine does not work with his. This would lead one to believe that my AOUT_NG does not work at all, and is the culprit. The weird thing is that my AOUT_NG DOES work with my MB6582. Hmmm.... Are there maybe some pins on the AOUT_NG that are just used with MBSEQ? Could it be possible that I have a bad solder joint (maybe on the surface mount chip on the AOUT_NG) that matters with MBSEQ and not MB6582?

Cheers,
grizz

[TK.]

Gridracer.Karma -= 1;
Just kidding! You can still feel welcomed for reporting any anomaly that you noticed, you found a lot of issues in the past!

Grizz: I'm still puzzled about your issue and don't have an answer. There is neither an additional pin, nor something else which would be special.
I know that you already checked the SPI connections... so, everything should be fine.

On the other hand I improved the initialisation part of the AOUT driver that is integrated into MBSEQ.
It should work more robust now - therefore it will be interesting if this already solves your issue.

Best Regards, Thorsten.

[grizz]

Um.... I'm so sorry for the dumbness on my part, but I can't find the CV config page... Can someone give me the button combos that will take me to it?

Cheers,
grizz

[TK.]

Press the MENUEXIT button and scroll with the datawheel to the end of the list.
CV Configuration is the page before the ethernet configuration.
There is no special button combination available to enter this page.

Best Regards, Thorsten.

[grizz]

Hmmmm.... If I press "Menu" and turn the datawheel either way nothing happens. It seems there aren't any other pages other than the ones on the screen. My datawheel definitely works... Is there a setting in the config file?

Nevermind... I found it

This post has been edited by grizz: 12 October 2010 - 16:27

[grizz]

... So I tried different settings with my AOUT_NG, but no luck. I did verify that it does work still with my MB6582... Weird. I went ahead and ordered a new AOUT_NG from Smash... hopefully that will be the solution...

cheers,
grizz

[nuke]

hi there...after upgrading i´m now also with the MBSEQv4 ...yippie....some great improvement here must say, wow...great job!!
beside some problems with my SDcard thing it´s all working really well...

but...
after a while fiddling around and exploring i think i found two bugs...
1. i discovered the exclude from "All" function when pressing "select" ...it works so far but not on the first step, is that right?

2. when using glides or long notes on a monophonic track and also accent, it seems that accented notes are ignored on the longer steps or on steps with glide on...

and a suggestion...maybe it would be nice to have also a dotted quantization in the FX Echo part...
like 16, 16t, 16d, 8, 8t , 8d...? what do you think?

[TK.]

Welcome to the club!

nuke, on 20 October 2010 - 10:51, said:

1. i discovered the exclude from "All" function when pressing "select" ...it works so far but not on the first step, is that right?

I will check this soon

Quote

2. when using glides or long notes on a monophonic track and also accent, it seems that accented notes are ignored on the longer steps or on steps with glide on...

Thats related to the MIDI protocol. It isn't possible to change the velocity while holding a note (for glide) w/o retriggering the gate!

Quote

and a suggestion...maybe it would be nice to have also a dotted quantization in the FX Echo part...
like 16, 16t, 16d, 8, 8t , 8d...? what do you think?

Unfortunately your request comes too late - the values are hardcoded, a change would make all existing patterns incompatible for all users.

Best Regards, Thorsten.

[nuke]

TK., on 20 October 2010 - 23:21, said:

Thats related to the MIDI protocol. It isn't possible to change the velocity while holding a note (for glide) w/o retriggering the gate!

yeah right...but it should work on the first note then, or?...ok i found out : when having long notes or binded notes and the velocity on the first note (which is held then) is high, it works as normal....but when using accent (which is full vel. imo ) its ignored...just use a note with a long gate and put accent on instead of using high velocity values and see the difference...
;)

Quote

Unfortunately your request comes too late - the values are hardcoded, a change would make all existing patterns incompatible for all users.

mm...sad...ok i was late ...hehe, so no possibility to add them after rnd and rnd2 either?

This post has been edited by nuke: 21 October 2010 - 12:06

[Echopraxia]

I have not had a chance to update to beta 28 yet.

I was using a midi keyboard controller going to the midi in of the seqv4 and had a question.

Right now, to pick which midi out port and channel for the seq to respond to the keyboard, you use the midi router correct? Is there a way that we can have another option that would be on/off selectable that can change the midi router to what ever track 1-16 is selected? I was using one keyboard and was using the live record feature and thought it would be very productive to be able to just select the track you want and have the keyboard automatically get routed to that midi out port and channel so you can quickly record to several tracks one after another without having to go into the midi router each time to hear the corresponding track while in live record mode. Is this workable?

Also can more than one keyboard controller get connected by way of another midi in on the seqv4? Its limited to 2 ins right now yes? I guess you could always get a midi merge box and merge several keyboards upto 16 for one midi in I would probably use 2 maybe 3 keyboards at most to do appregiators on one,keys on another and samples on another. 16 would be crazy though and I bet someone will try it. Can the seqv4 and midi router handle this ammount of input on top of a master midi clock at the other midi input?

regards

This post has been edited by Echopraxia: 21 October 2010 - 18:09

[vcfool]

Echopraxia, on 21 October 2010 - 18:06, said:

I have not had a chance to update to beta 28 yet.

I was using a midi keyboard controller going to the midi in of the seqv4 and had a question.

Right now, to pick which midi out port and channel for the seq to respond to the keyboard, you use the midi router correct? Is there a way that we can have another option that would be on/off selectable that can change the midi router to what ever track 1-16 is selected? I was using one keyboard and was using the live record feature and thought it would be very productive to be able to just select the track you want and have the keyboard automatically get routed to that midi out port and channel so you can quickly record to several tracks one after another without having to go into the midi router each time to hear the corresponding track while in live record mode. Is this workable?

This is already implemented:

-Go to MIDI -> Transposer and Arp.
-Select 1 Bus and choose the right Port/Chn/Range.
-On "Mode" select "Play".

Echopraxia, on 21 October 2010 - 18:06, said:

Also can more than one keyboard controller get connected by way of another midi in on the seqv4? Its limited to 2 ins right now yes? I guess you could always get a midi merge box and merge several keyboards upto 16 for one midi in I would probably use 2 maybe 3 keyboards at most to do appregiators on one,keys on another and samples on another. 16 would be crazy though and I bet someone will try it. Can the seqv4 and midi router handle this ammount of input on top of a master midi clock at the other midi input?

regards

Not sure I completely understand you... There is a 3rd MIDI In/Out on the Core for the BLM now. But you can use it as a normal MIDI port. I have 2 keyboards and 1 sequencer connected to the MIDI INs of the MB-SEQ v4. Using all 3 Core inputs without any problem.

Hope this helps.

This post has been edited by vcfool: 21 October 2010 - 18:30

[mastomo]

Hello everyone,

Quote

Wishlist for future features
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

add a possibility to copy patterns from one to another session

that is great !

another subject,
there is something that seems weird to me :
about song mode.
if my song start with pattern A1 and if in the pattern screen i've choose A2,
then when i'm playing my song, the first step is from A2 and not from A1.
sometime, this is a problem, specially when i play song 1 and then song 2.
the first step is not the good one.

hope i'm making clear...

best regards

[TK.]

nuke, on 20 October 2010 - 10:51, said:

1. i discovered the exclude from "All" function when pressing "select" ...it works so far but not on the first step, is that right?

I checked this, it works like expected:
the first step won't be changed if not in the selection mask and if you don't use the first rotary encoder to modify all steps.

Best Regards, Thorsten.

[TK.]

Beta29 is now available:

MIDIboxSEQ V4.0beta29
~~~~~~~~~~~~~~~~~~~~~

  o implemented tap tempo function.
    It can be accessed in the BPM menu page (rightmost GP button), or with MENU+PLAY

  o fixed "accent on stretched notes" issue

  o fixed pattern synchronisation issue at very first played pattern in song mode

Best Regards, Thorsten.

[nuke]

TK., on 24 October 2010 - 13:52, said:

Beta29 is now available:

  o fixed "accent on stretched notes" issue

Great!! ;) thank u very much!

...btw, is there a way to define additional buttons in the hwconfig?
my "old" setup had some additional buttons like : Mode, Groove, Length and Direction...somehow i haven´t figured out yet to assign those functions/pages to dedicated buttons...like i did in the seq3.4 layout...

This post has been edited by nuke: 27 October 2010 - 13:05

[Echopraxia]

nuke, on 27 October 2010 - 13:02, said:

is there a way to define additional buttons in the hwconfig?
my "old" setup had some additional buttons like : Mode, Groove, Length and Direction...somehow i haven´t figured out yet to assign those functions/pages to dedicated buttons...like i did in the seq3.4 layout...

Ditto:)