TK.

First of all it's important to use the "18f" version which can be found under http://miostools.midibox.org/ If SysEx transfers are unstable with this version, it could be related to a Windows driver issue of your MIDI interface (SysEx blocks > 256 bytes not transfered completely). Miditrix helps to overcome this - some informations can be found here Best Regards, Thorsten.

It's like you are trying to open a .mp3 file on your computer, but no MP3 player is installed... You've to upload the midibox64 application. Best Regards, Thorsten.

I checked the testtone application on my MBFM to ensure that this isn't related to a SW issue - it works, all 4 channels output the 1kHz sinewave Best Regards, Thorsten.

ENS->SID If you don't like the cumbersome usage, add SID buttons! Best Regards, Thorsten.

Chaining up to 16 DIN SRs is a physical, and not a software limitation. See also this posting However, beside of the possibility to use a button matrix with the old PIC based solution (1024 buttons or even more buttons? no problem) with MIOS32 it's much easier to scan a second DIN chain with less programming effort because of the flexible framework (e.g. generic SPI access functions) and C as a programming language instead of cryptic assembly code. It's definitely worth to wait for the public release (some people are already using the MBHP_CORE_STM32 module) Best Regards, Thorsten.

Thank you.

You are right... pin #28 was the intended one. To summarize: you've checked the SID itself, the amplifier, the control signals between 74HC595 and SID, the 5V/12V supply voltage - so: almost all pins, and they are ok. Remaining pins are #1..#4 (caps) can only be checked visually (should be easy!) Pin #6 (the clock pin) is connected to CORE::J10:PWM. On the core, it's a routed to Pin #17 of the PIC. Depending on the PCB you are using, a cable is required as a bridge (see also this picture - the red marked connection) - did you consider this? /Edit: a better picture Best Regards, Thorsten.

Ok, last possibility: measure the voltage between pin #14 and #24 #28 when the SID is plugged in. For a 6581 it should be 12V Best Regards, Thorsten.

Yes - so it seems that your SID isn't working. From where did you get it? Are you able to test it on an old C64? Best Regards, Thorsten.

The 74HC595s can be tested with the mbsid_interconnection_test application. See the README for details about the test procedure. Best Regards, Thorsten.

The testtone application has a special feature which allows you to test the output amplifier without SID. Power Off your MIDIbox, unplug the SID, apply power again and connect pin #8 of the socket with pin #27. Do you hear a 1 kHz pulse sound thereafter? Best Regards, Thorsten.

Ich nehme mal an, dass Du DEFAULT_J5_FUNCTION auf 1 gesetzt hast: ;; 1: J5 used for analog inputs - A0..A4 control Knob#1..#5, A5..A7 are not used at all Die Knob funktionen lassen sich im "KNB" Menue zuweisen, siehe auch: http://www.ucapps.de/midibox_sid_manual_l.html suche nach "Knob" Bei Basslines Patches sind Knob #1 und #2 per default dem CutOff und Resonance Parameter zugewiesen, bei anderen Patches musst Du das selbst tun. Gruss, Thorsten.

Shipped yesterday: mbreges kynsi puddingbrumsel fairplay Brianh Geoff_P theraven raoulblues polykobol Best Regards, Thorsten.

Fixed in midibox_seq_v3.4c. Best Regards, Thorsten.

Pollin hat ein Noname-MIDI Interface fuer 20 EUR im Angebot http://www.pollin.de/shop/shop.php?cf=detail.php&pg=NQ==&a=MDk5OTcyOTk= Es waere interessant, ob es stabil laeuft. Gruss, Thorsten.

Es ist normal, dass sie die letzte Einstellung nicht automatisch gespeichert wird. Du musst sie explizit unter ENS(emble)->SAV(e) abspeichern. Wenn kein ENS BankStick angeschlossen ist, nimm E001 H128* bedeudet, dass Du momentan eine Bank selektiert hast, die nicht existiert. Setze sie auf A001 (oder Deinen Lieblingspatch) bevor Du das Ensemble abspeicherst. Somit sind uebrigens nur 64 Patches verfuegbar. Leeren Patch selektiert? Es sollte auch ohne funktionieren, trotzdem wuerde ich sie anschliessen - so kann der Master schneller feststellen, dass wirklich keine Slaves angeschlossen sind. Gruss, Thorsten.

