2013-07-06, 10:54 PM
UncleJohnsBand Wrote:The network buffer is the one that would have the impact on view.....I just did all of mine to be consistent.
I also see you are using the mobile version of VLC. I don't have access to the VLC mobile....when I try to access it on the goggle store I get a message it isn't available for my country. I have a nightly build from June running on my tablet and it really sucks compared to what I am used to with the standard pc client. So you may be experiencing issue with the mobile version of VLC coupled with any limitations of video decoding on the mobile device.....i.e. you may be forced to use software decoding vs. hardware depending on your mobile device. I use MX Player on my tablet and after the stream is started I can open the network address in it and see a much better result on the video compared to VLC mobile (at least the version I have access too).
I think there's a confusion between portable and mobile. I don't have a mobile version of vlc, nor a tablet.
The portable version is a version made with (for example) thinapp. You don't have to install that version (but it runs on windows).
I worked with a portable version on my office, but on my client (laptop) and server (desktop) I have 2.0.7 from the videolan website:
http://get.videolan.org/vlc/2.0.7/win32/...-win32.exe
I will take my laptop to work on monday and test the buffer. I assume that I can tell the buffering is really taking place by having to wait for ..s before the video starts playing? I haven't noticed that with the portable version at work so maybe that didn't go right.
Server: Core2Duo 3,16GHz| Windows 7 Ultimate 64 bit | NPVR 3.2.9 | Analogue: Hauppauge PVR-150 | Digital dvb-c: Technisat CableStar HD 2 | No plugins
Clients: Laptop Windows 7 Home 64 bit via Wifi | Android tablet via Wifi | Androidbox s89-H via Lan
Clients: Laptop Windows 7 Home 64 bit via Wifi | Android tablet via Wifi | Androidbox s89-H via Lan