Jump to content

JaseM

Members
  • Posts

    45
  • Joined

  • Last visited

About JaseM

  • Birthday 05/10/1982

Profile Information

  • Gender
    Not Telling

JaseM's Achievements

MIDIbox Newbie

MIDIbox Newbie (1/4)

0

Reputation

  1. JaseM

    ...

    I actually like this idea. It would be nice for those of us who aren't comfortable with JB Weld and the like to mount the new PCB to the panel. As far as the aesthetics goes, I think the screws could add something to the overall look. Depending on what type of screws you use, it could add an interesting industrial feel to the overall sequencer. That's my 2¢.
  2. Many thanks to TK, Wilba and everyone else! After updating MIOS studio MKII to a newer version, I uploaded MIOS 1.9g. Everything worked, so I uploaded the setup_sammich_sid.hex file and this time everything seems to work. I'm going to test banksticks and everything else tommorrow. Thanks again for your help. Sorry about being a bit testy. These projects were driving me a bit crazy.
  3. Stupid question... Assuming I get MIOS 1.9g uploaded to PIC with MIOS Studio MKII, I should upload setup_mb6582.hex instead of setup_sammich_sid.hex? I'm going to upload MIOS after I get home from work, so I'll be able to see what's going on then.
  4. ALL RIGHT!! TK sent me the Beta for MIOS Studio MKII and uploading seemed to work.... I say seemed because after uploading setup_sammich_sid.hex, I got the message "Rebooting MIOS" on the LCD of the Sammich. Unfortunately nothing happened after that. I tried turning it off and on after shutting down MIOS MKII and re-starting, as well as trying to start up 9.4 (which crashed as soon as I connected the ports and started the Sammich) to no avail. Now, when I turn on the Sammich, I just get blocks instead of "Ready". These Midiboxes hate me.
  5. Thank You nILS. Now back to the question: Is it possible to send the hex file information to the PIC through another PIC programmer?
  6. I'm at a bit of a loss as to how I should proceed with the Hex upload. I've tried several different approaches (), and nothing has worked. So my question: Is it possible to send the hex file information to the PIC through another PIC programmer? I've seen a few here at SparkFun Electronics, but I'm unsure if it would even work. Thoughts?
  7. OK, I'm now able to get MIOS to recieve the Ready message ("SysEx: F0 00 00 7E 40 00 01 F7") on the PC. I had to re-install MIDI-OX, but I've gotten the message in MIOS studio. However, when I'm trying to upload, the device is still not uploading. The only thing I'm noticing now is that the LED in the top righthand corner is on occasionally. Is this a sign of a hardware issue or is the problem still in the software?
  8. I thought I had it correct (Interface in to MIOS IN, Interface out to MIOS out). Though, I have noticed that there are more than 1 set of inputs/ showing up on my Mac. I'll post a screencap when I get back home. As far as using MIDI-Ox, do I need to hook MIOS into the MIDI-Ox input or am I adjusting the settings as described in the Wiki? I'll double check the MIDI-Ox settings on the netbook, again when I get back home.
  9. Sorry about the delay. I tested both interfaces for MIDI input with the GorF and both were successfully transmitting MIDI data into the Mac. I then plugged in the sammichSID and got the following data once the unit turned on. With Audio Kontrol 1 21:18:01.182 From In SysEx Otari 8 bytes With Midisport Uno 21:23:15.541 From Port 1 SysEx Otari 8 bytes Is this the data that the core should be sending? As for my Java version, here's the data: java version "1.6.0_17" Java SE Runtime Environment (build 1.6.0_17-b04-248-10M3025) Java HotSpot 64-Bit Server VM (build 14.3-b01-101, mixed mode) As for Mandolane, I couldn't find a way to determine the version code. The package I downloaded was called "MandolaneInstallV2_96.mpkg" -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I noticed that on MIDI Monitor, that it has a function to use it as a way to send data. Could I use that layer to send the ready signal to MIOS and filter the output through MIDI Monitor back to the sammichSID core?
  10. Two interfaces simultaneously, eh? After I figure out my Java version and test with MIDI monitor, I might have to try that.
  11. The PC is was trying to upload hex on (Acer Aspire One netbook) also was unable to recieve the upload request. I also tried it again for the sammichSID and got the same results as on the Mac (no upload request) I'll double check, but I downloaded Mandolane recently (within the last 45 days or so). I'll try the MIDI Monitor test when I get home from work. I'll also double check what version of Java I have installed on my Mac. Would it help if I tested Sysex recieving through other hardware for a benchmark/proof of the MIDI in working?
  12. Mac OS 10.6.2 on a Black Macbook (2.16 Core 2 Duo w/ 2 GB RAM). I've been testing with a Midisport Uno and NI Audio Kontrol 1 (I've been testing both interfaces via USB, using both available ports on the Macbook, one at a time). Like I said before, I've used these interfaces with Reason and haven't had a problem getting MIDI input. I've also been able to dump SysEx data using SysEx Librarian onto my Mac.
  13. OK, tested MIDI input using GorF sequencer. First played GorF into Reason to see if the Midi interfaces worked at all. Both worked. Then I tried various configurations to see if I could get MIDI input to register in MIOS studio. Nothing would work.
×
×
  • Create New...