I'm trying to use Azure Media Services. For demo purpose I've uploaded a video directly on the portal then clicked to encode this uploaded video in 'H264 Smooth Streaming 720p' preset.
This scheduled a encoding job which generated another (off-course larger) file which I published to get the manifest file URL.
I can play this video on the portal itself but when I use the given URL I get the following error:
A network error caused the video download to fail part-way. Please check your network connection or try again later. (0x20200000)
I'm taking help from this Channel9 video.
Please help me on this.
Please add &format=smooth to your URL and it should work!
http://amsplayer.azurewebsites.net/azuremediaplayer.html?url=http%3A%2F%2Fmspocforknorish.streaming.mediaservices.windows.net%2F72496130-cb2d-455e-9ccd-420fcb506f1d%2FBigBuckBunny.ism%2FManifest&format=smooth
Otherwise, on the page check "Advanced Options" checkbox and select Smooth from the Format dropdown and click on "Update" button.
When you paste your URL into the URL input, delete the existing sample URL that is already there. The existing URL looks like placeholder text but it is not. I fell into that trap too.
Here is a screenshot of your video playing and here is the URL of it playing.
Related
After uploading video using youtube api with oauth2 authentication(as Desktop app) and code from
https://developers.google.com/youtube/v3/guides/uploading_a_video which is modified to compatible with python3 changing print function and httplib to http.client, YouTube locked uploaded video as private so no option to change as unlisted or public.
Same video file with same title and same description uploaded via youtube studio in webpage isn't locked and other user can watch it.
Sentence 'For videos that have been locked as private due to upload via an unverified API service, you will not be able to appeal.' from https://support.google.com/youtube/answer/7300965?hl=en is suspicious, but I can't exactly understand what that senetence means. Actually, there is appeal button on locked private mark.
I really hope someone can help me... thanks!
I'm trying to use Azure Media Services to live stream an IP cam through OBS.
So I'll try to describe my setup.
I added a new Media Service via the Azure Portal.
It has it's own storage account.
Still in the portal in that Media Service I choose 'Browse Channels'.
Here I create a new channel, I tried Live Encoding and Pass Through. I get the same result with both.
So the channel is created, I wait until it is started and I open that blade of the channel.
I copy the Primary Injest endpoint and copy that in the settings of OBS, as a stream key I use the name of the channel/account (I picked the same name for both) and start streaming from OBS.
I then click more in the top right of the blade and pick 'Watch preview'.
A new blade opens with a player with an error in it.
When I copy the playback url and open it in VLC it plays correctly for roughly 30 seconds.
Now if I add a new Program back in the Channel Blade it adds it, and starts it up. When started I open the Program Blade and get a loading screen which doesn't end. Looking in the network tab of the developer tools, no errors are present and no open requests.
When I refresh the page I sometimes get the following:
I don't like the red icon but okay. I click the locator and get this:
Clicking the blue box opens a new Blade with a generic error:
With the following error in the dev console:
When trying to open the url from the Locator Blade or the Program Blade in VLC it doesn't open.
I once had the problems I'm having now, but a couple of days later they were resolved without action from my side.
Now I'm having the same problems again.
I tried recreating everything from scratch, but I get the same errors.
From the comment, it seems that all the problems were solved now.
Here is just my experience which may answer your question. I used to have the same issue, and finally I found that I need to start the stream endpoint. At least one stream endpoint needs to be started before we can provide a video streaming service.
If you want to preview the live stream, you need to start the stream endpoint too, as all the stream content will be delivered from stream endpoints.
Update:
You can start a stream endpoint on the portal:
Navigate to your azure media service resource.
Click the "Streaming endpoints" label.
Then you will see all the streaming endpoints you have.
Choose one endpoint, and you can start or stop it in the showing page.
I have an audio file (e.g. mp3) located on Google Drive and accessible at a direct url that looks like https://drive.google.com/file/d/audio_file_id/view where there is a small sliding bar timeline scrubber and play/pause button that let the user hear the audio (and supposedly control the location in the file, but this feature is not working for me on Chrome on mac…; advice on this appreciated).
I would like to start the playback at a specific time. How can this be one? Is there a way to do it like one can do with video files hosted on Google Drive by adding a parameter like t=15s to the video url, like in YouTube?
Drive API doesn't have the seekTo method in Youtube API but you can add the t=123s at the end of the video url and it will work just like it.
sample:
https://drive.google.com/file/d/0Bz6447wI7cGV12546VBmQ2M/view?t=651s
I am new with the spotify app. I try to display a video in spotify's advertise page. However none of the things that I was trying work (jw player, flow player, youtube iframe. html5). Any hints?
Greetings!
Any external hosts with assets you request need to be added to the RequiredPermissions part of the app manifest:
http://developer.spotify.com/technologies/apps/guidelines/developer/#applicationmanifest
In order to display a video in the spotify you have to fulfill following requirements:
your video file has to be stored on the 3rd party server.
you have to use open-source video player (e.g “JW Player”).
you have to create a html file that will be your lightbox. This is the file that you will embed in the video file and player library.
image file for background of the player.
Destination URL must be open in new browser window.
And don't forget to add the address of host your host to the permissions in spotify's manifest file!!!
Example: here
The tool I'm building needs pull data from IBM Connections Ideation Blogs. I therefore use the Connections API with basic authentication to read Blog Entries. This goes well until the description contains images. When I ask the API to provide media resources for the blog, it does not show any entries of the /BLOGS_UPLOADED_IMAGES location - the one containing images uploaded through the blog's richtext editor. The user I use in my API call is the same user who created blog entries and uploaded pictures.
However the API call DOES contain images I publish using the API and a POST request to the blog's media entry collection. This is where the next problem appears. Those Atom entries for images contain various links, one of them with a ref="enclosure", of which the API documentation (link) tells me to "Use the web address in the href attribute to obtain the binary content of the file". However, my calls to this adress are always answered with 404 response code.
Another url in the Atom entry (this time of the element) is described by the same documentation (see link above) as: "Provides access the document's media. The following operation is supported: GET: Use the web address to obtain the media." When I make a call to this url, as always with basic authentication credentials attached, the response contains the html of the login form of Connections, so API authentication does not seem to be supported on this url. This is only the case for non-public communities, which require authentication, of course, if the picture is publicly availabe all works just fine.
Am I missing something out? Is there another way to retrieve the actual image from a blog's media entry through the API? Are manually uploaded pictures never contained in the media entries result or is this a bug?
It now magically works using the link with ref="enclosure" from the atom entry. I might have gotten something wrong with authentication I guess (although I'm not actually realizing what I'm doing different now than I did before).
Problem remaining: Pictures uploaded through the rich-text editor in the folder /BLOGS_UPLOADED_IMAGES do not appear in the media feed of the blog.