![]() ![]() as i recall i was the first to bring it to their attention and from the pic i posted back then Bub was the one that noticed my meter reading 666. apparently presonus is unable to fix it since it has been around since the advent of v2 that i know of and it keeps raising it's ugly head. it may be in fact initiated by a plugin (1st or 3rd party) but the problem lies within studio one itself and to just blame a plugin or plugins is just brushing the problem under the rug. i agree with Bub that i have ONLY seen this problem with studio one. not fix the problem but for safety's sake. JBranam wrotehere is a link to an old plugin that may help. but automute is a bandaid that is effective imo it is a purely random event and being so it can't really be remedied if you can't track it down to the source. it is almost impossible to fix the problem because it has never been repeatable. ice9 is an additional automute plugin again for safety's sake if you wish i believe presonus has implemented an automute for if/when it happens as a precaution. thank God i was able to unplug my interface to kill the piercing sound and also i am thankful i was NOT wearing headphones. my first experience it screamed at me and locked up the software leaving my system screaming and i had to hard boot to stop it. sadly it does or can have the potential to damage one's hearing especially if it happens while wearing headphones when it happens. ![]() Here is a link to an old plugin that may help. Ultimately you need to rule this out first, plugins regularly break regardless of which DAW you use, it's certainly not an issue exclusive to S1, it's an issue with software in general. Plugins often stop working properly upon S1 upgrades because S1 may use different libraries, often the solution is to upgrade the plugin. Please don't shoot the messenger when he is in fact providing very helpful information. What have you done to rule out plugins which is always the first port of call. I have no idea if it is plugins or studio one in your instance. Do not downplay the seriousness of the problem by blowing it off on to 3rd party developers. I have actually had hearing damage because of this, as well as other people. This is a problem with Studio One that no other DAW that I have ever used or heard of has. The post PreAI linked to basically states that it's not a problem with Studio One and is a plug-in problem. To the rest of the tracks you have added by zooming each individual trackĪnd I promise you you will find the clipped one. then you will have to stop your cursor on the third minut and check all the tracks right from track 1 Only the problem is you have to go through each and every track you have arranged at the same bar where the clipping occurs.įor example if the clipping has occurred on third minute. The solution is to check each and every track by zooming it at the same bar where you get the clipping.Īfter zooming that particular part ,you will find that one of the audio file will show you a big distorted waveline (this is only visible when you zoom in the track) you don't have to do anything just cut the distorted part and delete it. Yesterday I encounter the same problem while working on one of my project in studio one.Īnd yes I found the solution for this after working for 2 Nights.
0 Comments
Leave a Reply. |