issue with second workspace, anyone else have this?

[Pianoscope]

An example may help.
OSX Usine using Mac laptops built in output

Create a sample player in a rack WKP2, start playing a continuous loop of audio.
Create 2 racks in WKP 1, they can be empty.

Clear the workspace in WKP1. (while WKP 2 is playing)

The audio in WKP2 stutters and cuts out.

I would really like to use the WKP2 to create sound or process without stuttering while I load another workspace in WKP1.

This way in a live performance I can keep the music constantly flowing avoiding pauses which are about 15 -20 seconds due to their size and load time.

[sm_jamieson]

Maybe a "slow" workspace clear / save / load mode, that uses less processing and allows the sound to continue perfectly ?
If you wanted to do those actions on a workspace whilst not playing audio, you would use the "normal" functions which would be faster.

[Pianoscope]

..or some way to limit cpu use. My second workspace is very simple, just one rack. I just need anything playing, instead of blank silence if I am to use the playlist live. The idea was I fade the wkp2 rack in between songs.

I would be interested to know, how do others here use the second workspace?

-edit- did a search and read a post where someone has 2 copies of Usine open, one just for transitions. Going to try that way approach.

[x.iso]

If you're going to load new workspace while other is playing, it's possible, but it will likely stutter and UI might freeze while loading. It largely depends on project, but I don't think there's a good solution for that, since it will happen to any DAW if you try to load something while playing other project. In my case only dedicated simple player would play without problem while some relatively heavy project is loading.

The best approach for seamless transitions is to load *everything* beforehand, but disable the unused parts like racks or devices to save CPU. So then you would enable things that you need as you go and disable ones that you no longer need. You could even automate the process through Grid.

[Pianoscope]

x.iso.

yes I already do exactly that to move through 7 or 8 songs in a 50 minute set. A dedicated simple player would be fine for me...

I have each song correspond to a section of the grid, and place workspace presets at the beginning of each grid section.
The main problem with this approach is that if I change the settings on song 5, add bus routings, add processes etc then I have to go through every other song checking these actions have not altered or ar active in the other song presets. It can get very messy and complicated.
The other issue is that I end up with a big global patch with up to 30 racks. The grid becomes then becomes a bit of a problem as it starts to get really cluttered and visually hard to read, and individual workspace songs become really huge and prone to corruption.
I am grateful for what I can already do, as there is no other software currently available that has a timeline automation option and can host audio plug-ins, but its often a struggle.

[x.iso]

I think there should be a way to store routings as preset for each song, so that upon triggering corresponding section in Grid you would automatically get that preset on and routings align correctly.

[gurulogic]

I use a method in just one workspace where I have a dedicated "master" rack with a continuous looper that I engage for song changes. To do without dropouts, I engage the loop which automates all the other racks being disabled, then a patch on each rack is loaded sequentially, then each rack is turned on sequentially then the transition from the recorded loop to the new song. A bit clunky but works for me.

[senso]

I'll try to improve this point in next future major release but don't expect miracles.
Some wkp can take a lot of resources during the initialization process and just kill the CPU.
But there is maybe a soluce to reduce the impact (not to totally avoid all potential glitches).
Also think about VST's which are not made by sensomusic and can, for example, overload the HardDisk.

[x.iso]

I'll try to improve this point in next future major release but don't expect miracles.
Some wkp can take a lot of resources during the initialization process and just kill the CPU.
But there is maybe a soluce to reduce the impact (not to totally avoid all potential glitches).
Also think about VST's which are not made by sensomusic and can, for example, overload the HardDisk.

is it possible to treat wkp loading as low priority task if engine is on, so it wouldn't try to load everything at once and initialize everything one by one limited by reserved CPU 'space'? some VST's could still bring trouble, but that's a different story.

[senso]

it's already the case ! but when the HHD is busy it is for all the processes.