TK.

You don't really know what is going on, hm? GPUTILS is a 470k package and easier to install than MPLAB. Yes, you can still use MPASM, some files have to be converted so that they contain the DOS style linefeeds again. You also need to specify the target processor explicitely now, and sometimes you have to add an include path. If you don't know how to do this, just click on this link: https://sourceforge.net/project/showfiles.php?group_id=41924, and download the gputils-win32 package. It really doesn't hurt! Best Regards, Thorsten.

It remembers me on HardSID, but there is only one SID, the ready-built hardware is more expensive. Compared to MBSID you will mainly miss the polyphony, dedicated sound engines, modulation capabilities, wavetables, arpeggiators, live-sequencers, etc... etc... From the feature list: these are the SID internal functions, you will find them on any SID based synth Only two LFOs? Interesting, 2 ENVs I see 4 modulation sources Fits nice into the CC range Natively supported by the VST host Nice starting point Means: the filter is not self-oscillating. How about an automatic real time synchronisation between human and hardware? As workaround for PC based Logic Audio Thats the killer argument today! Sorry, couldn't resist ;) Just compare with the MBSID feature list, and consider that HyperSID is based on exactly the same hardware as MBSID V1! So, there is even no cost advantage. And we have a VST plugin as well: http://www.midibox.org/forum/index.php/topic,5116.0.html, so where is the innovation? Best Regards, Thorsten.

Fine that you solved this! :) Could it be, that he supply voltage of the PIC is not clean enough? (is there a big el-cap between 5V and ground?) Because a cap between +5V and Rx input normaly "worsens" the signal Best Regards, Thorsten.

Yes, the appr. label is named "MIDI_EVNT_Send_Int" Best Regards, Thorsten.

Ooops! Thanks for the input, it's a programming error in j5_dout.inc You need to replace ;; disable the ADC which allocates the analog pins movlw 0x07 movwf ADCON1 [/code] by: [code] ;; disable the ADC which allocates the analog pins #if PIC_DERIVATIVE_NEW_ADC == 0 ; PIC18F452 movlw 0x07 #else movlw 0x0f ; all newer PIC18F derivatives (like PIC18F4685) #endif movwf ADCON1 It will be fixed in the next release Best Regards, Thorsten.

So, you tried it but it doesn't work? I think that this code is ok. It's simple math: scaled_value = (min + (unscaled_value*2 * (max-min+1))) / 256; Best Regards, Thorsten.

Ok, conversion for these particular applications already done: http://www.ucapps.de/mios/sm_example1_v2a.zip http://www.ucapps.de/mios/sm_example2_v1a.zip Best Regards, Thorsten.

You don't need to do this, Stryd - I'm planning an official re-release of these applications as well - very soon (not today, as I got too many emails due to other issues... :-/) Best Regards, Thorsten.

Thats very difficult, because the 3 bits which are reserved for MIDI ports are already allocated: ;; o WREG == 0: Default port (depends in MIOS Interface Definition) ;; o WREG == 1: Internal port ;; o WREG == 2..5: IIC0..IIC3 ;; o WREG == 6: Loopback to Sequencer MIDI Engine ;; o WREG == 7: AOUT [/code] you would need to restructure a lot of things - it isn't really worth the effort. Maybe it would be easier to (mis-)use an existing port instead, e.g. IIC4 (if no 4th IIC module is connected) Thank you for the nice words! :) Best Regards, Thorsten.

You can use PortB as input when the appr. TRISB flags are set (Tristate driver - means: pin is not driving) However, the best choice for output pins which are not used by any other resources are RC0, RC1 and RC3. The best choice for an input pin which is not used by any other resource is RC2 (it already has an pull-up, which is perfect to prevent random values if the pin is open) By using these pins, you don't need to modify the TRISx configuration, just use (for example) PORTCbits.RC0 = 1; to set the pin to 5V, and PORTCbits.RC0 = 0; to set the pin to 0V Same for RC1: PORTCbits.RC1 = 1; // 5V PORTCbits.RC1 = 0; // 0V And don't touch anything related to the LCD Port B Hope that this answers your question? Or do you need even more input/output pins? There are special solutions for J5 and LCD port, but they require additional configuration... and you need to warn the end-users to disconnect the LCD, or disconnect pots (of J5 used as output) to prevent short-circuits. Best Regards, Thorsten.

