search

sdatkinson / NeuralAmpModelerPlugin

Plugin for Neural Amp Modeler
MIT License
1.98k stars 132 forks source link

[FEATURE] Plugin description in the .nam file; visable in the plugin #225

Open BugZappr opened 1 year ago

BugZappr commented 1 year ago

The problem is that descriptions must always be in the filename currently. Amps can have tons of settings, and differences in hardware (e.g. tubes, output xformers, speakers, cabinets). While there is a dynamic community for models, most creators don't try to cram all the details of amp settings and hardware into the filename. Such names could be very long were they to be attempted.

I would hope the amp model creator might have a way to create a text description. An external editor might be nice, but of course, creators could also just edit the JSON. Alternately, if it doesn't swell the size of the plugin too much, a rich text description might be nice. Some users might like to be able to show or hide the description. Alternately, it might pop up over the existing GUI.

A text file could be distributed with .nam file libraries describing details of the sampling; but this could be tedious while browsing text files from various users. Having it in the plugin would save the trouble to jump from text file or web page to the next. One might hope for a way to see models in a list, and then either click on them, or use up and down arrows to not only read the filenames, but the descriptions.

As they begin to be used, it could help users greatly to categorize their models; and also understand them if they wanted the real amp. With such a feature available, it would encourage creators to describe the amps modeled better. If an amp were modeled without a particular feature engaged, a user could know that a model with that feature should be asked for or created.

sdatkinson commented 1 year ago

I definitely agree that the file name shouldn't be carrying so much weight. I'm hoping to use the "name" field as what's primarily displayed in the plugin (when it's available).

As far as the other info, I'm hoping for it to (1) be usable in library systems like ToneHunt as well as (2) be displayable in the plugin. Perhaps something like a "?" button for the model. Not sure yet.

BugZappr commented 1 year ago

The problems with relying on ToneHunt for that info are:

  1. It relies on one being online for it to work, which is not always the case for audio computers, or e.g. laptops at a gig.
  2. It is on a model library basis, not a per model basis. A per model basis allows the specification of e.g. tone and drive settings per model.
BugZappr commented 1 year ago

Note that what I have in mind shouldn't be just a single line of text. I suppose it might be a text box below the current GUI, which might or might not be hideable, or else a tooltop that pops up, giving you a generous amount of time to read it, as you hover over an item in a list, depending on what else gets implemented; but even if it's a text box that's fairly small, there should be enough room to accurately specify all amp, cab and pedal settings. It needn't be difficult to implement; but have adequate room for description.