Rikitik / project-valerie

Automatically exported from code.google.com/p/project-valerie
0 stars 0 forks source link

PVMC crashing Vix3.0/OpenPLI3.0 on file playback finish #598

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hello Erik and the PVMC team.

What steps will reproduce the problem?
1.Open any file in PVMC on VIX3.0/PLI3.0 image.

2.at the end of file playback, where usually the pop up for stop/continue/stop 
and exit/play next appears the PVMC plugin causes a crash to green screen.

3.PVMC is not offering the option of 'play next' for episodic content.
For some reason episodic content is treated the same as individual movie files.
The plugin crashes at the end of file playback, but one can press 'stop' and 
exit the file before playback ends although episodic content won't offer the 
'play next episode' option

What version of the product are you using?
Revision?
Issue is on r1239, r1260 and r1263.

I've attached both the Valerie Debug log and the Enigma2 crash log.
Thanks in advance for any help on this issue.

Original issue reported on code.google.com by bryan.od...@gmail.com on 22 Aug 2012 at 10:26

Attachments:

GoogleCodeExporter commented 9 years ago
Just to follow up on this.
I thought that i may have had an issue due to installing the OE1.6 builds on an 
OE2.0image, but I can confirm that the same issue is present with the r1263 
OE2.0 build.

I had hoped it was just an incompatibility between the newer OE2 based images 
and the OE1.6 Valerie Builds but alas the issue persists on the newest build 
too.

I've attached the logs below, hopefully it will allow one of the Dev's to shed 
some light on my problem.
As barring an OE2.0 incompatibility I'm stumped

Original comment by bryan.od...@gmail.com on 27 Aug 2012 at 1:57

Attachments:

GoogleCodeExporter commented 9 years ago
Hi Bryan,

sorry for not beeing responsive on this one. Unfortunately due to the lack of 
an OE2.0 box / image I don't have the possibility to reproduce the problem here 
on my side. From the crash log it's pretty clear what's going on - but I don't 
have the slightest clue WHY this happens at all.

If noone else takes care of it I could offer to implement a work-around but 
from technical point of view a quick & dirty "hack" should be avoided if 
possible.

If you're interested I can send you an adapted file for testing purposes...

HTH & Cheers, Erik

Original comment by erik.for...@gmail.com on 27 Aug 2012 at 3:20

GoogleCodeExporter commented 9 years ago
Hi Erik,
        Thanks for the reply.
If I can help with implementing an OE2.0 fix in any way at all, please feel 
free to let me know.
I'm not much of a coder(Some experience in HTML and Ruby mainly in QA)but I do 
have an OE2.0 box and plenty of patience ;)
If anything at all I can do will help you and the other Dev's in getting OE2.0 
compatibility implemented then please...
Feel free to forward me the adapted file and I will provide any feedback I have 
and indeed if there is any particular circumstance/parameter you want tested on 
an OE2.0 image let me know and I will do my utmost to help.

Thanks and regards.
Bryan

Original comment by bryan.od...@gmail.com on 27 Aug 2012 at 5:24

GoogleCodeExporter commented 9 years ago
Hi Erik and PVMC team.
                      I'm just wondering if there is any update on this issue?
Will the r1264 rev work on an OE3.0 image?

Thanks and regards
Bryan

Original comment by bryan.od...@gmail.com on 19 Sep 2012 at 12:44

GoogleCodeExporter commented 9 years ago
Hi Bryan,

sorry - not yet... The changes introduced by r1264 should not have any impact 
on your problem... 

Since noone else seems to have a clue about this one I will send you an adapted 
file by mail so you can check how it behaves on your side - hopefully by the 
end of the upcoming week-end latest...

Thanks & cheers, Erik

Original comment by erik.for...@gmail.com on 20 Sep 2012 at 5:42

GoogleCodeExporter commented 9 years ago
Thanks for the udated info Erik :)
Rgds
Bryan

Original comment by bryan.od...@gmail.com on 20 Sep 2012 at 5:36

GoogleCodeExporter commented 9 years ago
Hi Erik & Team,

I also see enigma crashing on openpli 3.0. (rev1266_mips32el_oe20)
could you send me the adapted file you mentioned, so i can try it.
I attached the last part of the enigma crash log.

Regards,
Menno

Original comment by dream...@gmail.com on 23 Oct 2012 at 9:12

Attachments:

GoogleCodeExporter commented 9 years ago
Hi,

just like to mention that you can set the option "what to do at end of 
videofile playback" to "ask user" instead of the default setting "return to 
filelist"
These settings can be modified in Openpli 3.0 (setup->system 
settings->recording and filelist)
Thisway enigma does not crash at the end of playback.
Anyway i still like to see what happens when i use your adapted file :-)

thx,
Menno

Original comment by dream...@gmail.com on 24 Oct 2012 at 8:23

GoogleCodeExporter commented 9 years ago
Menno,
      Well done on deducing that this menu option eliminates the E2 crash.
I can confirm that this has eliminated this crash on my Vu+ Duo running 
VIX3.0.339.
And it allows the pop up menu to work too.
Hopefully Erik or one of the other team members will be along to share the 
adapted file with you.
Thanks and regards
Bryan

Original comment by bryan.od...@gmail.com on 24 Oct 2012 at 11:55

GoogleCodeExporter commented 9 years ago
Hi there folks,

I'm currently on vacation with limited internet-access. I will check back to 
this issue by the end of the upcoming week...

Cheers, Erik

Original comment by erik.for...@gmail.com on 28 Oct 2012 at 9:44

GoogleCodeExporter commented 9 years ago
Hi Erik,

any news on this?
Could you send me the adapted file to try?

thx,
Menno

Original comment by dream...@gmail.com on 2 Dec 2012 at 5:44

GoogleCodeExporter commented 9 years ago
Hi,

I've the same issue, see issue 636.

Any news on this?

thx

Original comment by jl.moss...@gmail.com on 18 Dec 2012 at 1:05

GoogleCodeExporter commented 9 years ago
There is a workaround by changing menu settings as described in comment 8 above.
I can confirm this method is working on VIX 3.0.514 and pvmc build r1269

Original comment by bryan.od...@gmail.com on 18 Dec 2012 at 1:15

GoogleCodeExporter commented 9 years ago
In fact it works must also set this option if you stop a movie. Any idea why it 
is necessary to put these options?
thank you
regards

Original comment by jl.moss...@gmail.com on 18 Dec 2012 at 8:05

GoogleCodeExporter commented 9 years ago
Hi,

sorry - I don't have OpenPli running on my box and thus can't comment / help on 
that... :-(

But good to hear, that the workaround is still valid and working! :-)

Concerning my adaption mentioned in earlier comments they did not work out 
since PVMC then crashed at a different / later position in code, so (at least 
for now!) no workaround from "our" side can be provided.

Cheers, Erik

Original comment by erik.for...@gmail.com on 19 Dec 2012 at 10:21

GoogleCodeExporter commented 9 years ago
I fixed this for my by adding two exception handlers in DMC_Player.py
line 178:
try:
                                        path = self.playlist[self.current][0]
                                        name = self.playlist[self.current][1]
except ......

and a few lines later:
try:
                                path = self.checkForAdditionalParts(path)
except ......

I dont have much knowlege about the code, and, I am not very familiar with 
python, but adding an exception does not hurt anyway.

Original comment by nobody.l...@googlemail.com on 26 Dec 2012 at 1:37