=FFW=>

hey pim, im sorry to say- everything is gone. except for the midirex pcb, which i still dont need. as well as a finished midirex (70.- Euro). alas!

i´ll try to put it to life and report back! thank you for being like that. always.

okay, guys - im not the profit oriented person. i just thought, adding up my costs for those pcbs plus shipping plus import fees and slight hassle addon - its fair. and i stand by that opinion. sorry if i am pissing anyone off by this. was not my intention :no:

hey (latigid :-), point is, getting everything needed (aside from the components) in one package with one shipping is more than worth it. getting all those pcbs together will at least set you back a few weeks. so this is a very good deal. and, of course, you do not have to take this stuff... best, =FFW=>

Hi there, as i have stacked up an amount of pcbs i dont need right now, i want to sell them. It was a hassle to get a hold of all these, so theres a slight topping within the prices for that. Good thing: you get everything needed in one package. 2 displays 40x2 (16 Euro stck) flashed stm32f4 board (20.- euro) st32f4 baseboard with midi out expansion (18.- euro) midirex board (35.- euro) cs pcb (42.- euro) tpd pcb mit led matrizen (17.- euro) blm pcb (35.- euro) So as you see, theres a midirex board in there, quite handy and highly recommended. And the sequencer is the actually possible "full blown" thing, with the blm 16x4 as well as the tpd from ilmenator. And: I want to sell the lot, not pieces of it... Im located in Germany, so count that in when thinking about shipping... Cheers =FFW=> ...and theres an LPD8 from AKAI with better potentiometer caps i will not need anymore (perfect condition) for 25.- Euro

Hmmm, as i understand it, this is a solution, isnt it? And not a bad one. Would you provide access to the flag (!) then? The case would be to have three Parameter Groups with their own snapshots (track send amounts / track device parameters (cutoff etc.) / return-feedback matrix). As i understood it, one will enable/disable the respective flags for there parameter groups right before _restoring_, as when saving a snapshot, all parameters available get stored anyways (no matter if they have a no_dump flag)? Cheers (and thank you), =FFW=>

Hi, maybe this has been coming up before and theres a solution. To the ones who might know one, please shed some light. Is it possible, to dedicate snapshots to certain groups of parameters? Goal would be, that (to be defined) Parameter Group 1 gets an own snapshot as well as Parameter Group 2 and so on.. Thanks in advance, =FFW=>

yes, that would be excactly what i have imagined: "The relative events take a number value that is an offset from the main pattern note." (Sequentix P3 Manual; p.134) I wonder if Thorsten thought about something like this already.

