25 postsPage 1 of 2
1, 2
Hello. I'm on the latest pro version and been having issues with clip gain. Sometimes the boost/cut will happen "before" the location where it's drawn in. So I might try to attenuate a breath, but it will dip the volume a beat or two before. Obviously that's very frustrating. I have not identified any commonalities. It seems random and other cuts/boosts work fine on the same clip. Has anyone experienced this?

Running v6.1, Windows 11, Intel i7, Steinberg UR242

Thanks :)

- Studio One v6.1.2
- Steinberg UR242
- Windows 11 x64
- i7 13700K
- 32 GB RAM
User avatar
by Lokeyfly on Thu May 11, 2023 6:10 pm
sgietz wroteHello. I'm on the latest pro version and been having issues with clip gain. Sometimes the boost/cut will happen "before" the location where it's drawn in. So I might try to attenuate a breath, but it will dip the volume a beat or two before. Obviously that's very frustrating. I have not identified any commonalities. It seems random and other cuts/boosts work fine on the same clip. Has anyone experienced this?

Running v6.1, Windows 11, Intel i7, Steinberg UR242

Thanks :)




You can't work like that! :)

Unusual. First, it is worth verifying the latency isn't along the track or arrangement itself.

So with no effects on at all, seeing a waveform peak, spike, or transient of a set hit like a strum or something percussive, you do not hear a delay in the waveform pattern itself, correct?

Now, by reducing the clip gain drastically to one of those very obvious points, you say the reduction or change in the clip gain happens earlier then that known waveform peak, like a beat or two before?

That doesn't sound possible as the clip gain is representative (or should be) in time with the waveform.

Next check - leave the clip gain neutral and reduce the waveform using automation. Same peaks or dips you'd expect to see. No issue?

"It seems random and other cuts/boosts work fine on the same clip. Has anyone experienced this?"


That's even more bizarre. Seems like you have some corrupt RAM or swap file issues doing random things.

I'd say check the MIDI clock timing, but the randomness, throws that out the window.


Can you send a snapshot, or even better a short video? Thx.

S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.

New song "Our Time"
https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq

Visit my You Tube Channel
https://youtube.com/@jamesconraadtucker ... PA5dM01GF7

Latest song releases on Bandcamp -
 
Latest albums on iTunes

All works registered copyright ©️
User avatar
by Tacman7 on Thu May 11, 2023 10:14 pm
sgietz wrote I might try to attenuate a breath



After I comp a track I have the active track with lots of pieces, I go through and look for plosives and sibilants and edit the events themselves, then they're on time.
Like a T at the start of a word could be attenuated by cutting the event close to the T then pulling the fade handle to fade into the T so you keep experimenting till you get what you're looking for.
You do that to the whole track then bounce it and take it into melodyne, bouncing makes 1 file which is what you need to go into melodyne.

Forum Moderator.
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Studio OnePro6 Melodyne Studio
Win10 Ryzen 5 3600 - Motu M2
Ventura Mac Mini M2 - Zen Go TB
User avatar
by Lokeyfly on Fri May 12, 2023 5:24 am
Tacman7 wrote
sgietz wrote I might try to attenuate a breath



After I comp a track I have the active track with lots of pieces, I go through and look for plosives and sibilants and edit the events themselves, then they're on time.
Like a T at the start of a word could be attenuated by cutting the event close to the T then pulling the fade handle to fade into the T so you keep experimenting till you get what you're looking for.
You do that to the whole track then bounce it and take it into melodyne, bouncing makes 1 file which is what you need to go into melodyne.



Sure, that would be the better editing process for a breath, or extensive edits with plosives, sibilance, etc.

Still, not knowing how much editing sgietz is doing, it may be that automation may be faster, or slicing/reducing. What is bizarre is the timing issue with clip gain "a beat or two before", or the randomness of all this.

That's why a screenshot could prove helpful.
Unusual occurence, and more needs to be understood.

S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.

New song "Our Time"
https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq

Visit my You Tube Channel
https://youtube.com/@jamesconraadtucker ... PA5dM01GF7

