Developing software tools needed to develop Apps and Plugs-Ins

[IIO]

well, in Cubase my Pluggo-host does open an "open"-window for loading a vstplug or maxpatch

oh i see.

well, why you are using a dialog then? you can use an umenu, allow to enter text, or you can use drag and drop, which would be my preferred method.

and as you know, when it is restricted to only one plug-in, you can load that on loadbang. (i would recommend against using the plug-in name as argument as i have bad experience with that.)

you can also chose if you want to have the original vst-interface or pluggos egg-slider view. i would like to know how thats implemented... and possibly i will find out soon...

if you investigate that you will only find out that the pluggo shell is not written in max/msp and not using the vst~ object.

this is why ... see above.

maybe 5 or 10 in my awkward way.

if it is 5-10 it seems in order to create individual pluggos.

for a dynamic host you will not be able to save the current VST plug-in as parameter anyway since chuncks are not supported by pp & runtime.

right. maybe thats better.

yea, or aliases, vst~ does not care where a file is.

what i also do (here in the default vst plug-ins folder of the max/msp app) is that i rename the VSTs so that they dont have spaces in their names. makes loading easier in some situations.

so i have sent you a bunch of about 1200 110-patches this morning, enough to keep you for 2 weeks busy.


-110

[IIO]

uploaded my current max abstractions to the FTP, too, upon request by one of you.

[Protools5LEGuy]

uploaded my current max abstractions to the FTP, too, upon request by one of you.

Thanks!

[supernova777]

the max installation really needs to be packaged with proper installation instructions included in the actual download
the installation should be explained clearly + simply

same goes for any other plugin or software package that we are uploading with the intention of others using it..
not everyone will have the proper forum post open to read the instructions
not including proper installation details will cause anyone who tries to open it confusion
making it more of a curse then a blessing

[supernova777]

http://www.soundonsound.com/sos/sep09/articles/vstdiy.htm

i posted this link in another thread.. osx info but maybe someone can benefit from it for os9 too

[Protools5LEGuy]

the max installation really needs to be packaged with proper installation instructions included in the actual download
the installation should be explained clearly + simply

On http://cycling74.com/downloads/older/
You have to download Max/MSP 4.1,Released 8/19/2002 for Mac OS 9. Not compatible with OS 10+
The package called Max/MSP 4.1 with documentation (14.6 MB) http://cycling74.com/download/max4msp241all.sit

this app is fully functional but in 30 day demo mode.

[suspicious]now in my Dr Bu folder at the server you will find the ILokdestroyer, which after a self explanatory install resets the max demo clock to day zero by "Zap authorisations". 110 told me you could encounter problems if you had some real ILok authorisations, but i dont.

Jitter is Max videoinclined sister. i dont know much about it. But some maxpatches will require it (or parts of it). If you want to use Jitter replace the Jitlib inside the installed max/msp folder with the Jitlib [k], also present in my misc folder. for some reason Jitter is in demo mode... but it works. Max/Msp is a challenge man![/suspicious]

We can download object from http://maxobjects.com/

It is not clear if to use 3.0.3 pluggo or macintosh garden 3.0.4...

the install instructions shoudl be clear enough though: install max4 demo and use it

when you look into the maxmsp program and you feel lost i can give you a little introduction to it.  the most difficult in the beginning is that you dont know about paths, objects, key commands, how to save stuff and so on ... well like ith most programs when you are new to it.

[supernova777]

http://web.archive.org/web/20021016234259/http://creativesynth.com/subgroups/MaxZone.html
great tutorials here for max/msp

perhaps we need to start a zone of our site for MAX/MSP
to collect all articles + infos

if that was the case this page ive linked above links to alot of other resources we could use to make that

[IIO]

i maintain the unofficial pluggo group here https://groups.yahoo.com/neo/groups/pluggo/ , the official pluggo forum is closed since years .... but i think it is still available somewhere hidden at cycling74 ... (used to be at /3) ... just search there to find tons of stuff if you are stuck with the tutorials.

[supernova777]

i maintain the unofficial pluggo group here https://groups.yahoo.com/neo/groups/pluggo/ , the official pluggo forum is closed since years .... but i think it is still available somewhere hidden at cycling74 ... (used to be at /3) ... just search there to find tons of stuff if you are stuck with the tutorials.

COOL thanks for contributing something useful for once;)

http://www.soundonsound.com/sos/may10/articles/livetech_0510.htm

[Protools5LEGuy]