Hi Thorsten, first off, thanks for that lightning speed with the update. I am always amazed at how fast things can happen here in Midibox Land. Before i get to answer these proposals, they get implemented :blink: I´ll try to keep up with that pace. 1. FX-Humanizer: - option to select affected target cc´s - 4 ccs available within gp buttons / encoders on the right display I think, selecting the parameter layer would be perfect as it extends the option of just selecting the cc. 2. extend parameter layers - there should always be at least 16 parameter layers as well as all 8 trigger layers available (especially the drum tracks would profit from more assignable parameter layers) absoluteley understandable now. Thanks for pointing it out so clearly. 3. Variable Step-length of parameter layers could open up the possibility for independent length of cc-modulations implementation (gui-wise)? can you point that out a bit? Why do we need to spend a layer for alternating the length of another layer? or is that a misunderstanding? 4. Having a „looping“ backing track for every note-track. One can configure a subset of parameter layers to form a sub-track having independent length. yes, i initially thought it would be great if one could loop a layer with a step length independent of the trigger layers. one could use the cc layers as a kind of step-lfo-modulators then, for example. keep their length, independent of the parameter layers. 5. chordFX - with toggle button use case: 1.user plays chord to memory 2.user can transpose chord according to played note on that track session wise chord entry would be sufficient i think. i just thought, that for big chords, this would be a handy function, to play a chord into memory and then being able to play back that chord, transposed by the played note. i havent thought of a neat way to implement that though. and while playing with the new edit-record function, im not so sure anymore if it is needed - i think it is more on the "nice to have" side of things. so if you stumble across an idea and time to implement such a function - great. 6. while in phrase mode (and using the save&take over patterns function): -song 1 „save and take over patterns“: a1-p1 -song 2 „save and take over patterns“: a2-p2 -… -song 8 „save and take over patterns“: a8-p8 that would be great. 8. having an option to modify the way, the function save&take over patterns will save pattern information (eg. 1. mixermap;2.mutes;3.mixermap;patterns…..) maybe while startup? maybe setting it up with variables that can be ordered somehow within the MBSEQ_HW.V4 file. In a way, that one can setup the order of the song positions to be saved, like: A1: Tempo A2: Mutes A3: Mixer A4: Pattern A5: Jump or: A1: Tempo A2: Mixer A3: Pattern A4:Jump I thought, that it would be good to maybe save patterns without the mutes or the mixer state to be sent and that a configuration option for that is missing for now. 9. Gate Modes as additional parameter layer to define step lengths (1/16; 1/8 etc.)? Maybe as an option (different entry mode) to the current length-layer input method. So the user can choose the length of notes right away. 10. euclid generator - note select function like it is within the random note generator If it is implemented as note selection, one could step through the notes of a chord and distribute those notes over the pattern, getting interesting "clashes" between the notes (assuming they get distributed over the respective note layers). Yes, the gui is crowded. Maybe if the parameter names "Pulses" and "Offs." get shortened to "Pul" and "Ofs" there is enough space? 11. having the option to select track groups (by using the track group buttons) simultaneously (selecting more than one group) as soon, as there is a longpress (around 1 sec.) of two group buttons simultaneously, the respective tracks within those groups are selected. 12. duplicate actual track (doubles the length of the track by copying the content of the actual content of the track) I thought of it as a way, the elektron-sequencer does it. When you have a pattern of the length 16-steps and switch to a length of 32 steps, the steps 1-16 will be automatically doubled. 13. On/Off Toggle for ExtraCC# function within lfo menu (theres a free button below the ExtraCC;-) THANK YOU! 14. four additional sequencer control track-layers that provide automation lines for sequencer settings (delay note; repeats; delay/ length/ divider etc.) I knew the note delay layer. I thought of altering certain parameters while the seq is running. As i get you now, it is not possible the way i thought of it. So, according to that logic, it will not be possible to modulate the length of the notes by the lfo (for example) as well. 15. echo page: on/off switch would be handy (within the display between „trk.“ and „repeats“). Thank you! 16. two (or more) LFOs That cost is too much then. I think you are right and there are enough workarounds for that. 17. record position indicator for step/layer/303 view (fast flashing red) Great. I tested the new functionality. It is such a great workflow enhancer. And the implementation is perfect like it is (4.086) 19. SR-allocation for important „live-tweakable“ parameter/trigger layer functions like note length etc. Hmmm, i see. But - displaying the value is not really needed. I thought of it as a purely live-oriented feature, where the parameters revert back to their original value, after they are tweaked. So it would be more about feeling than adjusting them meticulously. 20. Pitch Shift option for duplicate notes FX —> duplicated notes can be shifted by semitones Yes, more important for sure. It would be easy to get harmonics done with one track then. 21. when in record mode -while record mode is set to mono, there is an option missing to select the note layer, the recorded notes are recorded into. (could enable multitake recordings) Not so much, the new way of Note-Input is a charm. But the catch i thought of with the proposal was, that when in mono input mode, one could select the first note layer, put in some notes, then select the second note layer, put in some notes using another step-input-length (1st input: 16th; 2nd input: 8ths). 22. Automation port: define a port which sends out all data in parallel (mute-cc information as well) The way i have set up the Mbox NG now, cc parameters modulated by the seq (lfo/cc lines) wont be reflected by the led-rings of the encoders sending those ccs. If there would be feedback from the seq to the Mbox NG, the modulated parameters could be easily spotted. That was my imagination :-) So not all parameters would have to be sent to that port, just the ccs. What do other users think? Again, thank you for implementing all and everything so fast. The Seq is already a masterpiece for sequencing. So versatile and fun to use. So much better than commercial sequencers. Cheers Daniel

