image description


auto detect peaks
  Forum Index » Studio One Feature Requests 
Author
Message
Lokeyfly
Presonoid
[Avatar]

Joined: 07/06/2012 08:31:19
Messages: 1379
Location: N.Y.C.
Offline

Red marks or red slashes alongthe timeline, or mouse over the red peak indicator to see peak time(s) would be cool! Very useful suggestion!

Plus One from me
In the words of the late great Graucho Marx "I refuse to join any club that would have me as a member"

S1 Pro 2.5, Laptop: VAIO i7, 8Gb, Win 7 X64, SP1. Supporting software, too much to list. Audio Interface: 22 VSL, M-Audio Fast Track Pro, Audiophile 192 PCI-e, Controllers: Novation SL Mk II, M-Audio Axiom, Guitar controllers by Roland GR-50, Percussion controllers: Roland Octapad II, Akai MPD-18. Guitars by: Fender, Gibson, Gretch, Guild, Martin, Taylor, & Yamaha
Lokeyfly
Presonoid
[Avatar]

Joined: 07/06/2012 08:31:19
Messages: 1379
Location: N.Y.C.
Offline

Red marks or red slashes alongthe timeline, or mouse over the red peak indicator to see peak time(s) would be cool! Very useful suggestion!

Plus One from me
In the words of the late great Graucho Marx "I refuse to join any club that would have me as a member"

S1 Pro 2.5, Laptop: VAIO i7, 8Gb, Win 7 X64, SP1. Supporting software, too much to list. Audio Interface: 22 VSL, M-Audio Fast Track Pro, Audiophile 192 PCI-e, Controllers: Novation SL Mk II, M-Audio Axiom, Guitar controllers by Roland GR-50, Percussion controllers: Roland Octapad II, Akai MPD-18. Guitars by: Fender, Gibson, Gretch, Guild, Martin, Taylor, & Yamaha
Lokeyfly
Presonoid
[Avatar]

Joined: 07/06/2012 08:31:19
Messages: 1379
Location: N.Y.C.
Offline

Why is the thread not posting? ooof, new page, my bad.
In any event, I like the feature request.

This message was edited 2 times. Last update was at 07/09/2012 01:27:21

In the words of the late great Graucho Marx "I refuse to join any club that would have me as a member"

S1 Pro 2.5, Laptop: VAIO i7, 8Gb, Win 7 X64, SP1. Supporting software, too much to list. Audio Interface: 22 VSL, M-Audio Fast Track Pro, Audiophile 192 PCI-e, Controllers: Novation SL Mk II, M-Audio Axiom, Guitar controllers by Roland GR-50, Percussion controllers: Roland Octapad II, Akai MPD-18. Guitars by: Fender, Gibson, Gretch, Guild, Martin, Taylor, & Yamaha
Toth
Presonoid
[Avatar]

Joined: 02/09/2011 04:33:17
Messages: 1194
Offline

With 32bit floating point audio there is no such thing as clipping. You may exceed 0db, but you haven't really "clipped" because if you bring down the audio signal (even after bouncing!) your waveform will be intact. This is why the channel strips in S1 don't have clip indicators.
SoundCloud: http://soundcloud.com/toth_music
[WWW]
Lokeyfly
Presonoid
[Avatar]

Joined: 07/06/2012 08:31:19
Messages: 1379
Location: N.Y.C.
Offline

Hi Toth,

Not sure what your input about 32 bit floating point processing has to do with someone requesting the ability to view and locate where clipping occurs.

Clipping, or any unwanted distortion at the input, and output levels is a very real concern. Sure, 32 bit floating point processing allows levels to be turned down, and still maintain a good level of clean sound (internally) but....

