TK.

You can use the common MIOS mechanisms to upload code (or EEPROM) data. It doesn't matter, if data is located in code memory, EEPROM or a BankStick, it's only important that the tables are located at an absolute address (so that pointers compiled into the code never change) Method 1 (quick&dirty): recompile the application, and modify the .hex file, so that it only contains the data section which should be updated. Upload the .hex via MIOS Studio Method 2 (modification of #1): you could use the "mksyx.pl" script to convert the modified .hex file into .syx if you don't want to use MIOS Studio (not recommented, as MIOS Studio provides the much faster (and secure) "smart" mode) Method 3: create a Makefile which only compiles the .asm file to .hex Example: http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fexamples%2Fasm%2Fbs_xfer%2F Disadvantage of these methods: the core will be reset after upload. But this might be acceptable Alternatively you would have to program an own SysEx handler like I did in most of my "main" applications (mostly located in *_sysex.inc) - but it's some work and requires more knowledge about side effects, like collecting data into a buffer before storing into EEPROM, since the CPU won't be able to handle MIDI data during programming Program data into EEPROM from your application: just use MIOS_EEPROM_Write Best Regards, Thorsten.

Great that this issue has been clarified :) Best Regards, Thorsten.

Thank you! Nice to see that you find the new features useful :) Yes, this is already possible with the mixer. 32 CCs per page are free assignable, + Volume/Panorama/Program Change for each channel strip, and there are 128 mixer pages stored in a separate BankStick. I think that I know how to program a 8x8 matrix and integrate it perfectly into MBSEQ ;) (basically I will re-use the same routines and concepts like for MBSID V2) In difference to your version, it will be possible to use a 8x8 button matrix + the 16x4 BLM in parallel. I will do the implementation once I got a prototype board from Wilba - just in time :) Best Regards, Thorsten.

...is now available for download: http://www.ucapps.de/mios_download.html Most of the requested features of the last months (but also my private wishes) have been implemented (hope that the guys are still reading this forum ;)) -> http://www.ucapps.de/midibox_seq_changelog.html The remaining feature requests can be found at the bottom of CHANGELOG.txt Best Regards, Thorsten.

MB808 v1.0 has been released "by accident" last sunday (during the re-release of all MIOS applications). However, it works very stable since weeks, all planned features are implemented - have fun! :) Best Regards, Thorsten.

The clock signal change won't solve it (this is required to avoid doubletriggered gates) Yes, please measure the voltage between ground and pin #28? A 7812 doesn't guarantee that the SID will be supplied with 12V if the input voltage of the SID module (J1) is too low Best Regards, Thorsten.

Note that Rudger did all the work, not me! :) You will be asked by the editor if no MIDI interface is connected Maybe no interface is found at all? And which OS and Java version are you using? Best Regards, Thorsten.

Ok, there are three other possibilities for this effect: - either the filter caps are not connected correctly (bad soldering joints) - or you are using the wrong filter caps for your SID (6581: 470 pF, 8580: 4.7nF .. 22nF should lead to a good filter characteristic, 22 nF are recommented), - or the SID is powered with the wrong voltage (6581: 12V, 8580: 9V) You can measure the voltage between Ground and Pin #28 of the SID Best Regards, Thorsten.

The filter type has to selected as well, otherwise you won't hear the sound (CC#45 selects LP filter) Best Regards, Thorsten.

Some more words to the procedure: once I got the PCBs/GM5 chips from Ploytec this week, I will build one or two boards to doublecheck, that the PCB is fine now, and that the chips are programmed correctly and working under Windows/Linux/Mac. This is to avoid any trouble at your side (e.g. in worst case you would have to send back the PCBs or GM5 chips to Munich if there are unsolvable errors/failures) Thereafter I will send out the invoices/money requests, GM5/PCBs will be shipped whenever I receive the money of individual people (please allow a delay of 1..2 days) I will wait for up to two weeks, if there are still unpaid orders, all people in the list will get the chance to buy the remaining parts (first come, first serve). They will be asked via PM Best Regards, Thorsten.

No news yet, but I'm still in contact with Ploytec (due to other reasons) - don't worry, we will get our stuff Update: Response from Ploytec which I got on a sunday afternoon 5 minutes after I asked via email: they will get the programmed chips tomorrow. Order quantities: as mentioned in a change log comment, we should re-calculate the totals once the people of the first batch have been removed from the table. My own spreadsheet is already more up-to-date than the Wiki due to all the unplanned special wishes of various people :/ Best Regards, Thorsten.

Rutger implemented a Java based patch editor and bank librarian for MIDIbox SID V2, which allows you to manage/modify/create new patches under Windows/Mac/Linux remotely without the control surface Even users who built a complete MIDIbox SID might find it very useful, as this software gives a good insight into hundreds of parameters for all 4 sound engines! :) Note that the editor is still under development. Your feedback is very appreciated! Download Best Regards, Thorsten.