Latest song releases on Bandcamp -
 
Latest albums on iTunes

All works registered copyright ©️
User avatar
by brettgoodkin on Mon May 15, 2023 4:08 pm
This is happening to me, too... Studio One Pro latest version

This is an entirely new bug that I've never seen before. Clip gain introduces random volume dips before and/or after the clip gain information. It's random in that it occurs, then play back again and it doesn't. Play back again and it's there again. Bounce the section and it ALWAYS writes the error.

This happens with or without plugins on the impacted channel on/off or with plugins removed entirely. Also happens with ALL plugins disabled.

It's NOT a corrupt RAM issue, etc. This is a brand-new Windows 11 Pro build, 64 gigs of ddr5 super fast RAM, i9 3900k DAW machine.

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by Tacman7 on Mon May 15, 2023 5:38 pm
Could you describe the steps to get an error? I turned on clip gain and played with it some and bounced it but it seems fine.

Maybe a pic?

Thanks

Forum Moderator.
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Studio OnePro6 Melodyne Studio
Win10 Ryzen 5 3600 - Motu M2
Ventura Mac Mini M2 - Zen Go TB
User avatar
by sgietz on Mon May 15, 2023 6:45 pm
It is completely random, as this can happen with the same event, on the same track. No matter the plugins/no plugins.

- Studio One v6.1.2
- Steinberg UR242
- Windows 11 x64
- i7 13700K
- 32 GB RAM
User avatar
by sgietz on Mon May 15, 2023 6:51 pm
Tacman7 wroteCould you describe the steps to get an error? I turned on clip gain and played with it some and bounced it but it seems fine.

Maybe a pic?

Thanks

I'll take a screenshot next time I run into it. It's hard to explain steps as it's random. I will just draw in a bunch of cuts/boosts and then some of them "may" be out of time. The gain change happens just before it's drawn in. This is also present in the mixdown. When I move the gain up/down, it will work as expected once or twice, before going back to the faulty behavior. Clearly something funky is happening. I've been using S1 since v2 and this is a new behavior.

- Studio One v6.1.2
- Steinberg UR242
- Windows 11 x64
- i7 13700K
- 32 GB RAM
User avatar
by brettgoodkin on Mon May 15, 2023 7:02 pm
Same behavior here.

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by brettgoodkin on Mon May 15, 2023 7:04 pm
Tacman7 wroteCould you describe the steps to get an error? I turned on clip gain and played with it some and bounced it but it seems fine.

Maybe a pic?

Thanks


There’s nothing to take a picture of. It’s just dropping volume right before a drawn clip gain event… then when you bounce it, that attenuation shows in the bounce

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by Lokeyfly on Mon May 15, 2023 7:04 pm
sgietz wroteIt is completely random, as this can happen with the same event, on the same track. No matter the plugins/no plugins.

Given you and brettgoodkin are describing a similar issue, it would be best to notify support. The thread can be left as is, so that others who find the same issue can see this is new, and in process.

Just report back the findings guys. Still, a snapshot if you have time could help the cause.

Further reports or findings would be helpful.

S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.

New song "Our Time"
https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq

Visit my You Tube Channel
https://youtube.com/@jamesconraadtucker ... PA5dM01GF7

Latest song releases on Bandcamp -
 
Latest albums on iTunes

All works registered copyright ©️
User avatar
by brettgoodkin on Mon May 15, 2023 7:08 pm
Also:

Clip gain does not follow automation on audio with Melodyne instantiated

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by brettgoodkin on Mon May 15, 2023 7:14 pm
Opened a ticket. It’s been noted going back to v5 apparently… I’ve just never seen it before

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by Lokeyfly on Mon May 15, 2023 7:47 pm
brettgoodkin wrote: "There’s nothing to take a picture of. It’s just dropping volume right before a drawn clip gain event… then when you bounce it, that attenuation shows in the bounce"


Yeah, your first description and this were good. Understood. I'm afraid we'd only be taking pot shots, and not helping. Definately create a ticket, and we'll keep the thread open.

