Solved Getting So Disgusted!

[Vocalpoint]

I'm still open for suggestions. Maybe there's a solution. I hope. Tell me how to get a sample to you. I just want to send you a clip and not the whole song mainly because I don't want you wasting 5 minutes of your time listening to the whole thing. I just want to give you the "sore spots"
and maybe you could help me. I'm not buying a new computer or having expensive and complicated alterations to the one I have. I wouldn't hope it's necessary so please don't suggest that. I have to be able to work with what I have.

John

Through all of this - you have given us no idea about your gain staging. Plugins in play. How high on the meters are these tracks hitting? One moment you are mentioning a file glitch in a violin track and the next you are talking about channels "clipping" - which can be two very different things.

What exactly is the setup and what are you using in this session to mix? If you have 47 high CPU plugs engaged along with VSTs etc etc - there is only so much bandwidth in that Dell.

Would appreciate an overview of your mix, your track levels AND master bus levels and your CPU load (plugins etc)

VP

 

[JBMusic]

I think it was a plugin. I was using Softube's Tube Delay and Fix Doubler. I updated both earlier in the week, but when I removed the Tube Delay from the mix and replaced it with PreSonus Analogue Delay things improved at that spot. I ran it 3 times with no trouble. Keeping my fingers crossed.

John B

 

[Dave71]

I listened, and that sounds like either a CPU spike or clipping, I don't know how loud you mix..? But is it possible to send me the song file? Not the song folder, just the song file, it should be very small

 

[Dave71]

I think it was a plugin. I was using Softube's Tube Delay and Fix Doubler. I updated both earlier in the week, but when I removed the Tube Delay from the mix and replaced it with Presnonus Analogue Delay things improved at that spot. I ran it 3 times with no trouble. Keeping my fingers crossed.

John B

Aaah, for some reason this comment didn't appear till after I already commented. So in the end it probably was a plugin and not even the instrument. If it does happen again please let us know!

 

[JBMusic]

Aaah, for some reason this comment didn't appear till after I already commented. So in the end it probably was a plugin and not even the instrument. If it does happen again please let us know!

Yeah. So far so good. I made a few adjustments in the final mix and ran it two more times and it sounds perfect.
Thank you so much for your concern.
JB

 

[Lukas]

It's always a plug-in. Well. Almost always

 

[Vocalpoint]

It's always a plug-in. Well. Almost always

As suspected. Almost always

VP

 

[JBMusic]

Yeah. That being said, are there any other particular plugins that usually don't play nice with S1 that I should know about?
(third party, of course)

 

[Vocalpoint]

Yeah. That being said, are there any other particular plugins that usually don't play nice with S1 that I should know about?
(third party, of course)

There are a million plugins in the naked city. Can't really predict which one will decide to act up.

That said - I have about 406 installed here and every one is a winner.

Actually do not think I have ever had a plugin clash or issue in all my S1 history dating back to 2011.

I do however - only use VST3 at all times and stick with the tried and true (Fabfilter, Izotope, Nugen ,Waves and UAD).

VP

 

[JBMusic]

There are a million plugins in the naked city. Can't really predict which one will decide to act up.

That said - I have about 406 installed here and every one is a winner.

Actually do not think I have ever had a plugin clash or issue in all my S1 history dating back to 2011.

I do however - only use VST3 at all times and stick with the tried and true (Fabfilter, Izotope, Nugen ,Waves and UAD).

VP

Well actually, the problem I had with the Trilian bass a little while ago wasn't the volume level. But it was the fact that I had an old VST 2 copy on my system and was using it. I took notice in the browser when I highlighted it one said VST2 and the other said VST3 Synth. So I swapped them out and the problem went away. I need to get around to customizing my plugin menu. The Softube Tube Delay I just updated earlier this week. I assume it's a VST3 but I'm not sure. I'm just glad the problem is solved. But I have learned something valuable with this (and the Trilian issue) and that is noise in a track is usually caused by a bad plugin somewhere.

JB

 

[Vocalpoint]

Well actually, the problem I had with the Trilian bass a little while ago wasn't the volume level. But it was the fact that I had an old VST 2 copy on my system and was using it. I took notice in the browser when I highlighted it one said VST2 and the other said VST3 Synth. So I swapped them out and the problem went away. I need to get around to customizing my plugin menu. The Softube Tube Delay I just updated earlier this week. I assume it's a VST3 but I'm not sure. I'm just glad the problem is solved. But I have learned something valuable with this (and the Trilian issue) and that is noise in a track is usually caused by a bad plugin somewhere.

JB

I do not even allow S1 to scan for VST2 anymore - except for a custom symbolic link structure I use to expose just the three VST2's I have left (Absynth 5 and one other).

And yes - my View-Plugin Manager - is set to only allow VST3 to appear in the interface (with the only exception being the three above) - so there is no chance of any outliers slipping into any session.

VP

 

[TonalDynamics]

Make sure you did this:

'Enable low latency monitoring for instruments';

Turn this horrid invention OFF, and leave it off. It is only fit for small projects where one is not pushing the boundaries of one's DSP overhead.

It comes at the astounding cost of increased CPU-consumption for a given set of plugins, because it essentially duplicates the signal-path to feed it into a lower latency buffer in parallel.

When/if you need to monitor with low-latency, just set your interface to a lower buffer size and set Dropout Protection to 'minimum'.

 

[Lipica]

Make sure you did this:
View attachment 161

'Enable low latency monitoring for instruments';

Turn this horrid invention OFF, and leave it off. It is only fit for small projects where one is not pushing the boundaries of one's DSP overhead.

It comes at the astounding cost of increased CPU-consumption for a given set of plugins, because it essentially duplicates the signal-path to feed it into a lower latency buffer in parallel.

When/if you need to monitor with low-latency, just set your interface to a lower buffer size and set Dropout Protection to 'minimum'.

Interesting, but like you, mine is in gray, not clickable. Do you know why ?

 

[Lukas]

Interesting, but like you, mine is in gray, not clickable. Do you know why ?

Because Dropout Protection is set to Minimum (= 128) on the screenshot which is the same as the system buffer size. The options only make sense if DP is set to a higher value than the system buffer size.