Closed GoogleCodeExporter closed 9 years ago
Nope, as I do not own an xbox anymore I need logfiles. Both uzgplugin.log and a
debug xbmc.log.
Does the XBMC under Windows have the same issue?
Original comment by basrie...@gmail.com
on 20 Mar 2012 at 7:01
No, it works in Windows.
I attach log files when I run it as a script and as a plugin. Same with the
xbmc.log.
I get very weird behavior. Sometimes it start for 2-5 secs and stops and then I
can't get it to start anymore. Sometimes it will not start the first time I try
(after a reboot).
When I run it as a plugin I get audio, but no video. All problems is gone if I
disable advanced plugin mode and it's only TV4Play that has problems when
running it as a script. When I try to run it as a plugin I got issues with
SVTPlay too. Maybe it's the memory again that is low (I always do a reboot
after each try)? I hate this low memory problem :(
See if you can find anything in the log files.
Original comment by jagflash...@gmail.com
on 20 Mar 2012 at 7:59
Attachments:
Well, as far as I can see, it does seem to be related to memory. XOT-Uzg.v3
determines the stream to play correctly.
What skin are you using? You only have 27 MB memory free before you start the
script/plugin. That is not much. I usually got around 35 MB.
Did you try a more recent XBMC4Xbox build? I know they are doing a lot of work
on the video playback. Perhaps your issue is fixed in a more recent nightly?
Original comment by basrie...@gmail.com
on 20 Mar 2012 at 10:23
I updated to the latest build, same problem.
It seems to be a low memory problem. When using PM3.HD or PMIII it works, but
both skins are ugly in high res and text dialogs are too big. Text gets out of
the windows etc.
Now we at least know why there are some issues, but it has worked nice before
even TV4Play so that was the reason I reported it. I didn't tested it with the
advanced plugin mode enabled and when it's enabled it takes more memory, too
much memory :(
Original comment by jagflash...@gmail.com
on 20 Mar 2012 at 6:26
Ok, well, it's not using too much memory, it just does more steps in one go,
and thus uses more memory. I can't really control that.
Original comment by basrie...@gmail.com
on 20 Mar 2012 at 6:32
comment these 2 lines in the main default.py:
import remotedebugger
debugger = remotedebugger.RemoteDebugger()
it will gain you 1.5 MB
Original comment by basrie...@gmail.com
on 20 Mar 2012 at 8:42
Great, thanks! I'll see if that is enough. Maybe it's my lucky day :)
Original comment by jagflash...@gmail.com
on 20 Mar 2012 at 9:22
Original issue reported on code.google.com by
jagflash...@gmail.com
on 20 Mar 2012 at 6:05