Randomness is always a bit obscure. As you say, bouncing will still create the drop in audio prior to where the clip gain is drawn, once it occurs. In that case, no need to show anything.

Signing off. Let us know how you make out with support.

S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.

New song "Our Time"
https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq

Visit my You Tube Channel
https://youtube.com/@jamesconraadtucker ... PA5dM01GF7

Latest song releases on Bandcamp -
 
Latest albums on iTunes

All works registered copyright ©️
User avatar
by brettgoodkin on Mon May 15, 2023 10:01 pm
sgietz wrote
Tacman7 wroteCould you describe the steps to get an error? I turned on clip gain and played with it some and bounced it but it seems fine.

Maybe a pic?

Thanks

I'll take a screenshot next time I run into it. It's hard to explain steps as it's random. I will just draw in a bunch of cuts/boosts and then some of them "may" be out of time. The gain change happens just before it's drawn in. This is also present in the mixdown. When I move the gain up/down, it will work as expected once or twice, before going back to the faulty behavior. Clearly something funky is happening. I've been using S1 since v2 and this is a new behavior.


Open a ticket

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by brettgoodkin on Tue May 16, 2023 10:58 am
Support responded and advised that they are aware of the clip gain malfunctions and that it will be addressed in update version 6.1.2. Also stated that the clip gain not functioning at all on Melodyne tracks is normal.

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by wolfgerb on Wed May 17, 2023 8:07 am
I can confirm this behavior. This is a big one. I have a track to release with a ton of gain envelope edits. I already noticed a change of dynamics in certain vocal phrases and thought it was some kind of mistake I made. Now I realize it´s this strange gain-envelope behavior.
Please fix this fast!
kind regards
wolfger

P.S.: I made some quick tests switching between SO 6.02 and 6.1.1 and 6.02 didn't show this behavior.

Mac Book Air M2 15", Mac OS 14.3; RME Digiface USB, MOTU 828es + 8pre; Studio One 6.5.2; Faderport v2; Atom SQ
User avatar
by brettgoodkin on Wed May 17, 2023 10:20 am
I tried this and it appeared to work:

I added automation “nodes” just before and after the actual automation. Just drew in a “dot” at zero db.

Seemed to eliminate the issue.

https://soundcloud.com/brotherbrim/sets ... ernational

win 11 pro... S1 pro latest version... 64 bits... Rme latest drivers... All the ram and i9 3900k monster...
User avatar
by wolfgerb on Wed May 17, 2023 12:44 pm
brettgoodkin wroteI tried this and it appeared to work:

I added automation “nodes” just before and after the actual automation. Just drew in a “dot” at zero db.

Seemed to eliminate the issue.


Yes, this works indeed!
Doesn't really help with the song I have to finish though, where I used clip gain for deessing.
It would be a crazy amount of work, to go through all the esses and place clip gain points around them :(
this is a real bummer, I was so excited when switching to Studio One for the clip gain envelopes after using Logic Pro for 30 years and now this...

Mac Book Air M2 15", Mac OS 14.3; RME Digiface USB, MOTU 828es + 8pre; Studio One 6.5.2; Faderport v2; Atom SQ
User avatar
by wdkbeats on Sat May 20, 2023 5:10 am
I have the same issue. v6.1.0 works fine.

PC: AMD Ryzen 3900X, 32GB RAM DDR4 3600MHz CL16, ASUS ROG Strix X570-F, Gigabyte Radeon RX 570 8GB, SSD CORSAIR SSD MP510 960GB M.2 NVMe (OS)
OS: Windows 10 Pro x64
DAW: Studio One Professional x64
Gear: RME Fireface 802 + RME Advanced Remote, Prometheus Acoustics monitors, Avantone Mixcubes, JBL 305p, Softube Console 1, Presonus Faderport, AKAI Advance 61, Presonus Faderport, Beyerdynamic DT-990 Pro

25 postsPage 1 of 2
1, 2

Who is online

Users browsing this forum: No registered users and 69 guests