by using the MIOS C skeleton it shouldn’t be that difficult to realize a quantizer, simple sequencer or whatever you want. In difference to assembly programs, sharing code with other users is much easier.
So, how about a MIOS user library, a collection of some interesting functions and “program-modules”, maintained by users and not by myself?
(I used it, because all Unix-style make.exe programs I found cannot handle properly with path variables - it causes even more issues with all windows versions)
DOS batch should be compatible with all DOS/windows versions, but a potential problem is, that the PATH variables to sdcc and the gputils is not configured correctly. In WinXP this is done automatically during the installation.
So far I remember in previous windows versions this has to be done in C:\AUTOEXEC.BAT
Are you able to start “sdcc”, “gpasm” and “gplink” from the command line?
However, today I wrote some low-level AOUT functions for the C wrapper, it works very well and especially very fast (because they are assembly optimized ;-))
I’ve also prepared some small C programming examples which demonstrate the possibilities:
forward/processing incoming MIDI events to AOUTs
forward/processing AIN values to AOUTs
generate waveforms at the AOUTs (AOUT = f(t))
transform incoming waveforms to new waveforms (AOUT = f(x))
set gate outputs depending on AIN levels
hope that this gives enough inspirations - once I find the time to write some documentation, I will release it (maybe tomorrow if nothing else happens)
Best Regards, Thorsten.
P.S.: the programming effort to realize this was 2 hours so far
Are you able to start “sdcc”, “gpasm” and “gplink” from the command line?
Yes - my paths are correct. I found some info online that indicates many batch commands from NT/XP/2000 are incompatible with old DOS based machines. Example - in the clean.bat file
if exist _output del /s /q _output
My DOS version 8.0 doesn’t support the /q switch. Don’t know why, but it doesn’t.
I’ll keep plugging away at modifying make.bat so that it works.
However, today I wrote some low-level AOUT functions for the C wrapper, it works very well and especially very fast (because they are assembly optimized ;-))
I’ve also prepared some small C programming examples which demonstrate the possibilities:
forward/processing incoming MIDI events to AOUTs
forward/processing AIN values to AOUTs
generate waveforms at the AOUTs (AOUT = f(t))
transform incoming waveforms to new waveforms (AOUT = f(x))
set gate outputs depending on AIN levels
hope that this gives enough inspirations - once I find the time to write some documentation, I will release it (maybe tomorrow if nothing else happens)
With this set of examples, you have covered just about everything on my wish-list! Not only that, but I have always been a wannabe programmer - I can modify examples much much faster than I can program from scratch. So, armed with these examples, I’m going to have a great time. Let us know when they’re posted!
I think I found the major problem with the batch file syntax.
Commands like
set SDCC_DEFINES=-DDEBUG_MODE=0
make DOS 8.0 throw up - it doesn’t like the second = sign. I can’t think of a way around this - I may end up having to type everything in by hand at the command line.
