NOTE: Please use the search function above before posting to avoid creating duplicate topics.
- Device model (e.g. 2020 iPad Air 4th Gen): Intel i7-14700F with 32GB & NVMe SSD
- Version of operating system (e.g. macOS 14.4.1): Windows 11
- Version of djay (e.g. 5.1.2): 5.6.6
- Hardware/controllers used (e.g. Reloop Mixon 8 Pro): Rane Seventy
- Hardware firmware version (e.g. 1.0.1):
- Please consider sharing a short video or screenshots to help clarify your issue
A) SUMMARY OF ISSUE:
- From time to time when changing cue points the waveform shows empty space before the last pressed cue point for a few seconds before reappering. It is only visual because the audio is instant but it is confusing as it looks like I jumped to the beginning of the song. Also when using Instand Double it will take about a second before the song is duplicated. In both Serato and Traktor everything works instantly without any delay so it looks like some optimization issue in DJay.
Hi @Scratch-E_Con, welcome to the Community! Thanks for the setup details and issue explanation. Let’s focus on the blank waveform issue for now. I have some follow up questions for you to help isolate the issue.
- Please share your exact Windows 11 build (Settings > System > About, e.g. 24H2 / 26100.xxxx)
- What Rane Seventy firmware version # are you running?
- GPU model and driver version?
- Does it happen with the Rane Seventy disconnected, using only mouse and keyboard?
- Was this present in earlier djay versions? If so, which version was last known good?
- Does it happen with local files, streaming tracks, or both? If streaming, which service, and does it reproduce with a different service?
- Does it happen with all tracks or only certain ones? Any pattern by file format, bitrate, duration, or source folder?
- Are you using the (built-in) MIDI mapping or a custom mapping for the RANE Seventy.
- Have the Audio Device Settings been changed from default? Does increasing the buffer size change anything?
Please also provide the following:
- A short screen recording of the waveform blanking, showing several cue point presses, including at least one failure and one normal press for comparison.
- If possible, a recording with Task Manager visible alongside djay while the blank waveform issue is happening.
- Screenshot of djay Settings > Audio Device.
Thanks for answering my questions and sharing those screenshots @Scratch-E_Con - this is very helpful information! I have a few more follow ups before I share this with our engineering team to see if they can produce the issue:
- Can you please capture and share a short 30-60 second screen recording showing several cue presses including at least one failure and one normal press, ideally with Task Manager or an overlay showing CPU and GPU usage?
- Roughly how many cue presses out of ten show the blank waveform?
- Does this happen on a short track, for example three to five minutes, at an early playhead position?
- Does it happen on Deck 2 as well as Deck 1, and does it ever affect both decks at once?
- Does the Instant Double delay persist in Internal mode with no hardware connected, and with the maximum buffer?
- Does the waveform zoom level change the behavior?
Thanks again for you help!
Thanks again @Scratch-E_Con, this is exactly what I need to escalate this issue to our engineering team for further review. I’ll report back here when I hear back from engineering. They may require additional data from you, but I’ll let you know either way.
Hi, were you able to reproduce the issue?
Hi @Scratch-E_Con, thanks for checking in. Our engineering team has not reproduced this issue yet. I’ll share more news here when I have it.
Hi @Slak_Jaw some more info on the poor performance when using ‘instant double’: it is very slow when duplicating large (400 MB) .wav files. Yet still in both Traktor and Serato these files are ‘doubled instantly’ so my guess it is a software optimization issue. Also I am using high speed NVMe SSD’s so read/write should not be the problem.
Hope this helps.
Thanks for the additional info @Scratch-E_Con. I will pass this onto engineering for reference. In the meantime, they were able to reproduce this issue on their setups and are investigating further. I’ll share more news here when I have it. Thanks!