Hi Forum, while using the great SeqV4 frequently for some time now, some improvements came to my mind. I have started a small collection of proposals here and it would be great if the community would give feedback on those proposals. I would be very happy, if a few of them can resonate with your workflows :-) And please, if theres something you want to add or improve, by all means, do it! I hope we can build up a collection of useful feature improvements. I have marked my favourites with bold text. Here it goes: 1. FX-Humanizer: - option to select affected target cc´s - 4 ccs available within gp buttons / encoders on the right display usecase: 1. user wants to „humanize“ certain cc values 2. user has an option to select cc´s to be affected by adjustable modulation amounts while in fx-humanizer page (right side) 2. extend parameter layers - there should always be at least 16 parameter layers as well as all 8 trigger layers available (especially the drum tracks would profit from more assignable parameter layers) 3. Variable Step-length of parameter layers could open up the possibility for independent length of cc-modulations implementation (gui-wise)? 4. Having a „looping“ backing track for every note-track. One can configure a subset of parameter layers to form a sub-track having independent length. use case: playing a short looping ostinato upon a longer harmony implementation (gui-wise)? 5. chordFX - with toggle button use case: 1.user plays chord to memory 2.user can transpose chord according to played note on that track implementation (gui-wise) 6. while in phrase mode (and using the save&take over patterns function): -song 1 „save and take over patterns“: a1-p1 -song 2 „save and take over patterns“: a2-p2 -… -song 8 „save and take over patterns“: a8-p8 7. improving the cc mute function in a way that only the parameter layer of the incoming cc will be muted, instead of all layers as it is of now. maybe as well for note layers. 8. having an option to modify the way, the function save&take over patterns will save pattern information (eg. 1. mixermap;2.mutes;3.mixermap;patterns…..) maybe while startup? 9. Gate Modes as additional parameter layer to define step lengths (1/16; 1/8 etc.)? 10. euclid generator - note select function like it is within the random note generator 11. having the option to select track groups (by using the track group buttons) simultaneously (selecting more than one group) 12. duplicate actual track (doubles the length of the track by copying the content of the actual content of the track) 13. On/Off Toggle for ExtraCC# function within lfo menu (theres a free button below the ExtraCC;-) --> this is my absolute favourite :-) 14. four additional sequencer control track-layers that provide automation lines for sequencer settings (delay note; repeats; delay/ length/ divider etc.) 15. echo page: on/off switch would be handy (within the display between „trk.“ and „repeats“). 16. two (or more) LFOs -selectable while holding gp1 button - modifies encoder to function „track-lfo-select“ -while gp1 is pressed, track leds represent current (of 1-16 selectable) lfos by pulsing corresponding led -while pressed, trk. gets renamed to Tlfo 17. record position indicator for step/layer/303 view (fast flashing red) 18. 16 cc layers standard for every track configuration. (opens through second page (can be opened up with?; has cc number on top, value below. cc number can be changed by pressing the encoder or respective gp button and turning the encoder) 19. SR-allocation for important „live-tweakable“ parameter/trigger layer functions like note length etc. can be imagined as: „arcade encoders“ 16 (or 8) encoders like bm-buttons. that can be tied to certain functions, they are available for the actual selected track 20. Pitch Shift option for duplicate notes FX —> duplicated notes can be shifted by semitones 21. when in record mode: -while record mode is set to mono, there is an option missing to select the note layer, the recorded notes are recorded into. (could enable multitake recordings) 22. Automation port: define a port which sends out all data in parallel (mute-cc information as well) - to get omni-feedback on external controllers. -this would be especially handy in conjunction with the MidiboxNG. It would be great to have an optional „feedback-input“ for the MidiboxNG.

