9 posts
Page 1 of 1
I receive a message that clipping has occured but not where or when,
I can't watch very long exporting reports for even 20 minutes!
Is there a way to know it?

Sergio
http://www.sergiobrunetti.it
At Home studio: Studio One 5 Pro - Notion 6.7
Windows 10 on Vertex4 SSD - I7 3960x - 32 GB RAM -
2010 MacbookPro 2.66 Ghz 8 Giga RAM -
Presonus Monitor Station and
MOTU: 2408 MK3, 24I, Traveler, MIDI Express XT
At theater: Studio One 4 Pro
Windows10 HP desktop
Presonus Studiolive 1642
User avatar
by matthewgorman on Wed Aug 10, 2016 10:41 am
Not right now unfortunately. Its likely the sum of the tracks, not one in particular. Myself, when this happens, whatever the clipping amount was, I drop the main fader by that amount and re-export.

Also, are you using a limiter on the main? you may want to just to catch those stray peaks. Make sure the limiter is on the post slot of the main, not the insert.

Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor

S1Pro V5
User avatar
by vertigo on Wed Aug 10, 2016 11:43 am
A notice of the very moment in which a clipping occurs should be something simple to implement in the software!

Sergio
http://www.sergiobrunetti.it
At Home studio: Studio One 5 Pro - Notion 6.7
Windows 10 on Vertex4 SSD - I7 3960x - 32 GB RAM -
2010 MacbookPro 2.66 Ghz 8 Giga RAM -
Presonus Monitor Station and
MOTU: 2408 MK3, 24I, Traveler, MIDI Express XT
At theater: Studio One 4 Pro
Windows10 HP desktop
Presonus Studiolive 1642
User avatar
by matthewgorman on Wed Aug 10, 2016 11:50 am
vertigo wroteA notice of the very moment in which a clipping occurs should be something simple to implement in the software!


Possibly, however knowing the moment may not make the fix easier. For example, clipping occurs at 1:37. Which track was it? Or most likely, the sum signal of multiple tracks. Now you risk jacking up the mix to correct, or wasting time trying to figure out which track to lower, or write automation. Easier to just bring the main down by a few db

However, maybe head over to answers.presonus.com to the Studio One feature requests. Take a look and see if there is an existing request, and vote it up. If there isn't one, create it.

Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor

S1Pro V5
User avatar
by jpettit on Wed Aug 10, 2016 12:10 pm
I too thought it was strange that they did not tell you the time that it occurred ( since they know it).
I have a feature request in to add it, but it get very little notice. The response was similar to Matt's.
If it is .3db over turn the master down .3db.

This is true but puts a tax on all tracks due to one track.

If you prefer to leave the master at 0 db as I do, selecting all channels and adding a VCA is a quick way to bring the entire mix done.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by Lawrence on Wed Aug 10, 2016 12:22 pm
That's the thing... and I know I risk kicking off another one of those long "gain staging" debates just by saying it :) ... but if your mix clips by 2db, just pull the master fader down 2.5 db or whatever (or trim any master bus plugin by 2.x) and print it again.

It quite literally doesn't even matter, not at all.

Or, if you plan to "master" it later render it 32-bit float and ignore any such messages.
User avatar
by davidsampson2 on Tue Jun 15, 2021 8:39 am
This probably won't work for all genres of music, but you could export it and accept the clipping, then put the output wave file in as a track and mute it. Then you could take a closer look at the waveform, use your ears and instrumentation, and make a decision.
User avatar
by Lokeyfly on Thu Jun 17, 2021 11:03 am
~Old post alert~
Hey, we've all done it. ;)

I

S1-5.2, HP Omen 17" i7 10th Gen Laptop, 16 GB ram,512 GB TLC M.2 (SSD) and 1 TB SSD (both Internal). Audiobox 22 VSL, Audiophile 192 -Arturia Keylab 49 MkII, Novation SL25 MKII, Faderport 8, Roland JV-90, Roland GR-50, Roland Octapad, Akai MPD-18. MIDI Patchbay: MOTU 8x8, - Mackie HR824, Yamaha HS-7, Mixer: Yamaha Promix 01, Rane HC-6.

Latest song releases on Bandcamp -
 
Latest albums on iTunes

"Amber & Blue", and "Reasonable Approach" available on all major distribution music services.
Search "James Conrad Tucker music".
All songs copyright.
User avatar
by frank.crow on Thu Jun 17, 2021 4:54 pm
Lawrence wroteIt quite literally doesn't even matter, not at all.

Or, if you plan to "master" it later render it 32-bit float and ignore any such messages.


I’ve been waiting for someone to finally confirm this. I figured as much but didn’t want to be wrong.

Thanks Lawrence

Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7
Memory: 16 GB
Presonus. Studio One Pro V5
Presonus Quantum
Line 6. BassPOD XT Pro
Hardware DBX 160a
Hardware DBX 160XT
GA. Comp 2A
GA. Comp 3A
WA76 1176 (clone)
Softube. Console 1 MKII
Presonus. FaderPort & Faderport 8


"God's grace" :D

9 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 20 guests