KVR Audio

xbitz · Post by **xbitz** » Thu Mar 03, 2016 6:02 am

bungle wrote:It is nothing like automation clips/Items
It is the same as Reapers Clip/item automation
These are two very very different things

just was curious and yepp can be created shared "automation clips" between tracks too

so the macro knob based "clip automation curves" can be dropped to other tracks too and they begin to work instantly, if they were shared ones all of them can be edited at once, lanes also working, so dunno definitely seems automation clips for me (this is how it should work on DAW level too, so please developers

) so the Multi Ins. Containers can be connected with each other using macros + shared automation curves which is a very-very nice dunno why wasn't promoted feature, definitely missing for other DAWs

bungle · Post by **bungle** » Thu Mar 03, 2016 10:45 am

Automation items can be sent to any and multiple destinations, they also combine with other sources.
All i am seeing in your video is a piece of automation inside a clip that while it is being moved from track to track within a multi, is never actually going anywhere but the same destination.
Again for the record, this is nothing like Automation clips/items, this is Clip/Item automation.
While it is very useful, it is not what is needed for complex automation sequencing, but at the same time i doubt very much we will ever see automation clips/items in Studio One, Reaper is updated way more frequently than studio one and it is the number one requested feature for the last six years or such, those developers have never bothered to implement it and studio one is catering to the same sort of people, by developers who obviously have a very similar vision (ignoring the marketing side of things)

xbitz · Post by **xbitz** » Thu Mar 03, 2016 11:02 am

"All i am seeing in your video is a piece of automation inside a clip that while it is being moved from track to track within a multi, is never actually going anywhere but the same destination."

on the video the are two independent Multi Container(in the container we can automate the instruments, their fxs, and the mixer insert fxes together using one automate curve which has been assigned to a macro knob) which use a "common" shared clip with "piece of automation inside", they have independent macros by default, originally only the first one was automated but after the clip was dropped(using shared copy) to the second automation track it begin to automate the first macro knob of the second Multi Container instantly so the first macro knobs from both Containers (1,2) gonna move same

so as I see

from N track : 1 common macro (if it uses shared copy) automation : can control N knobs(in the same position) from different multi containers : which can control N*M(where M is the number of the targets) different device parameters (all of them have own trans. curve)

and whole thing can be multiplied with the number of macros S1 has 8 knob macros + 2 x/y one per container, all of them can be automated/controlled from a single clip (from different modulation tabs)

etc. and only the Multi Container knows it in S1, please correct me if I was f*ed something

xcentric · Post by **xcentric** » Thu Mar 03, 2016 10:02 pm

xbitz you are the man. I didn't know you can automate insert effects inside Midi Parts until you pointed it out

Thanks

LawrenceF · Post by **LawrenceF** » Fri Mar 04, 2016 12:13 am

Yep. Drag and drop directly into the key editor. The macro system bridges it over...

bungle · Post by **bungle** » Fri Mar 04, 2016 2:08 am

xbitz wrote:"stuff

It is very cool, it is not Automation clips though

galmo · Post by **galmo** » Fri Mar 04, 2016 4:53 pm

So it its worth it now to update from producer to pro v3?

recursive one · Post by **recursive one** » Fri Mar 04, 2016 5:11 pm

galmo wrote:So it its worth it now to update from producer to pro v3?

Also curious, but I'll probably stick to 2.65 producer in foreseeable future. It already has everything I need from a host. Also worth noting that it works like charm with my Virus TI, I'm afraid that I'll buy myself problems in this area once I decide to upgrade.

LawrenceF · Post by **LawrenceF** » Fri Mar 04, 2016 6:31 pm

Here's a plugin I made for myself to use with Studio One. What I often do when mixing is stage intermediate busses in front of FX return busses to be able to independently filter aux sends before they hit reverbs and similar. This plugin allow sending audio from any channel to any other via it's always open side-chain inputs.

In the use case below it's kinda like having FX inserts on each aux send, only filters in this case. It only affects the signal coming into it's side-chain inputs, nothing else on the channel.

32-bit VST: Download Zip

Enjoy, or not.

nathanj · Post by **nathanj** » Sat Mar 05, 2016 5:32 am

