TK.

It's related to an assembler bug in an older gpasm version. Which version number is displayed with "gpasm --version"? I'm using: mbp:midibox_sid_v2_039 TK$ gpasm --version gpasm-0.13.7 beta mbp:midibox_sid_v2_039 TK$ make rm -rf *.cod *.lst *.err rm -rf *.hex gpasm -p p18f4685 -I./src -I ./include/asm -I ./include/share -I ./modules/j5_io -I ./modules/aout setup_6581.asm gpasm -p p18f4685 -I./src -I ./include/asm -I ./include/share -I ./modules/j5_io -I ./modules/aout setup_8580.asm gpasm -p p18f4685 -I./src -I ./include/asm -I ./include/share -I ./modules/j5_io -I ./modules/aout setup_sammich_sid.asm gpasm -p p18f4685 -I./src -I ./include/asm -I ./include/share -I ./modules/j5_io -I ./modules/aout setup_tk.asm gpasm -p p18f4685 -I./src -I ./include/asm -I ./include/share -I ./modules/j5_io -I ./modules/aout setup_tk2.asm gpasm -p p18f4685 -I./src -I ./include/asm -I ./include/share -I ./modules/j5_io -I ./modules/aout setup_mb6582.asm gpasm -p p18f4685 -I./src -I ./include/asm -I ./include/share -I ./modules/j5_io -I ./modules/aout sid_filter_table.asm [/code] Best Regards, Thorsten.

Das LPCXPRESSO Modul kannst Du Dir direkt in Deutschland bei Watterott bestellen: http://www.watterott.com/de/LPC1769-LPCXpresso SmashTV wird die AINSER64 Platine demnaechst in den Shop aufnehmen, momentan ist sie noch in Produktion. Die Bauteile kaufst Du Dir am besten direkt bei Reichelt (sie entspr. "orderlists"), das ist insg. guenstiger als der Versand aus den USA. Gruss, Thorsten.

No, this is no april fool: MIDIbox SID V2 has left beta state after 5 years!!! ;-) (I removed the RC (release candidate) prefix) With V0.039 the LFO MIDI Clock synchronization has been improved, and the SysEx handling has been optimized for bidirectional communication with the upcoming Ctrlr based Editor. From the ChangeLog: V2.039: o LFO MIDI Clock Sync has been overworked, it now supports 32 different rates from 16 bars to 1/32 notes including triple and dotted delays! If the CSn flag enabled the available rates are: 0=LFO disabled, 8=16 bars, 16=14 bars, 24=12 bars, 32=10 bars, 40=9 bars, 48=8 bars, 56=7 bars, 64=6 bars, 72=5 bars, 80=4 bars, 88=3.5 bars, 96=3 bars, 104=2.5 bars, 112=2 bars, 120=1.5 bars, 128=1 bar, 136=1/2., 144=1/1T, 152=1/2, 160=1/4., 168=1/2T, 176=1/4, 184=1/8., 192=1/4T, 200=1/8, 208=1/16., 216=1/8T, 224=1/16, 232=1/32., 240=1/16T, 248=1/32 Note that in MIDI Sync mode, the LFO Delay won't work because the appr. resource is used as MIDI clock counter. o current bank and patch number won't be changed anymore on direct RAM access via SysEx [/code] And here a preview of the new editor: Currently all Lead Engine + Ensemble parameters (more than 1000!!!) can be accessed. The remaining engines will be implemented tomorrow, thereafter the panel should be ready for release. :) Best Regards, Thorsten.

DIN/DOUT werden vom LPC17 Core unterstuetzt, fuer die Potis benoetigst Du jedoch ein AINSER64 Modul: http://www.ucapps.de/mbhp_ainser64.html Um Missverstaendnisse auszuschliessen: AIN funktioniert nur mit den PIC Firmwares, AINSER64 nur mit den neueren 32bit basierten Cores. Die MIOS32 basierte MIDIO128 Firmware kann bis zu 128 Potis scannen: http://www.ucapps.de/midio128.html Gruss, Thorsten.