Hi Matteo, There is no need to use MPASM anymore, and it's strongly recommented to publish applications GPASM-compatible in future, so that even Linux and Mac OS users are able to customize an application, and to create a new .hex file. Thats the reason, why I'm planning to re-release all my own applications, which isn't so much effort at all. GPASM is slightly incompatible to MPASM (macro expansion), MPASM is slightly incompatible to GPASM (cannot handle files w/o DOS-style linefeeds, cannot handle filepathes longer than 63 characters). But at the end GPASM brings us more advantages than MPASM. If somebody encounters issues with the usage of GPASM, or with the conversion of an old, selfwritten application, just ask in the Assembler programming section for help. I'm willing to support you during the migration, I could also do this for you (it takes ca. 1 minute) if desired. Best Regards, Thorsten.

Hi, it's shouldn't be so complicated - look at MIDI_EVNT_Send_AOUT in midi_evnt.inc (please download the latest re-release of MBSEQ before doing modifications) Parameters are: MIDI_EVNT0 (either 0x9n or 0xbn for Note/CC; n = channel), MIDI_EVNT1 (note/CC number) and MIDI_EVNT_VALUE (velocity/CC value) Best Regards, Thorsten.

Und hier die Aufloesung: der PIC war nicht richtig programmiert; die Adressen 0x310..0x317 (liegt im Bootloader-Bereich) waren mit 0xff belegt. Gruss, Thorsten.

I give you an hint: update to one of the latest firmware versions. Best Regards, Thorsten.

I gave you permission to upload files. Best Regards, Thorsten.

You could help me by writing a bad feedback on this auction, which points out what he is doing This could even motivate me to spend some time to understand and solve your issue. So, you are the first customer of an illegal sale who expects help from my side, how much additional sparetime do I have to spend for supporting even more people w/ zero knowledge about how to fix the hardware, how to upload a new firmware version, etc... hope that you see the point. Best Regards, Thorsten.

Drum kit and instrument voices are seperated. Each drum has a dedicated voice (no issue here), but the 4 instruments have to share 6 voices. So, it depends on what exactly you are planning to play (poly or mono sequences?). However, maybe better to build a MBSID in addition for more voices and more variation - especially because MBSID has improved inbuilt sequences. :) Best Regards, Thorsten.

Do you mean something like demonstrated in this example: http://www.ucapps.de/mios_c_pic_pin.html Best Regards, Thorsten.

Hi Gene, I hope that you understand, that I'm not willing to help somebody who bought a MIDIbox device from somebody, who never got my permission. It's totally furstrating for me, that there is no chance to stop this (sorry for the harsh word) idiot. He got the money, and we have to support the customers? Not with me! Best Regards, Thorsten. P.S.: it isn't personally against you, you probably didn't know about these illegal sales

This topic has been moved to MIDIbox of the Week. [iurl]http://www.midibox.org/forum/index.php?topic=10547.0[/iurl]

Beautiful! :) My first thought after I saw the yellow-black label: it's perfectly matching with this amp design: Best Regards, Thorsten.

Great to hear, that you finally solved the issue :) Yes, thats normal. You could increase the capacity of C27/C28/C29/C30, but this would filter the "wanted" higher frequencies as well. A better solution could be the usage of a 24 dB (or more) lowpass filter - but this requires some additional hardware (-> expensive solution) Best Regards, Thorsten.

Hi, concerning FM drum kits: you can create 4 additional, more complex, drum sounds by using FM instruments. They can be assigned to the same MIDI channel like the drum kit, and assigned to a special note (or keyboard range) Best Regards, Thorsten.

Just prepare a dedicated basis patch for each engine, and switch to the patch via Program Change. Patches of the preset bank can be used for this, or new ones can be created with the SysEx editor (once available) Best Regards, Thorsten.

did you already change the baudrate? The "to-com" flag has to be set in the PIC ID header. You could do this with the change_id application. Open main.asm, change value of MIOS_TO_COM_FLAG to 1, rebuild the main.hex file with "make", and upload the new .hex file via MIDI. Thereafter the baudrate is changed for LTC interface (communication via MIDI won't be possible anymore) If MIOS has been uploaded correctly (and it seems that this is the case), this display should work fine. See this page for troubleshooting tips: http://www.midibox.org/dokuwiki/troubleshooting_lcd_displays Best Regards, Thorsten.