Consider inverting the range of some parameters for consistency with other modules

[federicobond]

Parameters like attack and release are mapped from slower to faster, which is counterintuitive when compared to most other envelope generators in modular systems. Inverting them may improve the module usability.

[diegodorado]

I understand... it is indeed counterintuitive... but for those who know ym2612 it would be weird ... should I add a "intuitive envelopes" global switch?

[federicobond]

I think it depends on what your goals with the CV2612 module are. Is the aim to expose a raw interface to the chip emulation parameters as a VCV module or something that can sit comfortably within the standards of the rest of the platform and produce sounds based on the YM2612 chip?

I'd argue that >99% of your user base will not know the low-level details of the YM2612 chip interface, but they would like to get some good sounds out of it, and would appreciate that knobs follow the standard modular semantics.

As an example, think about those old SoundBlaster keyboards. They exposed just a thin interface on top of the chip capabilities, yet the faders would follow standard conventions for musical instruments (faster attack below, slower above) because the way these parameters are encoded is just a technical detail.

[greggel1]

I have just played around with this great piece of work and found myself struggling with this issue. As this is an emulation, i must admit, it should be controlled like the original hardware. As a user without a clue about the hardware i had a bad experience at first. Adding "original envelopes" and "default original envelopes" (default off maybe) toggles to the context menu. Using the toggle could inverse the desired parameters. This would help new users to go deep with the module and having a nice trip 💃