rogic

I've done all that... if I haven't done it, my midiox monitor screen will be filled within a second.

Hi, I have problems with jittering; Connected 16 pots to MB64, and when I finish moving pots, I let MB alone and after some 10 secs, last CC changed start jittering. Not much at all, something like: 105 106 105 106 105 106 So it only jitters a little; Not a real problem with applications but it can be pain in the ass if you want to use 'learn' function of host application. In some cases this doesn't occur at all, but I was not able to figure out the reason why. Dynamic jitter filter doesn't fix this. Pots are on 25 cm cables to AIN, and connected 'starlike', like shown on Tor Arne's site. Pots are 10K. Is there any rule or something for grounding unused pot inputs of the AIN, or any other tip regarding this? Thanx.

Hi, I think you'll need some kind of drivers/remapping software in order to transform midi messages for host application... There is great example of non-audio use of midibox on Thorsten's midibox gallery page - a guy made mb just to control his graphic software.

Can you point me to that page? I would like to get that 18F for free also ;)

Thanks for the reply, I already know about 'free samples' but not sure if they are mailing to non-EEC countries. Regarding samples: should MIDIbox NG work only on PIC18F452 or PIC18F458? ??? I can see that their site listes models PIC18F452-I/P and PIC18F452-I/PT which can be obtained as samples. Are they the same as PIC18F452 ??? I just don't understand what firmware should I burn into PIC18F ? And I am afraid I cannot find instructions for MIOS... :( Sorry, too much newbie questions... :-/

Hi all, I had serious accident yesterday and I definately burned my PIC16F877-20. Is it possible to buy new other PIC (18F) and crystal and use it with my current modules (DIN,AIN,LTC,DOUT,CORE) for midibox 64 application or this it totally different thing? (firmware, etc.). I must admit I don't understand these threads about MIOS & stuff. Should I stick to the old good MBHP and PIC16F877-20?

Didn't tried many options, but works fine ;D

Hi and cheers to RAF! I have the *SAME* idea of laying out interface elements (pots, faders & buttons) on the Plexiglas (in my case some other plastic material, dunno name in english). My idea is to lay down all elements on this surface and metal case should go above. This way no screws will be visible on the top - faders also because they will be mounted on the plastic surface. Another idea: because I'm making mbox for Djing with Traktor, I am not sure where to put all buttons. So my idea is to make a precise matrix (2cm distance) of holes on the plastic and mount buttons on small veroboards with screw slots in a way they can fit to these holes (either horizontally or vertically). This way I can change positions easily. I think this idea leads to VERY modular midibox design :)

I am sorry I can't help you. But I just wanted to know what is this application you are using to monitor MIDI events? Is it something on windows?

Hi d2k, I have the same experience: I was torturing everyone on the forum in order to find what was causing MB64 not to work, and later on found that these header sockets if not soldered directly are the core of the problem - every single one has to be checked & rechecked dozen of times... and if you find after that the cable is causing problems, you begin loosing your hair :( All elements on all boards were fine, just these damn cables... I hope I want encounter such problems again ;)

Hi Serge, I solved MIDI serial problems, have a look in: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1045822398

Hi, these pots are claimed to be of good quality. I am going to use piher pots also.

My Midibox is specific: I don't have a LCD, nor MIDI standard connection - the only connection was through LTC, so this issue was very important to me.

No luck. I browsed all of Opera's history from last night and I couldn't find the URL where I downloaded file from. There is .wri document inside the archive, but with japanese (or similar) encoding, so no help in this one. Original archive name was "drvwinnt.zip", so nothing specific - meaning hard to find via google. I can send this driver to anyone interested, size is ~12 Kb... Thorsten can you host this file on ucapps.de?

Hi & thanks Thorsten for quick reply I found that this WAS NOT hardware problem at all! Yesterday late night, I was searching for alternative driver - I digged somewhere KORG serial MIDI Driver! Installed it, started MIDIox, loaded Sysex, transferred and voila! No problems at all! Generic settings are there, pots are working fine in NI Traktor and Propellerheads Reason - I tested it almost the same minute :) This driver is simple, has no additional settings - only one dialog where you choose the com port - no multiple ports option or error control. One input and one output port are available only. The craziest thing is that it is around 15Kb zipped! I'll try to find URL from which I downloaded it and send it to you Thorsten because I am sure other people might have problems with Yamaha/Roland driver. Also I can send you a copy which I hope can be hosted somewhere (if there is no some 'licence agreement' or similar that claims different). For the record - systems I tried to use Roland/Yamaha drivers were Windows 2000 Proffessional and Windows XP Proffessional - no luck on both systems. So, desired Sysex is there :) and I am not going to change it unless I need something different! ;) Thanks again for the help, I'll save this thread if I encounter problems. I'll post a URL for the KORG driver later here.

And yes, I forgot: this second application, Sysx, received 1,334 bytes from midibox after sending midibox_generic.syx. If this is helpful, I can upload it somewhere.

