MIDIbox

User Tools

Site Tools

Trace:
frequently_asked_questions_faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
frequently_asked_questions_faq [2016/06/10 14:34] – [MIDIbox in Use.] psykhazefrequently_asked_questions_faq [2016/06/10 14:41] (current) – psykhaze
Line 1: Line 1:
 ====== General Frequently Asked Questions (FAQ) ====== ====== General Frequently Asked Questions (FAQ) ======
 +
 +//FIXME Some updates needed out there//
  
 This page summarizes the most frequently asked questions concerning the projects found on the [[http://www.uCApps.de]] website. It will be enhanced with every new interesting questions and will be modified with every new awareness. Feel free to ask in questions in the MIDIbox forum [[http://forum.midibox.org]] or edit this document by yourself if you are missing an important question, don't understand an answer or if you found a better solution in order to improve this "living document". This page summarizes the most frequently asked questions concerning the projects found on the [[http://www.uCApps.de]] website. It will be enhanced with every new interesting questions and will be modified with every new awareness. Feel free to ask in questions in the MIDIbox forum [[http://forum.midibox.org]] or edit this document by yourself if you are missing an important question, don't understand an answer or if you found a better solution in order to improve this "living document".
Line 35: Line 37:
 Having said that, if you feel you're up to the challenge, you're encouraged to tinker around :) Having said that, if you feel you're up to the challenge, you're encouraged to tinker around :)
  
 +===== Forum / Wiki / Web =====
  
 +  * **I can't log into the forum!**
  
  
 +Possibly you are using the M$ Internet Explorer which prevents YaBB from saving "cookies" within a frame which contains content from another domain (midibox.org). In this case click on the "Forum (unframed)" link instead, or (better) change your internet browser - see also [[http://www.heise.de/security/dienste/browsercheck/demos/ie/]]
  
 +  * **I can't log into the Wiki!**
 +
 +Make sure you have cookies turned on in your browser.  As of May 13, 2006, at least one browser will not log in to the Wiki:  Camino 1.0.1 for Mac.  (Please add to this list if you find a browser that won't log in to the Wiki)
  
 ===== Building Your MIDIbox ===== ===== Building Your MIDIbox =====
Line 143: Line 151:
   * **I've burned the bootstrap loader into the PIC, but my LCD doesn't show any message?**   * **I've burned the bootstrap loader into the PIC, but my LCD doesn't show any message?**
 See [[lcd]] page for more information incl. troubleshooting of LCDs See [[lcd]] page for more information incl. troubleshooting of LCDs
- 
- 
- 
- 
- 
- 
-===== The PIC Microcontroller ===== 
- 
- 
-  * **Why are you using the PIC and not a more modern Microcontroller?** 
-TK: "I started my first MIDI projects in the 80's with a C64, later I worked with 8051 derivatives. Sometime along the way I decided to use a PIC controller because it *was* modern during many years - cheap, easy to program, almost non-destroyable, no SMD package, high availability for hobbyists. Although I have worked with a lot of 16 and 32 bit controllers in the meantime (job-related...), I stick to the lovely PICs in order to reduce my support effort for these sparetime projects. 
- 
- 
-  * **Do I need a deep knowledge of PIC microcontrollers in order to build your applications? ** 
-No! The software is ready made, normaly you don't need to assemble code, you just only have to burn the application (.syx file) into the PIC via the MIOS Bootstrap Loader [[http://www.ucapps.de/mios_bootstrap.html]]. 
-If the application provides software/hardware options, which are not part of the preassembled binary, you have to edit them in the main.asm file of the application package (therefore it always make sense to take a look into this file) and rebuild the application like described under [[http://www.ucapps.de/howto_tools_gpasm.html]] 
- 
-  * **Where can I learn more about PIC microcontrollers?** 
-Get all the interesting datasheets and application notes from the [[http://www.microchip.com]] website and check the famous [[http://www.piclist.com]] site. 
- 
- 
-  * **How do you develop your applications? ** 
-Update: Please see the [[application_development|Application Development]] page for new info!\\ 
-\\ 
-TK's answer, edited to remove references to MPLab which is now obsolete:\\ 
-Mostly I develop under Linux. I'm using XEmacs [[http://www.xemacs.org]] to edit the source, GPUtils to assemble the code and the MIOS bootstrap loader [[http://www.ucapps.de/mios_bootstrap.html]] to upload the application into the PIC.  
- 
-If I have to work under Windows (i.e. for making music with Logic [[http://www.emagic.de]] and Reaktor [[http://www.native-instruments.de]], I'm using the Windows version of Emacs [[http://www.gnu.org/software/emacs/windows/ntemacs.html]] and GPUtils to assemble the code. 
-Find a snapshot of my development environment under Linux here: [[http://www.ucapps.de/images/devl_env.gif]] 
- 
-It is also possible to develop on the mac, see [[how to use Xcode2 as IDE on a Mac]] 
- 
- 
-  * **Where can I download the source code?** 
-It's part of every application package: [[http://www.ucapps.de/mios_download.html]] 
- 
- 
-===== Buying and Selling MIDIbox stuff ===== 
-  * **Where can I buy your stuff?** 
-TK: "All the applications of [[http://www.uCApps.de]] are non-profit projects which are not for sale. The purpose is to follow the spirit of Open Source in order to allow people to rebuild, modify, improve or just learn from my projects. Many features that can be found here are not my inventions, but suggested by users from all of the world. On this way *we* are creating what *we* have ever searched for and I myself can enhance my experience with electronics and MIDI (makes really fun! :)" 
- 
-  * **Would you build a MIDIbox for me if I give you some money?** 
-TK: "I neither have the time, nor the motivation to build MIDIboxes for other peoples. These are DIY projects, that means: Do-It-Yourself. Just ask a friend or an expert in your neighbourhood for help." 
- 
-stryd_one: "If you don't have time to solder a little, you sure won't have time to use a synth to make music." 
- 
-  * **As everything is free, am I allowed to bring the stuff to market?** 
-Only under special circumstances. See also [[http://www.midibox.org/forum/index.php?topic=5758.0|this forum article]]. 
- 
  
 ===== MIDIbox in Use. ===== ===== MIDIbox in Use. =====
Line 214: Line 173:
  
 Both alternative solutions are not recommended for MIDIbox SID or FM due to the missing optocoupler. Both alternative solutions are not recommended for MIDIbox SID or FM due to the missing optocoupler.
-==== What is the meaning of this funny hexadecimal numbers? ==== +  * ** What is the meaning of this funny hexadecimal numbers? **
  
 That are the MIDI messages which will be send over the MIDI interface. That are the MIDI messages which will be send over the MIDI interface.
Line 230: Line 188:
  
  
-  - ==== Which MIDI events can I send with the MIDIbox? ====+  * **Which MIDI events can I send with the MIDIbox?**
 In fact MIOS can send any MIDI data, it only depends on the application which events can be configured without additional programming effort. E.g., with MIDIbox64/MIDIbox64E/MIDIO128 you are able to send Note/Controller/Aftertouch/Pitch Bender/Program Change Events by default. The events can be configured via the MIDI Learn function or via MIDI dumps. SysEx Streams, NRPN events, multiple events or whatever can be implemented via Meta Events. In fact MIOS can send any MIDI data, it only depends on the application which events can be configured without additional programming effort. E.g., with MIDIbox64/MIDIbox64E/MIDIO128 you are able to send Note/Controller/Aftertouch/Pitch Bender/Program Change Events by default. The events can be configured via the MIDI Learn function or via MIDI dumps. SysEx Streams, NRPN events, multiple events or whatever can be implemented via Meta Events.
  
  
-  - ==== How high is the latency of MIOS? ====+  * **How high is the latency of MIOS?**
 First of all it should be noted, that the latency of a common MIOS application is negligible compared to the latency of a computer. MIOS is a real-time system which runs on a dedicated microcontroller. The reaction time of the low-level drivers is deterministic, calculable and ensured. The design focus was on MIDI controllers, therefore the processor load caused by tasks running in background has to be measured against the initial latency caused by the MIDI transfer protocol. First of all it should be noted, that the latency of a common MIOS application is negligible compared to the latency of a computer. MIOS is a real-time system which runs on a dedicated microcontroller. The reaction time of the low-level drivers is deterministic, calculable and ensured. The design focus was on MIDI controllers, therefore the processor load caused by tasks running in background has to be measured against the initial latency caused by the MIDI transfer protocol.
  
Line 253: Line 211:
 MIOS MIDI Benchmark:  [[http://www.midibox.org/forum/index.php?topic=2342.0]] MIOS MIDI Benchmark:  [[http://www.midibox.org/forum/index.php?topic=2342.0]]
  
-  * ==== What the hell are Double-Note-Events? ====+  * **What the hell are Double-Note-Events?**
 Programs like Cakewalk, Cubase, Logic, ... support MIDI remote, which allows the user to control the software with his MIDI keyboard or something similar. Normaly MIDI remote works in a manner, that one note has to be played to enable MIDI remote (->"Shift" key), and another note at the same time to trigger a function like Play, Record, Pause, Forward, Rewind and much more. Programs like Cakewalk, Cubase, Logic, ... support MIDI remote, which allows the user to control the software with his MIDI keyboard or something similar. Normaly MIDI remote works in a manner, that one note has to be played to enable MIDI remote (->"Shift" key), and another note at the same time to trigger a function like Play, Record, Pause, Forward, Rewind and much more.
  
Line 259: Line 217:
  
 These codes have to be defined in your MIDIbox initialization file, see also [[http://www.ucapps.de/midibox/mk_syx.zip]] These codes have to be defined in your MIDIbox initialization file, see also [[http://www.ucapps.de/midibox/mk_syx.zip]]
- 
- 
- 
- 
- 
  
 ===== Customize your MIDIbox ===== ===== Customize your MIDIbox =====
Line 270: Line 223:
  
  
-  * ==== How many pots/ faders/ buttons/ encoders/ screens/ LED's/ etc is the maximum that I can connect? ====+  * **How many pots/ faders/ buttons/ encoders/ screens/ LED's/ etc is the maximum that I can connect? **
  
 There are two parts to this answer. The first relates to the standard hardware, the second is related to the implementation of that hardware. There are two parts to this answer. The first relates to the standard hardware, the second is related to the implementation of that hardware.
Line 312: Line 265:
   * IIC buss can be used to connect other IC's to the Core   * IIC buss can be used to connect other IC's to the Core
  
- +  * ** Can I use PWM to control individual LED brightness ?**
- +
- +
- +
-  - ==== Can I use PWM to control individual LED brightness ?====+
 The short answer is that using PWM on DOUT to do individual brightness control on a large number of LEDs is not possible as it would overload the Core. The short answer is that using PWM on DOUT to do individual brightness control on a large number of LEDs is not possible as it would overload the Core.
  
Line 328: Line 277:
  
  
-  - ==== Can I connect other parts aside from pots to the analog inputs? ====+  * **Can I connect other parts aside from pots to the analog inputs?**
 Yes, you can connect anything which delivers a voltage between 0 and +5V like additional buttons, CV outputs of antique synthesizer equipment, or just external effect units like LFOs, see the [[http://www.ucapps.de/midibox_ext.html|MIDIBox Extensions]] page. Yes, you can connect anything which delivers a voltage between 0 and +5V like additional buttons, CV outputs of antique synthesizer equipment, or just external effect units like LFOs, see the [[http://www.ucapps.de/midibox_ext.html|MIDIBox Extensions]] page.
  
Line 334: Line 283:
  
  
-  - ==== How do I add a MIDI Thru Port? ====+  * **How do I add a MIDI Thru Port?**
 Find the circuit under [[http://www.ucapps.de/midibox/midi_thru.gif]] - the 74HC00 is used to amplify the received MIDI signal. The MIDI Thru Port will not work without this amplifier. Find the circuit under [[http://www.ucapps.de/midibox/midi_thru.gif]] - the 74HC00 is used to amplify the received MIDI signal. The MIDI Thru Port will not work without this amplifier.
  
Line 340: Line 289:
  
  
-  - ==== Can I power a PIC from the MIDI line without additional power supply? ====+  * **Can I power a PIC from the MIDI line without additional power supply? **
 Thats very problematic and mostly doesn't work properly - the MIDI specification doesn't take this into account. The MIDI line is specified as current loop, and the maximum voltage level is not defined. Most interfaces deliver a logic signal with TTL level between 0V and 5V, a 7805 regulator between MIDI Out and Thats very problematic and mostly doesn't work properly - the MIDI specification doesn't take this into account. The MIDI line is specified as current loop, and the maximum voltage level is not defined. Most interfaces deliver a logic signal with TTL level between 0V and 5V, a 7805 regulator between MIDI Out and
 the PIC power pins would reduce the voltage to <4V, so it should not be used in this case. Instead the ground pin and one of the outer pins which always supplies 5V (has to be checked with a measuring instrument) should be connected directly to J2 (behind the PIC power pins would reduce the voltage to <4V, so it should not be used in this case. Instead the ground pin and one of the outer pins which always supplies 5V (has to be checked with a measuring instrument) should be connected directly to J2 (behind
Line 351: Line 300:
  
  
 +===== The PIC Microcontroller =====
  
  
 +  * **Why are you using the PIC and not a more modern Microcontroller?**
 +TK: "I started my first MIDI projects in the 80's with a C64, later I worked with 8051 derivatives. Sometime along the way I decided to use a PIC controller because it *was* modern during many years - cheap, easy to program, almost non-destroyable, no SMD package, high availability for hobbyists. Although I have worked with a lot of 16 and 32 bit controllers in the meantime (job-related...), I stick to the lovely PICs in order to reduce my support effort for these sparetime projects.
  
  
 +  * **Do I need a deep knowledge of PIC microcontrollers in order to build your applications? **
 +No! The software is ready made, normaly you don't need to assemble code, you just only have to burn the application (.syx file) into the PIC via the MIOS Bootstrap Loader [[http://www.ucapps.de/mios_bootstrap.html]].
 +If the application provides software/hardware options, which are not part of the preassembled binary, you have to edit them in the main.asm file of the application package (therefore it always make sense to take a look into this file) and rebuild the application like described under [[http://www.ucapps.de/howto_tools_gpasm.html]]
  
 +  * **Where can I learn more about PIC microcontrollers?**
 +Get all the interesting datasheets and application notes from the [[http://www.microchip.com]] website and check the famous [[http://www.piclist.com]] site.
  
  
-===== Forum / Wiki / Web =====+  * **How do you develop your applications? ** 
 +Update: Please see the [[application_development|Application Development]] page for new info!\\ 
 +\\ 
 +TK's answer, edited to remove references to MPLab which is now obsolete:\\ 
 +Mostly I develop under Linux. I'm using XEmacs [[http://www.xemacs.org]] to edit the source, GPUtils to assemble the code and the MIOS bootstrap loader [[http://www.ucapps.de/mios_bootstrap.html]] to upload the application into the PIC. 
  
-  - ==== I can't log into the forum ====+If I have to work under Windows (i.e. for making music with Logic [[http://www.emagic.de]] and Reaktor [[http://www.native-instruments.de]], I'm using the Windows version of Emacs [[http://www.gnu.org/software/emacs/windows/ntemacs.html]] and GPUtils to assemble the code. 
 +Find a snapshot of my development environment under Linux here: [[http://www.ucapps.de/images/devl_env.gif]] 
 + 
 +It is also possible to develop on the mac, see [[how to use Xcode2 as IDE on a Mac]] 
 + 
 + 
 +  * **Where can I download the source code?** 
 +It's part of every application package: [[http://www.ucapps.de/mios_download.html]] 
 + 
 + 
 +===== Buying and Selling MIDIbox stuff ===== 
 +  * **Where can I buy your stuff?** 
 +TK: "All the applications of [[http://www.uCApps.de]] are non-profit projects which are not for sale. The purpose is to follow the spirit of Open Source in order to allow people to rebuild, modify, improve or just learn from my projects. Many features that can be found here are not my inventions, but suggested by users from all of the world. On this way *we* are creating what *we* have ever searched for and I myself can enhance my experience with electronics and MIDI (makes really fun! :)" 
 + 
 +  * **Would you build a MIDIbox for me if I give you some money?** 
 +TK: "I neither have the time, nor the motivation to build MIDIboxes for other peoples. These are DIY projects, that means: Do-It-Yourself. Just ask a friend or an expert in your neighbourhood for help." 
 + 
 +stryd_one: "If you don't have time to solder a little, you sure won't have time to use a synth to make music." 
 + 
 +  * **As everything is free, am I allowed to bring the stuff to market?** 
 +Only under special circumstances. See also [[http://www.midibox.org/forum/index.php?topic=5758.0|this forum article]].
  
  
-Possibly you are using the M$ Internet Explorer which prevents YaBB from saving "cookies" within a frame which contains content from another domain (midibox.org). In this case click on the "Forum (unframed)" link instead, or (better) change your internet browser - see also [[http://www.heise.de/security/dienste/browsercheck/demos/ie/]] 
  
-  - ==== I can't log into the Wiki ==== 
  
-Make sure you have cookies turned on in your browser.  As of May 13, 2006, at least one browser will not log in to the Wiki:  Camino 1.0.1 for Mac.  (Please add to this list if you find a browser that won't log in to the Wiki) 
frequently_asked_questions_faq.1465569265.txt.gz · Last modified: 2016/06/10 14:34 by psykhaze