Jussy

As we know, the vst~ demands a minimum of 2 inputs. I really need a true mono one since I do not wish to just stick a mono signal into both. Does anyone know if there is a Frankensteined vst~ object/external out there which does this?

is-there-a-true-mono-vst-out-there

I think you can specify the number of outlets for the vst~ object with an argument. Also, you could query the number of outlets with the plugin with a get something or another message and create a pseudo mono to stereo or mono to whatever environment.

I see this is your first post. If you're new to max, I think the vst~ object and such can only be understood when you understand the manual as well as the tutorials. Sorry if thats not the case. I see a lot of new max users jump to the object or concept they're after without fully understand the max fundamentals. If you haven't done that, now is the time to do so.

I think you can specify the number of outlets for the vst~ object with an argument.  Also, you could query the number of outlets with the plugin with a get something or another message and create a pseudo mono to stereo or mono to whatever environment.

Indeed I am new to Max, however I think you will find that the manual does not specify the limits of I/O, although the vst~ help file does tell us that the default/minimum for both is 2. I am after a true mono version since Altiverb cannot see mono IRs when it inserted into a stereo buss, so 'shorting' the inlets/outlets will not change its status. That is why I was asking about 'Ture' mono!

Quote: Jussy wrote on Thu, 13 July 2006 01:57

----------------------------------------------------

> Indeed I am new to Max, however I think you will find that the manual does not specify the limits of I/O, although the vst~ help file does tell us that the default/minimum for both is 2. I am after a true mono version since Altiverb cannot see mono IRs when it inserted into a stereo buss, so 'shorting' the inlets/outlets will not change its status. That is why I was asking about 'Ture' mono!

there are no "mono" VST plug-ins - think of them as

so if you insert a 1-channel plug-in into a 2-channel

host interface such as the vst~ object you only have to 

connect the left inlet (and likewise if the plug-in also

Quote: Jussy wrote on Thu, 13 July 2006 01:57
----------------------------------------------------
> Indeed I am new to Max, however I think you will find that the manual does not specify the limits of I/O, although the vst~ help file does tell us that the default/minimum for both is 2. I am after a true mono version since Altiverb cannot see mono IRs when it inserted into a stereo buss, so 'shorting' the inlets/outlets will not change its status. That is why I was asking about 'Ture' mono!
----------------------------------------------------

there are no "mono" VST plug-ins - think of them as
1-channel plug-ins. 

so if  you insert a 1-channel plug-in into a 2-channel
host interface such as the vst~ object you only have to 
connect the left inlet (and likewise if the plug-in also
only outputs one channel)

Thanks, but you misunderstand. The limitation is with Altiverb. If it finds itself in a stereo slot (a la Max), it will not read its mono IRs. It will only see stereo ones. I need to use mono IRs, therefore I need Altiverb to believe itself to be mono, not just sending a stereo version a single signal. This behaviour can be verified by using Altiverb in ProTools or Logic and checking what it can see when inserted on either a mono or a stereo buss.

As far as I know, this cannot be overridden, so I need a pure mono vst~.

Thanks, but you misunderstand. The limitation is with Altiverb. If it finds itself in a stereo slot (a la Max), it will not read its mono IRs. It will only see stereo ones. I need to use mono IRs, therefore I need Altiverb to believe itself to be mono, not just sending a stereo version a single signal. This behaviour can be verified by using Altiverb in ProTools or Logic and checking what it can see when inserted on either a mono or a stereo buss.
As far as I know, this cannot be overridden, so I need a pure mono vst~.


16 years later... I believe I'm having a similar issue. Did you ever find a solution?

and i am not sure which design is more against the specs: that vst~ hosts mono plug-ins as stereo plug-in while having more IOs than 1 1 set - or that 

 refuses to load its mono files only because of some info from the host.

normally it should be the other way round: 

 should allow the user to load mono files into the left channel and then has 

i have never tried what happens to the CPU usage when you convert that mono file to LR (with a quiet right channel) and then use the plug-in stereo mode. did you?


there is still a minimum of 2 channels.

and i am not sure which design is more against the specs: that vst~ hosts mono plug-ins as stereo plug-in while having more IOs than 1 1 set - or that altiverb mono refuses to load its mono files only because of some info from the host.

normally it should be the other way round: stereo altiverb should allow the user to load mono files into the left channel and then has canMono() set to true. 

then it would work in mono and stereo hosts.

p.s.: 
i have never tried what happens to the CPU usage when you convert that mono file to LR (with a quiet right channel) and then use the plug-in stereo mode. did you?


If I were still using my 2012 macbook I'd be keeping a close eye on CPU usage, but my m1 macbook has been handling everything so well that I don't even worry about it anymore.

I'm not using altiverb, but I am using a few other plugins that function slightly differently depending on whether they're mono or stereo. It took me a while to figure out how to A/B true mono vs stereo summed to mono. Max, Ableton, Audacity, and Garageband can't do it, but Studio One 5 can. I realized that the preset I was using simply didn't sound good in mono, regardless of if the plugin was stereo summed to mono, or true mono. So I just switched to a better preset. The difference in gain/tone between true mono & stereo summed to mono is slight enough that it won't matter live.

hey guess what, this is fixed in max 8.5.3 :)

Is there a true mono vst~ out there?