23 Mar
2016
23 Mar
'16
8:40 a.m.
jalv.select is a little (gtkmm2) GUI to select lv2 plugs from a list and
run them with jalv.
it features:
* search LV2 plugins by regex or by plugin class
* select a LV2 plugin from a ascending sorted list
* select a preset to load
* select the jalv interpreter
* run LV2 plugin with selected preset in jalv
* reload lilv world to catch new installed plugins and presets,
* minimize app to systray icon
jalv.select is released into the public domain.
get the release tar ball here:
https://github.com/brummer10/jalv_select/releases/tag/V0.5
get the development source here:
https://github.com/brummer10/jalv_select/tree/master
24 Mar
24 Mar
7:28 p.m.
Now featured <http://libremusicproduction.com/tools/jalvselect> :) I
really hope it end up packaged *everywhere*. This thing is indispensable
to check a good studio install, test a few plugins, and it's indeed
super fast. LV2 rocks.
On 03/23/2016 07:40 AM, Hermann Meyer wrote:
jalv.select is a little (gtkmm2) GUI to select lv2
plugs from a list
and run them with jalv.
it features:
* search LV2 plugins by regex or by plugin class
* select a LV2 plugin from a ascending sorted list
* select a preset to load
* select the jalv interpreter
* run LV2 plugin with selected preset in jalv
* reload lilv world to catch new installed plugins and presets,
* minimize app to systray icon
jalv.select is released into the public domain.
get the release tar ball here:
https://github.com/brummer10/jalv_select/releases/tag/V0.5
get the development source here:
https://github.com/brummer10/jalv_select/tree/master
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur
7:38 p.m.
New subject: [LAU] [LAA] jalv.select released V0.5
BTW I find it confusing that no selection is actually visible. See what
I mean, Hermann? When you right-select an item, like in this very
capture
<http://libremusicproduction.com/sites/default/files/select_0.png>, the
selected item should appear as so, don't you think?
Either way, super work, thanks again. And I read the code. It's (far)
not as trivial as you made it sound ;)
yPhil
On 03/24/2016 06:28 PM, Yassin Philip wrote:
Now featured
<http://libremusicproduction.com/tools/jalvselect> :) I
really hope it end up packaged *everywhere*. This thing is
indispensable to check a good studio install, test a few plugins, and
it's indeed super fast. LV2 rocks.
On 03/23/2016 07:40 AM, Hermann Meyer wrote:
--
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur
jalv.select is a little (gtkmm2) GUI to select
lv2 plugs from a list
and run them with jalv.
it features:
* search LV2 plugins by regex or by plugin class
* select a LV2 plugin from a ascending sorted list
* select a preset to load
* select the jalv interpreter
* run LV2 plugin with selected preset in jalv
* reload lilv world to catch new installed plugins and presets,
* minimize app to systray icon
jalv.select is released into the public domain.
get the release tar ball here:
https://github.com/brummer10/jalv_select/releases/tag/V0.5
get the development source here:
https://github.com/brummer10/jalv_select/tree/master
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur /https://github.com/xaccrocheur
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
25 Mar
25 Mar
8:56 a.m.
New subject: [LAU] [LAA] jalv.select released V0.5
Am 24.03.2016 um 19:38 schrieb Yassin Philip:
BTW I find it confusing that no selection is actually
visible. See
what I mean, Hermann? When you right-select an item, like in this very
capture
<http://libremusicproduction.com/sites/default/files/select_0.png>,
the selected item should appear as so, don't you think?
Either way, super work, thanks again. And I read the code. It's (far)
not as trivial as you made it sound ;)
yPhil
Hi Philippe
Thanks for your comments, I'm glade you find it useful.
Thanks goes as well to the contributors Hanspeter Portner and Olivier
Humbert,
and to Christopher Arndt for his very useful suggestions and bug reports.
To the selected item, yes, makes sense.
It's changed now in the git repository, so, the selected plug is marked
now.
On 03/24/2016 06:28 PM, Yassin Philip wrote:
> Now featured <http://libremusicproduction.com/tools/jalvselect> :) I
> really hope it end up packaged *everywhere*. This thing is
> indispensable to check a good studio install, test a few plugins, and
> it's indeed super fast. LV2 rocks.
>
Thanks for mention it on
http://libremusicproduction.com/
regards
hermann
On 03/23/2016
07:40 AM, Hermann Meyer wrote:
> jalv.select is a little (gtkmm2) GUI to select lv2 plugs from a list
> and run them with jalv.
>
> it features:
>
> * search LV2 plugins by regex or by plugin class
> * select a LV2 plugin from a ascending sorted list
> * select a preset to load
> * select the jalv interpreter
> * run LV2 plugin with selected preset in jalv
> * reload lilv world to catch new installed plugins and presets,
> * minimize app to systray icon
>
>
> jalv.select is released into the public domain.
>
> get the release tar ball here:
> https://github.com/brummer10/jalv_select/releases/tag/V0.5
>
> get the development source here:
> https://github.com/brummer10/jalv_select/tree/master
>
>
28 Mar
28 Mar
3 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
(I'm not sure what is the best channel to discuss jalv.select
development other than opening a Github issue right away. If this is not
the right place, please direct to me to an appropriate mailing list.)
Currently, if I have jalv.select already running, whether minimized or
not, and try to run it again, I get the the following error:
$ jalv.select
The program 'jalv.select' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
(Details: serial 10 error_code 10 request_code 33 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
It is probably a good thing that only one runnning instance of
jalv.select is allowed, but the error message should probably be more
helpful (I guess the error has to do with registering the global
keyboard shortcut for opening the jalv.select window, which doesn't work
in all desktop environments anyway).
What I would ideally like is that, if jalv.select is already running and
you start another instance, the running instance opens its window (if
minimized). That would require some kind of IPC, so I'm not sure, if
this is something that's worth adding. As as simple hack, jalv.select
could just create a socket file at a known location, or it could use
DBus, which has the advantage that the "open jalv.select window" action
could be caleld from any generic DBus client.
But it would allow to define a keyboard shortcut to open the jalv.select
window accross different desktop environments, since you could use the
feature of your preferred desktop to bind a progranm or script to global
shortcut.
What do you think?
Chris
4:47 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 28.03.2016 um 15:00 schrieb Christopher Arndt:
(I'm not sure what is the best channel to discuss
jalv.select
development other than opening a Github issue right away. If this is not
the right place, please direct to me to an appropriate mailing list.)
Currently, if I have jalv.select already running, whether minimized or
not, and try to run it again, I get the the following error:
$ jalv.select
The program 'jalv.select' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
(Details: serial 10 error_code 10 request_code 33 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
It is probably a good thing that only one runnning instance of
jalv.select is allowed, but the error message should probably be more
helpful (I guess the error has to do with registering the global
keyboard shortcut for opening the jalv.select window, which doesn't work
in all desktop environments anyway).
Hi Chris
Yes, it's a failing XGrabKey error.
I've included now a trap to catch the error, and in case XGrabKey
failed, the HotKey will simply be disabled.
The message in terminal will give you a note about that, but you could
run jalv.select in multiple instances (even if it makes no sense)
Indeed, it's hard to find a free HotKey for any Desktop manager, I've
chosen SHIFT+ESCAPE, as it is free here on cinnamon, and my research
didn't pop up a use of it in other Desktop managers. Which desktop do
you run?
Also free here is SHIFT+CONTROL+ESCAPE, which I could set alternatively.
What I would ideally like is that, if jalv.select is
already running and
you start another instance, the running instance opens its window (if
minimized). That would require some kind of IPC, so I'm not sure, if
this is something that's worth adding. As as simple hack, jalv.select
could just create a socket file at a known location, or it could use
DBus, which has the advantage that the "open jalv.select window" action
could be caleld from any generic DBus client.
But it would allow to define a keyboard shortcut to open the jalv.select
window accross different desktop environments, since you could use the
feature of your preferred desktop to bind a progranm or script to global
shortcut.
What do you think?
Chris
I'm all open for patches, pull requests or what ever, gut, I've never
interact with DBus,
regards
hermann
5:28 p.m.
New subject: Opening jalv.select window from the command line
Am 28.03.2016 um 16:47 schrieb Hermann Meyer:
I've included now a trap to catch the error, and
in case XGrabKey
failed, the HotKey will simply be disabled.
Great, thanks.
Which desktop do you run?
Xfce4 (xfwm4)
I'm not sure for what Shift-Escape is used and which program grabs it,
as it just does nothing, but Xfce allows one to define global keyboard
shortcuts to run programs:
http://docs.xfce.org/xfce/xfce4-settings/keyboard
I'm all open for patches, pull requests or what
ever, gut, I've never
interact with DBus,
I'm not really a C++ programmer, but I'll probably try to implemement
sth similar in my jack-select systray app in Python and the DBus binding
I use there is pretty close to the underlying libdbus. When this is
accomplished I could at least give you some tips how to do it in
jalv.select.
Chris
30 Mar
30 Mar
1:03 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 28.03.2016 um 15:00 schrieb Christopher Arndt:
What I would ideally like is that, if jalv.select is already running and
you start another instance, the running instance opens its window (if
minimized). That would require some kind of IPC, so I'm not sure, if
this is something that's worth adding. As as simple hack, jalv.select
could just create a socket file at a known location, or it could use
DBus, which has the advantage that the "open jalv.select window" action
could be caleld from any generic DBus client.
Hi Chris
So I've added a named pipe to jalv.select, so that communication with
the app is possible.
Currently it understand "quit", "show" and "hide".
Syntax from bash is simple, for example:
echo show >jalv.select.fifo
echo hide >jalv.select.fifo
echo quit >jalv.select.fifo
It understand as well "exit", but that's for internal use.
I guess that will allow you to define your own keyboard shortcuts.
Regarding the intern Desktop HotKey's for show/hide, jalv.select will
now try <SHIFT>+ESCAPE first,
if that fail, it will try
<CONTROL><SHIFT>+ESCAPE.
If that fail as well, the KeyGrabber will be disabled.
Also, jalv.select takes care now to be the only instance of it's own, a
running instance will be presented, when you try to start a new one.
I hope this helps for a better cross Desktop integration.
regards
hermann
But it would allow to define a keyboard shortcut to
open the jalv.select
window accross different desktop environments, since you could use the
feature of your preferred desktop to bind a progranm or script to global
shortcut.
What do you think?
Chris
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
1:41 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Hi Hermann,
Am 30.03.2016 um 13:03 schrieb Hermann Meyer:
So I've added a named pipe to jalv.select, so that
communication with
the app is possible.
Currently it understand "quit", "show" and "hide".
that's great, thanks!
Is that fifo always created in the working dir or is there a way to set
its path?
BTW:
I did something very similar yesterday for my jack-select app, but using
DBus instead of a pipe:
https://github.com/SpotlightKid/jack-select/commit/0f4178b2e023eab67887a76e…
Which is available as version 0.5b1 now on Github, PyPI and as an AUR
package:
https://github.com/SpotlightKid/jack-select
https://pypi.python.org/pypi/jack-select
https://aur.archlinux.org/packages/jack-select/
Chris
6:53 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 30.03.2016 um 13:40 schrieb Christopher Arndt:
Hi Hermann,
Am 30.03.2016 um 13:03 schrieb Hermann Meyer:
Ha, good point.
I've set the fifo-path now to /tmp instead working dir, to ensure that
"all" instances use the same fifo and have access to it. Also it should
make it simpler to write to it from command-line.
So I've added a named pipe to jalv.select, so
that communication with
the app is possible.
Currently it understand "quit", "show" and "hide".
that's great, thanks!
Is that fifo always created in the working dir or is there a way to set
its path? BTW:
I did something very similar yesterday for my jack-select app, but using
DBus instead of a pipe:
https://github.com/SpotlightKid/jack-select/commit/0f4178b2e023eab67887a76e…
Which is available as version 0.5b1 now on Github, PyPI and as an AUR
package:
https://github.com/SpotlightKid/jack-select
https://pypi.python.org/pypi/jack-select
https://aur.archlinux.org/packages/jack-select/
Chris
I would like to try it, just, I'm a plain jack2 user, no jack-dbus here.
regards
hermann
7:10 p.m.
New subject: jack-select and DBus (Was: Opening jalv.select window from the command line)
Am 30.03.2016 um 18:53 schrieb Hermann Meyer:
Am 30.03.2016 um 13:40 schrieb Christopher Arndt:
I would like to try it, just, I'm a plain jack2 user, no jack-dbus here.
Sorry, since jack-select doesn't start or stop the JACK server directly,
it only communicates with jack-dbus via, well, DBus, plain jack1/2 is
currently not the scenario jack-select was made for.
I don't want to write another process manager for the JACK server
process, QjackCtl is perfectly fine for that.
Maybe in the future as an alternative I'll add support for talking to
QjackCtl's DBus service instead of to jack-dbus directly. jack-select
then would be basically just another, more directly accessible GUI for
part of the functionality of a runnning QjackCtl instance.
It's not something I personally need, though, so someone would need to
convince me that it is useful to somebody.
Chris
7:29 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 30.03.2016 um 18:53 schrieb Hermann Meyer:
I've set the fifo-path now to /tmp instead working
dir, to ensure that
"all" instances use the same fifo and have access to it.
Not that it's a very common usage scenario, but won't that preclude
jalv.select being used by different users on the same system at the same
time? Also any user can control another user's jalv.select process. And
if you make the fifo file permissions more restrictive, you'll get
problems with stale files etc.
I think it would be better to determine the fifo path with something
like this (pseudo code) and set its permissions to 0600:
fifo_path = getenv('JALV_SELECT_FIFO_PATH')
fifo_path = fifo_path if fifo_path else getenv('HOME') +
'/.jalv_select_fifo'
It's issues like these why I think DBus is a better way to do IPC for
any but the most simple program, which is intended to run in a desktop
environment anyway.
Chris
31 Mar
31 Mar
5:45 a.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 30.03.2016 um 19:28 schrieb Christopher Arndt:
Am 30.03.2016 um 18:53 schrieb Hermann Meyer:
mkfifo use umask to set the file permission (-0022), so the resulting
permission is 0644, eg. rw-r--r--
means, other users cant control (write) your jalv.select instance.
If jalv.select cant write to a existing fifo, the fifo just get ignored,
so in a multi-user environment, you could start your own jalv.select,
even if the fifo isn't usable for you.
I've set the fifo-path now to /tmp instead
working dir, to ensure that
"all" instances use the same fifo and have access to it.
Not that
it's a very common usage scenario, but won't that preclude
jalv.select being used by different users on the same system at the same
time? Also any user can control another user's jalv.select process. And
if you make the fifo file permissions more restrictive, you'll get
problems with stale files etc.
I think it would be better to determine the fifo path with something
like this (pseudo code) and set its permissions to 0600: fifo_path =
getenv('JALV_SELECT_FIFO_PATH')
fifo_path = fifo_path if fifo_path else getenv('HOME') +
'/.jalv_select_fifo'
I like to have it in /tmp, because, for the case that jalv.select ended
unexpected, the fifo get deleted at lest when you shut down the machine.
In home, it may exist for ever, at least.
It's issues like these why I think DBus is a
better way to do IPC for
any but the most simple program, which is intended to run in a desktop
environment anyway.
Chris
Well, maybe DBus is a better solution, but as I said, I've never dealt
with it, . .
regards
hermann
9:52 a.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 31.03.2016 um 05:45 schrieb Hermann Meyer:
I like to have it in /tmp, because, for the case that
jalv.select ended
unexpected, the fifo get deleted at lest when you shut down the machine.
In home, it may exist for ever, at least.
Good point.
You could append the UID to the fifo name.
Chris
12:11 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 31.03.2016 um 09:51 schrieb Christopher Arndt:
Am 31.03.2016 um 05:45 schrieb Hermann Meyer:
Also a good point. done.
regards
hermann
I like to have it in /tmp, because, for the case
that jalv.select ended
unexpected, the fifo get deleted at lest when you shut down the machine.
In home, it may exist for ever, at least.
Good point.
You could append the UID to the fifo name.
Chris
1:19 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 31.03.2016 um 12:11 schrieb Hermann Meyer:
Am 31.03.2016 um 09:51 schrieb Christopher Arndt:
Perfect.
One more thing: Whereas, when I run the first instance, itsw window
always opens horizontally centered on my desktop.
When I open the jalv.select window by running another instance, the
window *sometimes* opens in the upper left corner of my desktop,
independently of where the mouse pointer currently is.
I have not been able to consistently reproduce the behaviour or discern
a pattern.
Chris
You could append the UID to the fifo name.
Also a good point. done.
6:29 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
Am 31.03.2016 um 13:19 schrieb Christopher Arndt:
Am 31.03.2016 um 12:11 schrieb Hermann Meyer:
Hi Chris
I've implement some more guards now to stabilize the fifo read/write
handling.
I guess that should be fixed now.
regards
hermann
Am 31.03.2016 um 09:51 schrieb Christopher
Arndt:
Perfect.
One more thing: Whereas, when I run the first instance, itsw window
always opens horizontally centered on my desktop.
When I open the jalv.select window by running another instance, the
window *sometimes* opens in the upper left corner of my desktop,
independently of where the mouse pointer currently is.
I have not been able to consistently reproduce the behaviour or discern
a pattern.
Chris
You could append the UID to the fifo name.
Also a good point. done.
10:13 p.m.
New subject: Opening jalv.select window from the command line (Was:jalv.select released V0.5)
And I guess it warrants a release, did I understand it right, you guys
devised a command-line interface to jalv.select, right? Like I used
jalv.select to lauch say, Sorcer, and now...? Please, can you give me
one ore more use-cases? It sounds interesting. AND jalv.select actually
never made the news. So this seems to be it :) I just have to fully
understand what's going on. I read the thread several times, I always
seem to be missing the big picture ; And because I'm a journalist, I'm
clueless. 'Ts me job.
yPhil
On 03/31/2016 05:29 PM, Hermann Meyer wrote:
Am 31.03.2016 um 13:19 schrieb Christopher Arndt:
--
Yassin "xaccrocheur" Philip
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur
Am 31.03.2016 um 12:11 schrieb Hermann Meyer:
Hi Chris
I've implement some more guards now to stabilize the fifo read/write
handling.
I guess that should be fixed now.
regards
hermann
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev Am 31.03.2016 um 09:51 schrieb Christopher
Arndt:
Perfect.
One more thing: Whereas, when I run the first instance, itsw window
always opens horizontally centered on my desktop.
When I open the jalv.select window by running another instance, the
window *sometimes* opens in the upper left corner of my desktop,
independently of where the mouse pointer currently is.
I have not been able to consistently reproduce the behaviour or discern
a pattern.
Chris
You could append the UID to the fifo name.
Also a good point. done.
11:28 p.m.
New subject: Opening jalv.select window from the command line
On 03/31/2016 10:13 PM, Yassin Philip wrote:
Did I understand it right, you guys devised a
command-line interface
to jalv.select, right? [...] Please, can you give me
one ore more use-cases?
A video says more than a thousand words:
https://www.youtube.com/watch?v=RSRDbmTMA98
Chris
3087
days inactive
3095
days old
linux-audio-dev@lists.linuxaudio.org
18 comments
3 participants
participants (3)
-
Christopher Arndt -
Hermann Meyer -
Yassin Philip