The master channel has a little thing that dispays the peak amplitude values reached so far for L and R channels.
I think this could be improved by displaying where the peaks occurred in each instance in the format PP;LL where P is pattern number and L is line
Eg.
PeakL:10dB—PeakR:21dB
–@ 11;32-------@ 12;46–
I realise there is a spatial constraint however.
How about a tiny, tiny button then, just a blob really, that puts the cursor where the peak occured?
Well that would be perfect really!
Or one could double click or right click the already existing text itself.
double clicking the text +1
This could be usefull!
I was thinking of peak meter readings per channel but this sounds better!
why not have both…
+1
I’d love to be able to identify peaks in this way. As in simply have a jump to last peak function. I assume this peak would be the last peak since a play command was triggered?
Yeah that’s how it works at the moment. The function could either just take note of when it occurred or add the jump back to that peak function.
Why not USE the ears instead of pacify them more and more?
Well, measuring peaks on a certain line won’t give you an exact location of where the cause is of the peak.
It can only give you a sign that all currently processed audio crossed a limit.
Speaking of removing peaks:
In some cases, turning off effects right before the moment might remove the peak, (instead of filtering or compressing), or playing a specific note at a lower velocity amplitude might remove the peak, or spreading a stereo audio signal a bit wider on the channel might remove the peak or even cut either of those L/R channels might remove the peak…
So many tricks to remove peaks, but having to search for the cause makes it a little easier with this function.
Ears don’t always do this…
I am aware of this, but the rough indication of where the peak occured is a good place to start and work back from. Generally speeking, most peaks in my work are cumulative “accidents” resonance on filters and feedback on delays and the like are most often the culprits. I like using very high, squelchy res settings from time to time but where they cross the line isn’t always obvious and often attributable to another pad like intrument with a slow attack.
@ Butka:
My songs, or atleast my good songs, always start out very long indeed before being edited and rearranged down to a more listenable length and structure. Generally I’ll try and get the mixing roughed out at this stage too, or as i go along. Sometimes later processing introduces peaks in other parts of the song. Personally, I find mixing and eqing etc far more boring than the compositional/creative process. So for me, any timesaving in this dept is a good thing. In the mean time I can put my ears and time to better use and keep the track fresh for myself. Aswell as this I’m not a big fan of limiting/compression but like to keep my music loud in parts.