TK.

But it worked before, correct? I guess that you changed something on the MIOS Studio configuration which causes this effect, somehow it looks like a feedback loop, since messages are received multiple times. It could also be, that a second application is running in background which forwards MIDI events (you are working under MacOS, right?) -> check the MIDI routings. Best Regards, Thorsten.

One possible reason (beside of bad solderings or wrong connections between MBHP_CORE_STM32 and MBHP_DOUTX4 module) is that the 220 Ohm Pull-up resistor array R31 is not mounted. You can test this by measuring the voltage between ground and pin J8:SO, J8:SC, J8:RC when the DOUT module is *not* connected. Note that due to the AC waveforms generated by the SPI transfers you won't measure exact DC values with a common multimeter, but they could give you some hints. E.g., J8:SO should be 0V when your application sends 0 to all DOUT pins, and it should be ca. 5V when you application sends all-1 J8:SC should be between 4V..5V (each mS this pin sends a burst of 1 MHz for ca. 300 uS) J8:RC should be ca. 5V (only short pulses sent each mS) If you always read 0V, the pins are probably floating, accordingly the pull-ups are not connected. Btw: the usage of MIOS32_MIDI_SendDebugMessage() is really recommented for debugging, it's more useful than a LCD. See also http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F003_debug_messages%2F Best Regards, Thorsten.

In the hope that these pictures are saying more than 100 words ;) Best Regards, Thorsten.

for which MIDIbox projects? post the links please. Best Regards, Thorsten.

Shipped today: Hias lumstar Gerbil phunk Following guys will get their GM5 chips via Nils together with the GM5x5x5 PCBs: frailn vcfool kokiPsiho madox cavey magneto Best Regards, Thorsten.

On a Mac it was really simple, just click on the example Xcode project, edit it, build it - done. On a PC Phil noticed a lot of compatibility issues between gcc and MSVC while trying to compile my code, since I'm sometimes using code constructs which are not supported by the Microsoft compiler, such as variable declarations inside the function body, or casting one union to another in a single line. And there are problems with the latest MinGW based gcc version as well (I will give you access to the programmers lounge where you can read more about the details). However, for somebody like me Juce is still very attractive - without reading any documentation I was able to adapt the AU/VST wrapper example code for my needs within a couple of hours. :) No, it's because the latest Xcode version which was shipped with Snow Leopard uses gcc 4.2, but the MacOS 10.4 SDK isn't compatible to this version. I guess that the Plugin could be compiled successfully with an older version - sooner or later I will "sacrifice" an external HD for a Tiger installation. Best Regards, Thorsten.

Selecting sections with a keyboard is officially supported with the latest version, see the ChangeLog: http://www.ucapps.de/midibox_seq_changelog.html There is even a video which demonstrates the usage. The documentation hasn't been updated yet, therefore you probably missed this. I'm planning to write a tutorial about the usage, because a) this powerful feature can be quickly overlooked, and b) the perfect configuration in conjunction with your gear requires some learning. Thats how phrase mode is working, it can also set mutes, send mixer maps, change tempo, etc... It really makes sense to work with MBSEQ V4 first before proposing new features, which probably already exist or have been implemented on a different way. Best Regards, Thorsten.

In the last weeks I re-implemented the MIDIbox SID sound engines in C, so that it is possible to run MBSID on a STM32 core, but also to emulate it accurately on a Mac or PC. The AU/VST gives you the possibility to try some MBSID patches before building the hardware. The sound isn't so fat like on the original, the filter sounds weak and there are a lot of aliasing effects when higher frequencies are played... but probably you will like it anyhow. The AU/VST is based on Juce, Dag Lem's reSID is used for SID emulation, and the part of my MBSID code is to control the SIDs with the possibilities described in the MIDIbox SID Manual. Download (current version 0.2 from 2014-09-28) AU (for MacOS): http://www.ucapps.de/midibox_sid/virtual/MIDIboxSID.component_v0_2.zip (64bit AU which works with Logic Studio 10) VST (for Windows and Linux): http://www.ucapps.de/midibox_sid/virtual/MIDIboxSID_v0_2.dll.zip Known issues: - only the first preset sound bank with 128 sounds is available. No possibility to access the sound parameters yet. - no access to CCs, NRPNs, SysEx yet This will be added very soon, so that it is possible to automate parameter changes, and to edit complete patches with Rutger's editor (Java), or Nils' editor under Windows - the VST doesn't work with Logic 5.5 under Windows - the AU requires MacOS 10.6 or higher - only 64bit supported anymore - only a single instance can be opened! To support multiple instances it will be required to implement the MBSID code in C++, but this will also increase the memory consumption which is bad for the STM32 build. I will evaluate the separation in classes later. Best Regards, Thorsten. P.S.: big thanks to Philetaylor for building the VST under Windows - it wasn't straightforward!

