audiocommander

there's the "good-luck-with-it" JDM module from SmashTV: http://www.avishowtech.com/mbhp/mbhp_jdmR2.html and the (newer) MBHP-burner kit and/or PCB is available at Mikes Shop (located in Germany): http://www.mikes-elektronikseite.de/ http://www.mikes-elektronikseite.de/shop_englisch/index.htm Note that you need a +15V power supply for MBHP-Burner, but I found that most +12 universal power supplies have easily +16V if measured... I have both, and got the impression that the Burner is much faster and more relyable than the JDM. best regards, Michael

http://www.ucapps.de/mbhp_lcd.html :-X ;)

haha :) that went straight in my christmas playlist! merry christmas to both of you, too! I hope there's something better under the christmas tree than a 20 EUR MidiBox ;D LOL Michael

there's a changelog.txt included in every archive. regards, Michael

günstig != einfach wenn du ein billiges LCD-Display möchtest, kauf eines ohne Hintergrundbeleuchtung. Die gibt es schon für weniger als 5,- EUR. Allerdings ist das dann halt auch sch**ße zu sehen, v.a. im Dunkeln sieht man da gar nix. Fragt sich, ob man den Euro nicht lieber doch in ein besseres Display gesteckt hätte.

maybe I can add some more informations: the problematic asm keywords are: [tt]BIFSET, BIFCLR, IFSET, IFCLR, IFNEQ, IFLEQ, IFGEQ[/tt] these should be replaced by: [tt]btfsc, btfss, btfsc, btfss, spfeq, cpfsgt, cpfslt[/tt] But I must admit, that I can't read those regular expressions: [tt]s/\<IFSET\s*\([^,]*\)\s*,\s*\([^,]*\),\s*\(.*\)/btfsc \1, \2\n\t\3/g[/tt] an example of a GPASM invalid line is: [tt]IFSET PIR1, TMR1IF, rgoto IRQ_Timer1[/tt] I don't know what the syntax would be if this line is expressed with "[tt]btfsc[/tt]" It won't compile even if I replace IFSET by btfsc manually... And finally, I think the problematic line is the first one of the replace-macros.sed: [tt]1i;hey emacs, this is -*- asm -*-[/tt] I can't see what the "[tt]1i;[/tt]" should do? maybe an ASM-hacker knows what to do? ??? cheers, Michael

take care, Michael

Hello everyone, I just completed and tested v1.3 of the breadboard construction. New plans are already online, pics are coming when I find time for that... it has just one cable on the backside (instead of 5), all parts should fit now and the format is landscape (like DINs/DOUTs) http://www.midibox.org/dokuwiki/doku.php?id=speakjet_breadboard_construction http://www.audiocommander.de/downloads/midibox/mbhp_iic_speakjet_13.board.pdf Maybe the next version supports the TTS256 too... but that's not my main priority right now. I also discovered, that some MAX232's are NOT working! MAX232EPE, MAX232CPE are not working correct (producing only garbage) MAX232EEPE is okay. I have also tried a chip labeled "MAX232N", that's working, too -- but note that the MAX232CPE has also MAX232N printed on top... and I don't get a clue out of this ... :-X ...datasheet ::) I'm also working on updates for the control app, got cascading modules in mind ;D maybe also a tiny DIN control to set the envelope and scale but I think the plain midi control is not the badest idea ;) cheers, Michael

yes, that sounds great. I'm also interested in getting this going. remember I disabled the first line of the script, so I think this may be the reason why it's not working. But you're right, I'm currently very short on time – but I'll give my best to continue on this, even if I may not answer immediately ;) cheers! Michael

