stuartm
-
Posts
172 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by stuartm
-
-
FAQ on page 38 of the manual:
Question: Can I use the MPK25 as a MIDI interface for other MIDI devices?
Answer: Yes. The MPK25 functions as a MIDI interface and can be used to send or receive MIDI from other MIDI devices connected to it.
So yes, you can plug you MB64 into the MPK25.
Since the MB64 sends only control data and no timing critical stuff (notes, midi clock), the latency shouldn't be a problem.
P.S.: Don't presume we hate "commercial stuff", we just found out that there's an even better way.
P.P.S: Greeting from the other end of DE :wink:
-
Unfortunately not - the effort to program a perfectly working conversion tool is higher at my side than writing down the notes/songs/maps on a paper and transfering them manually to MBSEQ V4 at your side.
Thanks, I kind of expected that. But I understand your point.
Playback on V3 to recording on V4 could also be an option, kind of reel to reel midiboxing :ahappy: )
-
Record function: it seems that it makes sense to provide a separate Record Port and Channel, and to make it selectable from the appr. page instead of hiding the selection in the MIDI configuration page.
I'd second that! I haven't been much in to Seq V4 lately (still have to order a Core32), but this would definately improve the live recording workflow.
On another topic (sorry if this has been answered before):
Is there a (convenient) way to migrate the data (songs, patterns, mixer maps) from the SeqV3 to the SeqV4 ?
-
Hi there,
i've recently did a MB64 myself, I started to write a build report in the Wiki, including how to mount parts and PCBs:
http://www.midibox.org/dokuwiki/doku.php?id=stuartm_stukontrol
See also the thread here:
Hope this help.
-
With the PIC core you have MIDIbox Seq V3, which can do 3 drum trigger layers per Track, making 16x3 = 48 "drum tracks".
However, don't forget that the DrumStation runs out of voices at about 7-8 drums in parallel :thumbsup:
-
I wouldn't say it is impossible, but quite overambitious.
Since every channel has same controls (EQ, Sends etc.), why not try to do some clever control integration.
Have a look at for example the recent Presonus 16.4.2:
Separate faders per channel but a common section for channel editing.
You would have to do just one channel strip and just come up with some clever channel selection.
But honestly, if I were to think about building a CONTROLLER of that size and that full access + buying the software,
I would go for the real console anyway.
Don't want to ruin your motivation, just my thoughts.
-
The buttons are standard, cheap Digitast buttons, I think TK recommended them for the MBSeqV3, that's where I saw and used them first.
They are not beauties, but I like their tactile behaviour, and their price of course.
(Example Link: DT6 at Reichelt )
-
Just for my education:
what are you doing with 140 buttons when controlling Traktor Scratch ?
My advice is just to take into account possibility/controllabilty versus usability (i.e. I recommend to use a lower number of knobs buttons I meant), before digging deep into a hardware solution.
-
Hi Mudi,
my MB64 is sending just MIDI CC values.
I've assigned them manually to the Live sets in session view.
I am not using any kind of template, but I thought about preparing one as my standard project when opening Live / starting a new track.
Over time, I've developed my own system of how to group tracks and how to layout controls.
For examples, drums on the right, bass to the very left and then melodic stuff etc.
The more I migrate my "old" Live sets to the new "MB64-controlled" sets, I tend to use the same layout, however, I always to the MIDI assignement manually.
A template would work for general clip start/stop and volumes, but I tend to use very different track control on the pots, e.g filter, pan, FX send, very much depending what is going on in that track and what is most usable in a live situation.
And yeah, I would very much like to see a function in Live to copy-paste MIDI assingments between projects.
My advice is to come up with your own structuring of tracks and controls
If you want to always have the Lead's filter on the same pot, go that way.
I tend to keep things variable and use the scribble strips to tell me which control is doing what.
Anyway, there's always a lot of preparation involved. It just depends on how much time you want to put into it and how convenient you want it to be when doing stuff live.
Finally, I still plan to do the full report, already started on the Wiki Article, but other things need my attention right now.
-
Das ist ein Crossfader, oder?
sieht diesem hier ähnlich: http://www.deejayladen.com/Ecler-Crossfader-SMAC-32-MAC-70-70i-90i-SMAC-42-Pro3__sca14907.aspx
Dann bräuchtest du auch nen passenden "schmalen" Schubser-Knopf, in dieser Art (für die Ecler gibts auch welche, aber ohne Bild)
http://www.deejayladen.com/Pioneer-Fadercap-DJM-Serie-300-500-600-DAC2355__sca14790.aspx
-
Great news!
Glad we could help, and don't worry, everybody starts as a noob ;)
-
It's finished!
I made a compact case of multiplex plywood to fit underneath the aluminium front panel.
Took some days to give it nice blue spraypaint finish, but luckily, the tone of the blue fits the panel quite well.
Also had a late idea how to fix the scribble strips, using laminated paper strips, two cannibalised IKEA plastic floor bearers, super glue and a hole puncher :)
See the attached pictures of the finished MIDIbox which is working just as smoothly as I planned with Ableton Live (more videos?)
Inspired by some very good articles in the Wiki, I decided to to the building report as a Wiki article during the holidays.
Oh, and not to forget the obvious:
Thanks TK and everyone around here who is supporting the project!
-
... a without-LCD controller. Something like just join a CORE module, some AIN modules and DIN modules ..
That's exactly what I did recently with my new Midibox64 (see )
-
I was looking for the same option for my Midibox64 recently.
The only thing I found was I think in the mk_syx .ini files it said somthing like "can be deactivated in the main*.asm" (not 100% sure).
I didn't find any entry in the .asm files.
Finally, I went for the dirty solutions and connected the affected four buttons to my second DINX module, since I had some open inputs left.
-
First thing to do when you want to build a MIDI controller is to read and read.. and read again
Exactly. It's not magic, but you have to understand how a box is build up, how the modules work together etc.
I also recommend to start with a Midibox64.
You can start easily with say 8 pots and 8 buttons, just too see if you can get it done without larger problems (and you don't spend a lot of money on parts you'll probably never use).
As the system can be extended easily, you can than build the MIDI controller you ever wanted.
I also recommend reading this forum alot, especially the stuff where people descibe how they are building MIDIboxes, what problems they encounter etc.
-
Check the voltages on the potentiometers (on the Vd input against ground, not the sliding contact).
Should be 5V.
If not, check the Vd pin of J7 on AIN against ground, should be 5V.
Try to exchange the multiplexer lines that go to the Core J5 (A0 to A7), put the cable of the non-working potentiometers multiplexer to another input, i.e. put the cable that goes to A4 to A5 and the cable that goes to A5 to A4 (if the potentionmeters on the A4 or A5 line do not work).
/edit: If I understand your posting correctly, the potentiometers not working are connected to the IC1 multiplexer of the AIN, so try to exchange the A0 line to another core input as described above.
Just try to systematically remove or exchange things until you get it working. That way you might find our if the fault is in the pots, their power supply, the AIN, the cable to the core or the core itself (I hope not!)
-
Those are not motorfaders, sorry
just simple 10kOhm faders connected to the AINX modules.
I will put up a full "report" of all the parts and the building process soon.
-
Thanks TK!
There will be more videos to come, as soon as I have adapted my Live songs to the exteded MIDI controllability I've got now.
Oh, I'm about to finish the casing next week, I'll get up pictures as soon as it's done.
-
And here's the inaugural performance of my new MIDIbox 64 with Ableton Live:
MB64 Inaugural Performance - Video on Vimeo
I'm off to bed now.
I'll write more about the building etc. soon.
-
DIN problems solved: bad soldering and mixed up cables :whistle:
However, IT'S FULLY WORKING !
Video of the first "performance" is currently uploading, see pic below for the MB64 ready for action
(actually, I haven't come up with a proper name yet ...)
-
Sorted out the AIN problem, one of the multiplexer lines was making trouble.
Still got the DIN bug to figure out, but all analog control are running fine. Test run went smoothly :)
Here's the picture update:
-
All the wiring is done.
First test run revealed there's still something wrong with one of the DINX modules (the core won't start) and one AINX still causes random MIDI events (some incomplete grounding of open inputs i suppose).
So I'm off for de-bugging tonight.
But the unit is fully wired, still quite compact and looks very nice (pictures will follow soon).
-
Hi stuartm, your controller is looking good! ;) how much $ was the panel?
Thanks!
The panel from Schaeffer was about 135 Euros, thats about 200 Dollars.
-
hi ultra,
yes I did. I've been scratching my head quite while to figure out how to integrate the Midibox and Live.
What I ended up with was either using LiveApi or waiting how MaxForLive turns out.
I decided to go for the "classic" controller first, also to improve my planning and "manufacturing" skills (my MBSeq was quite a mess).
I'll keep an eye on your LiveAPI stuff, right now I'm more in the building mood ;)
In the meantime, here are some photos:
Panel ordered from Schaeffer, already stuffed with 16 ALPS faders:
Main Control Button Board:
Mounting of the board:
Buttons in the panel:
Status as of yesterday:
Live Jams with Midibox SeqV3
in Songs & Sounds
Posted
I've no started to get my stuff on soundcloud, you may find there two tracks which I used in one of my MBSeqV3 Videos:
->