Hallo Artem, schoen dass Du das Problem selbst loesen konntest! :) Weitere Soundpatches gibt es hier: und hier: Und sobald der neue Editor fertig ist, werden hoffentlich noch mehr hinzukommen! Gruss, Thorsten.

At the time the MBFM has been designed, external switches haven't been considered. Today it would be some effort to integrate this into the firmware properly. I'm not only speaking about the programming and testing (which would take 1..2 hours), but also about documentation, CS & SysEx editor enhancement, etc... To give you an example: yesterday I improved the LFO MIDI Clock synchronization of MBSID - I had to disable another feature to make this possible. Then I thought that I could add the same function to the MBFM because I really like the new behaviour, found out that the LFO implementation is very different, tried to adapt it, but gave up after 1/2 hour because I saw that there are much more changes required than expected. Therefore I postponed this feature (on which I'm interested by myself) to a day where I've nothing else to do ;) In short: no, it isn't possible with the current firmware. Would it be acceptable for you to add a physical switch for the filter bypass? Best Regards, Thorsten.

Yes, you can select the number of USB ports in mios32_config.h: #define MIOS32_USB_MIDI_NUM_PORTS 8 [/code] Best Regards, Thorsten.

ok for me. Best Regards, Thorsten.

Please wait for the Ctrlr based solution :) (see also ) Best Regards, Thorsten.

I will look into this at the weekend. It really seems that I need a second (LPC17 based) MBSEQ V4! :-/ Best Regards, Thorsten.

ok, changed this. I'm normally using the mouse wheel which is much more ergonomic, therefore it doesn't make a difference for my own workflow. ;) This is fixed in Ctrlr version r965, but unfortunately this one has another issue with Lua scripting. As Roman wrote in the Ctrlr forum, he will fix this soon. Changed It was on my agenda since many months... I was just unsure if I should program it in Juce directly, or take the Ctrlr project instead. I think that Ctrlr is the right route here, because it allows interested people to improve or customize a panel without programming knowledge. Now where I know how fast a panel can be created, the next step will be a fully featured editor for MBSID V2 including all tricks, such as multi-oscillator modifications, automatic switching of the panel layer depending on SID engine, etc. :) I will also create an editor for MBCV V2 - the firmware is running pretty stable, has great features (most recent one: a patch change mechanism which can be synchronized to the MIDI clock with selectable resolution!) but currently only a Lemur editor is available, which makes the project useless for most people. Back to topic: here a link to V1.0 of the panel: http://www.ctrlr.org/page.php?p=ddb I will ask Roman to add this to the Ctrl device database, so that it can be directly downloaded from the Ctrlr app done Best Regards, Thorsten.

Update: Drums can now be edited as well: The URL to the release package is identical: -> http://www.ucapps.de/midibox_fm/midibox_fm_ctrlr_panel.zip Best Regards, Thorsten.

The new Ctrlr based solution works under MacOS, and it can be used standalone, but also as AU and VST plugin! -> Best Regards, Thorsten.

A beta release is now available for download: http://www.ctrlr.org/page.php?p=ddb Currently I only tested it under MacOS All parameters except for Drums and Wavetables can be edited. Best Regards, Thorsten.

Maybe it's too obvious: the release package can be compiled without setting environment variables. Just install gputils, thereafter type "make" in the main folder - thats all! Best Regards, Thorsten.

The default MacOS implementation can't handle SysEx streams, and mmj (-> http://www.humatic.de/htools/mmj.htm) doesn't support Lion (yet) Best Regards, Thorsten.

Creating a MBSID panel will be a bit more effort, but it's doable! :) At the top of this thread you will see the current state: all instrument parameters are editable! :) Next step is to learn how to create a separate view for drums and wavetables. Best Regards, Thorsten.

Since I'm affected by the Java issue under MacOS 10.7 as well, I started a new implementation based on Ctrlr: Best Regards, Thorsten.