okay. the wiki page sais it quite clear, but I'm going to repeat it: there are macros used in the asm sources that are related to microchip's MPASM compiler and will therefore only work if you compile the source with MPASM! If you try to compile it with GPASM it will fail. Of course. That's the syntax error you get when you try to compile. This bash-script tries to identify these MPASM macros and convert them by search-and-replace, so that the sources will become (eventually) GPASM compatible. Before compiling again and again, you should make sure, that the bash-script actually works and really exchanged the problematic macros. The wiki entry has been written for Linux and you're on a Mac. And the Wiki is no professional book, it's written by people like you and me to help others, so this does not mean that everything is gold and the absolute truth. And don't forget: the script is not only for Linux, it's also for MIOS sources! So I don't know if there are any Macros in the SID sources that are not covered by this script. In other words: you should backup the original files for future reference, add the script (of course the adapted one for the mac), run the script and compare the freshly modified files agains the original ones to see if the script works! If the script works, you can try to compile with GPASM. The resulting hex-file should also be compared against the original hex-file (of course without having modified anything else!) to see, if it contains the same code. If the script does not work, we have to see how to make it work. If you're in hurry you should install MPASM for Windows and compile it on your PC. If you'd like to do it on OSX, we can continue this, but I can't guarantee anything... and I surely don't interspect all SID sources for problematic macros... regards, Michael

http://www.midibox.org/forum/index.php?topic=7282.0

yes, but you really need to go through it logically: -> if the error is the same as before: have you checked if the script really works and actually modifies the sources? you have not answered this. -> if the sources get modified by the script: weren't you the one who also tried to compile the seq application? will this work?

all right, no more errors. :D you should check the contents if the problematic mpasm stuff is gone. what happens if you compile it with gpasm? if it's working, is the new compiled hex-file identical to the original one?

could you try it moving all the sources in a subdirectory src/ and use the folder? because when I tested this, I got no error "*.h file not found". at least there are .h, .asm and .inc files, so you should not see this error... regards, michael

hey, don't cheer too soon :) could you try the following; I succeeded in calling, but I don't know if it replaces everything like expected: I put all files in src/ but you may leave that out' date=' so the line should read: "for i in \*.asm"... and so on. The EOF error occurs when ' or " are used, so obviously we just need the backslash for OSX compatibility... then there's been a problem with the sed-file. it seems, that comments are not recognized if they don't start at the line's beginning. And I have no clue what the first line is there for; it definitely produces an error. I simply commented it out, but it may be that I broke the functionality... Let's see if we get one step further :) regards, Michael

the first one is right. You can see your success in the change of the errormessages ;D Now it finds the files, but there's still an error in the shell script => unexpected EOF (= End of File), that means that the syntax or the file encoding is not correct. Maybe it runs fine on Linux... As I'm no bash-crack either, I have to look this up by myself: I will check this tomorrow and come back with an update, if your patience is still there :) Regards, Michael

I tried this and found out that it should work if you write [tt]\'*.asm'[/tt] The error message itself gave this hint: now I'm not sure if the sh script will work that way on OSX. I'll check that later. Maybe it already works this way for you? cheers, Michael ps: no reason to feed stupid, one cannot know this if you're not used to programming :)

