Conquistador.
ConquistadorThe Kjearhus GEQ plugins don’t show up properly in the Device Mapping Panel in Podium. The mono version for instance should show up as GEQ-7M and the Stereo version as GEQ-7S. Currently they both are named GEQ-7. Having both of them in the same project is a sure way to get confused as to which is which…any idea why Podium is not naming them properly ❓
The GEQ plugin variations are named correctly in Tracktion for instance.
ZynewaveIt must be Tracktion that appends the M and S to the plugin name.
Conquistador@Zynewave wrote:
It must be Tracktion that appends the M and S to the plugin name.
That may well be, but ACID and Ableton Live also do this. This suggests that something is different about Podium’s naming process for plugins that share the same name with a slight variation.
Of course you will know far better than me as to why this might be but for now all the other hosts I have tried (Tracktion, Live and ACID) all name the GEQ -7 plugs correctly. 😐
ZynewaveDownloaded, tested and confirmed. Could it be that the hosts you say display the names correctly are showing the plugin filenames? When Podium requests the name from the plugin, the same “GEQ-7” string is returned from all three variants. I have emailed Torben with a few questions about this.
Conquistador@Zynewave wrote:
Downloaded, tested and confirmed. Could it be that the hosts you say display the names correctly are showing the plugin filenames?
Unless our interpretation of ‘filename’ in this instance is different it does seem that each of the three hosts I tested the GEQ plugs with, are showing the actual file names GEQ7M and GEQ7S.
When Podium requests the name from the plugin, the same “GEQ-7” string is returned from all three variants.
Puzzling. ❗ That means that the other three hosts are reading something else in the file name or .dll file that Torben has placed there to identify his plugin variants. Somehow Podium is receiving only ‘part’ of the information Torben has made available to be read by a host. 😐
I have emailed Torben with a few questions about this.
Thanks, I am very interested to see what his response is.
ZynewaveSomehow Podium is receiving only ‘part’ of the information Torben has made available to be read by a host.
I don’t think that is the case. My guess is that the other hosts simply show the filename (minus the .dll extension) and ignores the effect name provided by the plugin. If you rename the filename of one of your plugins, does the plugin appear in your other hosts with the renamed filename?
ConquistadorThe plot thickens it seems because I just tried your suggestion and renamed the GEQ7M plug to GEQ7M test.
Guess what? Live and Tracktion did indeed show the plugin as ‘GEQ7M test’! Podium still imported the renamed file as just GEQ-7. ❗
I noticed something else which may help identify the problem here…Podium is naming the plug in with the hyphen “-” while the others are not ❓ ❗ ❓
They name it GEQ7S, Podium names it GEQ-7 with the hyphen inserted for each variant of the GEQ plug, but it still can’t ‘see’ the S and M file names that the other hosts ‘see’.
Tracktion and Live indeed, appear to be using the filename, but Podium is picking up a different name with a slight difference for the plug. Maybe Torben has used an interpretation of the VST spec in the development of the GEQ 7 plug that you have not come across yet in Podium? I guess only he can answer that.
In any case Podium is interpreting the file name differently from all the other hosts I have tried. Torben clearly wanted them to show up differently to avoid the obvious confusion that would follow if he did not add the letters M and S to his Stereo and Mono variants of the GEQ plug.
Somehow Podiums scanning process has not yet encountered this kind of plug in yet. Perhaps this is why it ‘sees’ the GEQ7 plugs differently, even though the GEQ-7 string is still being returned from all three variants as you mentioned earlier.
Just guessing as to what mght be the cause of a somewhat strange problem.
ZynewaveThere is nothing mysterious here. The VST spec provides a function called getEffectName() which the host can use to query the plugin for the effect name. This name is not related to the filename, but most plugins will return the same effect name as the plugin filename. It seems the hosts you tested ignores the effect name returned by the plugin, and instead uses the filenames.
In Podium I name the imported mappings after the effect name rather than the filename, because this in most cases provides a more accurate name. E.g. the “LPLL2.dll” plugin is imported as “LALLAPALLOOZA lite v2” because that is the effect name returned by the plugin.
The hyphen in the “GEQ-7” is there because that is the effect name returned by the plugin. So the GEQ-7 plugin is an example of a plugin that returns an effect name that is different from the filename. Unfortunately in this case the filename provides more information than the effect name. My advise is that you rename the imported GEQ-7 mappings and add the S and M manually.
ConquistadorCheers Frits. While I am still very interested in Torbens response your suggestion at least provides me with a work around for now.
Thanks 8)
ZynewaveTorben has sent me a short reply:
“The name is only defined in one place and is used for various things, such as copy protection, so therefore it is the same for all three variants”.
Conquistador@Zynewave wrote:
Torben has sent me a short reply:
“The name is only defined in one place and is used for various things, such as copy protection, so therefore it is the same for all three variants”.
Interesting. That means that all the other host I tried the GEQ -7 in, use a different naming process. Straight from the .dll file name.
Torben is talking about the name that is returned when a host asks for it (I think) which Podium is picking up correctly, he must know (I think he uses Cubase) that they will appear differently in most hosts perhaps Cubase as well.
I suspect he might not have come across this kind of problem before as other hosts will identify each plug based on the name of the .dll file. Don’t know why but clearly that is what is happening.
Podium is apparently doing nothing wrong. I guess I will just have to rename the plugs in my default project template, to avoid having to do it each time. That should side step me having to face the problem again.
Thanks for posting his response. I am not a developer but sometimes the multi layered interaction of hosts (VST, VSTi, driver, sub host, OS) means it is sometimes useful to know why something is different to everything else to avoid a similar problem later. 8)
Thanks for looking into it! 8)