rogic

Hi, I've built a midibox 64 with 1.00 firmware. Do I have to use vmidiboxv1.00f with it? Is this a way to operate with vmidibox? Correct me if I'm wrong: - open sysex file (midibox64_generic, for example) - send sysex - and midibox should work like defined in sysex? (num of pots,etc) When I click receive sysex, I see a message like "Bytes to receive: 1927" and nothing happens :( Is there something wrong with my midibox or am I not using vmidibox in a proper way? thanx

Photoshop is enough for this, but I am wandering what is .xpm file format? I am sure there is no need for windows specific software for bitmap editing - maybe there are some java applets around the web with similar capabilities? There were some for editing mobile phone logos, etc.

Hello, It seems that pots on joysticks don't work ok. :( I'll have to check connections again. Also I have problems with vmidibox - When I click on the receive button, it writes out how many bytes to send, but just stops after that. I don't think I can send/receive sysex at all. What should I check?

Hi, I found 2 joysticks from an old TV-game. They are basically 2 pots per joystick with different resistances per axis: 100k & 80k. I've read a topic here where someone suggested connecting these pots with different values than 10k to separate inputs of 4051 multiplexers. I've done that - connected them as inputs 28-32 of AIN and started MIDIox. I got proper values: from 0-127, CC 93. Only thing changed was MIDI channel. From 12-15 for last 4 inputs. But the problem is that NI Traktor cannot "learn" these controls. Is there any possibility to change last 4 pots via vmidibox to send MIDI messages on a dedicated channel or is there any other solution to this?

:) ok, thanks.

Hi everyone... at last, the problems from my last post: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1043237633 ...are solved :) I brought the MBox to this guy with 10+ years experience and we combed through all components and connections. One of the boards had some weak soldering points, but that was not the major problem - the problem was, beleive it or not, in CABLES! (I think mr. Murphy is laughing right now ;) ). Anyway, I would like to give a good tip to all newbies: DO NOT use flat cables between modules which are not soldered at the ends! I tried to re-use some with plactic connectors (not soldered) at the end (like used for floppy, for example), but you are never sure if all connections are OK. One of the cables even had the connections between the neighbor wires, although it looked ok! When we finished troubles with connections we still had a lot of random MIDI events, even though all unused pot inputs were grounded. Then I tried to ground unused AIN inputs (A4-A7 on CORE) to the ground on the core nearest to the power supply and voila! Random noise dissapeared! I was so excited, I had to open NI Traktor and test this (only) one pot! :) And everything worked excellent! Here is a photo of the newcoming wannabee-midibox :) : http://www.e-motion.co.yu/tmp/rogi/IMG_1901.jpg Now it's time to build the interface and find a good panel cutter. Thorsten, thanks for all help hints and expect a total report + photos for the gallery when I'm done :) Cheers!

Hi, saw in VMidibox thread that 1.01 firmware for MBHP is released, but I cannot find list of changes? What is new? DOUT Shiftregister map?

LOL! LOL! :) :) :) :) :) :) :) Swede, I was thinking to ask the same question :)

Hi Thorsten thanks very much for quick answer again. Yes, it is like that - circuit is doing something (random events are there, but I get something actually) for minute or two and then dies. Voltages on LTC are ok, but since I don't have that much experience with electronics, I' ll wait for a local guru to come back to town (monday) and check EVERYTHING with him. I'll check the contacts for all modules today myself. Other things - I'll wait for guy with more experience. I'll definately print everything today.

Hi Thorsten, to-COM is enabled in firmware - was patched before burning. I am not sure if you understand me properly - MB64 doesn't work at all. It only works for a few moments when I change all 3 ICs on the LTC - 232 & 74HC00.

Ups... but if to-COM is enabled, this is different baudrate - so I can't test MB64 without LTC?

Ok, I found a gif on the site - optocoupler not needed for direct connection to gameport.

