00000000481245 ms | Track Parameters of G1T1
...
00000000481247 ms | Synch-To-Measure: yes
[/code]
[code]
00000000543055 ms | Track Parameters of G1T2
...
00000000543058 ms | Synch-To-Measure: yes
00000000304375 ms | Global Settings:
...
00000000304377 ms | StepsPerMeasure 15
[/code]
(StepsPerMeasure counted from 0)
> Options page right under the word change it was set to 16 and I set that to 256.
Yes, of course - so, you've proven that Synch-to-Measure works correctly ;)
> Why would someone set this to 16? When looking at the code under global settings it is the steps per measure correct?
yes... and 16 is a good choice for common 4/4 style songs, I don't see a reason why I should change this default value.
> Also what does sync pat change (on/off) do exactly? (in options)
It's explained in the user manual - basically it has the same purpose as known from V3
But I just remembered, that I haven't implemented the synched pattern change yet (who really needs this?)
Best Regards, Thorsten.
Doing sync pattern change is not a big deal but I think that the option to do it would be great. Some people prefer new patterns to start imediatly and others like it like roland tr drum machines where the pattern changes at the end of the loop.
regards,
echo
But I just remembered, that I haven’t implemented the synched pattern change yet (who really needs this?)
I use this all the time. Much of my other equipment changes patterns at the end of loop.
I’m getting new core soon so ill try to give some feedback after upgrade.
Thanks,
koki.
TROUBLE WITH PHRASE MODE
Hi, I am not sure if I am doing something wrong, but I can not get my SEQ (Beta6) to
execute the action defined at song position when I am in phrase mode.
I use encoder #2 to change the song position but the new position will only flash in the
display and nothing will happen.
Am I missing something? Do I have to do something to execute the action defined at the
new song position?
Best regards
Gridracer
Am I missing something? Do I have to do something to execute the action defined at the
new song position?
You have to “fire” the song position by using one of the 16 GP buttons.
Each GP button selects another song position (accordingly 16 “phrases” can be selected).
This change was required, as users requested to combine multiple steps to a phrase (e.g. selecting the tempo, mixer map and mutes in addition)
I’m sorry about this complicated usage — but this is just the result when I have to try to find a feasible solution to cover your requests.
Best Regards, Thorsten.
Btw. Gridracer: please let me know when you are ready to test a modified firmware for debugging the chaselight issue you reported (I already wrote you a PM, but haven’t got an answer).
I copied an updated “mbseq_tmp” version based on beta6 to the server.
Best Regards, Thorsten.
Related to this comment a question to users:
I use encoder #2 to change the song position but the new position will only flash in the
display and nothing will happen.
I’m planning to improve the CC number entry in Event Track and LFO Configuration page this way: selection of CC with rotary encoder, confirmation with GP button, so that CC doesn’t change immediately (resp. “random CCs” will be sent while a sequence is playing)
I already feared that this way of number entry could be confusing, as all other values are usually modified directly with the encoder. Gridracers “trouble posting” confirms, that this is an unexpected behaviour.
So, I will probably get rid of this idea.
I could alternatively add a delay of (for example) 3 seconds until the CC number change takes place (counted from last encoder move), so that there is enough time to find the correct value. But this would slow down the usage.
Are there other proposals?
Best Regards, Thorsten.
Btw. Gridracer: please let me know when you are ready to test a modified firmware for debugging the chaselight issue you reported (I already wrote you a PM, but haven’t got an answer).
Dearful sorry, I did not notice the PM.
But now I uploaded the new file and everything works perfect!!
Thank you very much!
Best regards
Gridracer
I’m planning to improve the CC number entry in Event Track and LFO Configuration page this way: selection of CC with rotary encoder, confirmation with GP button, so that CC doesn’t change immediately (resp. “random CCs” will be sent while a sequence is playing)
Funny, just two hours ago I managed to completely confuse one of my synths by scrolling through the CCs so that only powering off and on could bring it back to life.
How about this:
Couldn’t you display a message in Event Track page when changing the CCs like:
“Confirm with SELECT” like in a way when saving a pattern on SEQV3?
But I think it is not a big issue as you can mute the parameter layer in advance.
And in the LFO Configuration page you can set the LFO to off for CCs while selecting.
But non the less, the 3s waiting time wolud be an additional help.
EDIT:
Another Idea:
How about to mark parameters that should not be automatically updated by turning the encoder
with e.g. a “!” sign ahead of their name to indicate that their change has to be confirmed by pressing the
GP Button below. I think that would be easy to learn and keep in mind if it would be possible to keep
that consistant within all menu pages.
Best Regards
Gridracer
You have to “fire” the song position by using one of the 16 GP buttons.
Each GP button selects another song position (accordingly 16 “phrases” can be selected).
Ah, now it is clear, i was missing “Each GP button selects another song position” as the manual says
“By pushing a GP button, the sequencer will execute the action defined at song position A1, B1, C1..P1”
Now that I know i think it is quiet easy and comfortable.
Anyway I just wasn’t trying hard enough in advance.
Best Regards
Gridracer
Thanks for the helpful input!
So… Beta7 is available, this time with following features:
[tt]
o a new label editor allows to enter track and pattern names so fast and easy
like typing a SMS on a mobile phone. Use the first 10 GP buttons or encoders
to cycle the characters (like on a telephone keypad), and the remaining
buttons/encoders to select a character directly, move the cursor, delete/insert
characters, selecting a preset (with the encoder) and to exit the editor.
This picture says it all - I really like the new entry mode - it’s essential for fast filename entry of future features! 
o implemented synchronous pattern change after x steps (x=1..256)
This function has to be enabled in the UTIL->OPT page.
The same number of steps is used for the Synch-to-Measure function.
o implemented Follow Song mode. It has to be enabled in UTIL->OPT menu.
o a warning message will be print if Synch-to-Measure is enabled, and a
track length greater than steps per measure is selected.
o CC number selected in Track Event and LFO Configuration page now has to be
confirmed with GP button below the appr. item.
A warning message will pop up to notify about this unusual data entry method.
In addition, the value will be marked with ‘!’ so long it doesn’t match with
currently active value.
o fixed various minor bugs
[/tt]
Best Regards, Thorsten.
Your daily update… (ok, for tomorrow I haven’t scheduled a new version ;))
ChangeLog of Beta8:
[tt]
o now your MIDIbox SEQ can play MIDI files, either exclusively or in parallel to
the 16 sequencer tracks.
MIDI files have to be copied into the /midi directory of your SD Card.
To select a MIDI file, go to the UTIL->DISK->PLAY page, and select
the desired modes (Exclusive/Parallel and Loop on/off)
o MIDI file import and export prepared in UI, but not implemented yet!
o MIDI port used to send a SysEx dump now selectable in file list browser
o fixed various minor bugs
[/tt]
Have fun!
Best Regards, Thorsten.
…Thorsten, Im lacking the words … got to … click… beeer…
Can you use mios to import and export the midi files?
…Thorsten, Im lacking the words … got to … click… beeer…
Cheers!
Can you use mios to import and export the midi files?
Yes, since MBSEQ can already play MIDI files, importing the data and doing the reverse thing is only a question of defining a good user interface, e.g. for track/range/resolution/event mode (note/CC or drum) selection
It would be interesting if the MIDI file player works with all your .mid files - the parser has only been tested with my own files so far.
Best Regards, Thorsten.
Some small bug report:
beta8 plays MIDI file (fade to grey.mid) and Mclk In/OUT is USB1 on/on (even with off/off or off/on).
If i try to sync this with ableton (EXT SYNC), i do get flucutating (around 800-900 BPM) on the Display and
a synth inside this behaves the same, e.g. the sync between the mbseq and ableton is not possible 
Also once a midi file has been selected it will always be played when you start the sequencer.
Question:
When Pressing C on Trigger Layer, i get the Assignment window (a-H), is that correct ?
Pressing C on pattern layer shows me Note/Vel/Len Menu, also correct?
synchronous pattern change is working great. It makes it real fun to switch patterns on the fly and stay in sync. And it will be more fun when I get the leds soldered
About the midi files. I havent used midi files very much in the past but if I could edit them on the mbseq I would start using them more often. are they stored in a song bank? or would it lay out the midi tracks from the files to each track on the sequencer when in pattern mode. It would be interesting to go to options and select midi player view and be able to mute and unmute the individual midi tracks form the mid files like you would in the mute page and edit each mid tracks notes from the edit mode the same aswell. You could have a pop up warning to tell you your in “midi player view” Then I could assign a function button to make short cut so I could handle classical midi files and seq beats in dj fashion:D
I would probably guess that this would be hard to do because the patterns loop and midi files don’t. This is probably to much to ask for.
I think if the midi files could start synced to mb internal patterns we’ll be set.
Thanks again,
echo
beta8 plays MIDI file (fade to grey.mid) and Mclk In/OUT is USB1 on/on (even with off/off or off/on).
If i try to sync this with ableton (EXT SYNC), i do get flucutating (around 800-900 BPM) on the Display and
a synth inside this behaves the same, e.g. the sync between the mbseq and ableton is not possible
It should work now (beta9).
In distance to the previous solution, the sequencer core is not disabled anymore in “Exclusive mode”. Instead, the tracks will be muted (not visible in Mute page yet - will be done later)
Also once a midi file has been selected it will always be played when you start the sequencer.
The MIDI file is now properly synchronized to the running sequence.
This was really hard work at my side - I hope that all possible cases are covered! :-/
When Pressing C on Trigger Layer, i get the Assignment window (a-H), is that correct ?
Yes, because there are 8 trigger layers, I had to find a way to make all layers selectable, so that no additional “Trigger Selection” button is required.
Pressing C on pattern layer shows me Note/Vel/Len Menu, also correct?
Yes, so long more than 4 parameter layers are configured.
I guess you configured it for 8 or 16?
If a track only consists of 4 parameter layers, ParLayer C button will toggle between layer C and D
synchronous pattern change is working great. It makes it real fun to switch patterns on the fly and stay in sync. And it will be more fun when I get the leds soldered
cool!
About the midi files. I havent used midi files very much in the past but if I could edit them on the mbseq I would start using them more often. are they stored in a song bank? or would it lay out the midi tracks from the files to each track on the sequencer when in pattern mode. It would be interesting to go to options and select midi player view and be able to mute and unmute the individual midi tracks form the mid files like you would in the mute page and edit each mid tracks notes from the edit mode the same aswell. You could have a pop up warning to tell you your in “midi player view” Then I could assign a function button to make short cut so I could handle classical midi files and seq beats in dj fashion:D
I would probably guess that this would be hard to do because the patterns loop and midi files don’t. This is probably to much to ask for.
Yes, thats really too much!!!
A MIDI file is just a stream of MIDI events, MBSEQ plays this stream to the end and optionally loops. Editing this stream would require a lot of work at my side which I don’t really want to do.
You could import the stream into one or more tracks, edit the events there, export back to a MIDI file and play it again… it’s like rendering one or more patterns to a file, and play them as a single additional pattern in parallel to the 4 patterns which can be edited interactively. I will use Meta events to embed track parameters, so that they won’t get lost during export/import.
You could also export tracks/patterns/songs to a file, edit them with your DAW, and import back to MBSEQ. Currently I don’t know, how comfortable this can be realized… due to all the options, the usage could get complicated.
Adding even more features for the MIDI file feature would make the usage even more complicated.
In short: I would like to keep it simple.
I think if the midi files could start synced to mb internal patterns we’ll be set.
thats possible now.
Best Regards, Thorsten.
ChangeLog beta9:
[tt]
o If a sequence is already running, the MIDI file player doesn’t cause a restart
anymore. Instead in automatically synchs to the next 16 step based measure.
o Track Event page: to trigger the Init function, GP16 has to be pressed for
2 seconds (a message will be displayed to inform about this)
o fixed various minor bugs
[/tt]
Best Regards, Thorsten.
Feedback:
- The MIDI File issue is solved.
What i still see:
- When using USB1 as input for Ableton Live and SYNC to USB1 (from MBSEQ) and accepted from Ableton: I get BPM of 999
(irregardless of MIDI File Play or just sequence play) ( Haven’t tested MIDI OUT yet).