TK.

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.

Christian: I haven't forgotten this issue, and will work on a solution soon (to get Ky1..4 for transposed notes working again). However, for the parameter assignments there is no hope, especially because the WT sequencer is organized differently compared to the lead engine. While the lead engine provides 4 independent tracks for a single stereo sound, the multi engine only provides a single track for 6 different sounds. Accordingly, controlling parameters of one instrument from another instrument can only work under special circumstances (e.g. same MIDI channel, keyboard zone, legato/mono/poly/WT only setting, etc...) I don't understand, why you see absolute values instead of the Note. I mean: if a Note parameter is assigned to the track, you should see the Note, e.g. C-1, C#1, D-1, D#1, etc. (and Ky1..4 for value 7C..7F) Or could it be, that you are trying to send the notes from a track which doesn't belong to the instrument? As mentioned above: this could be possible, but only under special circumstances. However, RC23 is available now. It's only a service release with precompiled .hex files for the finetune fix, no new (official) features (ok, there is a new upcoming feature, which is disabled by default since it has to be tested by the guy who suggested it - Razmo :) - linear oscillator pitch modulation) Best Regards, Thorsten.

You could use the Control Slider element in MidiPipe Best Regards, Thorsten.

Hi Lars, probably the oscillator won't start with higher cap values, it's better to use lower values like 22 or 15 pF Best Regards, Thorsten.

I'm sorry, the read-only svn access isn't supported anymore, since it slowed down the server too much. svn access is available again - a special demon has to be started to get it running - this has to be done after each reboot I could give you ssh access to the repository if required. If this is too complicated, just download the latest stribe firmware release package, it contains the driver module as well Best Regards, Thorsten.

Yes, this is the first demo where I experimented with sidechain compression on the pad sounds, and in demo5 I used it for the bass sound. Best Regards, Thorsten.

Yes, first I want to see the invoice from Ploytec which lists all costs (shipping, etc...) before will request the money from you. Best Regards, Thorsten.

http://www.midibox.org/forum/index.php/topic,10476.0.html Best Regards, Thorsten.

You need some more inspirations for the case of your upcoming MIDIbox SID? How about this construction, made by an electronic newbie with a lot of help from Julien Voirin! :) Very well done! :) poumtag wrote:

Thank you! :) Too bad, that the audio quality of the YouTube video is so terrible - on the other hand, it adds some extra filth ;) 4x20 screen: yes, thats a new feature especially made for MB-6582: The upper line shows the menu page name + selections (here Left/Right oscillator #1) The lower line shows a bar graph of the selected parameter Best Regards, Thorsten.

Bassline demo played on a MIDIbox SID V2 in a MB-6582 case made by Wilba. 0:03 first bassline starts to play 0:10 selecting different sequences, drums played from a sampler 0:17 "pumping" effect realized by sending the bassdrum to the sidechain of a compressor 0:25 checking the new O23 feature: bassline played unisono 0:33 changing the oscillator phase offset 0:47 detune 1:05 disabling the O23 functions 1:15 second bassline starts to play 1:22 showing the V-meter function in bassline mode 1:47 activating oscillator synch, second oscillator played with constant pitch 2:23 activating ring modulator, played with different pitches 2:55 tweaking cutoff/VCA release/O23 pitch (distortions are SID internal) 5:38 second bassline with detuned oscillators MP3 with better audio quality Best Regards, Thorsten.

the syntax of the subject wasn't correct, therefore I haven't found the email immediately Best Regards, Thorsten.

The problem: there are only 256 parameter slots free, and all are allocated, see also: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fdoc%2Fmbsidv2_parameter_chart.txt So - which parameters could be removed to provide this function? For chords you have to use "Ky1", "Ky2", "Ky3", "Ky4" (last parameters) - I just noticed, that they don't work in the multi engine. I've to check, if a solution is possible (could be difficult, as note stacks are not handled the same way like in the lead engine) On the other hand: if you only want to transpose a played Note, just assign the track to the transpose parameter (#41). Best Regards, Thorsten.

I must say that I don't understand your question. The WT editor is the same, only difference: 6 tracks instead of 4. So, why is this a shame? Which assignment are you using exactly? Transpose and Key (Note) assignments are working fine at my side It's really difficult to reproduce an issue if you don't tell me your exact configuration. Best Regards, Thorsten.

I'm still waiting for a 100% sufficient wording which makes cimo happy. ;) Btw.: the USB powering topic isn't new to me, see also http://soundwidgets.com/smf/index.php?topic=158.msg575#msg575 and http://soundwidgets.com/smf/index.php?topic=66.0. It's also clear to me, that many desktop PCs/notebooks don't really deliver 500 mA (the reason why many USB devices provide a separate power plug). Personally, I would never power my MIDIboxes via USB anyway to save my computers, but people are asking for this frequently... ...so, before wasting time in discussing about this "grey area": does anybody know some links to reliable reports/articles? Best Regards, Thorsten.

500 chips have already been ordered, which means that people below the 500 mark have to wait for the second order. But even for those people there is some small hope to get the chips earlier: 11 orders haven't been confirmed yet, deadline is 20th July. Unconfirmed orders will be removed from the list. Currently this would free 49 GM5 chips and 46 PCBs for people below the mark! Best Regards, Thorsten (uses NeoOffice Calc instead of Excel to avoid calculation errors ;))