TK.

Thanks for the compliments - now you should really contribute, regardless of the quality. Somebody else might fork a new patch from yours (-> double fun :)) Copy & Improve is explicitly allowed! Yes, it's only the feedbacked 6582 filter. Sometimes it sounds unusual since I'm driving it into saturation by using three oscillators for a single sound; the OSCs have to run at the same pitch (no detune!), the phases should be synchronized. This gives you some nice distortion for free :) Best Regards, Thorsten.

The error could also happen if you've uploaded the wrong MIOS version into your PIC. Please upload pic18f4685/midi/mios_v1_9g_pic18f4685.hex of the mios_v1_9g package, thereafter try to upload the application again. Best Regards, Thorsten.

Since you are using a single PSU, you should prefer starlike wiring: all grounds connected from the ground output of the PSU Best Regards, Thorsten.

Ich habe eine eigene Konfiguration erstellt (die dann auch in ein eigenes File erhaelt) Zum Einladen habe ich zwischen der Standard und der "MIDIbox" Konfiguration hin- und hergeschaltet, so hats bei mir geklappt. Gruss, Thorsten.

-> Best Regards, Thorsten.

Followup to Attached some bassline patches that I found on my second Bankstick. You already know the first ones from the remaining three ones were not published yet. Some short demos: direkt link, 13 MB (feedback pot used on all patches, external Fx and EQs have been added to the audio path) Update 2018-05-01: some new patches now released in SVN repository: http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fpresets%2F Some demos: http://www.ucapps.de/mp3/midibox_sid/mbsid_v2_tk2_soundbank_demo_part2.mp3 Please add your own patches to this thread, regardless if Lead, Bassline, Drum or Multi A MP3 which demonstrates the patches is nice to have, but no must! Best Regards, Thorsten. bassline_tk.zip

Use a pulse waveform and slowly modulate the Pulsewidth with an envelope. It's important that only a single oscillator is played, otherwise the sound will be "too fat" so that you won't notice the effect anymore. Best Regards, Thorsten.

For MIDIbox SID V2 you need a PIC18F4685 (96k flash). A PIC18F452 won't work, because it has only 32k flash. Also a PIC18F4620 won't work (this seems to be the first one that you tried) because it has only 64k flash Best Regards, Thorsten.

You should find the current consumption in the datasheet, it should be less than 10 mA. Best Regards, Thorsten.

Hi Mark, He bought a new AOUT_NG and this one worked for misterious reasons. If you are not able to solve the issue by yourself, would it be possible that you send me your module for further analysis? Because if this is a robustness issue, it would be good to know for me. Do you mean that your MBSEQ V4 is powered directly from the Mac w/o external supply, resp. an externally powered USB Hub? Yes, this could cause an unstable voltage with the effect that the AOUT_NG module won't work properly. Under certain conditions my own MBSEQ V4 crashes sporadically when it's directly powered from a Macbook Pro. Therefore I always use an USB Hub. Best Regards, Thorsten.

Since not only the DOUT, but also a transistor driver is involved, you have to build up a (small) part of the circuit. Best Regards, Thorsten.

This example just doesn't exist yet, and it will never be created for DOSFS since FATFS is much better. Tutorial #19 has to be overworked since it implies that DOSFS is the preferred choice (which isn't the case). This is the most simple code snippet which writes a file to SD Card: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fcore%2Fseq_file_g.c Best Regards, Thorsten.

Basically I'm using the same algorithm that I described under http://www.ucapps.de/mbhp_mf.html The biggest differences compared to the previous solution: Duty cycle has much higher resolution for more precise motor speed control Duty cycle depends on distance between current and target position -> than closer the target position, than slower the motor separate values for upward/downward movements, now for each motorfader individually. This is important to ensure that even after years all motors are running synchronously, because some get a bit slower, some others are still fast (the same problem which probably Alex noticed) Following picture shows how precisely a fader can be positioned now This is a ALPS RSAON11M9 fader at 5V. It overshoots the target position at t=100 mS, but can be precisely repositioned at t=180 mS to exactly the middle value (512) Such a control wasn't possible with the old solution. For those who prefer slow faders: just reduce the Max Duty Value :) Best Regards, Thorsten.

Funktioniert tatsaechlich! Danke - Tip des Monats! :) Gruss, Thorsten.

The big problem is, that you neither mentioned in the subject, nor in your first posting that you are working with MIOS32! It makes a big difference compared to MIOS8 (and the slow PIC) - please consider this next time. The MIOS32_SRIO_ScanStart() function is normaly called from vApplicationTickHook, which is a RTOS hook that is called each mS. See also http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fprogramming_models%2Ftraditional%2Fmain.c It isn't possible (resp. recommended) to change the interval of the timer which is used by FreeRTOS, but you could simply call MIOS32_SRIO_ScanStart from an own timer service routine. In order to disable the default handling, add "#define MIOS32_DONT_SERVICE_SRIO_SCAN 1" to your mios32_config.h file Now you can call the function from an own timer. The general usage of a MIOS32 based timer is explained here: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F007_mios32_timer%2F In order to speed up SPI transfers, it makes sense to reduce the number of SRs which have to be serviced, this can be done with "#define MIOS32_SRIO_NUM_SR <actual-number-of-sr>" in mios32_config.h Best Regards, Thorsten.

