Voted FOR it.

This is not a high priority in my opinion. The arrange view is not really the place for detailed editing.

Hint: Try double clicking on an audio event and edit the event down in the lower audio event edit window instead. (Have you tried this?) Waveform resolution is much nicer down there. It is called the Edit window and for good reason. Its a better place to edit.

Also if you are really serious about editing you should have another program for this eg Adobe Audition or Sound Forge etc. It is all very different in these programs. They are really designed for it. I have always been a fan of running an editor application alongside any DAW. They make the perfect combination.

This is a high priority in my opinion. I wants it, I needs it, and my vote is no more important than everybody else's my precious.

Signzied and voted..

Gollum.

Jemusic wroteThis is not a high priority in my opinion. The arrange view is not really the place for detailed editing.

Hint: Try double clicking on an audio event and edit the event down in the lower audio event edit window instead. (Have you tried this?) Waveform resolution is much nicer down there. It is called the Edit window and for good reason. Its a better place to edit.

Also if you are really serious about editing you should have another program for this eg Adobe Audition or Sound Forge etc. It is all very different in these programs. They are really designed for it. I have always been a fan of running an editor application alongside any DAW. They make the perfect combination.

Sorry jemusic, but the waveforms look absolutely the same to me in the arrange and the edit window..

And, ummmmm, I am really serious, and I do have other programs...but my workflow is based around a couple of Ravens and Studio One works really well with them so I prefer Studio One.

I don't see why we can't have nice looking waveforms like in Cubase. It's not just a cosmetic issue. It really helps when making fine edits.

YMMV. Cheers.

If it can be done then great but hopefully not at the expense of something else. I still have not found any DAW that edits as well and detailed as a dedicated editor though. They seem to be able to do a lot more and very precisely.

They can be a lot faster too. For example in Adobe Audition you can create a key stroke that removes selected audio in one button press. eg editing audio dialog. Select an area, hit one key and it is gone and ripple edited in one stroke. When you are doing lots of that it can really save time.

I am not fantasy project manager but I still wants it.

Jemusic wroteIf it can be done then great but hopefully not at the expense of something else. I still have not found any DAW that edits as well and detailed as a dedicated editor though. They seem to be able to do a lot more and very precisely.

They can be a lot faster too. For example in Adobe Audition you can create a key stroke that removes selected audio in one button press. eg editing audio dialog. Select an area, hit one key and it is gone and ripple edited in one stroke. When you are doing lots of that it can really save time.

Yep. I have lots of multi-step macros like that set up in Raven. Between that and its touch interface, my productivity has really increased.

I certainly wouldn't vote against it. you all have your right to want it, and that's fine. I'm just supporting the idea that a dedicated audio editor such as Sound Forge, and Adobe Audition of which I both use are better in that on either a sample level, or zero point cross fade, they are purposely audio destructive editors, where a DAW typically isn't. So in a DAW, you then (if you want a destructive edit) have to bounce the track if you then want the actual audio clip updated. So it's largely 6 on one hand....etc. True amplified waveform viewing is certainly a good thing on the editing front, but imho, it's also a bit of information overkill if you arent editing or drawing.

Somehow, and this is just my 2 cents worth, Studio One manages to display waveforms in a pretty useful and cool way. Example: Waveforms containing any modulation changes show such a varience in the waveform. To a guitarist using a slight vibrato at some point within the note duration will see that. The same for a horn player, playing some trill, or keboardist, vocalist, etc will see such variations in the waveform. With true peak only waveforms, the only change of that pitch will occur is, if there is some RMS level change, not a pitch change that alters amplitude. My guess is that this might be part of the ARA portion of possibly deciphering the audio, but I have no proof of that. What I do know is that I like the rendering waveform view that S1 places on audio clips/events/edits. It's also apparent frequency variation occurs with Melodyne. And I'm pretty sure people arent pointing to Celemony to change that any time soon. Celemony call them "Blobs", and make no apologies for it.

So it really comes down to using or altering what you have in front of you. Not everyone has some other dedicated audio editor, so it's reasonable to ask for it with S1. Even a bare bones one. Only, just like a video editor, Studio One doesn't expand on such use. You have to go to either the Pro or Consumer outside for such things.

So no, I don't wish Studio One to change it's waveform view. For waveform drawing, which is largely used for smoothing out waveforms on a very small scale. S1 is VERY good on its own right now with zero cross aligning. Pretty automatic, actually.

Waveform display seem fine to me. But if I want to edit on a waveform level (typically using cuts at zero crossings), I would like to have a feature like "go to next zero crossing".
Isn't there already a "tab to transient"? Now I'm thinking about using the sensitivity parameter of "detect transients" and the gain of a track to do what I want.
Darn, got to go to work now. I hate that.
But this post got me thinking about making a macro. Much to say. But I have to go to work.
I hate when that happens! But I'll try to explain what I mean later.

