antonybest

Hello people! I don't suppose anyone would take some time and just explain some questions please? I want to know how by pressing a button it is converted into a midi note and velocity please! I understand how by pressing a button it goes above a certain voltage which means that the button is on etc, I understand flip-flops and how the shift registers work, i know how the 'on' signal gets to the PIC pin I also understand that when it reaches the PIC the function is listed in the io_tables.inc, but then I get lost! How does the software interpret that into a midi note? where is the code so that I can see this happening? I understand that it converts it into a note so that the mackie protocol can understand it, i'm just missing that last piece in the jigsaw puzzle! If someone could help me it would be much appreciated! Thanks Antony

Hello, Thanks for replying! I have found the problem, it was a dodgy bit of soldering shorting several inputs together and causing these random messages, the problem is now solved and the MBLC is working like a charm! Only a few problems to iron out but nothing major! Thanks Antony

Hello Guys, I was wondering if anyone could help me please, I have, literally today, put together my MBLC, on my LC there are 8 MFs, 42 buttons. Therefore I have only used 7 shift registers (including touchsensors), I have changed the mapping in io_table.inc and have changed all unused shift registers to ID_IGNORE, is this the correct way to do it first of all? In the main .asm file I have said that there are only 7 registers being used. When I uploaded the hex file in mios studio it said upload successful, so I booted it up the LCD flashed something I thought wow it might actually work! How wrong I was! For some reason the LEDs on shift regsiter 5 & 6 all light up, then I looked in MIDIIn on mios studio and this was happening: 00000000129867 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129875 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129877 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129884 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129886 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129893 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129895 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129898 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129900 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129907 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129907 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129926 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129928 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129933 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129935 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129941 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129943 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 00000000129948 ms | [90 14 7F] Channel 1: Note On G#0 velocity: 127 00000000129950 ms | [90 14 00] Channel 1: Note On G#0 velocity: 0 There were other note ons, too many to mention! This was happening by itself, does anyone have suggestions at why this maybe? I then thought I would open Cubase, I set it up but these random messages were sending it hay-wire, starting and stopping recording selecting various channels, you get the idea! I don't know if anyone can help me because I really don't know where to go from here! Your help would be much appreciated! Thanks Antony

Hello, I have burned some 18F452s with the v1.2 bootloader, I then plugged it into MIOS studio and opened the MIDI In window, the sysex message appeared: F0 00 00 7E 40 70 01 F7 The 70 should be 00 according to MIOS Studio because when I tried to burn the MIOS v1.9 hex file it would not load! Any Ideas? Thanks Antony

Hello, Just a quick question! To get a PIC18F452 to work with LC I have to burn bootloader via a pic burner and can I then load MIOS V1.9 via MIOS Studio? Then load my application via MIOS Studio also? Thanks Antony

Hello, This is probably a silly question but on TK's LC project on ucapps the motorfader caps look like they are made of metal. I was wondering whether this maybe to do with the touch sensor or not? Also where is it possible to buy the fader caps to? Thanks Antony Best

Sorry forgot to write everything in the last reply, the select buttons were are they on the picture of the LC? Are they the buttons at the top of channel strips? When you say control a value does this include mute/solo/record arm/fader position? or just the assignable V pots for EQ, pan etc? Thanks

Hello, Thanks DOC for your help it makes so much more sense! The sections in the main.asm file for the rotary encoders and v-pots etc can all just be ignored then I take it? Thanks for your help! Antony Best

Sorry and one other thing, I have ommited: #define ID_SELECT_CHN1 0x18 ; o o #define ID_SELECT_CHN2 0x19 ; o o #define ID_SELECT_CHN3 0x1a ; o o #define ID_SELECT_CHN4 0x1b ; o o #define ID_SELECT_CHN5 0x1c ; o o #define ID_SELECT_CHN6 0x1d ; o o #define ID_SELECT_CHN7 0x1e ; o o #define ID_SELECT_CHN8 0x1f ; o o Are these essential for what I need the LC for? Thanks Antony Best

