[stuartm]

Echopraxia, on 08 June 2010 - 07:40, said:

I would say if the transpose page stayed on octave or semi, whichever being the last setting used globally, would not do much good. I would tend to forget that I set it to semi and make a mistake during jamming. Anyone else?

Also referring to your first post about this, I would also prefer to have Semitone selected first.
How about a setting in the config file where you could select if you'd have Octave or Semitone selected first, as a global setting?

On another issue, TK:
I think the external Restart is not working as perfectly as it was on the SeqV3. I have the V4 now in the same MIDI setup as the V3 before.
When hitting Start, everthing is fine and in sync. Stop, Start. Again in Sync.
Now while the Seq is running, i hit the external restart ("ext. restart request" appears), the start signal is sent, but the slave machines are just slightly out of sync.
It might be just a few ms, but I can hear it immideately.

This happens when a stopped slave machine is started again as well as a running slave machine is "re-synched" (tried with different machines).
Also, when I request an ext. restart while the SeqV4 is stopped (message appears) and then hit start, the slaves are slightly out of sync.
This slighty discrepancy stays, and the only way to get rid of it was to hit Stop and Start.

I guess that due to the MIDI handler in the Core, the function is implemented differently in the V4 than in the V3.
If you need more info or some test data, I'll be glad to provide.

This is THE killer feature of the MBSeq for me, so let's hope we can get this sorted out!

[stuartm]

Here's an MP3 demo of what I mean:

 synctest_bd.mp3 (153.7K)
Number of downloads: 10

two layered kick drums, one triggered directly via the Seq,
the other from the Machinedrum's internal sequencer running as slave of the MBSeq clock.
First 8 kicks are more or less perfectly in sync, on the 9th kick the ext. restart happens and you can hear that they are slightly out of sync.

I've tested different ports on the core, direct connections and different machines. All the same.
I'll have a look at the source code, C is a bit more readable for me

[TK.]

Thanks for the input!

I just came back home and won't have the time today to check firmware changes by myself.

However, I think that I know from where the delay is coming from: MIDI clock start was sent directly after the MIDI clock event, but it should be sent before.

Could you please try following temporary release if it works at your side?
If it still doesn't work, I will test this with various sequencers at my side... later.

Track transpose page now always starts with semitone selection.
Due to conceptional reasons it isn't possible to store the last setting, nor to make it configurable in a config file.

The issues reported by Gridracer are not fixed yet.

-> http://www.ucapps.de...beta23_pre1.zip

There are some preparations for OSC which hopefully won't conflict with existing functions.
They are currently only working on an iPad, MBHP_ETH support will be added this weekend.

Best Regards, Thorsten.

[stuartm]

Perfect!
That fixed the sync issue!

I think I owe you a beer

[Gridracer]

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

[Echopraxia]

Hey TK,

Is there a function in place to copy drum track configurations to other patterns (note and chord tracks as well)? I made a pattern in A1 and used the copy function to get the notes over to A2 but I want to be able to also copy all the mappings of the track ect. When you just copy notes over to A2 the drum note configuration is the default. Is there a second copy command to copy these additional parameters to the other patterns. Would be handy if its a separate function that's not tied in to the regular copy command.

Regards,
echo

This post has been edited by Echopraxia: 12 July 2010 - 18:03

[TK.]

Gridracer: your idea isn't lost - I like it and will see what I can do.

Echopraxia: the recommended method is to store the complete track from which the drum map should be exported into a preset (MENU->EVENT->PRESET->SAVE AS NEW PRESET)
Now you can import the drum map into another track with the PRESET function as well.
Note that you will be asked for several import options, e.g. you can exclude the pattern import (Steps: no), etc.

This function not only works for importing/exporting drum maps, but for anything related to a track.
It's the most powerful copy function (especially since you are able to edit preset files with a text editor) - you will like it!

Best Regards, Thorsten.

[gomiboy99]

Hi,
just completed the build of my MBSEQ, I am having trouble with the SD card. The firmware reads the hwcfg file ok and I can create session files but sometimes get error messages, E3 and E11 (these are not displayed for long enough to read all the details).

This extract from the manual states: "Some additional files are required for Patterns/Songs/Mixer pages. The firmware won't create them automatically, instead it will ask you to go to UTILITY->DISK menu, where you will find a "Format" option at the left side. Activate this function to create the files."
I have nothing in the left display when in the UTILITY->DISK menu so cannot create these files.

Have I missed something or is this function no longer applicable, do I have to create them manually?

Regards

Tim.

PS I have tried several different cards and changed the cable between the core and sd socket.

