eufex

:) Thank you Thorsten - that clears it all up.

Thanks for the link Thorsten - I've actually already seen that one - the pins are numbered sequentially from SR 1 onwards. But that is where the confusion is with: #define DEFAULT_DIN_SR_PIN_01_08 2 #define DEFAULT_DIN_SR_PIN_09_16 3 #define DEFAULT_DIN_SR_PIN_17_24 1 #define DEFAULT_DIN_SR_PIN_25_32 4 #define DEFAULT_DIN_SR_PIN_33_40 9 #define DEFAULT_DIN_SR_PIN_41_48 10 #define DEFAULT_DIN_SR_PIN_49_56 11 #define DEFAULT_DIN_SR_PIN_57_64 12 Where pin 1-8 is defined as shift register 2 and 17-24 as shift register 1. I wondered why this was so and what would happened if I renumbered them as I'm putting 128 pin outs on this particular core. Can anyone else answer?

I meant D fit knobs - you can get knobs with a D fitting for D shafts. I think some splined shafts have a different number of teeth to others (maybe).

They're M7 which I believe (someone please correct me if I'm wrong) is 7.9mm. W.R.T 'D'Â - yes you will be much better off finding D fit knobs. You may be able to get away with splined ones but there's no guarantee you will be able to get them on the pot/encoder without damaging them in some way. N.B. You can't fit splined knobs on round shafts.

;D Sorry - meant SmashTV. Don't know where I got Mike from...I've edited the post title so it makes sense now.

Looking at a single DIN handling buttons, the standard schematic has the 4 menu buttons on J3 (shift register 1). In 64E main.asm (64 is similar): #define DEFAULT_DIN_SR_PIN_01_08 2 #define DEFAULT_DIN_SR_PIN_09_16 3 #define DEFAULT_DIN_SR_PIN_17_24 1 #define DEFAULT_DIN_SR_PIN_25_32 4 #define DEFAULT_DIN_SR_PIN_33_40 9 #define DEFAULT_DIN_SR_PIN_41_48 10 #define DEFAULT_DIN_SR_PIN_49_56 11 #define DEFAULT_DIN_SR_PIN_57_64 12 But ; DIN pin numbers of menu buttons #if DEFAULT_ENC_DATAWHEEL == 0 #define DEFAULT_DIN_MENU_EXEC 7 ; menu exec button assigned to DIN pin #7 #define DEFAULT_DIN_MENU_RIGHT 6 ; menu right button assigned to DIN pin #6 #define DEFAULT_DIN_MENU_LEFT 5 ; menu left button assigned to DIN pin #5 #define DEFAULT_DIN_MENU_SNAPSHOT 4 In the schematic the pins from shift register 2-4 are numbered 1-24 - i.e SR 2 - pins 1-8, SR 3 = pins 9-16, SR 4 = pins 17-24 and SR1 is unnumbered. Going from that the first, second DEFAULT line matches and then it doesn't match. Then in the DEFAULT_DIN_MENU calls the pin numbering is different again because pins from SR 1 are numbered 4,5,6,7 as if counting 1 from the first pin on SR1. Is there something in one of the other application files that will explain this, or can anyone explain this as I'm totally confused.

Just thought I'd let everyone know that there are now pots at the store with metric shafts for all the people who are mixing pots and encoders on the same box (your knobs will now fit both) - SmashTV got me some of these in this week and very nice they are too - short shafts so you don't need to cut them too. The only thing to note is that the lug orientation is perhaps the opposite way around to the usual (i.e. for pot to move from 7 o' clock to 5 o' clock lugs are orientated at the top). Go get 'em :)

Farnell sell pot nuts - just type 'Pot nuts' in the search. Part number is: 351982

Thanks Thorsten - yes 80 of the buttons will be static, just sending out MIDI notes so that sounds good. Another option is to have 128 DINS on a MB64 application on one of th ecores I'm running - I see in another post that to do this the User_DIN-Notify Toggle hook needs to be enhanced - are there any other crucial areas to alter too (I guess the test app will show most of the way)/

I'm building a dual core box that has 64 analogue inputs and (at the moment) 192 digital inputs. Of the 192 inputs 19 are encoders, the rest buttons. I originally figured that one box could run MB64 and the other 64e - this was before i realised that as it stands 64e is set up for 64 buttons. Is what I want to achieve easily programmable or will I need to move to a third core? I've just spotted the test App for 64 Pots and 128 buttons - maybe this would be the basis for a solution (and also give me even more buttons to play with) Cheers

