Mr DJ Mel
I have noticed a bug (or behaviour change) in the latest EA release B9171
In previous versions of VDJ you could set a simple loop from the start of the last played/cue point simply by hitting the loop out button and it would loop back to that last cue/play position you started the track from.
In the latest version what seems to happen now is that if I start a track at cue/play point 1 and create a loop by hitting loop it will work as before. If I then decide, no let me go to cue/play point 2 (ensuring to stop and start the track at that point) and create another loop by hitting loop out again, it will create the loop at the first cue/play point 1 and not from the last play position which was cue 2.
Yes i could hit the Loop in and then loop out and that does work as expected, but ever since day 1 over 15 years ago it has always worked in the previous way and I now am conditioned to use the loop function in that way.
What has changed in the latest version to change this behaviour and can it be reverted?
Thanks
Mel
In previous versions of VDJ you could set a simple loop from the start of the last played/cue point simply by hitting the loop out button and it would loop back to that last cue/play position you started the track from.
In the latest version what seems to happen now is that if I start a track at cue/play point 1 and create a loop by hitting loop it will work as before. If I then decide, no let me go to cue/play point 2 (ensuring to stop and start the track at that point) and create another loop by hitting loop out again, it will create the loop at the first cue/play point 1 and not from the last play position which was cue 2.
Yes i could hit the Loop in and then loop out and that does work as expected, but ever since day 1 over 15 years ago it has always worked in the previous way and I now am conditioned to use the loop function in that way.
What has changed in the latest version to change this behaviour and can it be reverted?
Thanks
Mel
Posted Fri 20 Feb 26 @ 11:26 am
Mr DJ Mel
Is anyone else able to confirm this behaviour too? And if so why has it suddenly changed?
Posted Sun 22 Feb 26 @ 9:00 pm
Mr DJ Mel
As per my last post, could someone on the latest EA test this behaviour?
Posted Tue 24 Feb 26 @ 2:12 pm
Adion
Confirmed, the new behavior is actually the standard behavior for pioneer hardware as well.
Posted Thu 26 Feb 26 @ 11:03 am
Mr DJ Mel
Thanks for confirming - Is a way we have the option retain the older setting, as its a bit of a workflow blocker.
Posted Thu 26 Feb 26 @ 4:34 pm
apopsisdj
It will be fixed in the next update.
Posted Fri 27 Feb 26 @ 3:16 pm
Mr DJ Mel
amazing news - thank you
Posted Fri 27 Feb 26 @ 4:40 pm
Mr DJ Mel
Can confirm this has now been resolved and working as before.
Thank you for addresing so quickly.
Thank you for addresing so quickly.
Posted Thu 05 Mar 26 @ 12:43 pm