KVR Audio

jamcat · Post by **jamcat** » Fri Jul 21, 2023 6:59 am

A usual orchestra?

EnGee · Post by **EnGee** » Fri Jul 21, 2023 7:12 am

I'm really curious! Seriously!
I thought when you record an instrument (with midi), you use the articulations that come with the instrument, so why you need automation? Also, why you need to duplicate the same automation for each instrument?
Can you give an example? For example a screenshot of a project that uses the same automation for every instrument?
Even with that! It's not possible to arm all the similar instruments and record the same automation to all tracks?

lights · Post by **lights** » Fri Jul 21, 2023 7:56 am

ozinga wrote: Fri Jul 21, 2023 6:19 am
lights wrote: Fri Jul 21, 2023 6:05 am Not sure if this is a bug or something on my system.

After Upgrading to 6.2 the metronome stopped producing any sound.

Do you have Listen Bus active? If that is that case, in the mixer you need to activate click on it, not the Main channel.
That is the only thing I can think of.

You are a genius mate

Thank you !

jamcat · Post by **jamcat** » Fri Jul 21, 2023 8:55 am

EnGee wrote: Fri Jul 21, 2023 7:12 am I'm really curious! Seriously!
I thought when you record an instrument (with midi), you use the articulations that come with the instrument, so why you need automation?

SWAM are physically modeled instruments. The articulations are generated in real-time by how you automate the bows for strings, and breathe for winds and brass.

If you had SWAM v2 and then upgraded to version 3, and wanted to bring your existing projects or works in progress up to date by swapping v2 with v3, you would need to reassign all that automation to the new plugins. If you could just select a new instrument/parameter to route to from a dropdown, you wouldn’t have to copy and paste hundreds of tracks of loose automation data.

Here’s a video demonstrating a large symphonic arrangement with SWAM instrument:

Rohan Is using the v2 instruments, so if he was in Studio One and wanted to bring this project up to date with SWAM v3, he’d have to do exactly what I described.

EnGee wrote: Fri Jul 21, 2023 7:12 am Also, why you need to duplicate the same automation for each instrument?

I was talking about swapping instruments, going from v2 to v3. Or even swapping a part from cello to viola. Those are different VST instruments.

But, with a string section that has 12 1st violins that are all playing the same notes and the same bow changes, you could save a lot of time by duplicating some of the automation data among the instances and applying subtle transformations for slight variations between players.

EnGee · Post by **EnGee** » Fri Jul 21, 2023 10:51 am

jamcat wrote: Fri Jul 21, 2023 8:55 am
EnGee wrote: Fri Jul 21, 2023 7:12 am I'm really curious! Seriously!
I thought when you record an instrument (with midi), you use the articulations that come with the instrument, so why you need automation?
SWAM are physically modeled instruments. The articulations are generated in real-time by how you automate the bows for strings, and breathe for winds and brass.

If you had SWAM v2 and then upgraded to version 3, and wanted to bring your existing projects or works in progress up to date by swapping v2 with v3, you would need to reassign all that automation to the new plugins. If you could just select a new instrument/parameter to route to from a dropdown, you wouldn’t have to copy and paste hundreds of tracks of loose automation data.

Here’s a video demonstrating a large symphonic arrangement with SWAM instrument:

Rohan Is using the v2 instruments, so if he was in Studio One and wanted to bring this project up to date with SWAM v3, he’d have to do exactly what I described.

EnGee wrote: Fri Jul 21, 2023 7:12 am Also, why you need to duplicate the same automation for each instrument?
I was talking about swapping instruments, going from v2 to v3. Or even swapping a part from cello to viola. Those are different VST instruments.

But, with a string section that has 12 1st violins that are all playing the same notes and the same bow changes, you could save a lot of time by duplicating some of the automation data among the instances and applying subtle transformations for slight variations between players.

Thank you for the info. Really very interesting

He has a very nice workflow and the details are very balanced. I like it a lot!

It might be off topic question, but I'm also curious why then you don't use Logic instead of S1?

jamcat · Post by **jamcat** » Sat Jul 22, 2023 2:15 am

EnGee wrote: Fri Jul 21, 2023 10:51 am It might be off topic question, but I'm also curious why then you don't use Logic instead of S1?

