Our website has been having some issues with the Spotify Play button since the Spotify Web player has come into existence.
There are 3 issues that I have noticed so far:
1) Have to click twice to get the track to play
Clicking the play button (when the Web player didn't exist) used to start the song playback in the background. Now on clicking the button, it first launches the web player (which is fine) but doesn't automatically start playing the music. It imports the playlist but that's all it does. It works only if the user manually presses play on the Web Player/ Clicks on the button the second time (bad from a usability perspective - left our users confused). Along with this, to confuse users further, The Play Button shows "The Track Cannot be played" when this happens. However, if you press on that track again (either from the play button or the actual web player), it works fine and the message goes away.
Tested on Chrome (OSX and Windows 7) , Safari (OSX)
Can be replicated here: http://partysen.se/event/5/tanmays-awesome-party/
2) Invalid OAuth Token
A possibly connected problem seen since the launch of the web player is the play button saying "Invalid OAuth Token" when trying to play something. I do not have much more information to replicate it, other than the fact that it started happening on Mac OSX once the web player was launched and I also installed the mac spotify app.
Tested on Chrome (OSX and Windows 7) , Safari (OSX)
3) Button asks for App Installation
Another issue : On clicking the play button a spotify web page asks for installation of the app. Also discussed here:
https://stackoverflow.com/questions/16348049/spotify-play-button-not-working-in-google-chrome
Noticed this only in Chrome in Mac OSX.
Questions
Is it possible to fix if the button uses the Desktop apps or the Web Player in the mean time ?
Can we get any more information regarding the OAuth Error described above?
Related
Since the last update of Google Glass I have a problem with voice commands. My app worked very well before the software update, but since it updated to XE22 the "ok glass" doesn't work anymore.
When I start the Glass and come to "ok Glass" screen, I can say "ok Glass" and the List of commads (Take a picture, Google, Make a call to, etc.) open. But then the voice input seems to freeze, when my applications are in this list too. The Glass doesn't react on "ok Glass" anymore. But this don't happen with all of my apps. Some of my apps are excepted, although I use the same way to define the keyword (e.g. like this: <trigger keyword="Open my Application" />).
The same problem occurs in the contextual menu. When I use only 3 contextual menu items, it works very well. But when I use more then 3 menu items the voice input freezes, too. Glass doesn't react on voice commands anymore and I need to restart Google Glass.
Before the update everything worked without any problems. I could start my apps in "ok Glass", as well as use contextual voice commands, which I have created exactly like here (https://developers.google.com/glass/develop/gdk/voice#using_unlisted_main_voice_commands).
Have anyone the same problem with the new software update, or does anyone know what to do? Did anything change in defining voice commands? I searched very long, but I didn't find anything.
Here's the scenario I'm seeing -
You click to post a sound from SoundCloud to Facebook
It embeds a player in the post that can either be clicked on to take you to the original item on SoundCloud OR you can click a Play icon to play the sound right in your feed.
The player is a Javascript/HTML5 player (which you can see by viewing source) HOWEVER if you take the embedded URL and put it in the Facebook open graph debugger you'll see that it appears to be directing to embed a Flash SWF
How is SoundCloud doing, what appears to be, some kind of redirect trick to get a "og:video" SWF to turn into a JS/HTML5 player?
I notice that there is an "og:type" of "soundcloud:sound" so is it some kind of whitelist/Facebook application scenario?
Try it yourself with this:
OG debug: https://developers.facebook.com/tools/debug/og/object?q=https%3A%2F%2Fsoundcloud.com%2Fsystek_music%2Fcyberoptics-sub-antix-the%3Futm_source%3Dsoundcloud%26utm_campaign%3Dshare%26utm_medium%3Dfacebook
I did find this bit of info from the SoundCloud site about how they've switched to JS players (that fall back to Flash on older browsers): http://help.soundcloud.com/customer/portal/articles/1219149-where-has-the-flash-widget-gone-
This may only be a partial answer. But there exists a special Facebook Open Graph Music program which "is only available to whitelisted partners at this time". This includes a bridge which has the goal to "enable play buttons on feed stories on Facebook.com that can play and pause tracks and indicate which is playing."
However, apparently you can include both Flash (application/x-shockwave-flash) and HTML5 video (video/mp4) formats in the og:video:type property.
I use www.jango.com as PC music player and want to steer it remotly via my smartphone. I have a server program for controling the PC and an app as client.
I want to use the server program for example to press the play/pause or fast forward button in jango.com running inside the chrome webbrowser.
A simple way would be to simulate a windows mouse click at a specified position within the chrome window. But it would have the disadvantage that it would only work if the jango tab is active and will of course fail if the site changes it's layout and probably due to a lot other reasons.
So I'm thinking about generating kind of the same http request as the browser does if one clicks the button for real. Or somehow accessing the html elemnt
Please consider thatm while having a C/++ background, I lack any web/JS programming skills and would be in favor keeping it this way as much as possible.
Thank you for any suggestions!
The solution is to use an user script for the musik player web site which is able to trigger the buttons in question. Than websockets can be used to communicate between the user script and the c++ server program.
having an annoying problem with JW Player. If I click on the video it will pause and play generally fine however if I use the pause and play button it refreshes my browser. Seems to effect browsers using the HTML5, fine in Flash. Can't come across anyone reporting the same problem. Running the files from videos in Sitecore Media Library. I was having a problem in IE9, saying 'error loading media: file could not be played' I sometimes get this in Chrome after trying to resume playback of video. Any ideas? Have encoded the video in Handbrake as iphone4 and universal MP4 with web optmise ticked.
Not done anything that special with the Javascript and using default skin.
Some pages in my app allow users to click a hyperlink to launch the external browser via a WebBrowserHelper.
I'm carefully saving the app state in OnNavigatedFrom and restoring it in OnNavigatedTo, but when the user navigates back from the web browser into my app, the app hangs, then crashes.
I've carefully followed the great blog post on the Windows Team Blog, but can also reproduce the bug using the provided code there (just add a WebBrowserTask to one of the button click events on the DetailsPage; or in fact a send SMS task).
Can anyone else confirm this bug, or perhaps point out something special that needs to be done to overcome it?
Whoops! Yes it turns out in most cases you just need to resume the debugger to have the app come back to life.
However in my case there is also a bug in my own code. As usual.