i finally upgraded because of the audio editing enhancements and have been blown away by all the additions and improvements. i have however been bogged down in crashes and graphics glitches on osx. hopefully this is just some of the teething pains of the .0 upgrade and will be resolved later this month. just have to save more frequently than i was used to with v2.

bungle · Post by **bungle** » Sat Mar 05, 2016 3:59 pm

Yes running it in OSX is painful to say the least, if you have the option, run it in Windows, it has vastly superior stability.

troxx · Post by **troxx** » Sat Mar 05, 2016 4:45 pm

It doesn't appear to only be osx, i'm running it on Windows 10 (running as an administrator), running Pro 3.2 & it's crashed several times in as many times this past week. Crashes now and again just trying to open the application, second time it usually opens fine. Crashed while auditioning sounds in Kontakt, had a section looping and was just drag dropping sounds from a library while the transport was playing, & also has crashed when adding a couple more vst instruments, once when I installed Synthmaster and the other when I installed DCAM Synth Squad. S1 3 has also just froze for no apparent reason, can't shut the application down, Windows states the application is not responding, unable to end it in task manager and have to restart the whole computer, I've never relied on autosave so much

There must be definite bugs still going on with it, Studio One 2.6.5 was pretty solid and I never had this many crashes, though Studio One has been craptastic in the handling of vsts from my own experience, I always had to occasionally clear blacklisted vsts and rescan, for it to sometimes actually accept some in the past.

Funkybot's Evil Twin · Sat Mar 05, 2016 5:29 pm

troxx wrote:It doesn't appear to only be osx, i'm running it on Windows 10 (running as an administrator), running Pro 3.2 & it's crashed several times in as many times this past week. Crashes now and again just trying to open the application, second time it usually opens fine. Crashed while auditioning sounds in Kontakt, had a section looping and was just drag dropping sounds from a library while the transport was playing, & also has crashed when adding a couple more vst instruments, once when I installed Synthmaster and the other when I installed DCAM Synth Squad. S1 3 has also just froze for no apparent reason, can't shut the application down, Windows states the application is not responding, unable to end it in task manager and have to restart the whole computer, I've never relied on autosave so much

There must be definite bugs still going on with it, Studio One 2.6.5 was pretty solid and I never had this many crashes, though Studio One has been craptastic in the handling of vsts from my own experience, I always had to occasionally clear blacklisted vsts and rescan, for it to sometimes actually accept some in the past.

It sucks when people respond to this and say, "that's entirely not my experience at all," but it really isn't. I can count on one hand the number of times S1 has crashed on me from version 2.5 to 3.2 (I literally think it's crashed 5 or fewer times in probably years that weren't due to an issue with a corrupt Slate VMR install). And two of those crashes happened on close. And I use a lot of VST effects and instruments, including Kontakt.

The issue with it freezing on close makes me think Studio One is having a hard time releasing the ASIO driver, so for that, I'd take a look at your interface/driver.

troxx · Post by **troxx** » Sat Mar 05, 2016 5:51 pm

My crashes have not occurred when closing S1, never has done, they have been upon opening and during it's use, I did not have many crashes at all on S1 or S1 2, it has only been since I updated, i'm actually using a Presonus Audiobox with latest drivers as my audio interface. I also updated my graphics card drivers in case it had any bearing on the crashes.

TheRocker · Post by **TheRocker** » Wed Sep 07, 2016 7:07 pm

Huh,,, I'm using Studio One 3.2 and not had a crash during use, and I have it up sometimes for a day or 2, lol,,,
I did have Antares EFX 3 cause studio one from loading, so had to uninstall. Anteras said they are working on a fix,,,
But all of Slate SSD4 / Trigger - all VMR - Tape Mastering FX G . Kontakt, Waves, PluginAlliance, EW Gold, Synthmaster, UVI, Superior Drummer2 - EZ Drummer 2, Sugarbytes, Sampletank 3 - Amplitube 4 - Tracks, Bias Amp Pro - Bias FX Pro, Anteras Live - 4VOX, Melodyne Studio and more work fine,,, no crashes, and CPU never really over 33%...

NEW Studio One v3 updates incoming.