PlanetZ forums - scopeusers.com

Running SFP3.1a on Mac G4 867.
Excuse me if this is a stupid question, but now that Creamware have obviously decided to get rid of the background application, how do I force 3.1a to startup using my "StartProject.pro" ?
I tried putting an alias of my startproject into my "Startup Items" folder, but it still defaults to the "NewProject.pro" when it loads... any ideas
I also hate the fact that if I load SFP and then choose "Startup" from the "File" menu, I'm locked out and can't load another configuration unless I quit the SFP application and relaunch. This would be OK if it actually loaded from the begining. (under 3.0.1, my startup[background] project would load, then if I decided to use Pulsar synths/effects I just chose "start Pulsar" from the little background app and away we'd go. Then when I quit pulsar, the background project would reload itself - it was/is perfect)

The Live Bar menu is still glitchy. So, without posting a quote from Creamware's "readMe file" that came with the update... what was actually fixed?

What is the point in defining a system StartProject when you can't load it at startup?

not sure if i understood you right, but to define your project as a startup go to set->settings->project-> then click "save project as startup"
"save project as default" defines a new project.

The default project would be the starting project. So first Save as default.

I'm sorry for the confusion, it's hard to explain in text how I'm using my two different set-ups.
You have two options.... StartProject.pro and newproject.pro..... they are two different things... I saved a startup configuration and a new/default -"NewProject.pro" ... the NewProject.pro loads when you select "new" from the file menu.... the startProject is another thing all together. I have a few apps that can utilise ASIO, (audio editors etc) so I prefer to have Pulsar/SFP load and auto config itself to my "StartProject" when I just want to use my sequencer with midi and audio and no pulsar synths/effects but still have the audio routed to the Pulsar's SP-DIF instead of using the apple's built in soundmanager.
Under 3.0.1 I could do this easily because the background application that was supplied auto loads my "StartupProject" ...I think it was called Background.pro then (?)....so I could just use any ASIO application and any soundmanager applications and have their output routed to the Pulsar card's SP-DIF out. My monitor system has SPF-dif "in's".... I'm not explaining this well... but I could have all my sound applications routed thru the pulsar's SP-DIF for general playback and editing and avoid the Mac's built-in card which is 16 bit and sux.
I don't use sound manager modules in my "Pulsar Synth" projects/configs because it just uses up DSP.
The easiest way for me to show what I'm talking about would be to post jpgs of my two working set-ups...


Maybe someone could look at my routings and suggest a better setup ?
Please ignore the names shown in the screenshots, they are from 3.0.1 - they are just there to show the two different setups.. read Background as StartProject.pro


<font size=-1>[ This Message was edited by: blgrace on 2002-06-02 09:36 ]</font>

"background" in 3.0 is called now "startup" in 3.1, which would be your "startproject.pro"
your "newproject.pro" can be set as a standard with "default", so it loads everytime you start a new project

yes... I know what the respective project files are called in SFP 3.1 and 3.1a (please read the test before the screenshots) - the screenshots are from 3.0.1.. sorry.... still can't seem to get my point a cross can I?