Windows, Mac OS X & Linux.
DIN is a standalone application.
The Evaluation version of DIN on Windows and Mac OS X displays a message on startup. The Licensed version does not. You must buy a License if you use any evaluation version of DIN for more than 30 days. To support the DIN tour this is a Lifetime License. That is, you get FREE upgrades and bug fixes for the rest of your life. Once you buy a Lifetime License you are also protected from price increases to the Lifetime License and any changes to the terms of the license.
If you want to use DIN for free, use the GNU/Linux version. Although the GNU/Linux version lags behind Windows and Mac OS X versions, the Bezier curve technology and the instruments available are the same. More importantly, you can find out how DIN works by reading its code and even modify the code to make it do what you want it to do. You cannot do this with DIN on Windows or Mac OS X.
On Mac OS X, download and open the DIN Is Noise disk image. Drag the DIN Is Noise application to your Applications folder and double click on the DIN Is Noise application to start DIN.
On Windows, download and unzip the DIN Is Noise zip file. Enter the DIN Is Noise folder and double click on DIN.exe to start DIN.
On Mac OS X, double click on the DIN Is Noise application in your Applications folder to start DIN.
On Windows, enter the DIN Is Noise folder and double click on DIN.exe to start DIN.
On GNU/Linux, at a terminal type:
dinand press ENTER.
On Windows & Mac OS X, click on the Reset to Factory Settings! button on the Settings page of DIN. And restart DIN.
On GNU/Linux, at a terminal type:
mv ~/.din ~/.dinold and restart DIN.
Yes. On Windows & Mac OS X, click on Settings and choose the MIDI device from which DIN will get its MIDI input. DIN supports MIDI control change, program change, note on & off and pitch bend messages. DIN also automatically syncs FM, AM, gater & octave shift modules to the MIDI clock when it gets a MIDI clock and/or MIDI start message.
Yes. On Windows & Mac OS X, click on Settings and choose the MIDI device from which DIN will get its MIDI input. When MIDI input is available, DIN draws 13 dotted crosses in the middle of the keyboard-keyboard. Each cross represents one note of the chromatic scale. You can see an octave's worth of crosses. If you play a white note on your MIDI keyboard, a white box will appear. If you play a black note, a black box will appear. In both cases, you should hear the note. If not, choose a different MIDI device.
Any mouse with a sensitivity of 400 DPI. Most older mice are fine. Newer gaming mice can be too fast for playing DIN as a mouse / bow instrument - they operate at 800 DPI or more. But thanks to certain kinds of guns in shooting games, many of these mice support on-the-fly DPI switching down to 400 DPI.
However, the sensitivity of your mouse does not matter if you plan to use DIN to work with just drones & Bezier curves.
Press the TAB key. Press the TAB key again or the ESC key to leave the command mode. From DIN's command mode you can invoke DIN commands or run Tcl scripts that contain DIN commands that can change various parameters of DIN.
It is dormant, not dead! I need money to develop DIN on GNU/Linux. So, if you can, please donate. If you know powerful people or companies or organisations that would like to see a truly original piece of music software on GNU/Linux thrive, please ask them to donate. I want to make the GNU/Linux version identical to the proprietary versions of DIN because I want people that cant afford a license to make use of the instrument, study how the instrument works by reading its code and even modify it to make it do what they want it to do. But I dont have the money anymore to make this happen. Still, as it is, DIN on GNU/Linux is 6 years of intense work, the Bezier curve technology is the same, the available instruments are the same and there is plenty to see and hear! If you wish, you could also download the entire source code of DIN and develop DIN on your own.
You built DIN from source code but ran it from /path-to-din/src directory instead of doing a sudo make install. Please read README to learn how to build DIN from source code.
rm -rf ~/.dinwill delete these older files and do a fresh install of data files to clear this problem!
Yes because DIN uses OpenGL to draw its user interface. For best performance, install hardware accelerated OpenGL drivers from your graphics card manufacturer (eg., Intel, ATI, & NVIDIA). Drivers from ATI & NVIDIA are proprietary. Nouveau is an open source alternative for NVIDIA card users.
If you are compiling DIN from source code, check if you have OpenGL development files:
If you use Ubuntu and install DIN from packages,
the installation will go fine but check if you have hardware accelerated OpenGL drivers:
Do you see red, green & blue gears rotating? Yes? Good. At least some kind of OpenGL is installed :) Do you also see a good number (say in the thousands or tens of thousands!) for Frame per Second (FPS)? Yes? Very Good :) You seem to have hardware accelerated OpenGL drivers installed!
No?! How about:
Did a bunch of lines just scroll past you? No??!! There is no OpenGL on your computer...
The JACK server is not running. Try:
jackd -R -d alsa -s -r 44100 -X seq
If JACK fails to start, check if another program (eg., Firefox playing a video or sound) has grabbed your sound card. Quit this program & try again.
If that fails too, did you install the JACK server? On Ubuntu or similar try:
sudo apt-get install jackd
The JACK server is auto configured but keep the JACK FAQ handy.
This is usually because you have not installed the hardware accelerated OpenGL drivers from your graphics card manufacturer. Check the CPU usage when DIN is running. If it is high, you have software OpenGL drivers. If it is low, you have hardware OpenGL drivers. If you have hardware OpenGL drivers and DIN still crackles & glitches, disable vertical synchronisation to monitor refresh rate. The monitor refresh rate is usually 60 frames per second so if JACK audio buffer size is less than 1024 samples, DIN cant draw the UI and fill the audio buffer fast enough so ... havoc!
If you started the JACK server with:
jackd -R -d alsa -s -r 44100 -X seq
The latency will be 23.2 milliseconds. This means DIN reads your mouse (x, y & buttons) and keyboard 43 times every second. If you
moved the mouse from note C to D to E on the microtonal keyboard in under 1/43rd of a second, DIN would not sound the note D. Are you that fast? If you
jackd -R -d alsa -s -r 44100 -X seq -n 2 -p 128
The latency will now be 2.90 milliseconds. DIN now reads your mouse and keyboard 344 times every second. But the sound may glitch or crackle or not - depends on the computer you are running DIN on and the load it is under apart from din.
Yes. In command mode:
set-var auto_connect_outputs 0 <-- long form
sv aco 0 <-- short form
Now restart din. DIN will no longer connect to system audio outputs.
WARNING: You wont hear any sound from DIN until you do! To restore:
set-var auto_connect_outputs 1 <-- long form
sv aco 1 <-- short form
And restart DIN.