Hi,
When I upload a Youtube or Vimeo video I keep getting the "encoding pending" message.
What is wrong?
Just to clarify, this is an image of what I am talking about: http://img191.imageshack.us/img191/5228/publishstatus.png
Thanks!
--
Martin
Encoding pending when adding a Youtube or Vimeo video url
17 posts Started 1 year ago by dmferrari Latest reply from changux
-
-
Hi Martin,
So when you add the YouTube video (pasting the link into the URL box) you need to make sure that you hit "enter" after pasting it in there. Once it is added you should see a screen like this and the name YouTube should appear in the file dialogue. If it doesn't appear it's because you haven't added the file to the dialog.
Once it is added it should automatically skip the encoding step since the YouTube or Vimeo clip is already encoded... and it should proceed to awaiting publishing.
-
Oh I should also note that we are currently working on overhauling this functionality so that it is more obvious to the user. The next release of MediaCore will make adding files significantly more intuitive.
-
Thanks Stuart!
That thing does the trick :D -
I'm getting the same problem, with no fix. Screenshot: http://imgur.com/1kVqL.jpg
Edit: OK, it's only when adding to a podcast. Does that mean podcasts can only be uploaded audio-only? ... I want a podcast with Vimeo video embeds.
Edit2: Hmm, it works in your demo... but not for me :(
-
Hey nado,
When a media object is part of a podcast, it gains the extra requirement that it must have at least one 'podcastable' media file before it will be considered 'encoded'.
'podcastable' media files are generally .mp3 (audio only) or .mp4 (audio/video) files.
YouTube embeds and the like can't be added to podcast feeds, so they are not considered 'podcastable'.
-
You can do it in the demo though. i.e. create new podcast, add Vimeo media file to new podcast. Click "review" and it publishes.
-
So is this something only the demo can do, or is there something off in my installation?
-
Interesting find. Can you tell me the exact sequence of steps you went through to get that? The demo does run a slightly different version than 0.8 (it's a newer development version), but looking at the code, the behaviour I described should still be in place.
-
Nothing fancy:
1) Add new podcast: http://getmediacore.com/admin/podcasts/new
2) Add episode to podcast: http://getmediacore.com/admin/media/new?podcast=43
3) Add file (copy in Vimeo link) & title/details
4) Save
5) Click Review
6) It then skips the encoding step
7) Then click PublishThis is exactly what I'd like to do with my installation. i.e. I have a video podcast with all the episodes on Vimeo. To save storage and bandwidth strains, I want to just include the existing Vimeo videos into a neat podcast in my mediacore installation.
It's frustrating that it works so perfectly in the demo, and just sits on encoding with my install :(
-
So um, is there any way I can fix this?
-
I'll get one of the guys to look into this. This certainly shouldn't be happening.
-
Cool thanks. I'm using MediaCore as a media aggregator more than an upload site. So being able to add Youtube/Vimeo embeds to a podcast would be ideal.
-
This is the intended behaviour because iTunes doesn't support playing YouTube/Vimeo videos in a podcast. The only way to do so would be to download it and re-encode it as MP4 file with the H264 codec, and host the file from your own server.
If you add a YouTube link and an MP4 file, MediaCore will use the YouTube URL whenever possible to minimize your bandwidth usage. For example, with a modern browser, the YouTube URL is used, but on mobile devices and in iTunes, the MP4 file is used.
Hope that helps. In an upcoming release we're planning to make this much more clear to the user — all this file format nonsense is certainly a headache!
-
You can try to add vimeo or youtube videos, this:
1.) Login into mediacore database with privileges.
2.) Do:
> update media set encoded = 1 where encoded = 0;
> update media set publishable = 1 where publishable = 0;
If you want to allow only certain content, add one "where" condition with the column "slug".
Is dirty, but works! -
While you certainly could change the encoded value directly in the database, I wouldn't recommend it. Any time you go to the admin's edit media page the encoding status is re-checked, and your change would be overwritten just by viewing the page.
Under what circumstances do you need to override this value? Is it just for podcasts that its a problem?
-
I see, but if the podcast does not work properly with youtube and vimeo, I can not use.
I prefer to change the database that do not use.
Is dirty, but works!
Reply
You must log in to post.