image description


auto detect peaks
  Forum Index » Studio One Feature Requests 
Author
Message
guitarism
Prenoob

Joined: 06/03/2012 03:56:12
Messages: 75
Location: Nagoya, Japan
Offline

Good idea. The kind that makes you think "how could they not have something like this?". With flagging the peaks, keyboard shortcuts should be available so you can quickly jump peak-to-peak. I do mostly purely acoustic recordings and prefer to ride the levels rather than use limiting if I can avoid it.
iMac 27 | 2.66 GHz QuadCore i5 | 16 GB RAM | OSX 10.7 | Fireface 400 | Studio One 2 Pro
tkk
Prenoob

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

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've noticed that whenrendering multi output VST instruments to audio that it tells you that clipping has occurred. This happens through the render process. Maybe in a future version we will see the OPs request implemented.
Windows 7 x64
Core2Duo E4300 Cpu
4gb DDR2 RAM
ASUS P5B-E motherboard
Nvidia graphics card
Daw stew
Presonic
[Avatar]

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

If it was possible to do Nick Weiland's idea then yes, that would make the FR even better. Track specific flagging of peaks would make it very easy to see which event was hot.
Presonus could include a Zoom To Peak Flag function or where there is multiple peaks a Next/Previous navigation function to jump to and from peak markers
Windows 7 x64
Core2Duo E4300 Cpu
4gb DDR2 RAM
ASUS P5B-E motherboard
Nvidia graphics card
Ian13
Prenoob
[Avatar]

Joined: 27/04/2012 21:41:26
Messages: 78
Offline

Have not worked with Sonar in years, but I recall the track peaks were very useful.
They also had busses represented in the track view with their own peak flags.
Where would that happen in S1?
The forum member with the loudness track idea was on to something.
Intel Core 2 Quad Q6600 @ 2.4 GHz
ASUS P5K-V MB
6 GB RAM
NVIDIA GeForce GTX 560 Ti
PCI Firewire Card TI Chipset
Win 7 Ultimate x64 SP1
Studio One 2.5 (32 and 64 Bit)
RME Fireface 400
Pod HD500
Superior Drummer 2
Revalver Mk3
Daw stew
Presonic
[Avatar]

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

Really could have used this last night
Windows 7 x64
Core2Duo E4300 Cpu
4gb DDR2 RAM
ASUS P5B-E motherboard
Nvidia graphics card
whitePhazer
Presonic
[Avatar]

Joined: 09/11/2011 00:16:29
Messages: 382
Location: Somewhere north of Manchester UK
Offline

Win 7 64bit
Studio One Professional x64 (always latest update)
Intel i5 3.30GHz overclocked @ 4.20 GHz
Azus deluxe Motherboard
8GB RAM
M-AUDIO - Audiophile 192
M-Audio Oxygen 49
Akai MPD26
American Fender Stratocaster Deluxe
Retired, plenty of spare time
My Soundcloud

Daw stew
Presonic
[Avatar]

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

this feature would certainly make it much quicker to identify events that are pushing the master fader into clipping.

This message was edited 1 time. Last update was at 30/03/2013 16:31:03

Windows 7 x64
Core2Duo E4300 Cpu
4gb DDR2 RAM
ASUS P5B-E motherboard
Nvidia graphics card
trumpet
Prenoob

Joined: 05/09/2011 13:38:19
Messages: 83
Location: India
Offline

One simple idea is to color code the fader bar (currently in black) according to how 'hot' the signal is. (the vertical bar on which the fader icon moves up and down)

This definitely will let everyone on the mixer realize where his levels are going.

Colors (in order of how hot the signal is)

Blue -> green - > yellow -> orange -> red

Blue to signify - signal;s quite cold, you can crank up
Green - everything's perfect - Life is good
Yellow - Things can go out of hand - be careful
Orange - There is some problem - put on your thinking caps!
Red - You've blown it!

Just a thought

This message was edited 1 time. Last update was at 11/04/2013 16:50:35

Windows 7 SP1 | FireStudio Project
Intel i5, 3.2 Ghz | 8 GB RAM | 500GB HDD | Korg Triton V3 | Presonus S2,
Behringer Xenyx 802, Roland DR 880, Ibanez 5 stringed Bass
Samson CH 700 | Sony MDR XD 100 |
Rhode NT 1-A | Samson A6 Monitors | NI Komplete 8 | Korg MI & Wave Station | Swarplug | Hypersonic 2| HA400 Mic Preamp |
Lokeyfly
Presonoid
[Avatar]

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

