CALF plugins?

[kamiluni]

Hi all,
does anyone know if Calf plugins are still developed or has been abandoned?
Taking a look into the git repo everything seems stopped 2 years ago.

thx
KL

[bluebell]

Unfortunately I don't see any development, either.

But isn't that what we all want? Using software instead of continuously updating?

I like those plugins very much. Easy to use, good sounding, not too CPU-hungry.

[novalix]

Some more metadata:

• The last status tagged as a "release" is four years old

• 2019 happens to be the last year with a somewhat steady stream of commits to the src directory

• The maintainers (@boomshop) last appearance in the discussions about open issues is three years ago

So yes, the project is pretty much abandoned.

[elcalen]

But isn't that what we all want? Using software instead of continuously updating?

I like those plugins very much. Easy to use, good sounding, not too CPU-hungry.

Sadly, because they still depend on GTK2, they don't work with many newer DAWs that are linked with newer GTK versions. (REAPER, for example.)

[bluebell]

But isn't that what we all want? Using software instead of continuously updating?

I like those plugins very much. Easy to use, good sounding, not too CPU-hungry.

Sadly, because they still depend on GTK2, they don't work with many newer DAWs that are linked with newer GTK versions. (REAPER, for example.)

One more argument against the use of software that you can't compile/link by yourself.

The most recent version of Qtractor works fine with those plugins. Both self-compiled.

[kamiluni]

I'm using and I like these plugins very much...but if it is unmaintained its future is quite signed!
as long as they work... it's fine

[tavasti]

Sadly, because they still depend on GTK2, they don't work with many newer DAWs that are linked with newer GTK versions. (REAPER, for example.)

One more argument against the use of software that you can't compile/link by yourself.

The most recent version of Qtractor works fine with those plugins. Both self-compiled.

Biggest problems here are:

• Plugins that depend on heavy gui libs, like GTK, Qt, etc
• Plugins that aren't staticly linked

Even if you have source code of plugin or DAW, you can't rebuild it with different major version GTK. Or if that is so simple, just rebuild those calf plugins with GTK3? Good luck with it

[elcalen]

Also you can't assume that every musician is an IT engineer.

[kamiluni]

anyway, CALF is very used and IMHO it would have been a nice gesture on the part of the developers to say that they are no longer following the project... just out of politeness, that is.

[Audiojunkie]

But isn't that what we all want? Using software instead of continuously updating?

I like those plugins very much. Easy to use, good sounding, not too CPU-hungry.

Sadly, because they still depend on GTK2, they don't work with many newer DAWs that are linked with newer GTK versions. (REAPER, for example.)

I believe this is the key reason CALF plugins are being abandoned. There is a LOT of work involved in switching to something else, and it would be nearly as easy to just start over.

[Audiojunkie]

Sadly, because they still depend on GTK2, they don't work with many newer DAWs that are linked with newer GTK versions. (REAPER, for example.)

One more argument against the use of software that you can't compile/link by yourself.

The most recent version of Qtractor works fine with those plugins. Both self-compiled.

Biggest problems here are:

• Plugins that depend on heavy gui libs, like GTK, Qt, etc
• Plugins that aren't staticly linked

Even if you have source code of plugin or DAW, you can't rebuild it with different major version GTK. Or if that is so simple, just rebuild those calf plugins with GTK3? Good luck with it

Yes! This exactly! I hadn't seen your post when I responded. Sorry that I repeat a lot of what you already said.

[funkmuscle]

Calf is a great plugin suit. I'm surprised that Falktx or someone like that haven't continued it.. Same as these eq10q.

Thank goodness we have Vladimir and his LSP... They are superb!!

[tavasti]

anyway, CALF is very used and IMHO it would have been a nice gesture on the part of the developers to say that they are no longer following the project... just out of politeness, that is.

Is it known that developer is still alive? And sure, thinking 'I will continue that when this rush is over'. If that rush is for example kids, there can be 10-20 years of rush

[bluebell]

Biggest problems here are:

• Plugins that depend on heavy gui libs, like GTK, Qt, etc
• Plugins that aren't staticly linked

Even if you have source code of plugin or DAW, you can't rebuild it with different major version GTK. Or if that is so simple, just rebuild those calf plugins with GTK3? Good luck with it

It's not easy to foresee problems. But I guess it's no secret that gtk2 and gtk3 cannot simply coexist in the same process.
Solution: Don't use gtk3 for DAWs and plugins.

[folderol]

Biggest problems here are:

• Plugins that depend on heavy gui libs, like GTK, Qt, etc
• Plugins that aren't staticly linked

Even if you have source code of plugin or DAW, you can't rebuild it with different major version GTK. Or if that is so simple, just rebuild those calf plugins with GTK3? Good luck with it

It's not easy to foresee problems. But I guess it's no secret that gtk2 and gtk3 cannot simply coexist in the same process.
Solution: Don't use gtk3 for DAWs and plugins.

Add to that, gtk4 is just around the corner