Starting last Friday (9/15/17) we started having problems sending captions to live events on YouTube. It appears that the API has changed. The heartbeat post started enforcing the time stamp followed by a blank line format, before last week, an empty post worked fine, now an empty post returns a 500 error instead of the UTC time. Also, a much bigger problem - we are experiencing missing words and lines in the caption display. This just started late last week as well. Looking for some technical support from anyone involved at YouTube with the HTTP Post Captions API. The only documentation I have is from 2013 when we started using the API (ClosedCaptionHTTPPOSTProtocol.pdf), I cannot find any documentation for this API anywhere on YouTube.
Related
We've run a broadcaster awards site for the past 10 years. It's for local broadcasters and publishers to submit entries for their state association. Entrants can submit audio files, image files, document files, 3rd party website URLS...or for videos, submit a YouTUbe url from their own account that the judges will see played back on our embedded viewer.
This has worked great for several years. It's called www.bestinmedia.com
We've recently run into an API request failed quotaExceeded error and the url will not be added to the users account. This started happening over the last 2 weeks near the end of one associations entry period. We've never seen it before and nothing has changed on our site. No settings changed.
Is this a permanent error due to some change at YouTube, or can I fix it? I can send a video screen capture of the process and error if needed
Thanks for your time,
Tom
I checked the Youtube API and it's mainly to do with adding functionalities related to the YouTube app rather than getting analytics data about videos.
There is a chrome extension called VidIQ that shows the views per hours of a particular video when going to the video's page on YouTube, so I tried reading the source code for it, but it is all compressed and I can't easily find what I'm looking for.
Could someone explain to me how VidIQ chrome extension is getting the views per hour stat for YouTube? Maybe it's not an official stat from Youtube but a rough estimate calculated by VidIQ. How do they get this information?
I tried debugging the VidIQ chrome extension to search through the source code but adding a simple html tag made the file corrupted and disabled the extension until I repaired it again. I'm having difficulties deciphering the source code.
Most of what VidIQ gets is from the YouTube analytics api and not directly from the YouTube data api although i would be they use some combination of both.
If you create a report that extracts views and run it every hour you should get the results you are looking for.
However i would be willing to be that they cache a lot of the data and do some internal analytics on it. They would need to cache it as the YouTube analytics api only returns data for the last 90 days last i checked.
If your intent is to Reverse Engineer VidIQ you may need to accept that a lot of the data you are seeing is internally stored in their system and generated by them based upon the data that is avaliable in the YouTube Analytics API and the YouTube data apis.
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?
First of all, sorry for my badly articulated question, this is my first ever question to post here.
I have programmed a youtube search engine for myself and used it for a long time. Yesterday i noticed it was not working correctly anymore.
I spent some time looking for the problem and soon enough noticed that some of the video statistic data queries return nothing.
Here is an example API URL that doesn't work:
https://www.googleapis.com/youtube/v3/videos?id=nNmfb2FQ8MA&key=PUT API KEY HERE&fields=items(statistics)&part=statistics
If you replace the video ID it should return the statistics of the video.
It just doesnt show anything for some youtube IDs for some reason
I have a very basic python app that calls the google vision API and asks for OCR on an image.
It was working fine a few days ago using a basic API key. I have since created a modified version that uses a service account as well, which also worked.
All my images are ~500kB
However, today about 80% of all calls return "403 reauthorized" when I try to run OCR on the image. The remainder run as they always have done...
The google quotas limit page lists:
MB per image 4 MB
MB per request 8 MB
Requests per second 10
Requests per feature per day 700,000
Requests per feature per month 20,000,000
Images per second 8
Images per request 16
And I am way below any of these limits (by orders of magnitude) - any idea what might be going on?
It seems strange that simply running the same code, with the same input images, will sometimes give a 403 and sometimes not....perhaps the error is indicative of the API struggling with demand?
Thanks Dave - yes, I have. After much debugging at my end, it seems it was the API that was up the spout :-) All fine now...