Hi, Thorsten, a big thanks for your reply. I am going nuts with this thing :( On next monday, a friend who's an expert in electronics will be back in town and I will sit downwith him to check everything. I do not have easy access to a PIC programmer, but I will try to burn this test programs and check. But I didn't tell you - we don'thave LCD in our configuration - how I am supposed to see results of the tests? :( If I connect CORE directly to gameport (to omitt LTC as a possible cause of failure) do I need optocoupler? Thanks again, N

Hello, we're still having troubles to make midibox64 working. We connected CORE,LTC,DIN and AIN. We put the new max232 and 74HC00 chips on LTC - it worked again for a few moments and then nothing. First try was without AIN module, but now we added it and all unused pots were clamped to the ground. Also the second AIN input on the CORE module was clamped to the ground (we only need 1 AIN). Voltages on the CORE and LTC checked - everything fine. PIC is ok also - firmware checked, 'to-COM' enabled. During 'work time' a lot of random MIDI messages were sent but I noticed one value was 'proper' - I rotated one pot we connected to AIN (pot #1) and got from values 00 to 7F. Other MIDI messages are something like Contrast or Volume, etc... They appeared in 'series' - a lot of them, then a break for a second or so, then again. DIN and AIN modules are original from Thorsten's site. All components are with original values. CORE and LTC have changes - 5V supply from external source to the J2 of CORE. Some things removed since we don't need them: If this can help, here are some other symptoms: - when turned on, the sound is heard for the moment from the soundcard like there is some extra voltage running through LTC to com port... I am not sure if RS232 chip is ok, but is it possible that we have something burned because when we changed RS232 and 74HC00, MB64 worked? (for a moment) There is no sound when we connect 'dead' MB64... - LEDs on LTC are not working at all. Not even during the 'work time'. They are connected properly. Do they have to light if COM port is used only? - LTC module cable (from max232 to COM port) is 1.5m long (from old mouse) If anyone have any idea how to troubleshoot this, please help.

yes, we build up DIN completely, filled with resistors. We didn't have time to check everything again. As soon as we do some tests, I'll inform about results.

We have finished all required modules: 1 CORE 2 DINs 1 AIN 1 LTC 1 DOUT All PCB's are made with NO modifications from your site. Only changes - 5v from external source, so no power polishing on the CORE module, LCD and Luminance/Contrast omitted as well as transistor, MIDI connectors (DIN shaped) omitted, to-COM option enabled in firmware, no 6N138 optocoupler... We'll connect at least one pot (I found this information yesterday) and clamp other inputs to the ground. Do we have to do same for DIN? These 2 modules are complete - everything from the site schematics is there. PIC is checked and it is OK. >:( the worst thing I say is that this actually worked for few minutes...... arggghhhhh....

OK, we didn't know there must be an AIN connected. We have a fuse on the CD-player board, it didn't went off. Core has correct voltages on pins. But what should we check right now?

Meta event can be programmed in this manner? I had no idea about that :-/ anyway, great!

Hello everyone, We've finished yesterday all required modules for MB64 and installed Roland serial driver. Firmware in PIC is latest v1.0. COM port enabled in firmware. Only modification on the CORE module is that power supply is from other source (5V stable from old CD player). We tested CORE voltages on the pins like described on the CORE module page on Thorsten's site and everything is OK. We connected following modules: - LTC - Core - 1 DIN Turned it on and got a lot of random MIDI messages in the MIDImon application (same as MIDI-ox). So in a kind of a way, it worked. Is it required to connect AIN in order to get Midibox working fine? We were trying to get any NoteOn/Off event by connecting pins on a DIN, but we didn't manage it. So we switched on and off box for a few times. One minute later, nothing. Zero. No events, nothing... What can be wrong? If we burned something, what could it be? I've gave a PIC to a friend to check it out and I will know tommorrow if it's ok. What elements should we check and how? Please help.

Hello, Anyone tried to make pitch-bender like on classic hardware synths? I assume this will be possible if there is an option (maybe vmidibox has it) to send signals from potentiometer in following manner: - if value >64 and rising - > send relative difference + - if value <64 and falling -> send relative difference - Just an thought, I have no idea if this can be done at all. I had a idea to modify a potentiometer (add few springs ;) ) and try to use it as a bender... Any ideas?

Hi, this is a request for experienced owners of MIDIbox with LTC: which driver is better? Yamaha or Roland? I am alergic to resident drivers (which lurk in systray), that's why I am asking this...

I am also interested in dj software interfaces, please PM me or send it to this thread if you have some cool designs. I Have a basic idea for Traktor 2, but not sure about some functions :-/

I must also say : WOW! This looks fantastic! d2k, when you have time, please make that walkthrough, I also have an Logitech R.I.P. ;)

d2k, please post final report when you're done with modifications. I am also very interested in this type of hacks, but know shit about electronics. thanks!

Merry Christmas and a happy New Year to every MIDIboxer ! :)