Hello! My project that I am doing is the LC, I am not using all of the functions of it though just a selected few. I saw the file lc_io_table in the LC V1.6 folder and noticed that each button was assigned its on number, obviously! As I am not using all of the functions can I change what each button is assigned to for example: #define ID_REC_RDY_CHN1 0x00 ; o o #define ID_REC_RDY_CHN2 0x01 ; o o #define ID_REC_RDY_CHN3 0x02 ; o o #define ID_REC_RDY_CHN4 0x03 ; o o #define ID_REC_RDY_CHN5 0x04 ; o o #define ID_REC_RDY_CHN6 0x05 ; o o #define ID_REC_RDY_CHN7 0x06 ; o o #define ID_REC_RDY_CHN8 0x07 ; o o #define ID_SOLO_CHN1 0x08 ; o o #define ID_SOLO_CHN2 0x09 ; o o #define ID_SOLO_CHN3 0x0a ; o o #define ID_SOLO_CHN4 0x0b ; o o #define ID_SOLO_CHN5 0x0c ; o o #define ID_SOLO_CHN6 0x0d ; o o #define ID_SOLO_CHN7 0x0e ; o o #define ID_SOLO_CHN8 0x0f ; o o #define ID_MUTE_CHN1 0x10 ; o o #define ID_MUTE_CHN2 0x11 ; o o #define ID_MUTE_CHN3 0x12 ; o o #define ID_MUTE_CHN4 0x13 ; o o #define ID_MUTE_CHN5 0x14 ; o o #define ID_MUTE_CHN6 0x15 ; o o #define ID_MUTE_CHN7 0x16 ; o o #define ID_MUTE_CHN8 0x17 ; o o #define ID_SELECT_CHN1 0x18 ; o o #define ID_SELECT_CHN2 0x19 ; o o #define ID_SELECT_CHN3 0x1a ; o o #define ID_SELECT_CHN4 0x1b ; o o #define ID_SELECT_CHN5 0x1c ; o o #define ID_SELECT_CHN6 0x1d ; o o #define ID_SELECT_CHN7 0x1e ; o o #define ID_SELECT_CHN8 0x1f ; o o #define ID_VPOT_SELECT_CHN1 0x20 ; o - #define ID_VPOT_SELECT_CHN2 0x21 ; o - #define ID_VPOT_SELECT_CHN3 0x22 ; o - #define ID_VPOT_SELECT_CHN4 0x23 ; o - #define ID_VPOT_SELECT_CHN5 0x24 ; o - #define ID_VPOT_SELECT_CHN6 0x25 ; o - #define ID_VPOT_SELECT_CHN7 0x26 ; o - #define ID_VPOT_SELECT_CHN8 0x27 ; o - #define ID_ASSIGN_TRACK 0x28 ; o o #define ID_ASSIGN_SEND 0x29 ; o o #define ID_ASSIGN_PAN_SURROUND 0x2a ; o o #define ID_ASSIGN_PLUG_IN 0x2b ; o o #define ID_ASSIGN_EQ 0x2c ; o o #define ID_ASSIGN_INSTRUMENT 0x2d ; o o #define ID_BANK_LEFT 0x2e ; o - #define ID_BANK_RIGHT 0x2f ; o - #define ID_BANK_CHANNEL_LEFT 0x30 ; o - #define ID_BANK_CHANNEL_RIGHT 0x31 ; o - #define ID_FLIP 0x32 ; o o #define ID_GLOBAL_VIEW 0x33 ; o o #define ID_NAME_VALUE 0x34 ; o - #define ID_SMPTE_BEATS 0x35 ; o - #define ID_F1 0x36 ; o - #define ID_F2 0x37 ; o - #define ID_F3 0x38 ; o - #define ID_F4 0x39 ; o - #define ID_F5 0x3a ; o - #define ID_F6 0x3b ; o - #define ID_F7 0x3c ; o - #define ID_F8 0x3d ; o - #define ID_GLOBAL_TRACKS 0x3e ; o - #define ID_GLOBAL_INPUTS 0x3f ; o - #define ID_GLOBAL_AUDIO_TRCK 0x40 ; o - #define ID_GLOBAL_AUDIO_INSTR 0x41 ; o - #define ID_GLOBAL_AUX 0x42 ; o - #define ID_GLOBAL_BUSSES 0x43 ; o - #define ID_GLOBAL_OUTPUTS 0x44 ; o - #define ID_GLOBAL_USER 0x45 ; o - #define ID_SHIFT 0x46 ; o - #define ID_OPTION 0x47 ; o - #define ID_CONTROL 0x48 ; o - #define ID_CMD_ALT 0x49 ; o - #define ID_AUTOM_READ_OFF 0x4a ; o o #define ID_AUTOM_WRITE 0x4b ; o o #define ID_AUTOM_TRIM 0x4c ; o o #define ID_AUTOM_TOUCH 0x4d ; o o #define ID_AUTOM_LATCH 0x4e ; o o #define ID_GROUP 0x4f ; o o #define ID_UTIL_SAVE 0x50 ; o o #define ID_UTIL_UNDO 0x51 ; o o #define ID_UTIL_CANCEL 0x52 ; o - #define ID_UTIL_ENTER 0x53 ; o - #define ID_MARKER 0x54 ; o o #define ID_NUDGE 0x55 ; o o #define ID_CYCLE 0x56 ; o o #define ID_DROP 0x57 ; o o #define ID_REPLACE 0x58 ; o o #define ID_CLICK 0x59 ; o o #define ID_SOLO 0x5a ; o o #define ID_REWIND 0x5b ; o o #define ID_FAST_FWD 0x5c ; o o #define ID_STOP 0x5d ; o o #define ID_PLAY 0x5e ; o o #define ID_RECORD 0x5f ; o o #define ID_CURSOR_UP 0x60 ; o - #define ID_CURSOR_DOWN 0x61 ; o - #define ID_CURSOR_LEFT 0x62 ; o - #define ID_CURSOR_RIGHT 0x63 ; o - #define ID_ZOOM 0x64 ; o o #define ID_SCRUB 0x65 ; o o #define ID_USER_SWITCH_1 0x66 ; o - #define ID_USER_SWITCH_2 0x67 ; o - #define ID_FADER_TOUCH_CHN1 0x68 ; o - #define ID_FADER_TOUCH_CHN2 0x69 ; o - #define ID_FADER_TOUCH_CHN3 0x6a ; o - #define ID_FADER_TOUCH_CHN4 0x6b ; o - #define ID_FADER_TOUCH_CHN5 0x6c ; o - #define ID_FADER_TOUCH_CHN6 0x6d ; o - #define ID_FADER_TOUCH_CHN7 0x6e ; o - #define ID_FADER_TOUCH_CHN8 0x6f ; o - #define ID_FADER_TOUCH_MASTER 0x70 ; o - #define ID_SMPTE_LED 0x71 ; - o #define ID_BEATS_LED 0x72 ; - o #define ID_RUDE_SOLO_LIGHT 0x73 ; - o #define ID_RELAY_CLICK 0x74 ; - o This is the original file, can I change it to something like this? #define ID_REC_RDY_CHN1 0x00 ; o o #define ID_REC_RDY_CHN2 0x01 ; o o #define ID_REC_RDY_CHN3 0x02 ; o o #define ID_REC_RDY_CHN4 0x03 ; o o #define ID_REC_RDY_CHN5 0x04 ; o o #define ID_REC_RDY_CHN6 0x05 ; o o #define ID_REC_RDY_CHN7 0x06 ; o o #define ID_REC_RDY_CHN8 0x07 ; o o #define ID_SOLO_CHN1 0x08 ; o o #define ID_SOLO_CHN2 0x09 ; o o #define ID_SOLO_CHN3 0x0a ; o o #define ID_SOLO_CHN4 0x0b ; o o #define ID_SOLO_CHN5 0x0c ; o o #define ID_SOLO_CHN6 0x0d ; o o #define ID_SOLO_CHN7 0x0e ; o o #define ID_SOLO_CHN8 0x0f ; o o #define ID_MUTE_CHN1 0x10 ; o o #define ID_MUTE_CHN2 0x11 ; o o #define ID_MUTE_CHN3 0x12 ; o o #define ID_MUTE_CHN4 0x13 ; o o #define ID_MUTE_CHN5 0x14 ; o o #define ID_MUTE_CHN6 0x15 ; o o #define ID_MUTE_CHN7 0x16 ; o o #define ID_MUTE_CHN8 0x17 ; o o #define ID_BANK_LEFT 0x18 ; o - #define ID_BANK_RIGHT 0x19 ; o - #define ID_BANK_CHANNEL_LEFT 0x1a ; o - #define ID_BANK_CHANNEL_RIGHT 0x1b ; o - #define ID_AUTOM_READ_OFF 0x1c ; o o #define ID_AUTOM_WRITE 0x1d ; o o #define ID_AUTOM_TRIM 0x1e ; o o #define ID_AUTOM_TOUCH 0x1f ; o o #define ID_AUTOM_LATCH 0x20 ; o o #define ID_REWIND 0x21 ; o o #define ID_FAST_FWD 0x22 ; o o #define ID_STOP 0x23 ; o o #define ID_PLAY 0x24 ; o o #define ID_RECORD 0x25 ; o o #define ID_CURSOR_UP 0x26 ; o - #define ID_CURSOR_DOWN 0x27 ; o - #define ID_CURSOR_LEFT 0x28 ; o - #define ID_CURSOR_RIGHT 0x29 ; o - #define ID_ZOOM 0x2a ; o o #define ID_FADER_TOUCH_CHN1 0x2b ; o - #define ID_FADER_TOUCH_CHN2 0x2c ; o - #define ID_FADER_TOUCH_CHN3 0x2d ; o - #define ID_FADER_TOUCH_CHN4 0x2e ; o - #define ID_FADER_TOUCH_CHN5 0x2f ; o - #define ID_FADER_TOUCH_CHN6 0x30 ; o - #define ID_FADER_TOUCH_CHN7 0x31 ; o - #define ID_FADER_TOUCH_CHN8 0x32 ; o - As you can see there is a lot less functions on it! As I am only using 7 shift registers I will need to tell the main.hex file that won't I also? Can I disable functions in the main.hex file that control the LCD screen as well? I will not be using one thats all. Thanks for your time! Antony Best

