3.0.0-a6 (possible render ONLY issue)

[DeFlanko]

Ok here is a weird one.

I can reproduce this with all versions of UMS:

• 2.6.5
• 3.0.0 -a3
• 3.0.0 -a5
• 3.0.0 -a6

This is ONLY reproducible with the ASUS TF300T - an android tablet - with every file type i throw at it.
using this CONF File (i'm trying fine tune and configure):

Code: Select all

#----------------------------------------------------------------------------
# Profile for ASUS Transformer TF300T.
# See PS3.conf for a description of all possible configuration options.
# More Agent Searches could be used; Reference here for other models:
# http://en.wikipedia.org/wiki/
# but only tested with the SGH series

RendererName=Asus Transformer TF300T
RendererIcon=asus.png
UserAgentSearch=TF300T|TF300TG|TF300TL|AwoX
UserAgentAdditionalHeader=Dalvik
UserAgentAdditionalHeaderSearch=TF300T|TF300TG|TF300TL
Video=true
Audio=true
Image=true
SeekByTime=true
##the following toggled produced the same result##
TranscodeFastStart = true
TranscodedVideoFileSize = -1
CustomMencoderOptions = -lavdopts debug=0:threads=4 \
-lavcopts autoaspect=1:vcodec=mpeg4:acodec=mp2:abitrate=192:\
threads=8:keyint=0:vqscale=5:vqmin=2:vrc_maxrate=10000:vrc_buf_size=10000 \ 
-vf softskip,expand=::::1:16\/9:4,scale=640:360 \ 
-ofps 30000/1001 \
-lavdopts fast \ 
-channels 6
-af pan=2:1:0:0:1:1:0:0:1:1:1:1:1 \ 
-aid 0 \
-nosub \
-noautosub \
-mc 0.1 \
-o
#hold 

Steps to reproduce:

• Launch UMS
• Launch either Skifta or MyNet app on ASUS TF300T
• Navigate to a movie (note: thumbnails show portion of movie)
• Attempt to play movie endless loading on Device

Meanwhile on UMS

• 
• Peak bitrate goes mostly to 33,000 Mb/s then back to 0 with buffer at (-4,000)

Attempted to stream movies directly, same result, it picks a remux/transcode profile automaticly.

[DeFlanko]

@subjunk
I think these logs that magically showed up in the root of UMS might be related.
also had associated ~.mdmp files that were like 1 GB is size each...

Thoughts?

UPDATE: Nope, not related, but never the less they did show up in the UMS root folder.

[ExSport]

It is a minidump generated by JAVA I suppose. If UMS unexpectedly terminates or you will manually kill it, it will generate JAVA dump with error log. It depends on size of your heapsize how dump will be big, in my case about 2GB

[DeFlanko]

So then could be related... because even after trying to kill both UMS and the Android app cleanly. Once i relaunch UMS it trys to immediately re-stream to the Android Renderer without identifying the user-agent to assign it a CONF file or if the Android App is running or not.

Its very strange.