Rowan

Hi All, I've just come across the holy grail of button parts! http://www.mpcstuff.com/pad-sensors-with-ribbon-for-mpc.html and http://www.mpcstuff.com/akai-mpc-pad-set-grey.html So who is going to be first?

The ones that are mounted horizontally are DIN's and the ones mounted vertically are DOUT's (apart from one which is a DIN. It's just there at the moment so each module is the same hight). the 3 encoders on the top left of the modules have built in switchs, so thats an other 3 DIN's. There will also be 2 more panel mount switchs per module, 2 more DIN's. The faders I will be using have an extra switching track, like "fader start" on some DJ mixer. 26+3+2+1=32 ;) Each Module will require 15 DOUT's, so one 4xDOUT PCB will be shared between two modules.

Thanks, I spent ages planning the layout, I like things tidy. It makes it easier to fault find. Each of the 3 "channels" are made exactly the same so I only had to plan how to make one then just make copies. I think that I'll order the panel next, but I still haven't made up my mind on the layout of the last section. So I'm kind of at a dead end until I can decide.

After about 9 months of ignoring my MB project I thought it was about time to start working on it again. Here are some picture of its current state. All the DINs are up and running, all the buttons and encoders are working. I've got to spend some time wiring up the LED's now and have the panel made. Off to go buy a new soldering iron now :) Rowan

Sorry this is OT but I have to mention it here; I first discovered the MIDIbox because of synthedit. In 2002-2003 I was well into building plug-ins with synth edit and I needed a controller for them. After some searching the synthedit fourms I found ucapps......and here I am after all these years, and I haven't made a VST plug since ??? If my music PC was working at the moment I'd test your Plug, but the PSU is dead >:(

Due to a number or requests.........she's back ;)

Dunewar, I'm pleased you're up for the challenge, and trust me it will be exactly that. You'll end up spending twice as much on the parts alone. I'm not trying to discourage you, but beware if you're up for it you'll lose all touch with reality ;) Back to the point at hand. The HUI protocol has never been publicy released as far as I know. If you want to create an emulation of it you will have to reverse engineer it by getting a controller that supports it an spend a lot of time working out the data structure. It's really not a job for the faint hearted! Do you see the catch 22? Pro Tools can support up to up to 4 x 8 channel controllers (discounting the Icon system) so the CS-10 route would be the simplest way to go. Each controller needs it's own midi port. Food for thought. OT Screaming Rabbit - What DAW do you use? Nuendo? Pryamix?.......I'd be interested to know, as I've seen your PT bashing come up time and time again Rowan

Take a look at this puppy........ :o http://www.jlcooper.com/pages/oem.html drool.....drool

Welcome aboard :D Unforunatly your options are rather limited, as digidesign are very closed in what control surfaces they support. Currently digi only officially support their own controllers, though unofficially a few 3rd party controllers are supported. I haven't checked out what controllers are supported in PT M-Powered, but I will assume that it's the same as PTLE. Off the top of my head I would say that you have 2 choices. a/ Build a MBLC but load the MBMM (emulation on the CM Labs Motor Mix) Firmware. I have done very basic test with this firmware loaded onto a Core with a 40x2 LCD connected with PT TDM 6.4.1 and the display worked as expected. b/ Chose the JL Cooper CS-10 as the controller option and program a MB64 to emulate it. The manual has the Sys-Ex data structure on page 30 http://www.jlcooper.com/pages/CS10.html# a/ is the best option and b/ is the cheaper option. as for the master fader you are out of luck as far as I know. Nither controller supports a master fader. Last years someone had apperently written a firmware emulating the Mackie HUI but he seems to have disappeared from the forum and he never relased his source code, Bummer! An HUI emulation would the best solution. To be perfectly honest, unless you really want to build a controller, go buy a Behringer BCF2000 or one of the few remaining Tascam US2400's (If you can find one that is. discontinued due to ROHS) as they both have perfectly good HUI emulations. Hope that helps. Rowan

Might have to mod my US-2400 ;)

To right, the best book I've ever read about practical audio. He has some amazing insights.

