Gale, here are the steps:
- create a chirp tone
- hold down dot (.) or shift-dot until you shoot over the right boundary
- The play cursor/ selection moves to the end of the track or nearly so.
- try different selections and movement keys.
Audacity 2.0.7 alpha Rev 13536 (with the second patch applied), Host Wasapi.
Improved seeking
-
Robert J. H.
- Posts: 3633
- Joined: Thu May 31, 2012 8:33 am
- Operating System: Windows 10
Re: Improved seeking
I don't either.Gale Andrews wrote:Robert, can you please write steps out 1,2,3 for the bug. I can't understand exactly what you mean.
It doesn't shoot over the right boundary. It stops at the endRobert J. H. wrote:hold down dot (.) or shift-dot until you shoot over the right boundary
On my machine, it stop at the end of the final sample period.Robert J. H. wrote: The play cursor/ selection moves to the end of the track or nearly so.
"Shift + dot" does the same.Robert J. H. wrote:try different selections and movement keys.
"K" does the same.
"End" does the same.
What happens for you?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
-
Robert J. H.
- Posts: 3633
- Joined: Thu May 31, 2012 8:33 am
- Operating System: Windows 10
Re: Improved seeking
The audio is playing until the end is reached.steve wrote:What happens for you?
All following keys are interpreted as their counterpart in stop mode.
This means that the cursor will be moved from now on, either from its original position or the right selection boundary.
In other words, the holding down of the key seems to be interrupted at the end and resumed which leads to that odd behaviour.
I suspect that it is somehow caused by the screen reader. That would explain why you do not have this problem.
The issue remains if I quit NVDA, but disappears after a restart of NVDA, i.e. the selection is not altered anymore.
I hope it stays like that.
Another oddity: When I hold point (. down in order to seek and press at the same time space (to stop playback), Audacity crashes (but who does such a thing...).
-
Gale Andrews
- Quality Assurance
- Posts: 41761
- Joined: Fri Jul 27, 2007 12:02 am
- Operating System: Windows 10
Re: Improved seeking
I can reproduce that issue without NVDA on, but only in the patched build.Robert J. H. wrote:The audio is playing until the end is reached.steve wrote:What happens for you?
All following keys are interpreted as their counterpart in stop mode.
This means that the cursor will be moved from now on, either from its original position or the right selection boundary.
In other words, the holding down of the key seems to be interrupted at the end and resumed which leads to that odd behaviour.
I suspect that it is somehow caused by the screen reader. That would explain why you do not have this problem.
The issue remains if I quit NVDA, but disappears after a restart of NVDA, i.e. the selection is not altered anymore.
I hope it stays like that.
- Generate Tone 5 minutes, place cursor at 10s, press and release SPACE, hold down period (dot).
- When the playback stops, the editing cursor moves from 10s to the end of the track then stops there.
- Select from e.g. 1 minute to the end, press and release SPACE, hold down period (dot).
- When the playback stops, the editing cursor moves from 10s to the end of the track then stops there, removing the selection.
I can reproduce that in HEAD on Windows and Mac (but not on Linux) so I made a P4 bug for it: Bug 781 – Crash pressing SPACE while holding down short seek shortcut.Robert J. H. wrote:When I hold point (. down in order to seek and press at the same time space (to stop playback), Audacity crashes (but who does such a thing...).
Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual
Re: Improved seeking
I'm on the case! I reproduced it in Windows, and it was like something I had seen before but not with the unmodified source tree. I uploaded a patch to Bugzilla. Thanks to Robert and Gale for a proof that this crash was not a result of any change of mine.
Re: Improved seeking
... and James has committed my fix.