Frank

HI, when you buy the Alps motor faders, do they come with the conductive slider knobs or do you have to purchase them separately and if so where from and how much. Thanks Frank

Ok, I understand most of it in principal and i'll work with the above info for now. Thank you Master ;D Your grateful student Frank

Hi TK, I'm trying to learn to do this in ain_example3_v1_3. In its original coded form below, in the section "USER_AIN_NotifyChange", the pots are referenced to mios_tables.inc and for 64 pots table entry position 0x00 to 0x3f. ;; we read the entry from MIOS_MPROC_EVENT_TABLE ;; this has a big advantage: you can setup the "input" and "output" ;; events at one place! TABLE_ADDR MIOS_MPROC_EVENT_TABLE ; this macro sets the base address movf AIN_POT_NUMBER, W ; add pot offset (number *2) to TABLPTR mullw 2 ; multiplicate with 2, result in PROD[LH] movf PRODL, W addwf TBLPTRL, F ; low-byte movf PRODH, W addwfc TBLPTRH, F ; high-byte (+carry bit on overrun) ;; for MIDIbox Link: notify begin of stream call MIOS_MIDI_BeginStream ;; send first MIDI byte tblrd*+ ; read first byte from table movf TABLAT, W call MIOS_MIDI_TxBufferPut ; and send ;; send the second MIDI byte tblrd*+ ; read second byte from table movf TABLAT, W call MIOS_MIDI_TxBufferPut ; and send ;; send the third MIDI byte movf INDF0, W ; value from 0x00 to 0x7f call MIOS_MIDI_TxBufferPut ;; for MIDIbox Link: notify end of stream call MIOS_MIDI_EndStream ;; request a display update by setting DISPLAY_UPDATE_REQ,0 ;; USER_DISPLAY_Tick polls this flag! bsf DISPLAY_UPDATE_REQ, 0 ;; thats all How do i get the pots to reference for example to table entry positions 0x80 to 0xbf and still be able to get the soft takeover to function correctly for new pot positions. Sorry to keep picking on your brains but i'm just so motivated by all the possibilities of MIOS that i want to learn as much as i am capable of to be able to customise my own setups. Peace & thanks Frank

Hi TK, You are correct in your guess. I removed the 48th encoder and replaced with ENC_EOT , and the problem was solved. So it requires optimization. Thank you Frank

ok, no problems i can check this out and i'll get back to you :) Peace Frank

Hi TK, Just checkin in. Do you have time to look into the abovementioned problem? Thanks Frank

Thank you, I'll check it out. Frank

HI, can anyone help me with the below code snippet :- ;; now toggle the appr. DOUT LED movf TMP3, W ; button number has been saved in TMP3. This is also the LED number IFCLR TMP4, 0, call MIOS_DOUT_PinSet1 ; if button has been pressed (value = 0V = CLR): LED on IFSET TMP4, 0, call MIOS_DOUT_PinSet0 ; if button has been depressed (value = 5V = SET): LED off ;; thats all return As coded the led will not latch. How do i code it to get the led to latch, i.e. when button is pressed (0V) led lights up. When button is released (5V) led is still lit. On next button press (0V) led is off and so on. Any code ideas? Peace Frank

Yahooooo ;D congrats T.K & midibox community Frank

Hi TK, I've been fooling around with the above example application and have discovered this problem :- If you moved an encoder, the corresponding ledring displays smoothly and correctly. After recording the movements in the host software, the playback of the ledrings tends to flicker with wrong values. You would be able to see it clearly if you just record for encoder values that light up to 4 leds. On playback at random intervals some leds higher than this will light up too. I dont think its my setup cos i substituted with a mb64e firmware into the same setup and it doesnt exhibit this problem . Any input would be greatly appreciated. Peace Frank

Hi, Thorsten said that he'll do it but he doesnt know when. Peace Frank

Hi & welcome, Congratulations on getting the core and lcds to work on your first try. If you're refering to the 10*7 segment led digit display for smpte/beats than Midibox LC 1.4 does not yet support this. It does display smpte/beats on the 2*40 LCD. If you're talking about ledrings or pushbutton leds than there's nothing to modify to get a standard LC emulation working. So it all depends on what do you mean by 10+2 led digits Peace Frank

Hi guys, If your're building mbhp projects for mackie/logic controller emulation you are limited to 11 leds because of Mackie's protocol and not mbhp hardare limitations. If you're building MB16E projects or using its encoder ring source code in your own designs than you can have 16 leds by modifying the display pattern code. Its very simple to do so. Peace Frank

Actually not that impressive ;) Its cheap because :- 1. made in China 2. Motorfaders with no mention of Touch Sensitivity 3. Limited Visual display feedback (4*7 segment LEDs) 4. No track labels, so it gets messy when bank switching large mixers, no timecode display and dedicated transport controls. 5. Behringher Quality Control, so its 50/50; you may get a good unit or defective one on purchase or one that breaks down after a month of usage (from experience). In the end its always "you get what you paid for" midibox and MIOS still rules peace Frank