I am not sure if it is related to the post but here is some info from Apple about developing for OS 9
http://web.archive.org/web/20090330202327/http://developer.apple.com/technotes/tn/tn1176.html

changes and corrections in the next generation of Mac OS

Also
Packages in Mac OS 9. The Package Flag
This Technote describes how the Finder implements packages in Mac OS 9. Developers interested in creating packages for use in Mac OS 9 can use this document as a guide for creating packages
http://web.archive.org/web/20090706120103/http://developer.apple.com/technotes/tn/tn1188.html

Some kind of Index for the "carbon" tag http://web.archive.org/web/20041012202306/http://developer.apple.com/technicalnotes/LegacyTechnologies/idxCarbon-date.html

Technical notes http://web.archive.org/web/20040830210024/http://developer.apple.com/technicalnotes/index.html

[Protools5LEGuy]

Introduction to Moving CodeWarrior Projects to Xcode http://web.archive.org/web/20040221114934/http://developer.apple.com/documentation/DeveloperTools/Conceptual/MovingProjectsToXcode/index.html

We should "reverse engineering" this doc. We can be more interested in moving Xcode Projects to CodeWarrior.

http://web.archive.org/web/20030419070852/http://developer.apple.com/techpubs/macos8/mac8.html
Mac OS 8 and 9 developer documentation

Devices http://web.archive.org/web/20011116093153/http://developer.apple.com/technotes/indexes/dev-a.html
Hardware http://web.archive.org/web/20011115003148/http://developer.apple.com/technotes/indexes/hw-a.html
PCI Devices http://web.archive.org/web/20010818124124/http://developer.apple.com/hardware/pci/index.html


Open Firmware
Part 1 user interface http://web.archive.org/web/20020202141701/http://developer.apple.com/technotes/tn/tn1061.html
Part 2 the device tree http://web.archive.org/web/20011021132332/http://developer.apple.com/technotes/tn/tn1062.html
Debugging Open Firmware using TelNet http://web.archive.org/web/20010816015750/http://developer.apple.com/technotes/tn/tn2004.html
Debugging with TelNet 2 http://web.archive.org/web/20021019081909/http://developer.apple.com/technotes/tn/tn2023.html


Also this could be handy cause some software developers try to find the unique serial for a Mac http://web.archive.org/web/20011015113735/http://developer.apple.com/technotes/tn/tn1103.html

[Protools5LEGuy]

http://blog.steventroughtonsmith.com/post/109040361205/mpw-carbon-and-building-classic-mac-os-apps-in-os

In 2014 I came across a project on Github described as “Macintosh Programmer’s Workshop (mpw) compatibility layer”.

There has never been a good way to compile Classic Mac OS apps on modern OS X - for the most part, you were stuck using ancient tools, either Apple’s MPW or CodeWarrior, running in a VM of some sort. CodeWarrior, of course, is not free, and MPW only runs on Classic Mac OS, which is unstable at the best of times and downright nightmarish when trying to use it for development in an emulator like SheepShaver.

https://github.com/ksherlock/mpw

Final Thoughts

I am incredibly psyched about mpw. Its developer, ksherlock, has been very responsive to everything I’ve come up against as I stress test it against various tools and projects.

Right now it’s a fully usable tool that makes Classic Mac OS compilation possible and easy to do on modern versions of OS X, without requiring emulators or ancient IDEs or the like. To my knowledge, this is the first time this has been possible (excluding legacy versions of CodeWarrior).

I have used this toolset to build all kinds of things, including fun ports of my own apps. I’m sure I’ll be coming back to it for a long time to come.

I’m hoping I’m not the only person who’ll ever get to use it :-)

A new age of OSX tools converted to OS9 is coming!

Who has the guts to compile Ardour for OS9 with this?

[Protools5LEGuy]

https://developer.apple.com/legacy/library/documentation/Carbon/Conceptual/carbon_porting_guide/carbonporting.pdf

This document has helped me to understand what ways where used for developers Since OS8 to OSX. The concept of Carbon API and Core Foundation

Page 42

Using CodeWarrior to Build a CFM Carbon Application

This is the most likely scenario if you’re porting an existing Mac OS 9 application to Carbon, especially if you’re
already using CodeWarrior. You’ll continue to use the Mac OS development tools and processes you’re familiar
with, and you’ll create CFM applications that can run on both Mac OS 9 and Mac OS X. The only difference is
that you’ll include the CarbonLib stub library in your CodeWarrior project.

