audiocommander

no one keeps you from doing that, but if you ever got a problem inside a small box, you'd know that it's sometimes better to have some unpluggable and removeable single items in it. next point is, that not everyone is using a metal case...

Hello again, I just stumbled about a slight programming problem with MIOS: I want to control Speakjets Frequencies by SCP. A value between 0 - 3999 (11bit, manual p.10) is expected. For example: "\0 1J 2500N X" would set the frequency of OSC1 (1J) to 2500Hz (2500N)... but as far as I can see, [tt]MIOS_IIC_ByteSend(unsigned char b)[/tt] - called by [tt]IIC_SPEAKJET_TransmitByte()[/tt] - just sends 8bit, whereas the SpeakJet receives up to 16bits. It's no problem from the PC, so I wonder if there's a method to transmit an 11bit value by IIC so that it's automatically received in the right way? Otherwise I would have to change the PIC16-Firmware and write kind of a MSB/LSB merging function... Cheers, Michael

TV-Show-Voice from the Off: Just Two Messages Left Fooooor The Magical Five Thoouuuuuusaannnnd :o

right, but what do you want to do with that 10bit value? (you can send 14 bit by MIDI btw). There is more than one possibility: (N)RNP (CC's with a MSB/LSB value), PitchControl, SysEx... That really depends on what is receiving your message (eg modulation only accepts 0..127, so 14 bit is quite useless, whereas for pitchBend it can be very useful...)

CC is the abbrev. for ControlChange, which is one of the most important Midi Messages. NRPN is an advanced feature to allow transmission of values greater than 7bit (0..127) See here: http://www.midibox.org/dokuwiki/doku.php?id=midi_specification If you follow all links on this page, you're a MIDI-Pro :) Your question implies a lack of understanding: Why do you want to convert a 7bit value to a 14bit value? (You can't make 14 cookies if you just got 7 ;) - means: increase the resolution from low to high. However, you can read the 10bit value of an AIN-pin (maximum resolution you get from MIOS) and convert (and send) this as 14bit (N)RPN or PitchBend, for example (this is also interpolated, but you got 3 Bytes more (0..1023 is 10bit, 0..16383 is 14bit – 0..127 is 7bit). 14 bit values are just 2x 7bit with a Least Significant Byte (LSB) and a Most Significant Byte (MSB). See the midi page @ borg.com for detailed info. I'd be interested, too :)

:-* ;D

nice to hear :)

Hi Shum, I'm not totally sure about, but maybe you want to follow this description: http://www.ucapps.de/howto_tools_hex2syx.html it shows how to upload with MIDI-OX, which is proven to work. But before trying MIDI-OX, you also might try this: - increase the delay to 750 ms or 800 ms - Have you burnt another ID into your chip than '0'? => "If a different device ID than 0x00 is assigned to your core, the .syx file has to be generated again with the "-device_id" parameter." - unfortunately I don't know sysexBox, but I think that "MIOS format" should say rather "MIOS Update" (or sth similar) than "MIOS Program Memory"? (Just a guess...) EDIT: just saw here (http://www.ucapps.de/howto_tools_syxloader_18f.html), you have to set to MIOS EEPROM memory and the selected ID will overwrite the chip ID. nevertheless, the ID has to match! If I understand the messages right, your PIC is being reset when sending the 12th block. This seems very suspicious to me. If upload fails again after increasing the delay (and maybe trying with MIDI-OX), I'd recommend to look at the board again to make sure you really have soldered everything right! I had such an issue myself, where I searched two weeks for an error and missed to look at the core which I soldered some time ago and thought of it would be okay; but in fact a wire was totally wrong... but the nasty thing is, that you might not notice it, until you come to one special point... (if all these points are verified, I'd think about another midi-interface... maybe there's something wrong with your joystick/midi adapter? You're using such an adapter for AWE64, right?) Kind regards, Michael

That chip is fantastic! I just wanted to point to the Wiki, I am currently adding lots of resources and tutorials (as promised)... So if anyone here is building it's own SpeakJet IIC module, you might want to look there before :) I'm also working on a first MSA/SCP class to control the module by CC's and NOTE_ONs, so keep an eye on it ;) Cheers, Michael

I see :) I'm always uploading with SysEx-Librarian because it's so comfortable, but of course you're right about the POV of a Windows-Machine (I forget that sometimes :) ) I've sent shum the .syx-files I used for my Core(s). I'm very interested to see if they will work being uploaded with MIDI-Ox... Best Regards, Michael

