XPlay (WebOS)

Maybe you should undertad how HTML or better to say who actualy do media playback in HTML? Do you think that HTML page/app has own player? media codecs … media deoceders and etc? Or maybe media playback done by browser? In webOS case its done by some kind of launcher which uses AppleWebKIt/Chromium engine for handling HTML based apps.

About pin loop … Ive already told many times what probelm on system level leads to loop problems. Or you can read about it here https://twitter.com/lgxplay/status/1111023089662468097

The main problem that ppl will not read prevoius post and will continue blaming on me that the problem in the app. Ppl do not underatd the main thing … the app is jut GUI it does not do actual playback … it does not contoll local network and etc

@Metasyntactic
Could now comment now information from @Dad-Admin?
Still think that all problems in the app? And v1 will save the world? Still think that HTML page has own media player? Which is used for 4k video playback?

@bublikoff
I’ve followed your work since the application launch.
including I was one of the people who most publicized his work in the forums on LG TVs in Brazil.

I can not comment on something that I have no technical knowledge of.

my reports are about what has been happening to me in recent days, where it has made my experience very frustrating.

yesterday, after getting stuck on the Looping login screen, I was finally able to access Xplay in the online version 2,715,521, but I still can not open any videos in 4k. (because my tv is 4k, 90% of the content I have is in 4k.)

I have two LG TVs. a 2018/19 model with Webos 4.0 and the oldest model 2016 with Webos 3.0 and both Tvs have the same problem. if it was an isolated case of only one device I would understand, but in both? with different systems?

so I have two questions:

  • is there any other online version above that 2,715,521 that works best for me?

  • if you do not have a new version online, how do I keep only the store version 2.713.103, which works well for me.

thank you for your effort and fight with LG to try to solve these issues, and although it has a happy outcome for all.

a great compromise.

Mental Age: 10 years

the guy does not do anything of these users …
It explains that with the version 2.714.091 worked well, but no, it’s the fault of LG if it does not work anymore …

Pathetic…

@bublikoff you are obfuscating. I’ve already addressed these points. I’ve even acknowledged that there may be bugs on the LG side of things. However, even if that’s the case, it’s your updated version which triggers these far more often and which had a degraded experience over the original version.

You choose to release this version, despite the problems, and you are the one unwilling to roll back to the better working version.

You’ve taken money, but have released an update which makes things not work any more. That’s irresponsible.

Note: I’ve tried the information from dad-admin. It didn’t help. How would it? For example, I have the issue where it doesn’t even log in sometimes after selecting a user.

Note: all other apps work fine. I can even use the dnla player on the tv to play these 4k videos.

It is only xplay that doesn’t work.

Also, I’ve never claimed that html page has it’s own media player. I well understand on a technical level how this works. However, I can observe very easily all the issues with xplay that I did not have before with v1 and I don’t have with other apps.

The only constant problem I have had is with your updates, and you have not been willing to keep a v1 version in the app store.

Why not just release an xplay-legacy app? Have both apps in the store. Did you lose the code for the original app?

If you did your, people who are fine with v1 and don’t have issues with it will be ok. People who are fine with v2 can stay with that.

Such an approach would be customer friendly and would get us out of this pointless back and forth.

Heck, I’ll happily publish the app if you want to send me the old version.

Please update my account to online beta.

User ID: 13956191-NL

Let me ask as plainly as possible:

  1. do you still have the original source code or application binary?
  2. are you willing to put this back in the LG store as an app like “xplay-legacy”?

If you have the original code, i don’t see why you’d be against actually just providing people with the choice of using the original (which works for so many of these use cases), or using teh new one. People who are happy with the new one can use it. Those that are unhappy because of all the issues can use the original version. That way you have the best of both worlds.

You’ll have collected the money in either event, so it’s not like you’re losing out here at all. This would just be to help the people who are now in the position of having a non-functioning app (like myself).

The only reason i can think you wouldn’t do this would be if you’ve actually lost the original program due to not properly keeping track of your programming assets.

Note: I’m even willing to do this work for you. If you provide me with hte source/app-binary, i’ll submit it to the store and will work with LG qa on things. I have a lot of experience with web/desktop/mobile/app development as well as working with curated stores. So i’m very familiar with all that goes on here. If you don’t want to take the time to do this yourself, i’m willing to invest my own time and effort to reach a position that helps out all your audience.

3 Likes

I suppose that your mental age even lower … maybe 8? If you think that if app starts having problems it always must be the probelm in app. While app works it ocuopy TV, localt network, the Internet and etc … and if you think that app can control all aspects … you are totaly wrong. LG makes updates for webOS … it means that they are changing something in webOS functionality. The app does not control for eg the situation that there is something with wifi or problems with the internet connection. I can not control LG’s backdors, LG defently can control app’s access to the API. We can clearly see it … LG just striped subtitles functionality for the app or for my dev account. And I suppoe that it even will not work for other 3rd party apps.
Its most easiest and simple way is to say that if something wrong with the app it’s probelms with app. But before saying this you should understand how it works and who actualty do playback.
You simply do not want to accept a situation in which things that are simple at first sight are much more complicated than they seem. And the situation where @Metasyntactic is trying to tell me that a HTML page is responsibe for problems with video playback is a bit odd. And when @Metasyntactic is teling me that he has more than 20 years exp in IT industry is also strange … And as for me when he telling it must decreat his exp stage … for minues 5 years propobly. As spend those 5 years for studding. HTML app uses html tags video/audio for media playback. The app just catch events from those HTML media player and call such functions like play, stop, and etc. It has no control of media buffering or somthing else … Yes HTML api can wait more time until VIDEO tag will buffer more media data but it will not actualy help you if app will wait for 10-20-30 minutes to buffer it before it will start media playback. Or in case of local network problems. For eg current situation with media playback when the app even can not start video player … the app waits for event from VIDEO tag that it ghas loaded media data … then it wait for event that enougth media data loaded for playback and the app call play function after it got those events but VIDEO tag just does not fire them and app just think that it must wait a bit more and more. Of coure I can add own playback start timeout but it will not fix the maoin problem with video playback. I can even add more VIDEO tag must throw error event that it has problem with media playback but it does not throw any error event … I don’t have magic wand to fix such problem on app’s side. The problem is on web browser side … in webOS case it’s some kind of webOS launcher which uses AppleWebKit/Chromium web engine to host HTML apps. Its simular to webView in android … I can create app for android using HTML and JS and it will use webView for hosting it.

giphy-facebook_s
You still dont want toi underatnd the major thing. There is much chages in player starting the app creates html VIDEO tag and set its source url to correct url which is pointing it to media file on PMS side. And the app waits for events media meta data loded and enought media data loaded … and after those events it removes curtains and call play function.
The same algorism is in v1 and the same is in v2 …
V1 is not a magic staff … it will not heal playback issue …

Me, what I see is that with version 2.714.091, I had no problem: the 4K files were read perfectly and the function “resume” worked pretty much.
With version 2.715.521, almost nothing works.

And just for info, it’s me who controls the updates of WebOS on my TV! I disabled automatic updates.
I am on the version WebOS 2 (04.25.85 of December 2018). Last update to date for the model of my TV.
I installed this update in January 2019.

So in this case, how do you explain the fact that version 2.714.091 worked very well ??? while version 2.715.521 is almost unusable ??? While there has been no update of WebOS ??? Go ahead I listen to you Einstein!

My os is not set to update. All that updated was xplay. Prior to the update things worked fine. After the update, they did not.

1 Like

Let me ask as plainly as possible:

do you still have the original source code or application binary?
are you willing to put this back in the LG store as an app like “xplay-legacy”?

