TK.

Hi Chriss, I'm glad that it works at your side again! :) Best Regards, Thorsten.

You won't find details yet, as the project is still in the definition phase. I'm targeting end of this year for a first public release - hardware can change until then. Meanwhile I'm sure that it will be possible to upgrade an existing MBSID V2 (also MB-6582 and sammichSID) by connecting the new core32 module (*not* MBHP_CORE_STM32) via a simple two-wire CAN cable. PIC18F4685 will still be required to adapt the SIDs to the Core32 module, otherwise SID accesses would slow down the CPU too much. Also the existing CS can be re-used. So, must users only have to build a new core module and connect it to their existing MBSID V2 - thats all! They could build it into a breakout box. As a bonus they will get two MIDI IOs, USB, Ethernet (for OSC) and more. So, the core32 module will also be a nice MIDI interface replacement, and you could control your MBSID with an iPad/iPhone (or similar) as well if the ethernet interface is connected to a WiFi router. But MBSID V3 will also provide a shiny new (still DIY friendly) CS for improved usage - just two words: Hires-OLED and mulicolour! :) Best Regards, Thorsten.

Thanks for feedback, this bug was obvious! Fixed in Beta38 - as a bonus, the performance has been improved. :) MIDIboxSEQ V4.0beta38 ~~~~~~~~~~~~~~~~~~~~~ o CPU load reduced by more than 20%, this especially results into faster SD Card operations! o fixed move step function for moves which select the next step view [/code] Best Regards, Thorsten.

Hi Chriss, you are absolutely right, this was a bug! Fixed in V1.4a :) Best Regards, Thorsten.

You have to sync register accesses to the 1 MHz SID clock. It's especially important to prevent any setup or hold violation on the bus - depending on the microcontroller that you are using this can be very tricky! Due to this frequency limitation it's also better to control multiple SID chips from multiple microcontrollers. Some time ago I wrote a report about this issue: Best Regards, Thorsten.

Very nice ideas, I like the command decoding! :) And I've nothing more to add - they would already very useful! I gave you access to the programmers section where you will find informations about the latest developments (especially about MIOS32 and the new core module) I guess that you would add the MBHP_IIC_MIDI extensions by yourself? Best Regards, Thorsten.

Alright, it looks like this interface (MIDI cable at one side, USB cable at other side, case has similar shape and three LEDs) It's on the blacklist. If it isn't already too late: send it back and complain about the bugs - meanwhile I read from many users (not only in this forum) that SysEx transfers are not handled reliable by this cheapo interface. Best Regards, Thorsten.

Do you have a picture of this MIDI interface? Best Regards, Thorsten.

With MIOS32 we don't program in assembly language anymore; C programs written for MIOS8 are not 1:1 compatible, but have a similar look and feel. See also: http://www.ucapps.de/mios32_c.html The README files describe the new concepts in detail. MIOS32 already uses DMA for SRIO transfers, this article will give you some additional background informations for your "mission": Since your application is even more timing critical than we one described in, you could also disable the normal SRIO handling, and call MIOS32_SPI_TransferBlock directly. See also http://www.midibox.org/mios32/manual/group___m_i_o_s32___s_p_i.html Best Regards, Thorsten.

I read your observations, but there isn't enough input for a successful remote diagnosis. Could you please go through the troubleshooting guide and tell us, which tests are passing, which ones are failing? -> http://www.ucapps.de/howto_debug_midi.html Check also that your MIDI interface is not on the blacklist: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist Best Regards, Thorsten.

10 uS scan cycle for 64bit means that the required scan frequency is ca. 6.5 MHz. This can't be done with the PIC (if other tasks should run in parallel), but it's possible w/o much programming effort with MIOS32, because the DMA could fetch the shift registers in background while the CPU processes the results of the previous scan in parallel. Best Regards, Thorsten.

The upload shouldn't take longer than 10 seconds; it seems that you are using a MIDI interface which can't handle SysEx messages which are much longer than 100 bytes. 1) check if your MIDI interface is on the blacklist 2) check if there is a driver update for your MIDI interface 3) let us know which interface you are using, and under which operating system it is running. 4) Copy&Paste the output of the MIDI IN window (ca. 1 page is enough) because it may contain helpful diagnosis messages Best Regards, Thorsten.

Any other hardware, such as a PC or Mac? Any software you are already using and which supports OSC? Without more informations from your side it's really hard to propose a suitable setup. If you would own a MBSEQ V4, TouchOSC could send OSC packets to MBSEQ via a WiFi router. MBSEQ can convert OSC to MIDI messages, and then forward to sammichSID. Best Regards, Thorsten.

Of course you have my permission - but you should really keep it! :) Best Regards, Thorsten.

See http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fsrc%2Fsid_frq_table.inc The formula for calculating these numbers is well described in the SID datasheet Best Regards, Thorsten.

Wait for MBSID V3 no it won't be based on MBHP_CORE_STM32, but on a new board with a more suitable microcontroller. yes, it will provide an integrated ethernet controller yes, ethernet, USB, CAN and MIDI can be used in parallel. yes it will provide OSC Therefore it doesn't make much sense to document the halffinished stuff based on obsolete hardware - especially not to people w/o programming knowledge. However, there are many PC/Mac based possibilities to transfer OSC to MIDI - unfortunately you haven't specified, which HW/SW you already own. Even with MBHP_CORE_STM32 and MBHP_ETH it's possible, but as mentioned above: if you don't own this HW yet, it doesn't make much sense anymore to invest into it. More infos about this topic soon. Best Regards, Thorsten.

It could be directly connected to a MBSEQ V4, especially since a special 303 Edit view is available meanwhile. Parameters can be controlled from a dedicated Mixer Map, complete patches (stored on SD Card) could be sent from the SysEx menu :) Best Regards, Thorsten.

The FT232 chip has to be connected directly to J11 (without optocoupler) anyhow, because it works at TTL level and not as a current loop like MIDI. With All-Zero ID the MIDI interface will run at a common MIDI baudrate of 31250 - is it possible to select this baudrate on a FT232? Best Regards, Thorsten.

I must say that I haven't expected that R30 could disturb serial transfers to the SD Card - I will add a comment! Best Regards, Thorsten.

Edelst!!! :smile: Gruss, Thorsten. P.S.: habe das Posting in die "MIDIbox of the Week" Sektion verschoben

Great project and a very nice price! I guess that the CS will run on a second chip which sends the parameters to the "SSP" via MIDI? Is it possible to reprogram the chip, resp. to try code modifications? Best Regards, Thorsten.

Congratulations! It's especially great to see that you got it housed into the Heidenreich case with Julians frontpanel! This proves that it works! :) Best Regards, Thorsten.

Maybe the FT232BL transmits at the wrong baudrate? (I've no experiences with this chip... at the time it was released I already developed my own MIDI interfaces ;)) Best Regards, Thorsten.

Possible: yes Application: nobody implemented this for MBSID yet... a sophisticated ripper exists for HardSID as far as I remember. Best Regards, Thorsten.

:ahappy: Best Regards, Thorsten.