Since the JSynthLib based MBFM Editor, which I created many years ago, even doesn't run on my own computer anymore, I started a new one which is based on Ctrlr The early beta version after I learned how Ctrlr handles the dataflows: /Update: The panel can be downloaded from this location: http://ctrlr.org/midibox-fm-v1/ Ctrlr can be downloaded from http://ctrlr.org/nightly/ I tested this with Ctrlr_262f2710.dmg (version from 14. April 2014) under MacOS For Windows take Ctrlr_ac6a3185.exe /Update2: Drum edit panel: A complete implementation with access to all parameters is feasible, especially since Ctrlr supports LUA as a scripting language. Example: following code handles the OPx flags, which are located in a single parameter at different bit positions: OP1Flags = function(modulator, newValue) op = "OP1" flagSustain = panel:getModulatorByName(op .. "SustainFlag") flagVibrato = panel:getModulatorByName(op .. "VibratoFlag") flagTremolo = panel:getModulatorByName(op .. "TremoloFlag") if flagSustain ~= nil and flagTremolo ~= nil and flagVibrato ~= nil then value = 0 value = value + 2 * flagSustain:getModulatorValue() value = value + 4 * flagVibrato:getModulatorValue() value = value + 8 * flagTremolo:getModulatorValue() sat = panel:getModulatorByName(op .. "FlagsSatellite") if sat ~= nil then notify_vst_host = false notify_midi_device = true notify_component = true sat:setModulatorValue(value, notify_vst_host, notify_midi_device, notify_component) end end end At the end scripting the combined parameters is much less effort than writing the whole application by myself! Especially since we will inherit all these nice Ctrlr features such as Windows/Mac/Linux compatibility, support for VST, AU and Standalone mode, etc. The GUI design is very simple, because I'm not good at graphics. Is anybody interested on helping with the graphics? See following page for inspirations: http://www.ctrlr.org/page.php?p=ddb Best Regards, Thorsten.

I'm still searching for somebody who would create the GUI for editing parameters. The source code (based on Juce) is located under: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v3%2Fjuce%2F Best Regards, Thorsten.

MIOS provides software based debouncing which can be enabled with the MIOS_SRIO_DebounceSet function: http://www.ucapps.de/mios8_fun.html#MIOS_SRIO_DebounceSet In order to add this to the MBSID application, open src/main.inc, search for USER_Init, and write: USER_Init movlw 10 ; debounce for 10 mS call MIOS_SRIO_DebounceSet [/code] Best Regards, Thorsten.

ok for me. Best Regards, Thorsten.

It should work without additional measures when the In->Out function is enabled. Are you able to check the MIDI input (coming from your synth) and output (coming from MBSEQV4L when synth is connected to IN1) with a MIDI monitor running on your computer? Maybe the synth isn't configured correctly. Alternatively: loopback MIDI IN and OUT on your synth - does it work? And does it *not* work if the loopback is disconnected (ensure that "Local Off" function is active on your synth) Best Regards, Thorsten.

Hi Chris, I own a RM1x as well, in fact I'm using it as a reference sequencer when checking the interaction between MBSEQ and "another device" in master and slave mode (it's always good to have reference devices from different companies). Recording MBSEQ patterns via MIDI works fine, regardless if RM1x is in master or slave mode - I just tested this again. Timings are stable, no delays, the recorded pattern can be looped properly. t's especially important that you are pressing the Rew button on RM1x before recording to ensure that it starts from the first step, because it doesn't automatically synchronize to the MIDI start event (very annoying) I'm too lazy to check this with an expired firmware release. Best Regards, Thorsten.

Just noticed that J15S is still not not documented at my website, I should add hints in the schematic and with a picture at the MBSEQV4L page to highlight this. This jumper is required to supply the transistors on the MBSEQV4L frontpanel PCB - the LPCXPRESSO module shouldn't be fried if this jumper is missing. Just to doublecheck: did you bridge the cutted 3.3V line to power the LPC1769 standalone? A possible reason why the LPCXPRESSO doesn't boot when J15S connected: maybe a wrong J15 connection? Does it boot when J15 is disconnected from the frontpanel PCB? Best Regards, Thorsten.