You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated my system to the latest SWS plugin v2.14.0 #3. I am using Linux (LMDE 6).
I use a region playlist and when I seek in the playlist the view always jumps to the region which will be the next on the playlist instead of the current
E.g: assume a playlist like:
Region 1
Region 2
Region 3
I click on Region 2 to play and in the track viewport it jumps to Region 3
With this older version is it's working correctly.
I updated to the latest version again and I could also reproduce the issue. I tried in on another machine (/w Ubuntu Studio) the issue is the same there.
The text was updated successfully, but these errors were encountered:
talaberg
changed the title
Region playlist jumps the view to the next regions instead of current
Region playlist jumps the track view to the next region instead of current
Jan 9, 2025
talaberg
changed the title
Region playlist jumps the track view to the next region instead of current
Region playlist jumps the track view to the next region instead of the currently played region
Jan 9, 2025
Hi there,
I recently updated my system to the latest SWS plugin v2.14.0 #3. I am using Linux (LMDE 6).
I use a region playlist and when I seek in the playlist the view always jumps to the region which will be the next on the playlist instead of the current
E.g: assume a playlist like:
Region 1
Region 2
Region 3
I click on Region 2 to play and in the track viewport it jumps to Region 3
I downgraded SWS to the previous version which is available in the archive downloads: sws-2.12.1.3-Linux-aarch64.tar.xz
https://www.sws-extension.org/download/old/sws-2.12.1.3-Linux-aarch64.tar.xz
With this older version is it's working correctly.
I updated to the latest version again and I could also reproduce the issue. I tried in on another machine (/w Ubuntu Studio) the issue is the same there.
The text was updated successfully, but these errors were encountered: