TK.

Hallo, Deine Pot-Eingaenge haengen in der Luft, deshalb sendet die Box Zufallszahlen. Falls Du noch keine Fader hast, schliesse die 8 analogen Pins (J5) einfach an Masse Gruss, Thorsten.

Ich sage einfach mal: egal ;-) Die kleinsten Widerstaende (0.25 Watt) reichen allemal. Die Sternschaltung ist nur fuer analoge signale relevant, um Jitter zu vermeiden. Bei digitalen Signalen ist es egal, woher die Masse kommt. Widerstands-Arrays lassen sich problemlos einsetzen (spart Loetaufwand) Gruss, Thorsten.

Das LCD selbst verbraucht so gut wie keinen Strom, aus dem Datenblatt ist ja zu entnehmen, dass der Wert bei ca. 1 mA liegt. Bei Graphic-LCDs sind es maximal 10 mA. Die Hintergrundbeleuchtung verbraucht dafuer umso mehr Strom - siehe Datenblatt: typischerweise 200 mA. Mit dem Backlit-Poti kann man den Strom wiederum reduzieren, das Backlit wird dabei dunkler. Gruss, Thorsten.

Hi Lo, unfortunately there is currently no way to configure the applications w/o the assembler. Creating a GUI is a lot of effort and should not be started before the features are frozen... for myself it would be a "creativity blocker" if I would have to adapt a GUI to new features with every new release. yes, a MBMF port is planned, it will be compatible with the PIC16F solution so that Serge's Editor can be reused. The pot on the MF board has to be adjusted, yes. The MF calibration app allows you to find the perfect settings for: MF board voltage, motor speed for up/down movements, MF deadband, AIN deadband. The deadband itself is just the value range in which changes are ignored. For example, if the analog input has some noise which causes jitter, you can increase the deadband in order to filter the unwanted changes. With an increased deadband value you also decrease the resolution. For a 10-bit value a deadband of "0" is recommented. For a 7-bit MIDI value, a deadband of "7" is perfect (just try it to find out the difference). The PIC16F firmwares are working with a deadband of 7 by default. MF deadband is nearly the same - it means that the fader will only be moved if the new position is above or below the current position +/- deadband value Best Regards, Thorsten.

Hi Lo, unfortunately there is currently no way to configure the applications w/o the assembler. Creating a GUI is a lot of effort and should not be started before the features are frozen... for myself it would be a "creativity blocker" if I would have to adapt a GUI to new features with every new release. yes, a MBMF port is planned, it will be compatible with the PIC16F solution so that Serge's Editor can be reused. The pot on the MF board has to be adjusted, yes. The MF calibration app allows you to find the perfect settings for: MF board voltage, motor speed for up/down movements, MF deadband, AIN deadband. The deadband itself is just the value range in which changes are ignored. For example, if the analog input has some noise which causes jitter, you can increase the deadband in order to filter the unwanted changes. With an increased deadband value you also decrease the resolution. For a 10-bit value a deadband of "0" is recommented. For a 7-bit MIDI value, a deadband of "7" is perfect (just try it to find out the difference). The PIC16F firmwares are working with a deadband of 7 by default. MF deadband is nearly the same - it means that the fader will only be moved if the new position is above or below the current position +/- deadband value Best Regards, Thorsten.

Hi Lo, a port of all existing PIC16F firmwares to MIOS is planned, so that the configuration will be as easy as with the old firmwares. But it could take some weeks until I will find the time for this step Best Regards, Thorsten.

Hi Lo, a port of all existing PIC16F firmwares to MIOS is planned, so that the configuration will be as easy as with the old firmwares. But it could take some weeks until I will find the time for this step Best Regards, Thorsten.

No problem... in the meantime I made some music with the PIC18F based SID and noticed no malfunction anymore. Working with the minimal control surface already makes more fun than using the editor, but I think that I should start with the complete control unit now for even more fun ;-) Best Regards, Thorsten.

yep

The only way to verify the crystal is to use an oscillator and a scope, or to ask the manufacturer :-/ However, the PIC should run with a different frequency, that means: a LED hooked to MIDI Out should flicker during startup. Just only the MIDI receiver will not regognize the MIDI events because of the baudrate mismatch. Capacitance of the crystal: doesn't really matter here, it's only relevant for radio applications. 15 pF are fine Best Regards, Thorsten.

Hi, unfortunately Reichelt doesn't offer rotary encoders :-( An orderling list can be found under MBHP->MIDIbox16E->Design Best Regards, Thorsten.

Currently we have two possibilities to create arpeggios: set the arpeggio rate > 0 and play a chord (up to 4 notes are provided). Note that every oscillator has an own arpeggiator, so with the control surface you should select OSC "123" together and set the rate for all three oscillators to the same value use the wavetable sequencer to modulate the transpose CC - in this way an arpeggio can be played with one finger yes, MIDI clock sync for both, arpeggiator and wavetable sequencer, is planned :) Best Regards, Thorsten.

In theory it should be possible to access the card with the planned bridge, but I cannot support this from the software side, since I don't own this card Best Regards, Thorsten.

In theory it should be possible to access the card with the planned bridge, but I cannot support this from the software side, since I don't own this card Best Regards, Thorsten.

