Jump to content

audiocommander

Frequent Writer
  • Content Count

    1,358
  • Joined

  • Last visited

Community Reputation

0 Neutral

About audiocommander

  • Rank
    MIDIbox Guru
  • Birthday January 1

Contact Methods

  • Website URL
    http://www.audiocommander.de

Profile Information

  • Gender
    Male
  • Location
    Nuremberg, Germany

Recent Profile Visitors

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

  1. Hi there, hmm, that sounds a bit strange. Saving presets should just work. You can save anywhere, you don't have to select this particular menu. BNK is to select the Bank, PRG is to select the current Program. So, select a Bank/Program and press (the red) WRITE button. Then you can (re-)load this Program anytime. If you didn't save previously (or if there's some other data), it just loads and interprets that other data (probably nonsense). However, if your DIN wiring is still messed up and the LOAD/WRITE buttons aren't working properly, that would also explain why saving doesn't
  2. Well, there can go a lot of things terribly wrong. To rule out wrong wiring, you could do a general test by removing the encoders and hooking the device up via MIDI. ACSensorizer has a MIDI control API: http://www.midibox.org/dokuwiki/doku.php?id=acsensorizer_04#midi_implementation_charts see NRPN Controls and "Examples: Turning the Menu Wheel (virtually)" I've seen encoders that have different pin configurations than the ones I used here (at 9.) http://www.midibox.org/dokuwiki/doku.php?id=acsensorizer_04#step-by-step_building_instructions Best, Michael
  3. Hi Pawel, cheers and nice to hear you like it. First of all, I have no experience how to compile it with the latest setup. I haven't updated up by MIOS compiler environment for years. But looking at your makefile output, there's clearly something missing with your path, missing in your makefile or indeed simply missing MIOS files in the directory (it says: No such file or directory). So, the error at this point has nothing to do with the ACSensorizer project. Second: please look back a couple of pages. There are at least two different encoder types around and you have to play arou
  4. cheers sneakthief! Thanks for helping out. I was offline a couple of days :sweat: @Elektruck nice to hear you got it working! Hope you'll have fun with it. Best, Michael
  5. Hi Analog Monster, no, there isn't This project has been created 2007, so there's only a PIC based core module: http://www.ucapps.de/mbhp_core.html :-) Though I doubt that anything faster would do any good, as the SpeakJet is quite old and slow as well. cheers, Michael
  6. YAY! (^_^) Congratulations! This is looking really nice, and I like your performance! Cheers, auco
  7. Hi Chris, The beams are not supposed to exacty face each other, that's why I pointed them to different directions (otherwise the bottom distance sensor might receive the beam from the top sender). For all other questions, I suppose you might have overlooked ACHandTracker.h? /* * ACHandTracker.h (...) * This sensor matrix fetches the readings of 4 GP2D-Sharp GP2D120X distance sensors * to calculate additional vars. The matrix is set up by 2 top and 2 bottom sensors * If you put your hand in this space to simulate a hand-talking puppet following * infos are ac
  8. Heya, nice to hear it's working :thumbsup: IIRC there's a MIDI Merger setting somewhere that activates MIDI forwarding to the output. Best, ac
  9. sry, I'm on the Mac here and am not at all up to date with all the latest developments. But I'm pretty positive that all the registers in ACSyncronizer are fine :sweat: (it's written in C, so the error probably comes in after the ASM is generated). Regards, M.
  10. Hi Chris, v0.1 uses a 16x2 LCD and in v0.2 I'm using a 8x2 LCD. As 8x2 LCDs are quite rare, I suspect, you are showing the 8x2 output on a 16x2. Which works, but it might look strange. The O means "Oscillator", the E "Envelope", B is the base note and SPAN is the 4-char code for the current scale (SPANISH) ...but this is all in the docs: http://www.midibox.org/dokuwiki/doku.php?id=speakjet_application_software_v_0.1#lcd-values Also, you can take a look in the main.c file to see the LCD output function: DISPLAY_Init() and DISPLAY_Tick(). These are really clean to read and yo
  11. Hi Chrisbob, there are a couple of threads on this forum, where we discussed the implementation of the Sharp IR sensors in great detail. As you already found out, they don't deliver the full 0-5V range, so a scaling is required. Personally I found software scaling much easier than hardware scaling (requiring an amplification circuit and a higher voltage) and thus implemented a good software scaling that works well. Moreover, the scaling can be calibrated which is a lot nicer than hardware scaling. Please use the search function to find the relevant threads (good keywords are: IR, distanc
  12. IIRC yes, that is because of the way the SpeakJet works - you can send some control messages to it and then it'll react. I don't think it was possible to play a vowel and then change the pitch of that playing vowel. In contrast to changing an OSC that has been switched on, so there are much more control possibilities. Allophones are kind of pre-calculated OSC-Settings with specific curves, so (again IIRC) you can't alter them that much in realtime. However, you can alter almost anything if you know it in advance. But I guess the SJ has been produced for enunciation with a dictionary (there's a
  13. indeed, it's just a very tiny (and old!) chip, so one shouldn't expect too much, but I really like your demo! About the MidiChannels: right, I experimented a bit with this version (but it's nearly four years now, so I don't remember exactly what I changed, but your description sounds like it's all fine). I guess you've already seen it, but you can find the (outdated v0.1) Midi chart here: http://www.midibox.org/dokuwiki/speakjet_application_software_v_0.1#midi-implementation-chart. You can also take a look in the IIC_SpeakJetMidiDefines.h file and adapt these to your needs: // ******
  14. Hm, sorry, I don't know if there are any custom made PCBs out there... don't think so. I did several matrix boards, one of them I painted green (though I don't know why, it was just a fun-thing; probably because there were some old marks on it or something like that). The board used for the machine in the Kinetica Gallery was the manual matrix board though :sorcerer: Cheers, ac
  15. sure, just take a look in main.h. Maybe the default values (BUILDMODE_DEFAULT) are okay for you. I just seen that the AIN Matrix (HandTracker) is disabled by default, so it might even work without tweaking. cheers, ac
×
×
  • Create New...