guitarix<=>gx_head

[brummer]

the guitarix project have released gx_head, I wont to make some clarifications.

guitarix and gx_head use the same SVN repository and based on the same source, but you can safely install both versions parallel if you wish.
But never mixed up SVN versions with released versions, because in SVN guitarix and gx_head shared some installation paths were in released versions the install paths are split’s, to avoid package conflicts.
So when you use SVN you can build/install both versions from the same source tree, when you use released versions you can build both from it's own source tree, that's it.

greats brummer

[StudioDave]

Is there an advantage to using one or the other ? Is gx_head planned to replace guitarix or will they continue as separate projects ?

Just curious about it.

Best,

dp

[brummer]

Good question , I don't know

. . . if gx_head ever replace guitarix, they live in the same source repository, but development goes at time only in gx_head. I'm myself only use gx_head. But those who have involved guitarix in a project, witch they are working on, would prefer to hold guitarix. For that case I would say, you could safely install both.

For me, gx_head is a step back to the roots, to develop a OpenSource guitar tube amplifier simulation and it is in many cases match better then guitarix, that starts in the amp simulation, goes over the plugin handling to the convolver settings.
Just try it out and you will see what I mean.

So why it have a new name and didn't be simply the next guitarix version ?
Because it isn't backward compatible, You can't reuse the old prestets, nor can you reproduce the sounds of guitarix when you try the same settings, so we give the beast a new name to avoid confusion for those how already use guitarix. This is the head (heart) of guitarix, it's a beast, comes with new internal plugins witch wasn't in guitarix before, other parts be completely removed. First I think about to call it something like guitarx2, but damned, gx_head is the short for guitarix amp head.

How ever, if somebody ever would do future development on guitarix, it's free, also gx_head is a free project, living in the same source repository, so I cant say what the future brings, I don't know. . . . .

[GMaq]

Hi Brummer

gx_head looks and sounds great! Very nice work. If you recall I used to build guitarix packages with your included Debian script for AV Linux until Debian started doing it themselves. In the meantime I have been able to build gx-head also but I forget how to change the ./waf configure line in the Debian rules to build an architecture independent package to distribute. If you don't mind could you remind me what voodoo magic is required?

Thanks, keep up the great work!

[brummer]

Hi GMaq

Glad you like the new guitarix-head.

If you don't mind could you remind me what voodoo magic is required?

I have simplified this behaviour .
This time, no voodoo is needed, I have set up the debian/rules already to create a architecture independent package.
To create a architecture depend binary, the configure flag --optimization could add to line 20 in the rules.
Great that you like to push debian binary's

greats brummer

[Scary Hallo]

But never mixed up SVN versions with released versions, because in SVN guitarix and gx_head shared some installation paths were in released versions the install paths are split’s, to avoid package conflicts.

But what can I do if I did?
I wish to use the svn version

[brummer]

But what can I do if I did?
I wish to use the svn version

Use only one or the other, when you wish to use the SVN version, simply run ./waf uninstall from the package source tree as root. Then install the SVN version. The same work in the other direction.
No problem, when you have install one over the other, just remove the one you don't will use, and install the other again.
Reason is the modified install path for the package versions, in SVN both, guitarix-classic and gx_head is one package, as release they are spliced into two packages, therefore they need other install paths.

But anyhow, a release is always a capture from the SVN, only modified for install path, so you will nothing loose when using SVN only.

[Scary Hallo]

Thank you!