midilab

yeah there are a lot of then, i had use one for the matter. But when talk about standards for seqv4 doc i want to know exacly the one TK had use.

any ideas on where can i upload the documentation images? basicly those are just images simulating a lcd screen, i know that people here use some sort of lcd screen generator also for midibox seqv4 documentation. Maybe someone can point me the direction booth to standardirize(where can i generate those screens like seqv4 doc) and avoid offsite problems(a server to upload the images) on that matter.

I had write a manual usage for Pattern Remix workflow for those wondering what it is all about. Documentation suggestions are welcome as well. http://midilab.co/midibox-seqv4-pattern-remix/ I had use a midibox seqv4 photo from user galery on this doc article, and if you're are that user and feels that its not good to have your photos outside this community please drop a line so i can delete the photo from the article or at least put your credits on the photo.

Hi you all! Doing some gear setup checking before traveling to berlin came out with this little 5 minutes jam. This Jam was recorded using Midibox SeqV4 using 8 tracks, Inversed Shuffle for all tracks with 16% of intensity for all of them. 1 pattern loop only. https://soundcloud.com/midilab/berlin-system-checkup Gears list: 8 Channels Virtual Analog Mixer Harrison Mixbus (Running on a miniitx PC headless and armless, controlled via MIDI used as main mixer, effects and emulations). MIDI Sequencer MIDIBOX Seqv4 4 voice analog synthesizer Davesmith Tetr4 Emulated 303 and 808 - VB303 and TS808 2 Channel Sampler loop machine Controllers - UC33 and Nanocontrol

Hi stuartm, I think the best way is to implement a new mixer parameter "bank change" to get everything work without overcomes... It will be a good enhancement to SeqV4 in my opnion! I know your pain to had to deal with bank changes... i have code a support for Sysex parameter inside Mixer page to overcome all the problem with program changes and bank changes. So in that way i could manage in a painless way the external gear presets and also have every detail of my work backuped inside my midibox session(if a lost the preset of that pattern inside my external gear... or even lost my gear, i could just buy another one and midibox dumps my work on the fly). I dump the external gear Sysex of each track to midibox that manages everything when i change patterns or remix track patterns inside Pattern Remix page. Best Regards, Midilab

Hi, Stuartm I got the bug other day, i realize that just mixer data for the group 1 of tracks(1, 2, 3, 4) are being dumped. - Bug fixed! I think TK will relaase this fix in the next sev4 firmware update. Best Regards!

I have tested at my side. Everything fine, but im not using wilba panel, maybe some problem related with HW Configuration? The famous read before post... problem solved. :)

Strange... I have test at my side and everything is ok, could you please confirm that theres no track markerd to be remixed when you do the pattern change? Some times a track could be in mixed state for a lot of pattern changes until you deselect him. If theres some track marked to be mixed down it will appears at the bottom of rigth LCD marked with a X... If nothing there, could you please send me a copy of your Session directory for me to trying to reproduce this and check if there are some environment config that could be affecting the dump of mixer tracks? What mixer map settings are not being sent? its only for a single track? more than one track? only one parameter? or there are more than one parameter not being sent? Best Regards, Midilab

I have think about some nice add to seqv4. Use Mixer to hold sysex data, so we can automate sysex dump during live sessions. How it will be? When you are inside Mixer page and select the 'new' parameter Sysex, you could just send your sysex setup and the Mixer page saves it for you, assign that sysex data to the track that have receive it. Internally how it works? We could use the /SYSEX/ dir to put all data inside like that: /SYSEX/MIXER/[MIXER_NUMBER]/[TRACK_NUMBER].syx So each time we dump a Mixer data, the Mixer also dump the sysex data for that track. For me! quite very ultra usefull to full backup of tracks, for example backup also the Synths sysex sound data. What you guys think? And what you TK think about the implementation of that stuff? Midilab []'s

I have notice that when you record something into sequence, the notes are recorded 1 octave up of what have being played.

Hope so... :) If someone code it, for shure it will run on stm. I have plans to code this, but i prefer to wait for Tk words of wisdom about it.. hes the father and knows his son better than us.

It will be preaty nice to have PRE and POST options for all FX section. Today all the FX are POST processed, if theres a option to easy choose between PRE and POST processing will be sooo nice! For me the PRE processing of effects will be preatty usefull for example to record the effects inside track. So when i found some EFX or a group of EFXs that fits well to the track i am working on it, i can record down the idea. without this option i always have to remember what kind of EFX params i have use for that specific track(no persistent data).

so i think its time to go and buy a LPCExpresso... :)