Forums > MaxMSP

using transposer in a vst plugin

February 25, 2007 | 12:48 am

Hi –
I’ve been using MAX/MSP for several years and have a number of patches that utilize the transposer patch the comes with MAX (not gizmo~, but the patcher that has an audio, transposition, and float size input).
I have recently purchased Live and want to make plugins out of many of these patches. But the transposer patch will not work for some reason when embedded in a VST. I’ve tried building the patches including both "transposer.pat" and the "—windo" subpatch at patchers, files, etc… to no avail.
Does anybody have any suggestions (other than converting everything to gizmo~ – it would be a lot easier to just attach my plugin objects and be done with it). Thanks!

Drew


February 25, 2007 | 1:54 am

hello there,

i’ve tried and now must ask. can i input text from my
server [ie. a url address] directly into a patcher so i can update
the text file as required and have the text displayed
within the patcher/ as opposed to the browser. make sense?

thanks.

zehn


February 25, 2007 | 7:24 am


February 26, 2007 | 4:14 pm

dboles wrote:
> Does anybody have any suggestions (other than converting everything
> to gizmo~ – it would be a lot easier to just attach my plugin objects
> and be done with it). Thanks!

Did you look in the message part of your pluggo? I bet its missing the
waveform files for the windowing. You have to include them while
building the pluggo, or have a little initialisation patch which will
fill it while loading…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


February 26, 2007 | 7:18 pm

I didn’t recognize the waveform object as a patcher for some reason. But with your advice, it works no problem. Thanks so much Stefan!

Drew


February 26, 2007 | 10:25 pm

Sorry, I spoke too soon…
Once I added the windowing loads that Stefan mentioned, I was able to get the transposer to work. But that was with a direct connection from the tapout object to the plugout~ object (bypassing the crossfading acheived with the windowing). But when I connect plugout~ to the crossfading module at the very bottom, I cannot get a signal (that is, when converted into a VST – it works dandy in MAX/MSP itself). Obviously, I’m still doing something wrong with this windowing, since that’s where the signal seems to break.
I’ve included the test file I’m currently working with. Any ideas what I’m doing wrong?
Thanks again.

Drew


February 27, 2007 | 9:46 am

dboles wrote:
> I’ve included the test file I’m currently working with. Any ideas
> what I’m doing wrong? Thanks again.

I can’t read it, please open your patch, select all, copy, switch to
your mail program, paste the text into the mail body. Thats the way to
share patches…
If you are pre Max 4.5.5, then you need to open your patch as text, and
then paste that text into the mail body…

And yes, to help you further, you’d need to include the patch. For
example, out of your description I don’t understand what you mean with
"But when I connect plugout~ to the crossfading module at the very
bottom". Do you put functional parts behind the plugout~? That can’t
work, its the outlet of your pluggo, its only there to pass the pluggo
signal to a dac~ for debugging purposes while developing… (mentioned
in the help file to plugout~…)

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


February 27, 2007 | 9:58 am


Viewing 8 posts - 1 through 8 (of 8 total)