Jump to content

deletemeplease

Members
  • Posts

    95
  • Joined

  • Last visited

About deletemeplease

  • Birthday January 1

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

deletemeplease's Achievements

MIDIbox Newbie

MIDIbox Newbie (1/4)

0

Reputation

  1. I had the same problem recently, only I had MIOS v1.5. Email Thorsten as he has to provide specific firmware.
  2. ordered all the components to finish my box. First new midibox project in 7 years!

    1. Antix

      Antix

      better late than never

  3. Yes that makes perfect sense. Thank you. OK I'll give it a shot. I've read the readme, and don't really understand the implementation, but I think I should be able to search for that just fine. My switches have just arrived so I think it's testing time! Great stuff. I'll work on the switches first as the LCD is probably helpful for that. Thanks again :)
  4. I can't believe I didn't think of using decimal. I always try and overcomplicate things lol. I like the layout of this define and switch. It's very clean and straight forward. I think this is the way to go. I'm a little unclear about sending parameters to a function. Would the following work? void sendProgramChange(unsigned char sendProgramChange) { MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(sendProgramChange); // Program Number 12 MIOS_MIDI_EndStream(); } Or do I need to ensure that my unsigned char is different from the function name? I presume it's correct to do this as a void, as I don't particularly need any code output? Oh really? Thats very interesting indeed. I'd rather get away from using din/dout boards to save space. Is this difficult to code? Any functions I should be looking into? Knowing what I'm looking for might make it easier to search the forum. Thats a good point. The manufacturer of the box I'm trying to control states that the first scene is in fact patch 0, so I think I'm ok. Shouldn't be difficult to test. So you would actually recommend using the value as hex in my case?
  5. Hi. I'm trying to plan out my controller in my head and figure out the code as I go along. Below are my two questions, skip to the end of the post if you need more info about my project. Question 1) I need to send a program change message, value 12. Which of the following is correct? MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(0x12); // Program Number 12 MIOS_MIDI_EndStream(); OR MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(0x0C); // Program Number 12 MIOS_MIDI_EndStream(); I'm pretty sure its the second, but I thought I'd check. Question 2) I have 6 buttons, I want 4 of them to send program changes, and the other two are more complex so lets tackle the first four first. How do I set these up in the ain64_din128_dout128_v2c example? Can I create an array like the following. Please forgive my syntax, I only know a little objective-c, so I realise the syntax is probably massively wrong: static unsigned char switches[4] = { 0x00, 0x06, 0x0C, 0x12 }; And use MIOS_DIN_PinGet to say - "Pin 2 was pressed, select location 2 from the array". Then is it possible to store this hex result as a variable which i can use in a MIDI stream request? More information about my project It's a simple MIDI box. 1x core, with PIC18F452, 1x DINx1, 1x DOUTx1. 6x buttons, 6x LEDs. The first 4 buttons send different program change messages, the last two buttons send CC#. On first press they send value 127, on second press they are toggled to value 00. I'm quickly realising I'm in way over my head, but everyone has to start somewhere right?
  6. You don't have to use Xcode, it's just a nice way to edit projects using C. I personally tweak projects ib TextWrangler and then use the make command in terminal.
  7. In case anyone is struggling to compile their apps, here's what I do. Edit your project files in Xcode (or TextWrangler if you prefer something lighter), save your files, then open Terminal.app. Now type 'cd ' (without the quotes, but including the space. Now drag your project folder from Finder onto the terminal window. Now hit your return key. This will tell terminal that we want to use this folder as our root folder. Finally type 'make' and hit enter. A couple of moments later you have a .hex file which can be uploaded with MIOS studio.
  8. OK I've had some time to think, and plan out another layout. This one has fewer cuts, and I could make this even smaller. I like the look of that prototyping board you suggest Nebula. I need to make this as small as possible, as I'm making a MIDI bank switch for my guitar effects box, and I want to cram it into as small a space as possible. Even the small Core board is looking massive!
  9. Yes, true, but I don't really have time to etch myself. Plus I have a cupboard full of photo chemicals, and I don't think my girlfriend would be happy with ferric chloride in there too! I couldn't seem to find prices for fabrication in the UK. Is it worth doing? I would prefer a PCB really.
  10. Yes good point. The main reason i positioned the IC as I did was to enable the +5v line to run under the IC uninterrupted.
  11. so happy my 7 year old PIC18F452 is now running MIOS v1.9g!

    1. nILS

      nILS

      upgradability level up for MIDIbox!

    2. deletemeplease

      deletemeplease

      yes, but now I think i want at least CORE v3, or CORE32.. But I can't think of a project that requires it.

  12. I've designed a veroboard layout of DOUTx1. I've never made my own veroboard layotu before so is anyone able to double check it and make sure I haven't made any obvious mistakes? I'm using this schematic.
  13. Just a quick update, I emailed Thorsten, and he's sent me a .hex that will update both the bootloader and MIOS in one go. No programmer necessary. This is definitely the route to take if you are impatient like me, and do not read the README file properly. :frantics: ALL FIXED NOW!
  14. Cheers nILS.. It'll will be solved if I can find my JDM in my box room. Not looking forward to searching for that. Yes I haven't been around here for about 7 years :) I'm sure everyone will become well acquainted with me again as I ask further stupid questions, and solve them after 30 minutes. It shows that I haven't been here for a while as even the bootloader has been updated! There was a point when I thought that would be impossible! In fact my poor little PIC18F452 is looking decidedly ancient. Really impressed with the new MIOS32 interface, looks very tasty indeed. Take it easy buddy.
  15. OK apparently I should have read all the way to the bottom of the Readme file. I think I still have the old v1.1 bootloader. Where can I find the v1.2 bootloader? I still have an old JDM programmer somewhere in the house! Never mind. I found it *facepalm*
×
×
  • Create New...