Jump to content

audiocommander

Frequent Writer
  • Posts

    1,358
  • Joined

  • Last visited

Everything posted by audiocommander

  1. well, "not a lot" seems more than none :) if you want to try, follow the instructions on this page: http://www.ucapps.de/mios_c.html if you got your environment set up, load the clockbox source and try to recompile. If the recompiled .hex (or .syx) file is the same as the one that came with the project, we can proceed to the next step. Best, Michael
  2. If you have minimal experience in programming, it shouldn't be that hard to adapt the code and half the output to 48ppqn. Have you?
  3. Don't worry, the problem is on my side: I just thought 8 softPots and some LEDs wouldn't be that expensive, but after taking a look at the used parts, it makes absolutely sense. Sorry for the confusion ;-) Best, Michael
  4. sorry, Josh; I wasn't prepared to spend 430 / 500 $ (US-$, I guess). Still find it elegant and useful, but can't afford it currently. Best, Michael
  5. hi everyone, If there's no time-pressure, I volunteer for setting up an installer for Mac OS X. A binary installer for all the necessary tools and a nice Xcode template would be wonderful, wouldn't it? The same could be done for eclipse on Windows and Linux ...of course only, once I managed to set up the environment by myself ;-) I'm not sure if Arduino's IDE is really the ideal to look up to: I mean, it's a nice environment, but the main reason for me not choosing Arduino (and instead going for MBHP/MIOS) was in fact its interpreted language and specialized IDE: I wanted to program in C with the IDE of my choice. That's because I learnt programming with Lingo (Macromedia Director) and based on the experiences I made back then, I don't feel like I ever want to use a slow "specialized" lingo again. Nevertheless, I agree, that installers are the way to go :-) Best, Michael
  6. hm, I would also tend to Jidis' opinion: this sounds probably more like a driver issue or a chip bug (guess this cable has some kind of converter chip?!) :-\ I would test the device with another operating system; if it works on another OS, there might be an alternative driver available - if not, I'd suspect the chip. But I'm no expert with electron behaviour in cables, just guessing ;) Best, Michael
  7. Hi Sasha, SysEx issues may happen with some devices. There's a blacklist on the wiki (well, list sounds a bit overdone for three entries ;D - but I'm sure there are more of those) http://www.midibox.org/dokuwiki/midi_interface_blacklist Best, Michael
  8. hm... did I understand this right, that I first have to install the pic16 toolchain? I tried this on OSX 10.4.11. This is what I got right now: Am I missing something? ps: no stress from my side, don't want to distract your attention from more important things, Didier ;-) if I succeed, I'll complete the OSX part in the wiki :)
  9. http://www.midibox.org/dokuwiki/c_tips_and_tricks_for_pic_programming#bitfields_unions_structs ;)
  10. wow, that sounds great!!! :D I hope I find some time in the days past christmas to give it a try; got some 4620's lounging around in drawers that just waited for a service like this ;D Thanks and Cheers! Michael
  11. I'm not getting the point: We just improved greatly the possibilities and the design of the wiki, but there's still so much to do that I do not understand this useless discussion of "redesigning ucApps" Our place is the wiki and we can put, sort, redesign every information how we like it. If I think about the time it took to reply here and the huge amount of chars I see: this time would have been better invested in writing a nice short tutorial instead, filling up the wiki with some really useful informations - ::)
  12. IMHO you have to edit the 452.h file; don't think there's a 685.h file around - http://www.midibox.org/dokuwiki/mios_pic18f4685 Though I guess the PIC selection got easier with the latest MIOS releases, maybe stryd knows more about this? I always took the easy way and bought 452's instead ;) best, Michael
  13. hehe... S1 is back ;D cheers, mate
  14. Hi fsvo, Just look at the first error: [tt]main.c:103: error 65: function 'Init' already has body[/tt] That tells you, that there are two Init() functions, and there are indeed: - from main.c the emtpy skeleton method: void Init() {} - from your code snippet: void Init() { TRISA &= ~( ( 1 << BIT_CLOCK ) | ( 1 << BIT_LATCH ) | ( 1 << BIT_DATA ) ); } Just merge your code properly into main.c Not sure about the USER_NotifyReceivedEvent() method in your snippet; I never worked with the USER_ namespace, maybe that's okay - I'd use the MPROC_NotifyReceivedEvent() from main.c if it does not receive any MIDI Messages as expected Best, Michael
  15. Hi Ultra, in result from our chat yesterday, I would gess that the Core and the MIDI-Input is okay, but you probably have an error in one of these locations: - Core: around IIC connector - Cable between Core and SJ-Module - SJ-Module: from IIC to PIC16 - SJ-Module: from PIC16 to SJ I'd visually check all connections in these areas first. If you do not succeed in finding something strange, I'd solder a serial cable and load Phrase-A-Lator (http://www.magnevation.com/software.htm), so you can see if your SJ-board is working. Best, Michael
  16. Hi Bill, it sais: This is the state when switched "on". Selectable values range from 1ms to 2ms (1.5ms middle) like the RC-model specification). When the extended Mode has been selected, you can switch back to standard mode by writing a 0 (zero) to register 21. Values from 1 - 255 (0x01 - 0xff) in register 21 switch to extended mode Hope this helps ;) Best, Michael
  17. Hi ultra, I have three questions: 1. I guess you're using kII 026, right? 2. Is there any sound at all coming out of your speakjet? -> Do you hear something when you power up your device? -> Do you hear something when you're using the MIOS-Studio Keyboard (for example)? -> Do you hear phrases when you send CC#9, values 0 to 15? -> Do you hear vowels&consonsants when you: -> set the mode to CH 7 (Vowels & consonants) -> then change Jaw (CC#40) and Tongue (CC#41) and (optional) Pitch (CC#42) 3. Your Keyboard sends on CH 1, that's good. Now what Channelmode is set on kII (the number you see in the display, right after the scale?) It should read 1..3 or 11..16 but not 4..9. This is the Channelmode: [tt] C#-MAJ 16 O-E-_ ^ Base-Note (change with Listen) ^ Scale ^ Channelmode ^ OSC & ENV Forms ^ BPM Sync Length (1/32 to 1/cantremember) [/tt] If the Channelmode is 1 (Phonemes&FX), you must hear some allophones in the center range of the keyboard (eg. Note 64); on Channelmode 11-16 you should hear sounds on the whole range: [tt]// ********** CHANNELS ********** // channel assignments for NOTE_ONs 0x90 and NOTE_OFFs 0x80 functions // MIDI CHANNELS for NOTE_ONs #define SJCH_SOUNDCODES 1 // MSA Soundcodes (Allophones + FX) default 1 #define SJCH_ALLOPHONES 2 // MSA Soundcodes (Allophones) default 2 #define SJCH_FX 3 // MSA Soundcodes (FX) default 3 #define SJCH_PITCH 4 // MSA Pitch (Note2Freq) only! No sound output! default 4 #define SJCH_VOWELS_DIPHTONGS 5 // MSA Pitched Vowels incl. Diphtongs default 5 #define SJCH_CONSONANTS 6 // MSA Pitched Consonants (depending on jaw & tongue)* default 6 #define SJCH_VOWELS_CONSONANTS 7 // MSA Pitched Vowels & Consonants (mixed) default 7 #define SJCH_CONSONANTS_OPEN 8 // MSA Pitched Consonants produced by mouth opening default 8 #define SJCH_CONSONANTS_CLOSE 9 // MSA Pitched Consonants produced by mouth closing default 9 #define SJCH_PERCUSSIVE 10 // MSA Soundcodes (Percussive Consonants) default 10 #define SJCH_OSC1 11 // OSC 1 (Note2Freq, monophon) default 11 #define SJCH_OSC2 12 // OSC 2 (Note2Freq, monophon) default 12 #define SJCH_OSC3 13 // OSC 3 (Note2Freq, monophon) default 13 #define SJCH_OSC4 14 // OSC 4 (Note2Freq, monophon) default 14 #define SJCH_OSC5 15 // OSC 5 (Note2Freq, monophon) default 15 #define SJCH_OSC_SYN 16 // OSCs 1 to 5 (Note2Freq, harmonic polymode) default 16 [/tt][/code] And I expect, you did not customize this file? That's perfectly normal - this is the harmony listen: you're setting a new base note (when CC#82 is >64 you're in listen mode) Best, Michael
  18. uups, I thought I'd fixed this in Edit4 :-[ I attached a new package (but only design.css has been changed in the zip-package). ;-) MidiBox DokuWiki Style AC Edit5.zip MidiBox DokuWiki Style AC Edit5.zip
  19. in the media-manager, namespace "icons" - icons:iconbs.gif - icons:icondevice.gif both are 125x125px whereas the correct gifs have 100x100px :) Best, Michael
  20. jipee :D thanx twin-x!!! may I ask for one more favor: I'm exporting all png icons to gif as well, so that it's shown in IE - but I accidentially uploaded two .gifs that are too big (125px). The internal thumbnail-module cannot shrink gifs with transparencies, so I need to replace these two gifs, but I must not delete images on the wiki... can you do this for me? => iconbs.gif & icondevice.gif (both ugly & black) thanks again, best, Michael
  21. Hm... is this now the final state, as Twinny removed the css-note? :'( this is the version where I tried to fix stryds font-issues (has been never installed) (v4) : http://www.midibox.org/forum/index.php?action=dlattach;topic=9718.0;attach=1576 this is the version that was last installed (v3): http://www.midibox.org/forum/index.php?action=dlattach;topic=9718.0;attach=1520 Please note that I got a tiny little bit more time atm than normal, so if there are issues or if I should build a package to be installed with Dokuwiki (or hack/update the box-plugin) to be easily maintained, please tell me... Best, Michael
  22. hmm; I switched back the homepage to the last state and added a temorary note. The colors are missing of course, but at least the positioning is relatively okay (depends on the window size). Afaics only the Box-CSS has been resetted to its original state. best, Michael
×
×
  • Create New...