stryd_one

There's no timestamping in midi, that's just the time that the PC counted when it's received/the time when it sent it.

Well.... Seems i was too quick to blame MS, according to the international variables thread I created and ilmenator's response, the %programfiles% variable is intact in German Windows as it should be, and should be left as-is on the wiki page... in fact, I have no idea how your system is able to find the compiler because the path you've set is invalid!

LMAO ohhh yeh. I use a couple of firefox addons to take care of most BBCode/wiki tagging, and use the GUIs wherever possible... but the various different 'code' tags ALWAYS get me! dammit! I added another link to it in the big midi spec page too, might save some people a very heavy read ;) Thanks!! Doco is good!

This topic has been moved to Design Concepts. [iurl]http://www.midibox.org/forum/index.php?topic=12054.0[/iurl]

Well, this isn't midification - the DX7 already has midi support. What you're talking about is a knob control box, basically it's an MB64 or similar. I fixed the topic (and your capslock problem, you should look into that) and moved it for ya. A quick google search confirmed my suspicions - it only responds to a few CC's... Controlling via sysex is slow and on synths of that generation there would ofen be total dropouts when recieving sysex.... which leaves you with a few options: Control limited things with CC's - it already has a modwheel etc for that. Not worth it. Control via sysex - timing will not be realtime. Not worth it. Control one parameter at a time with the wodwheel, and use sysex to map the modwheel to a certain parameter - if that's even possible (check your manual) it'll be useful for changing one parameter at a time, so long as you don't want to change that parameter in realtime.... and then, you could do that within the patch and use the modwheel, so again....Not worth it. Just my 2c (based on several assumptions)

Don't worry about the board, forget all that - just take the C64 PSU just by itself, plug it in, find the pinout (google, or a forum search here will probably do it), and test the voltages. If you're not reading 9V from the correct pins, that'll explain why your optimised board isn't outputting 14V.

Now THAT is a troubleshooting post!!!! You get a fricken gold star man. All newbies, take note!!! You're totally right about everything. It's the opto. When you go for the long drive (sorry about that) grab a few. They're tetchy little buggers. Wow you made that easy! Thanks!

Heh, it takes some getting used to a new OS :) So, the OS sees the midi ports... I assume the apps do too... First thing I'd be doing is trying it with a loopback cable...

Yah that link is nice, I like the pics especially The wiki should be pretty easy... assuming you're already logged in (same username/pass as the forum) then you can edit any existing page such as this one http://www.midibox.org/dokuwiki/midi_specification .... Or, you can make your own URL like http://www.midibox.org/dokuwiki/simple_midi_specification and when you visit it, it'll tell you that it doesn't exist yet, and you can create it. Just, don't forget to edit some other page to link to your new one :)

I swore I wouldn't help you because you were so lazy before but anyway..... Is the c64 outputting 9V AND 5V ?

If you could pay this thread a visit International Windows Users Please Read! That would rock :)

Hi guys, In order to create more useful documentation for non-english-speaking MIOS users, it would be great if you could help me out. Just type the following command in the cmd.exe/command.com prompt: SET And paste the output here. You can feel free to edit any private data - if you're really paranoid you can even remove all the values - it's the variables' names I really need. this thread explains why :) Thanks!! PS - if anyone can translate this request for the international forums, that would be great. Here's mine: ALLUSERSPROFILE=C:\Documents and Settings\All Users APPDATA=C:\Documents and Settings\stryd\Application Data ** Hid my real username artcpport=2000 CLIENTNAME=Console CommonProgramFiles=C:\Program Files\Common Files COMPUTERNAME=stryd ** Hid my real computer name ComSpec=C:\WINDOWS\system32\cmd.exe FP_NO_HOST_CHECK=NO GPUTILS_HEADER_PATH=C:\gputils\header GPUTILS_LKR_PATH=C:\gputils\lkr HOMEDRIVE=C: HOMEPATH=\Documents and Settings\stryd ** Hid my real username LOGONSERVER=\\stryd ** Hid my real servername MIOS_BIN_PATH=C:\MIOS\_SVNMIOS\trunk\bin MIOS_PATH=C:\MIOS\_SVNMIOS\trunk nttcpclientport=2051 nttcpport=2050 NUMBER_OF_PROCESSORS=1 OPENSSL_CONF=C:\Program Files\OpenSSL\bin\openssl.cnf OS=Windows_NT Path=C:\Perl\site\bin;C:\Perl\bin;C:\MSYS\1.0\bin;C:\gputils\bin;C:\SDCC\bin;C:\MinGW\bin;C:\Program Files\Windows Resource Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ActivCard\ActivCard Gold\resources;c:\program files\MSSQL7\BINN;c:\Program Files\Microsoft SQLServer\90\Tools\binn\;C:\Program Files\MKVtoolnix;C:\Program Files\TortoiseSVN\bin PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.tcl;.pyo;.pyc;.pyw;.py;.CH PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER=x86 Family 6 Model 13 Stepping 6, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=0d06 ProgramFiles=C:\Program Files PROMPT=$P$G PURPLEHOME=C:\_DATA\IT\Settings\Pidgin SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\WINDOWS TEMP=c:\Temp TMP=c:\Temp ULTRAMON_LANGDIR=C:\Program Files\UltraMon\Resources\en USERDNSDOMAIN=stryd.com ** Hid my real domain USERDOMAIN=stryd ** Hid my real domain USERNAME=stryd ** Hid my real username USERPROFILE=C:\Documents and Settings\stryd ** Hid my real username VS80COMNTOOLS=C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\ windir=C:\WINDOWS

