guitarix and LADSPA

[brummer]

Hi

For those always interested in the latest development, I like to let you know that we have included LADSPA support into guitarix now. Supported are mono/stereo plugs only.
Additional there are some new internal plugs like a tubescreamer, a expander, a new flanger model, a mono convolver, . . .
If you like to check out our git repository,

Code: Select all

git clone http://git.code.sf.net/p/guitarix/git guitarix

don't forget to give feedback.

greets
brummer

[funkmuscle]

dude, will test when I get home for sure!

[luckylud]

Hi there,
Thanks a lot for this work brummer

I'm on ubuntu 12.04 with kxstudio repo,
I don't know if it's the good place to post my message ... so sorry if it's not.

After the last update of guitarix, Rosegarden crash on my station ...
After some web search and some testing, I found the guilty ! It's ... :
/usr/lib/ladspa/ladspa_guitarix.so

If I remove it, rosegarden start correctly.

It's just for information if someone have the same problem with rosegarden.

[brummer]

Hi luckylud

Welcome on board.
Thanks for the report, well, this bug is fixed in version 0.22.4.
Maintainer for guitarix in KXStudio is AutoStatic. Here on Board is a special section for KXStudio users, with a tread about guitarix, maybe you can report it there as well, so that AutoStatic find it easy, and maybe update the guitarix package for KXStudio.
http://www.linuxmusicians.com/viewtopic.php?f=47&t=8129

greets
brummer

[autostatic]

Guitarix has been updated to 0.22.4 in the KXStudio repository.

[luckylud]

Thanks AutoStatic, I've update guitarix and rosegarden doesn't crash anymore at startup

Thanks brummer, it's a good place here, with lot's of interesting topics and peoples.

Musicalement,

Luckylud

[studio32]

Would it be possible to support the JACK-RACK presets (*.rack). Those are just LADSPA plugins. Would be handy, not sure if it's possible or not.

And yes, please add NSM support. I see myself having fun when Guitarix and Rakarrack would have NSM support

[brummer]

Hi

DSSI wouldn't be a solution here, guitarix support already per effect pre-sets, as well as external UI's for LADSPA or internal plug-ins. We handle plug-ins (for now LADSPA, external guitarix plugs or internal plug-ins) over our own plug-in API, witch makes this possible. LADSPA plugins get wrapped to it, and the missing features get added.
Also, our LADSPA load widget gives advanced users the possibility to have a high influence on the UI for the selected LADSPA plugin, additional users can create a UI for any plug-in with glade if they wish. Otherwise guitarix create it automatic.

Anyhow, the problem with jack-rack pre-sets is on a other sheet, guitarix simply only support mono or stereo plugs, means only plug-ins with equal in and out-put ports not more then 2. are supported.
Guitarix itself could be simplified seen as 2 racks, a mono rack, followed by a stereo rack. So, mono plug-ins could only loaded into the mono rack, stereo ones into the stereo rack. Now, even if we could wrap jack-rack pre-sets to the guitarix pre-set format, loading will fail in most cases, because we can only load mono plugs before stereo ones, and cant load other plugs with non-equal or more then stereo audio ports.

To the NSM support, sorry Rosea, it's like I said in the other thread, I have nothing against add support for it, only my interest in it is low, so a patch will be welcome, as well as project members to implement it.

We have add LADISH support in a early state of the LADISH development, now we are marked as broken, because LADISH cant handle multi client apps. We have add jack-session support as well in a early state of the session API, now, it seems that development of jack-session is dead, and NSM comes in the game. Well, before I invest time in it, I will see if it becomes stable, otherwise, I have a bunch of other stuff on the to do list for guitarix already.

greets
brummer

[studio32]

@Brummer, I understand your POV at this moment. Afaik NSM is stable though, the fact that the last changes are still in the 'next' branch are due to the fact that non-daw and non-mixer aren't ready for the master branch yet. Atm NSM has been added to Azr3-jack and Petri-Foo as well.

Ok, Guitarix is now a mulitple client app? This makes it's situation comparable with non-mixer? Is Jack-session able to handle the new multiple client situation? Jack-Session can't handle non-mixer ...

Another reason why NSM is the best option for Guitarix imo, it that's it's able to switch between sessions (quickly) in a live situation (using OSC). I can imagine the use of different 'effect processing sessions' (with guitarix only or with another app (rakarrack and or non-mixer)) in a LIVE situation. Correct me if I'm wrong.

Concerning Jack-rack, I'll rewrite my favorite presets in non-mixer or in Guitarix (when it has nsm support). Nice that Guitarix has the LADSPA possibility now

[brummer]

Is Jack-session able to handle the new multiple client situation?

Yes, it need some quirks by implementation, but it work's well. Also LADISH will support Multi Clients (over Jack-session), when it have add support for Jack-session, at least that is what Nedko told me.

Another reason why NSM is the best option for Guitarix imo, it that's it's able to switch between sessions (quickly) in a live situation (using OSC). I can imagine the use of different 'effect processing sessions' (with guitarix only or with another app (rakarrack and or non-mixer)) in a LIVE situation. Correct me if I'm wrong.

Concerning Jack-rack, I'll rewrite my favorite presets in non-mixer or in Guitarix (when it has nsm support). Nice that Guitarix has the LADSPA possibility now

Well, I'm not against NSM, only I didn't use it, and I have a full todo list right now. So, . .
But I hope you enjoy guitarix even if it didn't fulfill your needs.

[studio32]

Given the fact that you can use jalv to use LV2 plugins as standalone JACK application, isn't having apps like Guitarix as LV2 plugins even more useful and more future proof? I start to think more and more it is ...

[brummer]

What is guitarix?
It is a effect host, a module sequencer. It's designed for fast module load/unload handling.
Effects get ramped up and down when loading, to avoid any unwanted pop or noise. Some plug-ins need special values to send to, to avoid noise. The amp, for example, long time guitarix users may remember this pop sound when switch a amp model. I guess anyone know this from a real amp when switch it on.
What is guitarix made for?
We have live usage in mind. So fast preset switching and proper midi cc support is given.
Are there any plans to port guitarix plug-ins to LV2?
Not that I know. I'm myself wouldn't do that, as far I know also Andreas haven’t a interest in do that. But guitarix is a Open Project, I cant say if one day a developer join the project to port guitarix plugs to LV2, than be it.

[brummer]

Making the current LADSPA plugins work as LV2 would be pretty trivial since LV2 is based on LADSPA.
Getting the UIs and presets to work though, it's a different story...

The LADSPA plug-ins become more ore less unrelated/outdated by time, and have not much to do with the stand alone app any more. I guess they are no worse to port to LV2.
A exception is ladspa_guitarix.so which is a (experimental) wrapper for the guitarix engine to ladspa, to run the engine headless.

To the UI, we have outsourced all used widgets to a gtk+ library, and created a gtkmm wrapper library which we use to create the UI. So reuse of the guitarix UI elements will be a easy task. Additional we provide a python wrapper and Glade support for the library.