TK.

Just to ensure that we have the same understanding ;) Not for the touch sensor, but as a good shield against noise (which would result into jitter). A perfect ground connection to the case is important, the connections via M3 screws are not sufficient. If you want to save money, it's a good choice. The motorfader project was created before BCF2000 came to the market, today I probably wouldn't do the effort anymore. We opened a BCF2000 case long time ago in doc's lab - the construction is impressively compact, faders and motors are directly soldered on a PCB. It was too hard (and dangerous) to find a way to control the faders directly with the core module. We haven't measured voltages, but it can be assumed that they are either 0-5V or 0-3.3V Yes, thats possible softwarewise, but the idea to connect the VCA CV directly to the MF wiper wasn't so bad, I think that this will already work, so that no AOUT module is required. I would need a frontpanel for my 16x16 BLM - I will write you a separate PM :) Best Regards, Thorsten.

Whenever a meta event is assigned to a button, pot or encoder, the meta handler will be called and here it's totally in your hand how the event should be processed. To improve the understanding, just let's try different code snippets. 1) send a constant SysEx stream - replace the code in mb64e_meta.inc by: MB64E_META_Handler_Enc MB64E_META_Handler_Fader MB64E_META_Handler_Button movlw 0xf0 call MIOS_MIDI_TxBufferPut movlw 0x01 call MIOS_MIDI_TxBufferPut movlw 0x02 call MIOS_MIDI_TxBufferPut movlw 0x03 call MIOS_MIDI_TxBufferPut movlw 0xf7 call MIOS_MIDI_TxBufferPut return [/code] Note that all Labels are assigned to the same code, so that encoders/faders and buttons can access the same meta events. Now assign "F0 00" to a button, e.g. with the mk_syx.pl script (I prefer this one), or with serge's SysEx editor (don't know if it still works, it hasn't been maintained since years, and I'm a Mac user...) The button should send this SysEx string. Depending on the button mode (OnOff/Toggle/OnOnly) it will be sent only on pressed, or on pressed/depressed button. I would recomment OnOnly mode here, so that the event will only be sent when the button is pressed, and not when it has been depressed Next step: as you can read in the comments: [code] ;; -------------------------------------------------------------------------- ;; This function is called by MB64E_midi.inc when a meta event (Fx xx) has ;; been assigned to a enc or button ;; You can use this handler to enhance the firmware by your own MIDI events. ;; Here you are able to send more than one MIDI event (i.E. two Note On ;; Events to control Cakewalk via MIDI remote with one button), or a ;; SysEx/NRPN string to your synthesizer, or just to toggle PIC pins ;; in order to switch relays... ;; IN: ;; on enc events (entry point: MB64E_META_Handler_Enc): ;; o Enc number in MB64E_CURRENT_ENC (BANKED access required!) ;; o first MIDI byte in MIDI_EVNT0 (no BANKED access required) ;; o second MIDI byte in MIDI_EVNT1 (no BANKED access required) ;; o enc value in MIDI_EVNT_VALUE (no BANKED access required) ;; ;; on button events (entry point: MB64E_META_Handler_Button): ;; o Enc number in MB64E_CURRENT_BUTTON (BANKED access required!) ;; o first MIDI byte in MIDI_EVNT0 (no BANKED access required) ;; o second MIDI byte in MIDI_EVNT1 (no BANKED access required) ;; o button value in MIDI_EVNT_VALUE (no BANKED access required) ;; -------------------------------------------------------------------------- Parts of the MIDI event (Fx xx, marked with x) are available in variables, which you can use to build your SysEx stream. E.g., with: MB64E_META_Handler_Enc MB64E_META_Handler_Fader MB64E_META_Handler_Button movlw 0xf0 call MIOS_MIDI_TxBufferPut movf MIDI_EVNT1, W call MIOS_MIDI_TxBufferPut movlw 0xf7 call MIOS_MIDI_TxBufferPut return [/code] The SysEx stream will contain the second byte of the MIDI event. E.g., with Meta Event "F0 11" this routine will now send "F0 11 F7" And with Meta Event "F0 22" this routine will send "F0 22 F7" Now try: [code] MB64E_META_Handler_Enc MB64E_META_Handler_Fader MB64E_META_Handler_Button ;; send F0 7F 00 06 xx F7 movlw 0xf0 call MIOS_MIDI_TxBufferPut movlw 0x7f call MIOS_MIDI_TxBufferPut movlw 0x00 call MIOS_MIDI_TxBufferPut movlw 0x06 call MIOS_MIDI_TxBufferPut movf MIDI_EVNT1, W call MIOS_MIDI_TxBufferPut movlw 0xf7 call MIOS_MIDI_TxBufferPut return and try Meta event "F0 01", "F0 02", "F0 03", "F0 04", "F0 05" with button mode "OnOnly" Success? Best Regards, Thorsten.

It would be required to overwork MIOS from scratch, e.g. because of overlapping memory ranges and missing support for multiple MIDI ports, resp. MIDI handling which fits with USB requirements (packet based transfers). All this has been solved with MIOS32, I don't plan to do the same for old PIC derivatives (especially because it would never work so perfectly like with STM32) However, if you have advanced programming skills, you could use the MBHP_USB_PIC firmware as basis and add AIN/DIN/DOUT/LCD drivers there - it's possible, but it will be some effort and it won't be compatible to the common MIOS8 architecture. If you are asking me: it isn't worth the effort, since with MIOS32 a better solution is already available. It's available here: http://www.avishowtech.com/mbhp/buy.html Best Regards, Thorsten.

