srmaietta

Alternately, one could just write them as a list in the wiki or “user manual” for people to have? I’m fine with scrolling the list, it’s rare that I do these days anyway..

This was added in v4.094 I believe, in 2017. Don’t think removing this would be a simple change. It’s something I’ve gotten used to. perhaps could be added as an option?

In the HW setup file there is a section to configure a number of buttons as either momentary or toggle. Perhaps this can help you customize a bit to your liking.

All button has a few modes of quickly modifying values, and yes, they generally revolve around the chosen step. there is a page/chapter in the beginners guide.. Steve http://wiki.midibox.org/doku.php?id=mididocs:seq:beginners_guide:start

Confirmed over here, no humanizer being applied to CC’s. I tried with an empty track sending layer A as CC on buss 1, and another track listing to buss 1. The listening track was responding to the cc’s, but humanizer did not effect the CC’s. Then moved the cc to layer B (usually the velocity layer) and still no changing of CC’s sent. steve

Great TK, much quicker to get to the nth commands, thank you!! steve

Thank you TK, waveforms VERIFIED!

Works great now Thorsten. I feel bad for asking so much lately! But would an inverse saw (ramp) be possible to add? Steve

Would it be possible to eliminate the “empty” options in the Nth1 and Nth2 parameter layers? We go through 16 encoder clicks before getting to the first useful command “Mu 1”. I think it has something to do with modulo result of zero (?) idk …? Perhaps these useless options could be removed from the list of nth options.? Lots of rolling the encoder to get to the “good stuff”, and there’s already a lot of options in there to go through!! thanks -Steve

Thorsten, the new LFO setting ClkDv is nice, great how the lfo stays locked to the track even if one changes the divider!! but perhaps not working as correctly as it should. Seems as if reset is happening before the final step is played. My simple setup: A 16 step track set at divider of 1/4 notes, all note A-1. I haveset the LFO to Saw, Steps to 16, Rst to 16, and ClkDv on. The notes rise up for 15 steps, but resets to base note at step 16. Musically, Seq is resetting the lfo before activating the note transpose for the step. ~steve

When setting the steps in the LFO page, it always refers to 16th note steps, even if your track is set on quarter or eighth notes, etc. It makes sense to me that the steps specified in the LFO settings match the divider setting so it’s easier to create an LFO of the desired length. -Is there a reason this cannot be configured to represent actual steps of the track one is editing?

TK -seriously. YOU DA MAN!!! —This now works just like I’d expect— Your amazing machine lives on and still is at the very top of the list!

Driving me crazy that the step direction parameter layer works fine in any other screen, but in the edit screen, it seems to freak out. When I get back to my workstation, I will see how the track responds when setting this up using a cc track through a bus.

Are these available without SID chips? I have two SID’s here. thanks!

Anyone could enter this in a seq4 and see how yours responds?

Playing with ctrl parameter layer and I’m noticing something that seems not right, and I don’t think it’s user error. (Bug? Fixable? Code architecture limitation?) I set up a single 16 step track with ascending scale of notes, on a new clear project to verify this. I set up parameter layer D to ctrl, cc40 (track direction) and put in 0000000551111111. This is forward x7 steps, random step x 2 and backward x7. —When I play the track from the edit screen the forward steps are randomly scattering forward and backwards. The backwards set of steps always seem to work correctly. —When I play the track from any other screen (track direction screen as shown in video) the CC assignments seem to work correctly. please watch the video to see what I’m talking about.

Posting about ctrl layer issue in new thread…

Thank you Rio, it gives me something to tinker with. and it gives me insight into the difficulties (as Hawkeye mentions) with changing something that is reliant on many other things in code..

Up for any ideas!

Hello! I know this has been brought up before, but I’d like to revisit the idea of “unquantized live recording”. currently the quantize percent basically shows how far off one can be before dropping a value in the current step/prev step. So it’s locked to a hard step position. I know we can up the resolution and track length to kinda sorta work within the system. But that is not ideal for a number of reasons. An idea: when recording midi, if we have the delay parameter assigned on a track, and have quantize set to 0%, it will then drop the played note wherever it was played within the delay parameter resolution. Perhaps a new track format needs to be set up, or perhaps it is a parameter to toggle in the menu. I have no idea if this is at all possible from a programming / code base perspective. But no truly unquantized recording is one of the only missing things of our mighty Seq 4!!!!! Thanks for reading! Steve

Loaded the sysex file, selected the midi output, set the time to 100ms and away it went. -SUCCESS! MIOS Studio for the WIN! now to use this to breathe some new life into my Yamaha FB-01 . . . . ~Steve

Thanks a lot!!! Excited to try when the new old synth arrives. Will report back here. ~Steve

I see the MIOS studio has a basic sysex transfer abilities and a sysex librarian/. Can I use this to send a sysex file (patches /programs) to my Roland JV1010? Or is this set up to only comunicate with MidiBox cores..? Id rather use MIOS than download some other app. since I've got it and use it for my midibox Seq. already. thanks! ~Steve

These still available? thanks ~Steve

Here's a simple "cheat Sheet" I made up a while ago and keep handy. May be a good starting point for folks. I add notes to it, go experiment, and then revise the cheatsheet. . ~Steve Seq4+RefSheet.rtf