Maybe the oscillators are not routed through the filter? CC#44 should be set to 7, CC#45 to 1 Best Regards, Thorsten.

This is an intended default configuration. You will notice, that most of my bassline patches are using the right-channel bassline with saw waveform in upper range. Best Regards, Thorsten.

You have to install gputils and SDCC on your Mac: http://sourceforge.net/project/showfiles.php?group_id=41924 http://sourceforge.net/project/showfiles.php?group_id=599 There are also some forum articles about this topic (installation on Mac) - just use the search function to get informations about what can be made wrong ;) You don't need to do any modifications on the base package (or on any other release package) to get the compiler running. If you already changed anything, remove it (copy over the original release) to avoid side effects (e.g., you don't need to customize GPASM_INCLUDE or SDCC_INCLUDE, since the pathes to default include files are already set correctly when gpasm/sdcc is executed) Best Regards, Thorsten.

There was an issue with the "local path" trick in the Makefile of release packages. Some users noticed following message: ERROR: ./bin/mios-sdcc: MIOS_BIN_PATH variable not set Fortunately Stryd_One found a proper solution - all packages have been re-released again (version number not changed), mios_base package is now available as v1_0a (only bin/mk-dist.pl has been changed) Best Regards, Thorsten.

The new MIOS programming platform is finally available for public after almost 6 months of continuous work. Big thanks to everybody who contributed! :) Basically it unifies the way how assembly and C based MIOS applications are built under different operating systems (Windows, Linux, MacOS) for different PIC processors (PIC18F452/PIC18F4620/PIC18F4685), and it allows to share code modules between different projects without copying source files to improve the collaboration of people who are interested to contribute. The file structures and build procedures have been defined for the special needs of this community. Most important intention was to ensure, that end-users without programming skills are still able to customize and recompile an application safely without running into issues like file inconsistencies, missing packages or wrong tool configuration. In order to achieve this, the file structure exists in different "views" for users and programmers (more about this topic below). Application Release Packages All applications have been re-released and they are now available in the MIOS download section. They contain the prebuilt .hex file + source code as before, but the file structure inside the package has been changed. There are subdirectories for include files (include/), low-level drivers (modules/), libraries (lib/), scripts (bin/), documentation (doc/), and mostly also a separate source directory for the main program (src/). Each package contains a README.txt file, where an introduction and sometimes also links to websites with more informations can be found. A "Makefile" and "Makefile.orig" is part of the package as well. "Makefile.orig" contains the original instructions to build the application, and the "Makefile" includes this file after setting MIOS_PATH and MIOS_BIN_PATH to the local release directory. This approach ensures, that users will always re-compile an application with the same resources used (and tested) by the programmer during a release. To rebuild an application different open source tools are required. Details are eplained in the Wiki (installation docs mainly written by StrydOne and Audiocommander - thank you!) http://www.midibox.org/dokuwiki/application_development Windows users: see especially this page http://www.midibox.org/dokuwiki/windows_toolchain_quickstart After installation of the toolchain, all you need to do for recompiling an application is to - open a command shell - change to the release directory "cd <dir>" - type "make" It's identical for all operating systems. MIOS Base Package Those who don't intend to program applications can stop reading here! While application releases only contain the used files/directories (a small part) of the programming platform, the base package contains all available include files, libraries, modules which were available at a given released date. It also includes programming examples and templates in the apps/ directory. In order to create a new application, just copy a template into a new directory and start with programming (e.g., try the MIOS C programming examples). To build a .hex file, the MIOS_PATH and MIOS_BIN_PATH environment variables have to point to the base package directory (MIOS_BIN_PATH points to the bin directory inside the base package). These variables can be set in the command shell; Linux/MacOS users can insert them into a ~/.bash_login (or similar) file, Windows users can add them to the system properties (one of those well hidden GUIs) so that the variables are already set correctly when a new command shell is opened. Example for DOS: set MIOS_PATH=C:\mios_base set MIOS_BIN_PATH=C:\mios_base\bin Example for Linux/MacOS: export MIOS_PATH=~/mios_base export MIOS_BIN_PATH=~/mios_base/bin To share an application with other users, copy it into a new directory, type "make dist" and follow the instructions. And/or bring it into the repository! (see below) MIOS Repository Alternatively to using the MIOS base package, it's also possible to download the current sources of MIOS base + all applications from the midibox server via SVN. This method could also be interesting for users who want to try out new features of applications, before they have been released. Once the complete repository is on your harddisk, you are able to keep it up-to-date by using the SVN sync mechanism ("svn update") - monthly/weekly/daily/hourly/whenever you want. Only the differences will be downloaded. The SVN URL (for read access only) is: svn://svnmios.midibox.org/mios Linux/MacOS user: "svn" is (mostly) already installed on your computer. Just type "svn co svn://svnmios.midibox.org/mios" Windows users: see http://www.midibox.org/dokuwiki/windows_toolchain_svn There is also a SVN web frontend installed which allows you to follow the progress without installing SVN: http://svnmios.midibox.org Write access to MIOS Repository Every programmer who want to contribute is invited to get write access to the repository. Just contact me! With SVN write access, you are able to: - publish new code modules (low-level drivers) and applications for other programmers - collaborate with other programmers on a single application (subversion supports file merging) - provide bugfixes for existing code (after agreement with the original programmers/copyright holder(s) of course) - fix typos and provide translations for ucapps.de (ucapps.de is part of the repository as well) - provide circuit diagrams under schematics/ (e.g. in xcircuit format) Have fun! :) Best Regards, Thorsten.

