Have a feature request or suggestion? Post your idea here!

Post

7 followers Follow
3
Avatar

rekordbox dj waveform zoom out

Please upgrade the waveform to zoom out one more time than the current furthest zoom. It helps me line up builds and drops perfectly.

Kevinesteban

Official comment

Avatar

Passing this along to the rekordbox team. Thanks for your feedback.

Pulse
Comment actions Permalink

Please sign in to leave a comment.

17 comments

0
Avatar

Agree. would love this option too. Another good way would be to put a cue marker on the drop and then you can see how close you are to the cue point. I often have to move forward 4 or 8 bars if i miss, but thats easy enough too..

DJ Chase 0 votes
Comment actions Permalink
0
Avatar

Yes being able to zoom out further would be very useful. And also being able to zoom in a little further to set grids would be nice too. 

(KB) Kieran Bowley 0 votes
Comment actions Permalink
0
Avatar

The playin waveform should be totally out zoomable, to be able to see the entire scrolling waveform on the current view, seriously ! It helps so much with tracks that you play on the fly and have no clue about besides the actuall duration. Saves me lotta head ackes when people request stuff and i dont have cue points ready set !!! Dont see how this has not made it through just yet, it's annoying. The very best thing about scrolling waveforms is the visual cue when mixing in the "dark" and at this time, RB zoom out is pretty much useless to say the least !! C'mon, do i have to switch platforms again, dont i get enough piss off when RB is crashin on me mid gig ??? Make it happen, dont wanna fall back to Traktor again !!

Jad Focstakuorta 0 votes
Comment actions Permalink
0
Avatar

@Jad > That's what the overview waveform is for.

If you are having problems with the software crashing, please file an inquiry ticket here and our rekordbox support team will be able to gather some additional information to assist you in resolving this issue.

Pulse 0 votes
Comment actions Permalink
0
Avatar

And what exactly am i suppose to say in there, that is crashed while performing ? Yeah, that's exactly what happened, dunno why, dunno how, just froze, sound was goin through but screen GUI was frozen solid !!! Heluva way to start up the night, luckly for me, was just a few people around at that hour, otherwise, i'd've been totally screwed !!!

Jad Focstakuorta 0 votes
Comment actions Permalink
0
Avatar

@Jad > If they can determine that it crashed because of a combination of the graphics driver and hardware, that could certainly help you and/or others.

Pulse 0 votes
Comment actions Permalink
1
Avatar

Bump for the original request. This should be a no brainer to implement, and its utility is crystal clear.

Since the original post is from over 3 years ago, would it be possible to have an update on it?

Cheers

 

RJ Hode 1 vote
Comment actions Permalink
0
Avatar

When obvious functionality like what's being requested here is consistently ignored I feel completely hopeless. Pioneer DJ controllers are only as good as the software they control.

Manuel Fernandez 0 votes
Comment actions Permalink
0
Avatar

Hi Pulse. Thank you for the update.

It is a bit disheartening that this has not been picked up.

Quite a few people here have explained that it would be very useful.
It is also rather simple to implement.
I think a lot of people feel that this happens too often... good suggestions from the forum, with a lot of positive feedback are ignored, only to prioritise other features that people don't care much about.

I have a software development company myself and I am not sure I understand why Pioneer would do this.

Perhaps if there was some transparency on the ticketing system, or at least on the feature implementation pipeline, we'd better understand why some very legitimate requests that would make RB better are ignored for years. Or forever.

I am not suggesting that the design of RB should be democratic. But I thought that "listening to the voice of the (paying) customer" was some kind of established principle.

Hope you don't mind the criticism. I am putting it forward in the spirit of making RB the best it can be. And to start a constructive discussion with Pioneer and with all the good people here that spend time on the forum because they love and use your product.

Cheers,

RJ

 

RJ Hode 0 votes
Comment actions Permalink
0
Avatar

@RJ They do this because they don't have any significant competitors. Another possible reason might be that on CDJ displays the waveform can't zoom out that far, and Pioneer don't want Rekordbox to be better than their flagship product in any way, because they ultimately want everyone to own a CDJ system. Remember, rekordbox
Is just an accessory to their controllers, not the other way round.

Manuel Fernandez 0 votes
Comment actions Permalink
0
Avatar

And while we are on the subject of waveforms, it would be nice if they could be taller. The argument that 'there is not enough screen space available' no longer holds valid. No my 15" 1080p display—a very common size these days—at 100% scaling I have two inches worth of browser at the bottom when all panels are visible. The browser only needs to be seen when loading tracks, so I don't see any reason why the waveforms can't be taller.

Manuel Fernandez 0 votes
Comment actions Permalink
0
Avatar

There are literally hundreds of requests that we place into a tracking system, and depending on the type (is it a request / bug report), importance (urgent to operation like can't export songs, or like this - wanting a wider zoom), feasibility (how hard is it to actually do what's being asked), cost / resource (this will take several engineers a few months), return (is it worth actually doing this) and finally, scheduling (is it something that could be worked on while the next version is being prepared), all play into whether or not it gets implemented. It's not just a matter of "Can you make it do this?" "Here it is."

And no, there is no information available for the public on the status of these requests because they go through so many different groups and there are so many moving parts.

Pulse 0 votes
Comment actions Permalink
0
Avatar

Thanks for your reply Pulse. I think the reason why requests don't get done might be that last bit you mentioned: "because they go through so many different groups and there are so many moving parts." Small dev teams are more agile and can make decisions without needing approval from five layers of management and people who don't even use the software. 

Manuel Fernandez 0 votes
Comment actions Permalink