Plugin development philosophy

Programming applications for making music on Linux.

Moderators: MattKingUSA, khz

User avatar
Impostor
Established Member
Posts: 1392
Joined: Wed Aug 17, 2022 1:55 pm
Has thanked: 148 times
Been thanked: 366 times

Re: Plugin development philosophy

Post by Impostor »

Michael Willis wrote: Sat Oct 07, 2023 6:44 pm
Impostor wrote: Sat Oct 07, 2023 6:30 pm

Which reminds me of a question I haven't yet asked: is there a way for a user to rename plugins?

Sure, if you have the source code. Just modify it and recompile. Free as in freedom fries.

So not simply editing a .ttl file somewhere?

User avatar
Michael Willis
Established Member
Posts: 1460
Joined: Mon Oct 03, 2016 3:27 pm
Location: Rocky Mountains, North America
Has thanked: 71 times
Been thanked: 169 times
Contact:

Re: Plugin development philosophy

Post by Michael Willis »

Impostor wrote: Sat Oct 07, 2023 6:55 pm

So not simply editing a .ttl file somewhere?

The LV2 ttl does not specify the plugin name and VST3 doesn't have a ttl file. I'm not certain about other plugin formats.

Kott
Established Member
Posts: 821
Joined: Thu Mar 21, 2013 12:55 am
Location: Vladivostok
Has thanked: 65 times
Been thanked: 124 times

Re: Plugin development philosophy

Post by Kott »

Michael Willis wrote: Sat Oct 07, 2023 7:01 pm
Impostor wrote: Sat Oct 07, 2023 6:55 pm

So not simply editing a .ttl file somewhere?

The LV2 ttl does not specify the plugin name and VST3 doesn't have a ttl file. I'm not certain about other plugin formats.

I'm not an expert, but:

LV2 ttl has doap:name field which exactly contains a name of plugin
VST3 (since 3.7.5) has optional moduleinfo.json which contains name also, but it's not intended for such tricks afaik

User avatar
Michael Willis
Established Member
Posts: 1460
Joined: Mon Oct 03, 2016 3:27 pm
Location: Rocky Mountains, North America
Has thanked: 71 times
Been thanked: 169 times
Contact:

Re: Plugin development philosophy

Post by Michael Willis »

Kott wrote: Sat Oct 07, 2023 7:50 pm

LV2 ttl has doap:name field which exactly contains a name of plugin

Wow, look at that, it actually worked. I was looking at Dragonfly Hall Reverb, I didn't see it the manifest.ttl and the DragonflyHallReverb_ui.ttl, but in the DragonflyHallReverb_dsp.ttl file there is the doap:name field, and modifying it does indeed rename the plugin from the DAW's point of view.

User avatar
Michael Willis
Established Member
Posts: 1460
Joined: Mon Oct 03, 2016 3:27 pm
Location: Rocky Mountains, North America
Has thanked: 71 times
Been thanked: 169 times
Contact:

Re: Plugin development philosophy

Post by Michael Willis »

@GMaq or anybody else who uses TAP Tubewarmth or Calf Bass Enhancer, do you tend to set it for more tube-style or tape-style saturation, or somewhere in the middle, or do you use a variety of settings depending on context?

Calf Bass Enhancer uses the terms "2nd" and "3rd" harmonics for tube and tape, respectively.

User avatar
GMaq
Established Member
Posts: 2831
Joined: Fri Sep 25, 2009 1:42 pm
Has thanked: 530 times
Been thanked: 574 times

Re: Plugin development philosophy

Post by GMaq »

Michael Willis wrote: Sat Nov 11, 2023 4:08 pm

@GMaq or anybody else who uses TAP Tubewarmth or Calf Bass Enhancer, do you tend to set it for more tube-style or tape-style saturation, or somewhere in the middle, or do you use a variety of settings depending on context?

Calf Bass Enhancer uses the terms "2nd" and "3rd" harmonics for tube and tape, respectively.

Hi,

I use the Tube type exclusively personally as I'm usually looking to 'brown' the sound up rather than do tape emulation.. Tape is a pretty complex thing to do I think, hence Plugins like Uhe Satin or NeuronTape which have a lot of parameters to tweak and secondary transport related controls like wow and flutter etc..

I usually have Tap Tubewarmth set between 6.5 - 10.. 6-7 for Vocals and 8-9 is magic on bass guitars and Hammond organs.

Post Reply