NON progress
Moderators: raboof, MattKingUSA, khz
NON progress
FYI: NON git updates
"For those who don't follow git too closely, there have recently been
some significant enhancements to Non Mixer.
1. OSC Signal discovery / connection between non-timeline and
non-mixer should be more reliable.
2. Non mixer now has a full plugin browser with search and favorites
instead of the cascading context menu. It will by default only display
plugins which are compatible with the channel configuration at the
insertion point.
3. A new module "Aux" allows one to create 'send' topologies with
fewer strips (note that you won't be able to load projects using the
Aux module in older versions of non-mixer)
4. Progress is sent to NSM when loading projects and the strips can be
seen as they appear during loading. This provides feedback when
loading very large mixes.
NSM has also seen some changes recently. Mostly enhancing the behavior
and appearance of the GUI.
Roy Vegard Ovesen has been hard at work patching programs for NSM.
Also, more and more developers are adding NSM support to their
programs.
I will continue to update
http://non.tuxfamily.org/wiki/ApplicationsSupportingNsm
and
http://non.tuxfamily.org/wiki/NsmPatches
As more support becomes available.
I'm getting pretty close to hitting all my milestones for another
release. I need to finish up the enhancements to Non Sequencer and
then get back to actually making music!
Please report issues and requests to
https://github.com/original-male/non/issues"
http://non.tuxfamily.org/
"For those who don't follow git too closely, there have recently been
some significant enhancements to Non Mixer.
1. OSC Signal discovery / connection between non-timeline and
non-mixer should be more reliable.
2. Non mixer now has a full plugin browser with search and favorites
instead of the cascading context menu. It will by default only display
plugins which are compatible with the channel configuration at the
insertion point.
3. A new module "Aux" allows one to create 'send' topologies with
fewer strips (note that you won't be able to load projects using the
Aux module in older versions of non-mixer)
4. Progress is sent to NSM when loading projects and the strips can be
seen as they appear during loading. This provides feedback when
loading very large mixes.
NSM has also seen some changes recently. Mostly enhancing the behavior
and appearance of the GUI.
Roy Vegard Ovesen has been hard at work patching programs for NSM.
Also, more and more developers are adding NSM support to their
programs.
I will continue to update
http://non.tuxfamily.org/wiki/ApplicationsSupportingNsm
and
http://non.tuxfamily.org/wiki/NsmPatches
As more support becomes available.
I'm getting pretty close to hitting all my milestones for another
release. I need to finish up the enhancements to Non Sequencer and
then get back to actually making music!
Please report issues and requests to
https://github.com/original-male/non/issues"
http://non.tuxfamily.org/
- autostatic
- Established Member
- Posts: 1994
- Joined: Wed Dec 09, 2009 5:26 pm
- Location: Beverwijk, The Netherlands
- Has thanked: 32 times
- Been thanked: 104 times
- Contact:
Re: NON progress
You've to ask 'male'. I know his opinion is that all audio plugins should be LADSPA, but iirc he has plans to add LV2 too, but I don't think it will be there in the next release. Carla gets LV2 support this week and has NSM support.
Patches are welcome I guess
Patches are welcome I guess
Re: NON progress
Wow,
Non is really impressive.
I am relatively new to the Linux ecosystem. I have a lot to learn.
I am inspired to learn and to contribute in some capacity.
Did I mention? .... wow. Huge potential.
Non is really impressive.
I am relatively new to the Linux ecosystem. I have a lot to learn.
I am inspired to learn and to contribute in some capacity.
Did I mention? .... wow. Huge potential.
At Play in the Tale of Now
- AnthonyCFox
- Established Member
- Posts: 393
- Joined: Mon Apr 22, 2013 3:50 pm
- Been thanked: 1 time
Re: NON progress
Any chance of seeing Festige supporting Non (or Carla, when it's ready for WinVST's)?
EDIT: Oops, never mind. Didn't see this
EDIT: Oops, never mind. Didn't see this
That's great!Carla gets LV2 support this week and has NSM support.
War, crime, disease, starvation, extreme poverty; these are serious things.
Music? Not so serious. Have some fun!
Music? Not so serious. Have some fun!
- rncbc
- Established Member
- Posts: 1068
- Joined: Mon Apr 19, 2010 12:20 pm
- Has thanked: 45 times
- Been thanked: 269 times
- Contact:
Re: NON progress
on this date, the Vee One suite is also high on NSM ... svn trunk, experimental though
cheers
cheers
Re: NON progress
@rncbc, could you add optional GUI to your nsm applications? http://non.tuxfamily.org/nsm/API.html#n:1.2.4.1
Is solves our 'cluttered Desktop' problem
Is solves our 'cluttered Desktop' problem
- rncbc
- Established Member
- Posts: 1068
- Joined: Mon Apr 19, 2010 12:20 pm
- Has thanked: 45 times
- Been thanked: 269 times
- Contact:
Re: NON progress
problem is that they're not actual optional GUIs.studio32 wrote:@rncbc, could you add optional GUI to your nsm applications? http://non.tuxfamily.org/nsm/API.html#n:1.2.4.1
Is solves our 'cluttered Desktop' problem
qtractor and the stand-alone vee one GUI's are integral to the application, not optional (as in a plugin). however, if one considers a minimized top-level window as gui_is_hidden state then yes, it might be possible to add this NSM optional-gui capability.
i'll see for it, thanks.
-
- Established Member
- Posts: 538
- Joined: Wed Oct 22, 2008 9:05 pm
- Has thanked: 35 times
- Been thanked: 94 times
- Contact:
Re: NON progress
rnbc:
For my qt applications I just call .hide() and .show() on my main qt window for the NSM signals.
For my qt applications I just call .hide() and .show() on my main qt window for the NSM signals.
- rncbc
- Established Member
- Posts: 1068
- Joined: Mon Apr 19, 2010 12:20 pm
- Has thanked: 45 times
- Been thanked: 269 times
- Contact:
Re: NON progress
exactly what i meant with minimize (hide) and restore/normal (show).NilsGey wrote:rnbc:
For my qt applications I just call .hide() and .show() on my main qt window for the NSM signals.
anyway, it's already there on svn trunk. qtractor and the vee ones have this NSM optional-gui capability, as of todays svn trunk.
cheers
Re: NON progress
Is there a reason to use both ladish and nsm? From what I understand ladish is hardly in active development.falkTX wrote:I think not anytime soon. it's ladish that needs NSM integration though, claudia is just a frontend to it (like gladish is one too).tatch wrote:Are we going to be seeing any NSM integration in claudia?
Re: NON progress
I was asking if there were a reason to be running both ladish and nsm at the same time. I don't see the point in running two session managers concurrently, much like how I don't see the point in running 2 DAWs at the same time.falkTX wrote:Is there a reason for more than 1 DAW?tatch wrote:Is there a reason to use both ladish and nsm? From what I understand ladish is hardly in active development.
People have different tastes and workflows. I use ladish myself and love it, others prefer NSM or even just bash scripts.
(But basically they are just different, different ideas and targets).
I guess my question isn't whether people have preferences, it's why; because from what I've read (is this accurate?), nsm isn't really all that different from ladish, it's implemented better and it's relatively easy to add nsm support in audio apps. Perhaps the answer to my question is "because some apps use ladish and others use nsm", which doesn't seem ideal to me (but what is in linux audio lol). But since you brought it up, what are the different ideas and goals of the two projects? I was under the impression that they both want the same thing, proper session-wide save/loading in linux audio, and do it in rather similar ways.