Chrome OS Beta for Rise Player

Comments

28 comments

  • Avatar
    Darius Aleksas

    In the meantime where do I get the old RV player for Chrome? I needed to reset one of my Chromeboxes and now I want to put RV player on it again.

  • Avatar
    Darius Aleksas

    Do not worry, I got it.

  • Avatar
    Dave Soper

    Will there be an "over the wire" upgrade path for all of the players ( I have 8) still running the old RV player for chrome?

  • Avatar
    Alan Clayton

    Hi Dave, our plan as of now is to release the new Rise Player for Chrome OS as an update to the legacy version.  Thanks!

  • Avatar
    Andrew Brigham

    So the community chromium Rise Player was stable for over a year and just stopped working last week.  Whats up? 

  • Avatar
    Darius Aleksas

    No, it did not. All is good with Chromeboxes here.

  • Avatar
    Andrew Brigham

    Weird perhaps I have a network issue.  We have had nothing but a good experience with the app on chromeboxes in kiosk mode.  Since last week they seem to reboot and forget their screen ID.

     

     

  • Avatar
    Denise Hastings

    I am having issues with mine as well.  All our boxes, backgrounds load, but no ad boxes load. 

     

  • Avatar
    Robb Price

    Andrew, Denise,

    Sorry for the delay in getting back to you. I'm not aware of anything that changed around that time. Are you still having those issues? Maybe a change in the ChromeOS caused this?

  • Avatar
    Wendi Borden

    We've not seen any issue on our managed boxes. Looking forward to official ChromeOS support again!

  • Avatar
    Abedin Bhollah

    The  Rise Vision Chrome APPS is displaying a black screen , no contents are being displayed !!!!!

  • Avatar
    Robb Price

    Abedin,

    I'm not sure what you mean. Do you mean to say that the Chrome App Player you have is not showing any content? 

    As mentioned above, this is an unsupported Player, but the first thing I would confirm is that data is set to Display on the device. Typically it will turn to a black screen if there is no content selected to Display.

    Let us know if that helps!

  • Avatar
    Andrew Kletke

    Scott,

    Any idea when this will be completed and a supported platform again? I'm seeing more and more widgets that we currently run on our chromeboxes google calendar, google sheets, etc become "Licensed" features. Currently those features do still work but without the ability to transition our displays to be licensed I'm worried might make our signage unusable in the near future. Unless you guys are thinking ahead about this exact issue. I'm not about to swap out my chromeboxes for a windows or linux device. I'll move to another platform that already supports Chrome out of the box before I make that investment.

    Please let us know the road-map and timelines.

  • Avatar
    Alan Clayton

    Hi Andrew, good question! We have taken this into consideration and there will be no impact on existing Chrome OS Displays until we have released the new Chrome OS Player which is currently scheduled for late July/early August. 

    Thanks! 

  • Avatar
    Riel

    So ... I had some players working with a custom fork that I did a few years ago

    Until very recently they all worked fine ...
    Now ... they don't work anymore and my demo chromeboxes that worked like battleships for years, have forgotten their ID.

    What gives guys?

  • Avatar
    Colby Maughan

    Hello Riel,

    This looks to be an issue with the current iteration of the ChromeOS player that affects a very small amount of its users. Currently, ChromeOS is unsupported due to issues we were having with the updates Google was pushing out. When our new ChromeOS player is released, this bug should be resolved.. 

    If your ChromeOS displays lose their ID again, I would recommend re-installing the player. This has resolved the issue in the past for most of the users that have experienced it. 

    If you'd like to assist with testing of the ChromeOS Beta, we've got a sign-up link in the post above. If you sign up, when the beta is released you will be notified. We would appreciate any feedback on the beta you may be able to offer!

  • Avatar
    Riel

    Hey Colby

    these were custom one's that I'd built from your opensource code

    worked fine till about a month ago

    now the video from youtube won't load for me at all

    https://chrome.google.com/webstore/detail/reach-network-player/aepggpifmcbdofojkggeajbobpeamllb

    any thoughts on why ?

     

  • Avatar
    Colby Maughan

    Hello Riel,

    I ran this by a few others in support and one of our devs suggested it may be similar to one of our known issues with ChromeOS. This is something we're working on correcting in our upcoming ChromeOS Player Release.

    https://help.risevision.com/hc/en-us/community/posts/360009354103-Videos-not-autoplaying-in-Preview-and-on-Unmanaged-Chrome-OS-devices

    That being said, I do need to make it clear that we're not able to officially support third party players, even if they are built from a fork of our open source code. We're not sure what modifications have been made to the open source code, so it's difficult for us to say what might be wrong.

    You can find more info on the change Google made here,

    https://developers.google.com/web/updates/2017/09/autoplay-policy-changes

    If it's based on our open source code, it's entirely possible that it may experience the same issues that our ChromeOS players have had in the past few months. I think this would be a good starting point, as you mentioned the issue began occurring about a month ago, which is not very long after Google implemented this change and we began seeing problems with our own ChromeOS Player as well. 

  • Avatar
    Riel

    Hummm ... that would make sense.

    I'm not the actual coder, so I'll have to verify, but my gut says that's the issue as of course, we relied on hitting autoplay on a pre configured playlist in youtube.

    **** (pardon my french) I hate having to spend money on coding when other people's API's get updated, it always feels like a punishment :)

    Any thoughts on how to work around?
    Spare me digging though the new docs ...
    I'm wondering for example, if I play it once on the player first to get it cookied prior to releasing maybe?

    I don't currently deploy with any keyboard or mouse, it just boots into the player and you can switch the playlist from an online software remote.

    The definition of plug and play :)
    I'd prefer to keep it that way, but if autoplay is out, I don't know how to do that, kinda kills the whole thing :(

    ----

    I thought I'd share some images to show you what we built :)

    Here's the 'remote' (software on your phone when you're logged in)



    This is one of the screen layouts for automotive

     

    The player is a chrome box in kiosk mode with the player booting automatically
    They just turn it on and it's preconfigured with it's ID# so it just played
    it was such a simple, elegant way to deliver to a clueless client :)
    Sucks that it just stopped :(

    Screen Example: this is the general layout
    Pretty basic video (eye candy - this is from the 'pure' playlist) with ads on side and below

  • Avatar
    Colby Maughan

    Hello,

    It can be pretty frustrating when you've got something working and the rug just gets pulled out from underneath it. 

    As far as workarounds, we don't really have anything prior to this ChromeOS player update we're pushing. A big part of why the ChromeOS player has been unsupported for a while is that there was just not much we could do on the support side. Eventually issues stacked up to the point where the player simply needed further revision to account for the numerous large changes on Google's side.

    I'm not 100% sure what our devs have done to correct the issue if I'm being honest - it's a pretty new fix. The Google documentation I linked above does have some information on it which I'm sure would be relevant in this case though.

     

    Additionally, if your Chrome Boxes are managed, you could try setting them to the previous version of Chrome that didn't have the autoplay issue, or you could mute the videos.

  • Avatar
    LUIS REYES

    Hello, is the new Chrome Version already released?

  • Avatar
    Darius Aleksas

    Just wanted to keep all of you informed that in the past 2 days two old Chromeboxes with the latest unsupported version of RV and management licenses have crashed and needed to be wiped clean and installed as RV kiosks again. Cannot be a coincidence. Highly unlikely...

  • Avatar
    Riel

    Frustrating

  • Avatar
    LUIS REYES

    Well in fact the reason of my question above is because today I found troubles with two players, regarding the autoplay, I wiped them 3 weeks ago, and  I thought I have installed the older version, I also set the autoplay chrome flag to NO gesture, and was OK. But today I have the autoplay problem, At the console these players appears with "RisePlayer 2018.08.24.7402 Free" . The other ones I have, have the unsupported version and works ok. So Idon´t  know if actually there are 3 versions: free, unsupported and beta??

     

    At the time I wiped the Chormebox, I first installed the BETA, but decided to delete it because I tried to play with i.e.TWITTER and says there is no preview (need to see the result in the display, mmm), then the screenshot  was not available, so I decided to wait until the final realease to come, tha if I understood was announced to be ready on august. Unfurtunatly tomorrow I need to drive to these two locations and get fixed. 

    Hope the new version come soon and fix these bugs. 

     

  • Avatar
    LUIS REYES

    Hello, want to ask if someone else is having this black screen autoplay issue? and how have you solve it. Do not know if this has somethingto do with an specific Chrome OS version (s) 

    For the last 5 days, I have been experienced this in at least 4 different displays, some times get solved with several reboots, some with several restarts, some others just get fixed after some minutes doing  nothing, but couldn´t find what is causing this and how to solve it .

    thanks

  • Avatar
    Patrick Arsenault

    @Darius:  Do you know what versions of Chrome OS were installed on the devices that crashed?  Can you describe the behavior?  We are currently tracking an issue which appeared to be relatively isolated.  Thanks!

    @Luis: A ticket is currently open for the issue you are experiencing with autoplay.  This actually sounds like the issue we first started experiencing when Chrome changed its autoplay policy in a version update last year.  If anyone else is having this same issue, try muting the videos and see if you still experience this.  If you do, please let me know so I can have a closer look.

    Concerning the versions of Chrome OS Player in circulation, your hypothesis is close but not quite true.  As with any software deployment that moves into Beta and then Stable, there are two sets of install instructions which you can find here (Stable) and here (Beta).

    - The Beta version is the newest version of the Chrome Player.  If you like to be ahead of everyone else, this is the version that will let you check out our newest features and provide feedback on them.
    - The Stable version is the newest version we have confirmed to be stable.  Player updates are rolled out in a deferred deployment, so it's possible to have the Stable version installed and be on the same version as Beta, but until that deployment reaches 100% you can have a version that is older than the newest available (Beta) version.

    So, in summary, "Free" and "Licensed" are actually about our recent shift towards display licensing and not related to the Chrome player version that is installed.   We currently have some devices still on the legacy player, some that have updated to a Stable release of the new player, and some that have opted-into and are in Beta.

    Hopefully that helps clarify things a bit.  My recommendation for right now is to stay on the Stable version, for which you can find install instructions here.  If you are already using the legacy Chrome player, there should be no action necessary for right now, since the instructions haven't changed.

    Cheers,

    Patrick

  • Avatar
    LUIS REYES

    Still having the problem of the auto play, 

    Today problme with 4 displays.

  • Avatar
    LUIS REYES

    Just to let you know, it seems to be fixed.

    My presentations were only running a video folder, so what I did was to add a 10 second image before the video folder, and that pushes the "video folder"  with no problem, made several reboots and ok.

     

    Keep tracking.

     

     

     

     

Please sign in to leave a comment.