I'll settle down when you wait patiently. The first post was made especially so that posts like yours would be unnecessary. Further than unnecessary, they're unwanted, and impolite. If you're gonna be rude, expect a rude reaction. Don't throw fuel on a fire and blame the fire for burning you. Congratulations, you've been waiting about 1/3 as long as me. Note the complete lack of "are we there yet?" posts from me? Let that be your guide. [img width=100]http://www.buzzshop.co.uk/images/devil-smiley.jpg Oh yeh, that's me to a tee. ;D Edit: this one makes it 6669. I don't have a devil/angel/pornstar smiley, sorry :D

Nice!

ISA AWE64....... Do expansion cards work after they've become fossilised? :D Drop by the chat too, maybe we can help in there. Realtime chat is good for troubleshooting.

Great news! :D NOW is the time for you and rasteri and sasha to get your shit together!!!!!!!!!!!!!!!!! Seriously, don't leave it until after the boards are created to merge your work into one, it'll only cause problems if you decide to do it later, and it'd be a damned shame to see a really good job done on the boards but to see them limited in their functionality.

Don't forget the wiki - there is a whole section devoted to this subject at http://www.midibox.org/dokuwiki/how_to_mix_c_and_asm. At the moment, it's very bare, although it links to a very informative forum post. Perhaps you'll flesh it out a little when you finish your work? :)

LOL OMG that was boring. He talks about ignoring what makes up music and how sound is everywhere... Then he makes some sounds that fit all of the usual criteria to be called music (it has rhythm and melody) but just played the first 5 second intro for 8 minutes. Yawn! Too much theoreticising and posing and not enough sound, if you ask me. There's nothing avant-garde about stripping back the same music everyone else makes until only one interesting instrument remains. It sounds like elevator music from the year 2100.... or maybe a CD from one of those hippie meditation stores that sells incense and crystals.

Great! Bloody microsoft!! Here's the funny thing: The original doco just had 'C:\Program files\*'. After some other changes to make it work better for users of international variants of windows, I changed it to %programfiles%, as that is *supposed* to be standard across all variants, so it should work for everybody... I guess not! Thanks for the heads-up, I'll adjust the document accordingly.

Yep, that is good doco, definitely should be on the wiki instead of here :) (Cut from here, paste to the wiki, format it up, and paste the link to the wiki back in here) Probably worth mentioning that the 'commands' are usually referred to as the 'status byte' so that people can relate your plain-english explanation to the other technobabble they find around the net. And a link to The Brainwashing Centre at the end for those who need more: http://home.roadrunner.com/~jgglatt/tech/midispec.htm

Here's a tip: SCROLL UP! 1st post.......

Not at all! On the contrary, we love it when people share the answer. It's the last, but not the least, Golden Rule of Troubleshooting (see my signature), and in a perfect world every troubleshooting thread would end with the answer explained in detail. Forum regulars like TK and I and the crew don't really have time to add this much detail because we're doing lots of stuff... It only takes a few minutes more to make an extra post like you did, but it may save someone in the future several hours of their time. That's a nice gift to share with the world, we all need more time. I thought it was worth spending a minute or two of my time to encourage this ;) Thanks mate!

Sweet :)

Code change looks fine, that should've worked really.... Are you sure that it actually compiled a new hex? Yeh that's it. Just be aware that if you add <filename>.hex, then it will try to compile it from <filename>.asm - so in your case, you must have your setup called SETUP_SEQ_JRP.asm.

LOL!