Yes, you make it more difficult than it is! ;-) Since you are not sure about the electronic details, my suggestion is that you shouldn't try to left out any component of the core modules in order to avoid trouble. E.g., from the electrical point of view, there is no difference between a master and a slave core (or did I ever write something about this?) - once you've built the modules, you are free to experiment with the setup in order to find the perfect combination. Best Regards, Thorsten.

Yes, you make it more difficult than it is! ;-) Since you are not sure about the electronic details, my suggestion is that you shouldn't try to left out any component of the core modules in order to avoid trouble. E.g., from the electrical point of view, there is no difference between a master and a slave core (or did I ever write something about this?) - once you've built the modules, you are free to experiment with the setup in order to find the perfect combination. Best Regards, Thorsten.

Solange ich die LCDs nicht genauer inspiziert habe, werden Dir die Angaben erstmal nicht viel weiterhelfen, und ich rate davon ab, bereits jetzt eines dieser (kompatiblen) Displays zu ersteigern, weil noch nicht klar ist, ob sie evtl. eine zweite Spannungsversorgung benoetigen. -> LC7981 kompatibel -> T6963c kompatibel -> DMF6104NB-FW (controller noch unbekannt) Es koennte auch durchaus moeglich sein, dass die neuen Driver der beiden oben genannten controller auch mit anderen zusammenspielen - vielleicht sogar mit jedem normal erhaeltlichen graphic LCD, aber darueber mache ich mir wirklich erst Gedanken, wenn die Displays vor mir liegen... bisher habe ich lediglich anhand der Datasheets ueberprueft, ob ein Anschluss an den PIC18F prinzipiell moeglich ist. Gruss, Thorsten.

Hi Lo, thats interesting, the order is not correct? Very strange - in this case the motordriver will not work, as it requires clear fader->motor assignments. Could you please check the order (also of the cables...) again with the AIN DIN DOUT test application? Just change following lines: ;; use 64 pots movlw 64 call MIOS_AIN_NumberSet ;; use the AIN 4051 multiplexers call MIOS_AIN_Muxed must be exchanged by: ;; use 8 faders movlw 8 call MIOS_AIN_NumberSet ;; don't use the AIN 4051 multiplexers call MIOS_AIN_UnMuxed Another important hint: the MF module voltage must be lower than on the PIC16F implementation (ca. 8V) and the AIN deadband value should be <= the MF deadband value. Best Regards, Thorsten.

Hi Lo, thats interesting, the order is not correct? Very strange - in this case the motordriver will not work, as it requires clear fader->motor assignments. Could you please check the order (also of the cables...) again with the AIN DIN DOUT test application? Just change following lines: ;; use 64 pots movlw 64 call MIOS_AIN_NumberSet ;; use the AIN 4051 multiplexers call MIOS_AIN_Muxed must be exchanged by: ;; use 8 faders movlw 8 call MIOS_AIN_NumberSet ;; don't use the AIN 4051 multiplexers call MIOS_AIN_UnMuxed Another important hint: the MF module voltage must be lower than on the PIC16F implementation (ca. 8V) and the AIN deadband value should be <= the MF deadband value. Best Regards, Thorsten.

No, this wasn't an april joke ;-) But forget the wavetable solution, a PIC is not practical for so much data, an old 386, running under Linux, can do this much better. I owned a GUS many years ago, before I bought an AWE. Sure, these were pretty good soundcards with great possibilities, but a real synthesizer is something completely different. Or how do you realize a pulsewidth modulation with a wavetable card? ;-) In the meantime wavetable soundcards can be easily replaced by (free) sampler PlugIns, and in fact it makes more fun to manage all the sounds on a computer and to control the parameters with a common MIDIbox. Best Regards, Thorsten.

No, this wasn't an april joke ;-) But forget the wavetable solution, a PIC is not practical for so much data, an old 386, running under Linux, can do this much better. I owned a GUS many years ago, before I bought an AWE. Sure, these were pretty good soundcards with great possibilities, but a real synthesizer is something completely different. Or how do you realize a pulsewidth modulation with a wavetable card? ;-) In the meantime wavetable soundcards can be easily replaced by (free) sampler PlugIns, and in fact it makes more fun to manage all the sounds on a computer and to control the parameters with a common MIDIbox. Best Regards, Thorsten.

This heavily depends on your planned setup, so which modules should be connected to the cores? Best Regards, Thorsten.

This heavily depends on your planned setup, so which modules should be connected to the cores? Best Regards, Thorsten.

Hi Lo, MIDIbox Link is natively supported by MIOS and is also compatible with the PIC16F implementation :) To enable this function, add following line to the initialization routine: movlw MIOS_MIDI_MERGER_MBLINK_EP call MIOS_MIDI_MergerSet for a MBLink endpoint movlw MIOS_MIDI_MERGER_MBLINK_FP call MIOS_MIDI_MergerSet for a MBLink forwarding point Best Regards, Thorsten.

Hi Lo, MIDIbox Link is natively supported by MIOS and is also compatible with the PIC16F implementation :) To enable this function, add following line to the initialization routine: movlw MIOS_MIDI_MERGER_MBLINK_EP call MIOS_MIDI_MergerSet for a MBLink endpoint movlw MIOS_MIDI_MERGER_MBLINK_FP call MIOS_MIDI_MergerSet for a MBLink forwarding point Best Regards, Thorsten.