sirmonkey wroteWaveform display seem fine to me. But if I want to edit on a waveform level (typically using cuts at zero crossings), I would like to have a feature like "go to next zero crossing".
Isn't there already a "tab to transient"? Now I'm thinking about using the sensitivity parameter of "detect transients" and the gain of a track to do what I want.
Darn, got to go to work now. I hate that.
But this post got me thinking about making a macro. Much to say. But I have to go to work.
I hate when that happens! But I'll try to explain what I mean later.

Nice idea.
1. A next zero cross frame would speed up locating next zero crossing, especially when zoomed in on such sample viewed levels. .
2. A next transient detection, I was hoping to have something similar. A next/previous "clip detection".
2+. Clip detection also revealed by a red line viewable at any zoom level, including the arrangement view. One would select to scan song for clipping at channel and master outs, and detection would be shown until some level set by user, or component altered such levels.

So maybe a few draw/next/previous editable or detection parameters could fall under this draw request. I'd be up for that. Not to change the current waveform interpretation, but to allow for RMS waveform editing as an option and detection. Might be possible.

I agree that it needs improvement, comparatively speaking to some other products. The OP is right imo, at the sample level it's 'blocky'. Zoom all the way in with some other products and you'll see something much different and better, more like an envelope where the nodes are the samples.

Liking the product and acknowledging it's subjective shortcomings are not (for me anyway) mutually exclusive.

A good compromise might be reached by leaving the waveform display as it is in the track view, but by providing a separate enhanced waveform view when the track is opened in the editor. As it is now, both views look the same to me when zoomed to the same size.

If the basic waveform display in the track arrangement view as we have now is CPU efficient, I would be all for leaving as is, and using the CPU for audio processing rather than rendering fancy eye candy.

But yep, it would be nice to see another level of detail if the transport is stopped and you are zoomed into the editor view.

JohnBW wroteA good compromise might be reached by leaving the waveform display as it is in the track view, but by providing a separate enhanced waveform view when the track is opened in the editor. As it is now, both views look the same to me when zoomed to the same size.

If the basic waveform display in the track arrangement view as we have now is CPU efficient, I would be all for leaving as is, and using the CPU for audio processing rather than rendering fancy eye candy.

But yep, it would be nice to see another level of detail if the transport is stopped and you are zoomed into the editor view.

This could work -- though I suspect that if you have it working for either one, the CPU hit would be the same.

Perhaps this idea is better expressed as a toggle or option? e.g.,

Hi Res Waveform Display: ___On ___Off

Can anyone from Presonus weigh in....?

nk_e wroteThis could work -- though I suspect that if you have it working for either one, the CPU hit would be the same.

I was assuming that if you were editing the waveform, the playback/recording transport would be stopped, so real-time audio processing and the related CPU load would not be a factor. Rendering the enhanced waveform drawing could be done as an offline process.

On the other hand, rendering enhanced waveform drawings during playback/recording could impact real-time audio processing, so I could see the benefit of minimizing that effect by using lower detail waveform drawings when the transport is active.

Lokeyfly wroteNice idea.
1. A next zero cross frame would speed up locating next zero crossing, especially when zoomed in on such sample viewed levels. .
2. A next transient detection, I was hoping to have something similar. A next/previous "clip detection".
2+. Clip detection also revealed by a red line viewable at any zoom level, including the arrangement view. One would select to scan song for clipping at channel and master outs, and detection would be shown until some level set by user, or component altered such levels.

So maybe a few draw/next/previous editable or detection parameters could fall under this draw request. I'd be up for that. Not to change the current waveform interpretation, but to allow for RMS waveform editing as an option and detection. Might be possible.

Lokeyfly nailed it (in reference to my earlier post). Explains everything I was thinking about, and more.
Maybe if I used Cubase, I would not like the Presonus display of waveforms. So I'm not too picky about that. But then, if it could be made better, I'm all for it.

CPU load

The above may or may not be a bad assumption or an unwarranted fear, not sure tbh as I'm not a developer, but waveform peak files are cached so the result that you see on screen or it's performance may or may not rest more with the display processor. Not sure how all of that works on a lower level though, but it doesn't appear to an issue anywhere else.

But again, no personal clue.

Lawrence wrote

CPU load

The above may or may not be a bad assumption or an unwarranted fear, not sure tbh as I'm not a developer, but waveform peak files are cached so the result that you see on screen or it's performance may or may not rest more with the display processor. Not sure how all of that works on a lower level though, but it doesn't appear to an issue anywhere else.

But again, no personal clue.

Yeah it really is no biggy for CPU. The images will be cached and "lazy loaded" whilst Presonus app isn't doing much work. Other DAWs and plugins have much better waveform displayed realtime and that's the main point.