Page 1 of 4
Another Java Exception 2.2.0
Posted: Fri Dec 14, 2012 9:23 am
by orgon3
This has been present since 2.1.0, and in all versions since. My roommate who streams to his Sharp Quattron TV, has been unable to since. The problem has always been the same. I am using the latest version of Java, 7u9. I'm on Windows 7 64-bit. I'm using the usual settings.
Code: Select all
12-13 16:17:19 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: DLNADOC/1.50 SHARP-AQUOS-DMP/1.1W
12-13 16:17:19 Starting transcode/remux of A.Movie.That.Is.Definitely.Legal.720p.mkv
12-13 16:17:25 Exception in thread "StartPlaying Event" java.lang.NullPointerException
12-13 16:17:25 at net.pms.dlna.DLNAResource$1.run(DLNAResource.java:1543)
12-13 16:17:25 at java.lang.Thread.run(Unknown Source)
12-13 16:20:10 Exception in thread "StopPlaying Event" java.lang.NullPointerException
12-13 16:20:10 at net.pms.dlna.DLNAResource$2$1.run(DLNAResource.java:1605)
12-13 16:20:10 at java.lang.Thread.run(Unknown Source)
The first line is obviously just his TV, and his normal. The second line is normal. Then the exceptions are thrown. He is unable to watch anything. I am reverting back to 2.0.0 for now. I love the new virtual A-Z folders though, so if you need me to help troubleshoot this at all, just let me know.
(Removed link)
Re: Another Java Exception 2.2.0
Posted: Wed Dec 19, 2012 5:03 am
by bevster
I see the same exceptions, and occasionally the sound will stop streaming while still seeing video. Its not every time, last night I watched a movie and no exceptions appeared and no glitches either. win7 64, latest java
Re: Another Java Exception 2.2.0
Posted: Wed Jan 16, 2013 8:05 pm
by orgon3
I am still seeing this happen all the way through 2.2.4. I had to revert all the way back to 2.1.2 to fix the problem. Now even my roommate can watch on his Sharp Aquos again (in 2.1.2). I have been on Java 7u10.
Re: Another Java Exception 2.2.0
Posted: Sat Jan 19, 2013 3:06 pm
by bevster
Version 2.2.5 has still not fixed this issue for me, here is a new debug pack to look at
error message seems to be different now, but still same random stopping of movie playing
Thank you
Re: Another Java Exception 2.2.0
Posted: Sat Jan 19, 2013 6:46 pm
by orgon3
bevster wrote:Version 2.2.5 has still not fixed this issue for me, here is a new debug pack to look at
error message seems to be different now, but still same random stopping of movie playing
Thank you
I guess that answers my question on whether or not to try 2.2.5. Thanks for the heads up, bevster. However, I think our problems are different. Yours was just saving you from watching a terrible show
Re: Another Java Exception 2.2.0
Posted: Wed Jan 23, 2013 11:14 am
by SubJunk
@orgon3: Your bug will be fixed in the next version after 2.2.6.
@bevster: Your bug is different but is something that you can fix
The problem happens with many "WEB-DL" files because of the way they are encoded. You can get around it by using FFmpeg or MEncoder, since the bug only affects tsMuxeR. This bug will be somewhat fixed in the next version after 2.2.6
Re: Another Java Exception 2.2.0
Posted: Wed Jan 23, 2013 4:11 pm
by SubJunk
Also, orgon3, what model TV does your roommate use? If I can get that I might be able to add it to UMS for better file support
Re: Another Java Exception 2.2.0
Posted: Wed Jan 23, 2013 7:27 pm
by bevster
Sounds good, thanks Subjunk!
Re: Another Java Exception 2.2.0
Posted: Fri Jan 25, 2013 11:48 am
by orgon3
SubJunk,
Thank you so much man. Everything you do here is very much appreciated, more than you can know. My roommate's TV is a Sharp Aquos LC-46LE830U. It has built-in WiFi and he uses the DLNA app on the TV. The only thing that works right now is TSMuxer, or if the file is already supported for the TV he can just play it. Otherwise, he has to select TSMuxer.
Thanks again SubJunk!!!! Please let me know if I can help anymore with adding this to the list.
Re: Another Java Exception 2.2.0
Posted: Mon Jan 28, 2013 12:48 pm
by orgon3
I'm going to check out 2.3.0 and report back. I knew the next version wasn't going to be 2.2.7. I figured since you were saying it will be fixed in the next version, and not in 2.2.7