It would be very useful to see where such peaks occurred in the audio track(s), and last but not least during mastering. Some of us would like to know more than a clip occurrence above 0db took place, but also to understand where such a peak/clip occurred. Thereby (a) minimizing the chance for it to re occur, or (b) determining if such peaks are acceptable. For practical purposes clipping is usually not desirable, and from a digital stand[point sounds very ugly.

Even when setting input levels, as stated in the S1 manual, “you should set the input gain on your audio interface as high as possible without overloading the input.” This is found in any lit that discusses setting audio levels, because the trade-off of setting levels too low can result in raising the noise floor.

Driving the point about 32 bit floating point internal affairs has nothing to do with detecting peaks and being able to locate such peaks. Peaks and distortions occur in the outside world when we record them quite often. By instruments we play, amplifiers that peak, crescendos , you name it. OK, not that often.

The request is to auto detect peaks. Your work habbits may be different.

I think it's a must have.

This message was edited 1 time. Last update was at 13/09/2012 04:10:25

In the words of the late great Graucho Marx "I refuse to join any club that would have me as a member"

S1 Pro 2.5, Laptop: VAIO i7, 8Gb, Win 7 X64, SP1. Supporting software, too much to list. Audio Interface: 22 VSL, M-Audio Fast Track Pro, Audiophile 192 PCI-e, Controllers: Novation SL Mk II, M-Audio Axiom, Guitar controllers by Roland GR-50, Percussion controllers: Roland Octapad II, Akai MPD-18. Guitars by: Fender, Gibson, Gretch, Guild, Martin, Taylor, & Yamaha
Scoox
Presonic
[Avatar]

Joined: 22/09/2010 07:29:03
Messages: 224
Location: Wuxi, China
Offline

from me, this is a fantastic idea
Windows 7 64-bit
Intel Core i7 920 CPU, 12 GB RAM
RME FireFace 400, NI Audio Kontrol 1
Presonus Studio One 2 v2.6.2 64-bit

My feature wish list:
1. Automation clips
2. Ability to (optionally) undo everything, inc. plugin and mixer knob/fader/buttons, add/remove insert, add/remove plugin, etc...
3. Mixer snapshots
4. Wraparound slide audio items like in Reaper
CubaseUser
Presonic
[Avatar]

Joined: 30/08/2010 23:13:52
Messages: 942
Offline

I've been thinking about my initial idea and I've come up with an additional idea.
Currently any peaks would be flagged at the precise moment on the event.
As an extension to this I'd like to propose this further development
Scenario
You have,say, a guitar track. The mixer is open, you have a number of inserts active (amp Sim, ir loader, a chorus , delay and a pro eq).
You have all inserts active. As we know the majority of plug have input and output controls.
You start playback and come to several points where the track is now clipping. Looking at the mixer currently shows the meters and how hot the signal is, but how about the mixer having the ability to visually show you when a plug in has its output set too high. I was thinking that the insert slot with the offending plug could flash red as an indicator its output was the cause
Intel Dual Core 4300
4 gig ram
Asus P4B E
Novation Nocturn
M Audio Keystation Pro 88
Tascam FW1884
KRK Rokit RP 10 3
Roland TD4
two 19" TFT monitors
Scoox
Presonic
[Avatar]

Joined: 22/09/2010 07:29:03
Messages: 224
Location: Wuxi, China
Offline

That would also be very useful, good idea.
Windows 7 64-bit
Intel Core i7 920 CPU, 12 GB RAM
RME FireFace 400, NI Audio Kontrol 1
Presonus Studio One 2 v2.6.2 64-bit

My feature wish list:
1. Automation clips
2. Ability to (optionally) undo everything, inc. plugin and mixer knob/fader/buttons, add/remove insert, add/remove plugin, etc...
3. Mixer snapshots
4. Wraparound slide audio items like in Reaper
NickWeiland
Presonoid
[Avatar]

Joined: 04/08/2012 20:33:05
Messages: 1050
Location: United Kingdom of Hypocracy
Offline

CubaseUser wrote:I've been thinking about my initial idea and I've come up with an additional idea.
Currently any peaks would be flagged at the precise moment on the event.
As an extension to this I'd like to propose this further development
Scenario
You have,say, a guitar track. The mixer is open, you have a number of inserts active (amp Sim, ir loader, a chorus , delay and a pro eq).
You have all inserts active. As we know the majority of plug have input and output controls.
You start playback and come to several points where the track is now clipping. Looking at the mixer currently shows the meters and how hot the signal is, but how about the mixer having the ability to visually show you when a plug in has its output set too high. I was thinking that the insert slot with the offending plug could flash red as an indicator its output was the cause


Computer: Asus Sabertooth x79 MOBO, 64 gb vengance Ram, 4gb windforce gigabyte Oc edition graphics card, processor: intel i7 3930 3.8 ghz 6 core, startech firewire card.
Laptop:Hp Pavilion Laptop G6 series amd 2.66 ghz quad core processor,256mb graphics card Ati,8 gb ddr3 ram,750gb Hybrid Drive;Audio Interface;Roland Octa-Capture,8 Mic pres,10 ins/outs, 44.1, 48, 98, 192 khz,Monitors:Adam a7xs,OS:Windows 7 Ultimate 64-Bit, Windows 8 Professional,Daw:Studio One Professional 64 bit version,Cubase 6.5,Plugins:Jbridge, Waves platinum bundle, Fabfilter bundleVst Instrumen,BFD2 64bit, Alchemy, East West Symphonic Orchestra.
[MSN]
roatan
Prenoob

Joined: 14/12/2010 19:13:21
Messages: 68
Offline

CubaseUser wrote:I've been thinking about my initial idea and I've come up with an additional idea.
Currently any peaks would be flagged at the precise moment on the event.
As an extension to this I'd like to propose this further development
Scenario
You have,say, a guitar track. The mixer is open, you have a number of inserts active (amp Sim, ir loader, a chorus , delay and a pro eq).
You have all inserts active. As we know the majority of plug have input and output controls.
You start playback and come to several points where the track is now clipping. Looking at the mixer currently shows the meters and how hot the signal is, but how about the mixer having the ability to visually show you when a plug in has its output set too high. I was thinking that the insert slot with the offending plug could flash red as an indicator its output was the cause


Windows 8.1 x64 / Windows 8.1 x32: Intel Xeon, 6GB Ram, RME ADI-8 DS, ATI Radeon HD 6770 PCIe, Studio One v2.6, Melodyne Editor v2, Nuendo v6

Slate Digital FG-X || Slate Digital VCC || Lexicon PCM Native Reverb || FabFilter Total bundle || Waves Mercury, SSL, Abbey Road || NI Komplete 8 || ReFX Nexus || Spectrasonics Omnisphere || Plugin Alliance Complete
tkk
Prenoob

Joined: 25/02/2012 11:22:25
Messages: 56
Offline

Any method to help find the clipping spot on the timeline would be most welcome. I was looking for something like that in the Manual and then on the Forum just to find this.

My specific workflow is with classical two track material, which I don't want to compress. However, some "fader riding" with the volume automation is done to decrease the top levels in order to bring the softest parts slightly up.

Now I increase the the overall level until I get clipping. Then I try to find the clipping spot and if it is just a short peak I make a hump around it into the volume.

Any method to find these peaks would be a great help. so here is my
Studio One Artist 2.6.1
Adobe Premiere Pro CS5
AudioBox 44VSL
Fujitsu Lifebook P771
i7-2617M @ 1.5 - 2.3GHz, 8GB
Win 7 64-bit
Daw stew
Presonic
[Avatar]

Joined: 11/10/2012 14:04:16
Messages: 957
Offline

I have to say that this is a great idea. I'd like to take it even further. Why not have a Loudness History. What this would be is a track that sits at the top of the screen (like the tempo track) and it shows how the song dips and peaks in volume throughout the length of the track.
Isotope Insight meter plugin has this and its great for seeing peaks over the threshold.
Windows 7 x64
Core2Duo E4300 Cpu
4gb DDR2 RAM
ASUS P5B-E motherboard
Nvidia graphics card
NickWeiland
Presonoid
[Avatar]

Joined: 04/08/2012 20:33:05
Messages: 1050
Location: United Kingdom of Hypocracy
Offline

what if when the peaks were detected S1 placed markers on the time line? with the offending track title?
Computer: Asus Sabertooth x79 MOBO, 64 gb vengance Ram, 4gb windforce gigabyte Oc edition graphics card, processor: intel i7 3930 3.8 ghz 6 core, startech firewire card.
Laptop:Hp Pavilion Laptop G6 series amd 2.66 ghz quad core processor,256mb graphics card Ati,8 gb ddr3 ram,750gb Hybrid Drive;Audio Interface;Roland Octa-Capture,8 Mic pres,10 ins/outs, 44.1, 48, 98, 192 khz,Monitors:Adam a7xs,OS:Windows 7 Ultimate 64-Bit, Windows 8 Professional,Daw:Studio One Professional 64 bit version,Cubase 6.5,Plugins:Jbridge, Waves platinum bundle, Fabfilter bundleVst Instrumen,BFD2 64bit, Alchemy, East West Symphonic Orchestra.
[MSN]
Daw stew
Presonic
[Avatar]

Joined: 11/10/2012 14:04:16
Messages: 957
Offline

I was thinking more that the Loudness History was its own track. It would be a loudness overview of the entiresong. Any peaks would be indicated on the offending track.
Windows 7 x64
Core2Duo E4300 Cpu
4gb DDR2 RAM
ASUS P5B-E motherboard
Nvidia graphics card
Lokeyfly
Presonoid
[Avatar]

Joined: 07/06/2012 08:31:19
Messages: 1379
Location: N.Y.C.
Offline

NickWeiland

"what if when the peaks were detected S1 placed markers on the time line? with the offending track title?"

All good ideas! Somehow, the timeline idea with offending track title sounds very functional and very visual. It may not be able to specify the offending track because the peak could be due to several tracks peaking at the same time. Still locating by a marker would be very clear (red flag anyone?). Then all one has to do is locate where the correction in offending track needs to be. Then scrub & determine if the track needs to be adjusted, or is usable or not.
At least how I'm picturing this.

This message was edited 1 time. Last update was at 20/11/2012 05:57:42

In the words of the late great Graucho Marx "I refuse to join any club that would have me as a member"

S1 Pro 2.5, Laptop: VAIO i7, 8Gb, Win 7 X64, SP1. Supporting software, too much to list. Audio Interface: 22 VSL, M-Audio Fast Track Pro, Audiophile 192 PCI-e, Controllers: Novation SL Mk II, M-Audio Axiom, Guitar controllers by Roland GR-50, Percussion controllers: Roland Octapad II, Akai MPD-18. Guitars by: Fender, Gibson, Gretch, Guild, Martin, Taylor, & Yamaha
 
Forum Index » Studio One Feature Requests
Go to: