I'm a new user using Kdenlive 17.08.1 64 bit with Windows 10 64. Having a curious issue. When I start the application and press space bar playback starts. When I press it again playback stops. Then when I press it again playback does not start up again. I have to press the right arrow key a few times and then press the space bar and go back and forth and then playback starts again this is very unusual behavior. Have to repeat this process every time I stop playback. Also the graphical play/pause/stop button works once then stops working. I installed Kdenlive as per instructions on the website where I downloaded the application. I also installed the ffmpeg shared application. I also have Shotcut and Lightworks installed and all the keys work perfectly with both applications. So I'm wondering if it's a flawed install of kdenlive or is it something that's missing in my system. I'd very much like to try out Kdenlive because it seems to be very robust and solid application. Unfortunately this keyboard issue is not making things easy. Thank you for any insights. Never mind. I downloaded and installed Kdenlive 17.04.3 and everything seems to work fine. No keyboard or other issues. [b] [u]There is a bug in 17.08.1.[/u][/b]
confirmed also on 17.08.2 (win64)
but is not a keyboard issue, the same thing can be reproduced using the "play" icon on preview windows.. it start just 1 time.. after that the PLAY is just a "STILL" function frame by frame.
(In reply to Davy Bartoloni from comment #2) > but is not a keyboard issue, the same thing can be reproduced using the > "play" icon on preview windows.. it start just 1 time.. after that the PLAY > is just a "STILL" function frame by frame. That is exactly what happened with 17.08.1 and 17.08.2.
(In reply to kambiz.khatami from comment #3) > (In reply to Davy Bartoloni from comment #2) > > but is not a keyboard issue, the same thing can be reproduced using the > > "play" icon on preview windows.. it start just 1 time.. after that the PLAY > > is just a "STILL" function frame by frame. > > That is exactly what happened with 17.08.1 and 17.08.2. This bug is still present in version 17.12.0 which I installed tonight. Reverting back to 17.04.3 which still works.
*** This bug has been marked as a duplicate of bug 388064 ***