If you have the original code, i don’t see why you’d be against actually just providing people with the choice of using the original (which works for so many of these use cases), or using teh new one. People who are happy with the new one can use it. Those that are unhappy because of all the issues can use the original version. That way you have the best of both worlds.

You’ll have collected the money in either event, so it’s not like you’re losing out here at all. This would just be to help the people who are now in the position of having a non-functioning app (like myself).

The only reason i can think you wouldn’t do this would be if you’ve actually lost the original program due to not properly keeping track of your programming assets.

Note: I’m even willing to do this work for you. If you provide me with hte source/app-binary, i’ll submit it to the store and will work with LG qa on things. I have a lot of experience with web/desktop/mobile/app development as well as working with curated stores. So i’m very familiar with all that goes on here. If you don’t want to take the time to do this yourself, i’m willing to invest my own time and effort to reach a position that helps out all your audience

1 Like

. And the situation where @Metasyntactic is trying to tell me that a HTML page is responsibe for problems with video playback is a bit

I have literally never said that. I have even said the issues may have been on LG’s side of things. However, your release triggers the issues far more often now. Hence why I would like you to make xplay-v1 available.

You can release this as a different app for all I care. Call it xplay-legacy. I’d just like to be able to go back to when things worked. I don’t understand why you are so resistant to that.

Then only thing I can think of is that you have actually lost the original app.

1 Like

… I don’t have magic wand to fix such problem on app’s side. The problem is on web browser side …

Yes you do. You could at least stop make the old app available for those who would like to use it. That way I can roll back the one thing that changed on my TV.

Again, it’s only your app that has a problem. Everything else still works. The tv os was not updated. The network is fine (I can play the 4k movies through the dlna player).

I don’t know why you won’t even try this out. Worse case, it doesn’t work and nothing has changed. Great case, paying customers like myself have a working profuct again.

Grow up and act like a professional. In my 20+ years in this industry I’ve never seen someone act like this. It’s immature and irresponsible.

2 Likes

Just give us back the old app. Even if it’s only to convince us that it’s not your fault.
It’s weird that a 4k movie that buffers every 30-60 seconds on new xplay only buffers 1 or 2 times during 2 hours on webOS player. And never buffered on old xplay. Strange that on webOS player I can whatch the same movie i cant in xplay because it’s always buffering…

1 Like

Agreed. What do you have to lose Bublikoff? If you’re correct, and it has nothing to do withthe app update, then we’ll just be in the same position as before. But, if you’re wrong, then we at least get a working app again.

I really hope you didn’t lose the original app. Given your refusal to not even address the question of if you have it; it makes me think you didn’t properly archive your work, and you then made a bunch of changes you don’t know how to roll back. I think a lot of your posts are simply trying to obfuscate things, by discussing html players over and over again, rather than discussing the core issue of your releases and your update strategy.

We’ll see if you continue to behave in this fashion, or if you’re willing to actually man up and attempt to do right by your paying customers.

3 Likes

@bublikoff To get away from this whole issue with LG…is there a reason you can’t just carry on working with just the online version to get rid of the bugs. I know you said there was some kind of issue when you pushed everybody to the online version (maybe you can go back to try and work out what this was), but I can honestly say mine has ran fine. Anybody had any issues with the online version that are not just bugs??? Can we formulate a list of known bugs somewhere (app bugs, not LG ones)?

If we are using the online version there does need to be some mechanism to change update channel though down the line… aka Stable/Beta (maybe even V1 UI option). I understand this could mean having a new version submitted to LG, but if you are clearly getting stuck every single time for an update there is no future for the app. Best to work on something that gives yourself back control.

v1 works a treat on my bedroom tv i havent updated :thinking:

Have you read carefully all information?
Playback issue also appear not for all users. For eg Ive no problems with v2 on my TV and I made a video for QA from my TV that I can play the same video content from event video from QA.
PIN loop or Sign in loop also appears not for all.
Magic? Street magic? :thinking: same source code but happens not for all … hmm … maybe because it is not so simple as you would think?