Because Logic has been my sworn enemy since the Great DAW Wars of the last millennium. I was team Cubase until Studio One came out and out-cubased Cubase itself.

I was on Windows when I switched to Studio One 1.0, and I have stayed with Studio One after I went Mac.

EnGee · Post by **EnGee** » Sat Jul 22, 2023 7:04 am

I see! Thanks for the clarification

BONES · Post by **BONES** » Sat Jul 22, 2023 2:24 pm

I've just run into a fairly serious problem - DS Thorn freezes Studio One as soon as I try to load it. Is anyone else having similar issues? I've tried both VST 2.4 and VST3 versions.

EnGee · Post by **EnGee** » Sat Jul 22, 2023 9:53 pm

BONES wrote: Sat Jul 22, 2023 2:24 pm I've just run into a fairly serious problem - DS Thorn freezes Studio One as soon as I try to load it. Is anyone else having similar issues? I've tried both VST 2.4 and VST3 versions.

I don't have a problem (VST3 version).

jamcat · Post by **jamcat** » Sat Jul 22, 2023 10:00 pm

EnGee wrote: Sat Jul 22, 2023 9:53 pm
BONES wrote: Sat Jul 22, 2023 2:24 pm I've just run into a fairly serious problem - DS Thorn freezes Studio One as soon as I try to load it. Is anyone else having similar issues? I've tried both VST 2.4 and VST3 versions.
I don't have a problem (VST3 version).

Mac or Windows?

xpoes · Post by **xpoes** » Sat Jul 22, 2023 10:08 pm

BONES wrote: Sat Jul 22, 2023 2:24 pm I've just run into a fairly serious problem - DS Thorn freezes Studio One as soon as I try to load it. Is anyone else having similar issues? I've tried both VST 2.4 and VST3 versions.

No problems here.

EnGee · Post by **EnGee** » Sat Jul 22, 2023 10:20 pm

jamcat wrote: Sat Jul 22, 2023 10:00 pm
EnGee wrote: Sat Jul 22, 2023 9:53 pm
BONES wrote: Sat Jul 22, 2023 2:24 pm I've just run into a fairly serious problem - DS Thorn freezes Studio One as soon as I try to load it. Is anyone else having similar issues? I've tried both VST 2.4 and VST3 versions.
I don't have a problem (VST3 version).
Mac or Windows?

Windows 11. I will check on Mac later (Ventura/M1).
[edit] It is ok also on Ventura [/edit]

Danilo Villanova · Post by **Danilo Villanova** » Sat Jul 22, 2023 10:35 pm

v6 is looking nice but I'm pretty happy with 5 artist. I'm looking forward to upgrading if/when they fix the Sample One XT time-stretching bug that they've ignored for years. I'm sure that won't happen until they decide it's time to update their entire instrument line. v7 maybe?

stuman · Post by **stuman** » Sat Jul 22, 2023 11:09 pm

BONES wrote: Sat Jul 22, 2023 2:24 pm I've just run into a fairly serious problem - DS Thorn freezes Studio One as soon as I try to load it. Is anyone else having similar issues? I've tried both VST 2.4 and VST3 versions.

I'm using the latest VST2 version of DS Thorn in Studio One 6.2 and I'm not getting any freezes. Tried numerous presets plus created tracks for playback without issues. Also, I'm on Win10. Not sure if this helps. Hope you get the issue resolved.

Yorkz · Post by **Yorkz** » Sat Jul 22, 2023 11:12 pm

lights wrote: Fri Jul 21, 2023 6:05 am Not sure if this is a bug or something on my system.

After Upgrading to 6.2 the metronome stopped producing any sound.

Of course I double checked that the Click is engaged and made sure the click button om the mixer master channel is engaged. Double checked the click volume fader and wiggled it up and down. Went into metronome setup and all my settings from 6.12 looked intact. Pre-count checked, Click in Play checked.

Even tried replacing the click sound with custom samples. Circled through all presets.

Nothing.

Reverted back to 6.12 and immediately the metronome sound was back.

Has anyone else experienced such shenanigans ?

I ran into the same problem and was quite frustrated. I too tried replacing metronome sounds lol. It turns out that the mixer can independantly mute the metronome which was my case. I had the metronome setting on my Listen Bus defaulted to mute. So check your mixer settings, particularly on your master and listen busses.

Studio One v6.2 Released