just add "-force" to get a valid .syx-file: [tt]./hex2syx.pl mios_v1_9_pic18f452.hex -os_upload -force[/tt] [tt]Block 000400-0007FF allocated - Checksum: 4E Block 000800-000BFF allocated - Checksum: 3A Block 000C00-000FFF allocated - Checksum: 23 Block 001000-0013FF allocated - Checksum: 40 Block 001400-0017FF allocated - Checksum: 6A Block 001800-001BFF allocated - Checksum: 5D Block 001C00-001FFF allocated - Checksum: 35 Block 002000-0023FF allocated - Checksum: 51 Block 002400-0027FF allocated - Checksum: 11 Block 002800-002BFF allocated - Checksum: 7F Block 002C00-002FFF allocated - Checksum: 42 Block 003000-0033FF allocated - Checksum: 2E Block 007C00-007FFF allocated - Checksum: 51[/tt] If you reply, just open up "Additional Options" below the reply text field, there you can attach a pic. Or upload your pic at imageshack or similar webservice and link it by 'img' and '/img' enclosed in brackets ;)

cool, 8) how could I've missed that? I always thought that came with iMIDI :)

Hey madox, thanks for this interesting posting :) Maybe you want to copy (or link it) to the Wiki? (maybe to the FAQ-Section: http://www.midibox.org/dokuwiki/doku.php?id=questions_and_answers#building_your_midibox )? This would surely help to understand what's it for and where to put the caps! Cheers, Michael

yes, I wonder, too: what's the thing about the host application to tell the MB it's config while most applications support taking the config from the MB anyway... IMHO all mentioned host applications support midi assignments, so why sit for hundreds of hours and write an MBHP_TCP/IP module and then you still need to implement the receiving handlers in your MIOS-app... I can imagine this consumes valueable space and processing time? I mean, this would be definitely a nice module to play around with, but the reason for this is not really clear to me :) Best regards, Michael btw: there's a nice software called iMIDI from GrantedSoftware for Mac OS X, that provides a MIDI connection over ethernet if installed on every client (just to mention it)

Yes. It's in the hex2syx.pl file: # SYNTAX: hex2syx.pl <hex-file>.hex [<-device_id 0x..>] [<-bankstick <0-7>] [-os_upload] [-force] [<-debug>] In other words: you need to type [tt]hex2syx.pl myfile.hex -os_upload[/tt] That's a precaution thing to prevent accidential overwriting of parts of the system! Maybe we should think about mentioning this in the README.txt of mios_download. I'd be very interested to hear the MIOSStudio-version you used for trying to upload the hex-file. If you succeed now with sending the .syx-file (and I think chances are very high :)), it might be likely that there's an error in MIOSStudio (because this would be the second case with this specific upgrade error)... please keep us up to date - best regards, Michael :)

table3 from midi.org (find the link at the midi-page/Basics on the wiki) shows you what controller numbers (MSB/LSB pair) you might want to choose for that (not really required, but nicer sticking to standards) :)

"Look man! How cool is that?! :o – a ganjaPot" "Yeah! Let's Rub'n'Roll" ;D

I'm thinking about it since a few months now, but did push it away because I cannot really decide what I want on screen and what not... and everytime I made my decision, I notice that it's crap, because I haven't though of something else... that would be a reason to use mb64 ;)

I haven't actually read about what application you are going to use? If you plan to use the MB64(e), stryd_one is right about ASM. If you're writing you own app, this would be quite easy to implement in C (but of course with MB64(e) comes a whole bunch of features that aren't thaaat easy to recode, for example bankstick patch storages or the whole LCD menu structure) – However, if you just need to send some Midi-Values when turning or pressing something, and you know a bit of C, coding your own app would be an option. It's really easy, once you've setup your SDCC/GPUtils environment ;) There's a nice C-skeleton available and you just have to go to your DIN-Notification function and write some lines... that's it :) Cheers, Michael

yeah, agreed. I just switched to a new one with digital controlled temperature. It's all a lot faster and more accurate to solder. And you definitely need a small tip for soldering SMD! t's really hard to fix, once you accidentially soldered to neighboured pins... so I would try to avoid this from the beginning... Cheers, Michael

yeah, agree :) I would try these two most obvious steps first: - uploading as .syx via another program - another MIDI device and/or driver update? There are quite a number of MIDI devices having trouble transmitting sysEx properly (I tried a Hercules FW card last week and got a reproduceable kernel panic when transmitting a syx-file to my core :o ) rgds, Michael

no ;D (sorry, couldn't resist)

I payed 3,- EUR for that supply (@Reichelt) ;) And the right power is elementary as you see. A "burned" PC costs you hundrets of bucks and a "burned ToS" costs your life... don't spare at the wrong end! ;) Regards, Michael

;D ;D LMAO...

I don't know, unfortunately I don't own an x-y pad :-\ But to cheer you up: I have also some linear softpots which require a lot less pressure... and in contrast to the round ones, it's not that hard moving the finger up and down, but you got to try this: move your fingertip in a circle, have noticeable pressure, do it on a plastic underground (sqeeee) and try to get a smoth movement (eg for controlling a fadeout)... :) This is nearly impossible with the 360° pots I have. I'm sure, they tested it only with wooden gloves for usage in laboratories and not with sweaty fingers in a nightclub ;D