Again: Sold Out! Let's try a 5th bulk order Best Regards, Thorsten.

Finally... :)

This has to be done by somebody with Windows skills. The instructions to compile the VST are given in the "extras/audio\ plugins/How\ to\ use\ this\ framework.txt" document of the juce library. Best Regards, Thorsten.

Too bad :-( However, for those who are interested, here the AU Plugin which allows you to emulate a MBSID w/o hardware: /edit: deleted link - see separate posting here: It has to be copied into your Library/Audio/Plug-Ins/Components directory (if it doesn't already exist, create it!) Thereafter (re)start your DAW - done :) It's built for MacOS 10.6 (Snow Leopard) - a build for older OS versions is available on request. Note that the high CPU consumption, the weak filter sounds and the aliasing effects are caused by the reSID emulation. Only the real hardware will produce the sounds we really love! :) Best Regards, Thorsten.

Are you interested to implement this in Juce instead of Synthmaker? You could take the plugins of the ctrlr project as inspiration. It would have many advantages, e.g. we could not only compile a VST for Windows, but also for Linux. And we could compile an AU component for MacOS. Background: last weekend I took the code of MBSID V3, combined it with the reSID emulator, and put it into an AU plugin: This plugin allows to emulate a MBSID on a Mac accurately (a VST for Windows could probably be compiled as well). All "Vintage Preset" patches can already be played, even Multi/Bassline/Drum patches! Support for sending SysEx messages to a real MBSID could be easily added, since the appr. informations are already available in the MBSID V3 code. See also the source code as a reference. (the simple Juce editor component is located under juce/src/EditorComponent.cpp) As you can see in the snapshot above, the GUI is currently very minimalist. You could help me in creating the GUI while I could continue with the low-level stuff. :) Best Regards, Thorsten.

Basically it would look like this example: http://www.ucapps.de/mios_c_cc_to_nrpn.html But instead of void MyFun_Send_MC303_NRPN() you would write something like: void MyFun_Send_OldSynth_SysEx( unsigned char evnt0, unsigned char sysex_parameter, unsigned char value) { MIOS_MIDI_TxBufferPut(0xf0); // SysEx Header MIOS_MIDI_TxBufferPut(0x11); // to your MIOS_MIDI_TxBufferPut(0x22); // old Synth MIOS_MIDI_TxBufferPut(0x33); // however it looks like MIOS_MIDI_TxBufferPut(0x44); // too bad that you haven't posted a spec MIOS_MIDI_TxBufferPut(sysex_parameter); // parameter number (specified when calling this function) MIOS_MIDI_TxBufferPut(value); // the CC value MIOS_MIDI_TxBufferPut(0xf7); // end of SysEx (or do you need a checksum before?) } [/code] Best Regards, Thorsten.

Hi, this CC parameter is only sent over eight MIDI channels (B0 5B .. B7 5B) If you are using the MIDIbox64 application with default configuration, they would be sent by the first eight pots multiplexed by IC1 of the first MBHP_AINX4 module. Possible errors: - AIN module not properly powered (check Ground/+5V connections to the 4051) - pots not properly powered (check Ground/+5V connections at outer terminals) - the three selection pins of MBHP_AINX4:J6 are not connected to MBHP_CORE:J6 Best Regards, Thorsten.

got it :) Best Regards, Thorsten.

Strange - does it work when you are sending the mail via the messenger? Best Regards, Thorsten.

There are only 20 GM5 chips in stock anymore. If you joined the GM5x5x5 bulk order, but haven't ordered the required GM5 chips yet,please do this now! Sold Out! Best Regards, Thorsten.

Shipped today: schokobaer Gripp ieatmumble Shiro Best Regards, Thorsten.