Hi Nicolas, you must not remove src/* but only the path src/ *.inc searches for {anyfile}.inc and forget about all errors, no need to get afraid by a long listing, just look at the very first error! it sais "command i expects" something. That means you gave something to it that was not expected, in other words it can't deal with it! Now when you look at the line of the bash script you wrote: "for i in *.asm..." (your faulty version should say "for i in .asm"...) you see that after "i" is "in", we can ignore that cause it's part of the for loop statement. Then comes ".asm" and that's why it's complaining. So by reading the error message right, you are able to look up where the problem is by yourself! (I'm now away from the computer the next hours, so don't wonder if I'm not answering right away :), but I'll be back... Cheers, Michael

okay, now look at the second line in the sh script: [tt]for i in src/*.inc src/*.asm src/*.h;[/tt] that's a loop and says {do something} in all files in the sub-directory src with the file-ending *.inc. Now remember, that this script has been written to change the macros for the MIOS-sourcecode itself. You are using it for something else. The error sais, that it can't find a subfolder src. Can you solve that by yourself? :) another hint: the same applies for files with the ending .h (header files) and the ending .asm cheers, Michael

I'll try to ;) But I won't compile it for you, because I'm very busy and if you ever want to compile another app (like the seq), the same problem occurs. besides this issue, what you're going to learn is valid for hundrets of other cases on osx, so you won't regret having heard about it! you can set the right permissions by typing [tt]chmod -R 777[/tt] then drag the file(s) into the terminal window, so the line says: [tt]chmod -R 777 thePath/to/myFile.ext[/tt] the relevant permission here is that you can execute the script. not sure if sudo helps in this case... if you don't like the terminal, you could also start any ftp-application that supports setting permissions and check "execute" in the file props (instead of typing chmod...). now you should be able to execute the .sh-script. when you get this command, it tells you something is not found. now it would be interesting what is not found. can you look it up and guess why it's not found? try setting the current workpath before calling anything by typing: [tt]cd [/tt] and drag the folder into the terminal window, so you'll see [tt]cd path/to/myFolder/[/tt] cd stands for "change directory" if you still got "command not found" tell us the exact first error message, and we'll see how to continue... cheers, Michael

hi nicolas, in case you don't know, crossposting is not the most welcome thing you can do on a forum ;) it would be helpful if you write what you have done and the errormessage you get. have you fixed gpasm.sh to replace the macros? regards, Michael

Hi, you have seen the Wiki page (fluke already said it) listing all the soundcards with the OPL-chip on it, have you? http://www.midibox.org/dokuwiki/doku.php?id=soundcards_with_ymf262_and_or_yac512_chips You could set up an ebay alert search. This way I got two ISA cards for 4,50 EUR each. Just be patient and let the parts find to you ;) regards, Michael

I doubt a complete mb seq fits in a computer keyboard ;) Anyway, I'd measure everything before ordering... My last case (no seq, no pac tec) is way too small :-\ arrr... best, Michael

Michaël, it seems you hit a great point on every midiboxer's wishlist ;D Just noticed that I wanted to post this link: http://www.geocities.com/tyala.geo/2ansynth.htm so what I meant to share was: if it's possible to add more oscillating (sine-)waves, you can create complex waveforms by simply playing these 4 osc's simultaneously in different pitches. let's say we have a base frequency of 110 Hz, then we'd setup the harmonics: f1 = 110 Hz, f2 = 220 Hz, f3 = 330 Hz, f4 = 440 Hz, f5 = 550 Hz, f6 ... (and so on...) to create a complex square wave, the basic, 3rd, 5th and 7th harmonic with different volumes have to be played: f1 (110 Hz @ 100% Vol) f3 (330 Hz @ 33% Vol) f5 (550 Hz @ 20% Vol) f7 (770 Hz @ 15% Vol) to create a saw waveform, it would look like this: f1 (110 Hz @ 100%) f2 (220 Hz @ 50%) f3 (330 Hz @ 33%) f4 (440 Hz @ 25%) because of the static relations, it's quite easy to implement by lookup-tables. If you're interested you can take a look in my speakJet code: http://www.audiocommander.de/downloads/midibox/kII.tgz Regarding your experienced approach I assume you already know this, but anyway... I hope you don't mind these notes... I'm really excited of the possiblities you opened up, mess! :D Cheers, Michael

Hey Michaël, that's great! :D I read a lot about subtractive synthesis and harmonics while writing the SpeakJet application (combined the five oscillators to a waveshaped harmonic sound). Basically it's about combining different OSCs with doubled frequencies but with dedicated volume-relations within. It looks like you aready know all this stuff... :-\ but if not, these are two quite interesting readings :) : - the synthesis tutorials at the end are pretty good: http://www.samplecraze.com/tutorial.php - and the same in short: how to create complex sounds http://carini.physics.indiana.edu/P105/Synthesis.html Michael