yes, and you can apply different filter settings/modulations to the left/right filter by selecting the L/R channel via SHIFT->GP button 1 and changing the parameters in FIL and MOD page. Best Regards, Thorsten.

There wasn't a change in the application itself... however, I updated the ChangeLog: http://www.ucapps.de/mido128_changelog.html Best Regards, Thorsten.

Yes, it will work when you swap the two motor pins and the Ground/+5V terminal of the fader. Take care: the metal case of the fader still has to be connected to ground, and not to +5V! Best Regards, Thorsten.

ucapps.de is my website, as you can see at the bottom of each page. The .zip file got the wrong version number (v1.1d is the right one), I will change the filename, and also fix the documentation. Best Regards, Thorsten.

Shipped today: zygis simonfloris Best Regards, Thorsten.

In Germany we call this "Schwanzvergleich" - it's better not to translate this term. ;) Don't get me wrong, Propeller is a nice SoC and it was obvious that sooner or later somebody will implement a SID emulation for this chip. It would be interesting, how long you worked on this project, and if you feel that there are enough resources free (not performance, but also memory wise) to enhance it in future. Or would you prefer to add a second uC to control the emulated SIDs? Best Regards, Thorsten.

What is the 8th Propeller core doing - USB? Best Regards, Thorsten.

Awesome! Was it pure imagination, or did I hear some unobtrusive stereo effects? Best Regards, Thorsten.

Since we don't hear filter sounds, it's probably a project which plays .sid tunes on an emulated SID. Nils, now it's your turn to demo your emulation which is running on the STM32 :) Best Regards, Thorsten.

In MIOS Studio hex file upload window, set the device ID to 70 (because thats the current one). Get the change_id application, and upload the device_id_00.hex file with this device ID. Thereafter you are able to upload with device ID 00 Best Regards, Thorsten.

Yes! Best Regards, Thorsten.

Btw.: with the setup_sammich_sid.hex file of the latest RC34 release, the LEDs should start to flicker ca. 2 seconds after startup for ca. 3 seconds Best Regards, Thorsten.

Hi, It seems to be a different problem. No, a gray icon indicates a successfully enumerated physical MIDI device. Cannot be excluded yet Cannot be excluded yet Yes, this is a sign of life. Looks nice, no? :) First we should exclude that this isn't a configuration problem with MIOS Studio. Click on "Options->Restore Default Internal Routing" to restore internal connections for the case that you unintentionally removed them. Thereafter ensure, that MIOS Studio In/Out ports are connected to the MIOS32 ports as shown in the newbie guide: http://www.ucapps.de/mios32_bootstrap_newbies.html If this still doesn't help, you could also try to contact the core with the SysEx tool of MIDI-Ox. Send: F0 00 00 7E 32 00 00 01 F7 The core should reply with: F0 00 00 7E 32 00 0F 4D 49 4F 53 33 32 F7 Does this help? Best Regards, Thorsten.

Unfortunately the new Apple extension doesn't support SysEx (yet). It also freezes Java when the device is closed. Meanwhile mmj is only running under MacOS 10.4 and 10.5 if Java 32bit enabled (64bit variant has to be explicitely disabled in Java preferences). Under MacOS 10.6, only the Mandolane driver is working correctly. Best Regards, Thorsten.

You are probably using an unregulated PSU - the voltage will be lower once the PSU is under higher load. Check the voltages again once the ICs are put into the sockets, and the LCD is connected. It could be, that thereafter the 7809 won't output 9V anymore. Best Regards, Thorsten.

No, it works like expected. :) I haven't mentioned the Pull-Up resistor R9 of the core module, which will pull the input voltage to 5V if the pin is not connected to ground. Accordingly, connecting the input pin to 5V doesn't make a difference anymore. So, your core and the MIDIO128 application is working correctly. But: Do you really mean a MBHP_AINX4, or MBHP_DINX4 module? An AIN module (Analog Input) would be the wrong one. Are the MIDI events still retriggered if QH is permanently connected to ground? If not: do you still notice the same issue as you described before with the new DINX4 module? Best Regards, Thorsten.

Great work and funny video presentation! I blogged this, and I'm patiently waiting for the second part :) Best Regards, Thorsten.

Upload the setup_sammich_sid.hex file again, this time with Smart mode and bidirectional MIDI IN/OUT connection. The other .hex files won't work correctly with the hardware, as LEDs/Buttons are assigned differently. Best Regards, Thorsten.

I've compiled the application again with the "base SDK" in the hope that this helps. Please try http://www.ucapps.de/tmp/SIDPLAY_with_ASID.app.zip This version also supports the "Pause" button. Best Regards, Thorsten.

Or combine following examples: http://www.ucapps.de/mios_c_send_enc_rel.html http://www.ucapps.de/mios_c_handle_mf.html http://www.ucapps.de/mios_c_send_din.html http://www.ucapps.de/mios_c_set_dout.html Best Regards, Thorsten.

Shipped today: dnode suchoj Best Regards, Thorsten.

Great build and nice video! :) *blogged* Best Regards, Thorsten.