Only portions of the code have to be re-written, mainly MIOS_* functions have to be mapped to MIOS32_*. I can do this... sooner or later... but currently my focus is on MBSID V3 :) Best Regards, Thorsten.

Thats strange, but interesting! It could explain, why Buhler doesn't get output on Channel #3 and #4 as well. To ensure that this is no SW issue, I doublechecked this with the latest MIOS V1.9g and MBFM v1.1d release - still works (when an instrument is assigned to Channel #3 and/or #4) Combined with the first issue: what happens when you store this setting in the default ensemble, and power cycle the MIDIbox? Change the ADSR settings, especially Attack (should be low) and Sustain (should be high) Also the modulation mode ("Con." setting in INS page) affects the way how operator 3/4 affect the sound - see also the pictures in the User manual. Best Regards, Thorsten.

A new "Happy new year to all MBSEQ V4 users" release is available! :) Gridracer: this issue should be fixed now in Beta15 Additional features: o Track sections which should be played can now be selected via MIDI Keyboard as demonstrated in http://www.youtube.com/watch?v=U_RQL24j8no Each group (G1/2/3/4) has a separate selection zone on the keyboard. Key C..B select section 1..12, the first key of the octave (C) plays the first section as usual, it has the same effect as if this feature is disabled. The width of a section depends on the track length. E.g., if the track length is set to 32, and if it consists of 256 steps, 8 sections are available which can be selected with Key C/C#/D/D#/E/F#/F/F#/G It is recommented to activate the "Follow" function under UTILITY->OPTIONS when using this feature, so that the edit display gets automatically updated whenever the section is changed. o the MIDI configuration page has been overworked to handle the new parameters. Track sections can be selected from a dedicated MIDI Port and Channel. The keyboard zone assigned to the group can be changed, so that it's possible to merge groups (e.g. all 4 groups controlled from a single octave). o an individual section can be selected for each track in the StepView. Press & Hold StepView + SELECT button, then press the GP button of the appr. section. This feature is also nice for editing large tracks! o implemented CC#123 (All Notes Off) - it empties the note stacks if value 0 is received. Values > 0 will be ignored [/code] I guess that you will especially like the "section" feature since it has been requested multiple times in the past. For a quick try, press & hold StepView + SELECT button and select a new step view. To control this from a MIDI keyboard (the method that I prefer during live playing), configure the MIDI settings under MIDI->Section Control, and play some keys on your keyboard. Sections will also be selectable via BLM4x16 and BLM16x16 in future (probably already with Beta16) Best Regards, Thorsten.

Hallo Wolfgang, evtl. optimiert Logic den MIDI Stream, indem es Note-Off Events nach Note-On mit Velocity 0 umwandelt, was nach der MIDI Spec gleichbedeutend ist. Du kannst das mit der "Spy on Outputs" Funktion des Snoize MIDI Monitors ueberpruefen: http://www.snoize.com/MIDIMonitor/ Wenn nun Dein Synthesizer mit dieser Umwandlung nicht zurecht kommt (was aber eigentlich unwahrscheinlich ist), waere das zumindest eine "logic"he Erklaerung. Falls der MIDI Monitor weder Note On mit Velocity 0, noch Note Off events anzeigt, liegt das Problem eher an Logic. Du koenntest die MIDI Daten ja auch mal an einen virtuellen Synthesizer senden, so wie diesem hier: http://notahat.com/simplesynth/ Gruss, Thorsten.

Thats really strange - I suppose an electrical issue or wrong documentation which is hard to solve remotely. To troubleshoot this by yourself, you could control the matrix manually - I will take the terms of my schematic as reference: Connect R0-R7 to the DIN module, connect C0 to ground, let C1..C7 unconnected. Now the buttons of C0 column should trigger a note, all others shouldn't generate a event. Now connect C1..C7 to +5V and repeat - nothing should change (and this should especially not cause a short circuit) Repeat with only C1, C2, ... C7 connected to ground, all other columns even unconnected or to +5V (shouldn't cause a difference) Results? Best Regards, Thorsten.

Great that you got the DIN/DOUT issue fixed! Yes, due to the memory limitations of PIC18F452 only the first four tracks can be edited on MBSEQ V2. And yes, with MBSEQ V3 running on a PIC18F4620 all 16 tracks can be edited in RAM :) Best Regards, Thorsten.