Hallo Stephan, ich gehe davon aus, dass Du nichts vertauschen musst. Falls die Tasten falsch gemapped werden, kann man die Notenwerte ja einfach in der Software umkodieren. Hier liegt nun die reduzierte Firmware - sie sieht sehr uebersichtlich aus ;-) http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fblm_scalar_4x8x8_buttons%2F Unter http://www.ucapps.de/mios/blm_scalar_4x8x8_buttons_v1.zip habe ich Dir ein fertiges Binary abgelegt, damit Du die Firmware gleich mal ausprobieren kannst. Gruss, Thorsten.

Hallo Stephan, die DOUTs muessen in diesem Fall invertierte Werte ausgeben, dies wird mit BLM_SCALAR_CATHODES_INV_MASK=0x00 eingestellt. Ich werde Dir morgen eine spezielle Firmware zusammenbasteln, denn die verfuegbaren Defines (die in blm_scalar.inc ausgewertet werden) sind nicht immer selbsterklaerend. Gruss, Thorsten.

Hi, the interconnection test isn't prepared for PIC18F4685; you also need a special modification in the MBFM firmware to get access to the OPL3 module. As I'm planning to upgrade my own MBFM to PIC18F4685 soon, I will be able to adapt the applications so that you are able to continue. Best Regards, Thorsten.

Thats fine for me, just try it :) Best Regards, Thorsten.

Hi Marxon, STM32F103RC has only 128k internal flash - this isn't enough. You could order the chip from Farnell.de or a reseller if you are not allowed to buy directly from Farnell. Best Regards, Thorsten.

Hi Axel, welcome back! :) By enabling the MIDI merger it will be possible to chain MBHP_MF_V3 with a common core module. The "Faked Logic/Mackie Control" Mode will handle the Pitch Bender Events. So: a Core32 won't be required, you can re-use your existing hardware and just only have to replace the MBHP_MF_V1 module. Best Regards, Thorsten.

Hallo Stephan, evtl. musst Du bei Deinem Webbrowser den Refresh-Button druecken; ich habe die blm_scalar Applikation erst vor zwei Stunden dort eingebunden (vorher war sie nur im Repository verfuegbar). Die fuenfte Matrix laesst sich im Makefile wie folgt deaktivieren: BLM_SCALAR_DEFINES += -DBLM_SCALAR_DIN5 0 [/code] Zum SVN: das Repository wird nicht mit dem Webbrowser, sondern mit einem speziellen SVN Client heruntergeladen. Falls Du unter Windows arbeitest, ist Tortoise die erste Wahl: http://tortoisesvn.tigris.org/ Weitere Infos stehen unter: http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_core Gruss, Thorsten.

Let's hope that Skra will finish his FPGA project (he is also member of this forum), usually he goes very deep into details: http://skrasoft.com/blog/?cat=31 Best Regards, Thorsten.

Thanks for the feedback - the first impression is always the most important one! :) I need this behaviour very often, e.g. when doing small changes in a pattern from any menu page to store the changes from the main menu, and to switch back to the page. There is no other button which would allow this. Just align your habits and press EDIT to exit the main menu instead ;) Since I don't use these buttons very often, it's very likely that I forgot to add the appr. code in seq_ui_*.c Could you please give me a list of pages where these buttons don't work? I know! :) Makes sense, I added this to the TODO list. thats strange - I checked the code and found that it even will be checked twice (one redundant line ;)) - but I don't see the reason why this button shouldn't work. I will test this with my HW soon. An interesting perspective (side view) which can only be realized with a VFD! :) Best Regards, Thorsten.

Hallo Stephan, zu 1: hierfuer gibt es bereits einen fertige Driver, er findet bei der BLM16x16+X Verwendung, und bedient defaultmaessig 5 8x8 matrizen. (Download hier, suche nach blm_scalar) Das besondere an diesem Treiber ist, dass er eine C Schnittstelle bietet, so dass man die zu sendeten MIDI Events relativ einfach selbst anpassen kann - siehe auch das main.c file: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fblm_scalar%2Fmain.c Eine 16x16 Matrix halte ich fuer ungeeignet, da sich hiermit die Latenz verdoppelt. Zu 2: bei der BLM_SCALAR sind die uebrigen DIN Register frei belegbar. Die 5. 8x8 Matrix liefert Dir bereits 64 weitere Eingaenge, es bleiben 11 DINs uebrig. Evtl. koennte man den Treiber auch so konfigurieren, dass noch mehr Matrizen gescannt werden (bin mir gerade nicht sicher, ob das problemlos funktioniert) Zu 3: funktioniert mit dieser Variante nicht, deshalb findest Du auch keine Hinweise in der Dokumentation. Gruss, Thorsten.