User Posts

After some further digging, I'd say the term polarizer is a bit of a grey area in eurorack. When googling, I see several discussions on Modwiggler where people are debating whether the word polarizer is equal to inverter OR attenuverter.
The brand Doepfer consistently uses the term polarizer only in the context of attenuverters.
If search for the keyword "polarize" in the free text input field here to search for modules that have that text somewhere in the title or description, it only shows modules with attenuverters.
On the other hand, if I search for the function "Polarizer", it also shows modules that only have an inverted out and no attenuverter, which is in line with using polarizer as synonym for inverter.

I guess if everybody would agree on only using the terms attenuverter and inverter from now on (and abandon the word polarizer), there would not be any confusion, but that is probably never going to happen :-)

Suggestion: add 'Inverter' to the list of available options for module functions.
-- MPCman

it's already there, although not as 'Inverter' - Polarizer - means the same thing
-- JimHowell1970

Thanks for mentioning that. Interesting, I thought that polarizer was synonym for attenuverter, but it apperantly is not :)
It looks like there are currently a lot of modules with inverter/polarizer functionality that do not have that Function label in the database.

Suggestion: add 'Inverter' to the list of available options for module functions.

I think it would be cool if modules could be linked to eachother, with relations such as:
- is a clone of /is cloned by
- is an imitation of/is imitated by
- is an extender for/is extended by
Etc.

Then for example, on the module page of the original Mutable Instruments Plaits, you could show:
- list of all existing clones of the module
- list of any clones that are for sale
- link to a search query in the module finder for modules with a certain relation to the Plaits. You can then further narrow down your search by say height or width.

Edit: I was thinking a bit more about this, we could also consider modules that there is a newer version of a certain module. Then there are also modules that contain functionality from other modules, i.e. the Disting EX does everything the Disting mk4 does, but it is not simply the Disting mk5. The Disting EX can also use MI Braids and Plaits engines but it is not a clone of these either. To consider whether new module versions are an instance of this 'generic' module relation, or a separate attribute type.

EDITED Aug 18th 2023, 15:05

I have no reason to post a public rack.