audiocommander

LOL :) ...PACMAN struggeling with death in an AIN/DOUT wire-mess ;D

If you want to know exactly, you have to learn to read exactly. If you want somebody to have patience with you, you have to learn to be polite. It's nothing but ridiculous insulting the founder of this community. Bye.

just 3 lines above your reply, I copied and pasted for you: [tt]"7 means: 7bit resolution, 15 means: 6bit resolution[/tt] (...) [tt]For a 10-bit value a deadband of "0" is recommented"[/tt] This is the second time, my copy-and-pastes for you out of the infos that can easily be found on ucapps & the forum were ignored. I'm out of this game >:( ==> http://www.midibox.org/dokuwiki/doku.php?id=forum_netiquette

Yep. And just to complete this: if you look at the MF-Page you can read: if you search the forum you get: http://www.midibox.org/forum/index.php?topic=5272.msg32427#msg32427 and: http://www.midibox.org/forum/index.php?topic=725.msg4145#msg4145 Maybe an additional hint: if you search the forum while being in a thread, the search is filted by that topic! As the C-Section is relatively young, you will miss important informations from the huge Assembler section. So try hitting "midibox.org Forum" first ;)

what a sad story :'( thank you for sharing this info. I do understand (and am thankful for not being a moderator having to bear such decisions...) that's very true. thank you also for the informations on Twin-X and the webhosting donations. I considered donating anyway, you speeded up my decision :) Best regards, Michael

wow, that's a nice thread :D I don't know about windows, but on the mac there's a calculator with a programmer's mode. That's pretty nice to understand >> and << and AND... when you see what's happening with the bits. I can also recommend a bash tool called "ch" from http://www.softintegration.com There's a free version available! It's a C console interpreter, that's very handy to test some values and settings! (and of course also available for DOS!) Cheers, Michael

allright, time has passed and hopefully everyone calmed down. I feel it's time to tell moebius that I'm really sorry he became silent. This forum is not the forum I learnt to know without moebius. I counted three occations in the past few weeks where we could have needed someone with a +10/-1 karma, if ya know what I mean ;) I tend to be very sensible if one talks rough to me, but I always apreciated moebius' thoughts and inputs and there were lots of occations where I was absolutely one opinion with him. Yeah. That's all. I feel, this had to be spoken out. :) Cheers, Michael

Nikifena, maybe you want to take a look at the schematic as seen here: http://www.midibox.org/dokuwiki/doku.php?id=application_development Just to avoid possible misunderstandings on what is MIOS... I already started with a similar schematic for MBHP, but haven't found the time to complete it yet ;) Cheers, Michael

LMAO ;D ;D I L-O-V-E this drawing!!! ;D First it showed me how these things work and besides that I like it as composition in correlation with its title: very ugly wheel. that's great!! ;D

ahh- forgot to add this one ;D That's really great! Thanks v much! :)

Hi Michaël :) I think it's Eagle from http://www.cadsoft.de, I'm not sure though... Cheers, Michael

sorry, I thought there was a link to the codeblocks tutorial (http://www.midibox.org/dokuwiki/doku.php?id=stryd_one_codeblocks) – (part of http://www.midibox.org/dokuwiki/doku.php?id=application_development) on your userpage ::) :) Michael

Hi Wisefire, you might take at look at Stryd_one's user page. He has a pretty good documentation/tutorial about Code:Blocks, an open source IDE, together with the integration of the mios_debug stuff (you can use it with a graphical debugger). If you start programming, this might be of some interest to you, because 75% of all problems are somehow code related. With a graphical debugger, you can easily inspect values of variables without having to send the code to the chip and wondering where to find the problem ;) Cheers, Michael

How about searching the forum for "Deadband"? Two pages of search results should contain a pretty decent explanation of what that is...

yeah, these are nice too :) there are also just the connectors available, too (without cables and socket) ;) just haven't found the link and no time to search... regards, Michael

naja, mehr als oben kann ich leider auch nicht schreiben, das DOUT_Set() war nur als allgemeiner "Bezeichner" gemeint für MIOS_DOUT_PinEinschalten()...sozusagen. In deinem Code wird nirgendswo diese Zeile aufgerufen: MIOS_DOUT_PinSet1(0); // schaltet pin1 am DOUT board einschalten MIOS_DOUT_PinSet1(2); // schaltet pin3 am DOUT board ein MIOS_DOUT_PinSet0(5); // schaltet pin6 am DOUT board aus mehr isses wirklich nicht. Aber wenn du die Funktion nicht aufrufst, dann ist es irgendwie klar, dass sich nix schaltet... In der Funktionsreferenz muss du auch unter C-IN und C-OUT schauen, da wird genauer erklärt, welche Werte du hinschicken musst und welche die Funktion zurückgibt...

