Package Details: non-daw-git 0.r1937.cdad262-1

Git Clone URL: (read-only, click to copy)
Package Base: non-daw-git
Description: A modular Digital Audio Workstation system - Git version.
Upstream URL:
Licenses: GPL
Groups: multimedia
Conflicts: non-daw, non-mixer, non-sequencer, non-session-manager, non-timeline
Provides: non-mixer, non-sequencer, non-session-manager, non-timeline
Submitter: epicurious
Maintainer: lievenmoors
Last Packager: lievenmoors
Votes: 22
Popularity: 0.000000
First Submitted: 2012-04-07 08:28
Last Updated: 2021-07-19 20:21

Required by (4)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

StuckUpCreations commented on 2016-02-22 07:43

ntk returns "package not found"
should switch ntk dependecy to ntk-git
for a fluid install, thank you.

anarch.linux commented on 2015-11-05 15:33

there is a problem with non sequencer's event editor in current source tree — it crashes the sequencer when trying to insert anything except for note events.
(issue #182 here: )

a quick and dirty fix:

--- non.orig/sequencer/src/gui/event_edit.fl 2015-11-05 17:09:53.843045795 +0200
+++ non/sequencer/src/gui/event_edit.fl 2015-11-05 17:13:42.058170232 +0200
@@ -138,7 +138,7 @@

e->status( opcode );

- Event_Widget *ew = v->value();
+ Event_Widget *ew;

if ( ew && ew->ev() )
e->timestamp( ew->ev()->timestamp() );

probably it's worth including to PKGBUILD until actual fix commited to the source tree.

pingplug commented on 2015-10-10 14:36

can not build with the latest libsig++
"-std=gnu++11" should be added to CXXFLAGS

lievenmoors commented on 2014-08-26 17:19


I just tested updating, and it didn't return any errors.
Are you sure you don't have any leftover files from another
non-daw installation? You could check if any of the files returned
by "pacman -Qpl nameofgitpackage" are already present on
your system (maybe you should remove the package first).

hollunder commented on 2014-08-26 12:22

I think one of the install() commands fails:
(1/1) installing non-daw-git [########################################] 100%
error: command failed to execute correctly

lievenmoors commented on 2014-04-30 18:39

python3/waf issues have been fixed upstream now.

lievenmoors commented on 2014-04-17 19:53

Thanks for the heads-up, switched to using python2 until this is fixed

haagch commented on 2014-04-17 19:21

Does it build for someone?

_pickle.PicklingError: Can't pickle <class 'waflib.Node.Context.__init__.<locals>.node_class'>: attribute lookup Context.__init__.<locals>.node_class on waflib.Node failed

It looks like waf had an issue with python 3.4 but in my it was already the new version:

lievenmoors commented on 2013-11-10 19:42

Hi, I'm the maintainer of the non-daw-git package, and I just discovered non-suite-git. They are virtually identical, so I propose we merge our packages.
It doesn't matter to me who maintains the package, so that choice would be up to you. So maybe we could discuss some of the differences:

- First of all the name: I think non-daw-git might be a better name, because
the author uses the word DAW a lot on the non website, and I've never seen him use the word suite. I know there was a lot of confusion when the audio recording/editing part of non was called non-daw, but know that name has changed to non-timeline.

- I have a different pkgver() function: I recently adapted mine to the recommendations found on the arch wiki, using commit count instead of date.
I don't mind either way, except that it might be good that most git packages would follow some sort of convention.

- depends: I still have ntk instead of ntk-git, because ntk-git should provide
ntk. But I can imagine it might be a problem for the AUR helpers like yaourt...

- I have libxpm in the makedepends. Namcap told me that was unnecessary, but
when trying to build the package in a chroot jail, I saw that it was needed to
build non. That's when I concluded it should be a makedepend.

- License: didn't know about LGPL, but I guess you know better

- I don't have the replaces array. Isn't the conflicts array enough?

- you add $_pkgname to provides and conflicts. Is this necessary? From the arch wiki: "Do not add pkgname to your provides array, this is done automatically"
I know $pkgname and $_pkgname are not the same, but I still wonder why you add an extra name...

- I didn't know about the python dependency in optdepends...

Let me know what you think,



jrdnjhntn commented on 2013-11-04 03:45

@Vixus - ah, i see (about the ntk-git part). I was already using that - so i was a bit confused as to why your package was building fine for me, but not you guys ;)

anyway, i was mainly just curious if there was maybe a specific reason to not use -O3 (aside from the known older issue), but i assume you're using -O2 because that's what was being used in Arch, already.

O.T. slightly: but NON is starting to get pretty good :)