Hi All, I'm about to move and i've got more switchs than I care to think about......So it's time for a clear out. I've got 400 x 96-302.807 EAO switchs....................These fit matrix board!!!!!!!!!!!!! Please note that I am only selling switchs, you will need to buy caps from someone else. These are the ones that can take 2 x 3mm LED's (or RGB LED's if you know what you are up to). These are only the switchs, NO CAPS ARE INCLUDED! The price is £0.50 each (about a third the price in medium size quantities) Data is avalible here http://www.eaoswitch.com/pcbs/96.htm Caps can be brought from here http://www.elfa.se/en/ Just search for "EAO 96 Switch Key" Shipping costs will depend on your location, but I will NOT charge more than my actual shipping cost to you. If you are interested please PM me. Regards, Rowan

Form the Euphonix MC, Tasty!

Hi, I've got 8 that I could sell you. I'm in Glasgow. P.M. and I'll tell you the details. Regards, Rowan

This should sort you out http://www.midibox.org/forum/index.php?topic=3980.0 happy twiddling ;)

Ok, I'm back from my hiatus from MB Land. I had to take a well deserved brake from my every day life...........I've spent a few very nice weeks on a beach soaking up sun (and rain). My chips arrived while I was away so I to have a stash to cook while we try to develop a MB1000, well I think that it will end up better than a Matrix 1000. So I guess it is down to us now to nut out some ideas on how to get this to work. As the data sheet states the chip runs off CV's and some timing signals for the waveform converter. After looking at the datasheet the suggested configuration uses 4051's to multiplex the CV's........how about using the AIN module in reverse (i.e. running the PIC pins as DAC's rather than ADC's) ? I don't know how this could be done, but 4051 can drive the CV inputs of the chip (as done on the matrix 1000). Just a hair brained scheme....? Rowan

Yeah your right the MMT-8 rocks. I use to own one. Great for live use. But sadly the MC-500 is a different beast, fine for playing MIDI files, I wouldn't want to have to do much more than that on one. At least with the MMT-8 you can mute tracks quickly on the fly. Rowan

MC-500...............don't go there.........we have computers now ;)

Ilmenator, 2 are set aside for you. I'll PM you when I've worked out the cost (sorry i'm busy as hell at the moment, off on holiday tomorrow so I got to pack and clean the house not to mention keep my clients happy ;)). SPL, I don't want to be rude but I'd rather thay went to some one who can help working on developing a new MBHP module. If you have some useful skills they are yours. Please don't be offended but if you can't work out from the datasheet what type of filter it has they will go to waste, when someone else may want them that could contribute to this. I think it would be in your interest to hold off untill a working solution is available. Any other time served memebers interested? Rowan

Cool, They are really just inventory for me as well. I'm guessing about £5-8 each I'll just need to work out all my costs and sell them on at my cost price. Rowan

Sorry ;) Small world Do you want 2 of them? I really only want 2 so there are 4 free for people who will put them to good use i.e. use them for an MB

Hi All, I just picked up 6 CEM3396's on eBay for next to nothing, hoping that in the future I may be able to make use of them for a MB based project (Once I've got even half a clue about C :P) Here is the data sheet: http://www.synthtech.com/cem/c3396pdf.pdf you can also by them from the above site: http://www.synthtech.com/cems.html By the look of things they could be used for a very nice synth, they are the voice chips from the much underrated Matrix 1000. Has anyone looked into using these chips before? Cheers, Rowan

I've got dibs on the Motorfaders................PLEASE DON'T OUT BID ME ;) I'm getting close to finishing my Ableton Live controller so it's time to start gathering parts for my next project, the Motormix clone for my new (secondhand) Protools TDM system. Here are some cheap 40 x 2 LCD's http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&ih=010&item=200019353422&rd=1&sspagename=STRK%3AMEWA%3AIT&rd=1 Though they must be brought in lots of 10 :P , Still cheap but. Thanks

I forgot to include MIOS_SRIO_UpdateFrqSet, MIOS_SRIO_NumberSet, MIOS_SRIO_DebounceSet in Init() :P Now the app is initiaizing properly. Thanks Michael, I'll be back....... Rowan

