maybe because it is not so simple as you would think?
There’s an easy way to tell. Just make xplay-legacy available for people. Worst case, it doesn’t work. Best case, it does. Why are you resistant to making htat option available? We’re paying customers. We had a working product. That product doesn’t work, and it would be behoove you to at least try this out to see if it would help.
I’m not going to discuss v1 anymore … Im tired to speak about v1 … how wonderful it was and if you get it back we all get back to a wonderful world with pink unicorns. Just stop taking LSD …
It’s useless discussion we both still have own opinions. And no step back …
How do you know? It’s the only thing that changed for me, and now things don’t work. So it’s totally possible that it may fix things.
It would be easy to find out. Just make it available and we can tell. If it doesn’t work, then no skin off anyone’s nose. If it does work, you’ve addressed the fact that your software update ended up with a lot of customers with a non-functioning product.
And v1 will not pass QA becouse of the same problems as v2 has
etc…
Why would that be the case. It passed before. Since it’s the same binary, it should pass again.
It’s useless discussion we both still have own opinions. And no step back …
Please refund my money then. You delivered an update which no longer works. And you are steadfast in your refusal to do anything about it. You won’t even try to see if v1 will help. You just childishly stamp your feet, insist it won’t, and won’t even bother working to make things better for your customers in this situation.
Dont even to try to tell me that you have exp in IT industry …
Oh… how sad for you. I’m really sorry that you’re tired about discussing options that might help but which you’re not even willing to even try.
Given your refusal to ever answer this simple question, it’s pretty clear ot me what happened. You didn’t properly keep track of your source code and your binary releases. And you lost the previous version. You messed up and released a new problem, and you have no ability to roll things back. You’re only willing to blame LG.
What’s crazy here is that i get updates on other apps all the time, and i play video with them fine all the time. It’s only your app that has this problem, and only since it was updated. Your complete refusal to even state that you still have your source code makes it pretty obvious what happened. You dropped the ball, and now you have no idea what to do about it. So, even though it’s been months since this has happened, many users are just SOL.
Im not sad … you you dont want to hear real situation and tech aspects …
At the moment I see in you a purely provocateur who does not hear the arguments and just trying to tell me that v1 will save the world.
Have a nice day …
I’ve heard your explanation. I’ve also heard your complete unwillingness to entertain the idea of rolling back a release after shipping a problematic update.
At the moment I see in you a purely provocateur who does not hear the arguments and just trying to tell me that v1 will save the world.
No, as i said numerous times, it’s an approach that can’t hurt. In hte worst case, you’re correct and V1 doesn’t help customers like me. But in the best case, you’re wrong and maybe it does help. But you’re not even willing to try.
The best you can do is put up strawmen and not actually respond to the argument being made.
That’s the problem here you keep stating that hte argument is: v1 will fix things.
IT’S NOT.
The argument is: it doesn’t hurt to try to see if V1 will fix things for people.
But you still are steadfast in refusing to even entertain trying that. Despite having taken people’s money and despite releasing an update that now has left people in a non-functional situation.
You have refused to even consider this, and you have stated the same strawman over a dozen times now. Your willingness to just lie about the position people are putting forth is just amazing. At first i thought you jut made a mistake, but you would try to do the right thing. Now i see that not only did you make a mistake, but you’re not even willing to try to fix it using all the means at your disposal. Instead, you just took the money and said “too bad” to people now in this position.
Anyways, i’m done. I was a big fan of this piece of software. I even recommended it to several friends who got LG tvs as well. I gave you 6 months to try to step up and address this scenario. And for six months you’ve given the same run around.
I’m a professional software dev, and I’m pretty amazed by all of this. With these sorts of issues, we would have rolled back within days (ideally same day). I gave you leeway as someone not very experienced with this. But at this point, it’s clear you just don’t have the first clue on responsible software development.
Same !
Shame on you @bublikoff
You’re not a developer, you’re a thief !
The latest update has put “please support me on twitter” in big bright red unsightly letters on the splash page for the xplay app.
Can this be removed? It makes something I paid money for look like freeware.
Indeed @bublikoff Remove the Twitter ads, solve our problem. Do not bug us with the problems.
Solve them., then you will get great appreciotion not by spamming us within a paid product!
Its peatty sad that developer does not understand what is actualy going on and can no even explain his own position using using tech knowledge. You are not good developer then. At least Ive tried to eplain the porblem but from you and some use users I can only hear that v1 will save the world and will return pink unicorns to our street … and unicorns will make a rainbow made of skittles.
Will you explain? Lets take two major problems of version from apps store.
Its “loop problem” … this problem meay lead for several issues is app. For eg “PIN loop” or “Signin code loop”. Cuerrent version from the apps store uses HTML/JavaScript API for storing some data on TV … for eg it uses sessionStorage to store session (temp) data while it navigates between screens. But in some cases when app calls function to write data to sessionStorage it just ignores it and does not save it. The app is trying to navigate to next screen and after navigaton is done app tries to load data from sessionStorage and check if evrithing is correct and all nesessary data is avalible. But as sessionStorage did not save data app have to return back and ask ppl for PIN code or ask to resign.
Hmm… How should I fix this problem on my side? I can not fix such starnge API behaviour as its probably is in web engine which is hosting the html app/page (AppleWebKit/Chromium).
But how we can try to bypass this issue and even more is it possible to bypass it … Propobly yes … but I can not garanty that fix will work 100%. I had to rewrite the app not to use sessionStorage at all. I even made some changes to reduce wirtes to localStorage whcih is used to store permanent app data (settings or plex account information). Now it debounces all writes to localStorage.
How can we explain this problem? Hm… interested question. But lets try to do that. First of all Im not a web browser’s develper and I’m a specialist in all IT spheres … only @Metasyntactic can be super duper developer who can not even provide valuable information and exlain the problem. As for me I can only guess. The web engine (AppleWebKit/Chromium) which is used by webOS to host HTML based apps uses SQLite db files for sessionStorage and localStorage. And there is propobly a issue with multithreading. And when app tries to make several writes at the same time it may lead to db file corruption. But HOLD ON … you can say that javascript is a single threading scripting language. Yes BUT it has “Web Workers”, timeouts and intervals … it allows to run some part of source code in a separate thread. And it’s probably more valid for “Web Workers” than timeouts and intervals. So … I guess that writing to sessionStorage and localStorage is not thread safe functionality especialy becouse TV has not so powerfull CPU or permanent storage is not so fast to handle writes fast enought to do not catch internal colision.
Lets speak about another problem … its “playback problem” … It also has several variants issues. In one it may lead to the situation when you video content is continiusly buffering it. And the second varian of playback issue is when the app even do not start playback at all.
First of all we need to understand that HTML app has no own media content players. It uses players which web engine proviedes to it. It means that suuport of media container types or media codec depends from web engine (AppleWebKit/Chromium) and webOS as webOS hosts web engine. Compatibility depends from webOS version … from TV platform. TV models are sharing its tv platform with several TV models.
So what about continius buffering issue … As we read from @Dad-Admin post it may be the problem how TV works with WiFI or wire connection. The app can not control such aspect of using the app. The is also possibe probelm with VIDEO tag (HTML video player) which is used by the app for video playback.
What about the situation when the app can not even start vide playback its defently somehow connected with HTML VIDEO tag. Ive already shaerd video with my tests how I was able to catch this playback issue. Anyway as @Metasyntactic is a developer I suppose that he can provide some valuable ideas what is wrong with my app. He is some part of soure code where vide player starts and initialize the video player GUI.
At this moment we already see curtains with media art. It also shows red loading spinner.
Here wa attach event lisnteners to know what is going on with vide playback
vm.$refs.player.addEventListener(‘error’, vm.playerOnError);
vm.$refs.player.addEventListener(‘invalid’, vm.playerOnError);
vm.$refs.player.addEventListener(‘canplay’, vm.playerOnCanPlay);
vm.$refs.player.addEventListener(‘timeupdate’, vm.playerOnTimeUpdate);
vm.$refs.player.addEventListener(‘play’, vm.playerOnPlay);
vm.$refs.player.addEventListener(‘pause’, vm.playerOnPaused);
vm.$refs.player.addEventListener(‘ended’, vm.playerOnEnded);
vm.$refs.player.addEventListener(‘seeking’, vm.playerOnWaiting);
vm.$refs.player.addEventListener(‘waiting’, vm.playerOnWaiting);
Here is one more event listener which waits for event from VIDEO tag which will indicate that VIDEO tag has loaded meta data. And after app got it it changes spinner color from red to orange
vm.$refs.player.addEventListener(‘loadedmetadata’, function (event)
{
var el = document.getElementById(‘player-loading’);
if(el) el.classList.remove(‘red’);
});
After we have attached event listeners the app tells to VIDEO tag which url to play.
vm.$refs.source.setAttribute(‘type’, vm.video.source.type + (vm.video.source.transcode === false && vm.video.source.options ? ‘;mediaOption=’ + escape(JSON.stringify(vm.video.source.options)) : ‘’));
vm.$refs.source.setAttribute(‘src’, vm.video.source.source);
vm.$refs.player.setAttribute(‘preload’, ‘auto’);
vm.$refs.player.appendChild(vm.$refs.source);
And after all done it wait 250 milliseconds and tells to VIDEO tag to load media file … actualy this is the start point after VIDEO tag do start media load
setTimeout(function() { vm.$refs.player.load(); }, 250);
And after the VIDEO tag loaded enought media data it throws event “canplay”
And after the app got this event it calls “play()” function.
So where here you can see the problem? v1 has the same logic of video playback start. The only difference between v1 and v2 how video playback starting is that v2 shows RED loading spinner and changes it to orange. The logic of video playback starting on HTML app/page actualy will not have major difference. It may have more or less event listeners or “play()” can be called automaticly by VIDEO tag itself after it got evrithing for playback … and that is all.
So … in our situation VIDEO tag does not even throw events “loadedmetadata”, “canplay” and does not therow error event “error” … hm. How HTML app/page should this issue? Could you explain? I can even add more … that sometimes after app calls “play()” function it returns “endless” JS promise … and this promise will not be resolved and as its not resolved VIDEO tag does not start playback.
You are trying to speak that v1 is a magic pill which will save the world but does not explain how … and why … as v1 and v2 will share the same VIDEO tag or better to say the same web engine (AppleWebKit/Chromium) it will not make any difference. As major issue is somewhere inside web engine or webOS as hosing OS. Ive no idea and only can guess but I can insist on that the problem can not fixed on app’s side and the app can not bypass such problems. The app only “asks” VIDEO tag to play url which is pointing to media file on PMS side. And what will VIDEO tag do I can only guess especialy becouse it does not throw any events to notify app about situation.
And trying to compared official app with the app is a bit incorrect. Official client will always use transcoder for better media content compatibility. It means that transcoder will transcode for eg 100-200 mb of media content and will wait untill VIDEO tags ask for another portion media content. What about XPlay … by default it uses direct media files url … it means that if media file has 2 Gb body TV will try to download it fully (to temp folder or to RAM Ive no idea) … or for eg if we speak about hight birated 4k content it will try to download for eg 30Gb to TV for playback. And propobly there is some memory leaking issue or anything else.
PS
Im not a webOS developer and Ive not deleoping web browser but at least I do understand how some parts are works. And at least I do try to explain the problems from tech side. But here only magic words like v1 will save us … it will save the world … you are thif and etc
At least to try to fight with LG Corp to solve the situation and what about you @Metasyntactic … what did you do to resolve the situaitin? I can only see useless posts here and valuable information … No help in twitter and etc … Im a developer … Ive 24 exp in IT sphere and etc … only bla bla bla …
The situation is quite simple LG is reducing doumented API which was avalible for developers … and trying to punish developers for continuing to using it … It does not accept the situation where issue is not on app’s side and this issue in webOS … in web engine which is actualy hosting HTML apps and do media playback. Of course it’s easier to say that app must fix issue. And they will not have to spend some extra mony to fix the probem. Its not a big problem for LG to have -1 app in apps store. LG just does not respect its customers and this is the main problem.
I can not even publish updates becouse LG is creating artifical borders to prevent app from updating. They are even trying to fool me with file version … its rediculas as I know what I do … and I store all files which I uploads in LG seller’s cabinet.
@Metasyntactic I’ll accept and admint your exp if you explain how HTML app/page can have more control over VIDEO tag … and how I can influance to buffering … and etc … but for the moment only bla bla bla
Just unfloow from twitter you did not force you to fllow me. I just asked to help me in small war with LG
what did you do to resolve the situaitin?
I offered to take your previous app (which you clearly lost) and to submit it and get it through the LG app process to get it back in the store so people could see if it solves their problem.
I offered to help in this manner, and you rejected it as well because you’re irresponsible, won’t accept assistance, and cannot own up to the idea that you should try all avenues available to you to try to improve the situation
So much blah blah for nothing …
You try to confuse us with your TAG VIDEO!
FYI, I still have not got an answer to my question:
It pains you to admit that even without doing WebOS updates, your application is deceiving ???
As a user, we do not care where the problem comes from! we want an application that works!
Version 2.714.091 works while version 2.715.521 not with the same version of WebOS !!! SAME VERSION OF WEBOS !!!
Again return v1 and that all … and no tech aspects … no explanation … just return me v1 …
I can only hear that v1 will save the world and will return pink unicorns to our street … and unicorns will make a rainbow made of skittles.
You lie.
I said multiple times:
that’s the problem here you keep stating that hte argument is: v1 will fix things.
IT’S NOT.
The argument is: it doesn’t hurt to try to see if V1 will fix things for people
You can’t even help but lie over and over again. Your deceptive nature is utterly transparent. Even when I’ve stated my case simply, you respond and you lie about it yet another time.
Again, I’m past giving you the benefit of the doubt. You’ve acted abhorrently, and when people have offered to help or explain their position you just lie about it.
Shame on you.
Again return v1 and that all … and no tech aspects … no explanation … just return me v1 …
Yes. Ffs. As stated before there are no downsides to that. Let’s say you’re correct. You return v1 and it doesn’t help. Well, we’re in the same place as we are now. It didn’t get any worse.
But say your return v1 and it does make things better. Then your customers who currently are screwed will be happy.
Your not even willing to try, even though for several of us nothing changed but the update, and now things are not working.
Again, no one is claiming with certainty that it will fix the problem. What people are asking for is that we at least try this it to see.
But as you seem to have lost the source code (since you won’t even confirm you have it, and won’t even try to work with people offering to submit it on your behalf), we can’t even do that. So we’re stuck having paid money for something that doesn’t work, while all the other apps on the system are fine
Are you idoit? Do the difference between those versions? how webOS hadles localy stored resources and online? Before this its was fairy tale about v1 … and about its magical properties. Now new … that 2.714.091 works … did you changed your maind after my tech explanation? Just to fit your new story? For eg I do also use online version 2.715.521 on my TV and Ive no probelms… and what? If you dont like just tell me I will return you to apps version … and you will be happy … oh no you will start telling me that v1 was better than 2.714.091 … endless circus.
2.714.091 and 2.715.521 are sharing main aspects how players starts … the only difference is how transcoded URL is formed … and some othe UI changes …
You are welcome
