[maxmsp] Re: Three stupid questions
Jeremy Bernstein
jeremy at bootsquad.com
Sun Dec 2 03:08:39 MST 2007
- Previous message: [maxmsp] Re: Three stupid questions
- Next message: [maxmsp] Re: Re: Three stupid questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 02.12.2007 um 09:58 schrieb Carl Lofgren: > Ah. So, IF I am building plugins, I will need Pluggo? And the Pluggo > runtime will be needed install if I distribute my plugs? > > Now, why is this? As I said - everytime I installed anything that > required the Pluggo runtime, I felt a slight annoyance that a step > like that had to be taken. But also as I said - no huge deal. But > just curious why. I believe that you only need it to USE Pluggos, not to develop them. The run environment (the version of Max running in your DAW) is distinct from the MaxMSP app, which is generally a good thing. >>> 4) MIDI-Out >> This has to be supported by the plugin host. If it is, >> then there should be no problem (my more plug-in savvy >colleagues >> might have to correct me, though). From the >PluggoDevGuide - "The >> ability to receive MIDI output from >> a plug-in may not be available in your host application >> (e.g. Pro Tools and Live)." > > By risk of getting myself banned straight away - I am going to ask > the question that might irritate you guys and think I'm a bloody > ignorant person. But may be true, as I am complete new to this > developing tool. You'll never get banned for asking questions in a constructive way! Banning is a last-resort response to unmanagable, disruptive behavior. Calling the validity of our work into question is no big deal. :) > Ok - here goes. Why Max/MSP. Why not SynthEdit? Or SynthMaker. I > know Max/MSP is cross platform. But compared to the pricing - there > is a slight difference. $50 for SynthEdit. $255 for SynthMaker. I > think I know the answer, but I'd rather have them confirmed than > eding up with the wrong kind of software. MaxMSP is not just about making synths or plugins -- quite to the contrary! It's a programming environment for building all kinds of media tools - custom video or audio processing chains, performance interfaces, installations, alarm systems, etc. We happen to think that this flexibility is worth the extra money! If all you are doing is programming audio instruments for use in VST plugins, we still believe that our solution is pretty awesome. You certainly have more options in this case, though. Try out the competition: if you can do everything that you want for $50, I know what I would do. If you think that there's more that you will want to do, now or in the future, MaxMSP offers some room to grow. jb jb
- Previous message: [maxmsp] Re: Three stupid questions
- Next message: [maxmsp] Re: Re: Three stupid questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