Using CodeWarrior to Build a Mach-O Carbon Application

Metrowerks CodeWarrior Pro version 8.0 and later has support to build Mach-O applications on Mac OS 9, as
well as build and debug applications on Mac OS X. If you have a second computer, you may also want to
investigate whether Metrowerks’ two-machine debugger suits your needs, as it can debug CFM applications
on both platforms. Contact Metrowerks for information about these products.

Using Project Builder to Build a Mach-O Carbon Application

Project Builder is Apple’s integrated development environment (IDE) for Mac OS X. It offers a comprehensive
feature set that includes source-level debugging. Project Builder is a good choice if your application will run
only on Mac OS X, and you want to take advantage of features available only on that platform. However, you
can’t use Project Builder to build a CFM application, so if you want your program to run on both platforms
you’ll either need to use CodeWarrior or other tools to create a CFM version for Mac OS 9.
See the Project Builder online help documentation for more information about creating Mach-O Carbon
applications.

Building a CFM Carbon Application With CodeWarrior

If you plan to use Metrowerks CodeWarrior, CodeWarrior Pro version 8.0 or later is recommended. You can run
CodeWarrior natively on Mac OS 9 or Mac OS X.

I searched a bit and it took me to CodeWarrior®Targeting Mac OS

http://web.uvic.ca/~ncs/406/HTML/Targeting_MacOS/

[Jakl]

Well here you go all you programmers - the VSTSDK you all wanted. Both the same, one as a .sit (stuffit 703, OS9) and one as a .zip from 10.4.11.

[IIO]

This document has helped me to understand what ways where used for developers Since OS8 to OSX. The concept of Carbon API and Core Foundation

you are supposed to use CW 5.x for VST and MAS development - and better forget about carbon if OS9 is the target for your app ... to many problems.

[geforceg4]

if macos9lives is serious about taking macos9 to the next level.. why not post these SDK's a bit more prominently on the site? so that programmers can actually see them + get their feet wet inventing some new basic VSTs?

not sure what version it is that JAKL has posted here, but theres also some other downloads here : http://macos9lives.com/smforum/index.php/topic,1700

[geforceg4]

if anyone knows java.
this might help:
http://web.archive.org/web/20040121175500/http://sourceforge.net/projects/jvstwrapper/
http://www.kvraudio.com/product/jvstwrapper_by_daniel309/details

[DieHard]

if macos9lives is serious about taking macos9 to the next level.. why not post these SDK's a bit more prominently on the site? so that programmers can actually see them + get their feet wet inventing some new basic VSTs?

I hate to say it, but with the plethora of good solid plugins in OS 9... I don't think there is much that has not already been done.

The virtual keyboard (that utilizes a standard Mac keyboard) was awesome because it filled a need... MIDI data could be sent to a VSTi that had no keyboard of it's own from a Mac that also had no external controller connected to it.

Rather than re-invert the wheel and program more plugins, I would love to see other users create ASR images that could be downloaded by beginners to setup full turnkey DAW systems... I did one for Cubase... it would be great to have one for ProTools with Plugins and also one for Logic.

[geforceg4]

if one could program a vst plugin for mac os 9 it would be a good entry level opportunity to get into doing it professionally for osx + other os'es. obviously this doesnt apply to the general population but rather special combination of skills + talents ie: individuals with programming experience aswell as creativity + historical knowledge.

my opinion is the opposite also regarding the virtual keyboard... as i have plenty of midi keyboards + i dont see how someone could really "PLAY" with a keyboard, especially if someone is a keyboardist who has trained all his or her life using keys, they would kind of laugh at using a mac g4 keyboard to jam. but hey, alot of people arent trained keyboardists... but id still say hey! get yourself a cheap 10$ midi keyboard pal!!!!! lol

anyways. the point is.. the TOOLS that were used STILL EXIST. its still possible to PROGRAM + CREATE NEW SOFTWARE whether that is vst plugins or otherwise. i think its worthwhile to collect those tools here for the sake of creating an opportunity for a select few people.

[DieHard]

anyways. the point is.. the TOOLS that were used STILL EXIST. its still possible to PROGRAM + CREATE NEW SOFTWARE whether that is vst plugins or otherwise. i think its worthwhile to collect those tools here for the sake of creating an opportunity for a select few people.

I guess that is a good point... we should at least collect and post the tools for anyone that wants to dive into such an endeavor.
Yes, the tools may actually be easier to get now that we have access to people that used them when they were "Top Secret" and not available in the wild