-
Posts
118 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by u-link
-
-
I have another little request / idea (which is born from my needs): at the moment, you can specify MIDI CCs to mute tracks. It would be amazing if you could chose to mute tracks via NOTES instead of CCs, too. Ideally, one would also be able to configure if "note on=track muted" or "note on= track unmuted". That would make mute automation a doddle in a DAW, you could simply have one MIDI track that sends out notes to mute and unmute tracks.
The reason for asking this is that i got some cheapo Akai controllers (Midimix and MPD218), and I would like to use one of them for track muting. The MPD218, which is a Pad controller with nice backlit pads, can't send CCs from the pads, and the Midimix's buttons cant be set to latch (and their backlighting only works with MIDI feedback, argh)!
-
41 minutes ago, gotkovsky said:
I asked for such a function a few months ago, except I called it ‘brocken chord’ instead of ‘strumming’. Still think it would be really nice as a parameter layer!
Sorry, I hadn't seen that. Would also be ace if the MIDI delay (one of my fave features) would allow for "spreading", kinda like a multitap delay, so some notes of a chord would be repeated at say 3/16 and others at 1/4 etc.
-
Has anybody ever proposed a "strum" feature on chords? So the start of the notes get broken up, like strumming on a guitar. It could be really simply implemented, maybe even just by assigning a parameter layer of a track with several pitch layers to be a roll layer.
-
I tried to connect a different motor fader (ALPS CP K.Fader), and this one works! I guess I'll just leave it at that and use those.
-
So, not too shabby, I think i figured my problem: these faders need higher voltage. I actually tried to connect some PSUs directly to a fader motor. 16V didn't do anything except some wiggling, 21.5V from an old Boss mixer PSU finally made it move! The faders were made to customer's spec it seems, maybe they are supposed to run on 24V?
The L293D can run up to 36V, the LM317 can also output 38V, I think, so would it be ok to connect a higher rated PSU to the MF_NG board? I would have to change the electrolytical caps, they are rated at 25V . The 7805 is already getting pretty dam hot, though, even with the 12V AC PSU I have connected now and a small heat sink. Maybe I could replace that with a switch mode regulator?
-
18 hours ago, Zam said:
"Stall current" is the current consumption when the motor is "lock", meaning want to move but can't, like mechanical stop end when you still ask him to move further. In short this is the max current the motor can ask.
Thanks a lot for clearing that up - makes a lot more sense than my assumption. I tried fiddling around a bit more, but the faders still won't move. The faders are actually looking a lot more like the earlier 3000 series P&G faders, they are open and supposed to move the wiper with a string, not with a belt. But even the data sheet of these guys has different wire colors listed than on mine, but i think i sorted that out. The touch sensor also works, but only when I touch the ground line with my other hand - there is a second ground wire for connecting the fader housing to ground (i think, which is what i did).
-
Hi! I am trying to get some faders moving, but up to now, they refuse to move. That's alright, "refusing to move" is a phenomenon that most people that produce dance music and perform it live or DJ might have experienced, it just takes some time, but you can normally lure the people into your groove. Well, IF they are people. Right now, they are NOT. They are P&G motor faders called PGFM3200. But an older version than the one i was able to find data sheets from. The wires have different color codes, but with some trial and (predominantly) error, I have manged to get the analog input working alright, with no jitter at all.
At the moment, I have only the first fader connected, and it is set to to output PB, I get values from -7936 to +7904. TBH, i don't even know what the complete PB range is, but as it's almost perfectly symmetrical, I just assume it's alright. However, the MOTOR doesn't do anything except some lame PWM growling, but no moving. It's my first time trying to get a motor fader to run, so please excuse my ignorance. The data sheet i found for the newer version of this fader says "stall current" is 0.54A. I guess "stall" means "not moving", and that seems like a lot of current for doing nothing - maybe the board (and the PSU) are not able to supply enough juice?
I am aware that there is not much action in this thread, but help would be appreciated! I even have spare faders to bestow upon ye that are helpful (because i was given a lot of them for free!).
Please see the attached photo for my (pretty simplistic) prototype layout.
-
I
2 hours ago, Hawkeye said:I've attached a "planned" silkscreen of the case for your convenience :). Light spill is imho really not bad, but you could always "tune" the Matias switch caps with a custom solution. No fixed inlay labels in the two upper rows, as their functions are dynamic! The upper Matias row is GP1-16 (i.e. enable/disable steps, menu functions), the lower Matias row is dynamic depending on the "round selection mode wheel". It could select tracks, steps, bookmarks, layers,... :)
Here are some promised update pictures:
The new v4+ UI PCBs, including the mini LED matrices and the integrated Beat LED, as requested by TK.! :)
A photoshop montage of the v4+ labels and the mini matrices. The final look may differ a bit, of course!
Thanks a lot for the info. So one could also go for switch caps that only have a transparent indicator line, similar to the ones on the TR-909 or the Cirklon. I personally would prefer that, as it gives a more focused indication. A friend of mine has the TR-8, and when we used it live in a club, it was annoyingly too bright (IIRC there's a dimmed setting, though, but it was still very bright). I also wonder if both the Matias switches and the round buttons won't outshine the displays?
I was asking about the labels because in the old thread, the idea for the transparent switch cap only came up in conjunction with the question on how to label the switches. Doing away with the Menu Shortcut names seems like a good idea, as these are shown on the screens as soon as you hit menu, and it will promote customization (on my Wilba panel, 16 is labelled "SYS EX" - not something I ever used, I put the remix function there). I for one would still like to see numbering from 1 to 16 in between the Matias rows or between the top row and the encoders. Anything that helps identifying a step at a glance is good IMHO.
-
Is my understanding correct that the final production case will be printed with the functions of the smaller round buttons, and that there's gonna be a set of labels to put into the transparent Matias knob caps? How is the "light spill" with the fully transparent knob caps? Would one ideally paint the caps' lower section from the inside (like an R/C car lexan body) so only the top ( where the printed inlay is transparent) lets trough light?
-
7 minutes ago, Smithy said:
Best way to buy Hawkeye a beer is to visit him in Munich! *2 beers maximum applies* ;)
Guys, I was wondering if all the feature requests TK has implemented in the firmware have been documented anywhere besides on the thread?
I haven't read through the MIDIbox manual on ucapps and the wiki extensively to make sure.It would be awesome to have an up to date manual for the SEQ V4(+). Since I've a lot of free time I could probably help out with that aspect.
I will gladly help out on that, too!
I saw pictures of Midibox meet-ups back in the PIC-days - are there anymore of those happening? If so, I would be delighted to join.
-
4 hours ago, Hawkeye said:
Of course:
44.5cm width (+ side screwheads, 1 or 2 millimeters on each side)
14 cm depth (front to midi ports)
8 cm height (standing on the table, incl. rubber feet) without the encoder knobs.
With encoder knobs, i'd say currently 9.5cm height, it should go down to 9.3cm - read below.
In conclusion: the case is really compact (for its contents!), we had to do some optimizations to have the waveshare MCU board fit in there, especially we need low-profile female headers on the wCore PCB. But these are available and unproblematic, now all works out. Do you have the Heidenreich case measurements for comparison? I'd be interested!
Regarding the encoder knobs: we will probably suggest to Adrian to counter-sink them "into the frontpanel", i.e. have bigger cutouts, like another famous sequencer out there :).
This has to do with them not scratching the frontpanel when pushing them down, and optimizing height for another few millimeters.Have a great weekend, y'all!
Many greets, PeterHey Peter,
I measured 43,8cm x 15,7cm x 8,8cm (WxDxH) on mine, including the rubber feet. Encoder knobs top and the (rounded) edge at the back are just about the same height.
You are actually using very tall encoder knobs on the pics. The tapered, low profile ones on the other famous sequen
tixcer do handle very well i gotta add!Thanks for info and have a nice weekend, too! BTW, do you not drink beer? Otherwise you should add a "buy Hawkeye a beer" signature, too. I'll also buy you an Apfelschorle if need be.
-
Could you post the dimensions of the unit? It looks like it might stand a bit taller than the Wilba Seq in the Heidenreich case, and in my setup (read: table with rack on top), there's not much spare room above it. When not doing music, I like to slide it underneath the rack. Thanks a lot!
-
Just now, latigid on said:
one channel is defined to work as a 0-5V gate input!
Well that's alright with me, too. Might be cool for spot erasing / overdub recording etc.
-
10 hours ago, lacuna said:
I just wish it would be possible to implement sth like a numeric keypad, such as the Yamaha QY700 had one.
Maybe with a shift-key-function (button-labeling 0123 would be required).
Or by addding an external computer-keyboard or USB-numpad...+1 for keypad - or even better, full ASCI keyboard support!
10 hours ago, latigid on said:Yep! And a stereo jack to boot, so one channel is defined to work as a 0-5V gate.
Nice one - I often wished to have just a single trigger out 'on board' to trigger a ducking gate for some sidechaining on a mixing desk bus insert!
-
Stunning work indeed.
Are you planning an "Analog Expansion Box" with CV/Gate/Triggers/Clocks in the same design? And what's the green illuminated port underneath the USB B? And the 1/8" jack? Footswitch input?
-
12 hours ago, MidiSlave said:
The "Duplicate FX" no longer works for me sending to any channel.
Is there something that I could have done to mess it up?
What have you set it to?
-
1 hour ago, k2z3k0 said:
yes that is exactly idea
in my mind it could make improvement for live performance
bests.k
It would also be great if one would be able to control track settings from within the track itself, eg. have a layer control the Delay Note +/- setting or the delay division. I find that using a second track to control a parameter of the first track eats up tracks fast (even more so if you use more than one, eg. with different lengths) and it's hard to remember which track did what. And the first step into that direction is, it seems to me, kinda taken already since TK added the transposition control for chord tracks from the same track.
But maybe we have to hold back a bit with more feature suggestions (taking to myself, mainly ;-))!
-
On 17.6.2018 at 1:30 AM, MidiSlave said:
anyone got the NRPN list for the robotizer effect?
I don't think it's implemented, at least I didn't find it on the list here: http://wiki.midibox.org/doku.php?id=mididocs:seq:beginners_guide:start#appendix_4_mbseqv4_cc_implementation
-
On 22.6.2018 at 8:54 AM, k2z3k0 said:
hi everyone
want to share with my idea for a tool ,kinda groovelizer
which would modify inside midibox tracks layers,
essentialy in my mind it could be simply one of the Track Type's
so you have to sacrifice one of midibox tracks
or maybe seperate module?
ok so my basic idea is-
Groovelizer Track Type(or module) would have one Groove sequence(or more),
would be great if it could keep regular track functions :Random Generator,Track Length,and Track Divider etc.
would be great if other Edit functions work too here
and each step of that sequence would be applied to each of the Groovelizer Layers
Groovelizer Track Type would have (for example) 8 Layers
each Layer contain Parameters:
-destination track nr
-destination track layer
-value range(value(from Groove sequence) div (select divider 1,2,3,4 etc.))
-Value mode:replace,replace inverse,add,sub (decides how value from Groove sequence is appplied to track layer value)
Main (EDIT)screen:
first row -Groove sequence
second row-(selectable) Layer Parameter(track nr,track layer,value range,value mode)
maybe it would be possible to have On/Off switch(encoder push),
when it goes ON,it makes snapshot of each(8) Groovelizer Layer currently set destination track layer's
when it goes OFF,it recals it them
of course would be nice to have also option to save current setting(Groove sequence,layer's params),maybe few slots for saving,maybe recall option too
please let me know what you think
bests
K
You mean some kind of meta-track that could control several other tracks instead of just one track? This would be great indeed! It would also be great to have some kind of a "horizontal mode" that would show one parameter for all 16 tracks. So EG you have all the dividers or directions or lengths or delays times at the same time - this might work well as an extension to the Mixer mode, I think. When I first got the Sequencer I actually thought you could use the Mixer for this, as in "just set to the appropriate CC that modifies the track parameter, eg. CC1 for controlling the Morphing on all channels".
-
19 hours ago, k2z3k0 said:
would it be usefull option among track settings that you can turn off or on,for midibox to send Note Off message when you Mute or Solo?
this way if you have for example longer sample(drumloop) on particular channel that you muting, this sample will be stoped by sampler,very handy
otherwise sample is still going after muting it,which could be not desired effect
and the same way Solo that will send Note off to every track that have this option on
i think this could nicely make mix clean
You are right, at the moment, the Note Off always gets sent when the note would finish without muting the track. An option to cut off the note immediately would indeed be handy!
On the same note: is there an Panic or All Notes Off button somewhere?
-
1
-
-
10 hours ago, Hawkeye said:
Thanks for pointing that out - have to ask Adrian, but it would make sense to also label the lower (blue) section of the case for consistency - the port names should be futureproof, we have 4 IN/OUT directly on the core and 4 OUT via IIC - it won't change in the future, even if there would be a newer core installed at some point in time.
Many greets,
PeterYou are welcome!
-
On 31.5.2018 at 7:46 PM, Hawkeye said:
Also, it is a prototype, we still need to add the "Beat LED" , and of course the label texts - as far as i would guess, it should be possible to label the backside ports on the "white portion" of the SEQ (the bent frontpanel), so this should work out.
So if you rack it, you'll have to do the labelling yourself on some masking tape or design a sticker. Maybe it's smart to have non-permanent port labelling: the function of some of the MIDI DIN-Plugs changed on mine when I exchanged the LPC17 Core with the STM32 and MIDI IO-Boards.
-
Looks extremely professional. A friend of mine always claimed that the Wilba-Seq looks like a shoebox :-)
Is there gonna be any labeling on the back I/O on the finished version? I quite like the colours, too.
-
As we're just tossing around ideas:
- "Morphing" (As on the Clavia / Nord synths): You select an input, channel, CC, you can set how much and in which direction it modulates any other CC on any output, allowing for very complex modulations at the touch of only one control. Ideally with modifiers etc. LFOs and Envelopes generated by the router itself as sources would be awesome, too!
- Support for microtonal scales would be interesting - I think Tubbutec's Microtune module might be a source of inspiration.
- BPM to Pitchbend calculator: A function that automatically calculates a Pitch Bend value to offset the tuning of loops in relationship to the actual BPM. Imagine you have some sampled percussion loops that are at 125 BPM, and you are playing at 128. You can enter both the original BPM of your loops and how many semitones your sampler detunes them in reaction to Pitch Bend. The router then calculates the needed PB value to send to the sampler patch so the loops are at the correct pitch (well, length, rather...). Something like :128/125=1.024, sampler pitchbends sounds 7 semitones, so PB value needed = XXXX
- A "performance mode", with split zones etc, both for keyboards and controllers.
- CC/NRPN/SYSEX presets for all kind of gear (can be added and exchanged by the community). So if someone figures out the Juno-106 SYSEX implementation, he can easily share it with all other users. Built in CC to NRPN/SYSEX (or even other CCs to standardize your implementation) conversion makes light work of automating such synths. This would even allow your controllers / sequencers permanently sending the same 16 or so CCs, and the conversion just takes place in the router. Pretty handy if you'd know that Parameter Layer 9, permanently assigned to CC12 on the MBSEQ is always changing Filter Env amount on all your synths. That would also be great to swap out different synths without having to change the assignments in the sequences!
- Editing of the CC to CC/NRPN/SYSEX conversion presets would be best in some kind of list editor (on a computer), vertical row shows incoming CCs, horizontal rows are all your synths. Now you can just select the function you want controlled in a cell via a drop down box.
Man, I never thought that thinking about a MIDI router could get me excited ...
-
1
Change default track setup globally or per session
in MIDIbox SEQ
Posted
Did you find a solution to this? I had my Seq for some years, and I always find the exact situation you describe unnecessarily complicated. I guess most people will assign a function to a track that'll stay the same in every session. Being able to "init" every pattern to have the same assignments would make life a lot easier. I actually work around it by switching Option 11/33: "Paste and Clear button will modify: Only steps VS. Complete Track". I then switch it back and just clear the sequence content in a next step.