Looping causes zoomed view in overview waveform

NOTE: Please use the search function above before posting to avoid creating duplicate topics.

  • Device model iPad Pro 2024
  • Version of operating system latest
  • Version of djay *(5.3+
  • Hardware/controllers used Reloop Mixon 8 Pro):

Summary of the issue: In some modes (most notably 4 deck non-hardware mode) when you loop or use some other loop like functions (slip loops etc), the overall track display zooms in to show the loop redundantly. You see loop on your main window but also now you can’t see overall position in track top of screen but rather it becomes a zoomed in version of your loop. In hardware mode this doesn’t happen and overall track view is maintained. This is how it used to be for most if not every mode and it’s important because you see where loop is overall and time in track etc. imagine if you looped on Cdj and both your track view and main view both showed the loop zoomed in… definitely think this is formally at the level of a bug because I can’t see logic for it but correct me if I’m wrong!

How to reproduce the issue: use 4 deck mode on iOS iPad and loop a track and look at track overall track view

Hi @17mics, this is indeed unexpected behavior. Good catch! I have shared this with the engineering team so they can make the adjustments in an upcoming release. I’ll report back when I have more news. Thanks!

1 Like

Since the new update, when you scrub the track on 4 deck mode the view of the entire song (next to the playtime and album art) zooms in, this happens on iPad when touching the main waveform or when decks are plugged in. Is there anyway to stop this, I don’t want it to zoom right in like that when I’m scratching or scrubbing through a song.

I’m sorry, I don’t know how to post images here so i had to use Imgr instead:

Hi @Matthew_Penhaligon, I’ve merged your new topic with this existing one. Please see above for more details. Thanks!

Hi @17mics and @Matthew_Penhaligon, engineering has identified the issue and is working on a fix which should be included in an upcoming update (likely 5.3.2). Thanks!

1 Like