so theres news on the cap-thing: as these buttons are "soft", theres no caps for them. caps mount on "hard" material, these are too soft to "mount" classic button-caps. nonetheless, theres always an option for the diy-spirited. if one decides for these silent and clickless buttons, caps are easy to be made when using a laser-cut service and an acrylic frontplate. i did caps for my seq by glueing cutouts on top of each other, while the last cutout (the top) is the button cutout you are doing anyways. this way one is having perfect matching buttons. you can easily calculate how much cutouts you have to glue on top of each other - the material has (usually) a thickness of 3mm. my experience says: this gets you PERFECT BUTTONS :-) --> and they will be even better when they are silent! this would be it for the cap-solution. what do you think?

yep, mr. kobler pointed out, that this thing (so far) will leave his lair in amounts of 500 only :-) but, maybe there is a possibility to get them in smaller amounts. encoder caps go individually, that is true. (and one can´t find better caps than the ones they sell...) i asked about the button-cap issue and will report back!

hi forum, it seems that a long search is finally coming to an end. i have found buttons that are silent. no annoying loud clicks anymore. here is the (scarce) technical information on them: http://www.fk-industrie.de/de/produktkatalog/S/T/367.html now, as they are soleley available in amounts of 500 pcs, i want to know if there is enough interest in "silent buttons" to start a (small) group buy. price (without tax) is 0,14.- Euro per piece when ordering 500 of them. so, if you have interest in these, please reply accordingly within this thread. cheers, daniel

isnt that possible with the midi router busses you have within the midi page? have you read that section in the manual? MIDI Page (Shortcut: MENU+GP Button #15) http://www.ucapps.de/midibox_seq_manual_m.html

i think you will need to put a mute position for the patterns before the last song-step "end". otherwise, the seq will loop the last song position endlessly. at least thats how i understood it :rofl:

wow! great news and somewhat "in time" :-)

wow! thank you so much, TK., for all the effort you put down to all projects.

NICHT NUR fantastische Knöpfe gibt es hier: http://www.fk-industrie.de/de/produktkatalog/ZU/K/0.html sondern zum Beispiel auch hochwertige und rasterlose endlos Encoder. zb der Knopf: DK10901 ein herrlicher Knopf mit sandgestrahlter und schwarz eloxierter Aluminiumverschalung. Zu sehen hier: Gruss, Daniel

Hi there, while building the TPD as well, i decided that it should feature a "shade" because, you know... Vital in doing that, is finding the right "shade". Because, especially for the segment-displays, i found there is an issue with contrast when in daylight. Because the background of those segment-displays is grey and the activated segments are green, you can hardly see the green segments in favour of the grey background reflecting too much light. Crawling through the options available @ formulor.de (the german branch of ponoko, so the materials are available from them also) i found "mittelgrau, transparent" (with formulor) to be excactly what i was looking for. I have attached a picture for you to decide if you like it and the cutouts for the shades as .ai file (they match the frontpanel file available from ilmenator/TK. - thanks a bunch btw.) the .ai file: (there are cutouts for the displays also, i found them to be a little dark with it - but you can try for yourself) https://dl.dropboxusercontent.com/u/633384/seqv4_tpd_shade_cutouts.eps I hope you have a nice time around christmas! Best, Daniel

Hi there, while reconfiguring my NG a question came up. How can one configure the LEDs of one encoder in one bank to be "all off" because encoder X in bank X is always off and has no function? Thanks in advance for helping me. cheers Daniel

so then - be it :-)

greyt! thank you so much, ilmenator, for developing the tpd. and, of course, for the blm. they are THE addidtion for the seqV4!

countcountcount = 10?

Hi there, if you have a spare DIO_MATRIX Module pcb around and in or around Germany, it would be great if you would drop me a line. Cheers Daniel