diff --git a/Makefile b/Makefile index 119872b..7f373cb 100644 --- a/Makefile +++ b/Makefile @@ -35,9 +35,9 @@ config: -include .config -export SYSTEM_PATH:=$(prefix)/share/non-daw/ -export DOCUMENT_PATH:=$(prefix)/share/doc/non-daw/ -export PIXMAP_PATH:=$(prefix)/share/pixmaps/non-daw/ +export SYSTEM_PATH:=$(prefix)/share/ +export DOCUMENT_PATH:=$(prefix)/share/doc/ +export PIXMAP_PATH:=$(prefix)/share/pixmaps/ # a bit of a hack to make sure this runs before any rules ifneq ($(CALCULATING),yes) @@ -119,9 +119,12 @@ install: all @ echo -n "Installing..." @ install Timeline/timeline $(prefix)/bin/non-daw @ install Mixer/mixer $(prefix)/bin/non-mixer - @ mkdir -p $(SYSTEM_PATH) - @ mkdir -p $(PIXMAP_PATH) - @ cp pixmaps/*.png $(PIXMAP_PATH) + @ mkdir -p $(SYSTEM_PATH)/non-daw + @ mkdir -p $(PIXMAP_PATH)/non-daw + @ mkdir -p $(SYSTEM_PATH)/non-mixer + @ mkdir -p $(PIXMAP_PATH)/non-mixer + @ cp pixmaps/non-mixer/*.png $(PIXMAP_PATH)/non-mixer + @ cp pixmaps/non-daw/*.png $(PIXMAP_PATH)non-daw @ $(MAKE) -s -C doc install @ echo "$(DONE)" ifneq ($(USE_DEBUG),yes) diff --git a/Timeline/TLE.fl b/Timeline/TLE.fl index 213e871..c98d114 100644 --- a/Timeline/TLE.fl +++ b/Timeline/TLE.fl @@ -890,7 +890,7 @@ Fl::check();} {} } { code {char pat[256]; -snprintf( pat, 256, "file://%s%s.html", DOCUMENT_PATH, file ); +snprintf( pat, 256, "file://%s/non-daw/%s.html", DOCUMENT_PATH, file ); open_url( pat );} {} } @@ -966,7 +966,7 @@ if ( logo_box->image() ) Fl_Box logo_box { label {} private xywh {51 180 418 235} box ROUNDED_BOX color 53 labelfont 1 labelsize 18 align 16 - code0 {o->image( Fl_Shared_Image::get( INSTALL_PREFIX "/share/pixmaps/non-daw/logo2.png" ) );} + code0 {o->image( Fl_Shared_Image::get( PIXMAP_PATH "non-daw/logo2.png" ) );} code1 {o->label( NULL );} } Fl_Text_Editor notes_field { diff --git a/doc/Makefile b/doc/Makefile index cddf39c..ba9e707 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -1,6 +1,11 @@ +NM_SRCS=$(wildcard non-mixer/*.mu) SRCS=$(wildcard *.mu) +ND_SRCS=$(wildcard non-daw/*.mu) + OBJS=$(SRCS:.mu=.html) +NM_OBJS=$(NM_SRCS:.mu=.html) +ND_OBJS=$(ND_SRCS:.mu=.html) %.html: %.mu @ echo Mupping $<... @@ -16,9 +21,11 @@ upload: all @ rm -f index.html install: - @ mkdir -p $(DOCUMENT_PATH) - @ cp $(OBJS) *.png mup.css ../COPYING $(DOCUMENT_PATH) - @ ln -sf $(PIXMAP_PATH)/logo.png $(DOCUMENT_PATH) + @ mkdir -p $(DOCUMENT_PATH)/non-daw + @ mkdir -p $(DOCUMENT_PATH)/non-mixer + @ cp $(ND_OBJS) non-daw/*.png non-daw/mup.css ../COPYING $(DOCUMENT_PATH)/non-daw + @ cp $(NM_OBJS) non-mixer/*.png non-mixer/mup.css ../COPYING $(DOCUMENT_PATH)/non-mixer +# @ ln -sf $(PIXMAP_PATH)/logo.png $(DOCUMENT_PATH) clean: - rm -f $(OBJS) + rm -f $(OBJS) $(NM_OBJS) $(ND_OBJS) diff --git a/doc/OVERVIEW.html b/doc/OVERVIEW.html index 9487191..860d1c7 100644 --- a/doc/OVERVIEW.html +++ b/doc/OVERVIEW.html @@ -47,6 +47,8 @@ March 1, 2008
  • What does freedom have to do with this software?
  • Donations @@ -64,7 +66,7 @@ March 1, 2008
    The Non DAW is a powerful, reliable and fast modular Digital Audio Workstation system, released under the GNU General Public License (GPL). It utilizes the JACK Audio Connection Kit for inter-application audio I/O and the FLTK GUI toolkit for a fast and lightweight user interface.

    -Please see the manual for more information. +Please see the Non DAW Manual and Non Mixer Manual for more information.

    1.2. What it is not

    @@ -80,7 +82,7 @@ In this author's opinion, a DAW comprises the following functionality:

    -Since Non uses JACK for IO, some things traditionally considered to be within the scope of a monolithic DAW can be pared out: +Since Non uses JACK for IO, some things traditionally considered to be within the scope of a monolithic DAW can be pared out into JACK and Non Mixer:


    +

    1. User Manual

    +

    1.1. The Mixer

    +
    + + + +
    +Fig. 1.1. Mixer +
    fig. 1.1
    +

    +The Non-Mixer is a stand-alone audio mixer, utilizing JACK as an audio subsystem. At the time of writing, the architecture of Non-Mixer is unique. By making the mixer stand-alone, concepts such as busses, sends, and inserts are eliminated, as the same goals can be achieved by simply adding more strips to the mixer. +

    +

    +Start by creating a new project. +

    +
    + + + +
    +Fig. 1.2. New Project +
    fig. 1.2
    +

    +

    1.1.1. Mixer Strip

    +
    + + + +
    +Fig. 1.3. Mixer Strip +
    fig. 1.3
    +

    +Each mixer strip has a name and color, each of which may be defined by the user. Names, but not colors, must be unique. In addition, each strip has controls to move it left or right (the arrows) in the display and to remove it entirely (the 'X'). +

    +

    +Strips start out in narrow mode, with the fader view enabled. Click the desired button to toggle the mode or view. +

    +

    +The fader view comprises a large gain control and digital peak meter indicator. These are automatically connected to the default gain and meter modules of the strips signal chain. +

    +

    +To see how an audio signal traveling through this strip will be processed, switch to its signal view. +

    +

    1.1.1.1. Signal Processing

    +
    1.1.1.1.1. Signal Chain
    +

    +The signal chain view of a mixer strip provides a way to view and manipulate the signal processing of a mixer strip. +

    +
    1.1.1.1.1.1. Modules
    +
    + + + +
    +Fig. 1.4. Modules +
    fig. 1.4
    +

    +All signal processing in Non Mixer occurs in Modules. Modules are +

    +

    +

    +Modules are displayed as named blocks. Some modules may have additional GUI components. +

    +

    +

    +An indicator in the upper left-hand corner of each module block indicates whether the module has any parameters bound to controls. +

    +

    +Non Mixer has several built-in modules. They are: +

    +
    +
    JACK
    +
    Performs JACK I/O
    +
    Gain
    +
    Applies gain in dB
    +
    Meter
    +
    Digital Peak meter
    +
    Mono Pan
    +
    Performs intensity panning of a mono signal into a stereo signal.
    +
    Plugin
    +
    Hosts a LADSPA plugin
    +
    +

    +Left-clicking on a module brings up the Module Parameter Editor. +

    +

    +Shift+Left-clicking on a module brings up a menu which allows you to pick a new module to insert before this one in the chain. +

    +

    +Control+Right-clicking on a module causes it to be removed from the chain (modules added by default cannot be removed). +

    +1.1.1.1.1.1.1. Module Parameter Editor +
    + + + +
    +Fig. 1.5. Module Parameter Editor +
    fig. 1.5
    +

    +The Module Parameter Editor is used to alter the values of a module's parameters, and, further more, to bind its parameters to controls. A menu button in the upper left-hand corner allows you to select between knob, vertical slider and horizontal slider controls. +

    +
    + + + +
    +Fig. 1.6. Horizontal Sliders +
    fig. 1.6
    +
    + + + +
    +Fig. 1.7. Vertical Sliders +
    fig. 1.7
    +

    +Underneath each control is a bind button. Clicking adds a new control to the chain's Controls view and binds it to the parameter in question. For simplicity, only one control at a time may be bound to a given parameter. +

    +1.1.1.1.1.1.2. Controls +
    + + + +
    +Fig. 1.8. Control View +
    fig. 1.8
    +

    +

    + +
    NOTE: +All knob and slider controls respond to mousewheel +events. Hold down the `Ctrl` key while scrolling the mousewheel to +achieve finer resolution. +
    +
    +

    1.1.1.2. JACK I/O

    +

    +Each mixer strip is presented as a separate JACK "client". This helps to avoid the necessity of internally duplicating JACK's routing logic and, with JACK2, permits the possibility of parallel execution of mixer strip signal chains. +

    +

    +The JACK client name of each strip will correspond to the name of the strip. +

    +
    + +
    NOTE: +The JACK API makes implementing this far more difficult and kludgey than it should have to be. +Please petition your local JACK developer to accept jack_client_set_name() into the API. +
    +
    +
    + + + +
    +Fig. 1.9. Patchage +
    fig. 1.9
    + + + diff --git a/doc/non-mixer/MANUAL.mu b/doc/non-mixer/MANUAL.mu new file mode 100644 index 0000000..933cb3c --- /dev/null +++ b/doc/non-mixer/MANUAL.mu @@ -0,0 +1,159 @@ + +! title Non Mixer User Manual +! author Jonathan Moore Liles #(email,male@tuxfamily.org) +! date January 21, 2010 + +-- Table Of Contents + +: User Manual + +:: The Mixer + +/ Mixer +< non-mixer-complex.png + + The Non-Mixer is a stand-alone audio mixer, utilizing JACK as an + audio subsystem. At the time of writing, the architecture of + Non-Mixer is unique. By making the mixer stand-alone, concepts such + as busses, sends, and inserts are eliminated, as the same goals can + be achieved by simply adding more strips to the mixer. + + Start by creating a new project. + +/ New Project +< new-project.png + + After the project has been created. Hit `a` or choose `Mixer/Add + Strip` from the menu to add a new strip to the mixer. + +::: Mixer Strip + +/ Mixer Strip +< single-strip.png + + Each mixer strip has a name and color, each of which may be defined + by the user. Names, but not colors, must be unique. In addition, + each strip has controls to move it left or right (the arrows) in the + display and to remove it entirely (the 'X'). + + Strips start out in /narrow/ mode, with the /fader/ view + enabled. Click the desired button to toggle the mode or view. + + The fader view comprises a large gain control and digital peak meter + indicator. These are automatically connected to the default gain and + meter modules of the strips signal chain. + + To see how an audio signal traveling through this strip will be + processed, switch to its /signal/ view. + +:::: Signal Processing + + +::::: Signal Chain + + The signal chain view of a mixer strip provides a way to view and + manipulate the signal processing of a mixer strip. + +:::::: Modules + +/ Modules +< modules.png + + All signal processing in Non Mixer occurs in /Modules/. Modules are + + signal processing abstractions providing ports for audio and control + I/O and, in addition, some simple user interface. Sink and source + modules carry audio out of and into JACK. + + Modules are displayed as named blocks. Some modules may have + additional GUI components. + + Each module has zero or more audio I/O ports and zero or more + control ports. Audio routing between modules is handled + automatically. Modules with mono audio configurations (one channel + in, one channel out) can be automatically adjusted to support any + number of discrete channels. Modules with more (related) channels, + however, introduce restrictions on the order in which modules can be + chained. + + An indicator in the upper left-hand corner of each module block + indicates whether the module has any parameters bound to controls. + + Non Mixer has several built-in modules. They are: + += JACK + = Performs JACK I\/O += Gain + = Applies gain in dB += Meter + = Digital Peak meter += Mono Pan + = Performs intensity panning of a mono signal into a stereo signal. += Plugin + = Hosts a LADSPA plugin + + Left-clicking on a module brings up the Module Parameter Editor. + + Shift+Left-clicking on a module brings up a menu which allows you to + pick a new module to insert before this one in the chain. + + Control+Right-clicking on a module causes it to be removed from the + chain (modules added by default cannot be removed). + +::::::: Module Parameter Editor + +/ Module Parameter Editor +< gverb-parameters-knobs.png + + The Module Parameter Editor is used to alter the values of a + module's parameters, and, further more, to bind its parameters to + controls. A menu button in the upper left-hand corner allows you to + select between knob, vertical slider and horizontal slider controls. + +/ Horizontal Sliders +< gverb-parameters-hsliders.png + +/ Vertical Sliders +< gverb-parameters-vsliders.png + + Underneath each control is a bind button. Clicking adds a new + control to the chain's /Controls/ view and binds it to the parameter + in question. For simplicity, only one control at a time may be bound + to a given parameter. + +::::::: Controls + +/ Control View +< controls.png + + The control view of a chain groups together all of the controls + bound to parameters of modules in that chain. The default mode of + controls is /Manual/. Right click on a control to bring up a menu + which will allow you to select one of the available control I/O + methods to use. When /Control Voltage/ (CV) is selected, a CV input + port will be created on the containing mixer strip's JACK + client. The control will now accept values from that input. A + control bound and configured in this way can then be connected to + the output of Non-DAW a control sequence using your favorite + connection manager. + +{ NOTE: +{ All knob and slider controls respond to mousewheel +{ events. Hold down the `Ctrl` key while scrolling the mousewheel to +{ achieve finer resolution. + +:::: JACK I/O + + Each mixer strip is presented as a separate JACK "client". This + helps to avoid the necessity of internally duplicating JACK's + routing logic and, with JACK2, permits the possibility of parallel + execution of mixer strip signal chains. + + The JACK client name of each strip will correspond to the name of the strip. + +{ NOTE: +{ The JACK API makes implementing this far more difficult and kludgey than it should have to be. +{ Please petition your local JACK developer to accept jack_client_set_name() into the API. + +/ Patchage +< non-mixer-and-non-daw-in-patchage.png diff --git a/doc/non-mixer/controls.png b/doc/non-mixer/controls.png new file mode 100644 index 0000000..f9f6d1d Binary files /dev/null and b/doc/non-mixer/controls.png differ diff --git a/doc/non-mixer/gverb-parameters-hsliders.png b/doc/non-mixer/gverb-parameters-hsliders.png new file mode 100644 index 0000000..7926b8c Binary files /dev/null and b/doc/non-mixer/gverb-parameters-hsliders.png differ diff --git a/doc/non-mixer/gverb-parameters-knobs.png b/doc/non-mixer/gverb-parameters-knobs.png new file mode 100644 index 0000000..e2bb4e1 Binary files /dev/null and b/doc/non-mixer/gverb-parameters-knobs.png differ diff --git a/doc/non-mixer/gverb-parameters-vsliders.png b/doc/non-mixer/gverb-parameters-vsliders.png new file mode 100644 index 0000000..3ddad3d Binary files /dev/null and b/doc/non-mixer/gverb-parameters-vsliders.png differ diff --git a/doc/non-mixer/mixer-strips.png b/doc/non-mixer/mixer-strips.png new file mode 100644 index 0000000..f69a9a2 Binary files /dev/null and b/doc/non-mixer/mixer-strips.png differ diff --git a/doc/non-mixer/modules.png b/doc/non-mixer/modules.png new file mode 100644 index 0000000..8150dc4 Binary files /dev/null and b/doc/non-mixer/modules.png differ diff --git a/doc/non-mixer/mup.css b/doc/non-mixer/mup.css new file mode 100644 index 0000000..fd4229a --- /dev/null +++ b/doc/non-mixer/mup.css @@ -0,0 +1,449 @@ + +/* Example CSS Style for MUP */ + +a:link { + color: yellow; +} +a:visited { + color: olive; +} +a:active { + color: white; +} +a:link:hover { + text-decoration: underline; +} + +/* #(url) */ +a.ext:link { + color: red; + text-decoration: none; + border-bottom: dashed silver 1; +} +a.ext:visited { + color: darkred; + border-bottom: dashed silver 1; + text-decoration: none; +} + +/* #(ref) */ +a.int:link { + border-bottom: dashed silver 0.15em; +} +a.int:link:hover { + text-decoration: none; + color: white; +} + +/* + a[href^="#"]:link { + border-bottom: dashed silver 0.15em; + } + a[href^="#"]:link:hover { + text-decoration: none; + color: white; + } + */ + +p:contains("Warning:") { + background: #d00; + color: white; + border: dotted gray 0.5em; + display: block; +} + +/* First letter of first paragraph of every chapter */ +/* + h1 + p:first-letter { + text-transform: uppercase; + float: left; + line-height: 0.8em; + font-size: 350%; + font-family: Serif; + letter-spacing: 0; + margin-right: 0.1em; + margin-top: 0.1em; + border: solid gray 1px; + padding: 1px; + color: #d00; + text-shadow: #666 3px 3px 3px; + } + */ +/* First paragraph of every chapter */ +/* + h1 + p { + text-indent: 0; + } + */ + +/* cover */ +#cover * { + background: transparent; +} +#cover { + position: relative; + background: #da0; + color: black; + text-align: center; + margin: 0; + padding: 0.5em; +} +#cover h1, #cover h3 { + text-shadow: #444 0.2em 0.2em 0.2em; + color: white; + border: none; + letter-spacing: 0.2em; + line-height: 0.8em; + margin-left: 2em; + margin-right: 2em; +} +#cover h1:before, #cover h1:after { + content: "::"; + font-size: 300%; + color: black; +} +#cover h1:before { + position: absolute; + top: 0.2em; + left: 0.1em; +} +#cover h1:after { + position: absolute; + top: 0.2em; + right: 0.1em; +} +#cover hr { + display: none; +} + +hr:first-child { + display: none; +} + +hr { + height: 0.2em; + background: #555; + color: #555; + margin-left: 0.5em; +} + +#cover a:visited { + color: black; +} + +/* endnote */ +#endnote { + color: black; +} + +/* TOC */ +#toc { + position: relative; +} +#toc hr { +} +#toc h1 { +} +#toc ul { + font-size: 125%; + font-weight: bold; + margin-bottom: 1em; +} +#toc ul ul { + font-size: 90%; + font-weight: normal; + margin-bottom: 0; +} +#toc li { + list-style: none; + +} +#toc a:link { + border-bottom: 0; +} + +body { + margin: 0; + background: #222; + color: white; + font-family: Arial, sans-serif; +} +/* */ +#body { + position: relative; + margin: 0.5em; + padding: 0.5em; +} +/* ;, : */ +h1 { + color: #ff0; + border-bottom: solid #444 0.1em; +} +/* ::, :::, ::::, :::::, :::::: */ +h2, h3, h4, h5, h6 { + color: #dd0; +} + +/* tables, figures */ +.fig caption { + color: gray; + text-align: center; + /* Required for Mozilla */ + margin: auto; +} +.fig table { + border: none; + margin: auto; +/* border-collapse: collapse; */ +} +/* / */ +.fig.table th { + border: none; + background: gray; + color: black; +} +/* [ */ +.fig.table td { + border: none; + background: silver; + color: black; + padding-left: 1em; + padding-right: 1em; + padding-top: 0.2em; + padding-bottom: 0.2em; +} +/* < */ + +.fig.image table { + border: dashed silver 0.2em; + background: transparent; + /* Every browser should support border radii */ + -moz-border-radius: 0.5em; + border-radius: 0.5em; + +} +.fig.image tr, .fig.image td { + border: none; + background: transparent; + padding: 0; +} + +/* */ +p { + margin-right: 2%; + text-align: justify; + text-indent: 1em; +} +/* > */ +.example * +{ + background: transparent; +} +.example table +{ + margin: 0; + padding: 0; + table-layout: fixed; + width: 100%; + caption-side: top; + overflow: auto; +} +.example caption +{ + caption-side: top; + +} +.example { +} +.example p { + display: inline; + margin: 0; + padding: 0; + text-align: center; +} +.example pre { + margin-top: 0; + font-family: Monospace; + padding: 1em; + border: dashed 0.3em gray; + background: #111; + color: white; + display: block; + overflow: auto; + /* Every browser should support border radii */ + -moz-border-radius: 0.5em; + border-radius: 0.5em; +} +/* " */ +/* + .quote:before { + float: left; + font-size: 500%; + content: "\201C"; + } + */ +/* + blockquote:after { + content: "\201D"; + }*/ +.quote blockquote { + padding: 0.5em; + margin-left: 0.5em; + font-family: Serif; + border-left: solid 0.4em gray; + /* background: #333; */ + color: white; +} +/* ^ */ +small { +/* + color: silver; + font-size: 50%; + */ +} +.footnote p { + color: silver; + margin: 0; +} + +/* Popup footnotes */ +.footnote p { + display: none; +} +.footnote p:target { + display: block; + overflow: auto; + position: fixed; + left: auto; + bottom: 0; + right: 0; + max-width: 50%; + border: solid 0.3em white; + -moz-border-radius: 0.5em; + background: black; + padding: 0.2em; +} + +/* { */ +.admonition * { + background: transparent; + color: white; +} +.admonition dl +{ + display: table; + margin: 0; + padding: 0; + background: #333; + border: dotted black 0.3em; + width: 90% + margin-top: 0.5em; + margin-bottom: 0.5em; +} +.admonition dt +{ + display: table-cell; + vertical-align: center; + border-right: solid silver 0.4em; + font-weight: bold; + font-size: 115%; + font-family: Serif; + background: gray; + width: 0; + text-shadow: black 0.15em 0.15em 0.15em; +} +.admonition dd +{ + padding-left: 0.4em; + display: table-cell; + width: 100%; + text-align: justify; +} + +.admonition table +{ + margin: 0; + padding: 0; + background: #333; + border: dotted black 0.3em; + width: 90% + margin-top: 0.5em; + margin-bottom: 0.5em; +} +.admonition td { + width: 100%; + text-align: justify; +} +.admonition td:first-child:contains("Warning:") { + background: #900; +} +.admonition td:first-child:contains("Caution:") { + background: #960; +} +.admonition td:first-child:contains("Note:") { + background: #690; +} +.admonition td:first-child { + border-right: solid silver 0.4em; + font-weight: bold; + font-size: 115%; + font-family: Serif; + background: gray; + width: 0; + text-shadow: black 0.15em 0.15em 0.15em; +} + + +/* #(b) */ +/* b { color: olive; } */ +/* #(c) */ +tt { + color: #7f0; +} +/* ! keywords ... */ +p em { + color: gray; + font-style: normal; + font-weight: bold; +} + +/* *, + */ +/* Bullet, numbe */ +li { + color: #f0f; +} +/* Text */ +li span, li p { + color: white; +} +li p { + color: red; + display: block; +} +ul { + list-style-type: square; +} +dl { + margin-left: 2%; + margin-top: 1em; +} +/* = */ +dt { + background: #181818; + padding: 0.2em; + font-variant: small-caps; + font-weight: bold; + color: #f0f; +} +dd { + color: white; + text-align: justify; + margin-right: 5%; +} +dt a:link, dt a:visited { + color: #f0f; +} +dt a:link:hover { + color: silver; + text-decoration: underline; +} diff --git a/doc/non-mixer/new-project.png b/doc/non-mixer/new-project.png new file mode 100644 index 0000000..f6bfd61 Binary files /dev/null and b/doc/non-mixer/new-project.png differ diff --git a/doc/non-mixer/non-mixer-and-non-daw-in-patchage.png b/doc/non-mixer/non-mixer-and-non-daw-in-patchage.png new file mode 100644 index 0000000..781ca71 Binary files /dev/null and b/doc/non-mixer/non-mixer-and-non-daw-in-patchage.png differ diff --git a/doc/non-mixer/non-mixer-complex.png b/doc/non-mixer/non-mixer-complex.png new file mode 100644 index 0000000..376b256 Binary files /dev/null and b/doc/non-mixer/non-mixer-complex.png differ diff --git a/doc/non-mixer/single-strip.png b/doc/non-mixer/single-strip.png new file mode 100644 index 0000000..c933039 Binary files /dev/null and b/doc/non-mixer/single-strip.png differ diff --git a/pixmaps/logo.png b/pixmaps/logo.png deleted file mode 100644 index 33f7b2f..0000000 Binary files a/pixmaps/logo.png and /dev/null differ diff --git a/pixmaps/non-daw/logo.png b/pixmaps/non-daw/logo.png new file mode 100644 index 0000000..98e3c54 Binary files /dev/null and b/pixmaps/non-daw/logo.png differ diff --git a/pixmaps/logo.svg b/pixmaps/non-daw/logo.svg similarity index 100% rename from pixmaps/logo.svg rename to pixmaps/non-daw/logo.svg diff --git a/pixmaps/logo2.png b/pixmaps/non-daw/logo2.png similarity index 100% rename from pixmaps/logo2.png rename to pixmaps/non-daw/logo2.png diff --git a/pixmaps/logo2.svg b/pixmaps/non-daw/logo2.svg similarity index 100% rename from pixmaps/logo2.svg rename to pixmaps/non-daw/logo2.svg diff --git a/pixmaps/non-mixer/logo.png b/pixmaps/non-mixer/logo.png new file mode 100644 index 0000000..3f721a8 Binary files /dev/null and b/pixmaps/non-mixer/logo.png differ diff --git a/pixmaps/non-mixer/logo.svg b/pixmaps/non-mixer/logo.svg new file mode 100644 index 0000000..8e2f5c7 --- /dev/null +++ b/pixmaps/non-mixer/logo.svg @@ -0,0 +1,712 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + MIXER + NON + +