We are making a live broadcasting software for YouTube. Following LiveStream API guide, we could successfully broadcast our live event.
One issue we encountered, however, is that we never get the correct GMT information for the event.
For example, even though we are on live from from South Korea, which is GMT+9, but according to the creator studio's page, all live events were
broadcasted from GMT-7.
Currently we’re using the following API: snippet.scheduledStartTime
https://developers.google.com/youtube/v3/live/docs/liveBroadcasts
The usage is like snippet.scheduledStartTime(1997-07-16T19:20:30.45+01:00)
As guided in http://www.w3.org/TR/NOTE-datetime
Is there any issue with Google's API for Timezone setting?
Thanks.
Related
I want to embed a Youtube Live Video inside a webpage. Some years ago this was not a further problem. At the weekend I created a new Youtube account for a sports club and Livestreaming was activated 24h after verification. Now I set "allow embedding" for the Livestream, but every time I create an Event with OBS and stream to this event, the "allow embedding" option is disabled. An older installation for another sports club has this option enabled every time I stream.
Once the Livestream is startet it is possible to change the option via YouTube Studio, but it should be the default.
Any ideas?
The moment you start the live stream the "allow embedded" is switched off. If you immediately after going live (during your intro video or waiting video) switch it back on again on the youtube website it works fine. But it is indeed an irritating bug.
I have a problem with the YouTube Livestreaming API, and it is only causing a problem on one single account.
The CMS I support has a live to YouTube function that automatically schedules and delivers a livestream from our studios to YouTube as a parallel channel to our website. We support multiple teams who all authenticate their accounts against our application to do this.
About 6 weeks ago we had a single group report that they are no longer seeing their content streaming live to YouTube. All the other accounts, as well as our test channels, are working fine.
With the account in question we can see the livestream get created, the broadcast is created, and they are bound together. Once the encoders are started we are able to successfully transition the stream to "TESTING" without problem approximately 10 minutes prior to the scheduled start time. Where we are seeing the problem is in the final step where we transition the stream from "TESTING" to "LIVE" at the starting time of the broadcast. We get a response with "(#100) Status transition not allowed" when we attempt to transition to live. Prior to this step we retrieve the lifeCycleStatus value, and it shows as "TESTING".
If a user logs into YouTube Studio at this point, they are able to manually transition the stream to live.
The fact that this is working with multiple other accounts, and all are using a common code base and app, I am concerned that there is something about the account itself that is causing this issue. I have not been able to see any significant differences in the account settings when comparing with our test account.
Is there any way I can get further information about why the transition is failing, or something I should be specifically looking for as a potential problem?
I'm looking to get some information from the Sonos API but I can't seem to find it.
In the Sonos app on the "About My System" page when you scroll down (And have a device connected to your tv) it shows "Audio in". I want that information from the API. Is that possible?
Hope to hear,
Kind regards,
Namanix
The Audio In field displays the audio format that Sonos home theater speaker is receiving. See Check the audio format in Troubleshooting low audio from surround speakers for details.
The Sonos platform enables the following line-in APIs and capabilities:
Use the loadLineIn command in the playback namespace to change the current group source to the line-in source of a specified player.
View the source type in the container object. Sonos home theater products use the linein.homeTheater type. See container in Playback Objects for details.
Products with line-in capabilities include the LINE_IN capability in the player object. See the groups object for details.
I'm not sure what you're looking for, but the Sonos Play:5 (gen1) has an UPNP service called AudioIn.
If my playbar switches to TV mode (I've turned auto switching on), than the CurrentURI changes to x-sonos-htastream:.......
Instead of building something yourself, you can also check-out this typescript/node library #svrooij/sonos.
I was wondering if it was possible to detect what song a user is listening to from his/her current active device via the spotify web api.
Thanks.
I know this is an old question, but there is a new beta API endpoint available that supplies this information. It does have some bugs that I've noticed though.
Stations only: If you change stations, you have to restart Spotify to get the API endpoint to update and continue updating.
According to bug reports, it lags behind 20 to 30 minutes at random. I haven't had that problem, so it may be fixed.
GET https://api.spotify.com/v1/me/player/currently-playing
Docs: https://developer.spotify.com/web-api/get-the-users-currently-playing-track/
This is not possible using the web API. If you're writing a Mac app, you can use the Spotify Desktop Client's AppleScript API to access the current track. If the user is scribbling to Last.fm, you can use Last.fm's APIs. Otherwise, this data is not accessible.
In an effort to get music-related events for an app we're building, we've mulled through Myspace's decidedly clunky authentication process and managed to set up a subscription and endpoint.
Using all this fun stuff:
http://wiki.developer.myspace.com/index.php?title=Category:Real_Time_Stream
http://wiki.developer.myspace.com/index.php?title=Stream_Subscription_API
http://wiki.developer.myspace.com/index.php?title=Stream_Subscription_Example_Walkthrough
The Myspace GET request verifies the existence of our subscription. So all we were hoping to do was sit back and wait...
...but even with no query filtering set whatsoever (i.e. we should get EVERYTHING that happens!), we seem to get no data pushed our way.
Most worrisome is that I don't see anyone talking about this on the web anytime recently. Does it still exist? It's still on Myspace's Developer homepage. Did they forget to take it down? Is their sense of self-esteem so low at this point (for obvious reasons) that they've stopped caring about whether their services work?
A boolean answer with conclusive supporting evidence would be most appreciated.
Links to resources and discussions less than a year old would be an awesome bonus.
Myspace has a very inactive MySpace Developer Team News and Announcements that lists various API modules designed to work with the ActivityStrea.ms standard and has a dedicated Activities API webpage with examples.
Once you view that page, you'll see they work within the depreciated OpenSocial API v1 Platform.
In reference to the Stream Subscription method your using, the History Log has the last entry at January 2010. It's safe to say that method has been abandoned. Reference screenshot:
I visited Wikipedia Myspace Page to discover what Developer API is currently used and was greeted with the same outdated information that you already have. The last API used was in 2010.
There still is hope for your goal of getting music related events via a current API method: The above Wikipedia page has a section titled Decline: 2008–present which links to footnote 71 for a January 2012 article: MySpace is Reborn at Panasonic Press Conference, Unleashes Justin Timberlake
That Wikipedia announcement reads:
In January 2012, the company announced at CES that it would introduce MySpace TV with Panasonic.
While Myspace is currently under the radar for developers and your goal is to get Music Related Events (from music artists?) via API, consider using YouTube API that has a powerful search feature to find such events from artists with legitimate YouTube ID's.
If that's not an option perhaps Myspace TV / Panasonic venture will come into fruition soon.
As this is not a happy answer, it's only fitting to Cry Me A River until a new API is realized.
Edit: As your looking for a Boolean Answer, MySpace API is false.
To complement that Boolean state, these other JavaScript values are considered false too: 0 -0 null "" undefined NaN.
WordPress for MySpace API is abandoned with last blog entry April 2010.
The MySpace Stream Subscription API is a component of MySpace RESTful API that is abandoned.
Finally, the MySpace Developer Home Page was last updated on December 2010.
Even to this day, Google Groups for MySpace API has no activity since July 2010.
The above links is Further Evidence that the MySpace API is dead.