## loader, unloader null device (freeze to vdat to save DSP)

Device/Module Wishlist

Original topic on PlanetZ: https://forums.scopeusers.com/viewtopic.php?t=19129

####

Posted: Sat May 27, 2006 3:44 pm
by masta
hi!
let me explain the title.
it's almost be like a modular shell but with one difference a load/(save)unload button.
i would like to have a null device that can hold information like:
1. synth device or fx device (load/unload)
2. faders'n'nobs current position
3. nr of voices
4. midi channel
5. notes
6. shell with i/o connected
the reson for this is that i often record synths to vdat or cubase, and i also save the midi file. so if i need to tweek something i have to remember the synth and the patch that was recorded on that track and load it manually...would be easier to just push a button and load it up automatically
its almost like freeze function in vst.
or...how about a button that can freeze=(record to vdat)all channels in the mixer but the one you are currently recording.
maby this is possible without a device...in that case plz tell me!
cu

####

Posted: Sat May 27, 2006 4:47 pm
by djmicron
hi,
it's not totally clear to me what you need.
At my first read, it looks like saving the entire scope project....
Could you explain some more details, as, which kind of device should be loaded into the module ?

####

Posted: Sat May 27, 2006 5:23 pm
by masta
ok!
realworld example here
i start up with a scope project and a vst project. with i/o mixer and vdat.
lets say i have a minimax loaded with lots of voices and a hole chain of effects. my DSP power is at RED! so i record my stuff with minimax both to midi and wave. then i delete minimax from the scope project(still have the wave for playback). DSP nice and yellow again, and then i add a vectron..ups into the red again...u get the point. since i deleted minimax from the project to save DSP i lost all the information i had before(connection to mixer, midichannel, fx chain) and so on.
so to be clear.
i would like to be able to unload a synth (or a hole chain of devices in a shell)instead of deleting it from the project.
so i have a visual representation in the scope project but if its unloaded it does not take up any DSP.
then if i need it again i could just press the load button and scope would load all the devices in the shell. and offcause use lots of DSP again.
this would help my workflow alot!
thx

####

Posted: Sat May 27, 2006 5:51 pm
by at0m
Your current options would be to use DP/SDK, which allows grouping of devices/modules, or within Scope/SFP to save new versions of your project as you go. This last one is what I commonly use...
Still, would be nice indeed to be able to group devices ...

####

Posted: Sun May 28, 2006 1:34 am
by astroman
... as part of a whatsoever version of Scope sequencer, syncing midi and vdat etc.
it's a little beyond the current capabilities of CWA regarding manpower and schedule - and very dubious if profitable at all.
Pro studios wouldn't risk their setup and newcomers can start with tons of bundled soundcard stuff or things like EnergyXT for just 30 bucks).
Of course it's exactly what SFP lacks in productivity and ergonomic design - but it's a really complex item.
And it depends on a timescale, while a project is a static(!) snapshot.
Imho At0m is as close as possible with his multistage-saving approach. With proper naming of the project one could probably picture it's developement rather well.
Not exactly easy to jump back and forth within, tho.
cheers, tom

####

Posted: Sun May 28, 2006 6:58 am
by alfonso
It should be a decent workaround saving the modular patches as they are in the song folder and saving presets for all other devices (synths, mixer etc) in a bank that only contains song-named presets. Then you can use a text tool to remember connections.
Naturally saving the whole project for each recorded stage is much easier.

####

Posted: Sun May 28, 2006 7:45 am
by Shroomz~>

> On 2006-05-28 07:58, alfonso wrote:
> Naturally saving the whole project for each recorded stage is much easier.

and not really much of a drain on workflow.
Scope's a little sluggish changing projects, but so are native apps when your project is packed with intensive plugs.

####

Posted: Mon May 29, 2006 8:04 am
by masta
hmm...the insert device in modular III is cool with activate toggle...is it impossible to make a modular insert device for synths? to bad they take up quite alot DSP even if they are not activated.
maby its not that bad idea to save out different projects for each track.then i could have a v-dat in each project linked to the same wave files so i will have a uppdated version of the song at all times.
thanks for all ur help
laters

####

Posted: Mon May 29, 2006 4:14 pm
by borg
hi there,
today i have had my first go with sfp in more than a year! and it was great... so i had to get back to the Z to get into it again.
forgive me if i'm wrong, it's been a while but what about just setting polyphony for the synths to zero? can't really remember if bypassing fx helps too (reading your post it doesn't).
of course saving different versions of patches has always done the trick for me as well.
and sure, a new device/shell would be nice too, with maybe new possibilities. who said progress is not possible without deviating from the norm? less than 24 hours to go, and then i'll be in zappaheaveni
will see you guys more in the near future...
_________________
andy
<FONT SIZE="-2"> the lunatics are in the hall </FONT>

####

Posted: Tue Jul 04, 2006 3:13 pm
by JL

> On 2006-05-29 17:14, borg wrote:
> hi there,
> but what about just setting polyphony for the synths to zero?
> _________________
> andy
> <FONT SIZE="-2"> the lunatics are in the hall </FONT>

This trick works great, especially with Modular.

####

Posted: Tue Jul 04, 2006 6:19 pm
by dawman
I believe that Medhi is designing something along those lines as we speak. I loved Saturn 4 it's abilities to go from 8 voice Oberheim filter pad, to a 1 voice " Solar Wind " effect preset, having the DSP usage drop drastically due to the scaling down of polyphony. I anxiously await his work, as I have used this synth live when I only had 2 x Scope Projects then, and it was very useful as I didn't have to look at the LCD and make people in the audience think I was sequencing and faking my performance. I am used to people asking me what sequencer I use at my gig, I take this as a compliment for I play live, but I just hate the thought of having to zero out my polyphony during a gig. I have solved this problem by building a 45 DSP DAW 4 live use, and having my 3 x Project card SFP DAW doing all the mixing, FX ( internal, and external )and putting B2003 on that DAW. I use the STM2448 with 4 AUX effects, 2 main insert FX and 9 other effects per channel on channels like Gigastudio 3 Orchestra samples, and Synths from DAW #2 that require additional treatment. But I love Solaris 4 it's ability to store it's own effects per preset, a very forward looking design on Zarg musics part. I'm thinking along the lines of the modern day CPU's that throttle themselves down when the extra horsepower isn't being used, this could be a money maker 4 a 3rd party developer, but I am green in many areas still, and don't know if this is even possible. But imagine SFP throttling itself up and down while we need. How enticing is that. Just shows you what a beautiful platform we use, it seems to be infinite. It's up to us to maximise it's potential. So I'm in it 4 the long haul, at least for the life of my new DAW.
Scope,... The Designers DAW,
_________________
Jimmy V.

####

Posted: Wed Jul 05, 2006 3:07 am
by Shroomz~>
Would the event of SFP throttling up & down not be a CPU killer?