Jump to content

djiceman

Members
  • Posts

    26
  • Joined

  • Last visited

About djiceman

  • Birthday 01/01/1

Profile Information

  • Gender
    Not Telling

djiceman's Achievements

MIDIbox Newbie

MIDIbox Newbie (1/4)

0

Reputation

  1. Hi Sorry to revive such an old topic. Im using a win xp sp2 laptop and found that the mhbp pic usb is not picked up in mios studio or midiox. The system installed as an audio device. From searching the forums, i found that there needs to be a different descriptor? for winxp on the midi controller? Does anyone have this pre-compiled? Thanks
  2. Im using midibox 2.4 on mios 1.9f When i turn my encoder clockwise, it gives off, channel 5 note c3 on, then channel 6 note c3 on, then channel 5 note c3 off, then channel 6 note c3 off. Whats causing this issue? I even tried another encoder, same issue. The output should be: clockwise turn: channel * note c3 on channel * note c3 off channel * note c3 on channel * note c3 off and then for anti clockwise turn: channel X note c3 on channel X note c3 off channel X note c3 on channel X note c3 off * and X are just variables. My problem is that which ever way I turn the encoder, it does both channels on and off. ***update, i connected only one pin of the encoder to the din module, now which ever way I turn the encoder, i get values. I get the same values if I turn the encoder clock or anti clock wise. Faulty encoders? Update*** ive just changed to midibx64e (after hours of reading and a few simple changes in the code), I still get the same problem. I read somewhere about encoder mode DETENT3, but now I cant find it anywhere, I even tried to use it in the code but I got compile errors. Below is the code that im using now. I still have the problem with the encoder(connect to SR2 on PIN 6 and PIN 7. LIST P=PIC18F452, R=DEC ERRORLEVEL -223 ; suppress "Redefining processor." ; #define SEPERATE_SETUP_FILE #define DEFAULT_NUMBER_ENCS 2 #define DEFAULT_ENCODER_GROUP_WIDTH DEFAULT_NUMBER_ENCS #define DEFAULT_NUMBER_BUTTONS 64 #define DEFAULT_SRIO_DEBOUNCE_CTR 16 #define DEFAULT_PATCHMODE 0 #define DEFAULT_BANK_PRG_CHNG_CHANNEL 16 #define DEFAULT_PATCH_PRG_CHNG_CHANNEL 15 #define DEFAULT_BANKSTICK_CS -1 #define DEFAULT_DEVICE_ID 0x00 #define DEFAULT_AUTO_DEVICE_ID 1 #define DEFAULT_MIDI_MONITOR_ENABLED 0 #define DEFAULT_MIDI_RX_LED 0x40 #define DEFAULT_MIDI_TX_LED 0x41 #define LEDRINGS_SR_ENC1_16_CATHODES_1 0 #define LEDRINGS_SR_ENC1_16_CATHODES_2 0 #define LEDRINGS_SR_ENC1_16_ANODES_1 0 #define LEDRINGS_SR_ENC1_16_ANODES_2 0 #define LEDRINGS_SR_ENC17_32_CATHODES_1 0 #define LEDRINGS_SR_ENC17_32_CATHODES_2 0 #define LEDRINGS_SR_ENC17_32_ANODES_1 0 #define LEDRINGS_SR_ENC17_32_ANODES_2 0 #define LEDRINGS_SR_ENC33_48_CATHODES_1 0 #define LEDRINGS_SR_ENC33_48_CATHODES_2 0 #define LEDRINGS_SR_ENC33_48_ANODES_1 0 #define LEDRINGS_SR_ENC33_48_ANODES_2 0 ; #define LEDRINGS_SR_ENC49_64_CATHODES_1 0 #define LEDRINGS_SR_ENC49_64_CATHODES_2 0 #define LEDRINGS_SR_ENC49_64_ANODES_1 0 #define LEDRINGS_SR_ENC49_64_ANODES_2 0 #define DEFAULT_ENC_SPEED_NORMAL_MODE MIOS_ENC_SPEED_NORMAL #define DEFAULT_ENC_SPEED_NORMAL_DIV 0 #define DEFAULT_ENC_SPEED_SLOW_MODE MIOS_ENC_SPEED_SLOW #define DEFAULT_ENC_SPEED_SLOW_DIV 6 #define DEFAULT_ENC_SPEED_FAST_MODE MIOS_ENC_SPEED_FAST #define DEFAULT_ENC_SPEED_FAST_DIV 4 #define DEFAULT_DIN_SR_PIN_01_08 2 #define DEFAULT_DIN_SR_PIN_09_16 3 #define DEFAULT_DIN_SR_PIN_17_24 1 #define DEFAULT_DIN_SR_PIN_25_32 4 #define DEFAULT_DIN_SR_PIN_33_40 5 #define DEFAULT_DIN_SR_PIN_41_48 6 #define DEFAULT_DIN_SR_PIN_49_56 7 #define DEFAULT_DIN_SR_PIN_57_64 8 #define DEFAULT_ENC_DATAWHEEL 0 #define DEFAULT_DIN_MENU_EXEC 7 #define DEFAULT_DIN_MENU_RIGHT 6 #define DEFAULT_DIN_MENU_LEFT 5 #define DEFAULT_DIN_MENU_SNAPSHOT 4 ; #define DEFAULT_DOUT_SR_PIN_01_08 1 #define DEFAULT_DOUT_SR_PIN_09_16 2 #define DEFAULT_DOUT_SR_PIN_17_24 0 #define DEFAULT_DOUT_SR_PIN_25_32 3 #define DEFAULT_DOUT_SR_PIN_33_40 4 #define DEFAULT_DOUT_SR_PIN_41_48 5 #define DEFAULT_DOUT_SR_PIN_49_56 6 #define DEFAULT_DOUT_SR_PIN_57_64 7 #define DEFAULT_GP_DIN_SR0 0 #define DEFAULT_GP_DIN_SR1 0 #define DEFAULT_GP_DOUT_SR0 0 #define DEFAULT_GP_DOUT_SR1 0 #define DEFAULT_YOFFSET_LINE0 0x00 #define DEFAULT_YOFFSET_LINE1 0x40 #define DEFAULT_YOFFSET_LINE2 0x14 #define DEFAULT_YOFFSET_LINE3 0x54 #define DEFAULT_MORPH_FUNCTION_ENABLED 0 #define DEFAULT_NUMBER_AIN 64 #define DEFAULT_ENABLE_AIN_MUX 1 #define DEFAULT_ENABLE_MOTORDRIVER 0 #define DEFAULT_MF_PWM_DUTY_UP 0x01 #define DEFAULT_MF_PWM_DUTY_DOWN 0x01 #define DEFAULT_MF_PWM_PERIOD 0x03 #define DEFAULT_TOUCH_SENSOR_SR 0 #define DEFAULT_TOUCH_SENSOR_MODE 0 #define DEFAULT_TOUCH_SENSOR_SENSITIVITY 3 org 0x3280 ; never change the origin! ;; encoder entry structure ENC_ENTRY MACRO sr, din_0, mode dw (mode << 8) | (din_0 + 8*(sr-1)) ENDM ENC_EOT MACRO dw 0xffff ENDM MIOS_ENC_PIN_TABLE ;; encoders 1-16 ;; SR Pin Mode ENC_ENTRY 2, 6, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 1 ENC_ENTRY 3, 2, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 2 ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ;; encoders 17-32 ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ;; encoders 33-48 ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ;; encoders 49-64 ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT ENC_EOT #include "main.asm"
  3. Hi I have an issue with the traktor midiout to midibox. If I have it enabled with an output for a LED, the midibox doesnt work properly. I have button 1 set as toggle for play and I an output for the same to the LED. If I press the button, traktor plays and then stops playing after 1 second. If I remove the output for the LED, the button works fine. It seems to have problems with any output to the midibox. Anyone else experience this? I also tried this on the mpu401(gameport) and on serial with the roland driver. with the midibox - if i press the button, the LED comes on for the duration of the button being press(this works using the midibox v2.4) Now in MIOS and midiox, i press the key in the keyboard that generates the event as when pressing the button on the midibox, but the LED doesnt come on. I have the port routings correct. Should the LED come on when generating the event in mios or midiox provided that the event is the same as the channel that the LED is on. ************Update Im now using midibox64e 2.2 The button now works with the midi output enabled and a output for the LED. But the LED doesnt stay on.... The output for the LED is the exact same as the input for the button except that its an output type. The LED does come on when I press the button(this is a normal function of the dout) even with the midibox in standalone mode
  4. I used a virgin pic, flashed bootloader 1.2b using mplab and picstart plus programmer. In mios studio - received unexpected mios sysex message = 00007E407001F7 expected = 00007E4000 And the midi in monitor shows the 00007E407001F7 coming in every 2 seconds I also tried another pic with the same process as above.... How can I solve this?
  5. I came across a prioject called midi-nator, it uses a 18f2455. Though the usb to midi pic module on the midibox site says that all 18F devices are useless for midi??? Can anyone help with this? I have the source code for the midi-nator project, maybe that will help to complete the midibox usb to midi? I need to get the midi to usb as laptops dont have game ports and the commercial usb to midi units are very expensive in south africa. just another thought, will this work>>> midibox to com(rs232) then a rs232 to usb? so you end up having the midibox going to usb via the serial port? thanks
  6. im using a 18f452 pic. Its a pretty annoying thing trying to plug the pic in the socket, pins bend alot. Can I use a 18LF452 pic? Btw, i used the mhbp burner to flash the bootloader onto the pic. The measured voltages where about 1 volt below the required. But the flashing worked fine. Seems like my meter reads voltages one volt lower or it could just be, my power... But to flash, i use the big variable power supply (20v) as my ac adapter only went up to 12v max.
  7. i earthed pot5, plug in....still jitter in midi-ox...but worked fine in traktor... so i soldered pot 5 back, changed the ainx IC....im back to square one, where it works fine with mios studio and traktor..but in midi-ox and fruity loops i get jitter. Resistor tests> wher you said to solder a 7.5k (i used 10k) resistor to earth and to the ain pin then touch the ain pin with a 100k from power(5v) and check if i get a value in midi-ox...but i just get alot of jitter. I dont have any 9v with me at the moment.Though I did try a big variable power supply(0-20v dc)(0-3a) and i set it to 12v. Its a regulated dc power supply from metronix(about 20 years old, its dads) Still get jitter. Its 8:30pm and dont think any shops are open to get a decent duracel battery. Will have to try tomorrow. Though, im happy it works with traktor. But i want a 100% proper functioning midibox. I want to expand later one when funds are available to buy pots and buttons, they are quite expensive.
  8. what i mean is, if i turn pot five, the needed control turns. But if I turn anyother pot, then that control + the control that is linked to pot 5 also turns.
  9. i did the resistor test that you mentioned to me 2 days ago. I got the same problem. Now i removed the resistors and pluged in my 8pot ainx module. I get jitter, but not like before, now i get jitter that is slower and all different types like bank memory... and only from the pot i turned, mainly number 5. Jitter only shows in midi-ox. In mios studio, i dont get jitter, i only get values when i turn the pot, its pretty sensetive, I have to turn it about a milimeter to get one value, if i turn it abit more i get like 2-4 values. I checked the voltages, it reads 4v on my meter. Im using new parts, old pic and the same power supply. I just tried it in traktor, pot 5 seems to be turning the controls in traktor. I guess pot five it messed up. Time to just earth it out.
  10. Hi I just completed the new core. Only part that is used second is the pic. Doing the resistor test, i get tons of jitter. Tried both modified software and even the original midibox 2.4 software. Same results. Is the pic damaged?
  11. After my problems with my first attempt with the midibox 64 core, im making a core with the features that I need. So i removed j4, j15, j10, j13 and j12 along with the optocoupler and the trimpots. What is the function of R12? its not shown on the schematic? I changed a few things around and made the traces more easier to work with in some places.
  12. im using j11 to gameport. I just tried the 7806 which gives a 5v output according to my meter which cost 200 bucks locally...thats alot for me.... I did the voltage check with the meter, it shows 5v in the needed places. Hooked the pic back in and did the resistor test, i still get jitter. Im thinking, i will just build another core but use the same pic. I will leave out the diode and the optocoupler since i use j11 to gameport. Btw, the optocoupler is not on the board. I wasted money buying it in the first place. I need a new soldering iron, the tip on my is eaten away. So no more work tonight. Until i build the new core, ill just use my 8 port midi box with traktor. hopefully I get parts and new soldering iron by tomorrow.
  13. i used a 7806 by ST in another circuit. It measures 5v output.....but the power circuit design for that is the same as the one in the midibox. Ok, i will try the 7806
×
×
  • Create New...