acousmodacousmodJust curious, what are the next new features/improvements on your list Frits?
Time-stretching perhaps ? 😉 (at least I hope so…)
acousmodAdded support for the VST setSpeakerArrangement function. Insert mappings will be created for each supported speaker configuration. Plugin scanning now detects surround configurations and automatically creates surround insert mappings instead of multiple stereo pair mappings.
😛 😛 😛
Updated the zPEQ and zPitch VST plugins to support up to 32-channels surround setups.
Wonderful !!!
Thanks !
acousmodThere were no feedback on the beta6, so I take it that noone saw an improvement with this option.
I have not made extensive tests, but I have seen no difference too.
Other subject, concerning the final 1.97, do you confirm that the ZPitch plugin will be multichannel like the EQ ? (it will be a great help for my current work)
acousmodI’m not too happy with that. It would mean that importing a stereo-only multiple output instrument will create a useless surround mapping, which may confuse users that only work in stereo.
Yes, I understand.
Absynth4 and Cronox3 are the only surround capable instruments I know of. Can you list other surround instruments?
I agree that they are quite few and that it will not help a lot of people…
Reaktor (8), Kontakt (16), CrusherX (10), Independence (9), MachFive (6 ?), GigaStudio (?), Halion (combination of stereo and 5.1), and of course my little toys 😉
Forget it !
acousmodYes, it is not your fault.
I will ask the the developper if he can correct it.
Thank you for all Frits !
It is now really a pleasure to import plugins 😛
Perhaps a small request if I dare…
Could you eventually add also a multichannel mapping for instruments who have multiple outputs together with the stereo one ?
acousmodI think Podium now will import all multichannel plugins correctly as inserts. Let me know if there still are plugins that are not recognized as multichannel.
All plugins are now well recognized, including ambisonic and Pluggo made, except the 8 channel versions from Acon : Studio Necessities and Studio Clean.
http://www.acondigital.com/us_StudioNecessities.html
I think that they are linked to an ini file or something like that.
Please try enabling the new option and let me know if you notice any change at all in CPU spikes, or if you find plugins that behave badly with the new option enabled.
I will try…
acousmodThe beta4 zip also includes an updated zPEQ dll that supports up to 32 channel processing. With the new speaker arrangement support in Podium, this single dll can be used both for mono/stereo and surround processing.
I have dreamed of it, Frits has done it 😛
Marvelous !
I’ve also further trimmed the creation of alternative surround mappings during import. Now only mono, stereo and all-channel mappings are created for plugins that seemingly support all possible speaker arrangements.
I think that it is perfect now.
There is no change for the plugins that are not recognized as multichannel (the list in my previous post).
Is this because you are yet working on it or because it is not possible ?
acousmod2. The Outputs and Busses folder separate to Inputs. Again, wouldn’t it make sense to house these with the Inputs area? The outputs in particular are changed infrequently – whenever I go to the VST Mapping area I have to also encounter outputs and busses. These are small things I know, but why not have a section for structural objects like in’s, out’s and busses, and a distinct plugins compartment?
200 % agree ! 😉
The subject has been already tackled, perhaps that it will have some effect eventually ?
acousmodIf the plugin reports that it supports all the speaker arrangements that Podium tries to set, Podium will now assume that the plugin reports “technically” possible configurations, instead of “sensible” configurations. Podium will then create a reduced set of sensible mappings, e.g. 5.0 and 7.1 configurations are discarded.
Very good !
But it seems that some are not well discarded :
– I have yet 9 mappings for PristineSpace, only the 5.0 has disappeared
– Respatializer shows all the mappings like before. But perhaps is this because we can select the speakers arrangements inside the plugin ?
– Bidule VST with 16 or 32 channels shows well the 16/16 or the 32/32 mappings, but also : Mono, Mono/Stereo, Mono/5.1, Stereo, Stereo/5.1, 5.1, and curiously there is no 7.1.
If you’ve enabled the surround import option, Podium now also creates surround mappings instead of stereo pair mappings for multi-channel effect plugins that does not support the setSpeakerArrangement function.
Excellent !
It works now with Upmix, Wizooverb W5 and Reaktor as FX.
But it seems that it doesn’t work yet with some others :
– those exported with older versions of Synthedit and which have more than 8 channels (but it is perfect with all others)
– Toby bear DMO bag with more than 8 channels
– Crusher3 FX (10 channels)
– the Flux bundle
– all ambisonics
– all the Acon 8 channels plugins
Thank you for all your efforts. I suppose that it must not be simple to deal with all the different ways of doing that are used around the VST specs…
acousmodFrits,
Please, can you suppress the automatic creation of “secondary” surround mappings ?
I mean all the mappings that have less channels than the plugin ?
For example, when I import PristineSpace with the beta 2, Podium creates 12 mappings from which only the last three ones correpond to something really usable.
Like in nearly all multichannel effects plugins, all the mappings with mono or stereo input that goes to another number of channel have no interest because these plugins do a parallel processing of the channels. Only mappings with equal number of inputs / outputs have an interest.
I understand that you have wanted to do something complete, but we have changed from an extreme (no multichannel mapping) to another (too much mappings).
Can you consider to implement only what is necessary for the users, that is ONLY the mapping that corresponds to the total number of inputs / ouputs of the plugin ?
I know that you don’t care about what is done in other hosts, but they show only one “mapping”… and it is good…
Or, if you really want to create automatically all the possible mappings, do like in OS X where mono Audio Unit plugins are also available in other parallel versions (3 x 3, 4 x 4, 5 x 5 etc…), not the mono or stereo to surround versions.
But I really don’t think that it is necessary, because it is so easy to add other mappings in Podium WHEN we need them, and only these ones.
With the current beta, the result is an unnecessary accumulation of mappings, moreover which can be very confusing because they don’t correspond to the real usage of the plugins.
Anyway, the automatic creation of a multichannel mapping is great 😀
Thank you !
acousmodHow many channels would you need max? I was planning to set the maximum to 8 (7.1), but you probably need more
Oh yes, please, do not limit it !
The same 32 channels max as the bus will be perfect.
It is one of the most important features of Podium not to be limited to 12 channels like Nuendo, DigitalPerformer or others.
The ideal would be a selectable number of channels in the plugins mapping ?
acousmod@Zynewave wrote:
For the 1.97 release I’m going to extend zPEQ and zPitch so that they are surround capable.
Incredible !!!! 😀 😀 😀
Thank you VERY much Frits !
acousmodI’m going to add support for drag reordering effect tracks in compact mode. So please be patient.
No problem, I am 😀
acousmodI will save it for another time
Of course !
I feel I should move on to other areas.
Me too 😉