[LAU] Re: Looking for a cLI recordiing solution / ideas, brainstorming

Brandon Hale wrote:

> I'm very sad that ecasound is slowly falling behind. What does that mean for
> Nama?

Hi Brandon,

Sometime Nama author here. Thanks for asking.

The last ecasound release was in 2020. I think ecasound can
tolerate a backlog of a few patches from distro maintainers.
And I'm confident that author Kai Vehmanen will consider
reviewing and merging them into his sources.  Or if
necessary, someone will step up.

LV2 plugins with poor support for CLI are not an ecasound
problem. As Jeanette explained it to me, for some plugins,
the GUI might display a certain parameter as frequency in
Hz, however the same parameter accessed via liblilv might
simply indicate a range of 0 to 1. 

I hope mod-host users and others wanting better information
about LV2 plugins outside a GUI framework will complain
loudly (and politely) to the plugin authors. Also, it sounds
like someone will have to port JUCE to linux for some
plugins to compile. 

Regarding Nama, I think it's worth maintaining a
recorder/editor for terminal users that doesn't require the
overhead of a GUI with an accessibility framework. 

Nama has convenience features in the pipeline that are
blocked by problems with the keymaps and terminal libraries.
The new features will reduce the keystrokes needed for
transport seeking, setting and bumping marks, trimming and
assembling audio segments, and adjusting plugin parameters.

Overcoming terminal-related issues and landing these
features will be the biggest help for Nama, IMO :-)

regards to all 

Joel

 
> On 7/25/25 07:59, Jeanette C. wrote:
> > Hey hey,
> > I just heard that Ecasound, as robsut as its code is, is slowly moving
> > out, requiring more and more patches. So I should really look for a new
> > solution.
> > 
> > Why CLI? I had a GUI running on my system, with JACK, and found that
> > Orca was very sluggish, not condusive to fast efficient work. Besides,
> > there are quite a few LV2 plugins which are built on JUCE and JUCE Uis
> > are not accessible on Linux. Last thing I heard, they added
> > accessibility but only to mac and windows.
> > 
> > So back to the commandline. LV2 plugins can be controlled there,
> > mod-host a case in point. Though, admittedly, I found quite a few
> > plugins with quite meaningless parameter ranges. Still, they can be
> > used.
> > 
> > Does anyone have any ideas? Perhaps something that is in its early
> > stages or a UI that was created for testing or automation and might
> > offer more beyond that purpose? -- Any suggestions or hints are welcome.
> > For the time being, Ecasound will run, but its life-cycle looks
> > definitely finite in the foreseeable future.
> > 
> > Best wishes,
> > 
> > Jeanette
> > 
> _______________________________________________
> Linux-audio-user mailing list -- linux-audio-user-cunTk1MwBs/[email protected]
> To unsubscribe send an email to linux-audio-user-leave-cunTk1MwBs/[email protected]

-- 
Joel Roth
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user-cunTk1MwBs/[email protected]
To unsubscribe send an email to linux-audio-user-leave-cunTk1MwBs/[email protected]