27 Jul
2012
27 Jul
'12
6:27 p.m.
We are proud to announce the release of guitarix2-0.23.3.
Guitarix is a modular tube amplifier simulation for jack, with
additional Effect-Racks, inbuilt effects as well as support for LADSPA
plug-ins.
This is a Bug-fix release witch fix the ladspa_guitarix.so
module guitarix-fx [UniqueID 4070] to avoid segfault when loading into a
host.
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
download site:
http://sourceforge.net/projects/guitarix/
have fun
guitarix development team
27 Jul
27 Jul
6:35 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/27/2012 06:27 PM, hermann meyer wrote:
We are proud to announce the release of
guitarix2-0.23.3.
Guitarix is a modular tube amplifier simulation for jack, with
additional Effect-Racks, inbuilt effects as well as support for LADSPA
plug-ins.
This is a Bug-fix release witch fix the ladspa_guitarix.so
module guitarix-fx [UniqueID 4070] to avoid segfault when loading into a
host.
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
download site:
http://sourceforge.net/projects/guitarix/
have fun
guitarix development team
Maybe it's an idea to make a visual distinction between internal and
external (LADSPA) plugin. Now it's hard to see which effects are part of
the Guitarix software and which are LADSPA plugins (after you enabled a
list of LADSPA plugins).
In the 'effects' menu on the left side, there is an 'external' entry,
but not all LADSPA plugins are displayed there.
Another feature suggestion, which you are aware of already, would be
adding NSM support, with the OSC functionality of NSM it should be easy
to switch between (effect processing) sessions in a live situation.
Regards,
\r
28 Jul
28 Jul
5:06 a.m.
New subject: [LAD] The guitarix project release version 0.23.3
Am 27.07.2012 18:35, schrieb rosea.grammostola:
On 07/27/2012 06:27 PM, hermann meyer wrote:
Hi
Explore the LADSPA select list a bit, it is a power-full tool. Have a
look at the "Show Details", there you can select under witch category
the plug-in appears, you can set the name (if you like to have a
indicator for LADSPA plug-ins, set a (L) before the name, for example),
the controllers type, range and order, the master controller, you can
add a dry/wet controller,.....
At default, we order plug-ins under the category witch is given by the
plug-in author, only if non is given, it will appear under the external
entry. But you can change all that to your needs. Any detail is editable.
Also you can select to show only enabled plugs, you can leave the widget
open at any time to get a overview of what you have selected and under
witch category to find it and/or change the behavior of the plug.Just
press "Apply" to make your changes work.
To NSM, well, you know it already, it isn't high on my todo list :-) ,
but guitarix is a open project, we accept patches, we welcome developers
to join the project, . . .
anyhow, I hope you enjoy guitarix also without NSM support for now.
greets
hermann
We are proud to announce the release of
guitarix2-0.23.3.
Guitarix is a modular tube amplifier simulation for jack, with
additional Effect-Racks, inbuilt effects as well as support for LADSPA
plug-ins.
This is a Bug-fix release witch fix the ladspa_guitarix.so
module guitarix-fx [UniqueID 4070] to avoid segfault when loading into a
host.
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
download site:
http://sourceforge.net/projects/guitarix/
have fun
guitarix development team
Maybe it's an idea to make a visual distinction between internal and
external (LADSPA) plugin. Now it's hard to see which effects are part
of the Guitarix software and which are LADSPA plugins (after you
enabled a list of LADSPA plugins).
In the 'effects' menu on the left side, there is an 'external' entry,
but not all LADSPA plugins are displayed there.
Another feature suggestion, which you are aware of already, would be
adding NSM support, with the OSC functionality of NSM it should be
easy to switch between (effect processing) sessions in a live situation.
Regards,
\r
29 Jul
29 Jul
12:29 a.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/28/2012 05:06 AM, hermann meyer wrote:
Am 27.07.2012 18:35, schrieb rosea.grammostola:
Is it possible to start guitarix with a specific preset via command
line? Then I could use it in NSM via the nsm-proxy client. Not so nice
as full NSM support, but alas ...
\r
On 07/27/2012 06:27 PM, hermann meyer wrote:
Hi
Explore the LADSPA select list a bit, it is a power-full tool. Have a
look at the "Show Details", there you can select under witch category
the plug-in appears, you can set the name (if you like to have a
indicator for LADSPA plug-ins, set a (L) before the name, for example),
the controllers type, range and order, the master controller, you can
add a dry/wet controller,.....
At default, we order plug-ins under the category witch is given by the
plug-in author, only if non is given, it will appear under the external
entry. But you can change all that to your needs. Any detail is editable.
Also you can select to show only enabled plugs, you can leave the widget
open at any time to get a overview of what you have selected and under
witch category to find it and/or change the behavior of the plug.Just
press "Apply" to make your changes work.
To NSM, well, you know it already, it isn't high on my todo list :-) ,
but guitarix is a open project, we accept patches, we welcome developers
to join the project, . . .
anyhow, I hope you enjoy guitarix also without NSM support for now. We are proud to announce the release of
guitarix2-0.23.3.
Guitarix is a modular tube amplifier simulation for jack, with
additional Effect-Racks, inbuilt effects as well as support for LADSPA
plug-ins.
This is a Bug-fix release witch fix the ladspa_guitarix.so
module guitarix-fx [UniqueID 4070] to avoid segfault when loading into a
host.
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
download site:
http://sourceforge.net/projects/guitarix/
have fun
guitarix development team
Maybe it's an idea to make a visual distinction between internal and
external (LADSPA) plugin. Now it's hard to see which effects are part
of the Guitarix software and which are LADSPA plugins (after you
enabled a list of LADSPA plugins).
In the 'effects' menu on the left side, there is an 'external' entry,
but not all LADSPA plugins are displayed there.
Another feature suggestion, which you are aware of already, would be
adding NSM support, with the OSC functionality of NSM it should be
easy to switch between (effect processing) sessions in a live situation.
Regards,
\r
5:48 a.m.
New subject: [LAD] The guitarix project release version 0.23.3
Am 29.07.2012 00:29, schrieb rosea.grammostola:
Is it possible to start guitarix with a specific
preset via command
line? Then I could use it in NSM via the nsm-proxy client. Not so nice
as full NSM support, but alas ...
\r
It is, it's a little tricky, . . . :-)
The preset to load is given by the guitarix state file, . . .
So, you can start guitarix with the -n parameter to give a name for the
(jack)instance,
example guitarix -n gx2.
guitarix will create a own state file for guitarix:gx2, select the
preset you will use, and quit guitarix.
Now, when you would like to start guitarix with this preset, just start
guitarix -n gx2. Create as many
state files you need the same way, maybe guitarix -n lead, . . . rhythm,
. . .
If you use the name of the preset you like to load, you will have a cool
overview of this stuff.
The name given by the -n parameter is the name witch is used for connect
to jack, so for connections you must take care to use the correct name.
A other way is the -f parameter, . . .
Select the preset you would use to start guitarix, quit guitarix, go to
$HOME/.config/guitarix/
and copy and rename the file guitarix2_rc to what ever you like
(preset_name? _rc). Repeat that for any preset you need to start
guitarix with. To load the state file, start guitarix with
guitarix -f /were/ever/your/state_file/is_rc
greets
hermann
12:57 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/29/2012 05:47 AM, hermann meyer wrote:
Am 29.07.2012 00:29, schrieb rosea.grammostola:
Thx.
Does guitarix autoconnect to JACK? Afaik this is not proper practice
concerning JACK. Autoconnect might be an option but not the default and
it should at least be able to turn it off.
When using guitarix only or with a preset via nsm-proxy, guitarix amp is
always connected to the outputs of my soundcard, where it should only
connect to guitarix fx right?
When I disconnect those outputs and save the session (and the changes in
guitarix (this option is always available even when there are no changes
made, which is kind of not logic to me)), when restarting the session,
every time those connections from guitarix amp to output soundcard is
back :/
\r
Is it possible to start guitarix with a specific
preset via command
line? Then I could use it in NSM via the nsm-proxy client. Not so nice
as full NSM support, but alas ...
\r
It is, it's a little tricky, . . . :-)
The preset to load is given by the guitarix state file, . . .
So, you can start guitarix with the -n parameter to give a name for the
(jack)instance,
example guitarix -n gx2.
guitarix will create a own state file for guitarix:gx2, select the
preset you will use, and quit guitarix.
Now, when you would like to start guitarix with this preset, just start
guitarix -n gx2. Create as many
state files you need the same way, maybe guitarix -n lead, . . . rhythm,
. . .
If you use the name of the preset you like to load, you will have a cool
overview of this stuff.
The name given by the -n parameter is the name witch is used for connect
to jack, so for connections you must take care to use the correct name.
A other way is the -f parameter, . . .
Select the preset you would use to start guitarix, quit guitarix, go to
$HOME/.config/guitarix/
and copy and rename the file guitarix2_rc to what ever you like
(preset_name? _rc). Repeat that for any preset you need to start
guitarix with. To load the state file, start guitarix with
guitarix -f /were/ever/your/state_file/is_rc
1:18 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/29/2012 12:57 PM, rosea.grammostola wrote:
On 07/29/2012 05:47 AM, hermann meyer wrote:
Ok, so it seems that if you save the preset state with the wrong
connections, it stays wrong forever. Changing ports in guitarix, and
then hit 'save changes' doesn't do anything anymore after restarting
guitarix with the preset. It works here when I unselect all the port in
guitarix and then save the preset. Then I can handle the connections
correctly in NSM (or guitarix itself if I run it outside the session).
Anyway, this feels pretty cumbersome and technically not 100% correct.
Regards,
\r
Am 29.07.2012 00:29, schrieb rosea.grammostola:
Thx.
Does guitarix autoconnect to JACK? Afaik this is not proper practice
concerning JACK. Autoconnect might be an option but not the default and
it should at least be able to turn it off.
When using guitarix only or with a preset via nsm-proxy, guitarix amp is
always connected to the outputs of my soundcard, where it should only
connect to guitarix fx right?
When I disconnect those outputs and save the session (and the changes in
guitarix (this option is always available even when there are no changes
made, which is kind of not logic to me)), when restarting the session,
every time those connections from guitarix amp to output soundcard is
back :/
\r Is it possible to start guitarix with a specific
preset via command
line? Then I could use it in NSM via the nsm-proxy client. Not so nice
as full NSM support, but alas ...
\r
It is, it's a little tricky, . . . :-)
The preset to load is given by the guitarix state file, . . .
So, you can start guitarix with the -n parameter to give a name for the
(jack)instance,
example guitarix -n gx2.
guitarix will create a own state file for guitarix:gx2, select the
preset you will use, and quit guitarix.
Now, when you would like to start guitarix with this preset, just start
guitarix -n gx2. Create as many
state files you need the same way, maybe guitarix -n lead, . . . rhythm,
. . .
If you use the name of the preset you like to load, you will have a cool
overview of this stuff.
The name given by the -n parameter is the name witch is used for connect
to jack, so for connections you must take care to use the correct name.
A other way is the -f parameter, . . .
Select the preset you would use to start guitarix, quit guitarix, go to
$HOME/.config/guitarix/
and copy and rename the file guitarix2_rc to what ever you like
(preset_name? _rc). Repeat that for any preset you need to start
guitarix with. To load the state file, start guitarix with
guitarix -f /were/ever/your/state_file/is_rc
2:01 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
Am 29.07.2012 13:18, schrieb rosea.grammostola:
On 07/29/2012 12:57 PM, rosea.grammostola wrote:
Maybe that is a bit confusing, but, connections are stored in the state
file (guitarix2_rc), not in the preset file (bank).
So, when you save a preset, no connections are stored, presets only
include the states of the controllers, (Knobs, sliders, selectors,
switchers, . . ) related to the engine.
When you quit guitarix, the current (UI) state will stored in the state
file, that including the connections.
The state file points to the preset file witch was last in use and load
it into the engine.
So guitarix will cover the last used state, before you quit guitarix.
Switch a preset file wouldn't change any connection.
Only if guitarix is controlled eg. started by jack-session manager, self
connection is disabled. Maybe NSM need a same behavior like jack-session
manager, I don't know?
A workaround could be to "fake" a jack-session-call, when you use the -U
-A flags,
guitarix -U 1 -A 2 -f /your/state_file_rc
that will disable any self-connection by guitarix.
greets
hermann
On 07/29/2012 05:47 AM, hermann meyer wrote:
Ok, so it seems that if you save the preset state with the wrong
connections, it stays wrong forever. Changing ports in guitarix, and
then hit 'save changes' doesn't do anything anymore after restarting
guitarix with the preset. It works here when I unselect all the port
in guitarix and then save the preset. Then I can handle the
connections correctly in NSM (or guitarix itself if I run it outside
the session).
Anyway, this feels pretty cumbersome and technically not 100% correct.
Regards,
\r
Am 29.07.2012 00:29, schrieb rosea.grammostola:
Thx.
Does guitarix autoconnect to JACK? Afaik this is not proper practice
concerning JACK. Autoconnect might be an option but not the default and
it should at least be able to turn it off.
When using guitarix only or with a preset via nsm-proxy, guitarix amp is
always connected to the outputs of my soundcard, where it should only
connect to guitarix fx right?
When I disconnect those outputs and save the session (and the changes in
guitarix (this option is always available even when there are no changes
made, which is kind of not logic to me)), when restarting the session,
every time those connections from guitarix amp to output soundcard is
back :/
\r Is it possible to start guitarix with a specific
preset via command
line? Then I could use it in NSM via the nsm-proxy client. Not so nice
as full NSM support, but alas ...
\r
It is, it's a little tricky, . . . :-)
The preset to load is given by the guitarix state file, . . .
So, you can start guitarix with the -n parameter to give a name for the
(jack)instance,
example guitarix -n gx2.
guitarix will create a own state file for guitarix:gx2, select the
preset you will use, and quit guitarix.
Now, when you would like to start guitarix with this preset, just start
guitarix -n gx2. Create as many
state files you need the same way, maybe guitarix -n lead, . . .
rhythm,
. . .
If you use the name of the preset you like to load, you will have a
cool
overview of this stuff.
The name given by the -n parameter is the name witch is used for
connect
to jack, so for connections you must take care to use the correct name.
A other way is the -f parameter, . . .
Select the preset you would use to start guitarix, quit guitarix, go to
$HOME/.config/guitarix/
and copy and rename the file guitarix2_rc to what ever you like
(preset_name? _rc). Repeat that for any preset you need to start
guitarix with. To load the state file, start guitarix with
guitarix -f /were/ever/your/state_file/is_rc
5:31 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/29/2012 02:00 PM, hermann meyer wrote:
Am 29.07.2012 13:18, schrieb rosea.grammostola:
This becomes relevant imo when NSM support will be added to guitarix
On 07/29/2012 12:57 PM, rosea.grammostola wrote:
Maybe that is a bit confusing, but, connections are stored in the state
file (guitarix2_rc), not in the preset file (bank).
So, when you save a preset, no connections are stored, presets only
include the states of the controllers, (Knobs, sliders, selectors,
switchers, . . ) related to the engine.
When you quit guitarix, the current (UI) state will stored in the state
file, that including the connections.
The state file points to the preset file witch was last in use and load
it into the engine.
So guitarix will cover the last used state, before you quit guitarix.
Switch a preset file wouldn't change any connection.
Only if guitarix is controlled eg. started by jack-session manager, self
connection is disabled. Maybe NSM need a same behavior like jack-session
manager, I don't know? On 07/29/2012 05:47 AM, hermann meyer wrote:
Ok, so it seems that if you save the preset state with the wrong
connections, it stays wrong forever. Changing ports in guitarix, and
then hit 'save changes' doesn't do anything anymore after restarting
guitarix with the preset. It works here when I unselect all the port
in guitarix and then save the preset. Then I can handle the
connections correctly in NSM (or guitarix itself if I run it outside
the session).
Anyway, this feels pretty cumbersome and technically not 100% correct.
Regards,
\r
Am 29.07.2012 00:29, schrieb rosea.grammostola:
> Is it possible to start guitarix with a specific preset via command
> line? Then I could use it in NSM via the nsm-proxy client. Not so nice
> as full NSM support, but alas ...
>
> \r
It is, it's a little tricky, . . . :-)
The preset to load is given by the guitarix state file, . . .
So, you can start guitarix with the -n parameter to give a name for the
(jack)instance,
example guitarix -n gx2.
guitarix will create a own state file for guitarix:gx2, select the
preset you will use, and quit guitarix.
Now, when you would like to start guitarix with this preset, just start
guitarix -n gx2. Create as many
state files you need the same way, maybe guitarix -n lead, . . .
rhythm,
. . .
If you use the name of the preset you like to load, you will have a
cool
overview of this stuff.
The name given by the -n parameter is the name witch is used for
connect
to jack, so for connections you must take care to use the correct name.
A other way is the -f parameter, . . .
Select the preset you would use to start guitarix, quit guitarix, go to
$HOME/.config/guitarix/
and copy and rename the file guitarix2_rc to what ever you like
(preset_name? _rc). Repeat that for any preset you need to start
guitarix with. To load the state file, start guitarix with
guitarix -f /were/ever/your/state_file/is_rc
Thx.
Does guitarix autoconnect to JACK? Afaik this is not proper practice
concerning JACK. Autoconnect might be an option but not the default and
it should at least be able to turn it off.
When using guitarix only or with a preset via nsm-proxy, guitarix amp is
always connected to the outputs of my soundcard, where it should only
connect to guitarix fx right?
When I disconnect those outputs and save the session (and the changes in
guitarix (this option is always available even when there are no changes
made, which is kind of not logic to me)), when restarting the session,
every time those connections from guitarix amp to output soundcard is
back :/
\r A workaround could be to "fake" a
jack-session-call, when you use the -U
-A flags,
guitarix -U 1 -A 2 -f /your/state_file_rc
that will disable any self-connection by guitarix.
This works when I give this as arguments in the nsm-proxy client, thanks
so far.
greets
hermann
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
5:42 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/29/2012 05:31 PM, rosea.grammostola wrote:
On 07/29/2012 02:00 PM, hermann meyer wrote:
Picture: http://pix.toile-libre.org/?img=1343576229.png
Am 29.07.2012 13:18, schrieb rosea.grammostola:
This becomes relevant imo when NSM support will be added to guitarix
On 07/29/2012 12:57 PM, rosea.grammostola wrote:
Maybe that is a bit confusing, but, connections are stored in the state
file (guitarix2_rc), not in the preset file (bank).
So, when you save a preset, no connections are stored, presets only
include the states of the controllers, (Knobs, sliders, selectors,
switchers, . . ) related to the engine.
When you quit guitarix, the current (UI) state will stored in the state
file, that including the connections.
The state file points to the preset file witch was last in use and load
it into the engine.
So guitarix will cover the last used state, before you quit guitarix.
Switch a preset file wouldn't change any connection.
Only if guitarix is controlled eg. started by jack-session manager, self
connection is disabled. Maybe NSM need a same behavior like jack-session
manager, I don't know? On 07/29/2012 05:47 AM, hermann meyer wrote:
> Am 29.07.2012 00:29, schrieb rosea.grammostola:
>> Is it possible to start guitarix with a specific preset via command
>> line? Then I could use it in NSM via the nsm-proxy client. Not so
>> nice
>> as full NSM support, but alas ...
>>
>> \r
> It is, it's a little tricky, . . . :-)
> The preset to load is given by the guitarix state file, . . .
> So, you can start guitarix with the -n parameter to give a name for
> the
> (jack)instance,
> example guitarix -n gx2.
> guitarix will create a own state file for guitarix:gx2, select the
> preset you will use, and quit guitarix.
> Now, when you would like to start guitarix with this preset, just
> start
> guitarix -n gx2. Create as many
> state files you need the same way, maybe guitarix -n lead, . . .
> rhythm,
> . . .
> If you use the name of the preset you like to load, you will have a
> cool
> overview of this stuff.
> The name given by the -n parameter is the name witch is used for
> connect
> to jack, so for connections you must take care to use the correct
> name.
>
> A other way is the -f parameter, . . .
> Select the preset you would use to start guitarix, quit guitarix,
> go to
> $HOME/.config/guitarix/
> and copy and rename the file guitarix2_rc to what ever you like
> (preset_name? _rc). Repeat that for any preset you need to start
> guitarix with. To load the state file, start guitarix with
> guitarix -f /were/ever/your/state_file/is_rc
Thx.
Does guitarix autoconnect to JACK? Afaik this is not proper practice
concerning JACK. Autoconnect might be an option but not the default and
it should at least be able to turn it off.
When using guitarix only or with a preset via nsm-proxy, guitarix
amp is
always connected to the outputs of my soundcard, where it should only
connect to guitarix fx right?
When I disconnect those outputs and save the session (and the
changes in
guitarix (this option is always available even when there are no
changes
made, which is kind of not logic to me)), when restarting the session,
every time those connections from guitarix amp to output soundcard is
back :/
\r
Ok, so it seems that if you save the preset state with the wrong
connections, it stays wrong forever. Changing ports in guitarix, and
then hit 'save changes' doesn't do anything anymore after restarting
guitarix with the preset. It works here when I unselect all the port
in guitarix and then save the preset. Then I can handle the
connections correctly in NSM (or guitarix itself if I run it outside
the session).
Anyway, this feels pretty cumbersome and technically not 100% correct.
Regards,
\r
A workaround could be to "fake" a
jack-session-call, when you use the -U
-A flags,
guitarix -U 1 -A 2 -f /your/state_file_rc
that will disable any self-connection by guitarix.
This works when I give this as arguments in the nsm-proxy client, thanks
so far. 
5:50 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/29/2012 05:42 PM, rosea.grammostola wrote:
On 07/29/2012 05:31 PM, rosea.grammostola wrote:
It seems it's possible to use Guitarix with the SIGUSR1
(http://ladish.org/wiki/level1) command to
http://pix.toile-libre.org/?img=1343576229.png
On 07/29/2012 02:00 PM, hermann meyer wrote:
Picture: http://pix.toile-libre.org/?img=1343576229.png
Am 29.07.2012 13:18, schrieb rosea.grammostola:
This becomes relevant imo when NSM support will be added to guitarix
On 07/29/2012 12:57 PM, rosea.grammostola wrote:
> On 07/29/2012 05:47 AM, hermann meyer wrote:
>> Am 29.07.2012 00:29, schrieb rosea.grammostola:
>>> Is it possible to start guitarix with a specific preset via command
>>> line? Then I could use it in NSM via the nsm-proxy client. Not so
>>> nice
>>> as full NSM support, but alas ...
>>>
>>> \r
>> It is, it's a little tricky, . . . :-)
>> The preset to load is given by the guitarix state file, . . .
>> So, you can start guitarix with the -n parameter to give a name for
>> the
>> (jack)instance,
>> example guitarix -n gx2.
>> guitarix will create a own state file for guitarix:gx2, select the
>> preset you will use, and quit guitarix.
>> Now, when you would like to start guitarix with this preset, just
>> start
>> guitarix -n gx2. Create as many
>> state files you need the same way, maybe guitarix -n lead, . . .
>> rhythm,
>> . . .
>> If you use the name of the preset you like to load, you will have a
>> cool
>> overview of this stuff.
>> The name given by the -n parameter is the name witch is used for
>> connect
>> to jack, so for connections you must take care to use the correct
>> name.
>>
>> A other way is the -f parameter, . . .
>> Select the preset you would use to start guitarix, quit guitarix,
>> go to
>> $HOME/.config/guitarix/
>> and copy and rename the file guitarix2_rc to what ever you like
>> (preset_name? _rc). Repeat that for any preset you need to start
>> guitarix with. To load the state file, start guitarix with
>> guitarix -f /were/ever/your/state_file/is_rc
>
>
> Thx.
> Does guitarix autoconnect to JACK? Afaik this is not proper practice
> concerning JACK. Autoconnect might be an option but not the default
> and
> it should at least be able to turn it off.
>
> When using guitarix only or with a preset via nsm-proxy, guitarix
> amp is
> always connected to the outputs of my soundcard, where it should only
> connect to guitarix fx right?
>
> When I disconnect those outputs and save the session (and the
> changes in
> guitarix (this option is always available even when there are no
> changes
> made, which is kind of not logic to me)), when restarting the session,
> every time those connections from guitarix amp to output soundcard is
> back :/
>
> \r
Ok, so it seems that if you save the preset state with the wrong
connections, it stays wrong forever. Changing ports in guitarix, and
then hit 'save changes' doesn't do anything anymore after restarting
guitarix with the preset. It works here when I unselect all the port
in guitarix and then save the preset. Then I can handle the
connections correctly in NSM (or guitarix itself if I run it outside
the session).
Anyway, this feels pretty cumbersome and technically not 100% correct.
Regards,
\r
Maybe that is a bit confusing, but, connections are stored in the state
file (guitarix2_rc), not in the preset file (bank).
So, when you save a preset, no connections are stored, presets only
include the states of the controllers, (Knobs, sliders, selectors,
switchers, . . ) related to the engine.
When you quit guitarix, the current (UI) state will stored in the state
file, that including the connections.
The state file points to the preset file witch was last in use and load
it into the engine.
So guitarix will cover the last used state, before you quit guitarix.
Switch a preset file wouldn't change any connection.
Only if guitarix is controlled eg. started by jack-session manager, self
connection is disabled. Maybe NSM need a same behavior like jack-session
manager, I don't know? A workaround could be to "fake" a
jack-session-call, when you use the -U
-A flags,
guitarix -U 1 -A 2 -f /your/state_file_rc
that will disable any self-connection by guitarix.
This works when I give this as arguments in the nsm-proxy client, thanks
so far.
9 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
Am 29.07.2012 17:50, schrieb rosea.grammostola:
Picture: http://pix.toile-libre.org/?img=1343576229.png
It seems it's possible to use Guitarix with the SIGUSR1
(http://ladish.org/wiki/level1) command to
Not really, when the command-line options -U -A involved, eg. in a
jack-session, even when it is faked, SIGUSR1 will be ignored, as well as
any other call to save state. Also preset saving is disabled in a
managed jack-session.
The only way then to save the state to file is, a call by the
jack-session handler.
Without -U -A, SIGUSR1 will indeed save the state (LADISH level1).
A other way to disable the self-connection of in and out-put ports are
the command-line options -i and -o, when you use them like that (space
between the quotation marks)
-i " " -o " "
in and out-put start unconnected, but the connection between amp and fx
client still will be made by guitarix.
greets
hermann
A workaround
could be to "fake" a jack-session-call, when you use
the -U
-A flags,
guitarix -U 1 -A 2 -f /your/state_file_rc
that will disable any self-connection by guitarix.
This works when I give this as arguments in the nsm-proxy client,
thanks
so far.
30 Jul
30 Jul
11:50 a.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/29/2012 09:00 PM, hermann meyer wrote:
Am 29.07.2012 17:50, schrieb rosea.grammostola:
It seems it's possible to use Guitarix with the SIGUSR1
(http://ladish.org/wiki/level1) command to
Not really, when the command-line options -U -A involved, eg. in a
jack-session, even when it is faked, SIGUSR1 will be ignored, as well as
any other call to save state. Also preset saving is disabled in a
managed jack-session.
The only way then to save the state to file is, a call by the
jack-session handler.
Without -U -A, SIGUSR1 will indeed save the state (LADISH level1).
A other way to disable the self-connection of in and out-put ports are
the command-line options -i and -o, when you use them like that (space
between the quotation marks)
-i " " -o " "
in and out-put start unconnected, but the connection between amp and fx
client still will be made by guitarix.
It's not that I really like this method, but for some it might be handy
to have Ladish l1 in NSM.
But this doesn't work here. Connections from amp out > soundcard are
still there
http://pix.toile-libre.org/upload/original/1343641711.png
> A workaround could be to "fake" a
jack-session-call, when you use
> the -U
> -A flags,
>
> guitarix -U 1 -A 2 -f /your/state_file_rc
>
> that will disable any self-connection by guitarix.
This works when I give this as arguments in the nsm-proxy client,
thanks
so far.
Picture: http://pix.toile-libre.org/?img=1343576229.png
greets
hermann
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
8:14 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
Am 30.07.2012 11:50, schrieb rosea.grammostola:
On 07/29/2012 09:00 PM, hermann meyer wrote:
Hi
Okay, I have add 2 new command-line options now, -J for disable
auto-connection, and -K for disable auto save state when quit. Try
--help-all for all options. Additional I have made the SIGUSR1 signal to
save state in any case, even when it's a jack-session. But you can use
it now like guitarix -J -K -n freebases for example and SIGUSR1 will
save the state. No more faked jack-session is needed.
Code is in our git repository. Get it with
git clone http://git.code.sf.net/p/guitarix/git guitarix-git
regards
hermann
Am 29.07.2012 17:50, schrieb rosea.grammostola:
Not really, when the command-line options -U -A involved, eg. in a
jack-session, even when it is faked, SIGUSR1 will be ignored, as well as
any other call to save state. Also preset saving is disabled in a
managed jack-session.
The only way then to save the state to file is, a call by the
jack-session handler.
Without -U -A, SIGUSR1 will indeed save the state (LADISH level1).
A other way to disable the self-connection of in and out-put ports are
the command-line options -i and -o, when you use them like that (space
between the quotation marks)
-i " " -o " "
in and out-put start unconnected, but the connection between amp and fx
client still will be made by guitarix.
It's not that I really like this method, but for some it might be
handy to have Ladish l1 in NSM.
But this doesn't work here. Connections from amp out > soundcard are
still there
http://pix.toile-libre.org/upload/original/1343641711.png
>> A
workaround could be to "fake" a jack-session-call, when you use
>> the -U
>> -A flags,
>>
>> guitarix -U 1 -A 2 -f /your/state_file_rc
>>
>> that will disable any self-connection by guitarix.
>
> This works when I give this as arguments in the nsm-proxy client,
> thanks
> so far.
Picture: http://pix.toile-libre.org/?img=1343576229.png
It seems it's possible to use Guitarix with the SIGUSR1
(http://ladish.org/wiki/level1) command to
9:27 p.m.
New subject: [LAD] The guitarix project release version 0.23.3
On 07/30/2012 08:14 PM, hermann meyer wrote:
Am 30.07.2012 11:50, schrieb rosea.grammostola:
On 07/29/2012 09:00 PM, hermann meyer wrote:
Hi
Okay, I have add 2 new command-line options now, -J for disable
auto-connection, and -K for disable auto save state when quit. Try
--help-all for all options. Additional I have made the SIGUSR1 signal to
save state in any case, even when it's a jack-session. But you can use
it now like guitarix -J -K -n freebases for example and SIGUSR1 will
save the state. No more faked jack-session is needed.
Code is in our git repository. Get it with Am 29.07.2012 17:50, schrieb rosea.grammostola:
It's not that I really like this method, but for some it might be
handy to have Ladish l1 in NSM.
But this doesn't work here. Connections from amp out > soundcard are
still there
http://pix.toile-libre.org/upload/original/1343641711.png
>>> A workaround could be to
"fake" a jack-session-call, when you use
>>> the -U
>>> -A flags,
>>>
>>> guitarix -U 1 -A 2 -f /your/state_file_rc
>>>
>>> that will disable any self-connection by guitarix.
>>
>> This works when I give this as arguments in the nsm-proxy client,
>> thanks
>> so far.
>
> Picture: http://pix.toile-libre.org/?img=1343576229.png
>
>
It seems it's possible to use Guitarix with the SIGUSR1
(http://ladish.org/wiki/level1) command to
Not really, when the command-line options -U -A involved, eg. in a
jack-session, even when it is faked, SIGUSR1 will be ignored, as well as
any other call to save state. Also preset saving is disabled in a
managed jack-session.
The only way then to save the state to file is, a call by the
jack-session handler.
Without -U -A, SIGUSR1 will indeed save the state (LADISH level1).
A other way to disable the self-connection of in and out-put ports are
the command-line options -i and -o, when you use them like that (space
between the quotation marks)
-i " " -o " "
in and out-put start unconnected, but the connection between amp and fx
client still will be made by guitarix.
git clone http://git.code.sf.net/p/guitarix/git guitarix-git
This seems to fine, thanks! You're getting closer and closer to full NSM
support, good job ;)
\r
http://pix.toile-libre.org/upload/original/1343675349.png
regards
hermann
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
3 Aug
3 Aug
11:44 a.m.
New subject: [LAD] The guitarix project release version 0.23.3
Am 27.07.2012 um 18:35 schrieb "rosea.grammostola"
<rosea.grammostola(a)gmail.com
:
Another feature suggestion, which you are aware of already, would be
adding NSM support, with the OSC functionality of NSM it should be
easy to switch between (effect processing) sessions in a live
situation.
+1
4293
days inactive
4300
days old
linux-audio-user@lists.linuxaudio.org
15 comments
3 participants
participants (3)
-
Burkhard Wölfel -
hermann meyer -
rosea.grammostola