This is a very simple question and I am probably doing something wrong, I'm trying to open MIOS studio 7.4 and I cant!! I downloaded the zip file and the Java recommended, then I unpacked the zip file and according to the website you should just be able to click on the file and it will open, with no success it just goes into the folder. I have tried to open it in MS-DOS also by doing: java -jar MIOSStudio_beta7_4 and an error message appears in dos saying: Unable to open jar file: MIOSStudio_beta7_4 Sorry if its a simple answer but can someone help? Thanks Antony Best

Hello, Sorry forgot to mention that, on the ALPS there is a touchsensitive function which as well as being connected to MF is connected to DINX4 also. Sorry Thanks Antony

Hello guys, I'm building a LC and I have a few questions, I am struggling abit when it comes to putting it together. 1. I want 8 channels, each with mute, solo, and rec arm, so 24 buttons, plus I have 8 ALPS motorfaders, plus I want transport control, ff, rw, stop, play, record and bank left & right. The ALPS need to be connected to the DINX4 correct? so I will have 39 inputs. I have 2 x DINX4, do I need to use the other inputs on the DINX4 or can I just put a 10K resistor on them and leave them? 2. As there is not as many functions as a normal LC project will MIOS and app be compatible with my project or will I have to program specifically for my project? And if so how do I go about this because I haven't a clue about that sort of thing!! Sorry if this all sounds like rubbish!! Thanks Antony Best

Hello, I intend to integrate functions from the MBLC into a current mixer, on seperate systems but with everything in the same box if that makes sense, I probably didn't make that clear! Does anybody no where I can by dual rail linear faders from, with rails for the control voltage (0V-+5V) and also a standard audio fader? Thanks Antony

Hello Folks! I am designing a MBLC and was considering integrating it into an exsisting mixer (Yamaha MG16/4) but the only problem I can see with it at the moment is that fact that MBLC uses linear faders, whilst my mixer uses logaritmic faders. Is there any way in which I can use logaritmic faders with the MBLC and also be able to control them both at the same time using the same fader? Cheers Antony