Only difference is the default calibration value for the filters (which you can change in the ensemble later. For each channel seperately if required) So - yes, a single core can ontrol 8580 and 6581, and there are different possibilities For example: L: 8580, R: 8580 (especially useful for filtered stereo leads and basslines) L: 6581, R: 6581 (for vintage fans and old .sid file playback) L: 8580, R: 6581 (download the setup_8580.hex, and change the calibration MAX value of right channel from 600 to FFF) L: 8580 and 6581, R: 8580 and 6581: left/right channel SIDs will get the same values, but mixed waveforms and filters will sound different between 6581/8580 You could add a audio switch (or audio channel mutes) to mute 6581/8580 You could use different ensembles to switch between the filter calibration values (up to 128 ensembles are available) Other obvious combinations are not listed. (e.g. using multiple cores, or using 8580/6581 only on the left channel) 8580 can be replaced by a 6582 - there is no real difference. The preset bank is adjusted for 8580/6582 with 22 nF styroflex caps Best Regards, Thorsten.

And again a new version (RC25) with fixed SusKey behaviour Razmo is currently doing a lot of checks beside of bringing up his Soundforge based editor. Here a demo of some really punchy patches (created & manually played by Razmo) http://www.midibox.org/users/razmo/mbsidv2_PatchTest.mp3 Best Regards, Thorsten.

RC24: [tt] o voice allocation of multi engine working again o Lead engine: MdW (ModWheel) and Key modulation source now provide a value in positive range only o overworked oscillator pitch handling: now completely linear frequency calculations. Advantages: - modulation frequency (e.g. LFO vibrato) independent from oscillator frequency - accurate filter key tracking - the O2A option (forward pitch to AOUT) doesn't result into out-of-scale SID frequencies anymore o the presets under presets/v2_vintage_bank.syx have been overworked according to the new osc frequency handling [/tt] Following sound samples demonstrate the difference between the old and new oscillator pitch modulation handling: Old handling: with higher frequencies, the LFO modulation of the pitch got less "intensive" http://www.ucapps.de/mp3/midibox_sid/mbsidv2_lfo_nonlin_osc_frq_mod.mp3 New handling: same "intensity" of the pitch modulation independent from the OSC frequency: http://www.ucapps.de/mp3/midibox_sid/mbsidv2_lfo_lin_osc_frq_mod.mp3 Please update your preset bank! Best Regards, Thorsten.

Meanwhile the approach to compile applications has been completely overworked, so that it works flawlessly under all operating systems. Maybe I should reserve this weekend for a complete re-release of all applications - it will simplify a lot of thinks (and some Wiki pages always refer to the new methods) Best Regards, Thorsten.

Got my board here in Germany! Thank you! :) Best Regards, Thorsten.

SysEx Librarian is a Cocoa based application, so this issue isn't java specific. Are the MIDI ports listed by this MIDI Monitor? Best Regards, Thorsten.

Great work! Blogged :) Btw.: for the 4x20 LCD you could activate a special configuration in your setup_8580.asm file, so that all 4 lines are used: ;; number of LCD lines (supported: 2 for 2x* LCDs and 4 for 4x* LCDs) #define DEFAULT_LCD_LINES 4 ;; LCD line -> cursor offsets #define DEFAULT_LCD_LINE_Y0 0x40 #define DEFAULT_LCD_LINE_Y1 0x14 #define DEFAULT_LCD_LINE_Y2 0x00 #define DEFAULT_LCD_LINE_Y3 0x54 ;; 1: LCD cursor will be set to current parameter position (clashes with bar graph which is enabled with DEF AULT_LCD_LINES >= 4) ;; 0: disable this feature #define DEFAULT_LCD_PRINT_CURSOR 0 [/code] (requires the latest RC23 release) Best Regards, Thorsten.

I haven't received the parts yet and I haven't received an invoice yet, accordingly shipping isn't possible yet ;) Ploytec informed me, that they will get the PCBs end of July. The GM5 chips are currently programmed/flashed by a special company. So, everything on track! :) Best Regards, Thorsten.