This post has been edited by gomiboy99: 20 July 2010 - 11:08

[TK.]

With the session concept the format function under UTILITY->DISK got obsolete, therefore I removed it from the application (but haven't updated the documentation yet).

E3 means that the volume information (part of the filesystem) couldn't been read
E11 means, that a file couldn't been written

Probably E11 is a side effect of E3 - means, there seems to be an issue with the format.

Phil has created an application which formats a SD Card properly, it can be found here:
http://midibox.org/f...ge-device-stm32

(please continue discussion there)

Best Regards, Thorsten.

[gomiboy99]

Thanks TK,
the answer is much appreciated, I will try formatting the card as suggested.

Keep up the good work, I can't wait to use this thing in anger

[stuartm]

TK., on 20 July 2010 - 18:46, said:

With the session concept the format function under UTILITY->DISK got obsolete, therefore I removed it from the application (but haven't updated the documentation yet).

Ahhh. So I can take this point off my little list of "bugs" discovered so far.

[Echopraxia]

I seem to be having trouble getting a drum track to go for more than 16 steps without having to adjust the options page measure function. It tells me that sync to measure is active for 16 steps when I try to make the drum track 64 steps. that means the pattern will change/update at 16 steps for changing to a new pattern or scubbing right? And it still just loops the first 16 steps even though I have pressed the 64 length. I thought this behavior was odd because my non-drum tracks are not doing this. Is this a bug with drum tracks?

[vcfool]

Echopraxia, on 01 August 2010 - 09:28, said:

I seem to be having trouble getting a drum track to go for more than 16 steps without having to adjust the options page measure function. It tells me that sync to measure is active for 16 steps when I try to make the drum track 64 steps. that means the pattern will change/update at 16 steps for changing to a new pattern or scubbing right? And it still just loops the first 16 steps even though I have pressed the 64 length. I thought this behavior was odd because my non-drum tracks are not doing this. Is this a bug with drum tracks?

I get the behavior you mention when I got the "Synch to Measure" enabled under the track's "Divider" page. Maybe your drum track has this enabled and your non-drum tacks have not.

Just a thought because I still don't really fully understand the Synch to Measure feature.

[Echopraxia]

vcfool, on 01 August 2010 - 09:41, said:

I get the behavior you mention when I got the "Synch to Measure" enabled under the track's "Divider" page. Maybe your drum track has this enabled and your non-drum tacks have not.

Just a thought because I still don't really fully understand the Synch to Measure feature.

Ah man thank you! Good call. Working just fine now. So many things to forget ya know?

[TK.]

The long summer break is over and I continued with MBSEQ development

Beta24 is available now:

  o support for OSC (requires MBHP_ETH module)
    4 OSC ports are available, currently they only send MIDI packets.
    A MIDI<->OSC proxy is currently only available for MacOS (on request)
    An easy to use Juice based Proxy is planned and will be released soon.
    (Firmware-)configurable OSC packets will be available in one of the
    next releases.

  o new network configuration page for the MBHP_ETH module

  o the debug terminal now supports a "network" command to retrieve
    the current status of the network configuration.

  o now we have global configurations which are stored independent from the
    session configuration in the "/MBSEQ_GC.V4" file 

    Following parameters have been moved to this file:
      - MetronomePort
      - MetronomeChannel
      - MetronomeNoteM
      - MetronomeNoteB
      - RemoteMode
      - RemotePort
      - RemoteID
      - BLM_SCALAR_Port
      - ETH_LocalIp
      - ETH_Netmask
      - ETH_Gateway
      - ETH_Dhcp
      - OSC_RemoteIp
      - OSC_RemotePort
      - OSC_LocalPort

  o probability parameter now incremented correctly in edit page

  o if the track plays multiple notes, gate is only cleared if
    all notes are set to "---"

  o BLM: triggers now displayed correctly in all stepviews

The new network configuration page can be found at the end of the menu pages list (press EXIT button, scroll the list to the end)



One issue isn't fixed yet:

Gridracer, on 29 May 2010 - 10:55, said:

I noticed that the arpeggiator (and transposer) behave different when they are contorlled from external eg. keyboard or from an internal track:

- If the contorl notes come from external, the settings HOLD and RESTART work as they are described in the manual
- If the contorl notes come from an internal track, the arpeggiator (and transposer) always behaves like if HOLD is ON and RESTART is OFF,
no matter to which value they are actual set.

Is this behaviour intended?

you will find it in the TODO list at the end of the CHANGELOG.txt file.
Here some technical notes:

The handling of loopback tracks differs from normal tracks. MIDI Events are sent
immediately to the transpose/arpeggiator function instead of using the scheduler, so that
note changes take place immediately and independent from the track number before new
MIDI events are scheduled.
Disadvantage of this method: note off events won't be generated, accordingly the gatelength
won't be considered and HOLD/RESTART of transposed tracks won't work as expected.

Possible solution: gatelength counter for note off events, only used for loopbacked tracks.
Problem: how should polyphonic loopback tracks be handled?
It could be sufficient to call SEQ_MIDI_IN_ResetTransArpStacks(<bus-number>) depending on
the gatelength

So - a proper solution will need some time, because I'm currently not sure about the side effects.

Best Regards, Thorsten.

[mastomo]

Hello TK, hello everyone,

is it possible to reorganize pattern between differents sessions ?

if yes, i can't find the procedure.

if no, is it possible in future ?
that would be a great things for me.

btw, i'm playing this new midibox on stage since 2 weeks, and this is amazing,
once again, many thanks for this

[TK.]

mastomo, on 09 September 2010 - 01:57, said:

is it possible to reorganize pattern between differents sessions ?

if yes, i can't find the procedure.

if no, is it possible in future ?
that would be a great things for me.

Such a function isn't available yet, and it will be some work.
But I will add it sooner or later, because it definitely makes sense!

Best Regards, Thorsten.

[TK.]

Beta25 is available now:

  o now each OSC port has an individual configuration set which consists of
    the Remote IP, Remote Port, Local Port and Transfer Mode

  o an OSC Transfer Mode has been added, it can be configured in the network
    configuration page for each OSC port.

    In MIDI mode, all events generated by the track will be embedded into a
    'm' type packet. This mode allows to tunnel MIDI events via ethernet to
    a proxy which runs on the host (or any device which is able to convert
    these messages)

    In "Text Msg (Integer)" and "Text Msg (Float)" mode, the OSC packets will
    be encoded the following way:
      - Note Events: /<chn>/note <note> <velocity>
        Integer: note and velocity in range 0 .. 127
        Float: note still as integer, velocity in range 0.0 .. 1.0
      - Poly Pressure Events: /<chn>/polypressure <note> <pressure>
        Integer: note and pressure in range 0 .. 127
        Float: note still as integer, pressure in range 0.0 .. 1.0
      - CC Events: /<chn>/cc <cc-number> <value>
        Integer: value in range 0 .. 127
        Float: cc-number still as integer, value in range 0.0 .. 1.0
      - Program Change Events: /<chn>/programchange <value>
        Integer: value in range 0 .. 127
        Float: value in range 0.0 .. 1.0
      - Aftertouch Events: /<chn>/aftertouch <pressure>
        Integer: pressure in range 0 .. 127
        Float: pressure in range 0.0 .. 1.0
      - Pitchbend Events: /<chn>/pitchbend <value>
        Integer: value in range -8192..8192
        Float: value in range -1.0 .. 1.0

    <chn> range: 1..16

  o OSC option now supports SysEx transfers (SysEx stream is embedded into blobs)

  o it's now possible to route USB/MIDI/IIC/AOUT ports to the OSC ports in 
    the MIDI Router page.

  o SysEx streams will now be forwarded by the MIDI Router as well.
    The Chn setting has to be set to "All" for source and destination port.

    This allows you to access the SysEx functions of your synth - it's even
    possible to upload a new firmware to a MIDIbox which is connected 
    to a MIDI port of MBSEQ now.

  o MIDI->Misc menu: BLM can now be assigned to an OSC port

Especially the SysEx forwarding function has been requested by multiple people.
The OSC add-ons are only for nerds ;)

Best Regards, Thorsten.

[Echopraxia]

Having some issues with the save function. Maybe I should update to the lateest beta. i think I am still at 22.

When I press the exit button, to go to the session load and save menu, I press the save button and I see that the leds that flash to select a session stop flashing and stay lit for a second and then nothing else happens. I get no response and I thought it used to tell me that it saved. And it was not saving when doing this. I can save by overwriting the session but I have to rename it correctly. I will update and let you know if that fixes the issue.

Also does the clear button do nothing now?

[TK.]

Quote

I press the save button and I see that the leds that flash to select a session stop flashing and stay lit for a second and then nothing else happens. I get no response and I thought it used to tell me that it saved.

it should tell you "all 4 patterns stored" for ca. 2 seconds at the right lcd.
are you sure that the button is working?

Quote

Also does the clear button do nothing now?

yes - you have to press&hold the button for two seconds, a message will be displayed which asks you to do this.
so far i remember this special handling was requested by you?

best regards, thorsten.