Hi Dan, If you can code for the third LCD by yourself, yes its possible. I have made a remote transport controller consisting of a core, a 16x2 LCD, and transport buttons with LC/MC firmware. I've hacked the code so that the display only shows SMPTE/BEATS. If you wanna take a look at this hacked firmware let me know. peace Frank

Hi, If you change the last parameter from 0 to 1, then the spacing between channels is larger. ;; print host messages at position 12/0, (0=normal spacing) SET_CLCD_HOST_MSG 1, 12, 0, 0 <--- to 1 After setting this you can also customize the spacing to your own liking by changing the parameters in "lc_hlp.inc". peace Frank

Hi Schoko, The houston emulation only supports 2 x 40 display. The original Houston uses a custom LCD that has a space after every 5 characters. So the emulation display is very messy and hard to read with no spaces between individual tracks. My advise is to use the LC/MC midibox configuration. If you have any more questions on Houston emulation please fire away. Peace Frank

Hey guys, You dont need to use perl script from the Dos prompt. In all the LC firmware releases after downloading, extract the zip file and you'll find in the folder "convert.bat". Just double click this and it'll convert the main.hex into main.syx automatically for you. Peace Frank

Hi TK, You're the man ;D. My problem is solved with your new Touch sensor Mode 2. Taking into account the low quality and low cost of the Panasonics, i'm really happy with the performance of my setup now. If i want better than this i would have to pony up cash for the ALPS. So once again THANK YOU, THANK YOU & THANK YOU. Steve_C, i guess theres no need to do the verification, thank you for your help too ;) Peace Frank

Hi Steve_C, No i'm using my own vectorboards, cos i prefer to do eveything by myself. The more problems you overcome the more you enjoy the project ;D. Are you using one of the prefab cores? , if you are and have the time you could also use Logic to help me verify the problem. All you need to do is have 1 channel of fader automation for 8 bars and loop the playback. (audio on the track is not needed). Sent the output from Logic into MidiboxLC and sent the output of MidiboxLC into midiox and monitor it for intermittent pitchbend data (E0 xx xx ). By right if Logic's automation is in read mode, midibox should move its fader but not output any pitcbend data. Any help would be much appreciated. Peace Frank

Hi Steven_C, Thanks for the reply. I've made 4 different core boards with 4 different layouts and tried all manner of grounding, power schemes and filtering capacitors but still no go with the faders. I tried it on my friend's Logic Platinum same problems with fader data being sent while playing back automation. I tried with hardware touch sensor set off but where do i set software touch sensor off?. The problems you experienced with your fader is also what i experience with my setup. I do remember earlier in the year i had a working fader setup so maybe i should check out MIOS V1.2 again. Are you having better performance with MIOS v1.2 ? Peace Frank

Hi guys, I need some others here who have Cubase SX or Nuendo to help in a verification test. Midibox using MIOS ver 1.3 and Midibox LC version 1.3 and MIDIOX will also be needed. 1. Use midibox LC in mackie control emulation mode and setup up Cubase SX/Nuendo with Mackie Control in remote setup. Assign midi in/midi out ports to mackie control and hook up midibox. 2.Setup a 8 channel audio template and record some fader movements for 30 to 45 secs and loop it to cycle playback. 3. Launch Midiox and use it to monitor incoming midi port of your computer. Monitor the looped playback for 5 minutes. During this time do not touch any faders, buttons or encoders on midibox LC Do you get intermittent random data displayed on Midiox input monitor? Do you also get Pitchbend data displayed by Midiox? For Cubase SX/Nuendo any incoming Pitcbend data that is received while it is playing back recorded fader automation data causes the faders to jerk, jump or glitch very fast. Sometimes the faders get stuck in mid travel for awhile and later recovers again. Other software like Logic may be internally blocking incoming fader data while it is playing back recorded fader data until a touch sensor is activated. Any help would be much appreciated since its been some months of trying everything to overcome this fader problem with Steinberg products. Its not because i'm using a Panasonic fader cos its unrelated to the already known poor mechanical performance compared to Alps. Thanks & Peace Frank

Here's a link to a supplier of TOSLINK tx and rx modules for ADAT lightpipe http://www.sysconcept.ca/product_info.php?cPath=34&products_id=157 peace Frank

Hi DrBunsen, TK's responce to this often asked question is in this thread : - http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=misc;action=display;num=1056712913;start=15#15 peace Frank

Hi TK, I've been fooling around with "mf_example2_v1_3" and cubase SX and i think theres a problem with the code. When playing back a previously written fader move the motor faders will move but there is also random data coming out of the midibox that corresponds to the CC no of the fader being moved but with random values intermittenly and this causes the automation to lockup in Cubase SX. I think we had this problem in the early beta versions of LC development but you managed to solve it. Its the same problem also with "mf_example1_v1_3". Peace Frank