Jump to content

goyousalukis

Members
 View Profile  See their activity

  • Posts

    387

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Posts posted by goyousalukis

  3. Can damaged PIC still be programmable?

    in Testing/Troubleshooting

    Posted

    Hmmm.... I've done some horrible things to my PICs and they still worked. One thing I've encoutered - I've messed them up to the point where I've had to completely erase them and re-program them. This usually happened when I was playing with code and sending new applications over and over to the PIC. You might try completely erasing it with your programmer.

    Justin

  6. any idea on mechanical part of modwheel?

    in Design Concepts

    Posted

    Well, I don't know if you will find new replacement Mod wheels easilly, but you have a couple of options. Try to find a dead keyboard to steal one from. Also you might consider using a Joystick like some manufacturers do. I found a couple of old Apple IIe joysticks at a flea market for $1 apiece, and they worked great. You can also use them for things like filters as well.

    Justin

    p.s. the great thing about the joysticks I got was that it had mechanical switches to change it between auto-centering and loose.

  7. --== Computer Design & Panel cutting ==--

    in Design Concepts

    Posted

    Yes, there are standard dimensions, you find the dimensions by looking at the datasheet for the part you order. For example go to mouser.com and find some buttons or pots and look at the data sheet - it will tell you the spacing. The critical thing is that you space holes for pcb mounted parts so that they mount properly. I am not too experienced, but I can tell you that Thorsten's front panel design for the midiboxSid is right on the money. You can use that to get started. I printed that out and taped it to a piece of aluminum and drilled the holes. Everything lined up perfectly. For my next panel, I will start with that and cut and paste parts from it.

    Justin

  8. n00b 4 dummies

    in MIDIbox Documentation Project

    Posted

    Hey, I'll throw my bit in - having watched and participating in this forum for over 2 years, I know that moebius has helped more newbies than most everyone else. Check the top 15 posters - he's there(woohoo I made the list!) Usually he helps by cutting and pasting the answer from Thorsten's webpages - to show that if the person had read the pages carefully - they would have found the answer themselves.

    The only problem is that I won't achieve the optimum results and I am likely to make errors which could be avoided by just asking simple questions.

    As other's have said, if you want optimum results the first time out you're better off buying something. And everyone knows that you learn best by your mistakes.

    If you have waited a year to get started, I think that's your problem there. A core module only costs $23.95 if you buy the kit from SmashTV. Add some other stuff and you're still under $50. Dive in and get started! You will learn best by doing. This is a "Hands-on" project. It won't take you as long as you think. And once you are done, you can start helping others as we try to do. That is the best contribution we can make - to give Thorsten the time to let his genius prosper!

    Good Luck

    Justin

  10. Sid step B w 7 add. buttons & leds and 2x40 lc

    in MIDIbox SID

    Posted

    Not too hard. Just change the following, re-assemble and use convert.bat to create the syx.

    Change this in main.asm

    #define CS_MENU_DISPLAYED_ITEMS 5
      ;; NOTE: if CS_MENU_DISPLAYED_ITEMS > 5, you have to adapt the DIN settings
      ;; in cs_menu_io_tables.inc
    Change it to 10. Change this in cs_menu_io_tables.inc 
    CS_MENU_DIN_TABLE
      ;;            Function name            SR#      Pin#
      DIN_ENTRY      CS_MENU_BUTTON_Dec,       1,       0      ; only valid if rotary encoder not assigned to these pins
      DIN_ENTRY      CS_MENU_BUTTON_Inc,       1,       1      ; (see mios_tables.inc) and CS_MENU_USE_INCDEC_BUTTONS == 1
      DIN_ENTRY      CS_MENU_BUTTON_Exec,       1,       2
      DIN_ENTRY      CS_MENU_BUTTON_Sel1,       1,       7
      DIN_ENTRY      CS_MENU_BUTTON_Sel2,       1,       6
      DIN_ENTRY      CS_MENU_BUTTON_Sel3,       1,       5
      DIN_ENTRY      CS_MENU_BUTTON_Sel4,       1,       4
      DIN_ENTRY      CS_MENU_BUTTON_Sel5,       1,       3
      DIN_ENTRY      CS_MENU_BUTTON_Sel6,       0,       0      ; define this if CS_MENU_DISPLAYED_ITEMS > 5
      DIN_ENTRY      CS_MENU_BUTTON_Sel7,       0,       0      ; define this if CS_MENU_DISPLAYED_ITEMS > 5
      DIN_ENTRY      CS_MENU_BUTTON_Sel8,       0,       0      ; define this if CS_MENU_DISPLAYED_ITEMS > 5
      DIN_ENTRY      CS_MENU_BUTTON_Sel9,       0,       0      ; define this if CS_MENU_DISPLAYED_ITEMS > 5
      DIN_ENTRY      CS_MENU_BUTTON_Sel10,       0,       0      ; define this if CS_MENU_DISPLAYED_ITEMS > 5

    Change the last 5 entries to show the shift register and pin number your extra buttons are connected to. Just make sure you don't have a shift register defined twice. Just change unused ones to 0,  0

    Hope this helps

    Justin

    p.s. I just checked the top one on my sid, and it works for a 2x40 display. I can't check the buttons though.

  12. MIDIBox SID voltage issues

    in Testing/Troubleshooting

    Posted

    Since no one else has answered, I'll take a shot. It sounds like you have ground problems. Are you talking about using two separate power supplies - one 9v and one 15v ? I am not sure what you have to do if that is the case. Normally you would take the 15v and use the voltage regulators to get a 12v supply and a 5v volt supply. Hopefully someone smart can correct me if I'm wrong.

    Justin

  13. Only 128 with MIDIO128

    in Design Concepts

    Posted

    I think the 128 limit is set by the speed at which the shift registers can be set. Thorsten designed it to scan all the inputs in 1ms. I assume that the outputs are set in the same time frame. If you alter it to handle more outputs, you would incur a time penalty and might have latency issues. You could look into the Matrix discussions over in the Midification topic. They have been modifying the MidiIO128 for use in organs with Matrices for the inputs. I assume the code could be changed for the outputs. Also, the MidiBox Sid uses a matrix to drive the LEDS in the Modulation matrix. If you are fluent in asm then dive into the IO128 source and see what you can find out. I still think that using multiple cores would be the most reliable easiest way, and the extra cores wouldn't cost that much more.

    Good Luck,

    Justin

  14. MBSID - changing bankstick bank through the app

    in Testing/Troubleshooting

    Posted

    Don't give up!

    Ok, I am pretty sure your problem is JSynthLib. One problem I have had in the past is that it wouldn't work if I had both midi in and midi out connected to the sid. You might try just connecting midi out for now.

    Check your configuration inside JSynthLib:

    goto config->preferences->midi

    Make sure you have wireprovider selected in the MIDI Access

    Make sure startup initialization has your midi ports.

    Now goto config->synths

    Don't try the auto-scan - I don't think it works well with this version of JSynthLib

    Choose Add Device

    Choose MIDIBox SID

    Make sure that the Midi In and Out Ports are correct for your SID.

    Now make a new library

    Now goto Patch -> new

    Choose the MIDIBox Sid Device and a single driver

    Click Create

    Double-click on the Patch Name for the patch you just created - Change the name to Test Patch

    With only the Midi-Out connected to the SID,

    Right-click on the patch and choose send.

    You should see the Name of the patch change to Test Patch. If it does you should be good.

    Now right click on the patch and choose edit.

    The patch edit screen should open. Try choosing different waveforms for OSC 1. Then click on the Speaker toolbar button. You should hear changes in the sound.

    If this works then you should be good.

    When you send the patch Library to the MBSid it puts it in the currently selected bank. This is also the bank that it will play from. The bank number is not shown on the LCD. If you are worried about the bank, you might want to only hook up one bankstick until you get it working.

    Hope this helps.

    Justin

  15. Recieving constant system exlusive message

    in Testing/Troubleshooting

    Posted

    No - the 2 second message means you don't have mios loaded yet. You only have the bootstrap loader.

    You need to send the mios_v1_7.syx file from the MIOS download first - then send the main.syx from the MidiBox64. Remember you need to ground A0-A7 of J5 on the core if you aren't using any Pots. (or you can change the number of connected pots to 0 in the main.asm and re-assemble it.)

    Justin

    p.s. This really isn't a MIOS Programming question - it should be posted under Testing/Troubleshooting.

  16. MBSID - changing bankstick bank through the app

    in Testing/Troubleshooting

    Posted

    how do I upload the preset sounds to MBSID?

    Open JSynthLib.

    Go to library - open presets_v1_5.patchlib

    Right click on the bank and choose send.

    You should see messages in the DOS window saying:

    Sending Patch #1 ......

    I hear a clicking sound on each new patch. The LCD should show:

    (starting with P  1 and ending with)

    P128  C  1    1----

    New Patch

    This process takes my SID ~1:17

    The MbSid ends on patch 128, which is just a default patch, so this may be why you just hear the default sound.

    Now send a Program change message (via MIDIOX) to change to program 1 (starting from 0) this is Techno PW.

    You should now hear a different sound.

    Patch 0 is also a New Patch, so it will also be a default patch.

    Justin

  18. MIDIBox Sid MIDI problem

    in Testing/Troubleshooting

    Posted

    If possible, disconnect the SID module. Try to test the core by itself and get it working first. You don't have to have the SID connected to test the core.

    So you've programmed the PIC with the bootstrap loader, and you have the Midi out of the core going to the midi in on your computer - do you get anything at all in MidiOx?

    Justin

  19. help with SID interconnection test!

    in MIDIbox SID

    Posted

    if i mount the sid interconnection test application (on MIOS 1.7, did the hardware upgrade, and all the connections seems OK), i read 5V on all the SID pins, and i cannot control them with the modwhell (using MIDIOX).

    ideas??

    I am unaware of any SID test application - is this new? I don't see it anywhere in the MIOS download section.

    PS: the SID is not working (i dont hear the dropping tune at the startup)

    You will only hear the tune if you have a bankstick connected - it will be an ascending arpeggio. It signifies that you have a bankstick connected. You should hear the descending one when you disconnect the bankstick.

    Justin

  20. New design

    in Design Concepts

    Posted

    tnkx :)

    imagine that i just use 1 core

    what componnents more do i need to handle 64 buttons 20 pots ?

    sorry my stupids questions

    but i don't know what are DINs and AIN boards and how many controls do they handle...

    you'd need 4 DIN boards and one AIN

    moebius is right - go to www.ucapps.de and read up the boards are on the left under MBHP

  21. New design

    in Design Concepts

    Posted

    Well, using just MidiBox 64, you'd need 2 cores.

    1 core would handle 64 buttons and the 15-20 pots(pods?)

    1 core would handle 36 buttons.

    You'd need 4 DINs, and 1 AIN board.

    OR

    Using MidiIO128 and MidiBox64,

    1 core (with midiIO128) would handle 100 buttons (need 4 DINS)

    1 core (with MidiBox64) would handle 15-20 pots(need 1 AIN)

    You'd need either a PIC programmer (JDM) or buy the PIC's pre-programmed.

    You'd need a wall-wart type power supply 6-9v about 300-500ma.

    You'd also want an LCD(or two).

    That's it -

    Justin

  22. Link for DIY MIDI through module

    in Miscellaneous

    Posted

    Hey, I know this isn't DIY, but I bought a Yamaha MJC8 Midi Patchbay on ebay for less than $20: here's one now

    http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&category=23792&item=3758018316&rd=1&ssPageName=WDVW

    This is one of the best tools I ever bought - you can reroute your midi cables a bunch of ways without ever unplugging them. It can send any of 8 inputs to any of the 8 outputs. It doesn't merge midi though.

    Justin

  23. LCD problem

    in Testing/Troubleshooting

    Posted

    I also tried to upload the midibox64 application (main.syx). after that, the display shows some strange hyroglyphs and the module sends a continuous sysex stream.

    The sysex stream is correct, because you don't have an AIN hooked up so you get random messages.

    It sounds like you have no problem loading MIOS and apps, which means the problem is most likely the display wiring is messed up.

    I tried the trimpots to adjust backlight and contrast, but the display stays blank (apart from the blocks).

    So do they have the proper effect: the backlight should get lighter and darker, and the contrast should make the blocks lighter and darker.

    Double(triple) check your lcd connection, cause I think that is where the problem is.

    Good Luck...

    Justin

  24. help me with my SID...

    in MIDIbox SID

    Posted

    Hi Taylor,

    SmashTV's midiBox store is indeed in the US, so I'd imagine that would be your best bet.

    i was thinking:

    -SID module

    -CORE module

    -PSU module

    -JDM module

    for main items i needed.  

    how many sid modules should i get? and for each sid do i need another core, psu, jdm, ect?

    You are on the right track. If you want to have LED's you will also need at least 1 DOUT. Each DOUT handles 32 LEDs, so you probably only need one. If you want to have some knobs and buttons, you will need at least 1 DIN module. I also recommend you get an LCD as this makes troubleshooting and changing parameters much easier. Also, you might want one bankstick, so you can hold 128 patches.

    how many sid modules should i get? and for each sid do i need another core, psu, jdm, ect?

    I'd suggest you start with one, get it running and then decide if you want more. Each Sid module needs it's own core, but they can share the PSU. You only need one JDM to program the 18F's

    so, where can i get the 6581 chips from?

    Most of us pull them from used C64's TK had a link where they sold them, but I don't know if any are still available. Go to local flea-markets and second-hand stores. Even if the C64 looks abused, there is a good chance the 6581 is still good.

    From your description, I'd recommend you build a Sid http://www.ucapps.de/midibox_sid_csB.html with one SID to start. This will let you change all the parameters of the sound from the menu with one encoder and 6 buttons. Then you can add more controls and(or) LEDs.

    Some advice when you get started. Build the Core and JDM first - get them running. Then build the SID module and add it to the core. Get it running. Then build a DIN, add it to the core and get it running and so forth. This method of building a small piece at a time and then testing it is so much easier than building and hooking up everything at once and then trying to find your problems.

    Hope this helps

    Justin

×
×
  • Create New...