Beside of the flexibility: not really. OSC is even slower than MIDI over USB (tested with a UDP packets sent between Reaktor<->STM32 under MacOS and Windows) no - it's more interesting for experimental stuff. Accessing the motorfaders via OSC is more comfortable from Reaktor or Max/MSP. Another advantage: less cables and access from/to multiple computers if MBHP_ETH is connected to a WLAN bridge or router/hub/switch. But none of the DAWs I know natively support OSC yet. Best Regards, Thorsten.

...und mit der Stereo Konfiguration der Oberhammer! :) Gruss, Thorsten.

There is no solution to send strings to a STM32 via MIDI yet, mainly because I don't have that much Java skills. I was happy enough to get the output terminal running (code is based on the MIDI monitor window). At the MIOS32 side, it wouldn't be so that effort to support this (maybe 10 minutes to add this into the existing SysEx handler). The output functions are quite powerful. E.g., you can send formatted strings (printf like interface) and memory dumps. Example: This was my initial idea, and it's already used at many places :) Debugging is so much better with message/parameter output in plain text format. Also the typical troubleshooting application to check the hardware are much more verbose than the old MIOS8 ones which are sending cryptical MIDI events to notify about the status. A lot of programming effort to get it flexible enough, but it's nice that you will take over this job :) No, because such a file system which gives you access to HW resources as well would consume too much RAM. Another disadvantage: the string handling to access drivers (like known from uCLinux or eCos), generic pipes and/or block access layers, etc... consume some additional CPU time. Resources are better invested into application features instead of emulating something which isn't really relevant for our usecases. However, the existing low-level functions don't prevent you to setup a file system if you find this useful. Files of a SD card are accessed via a DOSFS driver. Running a single binary is still prefered (due to realtime requirements), but debugging possibilities are much better. MIOS32 itself doesn't support multiple programs stored in internal flash, which then can be executed from a file system. It's a nice idea, but not really applicable for a microcontroller without MMU (memory managing unit which maps address ranges) Means in other words: for STM32 memory references have to be located during compile time (by the linker) anyhow. Best Regards, Thorsten.

I won't release the C based MBLC V2 for the PIC, as it is incomplete (e.g. no graphical LCD support), and since I won't be able to maintain it in future. A STM32 module is already built into my MBLC case, but in the last weeks I focused more on trying some new stuff (e.g. controlling motorfaders via OSC messages transmitted over ethernet) than using the Logic Control protocol. The V2 code will be the basis for the MIOS32 variant... sooner or later. Best Regards, Thorsten.

Let's remember the good old times:

Ich gehe davon aus, dass Du die Upgrade Guide komplett durchgearbeitet hast... falls nicht, bitte nochmal alle Punkte durchgehen bevor Du auf folgende Fragen antwortest. Hoerst Du dieses typische Filter-Klicken beim Umschalten der Patches? Falls ja: MIDI Kanal falsch eingestellt? Gruss, Thorsten.

Alright, I gave you access to the programmers section of this forum (third board from the top, only visible when you are logged in) It will take some time until I will start with MBSID V3 for the STM32 module. However, SID access routines are already prepared and tested: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fsid%2F I also experimented with a "CAN<->OSC proxy", which allows me to access MBSID V2 via ethernet by using the OSC protocol. STM32 acts as a bridge between Ethernet and the CAN network of a MBSID V2: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fmbsid_can_osc_proxy%2F Best Regards, Thorsten.

Yes, the telnet access is already available, and a COM access (either via RS232 or USB COM) is prepared as well. Even a text based console via MIDI is feasible (and very comfortable, as it would allow an USB connection under Windows, where USB MIDI and USB COM cannot be used in parallel... MIOS Studio already provides a terminal window, which is currently only used to display debug messages) Examples: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fexamples%2Fethernet%2Ftelnetd%2F http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fexamples%2Fcom_console%2F Only missing thing is a command set for the shell. If you would like to help out, you are welcome to join the team :) Best Regards, Thorsten.

Thank you! :) The change is now in the code repository, so that it doesn't get lost. Best Regards, Thorsten.