Changes between Version 2 and Version 3 of IngenGettingStarted


Ignore:
Timestamp:
Nov 25, 2008, 11:32:53 AM (13 years ago)
Author:
David Robillard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IngenGettingStarted

    v2 v3  
    11== Running Ingen ==
    22
    3 === GUI ===
    43
    5 If you want to run the GUI it should already be present in your desktop's application menu (or equivalent).  If not, you can simply run it yourself: `ingen -g`
     4=== Monolithic (Engine and GUI in one process) ===
    65
    7 You will be presented with a dialog which lets you start your Ingen session.  Because Ingen itself is a modular system, there are a few different ways you can use the system.  Assuming you don't already have an Ingen server running, the relevant options are to run with an internal engine, or launch a server daemon and connect to that.  The internal engine has less overhead, but running a separate server is much more stable (no matter what happens to the GUI the audio side of things will continue working).  Running with a separate server is highly recommended if you're running Ingen out of SVN.
     6If you want to simply run Ingen as a graphical application it should already be present in your desktop's application menu (or equivalent).  If not, you can simply run it yourself: {{{ingen -eg}}}
    87
    9 Your machine's network settings may be configured incorrectly which can cause problems.  Running an internal engine will work around this, but ''please'' report the issue regardless in case it's actually an Ingen bug that can be fixed.
     8A window should show up containing the root patch, which will be empty since you just started ingen.
    109
    1110
    12 === Running your own server ===
     11=== Running an ingen server ===
    1312
    14 If you're doing something a little more interesting, you might want to run an Ingen server yourself and control it via OSC.  Simply run `ingen` and the server will launch on the default port.  To run on a specific port (or do anything else that isn't the default behaviour) see the output of `ingen --help`
     13''' NOTE: Running a separate engine is currently/temporarily not supported.  Use ingen -eg only! '''
     14
     15If you're doing something a little more interesting, you might want to run an Ingen server yourself and control it via OSC.  Simply run {{{ingen -e}}} and the server will launch on the default port, 16180.  To run on a specific port (or do anything else that isn't the default behaviour) see the output of {{{ingen --help}}}
    1516
    1617
    1718=== Running from a source tree ===
    1819
    19 It isn't necessary to install Ingen to have it run.  If you wish to run from the source tree, switch to the directory {{{
    20 src/procs/ingen
    21 }}}
    22 and run ingen.dev (to just execute ingen) or ingen.dbg (to execute ingen in the debugger).
     20''' NOTE: Running from the source tree is currently/temporarily not supported.  You must install! '''
     21
     22It isn't necessary to install Ingen to have it run.  If you wish to run from the source tree, switch to the directory {{{src/procs/ingen}}} and run ingen.dev (to just execute ingen) or ingen.dbg (to execute ingen in the debugger).
    2323
    2424=== What's next? ===