Page 1 of 1

after upgrade to 2.2.2, not remembering last postion?

Posted: 15 Feb 2016 21:36
by VlcWannable
I upgraded VLC from 2.2.1 on a Win7 and an XP box.

With 2.2.1, both would remember screen postion (although win7 would ask each time).

Now, XP doesn't remember or ask, and Win7 remembers without asking (which is perfect).

I did a normal upgrade and said yes to the screen asking if I wanted to keep my prefs.

I have Interface->Main Interfaces->Qt->Continue Playback set to 'always' for both XP and Win7.

How can I resolve this for my XP box?

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 15 Feb 2016 23:43
by VlcWannable
Was able to resolve this by setting 'continue playback' to 'never', saving, closing, and then setting 'continue playback' to my original setting: 'always'.

As it clearly showed 'always' and was not functioning after the upgrade, there may be some upgrade issues with pulling over settings?

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 22 Feb 2016 06:03
by dolphinwigs
I too am experiencing this. I am no longer getting the Continue Where I lift Off button option when I restart a video like I did before. I have tried every fix I have seen (which is not that many as this is a very new version of VLC so not many people have posted about this issue yet), including the ones on this page. I like that some bugs have been fixed, but this feature is something I use ALL the time every day. Has anyone found a fix or know if VLC is working on fixing this?

Thanks! :D

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 26 Feb 2016 05:37
by VlcWannable
I thought that it was continuing playback after I changed from always to never and back again, but ... now it is Never remembering my place on XP - so ... this feature is definitely broken.

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 20 Mar 2016 21:59
by dolphinwigs
Has anyone found a fix for VLC not giving the option to Continue Playback where you left off at yet?

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 31 Mar 2016 15:52
by joe_schmo
I would like to see a resolution as well.

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 31 Mar 2016 22:54
by iJunaid
Not yet, the latest nightlies in both the 32-bit and 64-bit variant for Windows 10 for 2.x.x and 3.x.x have not fixed this bug even though the bug report tracker says it's been fixed.

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 26 Apr 2016 07:30
by dolphinwigs
Any new developments? I still am not able to "Continue Playback" like I could with 2.2.1. Also I have noticed that with some video files if I skip forward or backward at ALL it has a long time delay before the audio kicks back in. But then the rest of the time the same files play just fine... Some files don't do this at all while others do. It's really random. This never happened in the past. I figured since I was posting that maybe someone else here noticed this additionally with the new version as well.

Anyways I am mainly interested in seeing if the continue playback issue has been fixed. Any progress?

Thanks.

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 28 Apr 2016 21:32
by 2mg
Same here, fresh Win7 x64 installation, doesn't ask to resume playback.

Tried all Qt settings.

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 03 May 2016 19:50
by BladeEdge
I am also having that same problem but I am running win 10 x64 all other programs work. up grading from v2.1 where it did work. the above fix did not work sorry.

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 07 Jun 2016 23:20
by dolphinwigs
If it helps at all I am using Windows 8.1 Pro 64-bit.

Re: after upgrade to 2.2.2, not remembering last postion?

Posted: 03 Aug 2016 05:53
by iJunaid
I'm still having this issue with the stable release of 2.2.4 and the nightly from 7/31 for 2.2.5.

Continue playback is working though for the nightly from 8/2 for 3.0.0.

Can anyone give us an update on why this marked fix even though it isn't?