Hi. Yes you are missing the point slightly. The point is that Thorsten says you can mix and match on 64E - something which was refuted before. He then explains about 64E being able to cope with 128 MIDI parameter values and 64 button states. A state is 1 or zero yes? Which must mean that 128 parameters +32 buttons can be accomodated. If 64 of the parameters are analogue, that leaves another 64 for digital + 32 buttons or minus 32 buttons? As far as I knew the MB64E spec was 128 Dins, which means that you can, if you want ,connect 128 buttons or (say) 64 buttons and 32 encoders. You can see where the confusion is? Unless you have got a box up and running and have played around with the OS none of this is crystal clear. Of course I could be talking out of my jacksie?

illogic. I'm so very sorry that I've offended you. The fact of the matter is that this IS a forum and like any other forum isn't a definitive collection of information and contains plenty of information that is not totally correct. I've done plenty of seraching and plenty of reading believe you me. There isn't a definitive answer that I've been able to find. I was told in another thread that you can't mix pots with 64E easily without custom coding. Thorsten says different (and this must be correct). I was just clarifying what the spec is when mixing DINS and AINS. By the way your link doesn't work :P

Just for clarification ( I may be being stupid here but I asked this in another thread and was informed it was not possible). Can MIDIBOX 64E handle 4Dins, 4Douts and 2Ains - i.e. the full MIDIBOX 64E spec + 64 analogue inputs. Thanks.

;D wikkid

I'm putting an audiocard into the one I'm building. It doesn't interface with mbhp in any way - just a shared power supply. The idea is just so that I only have to cart 1 box about instead of 2. I managed to get a B stock Firewire audiophile - only had 3 months warranty on it but what the heck - I'm ripping it apart anyway. Sure beats the risk of lugging my MOTU about :)

That explains all. Thanks.

It's things like that which are good to hear about (although not good for you, money wise). Was it the current from your -ve contrast voltage that was too high as I thought the core board limits the current anyway via the resistor and transistor? I can see on your boards you've got current limiting resistors in there too for LEDs. Are the resistors in the Dout boards not large enough for your leds or have you got them there to alter the brightness, or another possibility, are they ground lifts?

Nice move :)

:) Sounding great. Can't wait to see it painted up. I see you've screwed your pot sliders top the board - did you manage to get ones that were at the correct height for your fader knobs or did you have to cut them down?

Finished the boards yesterday after about 24 hours solid soldering.

You've got 25 analogue ins and 111 digital ins (each encoder takes 2 digital inputs). Yes you're going to need 2 cores for that. MB64 spec is 64 Ains, 64 Dins, 64 LED MB64E spec is 128 Din, 128 Dout so even if you changed your analogue ins to encoders you're still going to end up using 2 cores. You're going to need some Dout boards if you want any indicator lights on there.

I'm in the process of building a box along similar lines with an audiophile fw in it - are you using the headphone out straight out? I'm in 2 minds as to whether to put a headphone amp in mine too as I don't the the fw output is going to be strong enough in some situations.

Boards and kits have arrived from SmashTV - I could have etched boards here but time is precious. The boards are fantastic - extremely well etched and silkscreened - I would recommend them to anyone. SmashTV has been really helpful with a couple of questions I had and with an error I'd made in the order. Great stuff  :)

Hi Lo Thanks for the info. Doing some programming doesn't scare me too much - I did a degree in microelectronics in the late 80s and early 90s and was quite handy programming 8 bit assembler on 68xx and 65xx systems plus the usual Pascal and C. Very rusty though. From what I've since gleaned it looks possible to have 1 LCD on a dual core box - the LCD goes on the 2nd core but as you say will probably involve some coding. The cardboard box sounds good I need to do some wood drilling too to get the correct sizes for the led buttons because according to the datasheet the caps are the same dimension all the way down but they feel (and logically) must be slightly tapered. I've got a good grasp of the hardware side of things now - I've got to do some reading on the soft/firmware side to get buttons/leds doing what I require etc and I'm still trying to get hold of that blasted data wheel. It will arrive...

This is a (very) quick mock up. I'm not decided about the square buttons and may go for something else. Ideally I want to get a USB trackball and 2 buttons into the case as well so I don't have to touch the computer at all when in a club but it depends on how much real esate this will all take. It may fit into the bottom left - I'll know better when I've decided on final components, measured and laid them out properly.