A.C. Can you take a look at this and give me a clue where I'm going wrong. The code complies fine, but once I've uploaded it it doesn't do jack ??? The LED's don't even go to the inital state. /* * MIDIfire Version 0.0.1 * * ========================================================================== * * Copyright (C) <2006> <Rowan Spicer> (******@******.com) * Licensed for personal non-commercial use only. * All other rights reserved. * * ========================================================================== */ //////////////////////////////////Thanks/////////////////////////////////////// // Thorsten Klose, Audiocommander, Smash TV // ////////////////////////////////////////////////////////////////////////////// #include "cmios.h" #include "pic18f452.h" #define MIDI_NOTE_ON 0x90 // 144, on CH1 #define MIDI_NOTE_OFF 0x80 // 128, on CH1 #define DIN_BUTTON_START 5 #define DIN_BUTTON_STOP 7 ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS after startup to initialize the // application ///////////////////////////////////////////////////////////////////////////// void Init(void) __wparam { // Initialize Clip Launch LED's MIOS_DOUT_PinSet(0,0); MIOS_DOUT_PinSet(1,1); } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS in the mainloop when nothing else is to do ///////////////////////////////////////////////////////////////////////////// void Tick(void) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is periodically called by MIOS. The frequency has to be // initialized with MIOS_Timer_Set ///////////////////////////////////////////////////////////////////////////// void Timer(void) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when the display content should be // initialized. Thats the case during startup and after a temporary message // has been printed on the screen ///////////////////////////////////////////////////////////////////////////// void DISPLAY_Init(void) __wparam { MIOS_LCD_Clear(); MIOS_LCD_CursorSet(0x00); MIOS_LCD_PrintCString("Hello World!"); } ///////////////////////////////////////////////////////////////////////////// // This function is called in the mainloop when no temporary message is shown // on screen. Print the realtime messages here ///////////////////////////////////////////////////////////////////////////// void DISPLAY_Tick(void) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a complete MIDI event has been received ///////////////////////////////////////////////////////////////////////////// void MPROC_NotifyReceivedEvnt(unsigned char evnt0, unsigned char evnt1, unsigned char evnt2) __wparam { switch(evnt1) { case MIDI_NOTE_ON: // Note on received if(evnt0 == 0x90) { MIOS_DOUT_PinSet(0,1); //LED 1 On MIOS_DOUT_PinSet(1,0); //LED 2 Off } break; case MIDI_NOTE_OFF: //Note off is received if(evnt0 == 0x80 || evnt2 == 0x00) { MIOS_DOUT_PinSet(0,0); //LED 1 Off MIOS_DOUT_PinSet(1,1); //LED 2 On } break; } } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a MIDI event has been received // which has been specified in the MIOS_MPROC_EVENT_TABLE ///////////////////////////////////////////////////////////////////////////// void MPROC_NotifyFoundEvent(unsigned entry, unsigned char evnt0, unsigned char evnt1, unsigned char evnt2) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a MIDI event has not been completly // received within 2 seconds ///////////////////////////////////////////////////////////////////////////// void MPROC_NotifyTimeout(void) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a MIDI byte has been received ///////////////////////////////////////////////////////////////////////////// void MPROC_NotifyReceivedByte(unsigned char byte) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS before the shift register are loaded ///////////////////////////////////////////////////////////////////////////// void SR_Service_Prepare(void) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS after the shift register have been loaded ///////////////////////////////////////////////////////////////////////////// void SR_Service_Finish(void) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when an button has been toggled // pin_value is 1 when button released, and 0 when button pressed ///////////////////////////////////////////////////////////////////////////// void DIN_NotifyToggle(unsigned char pin, unsigned char pin_value) __wparam { switch(pin) { case DIN_BUTTON_START: // Clip Start button pressed (core sends note on) if(MIOS_DIN_PinGet(0) == 0) { //LED 1 Flashing MIOS_DOUT_PinSet(1,1); //LED 2 On } break; case DIN_BUTTON_STOP: // Clip stop button pressed (core sends note on) if(MIOS_DIN_PinGet(1) == 0) { MIOS_DOUT_PinSet(0,1); // LED 1 On // LED 2 Flashing } break; } } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when an encoder has been moved // incrementer is positive when encoder has been turned clockwise, else // it is negative ///////////////////////////////////////////////////////////////////////////// void ENC_NotifyChange(unsigned char encoder, char incrementer) __wparam { } ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a pot has been moved ///////////////////////////////////////////////////////////////////////////// void AIN_NotifyChange(unsigned char pin, unsigned int pin_value) __wparam { } I know my hardware is fine as it works with the test apps and C examples. I am also a little confused as to the comments that you added to the defines #define MIDI_NOTE_ON 0x90 // 144, on CH1 144, on CH1? What does the 144 relate to? Thanks mate, Rowan