doch :) Entweder du nimmst [tt]void MIOS_DOUT_PinSet(unsigned char pin, unsigned char value)[/tt], wobei value 1 (an) oder 0 (aus) ist, oder aber: [tt]void MIOS_DOUT_PinSet1(unsigned char pin)[/tt] für einschalten und [tt]void MIOS_DOUT_PinSet0(unsigned char pin)[/tt] für's ausschalten :) Grüße, Michael

...ist trotzem noch kein MIOS_DOUT_Set() drin ;) Grüße, Michael

Actually, there are some very nice tips on this forum for desoldering... (just do some forum search on 'desolder') If I find the time, I will post this method along with some pics to the Wiki... I did it with a very (very) thin piece of blank wire, that I "injected" below the pins and connected one end to some nearby element (eg. wrapping around an Elko). Then you can pull the other pin with tweezers; by one soft and very short touch of the soldering iron, the wire snaps below the pin to your direction and because the small amount of lead now sticks to the wire, you unsoldered the first pin! Proceed... and with a tack-tack-tack-tack... you get the others in a minute :) The only problem is, that the wire may tear apart from time to time, but I got four chips desoldered in about 15-20 minutes... and the most timeconsuming was to get the wire below the pins :) cheers, Michael

You might solder them to one end and put a connector on the other end. There are cheap plastic connectors for flat band cables, with and without cables/pins; eg. see: Reichelt Platinensteckverbinder

Das könnte vielleicht daran liegen, dass du keine DOUT-Funktion aufrufst (kann aber auch sein, dass ich die vor lauter Code nicht sehe... es ist generell keine schlechte Idee, Codeschnipsel auf das Relevante zu kürzen ;) ) Grüße, Michael

Right! Thanks Tom :D I just succeeded contolling the 5 Oscillators with my microKONTROL... (and updated the Speakjet definition listing) I'm completing the code, do a bit cleanup work and will put the updated IIC_SpeakJet-Files on the Wiki next week... Cheers! Michael :)

Then look in the traktor midi-implementation chart that exists for every midi-capable device and see what kind of messages traktor likes to receive for tape deck tempo. If traktor supports midi assignments,see if you can assign pitch wheel or NRNP messages. Then you can simply send a message of this type from your midibox. however, you could (as stryd_one mentioned) have searched this forum for traktor and would have found two threads that might be of interest to you: http://www.midibox.org/forum/index.php?topic=3852.0 http://www.midibox.org/forum/index.php?topic=3858.0 Then search for MSB LSB. There are plenty of topics covering exactly your question, even in german language. If questions remain, you might ask again here - :) best regards, Michael

Hmm.. I just realized I haven't tried sending single numbers (2 5 0 0); as they will be stored in the input buffer, I think this might be the way to do it... As I'm currently not at home, I have to try later; Cheers, Michael

Chomsky, I think you're making it a bit too complicated ;) Forget about the bits, it's just interesting to know that if the status-bit is set, then it's no data-byte, but if you're not coding a MIDI-protocol that's of no interest for you. You might rather check out the midi-tables 2 and 3 table 2 shows you the midi-summary: http://www.midi.org/about-midi/table2.shtml - NOTE_OFF on ch1 is 128; NOTE_OFF on ch2 is 129, NOTE_OFF on ch3 is 130 and so on... - CONTROLLER (CC) is in fact the same type as NOTE_ON or NOTE_OFF, it ranges from 176 to 191. for NOTE_ON you have: Type/CH + Pitch + Velocity for CC its: Type/CH + CCNum + CCValue (it's really all written down there, I can't explain it better!) basically it's just two or three times numbers from 0-255 or 0-127 (type/CHannel + parameterA + parameterB). table 3 shows you the available CCNums! The trick is to send 2 CCs, 1 MSB (most significant byte) and 1 LSB (Least significant byte). By combining the two 7bit values you get 14bit. BUT: the host (in your case B) has to combine these bytes and it won't do this automatically! And that's why stryd_one and me asked about your plans (which are still not revealed)? If you don't explain in what way your slave will process this 14bit value, I can't tell you if you should send an MSB/LSB CC or (for example) a pitch, which is recognized as 14bit by default and is no CC but a type of it's own (again, see the table!): regards, Michael