One example is the plugin sforzando from the vendor "Plogue Art et Technologie, Inc": I did not yet encounter a plugin with special characters, as such I couldn't test it." "Right now, it's unknown if special characters (anything else than a-z, 0-9, dashes, and underscores) must be replaced or ignored. When you load the plugin images do show up (see above). If the vendor name contains special characters the images do not show up in the preset browser.
This is true for both the folders image\\\ as well as image\\ģ. It did not make any difference if I renamed the. You wrote: "Note that the meta file must be named the same as the directory." I could not confirm this. Images now appear when loading the plugin. removing special characters, concatenating MD5 hash) did the trick. Adding the image directories as per your findings for those plugins with special characters in the dll filename (i.e. Are they associated just by the vendor name and reported plugin name? If the latter was then I think I could change the filename (question above) without having to recreate the presets.Ĭ) Even if I have to recreate the presets: Can I keep the audio previews?ġ. Questions: If I was to change the dll filenames for my existing plugins like described aboveĪ) Would I be able to keep the already created nksf files or should I re-create them with PresetMagician?ī) How is the plugin dll file associated with the nksf? Form the He圎ditor view it seems that nksf files do neither contain the plugin ID nor the file name. In that way there is the lowest risk of name/path confusion. On the other hand, for new plugins, it seems that it would be advisable to first check with PresetMagician what the plugin reports as its name and then change the filename of the dll to exactly that and finally to analyze and generate the presets. I am a bit worried that if I change the filenames of the dll I might break something or have to regenerate all the nksf, previews etc again. Reason: Despite of the fantastic help of PresetMagician it still took me some time to get all my user presets (thousands) neatly organized with tags, previews etc. If possible I would prefer keeping my current dll filenames (quite a few have special characters like "(圆4)" or "_") and rather updating image directory names rather than changing the dll filenames.
(Maybe) related question: Have you figured out how the data following "uuid" in the nksf file relates to the plugin? Is this some checksum/hash over the plugin ID or even the actual plugin file?Ĭlick to expand.Thank you, Felicia, for the speedy reply! I will check out your findings and report back if I can confirm them on my machine too. only works in specific situations which makes it appear the filename was the root cause but in reality it is buried deeper.) It somehow appears to be a mix of filename and embedded data in nksf files (maybe it sometimes works in certain constellations due to fallback mechanisms which obfuscates the real culprit, say: nksf file would require a tweak but KK somehow compensates this problem via filename matching.
I tried renaming the dll file names, tried different image folder names (both vendor as well as plugin specific folder) etc - but very limited success. I have a bunch of plugins where the images don't show up in KK's preset browser or - even if they do - once you load the plugin they do not show in the plugin view (KK keyboard Mk2). Rather focus on improving the auto generation and storing the correct data in nksf file, making sure that folder names, plugin file names etc allow KK to find the resources. Click to expand.I agree you can reduce complexity by eliminating the upload feature.
0 kommentar(er)