Hi, here are the results of tests: First I checked firmware, and only change is TO-COM option enabled in a line before last one. Roland driver default settings - no multiple ports - I got no LEDs lighting on MIDIbox during send Sysex, no response from the box after [pre] F0 00 00 7E 43 <ID>F F7[/pre] But, when I choose 'use multple ports' in driver settings, I got LEDs flashing and response from the box is like this (MIDIox dump): [pre] TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT 0000F720 Rol Rol F0 Buffer: 2 Bytes System Exclusive SYSX: F0 F7 0000F7D6 Rol -- F7 Buffer: 0 Bytes SysEx End [/pre] The response is same for all 8 Sysex requests (ID=0 ..7). When I Send Sysex (midibox_generic.syx), I got the same response like this one, but no change in Input (pots still the same). I tried even another application (Sendsx, http://www.bome.com/midi/sendsx/) and Input just echoes 7 Sysex bytes which are sent (on Roland Out A or Roland Out B set as out port). In VMidibox, there is no option for multiple output ports, so when I select one of these ports and try to send Sysex, both LEDs flash for a second and then stop. I tried lowering the speed (bytes/sec) but same thing. Here is the dump from the MIDIox about devices: [pre] TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT DEVICE INFORMATION IN: 9) Roland Serial MIDI Input OUT: 10) Roland Serial MIDI Out A In: MIDI-OX Events Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx OUT: 11) Roland Serial MIDI Out B In: MIDI-OX Events Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx [/pre] I assume I can always get a dedicated firmware with to-COM enabled and generic settings, but maybe I will need, for example, button toggle as an option sometimes, so I find this solution not so flexible... :( If anyone has an idea what to troubleshoot, please help.

Hi, Sure - the optocoupler is removed. My box is made for to-COM option exclusively. Firmware is set like that, and there is no LCD. Input works like a charm, I got 2 joysticks (4 pots) connected, they give ranges from 0-127. I tried different setups of the Roland driver (multiple ports, etc) and when I start Sysex transfer, some settings do not light-up LEDs on LTC at all, some light them, but no data is sent. I only noticed difference for the first pot - it changed CC to Bank_something (I can't remember now). So, I don't know how, but the transfer works only for the first pot.... :( Is it OK that red & green LED are lighting while transferring Sysex? I'll check tonight with these commands, but I'm sure I didn't change anything in firmware except to-COM option, so I have no idea how device ID could be changed. I already tried manual dump (like described in http://www.ucapps.de/midibox/midibox64_sysex_implementation.txt), but no response. Thanks Thorsten, I'll post results tommorrow.

That's actually what I've done, but no success :(

Hi, the box is working, but I am still not able to put desired Sysex into PIC. VMidibox application doesn't work at all. Can anyone tell me how to transfer Sysex file to MIDIbox via Roland Serial MIDI driver? How do I configure this driver? (Flow control settings? Which synth should I choose? Which output ports?). I gave up installing Yamaha driver, because I couldn't make it work at all. Now I brought the MIDIbox into the office (collegues are thinking I am some kind of mega-nerd ;) ) just to be shure this is not the problem with WinXP at home. I am receiving input in MIDIox, devices are configured properly, delays are like described on Syssex howto page, LEds are flashing when sending data... but I cannot see any changes afterwards. Every pot is still on different channel. I need all pots on same channel, different CC numbers (midibox64_generic.syx). Can someone give me advice how to do this?

Hi, first question: I cannot find this veroboards bigger than 100x160 mm... I need them for buttons/pots - Does anyone know if there is any bigger size than 100x160? Something like 200x200? second: Is there any way I can add a small circuit that will change resistance of 100k pot to 10k and still be linear? Thanks everyone

Hi Thorsten, I tried to send a sysex and request it from PIC in order to check if this transfer works fine. I already asked Serge about this problem: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=editor;action=display;num=1045045038 but I'm not sure if it is a hardware or software problem... :-/

I'll try during the weekend and post results on monday. Thanks!

Hi & thanks for reply... My configuration doesn't have a LCD, it has only one CORE and device ID is set to 0, is this right? Speed is set to 200 bytes/sec. When I click 'send', it sends some data, because counter (bytes left to send) is counting down... but no LEDs on the midibox lit. When I click 'receive', it shows 'bytes to receive: 1927(or some other number)', but nothing happens. No countdown. When I close vmidibox, I can see in task manager that application is still active, so I have to end it manually. I am using Roland's serial MIDI driver. In VMidibox, ports are selected as following: MIDI In: Roland Serial MIDI driver MIDI out: Roland Serial MIDI driver Out A (or something like that, I can't remember right now - I am in the office) Is this correct? MIDIox shows values from pot & buttons like it should, but I cannot send/receive sysex files. What should I look if I have hardware problem? thanks again, rogic

What should I use? vmidibox64_100f.zip or vmidibox64_101a.zip for firmware 1.0 ?