Hi There,
I found this video talking about a new option in Studio One 5 for for file save settings "Use cached plug-in data on save". https://www.youtube.com/watch?v=dsowD9BEdjg The person posting the video says it will save a significant amount of time on a file save. The current save time is a very annoying issue to me on larger projects, and seems to be to others also. Here is where you set this new setting. download/file.php?mode=view&id=13913 As per the video poster I could not find anything about this in the new Studio One 5 manual. Does anyone know what this really does and if there are any disadvantages to saving song files this way? Thank you, eaglepass |
Following
aka "gesslr" or "george napier"
10 core iMacPro 1,1 | 64GB | OSX 10.15.6 | S1Pro 5.0.1 | MOTU I/O | Too Many Plug-ins | http://www.storyaudio.com FB: geo.napier3 PLEASE SUPPORT THESE FRs Video follows edit mode http://tinyurl.com/yc2gc9b3 Studio One Workspaces http://tinyurl.com/ybgfjpoj |
It's going to be safer doing it the slow way. If the cache gets corrupted then your projects may get corrupted.
The question is how would this cache get corrupted. I guess if you upgraded a plugin with studio one still running? Antivirus could lock a file in the cache (hence always a good idea to make sure antivirus never goes near any caching folders). The code with studio one V5 could be buggy and it could corrupt itself. Personally I would avoid this feature until it's proven to be bug free. Then again I'm not upgrading studio one until at least a few patches are out.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
I am bumping this to see if anyone now has any additional experience or insight into this new save option?
It would be great to understand this better and get some understanding if there is any significant risk in using this new save option. |
robertgray3 wroteI tried it with a project that took a long time to save and it made no difference on the save time. Same experience with my tests as well. If it’s supposed to be faster I”m not feel in’ the love |
I'm using Studio One with a huge metaframe in Vienna Ensemble Pro, and it takes several minutes (!) to save a project. When I tick this option, it takes only a few seconds.
I tried it yesterday for the first time after tweaking some keyswitch preferences in an instance of Kontakt (which is hosted by my VE Pro metaframe). When I loaded the project today I was wondering where those keyswitch settings went, because they were at default again. At first I wondered if I had forgotten to save the project, but then I remembered that I used this option yesterday for the first time. May be I'll try it again some time in the future, but for the moment I will return to deactivating this option just to be sure and play it safe with my huge template. |
I've been using this feature for a couple of months and as I am one that saves often, it's a big time saver. How it saves so fast that it doesn't save the info in the plug-ins. So if you make a change in a plug-in, you have to do a full save in order to have S1 remember it the next time you load the project. Say you made a change in a Kontakt instance, you have to do a full save. I always do a full save before closing a song.
|
Well it's been seven months now since this thread was created, one would hope if there are any bugs that they would be ironed out by now. Haven't seen many complaints recently.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
alexanderschiebel wroteI'm using Studio One with a huge metaframe in Vienna Ensemble Pro, and it takes several minutes (!) to save a project. When I tick this option, it takes only a few seconds. Yeah, there are some plug-ins it doesn’t work with so I stopped using it. It wasn’t worth the faster saves to find every once in a while some plug-in’s settings were back to default. |
Famous last words.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
"Use cached plug-in data on save" is permanently checked on my computer.
My template has more than 150 tracks, I have never lost settings on my vsti, vst. I am using EW Holywood Orchestra, with 32Gig of RAM. I make sure not to use all of my RAM (in general, there is between 9 and 12Gig available) I would like to know, which plugins are causing the problem, if I have them, I would like to do a test. Patrice |
stevenpalomino wroteStuBabe wrote Say you made a change in a Kontakt instance, you have to do a full save. I always do a full save before closing a song. A full save is without the Use cached plug-in data on save checked. Without it checked, S1 will save the current status of your plug-ins. |
I find the time it takes to save varies even when the box is ticked. IOt takes longer if you;ve made some changes to the instruments.
The advice is to leave it ticked when working on the project, but untick it before your final save. It's a pity given this advice, that if the box is ticked, when you decide to save the project, it doesn't offer you the choice to do a full save. This would be the best of both worlds. It would, of course, not do that during auto-save. The project I'm currently working on has 49 midi tacks, but for many tracks I'm using Opus (with up to 16 sample sets per instance), Synchron, VSL Instrs, UVI and MIR. It takes a long time the first time it saves, but is much quick after then - useful when auto backing up, but still a bore. The time difference isn't significantly smaller when closing the file with or without the box ticked. I rarely use Kontakt. Windows 10 i7-6800K running at 20% clocked 96 GB RAM Multiple SSDS (and two M2) |
eaglepass wroteDoes anyone know what this really does and if there are any disadvantages to saving song files this way? Yes, I heavily discussed this feature with Studio One's main programmer back then. Here I've explained how it works: Apologies for the terrible English in the video... but the content is still almost up to date A "new" behavior we introduced in Studio One 4.5 is that autosave always uses cached plug-in data - independently from the option. The “Use cached plug-in data on save” option now affects manual Save only. So autosave takes less time but you can do a full save by disabling the option and saving manually. PreAl wroteWell it's been seven months now since this thread was created, one would hope if there are any bugs that they would be ironed out by now. Haven't seen many complaints recently. The problem isn't bugs in that feature. It's that it requires plug-ins to notify the DAW of any changes the users makes inside the plug-in. If the plug-in does not report changes, these changes won't be saved to the song file so they would be lost if no "full save" is done which requests the data from all plug-ins again and saves them to file. By the way, I've enabled this option since it's introduction in summer 2020 and I haven't had any issues with it even with large templates with hundreds of Kontakt, VSL, SINE Player, ENGINE and HALion instances and all synths I have.
Lukas Ruschitzka
Studio One Specialist Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
Users browsing this forum: No registered users and 72 guests