Waveform display returns as in ST3

royandreno

peter waveform with regions, yes please!🙏🏼

AnthonyB

Because I don't use the buttons for live looping and jumping around a song, I will profess ignorance and thus have a very genuine question in the hope I can better understand.

If I use the screenshots in MarkGuitar's post earlier as a point of reference, for someone that really wants these buttons along the lines of the way they are currently implemented in ST4, what does the ST3 implementation not provide?

The ST3 audio regions are still clickable, coloured, etc. the only difference I'm seeing in ST4 is that they are more specific a 'button' than a 'region' - isn't that really just saying ST4 turned a rectangular regional into something with more roundered corners and put a small space between them?

I'm genuienly not attacking anything or anyone here, but I feel like I'm missing something that the current ST4 button-based audio regions provides that the ST3 method does not to cause people to feel so strongly about it. I feel like if I can better understand the ST4 button 'position' I might be in a better position to offer options or alternatives to the conversation.

I think I understand the "stick with ST3 layout" arguments which are:

Don't want more things on the screen that I can accidently hit and cause chaos (which seems to be solvable by making these buttons optional on/off)
Many like the waveform (ok, Peter is open to finding a way of returning that in around the song title area of the screen)
Many like the audio regions overlay on the waveform (ok, this saves some screen realestate, combines UI elements that relate to song position, in theory this could also be something that could be turned on/off.. ooh, @peter what if there was an option not not just turn the regions/button on/off, but to have them on but not 'clickable'? that way they act as visual guides but remove the risk of people clicking on them accidently? For me, and a few others, this would be something I'd have on during a rehearsal where you might want to jump to different parts of the song intentionally to run over it, but at the gig, it's like the 'safe mode' concept someone previous aired.)

Sometimes not having a stake in a decision helps you see more clearly 🙂

peter

@Damir Please don't hijack this thread, it is solely about the waveform view and not about anything else like the queue button.

Everyone else: If you agree with this request, upvote the thread in the first posting. There are only 2 upvotes, but from the comments I sense a much higher interest in this topic.

AnthonyB The ST3 audio regions are still clickable, coloured, etc. the only difference I'm seeing in ST4 is that they are more specific a 'button' than a 'region' - isn't that really just saying ST4 turned a rectangular regional into something with more roundered corners and put a small space between them?

The main difference is that in ST3 small regions could be so small that you could effectively not tap on them. The buttons in ST4 ensure that even small regions are large enough to tap on.

AnthonyB what if there was an option not not just turn the regions/button on/off, but to have them on but not 'clickable'?

The regions are also displayed in the titleview (the colored rectangles). I guess if you don't need the region buttons or the waveform, you can still use that to find out where you are in the song.

AnthonyB

peter The regions are also displayed in the titleview (the colored rectangles). I guess if you don't need the region buttons or the waveform, you can still use that to find out where you are in the song

AH OK, so these are classified as different entities? We have

The audio regions in the titleview (i.e. ST3 view), AND
New Audio Region Buttons
Is that correct?

And it is the latter (Audio Region Buttons) that seems to be quite polarising in opinion.
I'm assuming the buttons and the regions are both using the same data source, but are just different 'views' or ways of representing the Audio Region data?

So like you've said before:

region buttons (the new ST4 feature)
waveform with regions (like ST3)
none
while you are at it, you may as well add
waveform without regions, because you can guarantee someone will want that 🙂

My question if that is firming up as a likely course of action is what would be visible for a Network Session Client? Because in ST3, the regions do not display on the waveform for a Client. In ST4, if you selected 'waveform with regions' on the Host, would a client get same? In short, I just want to make sure the Audio Region data is somehow viewable on a Network Session client regardless of which method you choose on the Host to view that info.

peter

Yes, that's correct.

I don't see why anyone would want the waveform displayed without regions if they define regions in the first place. If you don't want regions, don't create regions.

AnthonyB My question if that is firming up as a likely course of action is what would be visible for a Network Session Client?

The clients would display whatever is configured on the client. It's the same with lyrics vs pdf. If the client prefers to view lyrics, it will show lyrics no matter what you have selected on the host.

peter

Implemented in build 1832 including full network client support. Network clients with configured waveform view will ask the host for a waveform. You need both client and host on build 1832 for this to work.

AnthonyB

Thanks Peter!

I just tried this out and... was surprised? I'll be interested to see feedback from others, but the new waveform+audio regions hasn't ended up where I expected.

I was assuming that it would be up in the top display section where the Song Name, Clock, Elapsed time, etc. is. Especially as the song progress bar also already has the colour segments.

By putting it on the lyrics pane, if you have the Queue/Playlist sidebar open, it gets squished up and is (IMHO) unusable. If you don't have the sidebar open, it's great, and in fact gives more room (greater screen width) by not being in the song title display section.

Hmmm... quite the conundrum. Pros and Cons for both.

I guess it will depend on whether people tend to want to keep the sidebar open, and how wide they set it, as to whether the current location is usable.

MusicMan81

AnthonyB I understand your needs but I do use a lot the regions and having them below the title and with more room is a dream for me…

Might slaving the bar with the audio regions to be part of the top display and forcing the side bar to open below the regions work for you? Maybe for others too? This way, no one loses sight nor squishes the waveforms and get to see the side bar. It might be a good compromise?

AnthonyB

MusicMan81 Might slaving the bar with the audio regions to be part of the top display and forcing the side bar to open below the regions work for you? Maybe for others too? This way, no one loses sight nor squishes the waveforms and get to see the side bar. It might be a good compromise?

Yeah, I think having the Audio regions (waveform or buttons) in their own pane that sits under the top Songtitle display pane, but above the sidebar/lyric panes, would be perfect. That way they are in a pane that can always use the full width of the screen, and it you don't want waveform or audio regions, then the pane just goes away and the sidebar/lyrics panes move up vertically.

peter

Integrating the waveform into the titleview does not offer enough space for the waveform to really be usable (especially not enough height).

I could attach the waveform and audio regions panel to the top and let the sidebar start below it. But I was hesitant because that would make the sidebar unusable on iphones in landscape mode.

MusicMan81

peter

Got it…. As @AnthonyB said… every idea is a conundrum lol… what might work for some people is detrimental for others.

The solution that I saw in another app is they resize everything the same way in any device “scaled”. Whatever you see on vertical or landscape in an iPad 11” you’ll see the same way on an iPhone, but scaled… that being said, it might work for some and not so much for others.

« Previous Page