LO

Hi I am having a few problems with random midi data it doesnt happen that often but when it does it is very annoying looks something like this: 00001140 1 2 B1 4D 0C 2 --- Control Change 00001145 1 2 B1 4D 0F 2 --- Control Change 00001149 1 2 B1 4B 5A 2 --- Control Change 00001151 1 2 B1 4B 5B 2 --- Control Change 0000115D 1 2 B1 4B 5C 2 --- Control Change 00001162 1 2 B1 48 19 2 --- CC: Release Time 00001163 1 2 B1 4B 5D 2 --- Control Change 0000116F 1 2 B1 4B 5E 2 --- Control Change 00001178 1 2 B1 4B 60 2 --- Control Change 00001181 1 2 B1 4B 61 2 --- Control Change 00001191 1 2 B1 4B 63 2 --- Control Change 0000119B 1 2 B1 4B 64 2 --- Control Change this was when I was just moving 1 pot as you can see 1 lines data is different It only seems to occour when I am using MB_LINK and I was wondering if it could be to do with the length of cable im using? (approx 1.5mtr) it is a shielded cable but I do not have it earthed. I dont want to chop up the cable if this would not be the cause, as its a 25pin job and it will take forever to re-solder it Any thoughts? peace LO

A good protective lacquer: Electrolube- CPL (clear protective Lacquer) comes in a 200ml can for the equiv of about 5-6 euro's spray the board after etching, solder, then re-spray. EASY. I use steel-wool for cleaning tracks but this is not actually a good thing to use as the steel could make the copper corrode. ( I think? cant remember my school lessons!)

Another way to skin the cat: Open up the turntable and conect an encoder to the drive, as long as you have a high torque table should be OK Now you have a 3 wire conection to a midibox good for scratches, spin backs, whatever? But you will void your warranty! LO

Not sure but I think when you set up your controller in cubase you should be able to select transmit or recieve or both for each button, this might work?

mmmm OK good more things to try 8) Thanks

OK Some minor probs I tried using the ID change program but with no luck So I re-burnt the PIC with a header of :....00000112 (also tried ....000142) for "to com" = ON and device ID = 0x12 No luck when attempting to upload MIOS So I tried going back to my standard midi interface with a header of .....00000012 for "to com" = off device ID = 0x12 And still no luck Mios will not upload when ever I change the PIC header; I am changing the 00000000 number in the bottom right corner of IC-prog is this the right place? But its fine when I leave it with all zero's in the header! Do I need to change something in Midi-OX to send the data to the correct core now that it has a different ID? Also how do I learn what 0x12 means in normal numbers ie I want one core to have a device ID of 1 and the other 2 what do I enter in IC-prog? Help! :o

I wonder if this SID offer even came about? the last mention from OpiumX was in April Maybe it was only pipe dreams :P peace LO

I think you are right MB_64 I think already supports this but I have not had any luck making it work, I would like to know tho! ::)

blush... Â blush I dont think so The extension port: Basicly I have 2 cores & a sid in a 1U rack case One of the cores has 2 cables comming from it a 9 pin connector & a 25 pin connector. The 9 pin is for AIN extention devices only. The 25 pin (pictured) contains lines for MB_link (if required) DIN, AIN DOUT modules. Therefore I can connect the traktor module, which only contains 1xAIN & 1XDIN or unplug and connect the other module which contains Motor faders, additional core etc etc. When Modules are not connected I have "blank" plugs to fit on the ends of the cables which earth the AIN's to stop them going crazy The wires inside are a bit of a mess! I struggle to remember what I have done every time I need to open it up! (just finished upgrading to 18F's phew...) The overlay is a decal done with Lazertran (designed with CAD & Illustrator) and baked in the oven was actually very cheap to make! My brother is a wood worker (plenty of offcuts!) & some people owe me favours! ie laser cutting panels etc. cheer LO

this also makes good sense Thank-you 8)

OK thanks Makes sense! While Im on the topic of MB Link Should it be possible to send sysex or applications ie MB_MF to the Second/last core in the chain without removing the first core? I have gone in to the sysex dump menu and changed the first core to device ID 1 and the second to device ID 2 When I attempt to send sysex via vmidibox I can get the first core to recieve the dump but when I change the device ID to 2 and resend the second core does not receive the dump. Thanks LO

Hi I have been busy trying to get my MB's upgraded to 18F's and the new Mios & firmware. I may have found a potential bug or maybe I am doing something wrong? Whenever I set the midi config to MBLINK ForwardPoint or EndPoint and "To Com=Yes" and then afer I turn the box off & on again it has lost the setting for "To-Com=Yes" Â ??? It always reverts back to Off! it seems to keep all other settings I have have tried this with & without a bankstick; no diff! Could someone else please confirm this behaviour? Cheer LO Edit: I am using MB64 2.1 & Mios 1.4b (also happens in the MB_MF new firmware?)

Hi Pilo Thanks :) The transport buttons were very easy The local surplus shop has these buttons with a removeable clear plastic top all I did was to pop the top off then print a design on the inkjet and stick it underneath. peace LO

Not sure about the MTC (but I would like to know) As far as the MF's (motorfaders that is!) go: of course that is one of the main advantage for me of having motorfaders, whenever you open a new track the faders jump straight to the correct position! peace LO

Huh??? What about all the PCBs @ uCapps? there are PCBs done in eagle for every board, should be good examples; or is that not what you are wanting? oh.. is it just the .sch file and not the .brd perhaps?? LO

Not much help but... have you not got an LCD just change it via the menu if you have

I'll do it ;D peace LO

Man I gotta build me one of those microwave guns! :o

excellent ;) peace

Hi The sysex string does not appear on the LCD it appears in the midiox monitor window when you turn power up. The blocks on the LCD could be OK, you know you have to send the mios within 2 seconds of power on aye? Once MIOS is loaded then the LCD comes to life it should say "ready." If the JDM says verified all should be OK for the bootstrap I found that sometimes you must send the MIOS more than once? dont know why? LO

Just play around with the show/hide options but you def want the pads LO

0.5A fuse is good but anything up to 1A should be enough protection but get a few cause if you are like me youll blow a few while fault finding

"Warm" ? yes some people have reported their SID getting real hot... to the point of needing a heatsink! (esp the 6581's) so dont despair yet Triple check those traces are you getting 1mhz via core PIC? tried playing a note via jsynth? peace LO

Could you post this firmware at the portal? I too would be interested in this Cheer LO

This is simple just go to device setup and add a generic controller then you can use the learn function Dont you have the Cubase SX manual? it gives a pretty good description in there LO