Another take on identifying and fixing peak overload occurrences would be:
When overload peak indicator shows red, simply mouse over the red indicator, and a drop down list displays the song location, and track(s) of the occurrence. By then clicking on any listing in the “Peak list” (I’ll call it) moves the song pointer two or so measures before the peak to audition. There is also (in the list) a “-3 dB” button column to reduce the peak at that immediate location, also taking the pointer two measures before the occurrence. Therefore you have the option to listen only, or reduce the peak instantly. 1 dB reduction is optional, I’d guess.
This ability to select and audition the occurrence also opens up the wave or instrument editor [F2] so that there is an instant view of where the peak happened. Basically, S1 simply opens the [F2] editor really for easy viewing.

Finally, there is also the option in the drop down peak list to simply “Fix”, which causes S1 to fix the anomaly based on whatever criteria it needs to do this. Perhaps reducing the overload peak (or spike) by 1 dB and calculating the sum until no peak occurs at the track(s) or main out, buss, until the peak no longer occurs in the audio path.

I think this is feasible, visual, and provides fix options that are fast, but would appreciate some feedback.

This message was edited 2 times. Last update was at 13/04/2013 16:01:12

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
NickWeiland
Presonoid
[Avatar]

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

Lokeyfly wrote:Another take on identifying and fixing peak overload occurrences would be:
When overload peak indicator shows red, simply mouse over the red indicator, and a drop down list displays the song location, and track(s) of the occurrence. By then clicking on any listing in the “Peak list” (I’ll call it) moves the song pointer two or so measures before the peak to audition. There is also (in the list) a “-3 dB” button column to reduce the peak at that immediate location, also taking the pointer two measures before the occurrence. Therefore you have the option to listen only, or reduce the peak instantly. 1 dB reduction is optional, I’d guess.
This ability to select and audition the occurrence also opens up the wave or instrument editor [F2] so that there is an instant view of where the peak happened. Basically, S1 simply opens the [F2] editor really for easy viewing.

Finally, there is also the option in the drop down peak list to simply “Fix”, which causes S1 to fix the anomaly based on whatever criteria it needs to do this. Perhaps reducing the overload peak (or spike) by 1 dB and calculating the sum until no peak occurs at the track(s) or main out, buss, until the peak no longer occurs in the audio path.

I think this is feasible, visual, and provides fix options that are fast, but would appreciate some feedback.



hmm an automatic fix.. isnt that just lazy mixing? im ok for the detection but for automatic fixing?
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 like Lokeflys idea. Its a Peak History. If I'm understanding him correctly, the red peak indicator icon on the master fader could be a peak history button, whereby clicking it reveals a time based list of where peaks occurred. Great idea and it removes the need to have flags on the timeline.
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 wrote: hmm an automatic fix.. isnt that just lazy mixing? im ok for the detection but for automatic fixing?


Not at all. First of all it's an option. Secondly you are audtioning in a number of ways either to hear any "fix" which you need to do based on any adjustment you make really. I'm a purist myself when mixing NickWeilland so I appreciate your take on this.

I personally would use the auto option less in a final mixdown. It would be best served in the ealy portion of laying tracks IMO.

Finally, every selection would take the user two measures before the peak incident. Weather they want to not listen and go past would be their laziness. Not something I would do. This function would only steer you there. Probobly just like you, in that I don't believe in a DAW mixing for me, but this is a nuts and bolts "option" (or tool) to help remove something that yes, should be listened to how the outcome would be. Just like listening to what a compressor or limiter cut back on. That's not making things lazy, it's an aid.

Hope this helps explain your concern.

Thanks!
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

Daw Stew: I like Lokeflys idea. Its a Peak History. If I'm understanding him correctly, the red peak indicator icon on the master fader could be a peak history button, whereby clicking it reveals a time based list of where peaks occurred. Great idea and it removes the need to have flags on the timeline.


Exact a lee Daw Stew!
I like the flags idea, but tried to make this as seamless a fix as I could. I may post a visual of the peak list later when I can to help clarify any questions.

The beauty of this method is, you run play again when auditioning. If a peak still is present, the peak list (available at any red indicator) updates. Nice right?

Thanks!

This message was edited 1 time. Last update was at 13/04/2013 16:54:45

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
NickWeiland
Presonoid
[Avatar]

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

Daw stew wrote:I like Lokeflys idea. Its a Peak History. If I'm understanding him correctly, the red peak indicator icon on the master fader could be a peak history button, whereby clicking it reveals a time based list of where peaks occurred. Great idea and it removes the need to have flags on the timeline.


i like that idea that way youd get a proper representation and a more indepth detailed description if there was a tab in the master section of the mixer that was expandable telling you at what time and what track and by how much db it was offending. but i dont want it to notify me if its something that sounds good but isnt distorted. i currently dont understand studio ones message of its clipping but i dont hear any clipping???
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]
 
Forum Index » Studio One Feature Requests
Go to: