TK.

Hi, these are the wrong defines, because they are part of the old BLM driver, which is referenced, but not used at all (instead the new blm_scalar driver is used) In order to make this clear, I removed all references to the old BLM driver and added all available defines to the Makefile: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fblm_scalar%2FMakefile Please update your svn repository, or download blm_scalar_v1_0a.zip from the MIOS download section Best Regards, Thorsten.

The trick: you can shift any data to both SIDs as long as the CS# line is individually controllable. Register accesses will only happen on a 1->0 transition. See also this source, SID_UpdateReg() function. The code also shows how dual SID transfers can be optimized by checking if the same value has to be transfered to both SID chips - in this case both CS# lines are activated to avoid a redundant SR load. Best Regards, Thorsten.

MBSID has already such a page, for MBSEQ it will be very difficult as some parameters can't be displayed in a single 5 character item. It would be too difficult to provide a generic configuration page :-/ However, I'm glad that you like the new features - I like them too! :) Best Regards, Thorsten.

Just yesterday, I had a similar experience: a loose contact in a MIDI cable from Reichelt -> trash can :-/ Best Regards, Thorsten.

Thanks a lot for beta testing!!! :) These bugs are now fixed in beta35: MIDIboxSEQ V4.0beta35 ~~~~~~~~~~~~~~~~~~~~~ o bugfix: step view displays steps >= 17 correctly again o bugfix: step length displayed correctly again in "step view" o new feature for more comfortable editing of multi-note tracks: if assigned parameter layer is Note or Chord, and currently 0, re-start at C-3 resp. A/2 when value is incremented [/code] Best Regards, Thorsten.

Beta34 is available - you will like it! :) MIDIboxSEQ V4.0beta34 ~~~~~~~~~~~~~~~~~~~~~ o implemented various "Edit Views". Press SELECT button to select the view in EDIT screen. Following views are available: - Step View: you already know it - Trigger View: left page allows to select the step, Gate, Accent, Roll, Glide, Skip, Random Gate and Random Velocity. Right Page allows to edit up to 8 parameter layers. - Layer View: allows to select the step, Gate and up to 14 parameter layer. Especially nice for custom chord editing. - 303 View: provides a 303ish interface to select the Step, Gate, Accent, Glide, Octave, Note, Velocity and up to 9 additional parameter layers - Step Select: allows to select the steps which are modified by the ALL function o glide trigger now handled (much) more 303-like o added testmode for AOUT interface connections. Enter "testaoutpin" in MIOS terminal for further informations o step record function now allows to define the step incrementer (+0..16) in "Record Mode" item o BLM keyboard mode: each column plays now an assigned drum instrument o new BLM entry mode 303: - first row selects accent - second row selects glide - third and fourth row select octave (4 different selections) - remaining rows select key of octave and set/clear gate o new session now initialized correctly after "SaveAs..." o optional "Tap Tempo" button is working now o optional "Left" button is working now in all menu pages [/code] Please note: 303 Glide function will only work correctly if your synth supports "fingered portamento" (sometimes also called. "SusKey") and legato mode. Best Regards, Thorsten.

Super dass das alles so gut geklappt hat! :) Somit hast Du Dich fuer den Programmer Status qualifiziert - ich habe Dir Zugriff auf die Lounge gegeben, wo Du wesentlich detailiertere Informationen finden wirst. -> http://midibox.org/forums/forum/41-programmers-lounge/ Gruss, Thorsten.

Hi, are numbers incremented/decremented when you shortly connect DIN pin 4 and 5 to ground? No: strange! Did you really recompile the project to generate a new .hex file? Yes: the encoder pinning is different - check it. Best Regards, Thorsten.

No, there shouldn't be a short circuit during power-on, because these pins are input-only (no drivers) So: yes, just connect the unused inputs directly to 5V Best Regards, Thorsten.

Last time you had such strange issues it was related to a private modification in your repository. So, something is inconsistent again... You could find out all changes with the "svn diff" command, e.g. "svn diff $MIOS_PATH" Best Regards, Thorsten.

Hallo, Du kannst eine beliebige MIOS32 Applikation aufspielen, der Bootloader wird immer darin enthalten sein. Im .hex File stehen bereits die richtige Adressen (ab 0x08000000) (MIOS32 ist etwas unkomplizierter zu handhaben als MIOS8, deshalb gibt es ueber diese Themen auch keine besondere Dokumentation ;-)) Gruss, Thorsten.

Meanwhile it's Juce 1.51 Once I update to a new version and change the source codes accordingly, previous Juce releases won't work anymore. Best Regards, Thorsten.

Since you are using a PIC, you will need a scope for accurate measurements, because all timer resources are allocated. However, your PIC doesn't reset because the output is too fast, but because the watchdog won't be serviced (-> see datasheet for details) You have to execute the clrwdt instruction at least once per second, e.g. you could execute it whenever a new patch will be sent. On a MBHP_CORE_STM32 you could use the MIOS32_STOPWATCH functions. Best Regards, Thorsten.

also ich lese setup_midibox64.hex Diese Variante unterstuetzt keine Motorfader. -> nimm midibox64e oder midibox_mf -> zu downloaden unter http://www.ucapps.de/mios_download.html -> lies die README.txt files -> und lies den Inhalt der entspr. setup_*.asm files! was meinst Du nun wieder mit mbox_mf? ja... ja... Gruss, Thorsten.

MIOS_BANKSTICK_WritePage will never return 0x40, only 0x00..0x02 (0x00 on success) It seems that you are using a corrupted C compiler version - which one exactly? Please type "sdcc --version" It should return: SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.8.0 #5117 (Mar 23 2008) (Mac OS X i386) [/code] (-> 2.8.0) Best Regards, Thorsten.

Zum P1 Poti schaltest Du am besten noch einen 470 Ohm Widerstand in Reihe, so wie in diesem Schaltplan zu sehen: http://www.ucapps.de/mbhp/mbhp_mf_v3.pdf Andererseits werden die Fader wahrscheinlich auch mit 6V prima funktionieren - und sie werden vor allem leiser als mit 7.5V laufen. Zu dem seltsamen LCD Output: kann ich nicht nachvollziehen. Ich vermisse auch irgendwie die Angaben, was Du genau gemacht hast - es gibt bspw. keine "Mbox64.hex" Datei (zumindest habe ich ein File mit diesem Namen noch nie released). Und wenn Du damit ein .hex File der MIDIbox64 Applikation meinst, dann waere es mit Sicherheit die falsche. Fuer Motorfader waere eher midibox_mf oder midibox64e (-> setup_midibox_mf.hex) geeignet. Gruss, Thorsten.

Hi Michael, the precompiled toolchain hasn't been prepared for PPC (it isn't an universal binary). And from my experiences it will be very difficult! No, you can't use Xcode to compile the toolchain. Before writing too many redundant words, I give you access to the Programmers Lounge where we discussed the details about the toolchain and shared scripts. Best Regards, Thorsten.

Due to the strange LCD output messages it seems that your installation is corrupted... I never got the MIDI upload properly working on my own (old) Linux Laptop, therefore I can't really help you. Do you have access to a PC or Mac? (e.g. try it out with the computer of a friend) Best Regards, Thorsten.

MIDIbox FM V1.3 has been released! From the ChangeLog: MIDIboxFM V1.3 ~~~~~~~~~~~~~~ o PIC18F4685 only: Wavetables are stored in RAM for non-destructive editing o name is now entered when a patch should be stored in SAVE menu o random generator now copies new patch into all selected instruments o fixed waveform display in drum pages [/code] Best Regards, Thorsten.

Yes, thats ok Best Regards, Thorsten.

I'm not sure what you mean with "mcu32" and why you would need two of them, maybe you wrote this question in the wrong forum? This is midibox.org, we are using the hardware platform of uCApps.de Following tutorial describes how to scan up to 128 buttons with a MBHP_CORE_STM32: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F010_din%2FREADME.txt If you are searching for a ready built solution, and don't rely on high flexibility (e.g. programming your own "control logic"), go for Doepfer - they have a USB based button scanner as well. Best Regards, Thorsten.

Toolchain: please use the official version which is qualified for MIOS32: http://www.ucapps.de/mios32_c.html It won't solve the bootloader compile issue - but again: you don't have to compile it anyhow! Best Regards, Thorsten.

I'm also not sure about the second problem, but to the bootloader: you don't need to compile it by yourself, as a precompiled binary (0x0000..0x3eff) is always part of any MIOS application build, because it's added in http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmios32%2FSTM32F10x%2Fmios32_bsl.c In other words: flash any MIOS32 application via JTAG or UART, this will install the bootloader as well! :) Best Regards, Thorsten.

Boyz with big PMUs don't need to reduce the brightness :D

are 500mA really sufficient for 2 SIDs + the big variety of LCDs which are used for this project? (some backlights draw only 100 mA, some others 300 mA and more) The result could be, that the input voltage drops below 10.5V, so that the 7809 won't output 9V anymore -> the filter won't work correctly, or there won't be any sound output at all. Another possible effect: the PSU gets hot because it isn't dimensioned for permanently high power consumption. Low-quality PSUs will be damaged over time (1..2 years) if they are used out-of-spec - I had this issue several times in the past. /edit: btw: Best Regards, Thorsten.