• Chris O'Shea 6 months ago
    Ideally what I would like to do is have a vimeo player embedded on a page, and another flash movie that can access the position in the timeline of the vimeo video.

    We have a conference where we publish the speakers videos, it would be great if we could publish sub titles and images from peoples presentations alongside this.

    Any thoughts?
  • Soxiam 6 months ago
    i think you will find there are many apps that does something like this. while i find this interesting, it's not in our plan to work on something like this at vimeo in the near future.
  • Ted Roden 5 months ago
    We've been talking about getting these kinds of things via JavaScript. You can probably hope to see it in the next week or two.
  •  
  • Chris O'Shea 5 months ago
    Is it possible to even get as a variable the timeline seconds? via javascript to the flash object.
  •  
  • Peter Kirn 5 months ago
    This is funny, because I was just having a similar conversation with some of the Flickr team (including their lead designer), having looked at their API. I'm assuming the point of having an API is to enrich the interest level in the content on the site -- thus driving additional revenue (via advertising or premium accounts or whatever). But the problem is, if there isn't a single method in the API that goes beyond what the site interface itself provides, where's the incentive to use the API? Vimeo.com already gives you the interface for the activities described in the API methods. So if I can just get a list of videos, that's something I could do by hyperlinking to a page or using RSS. What I want is something that goes beyond that.

    Now, I realize this could yield some feature creep. But you could pick a couple of methods that would be most useful. So in this case, there are two methods:

    1. A setter for playhead position.
    2. A getter for a thumbnail at a playhead position.

    Both are already there somewhere, or Vimeo's navigation -- and ability to let you choose from among various thumbnails -- wouldn't work. It's just a matter of making them public. And it would yield many applications beyond the ones described here. Increasingly, I think it'll be that kind of developer access that makes people choose one service or another.

    It doesn't mean make the API do everything. That's clearly impractical. It means pick one thing beyond the basic methods -- maybe it's not this, maybe it's something else -- but one or two things that let the developer's extension to the site meaningful.
  • Soxiam 5 months ago
    "if there isn't a single method in the API that goes beyond what the site interface itself provides, where's the incentive to use the API?"

    i fail to understand your statement. are you saying that the purpose of api is to offer methods that are not available as a site feature?

    i've always thought the main purpose of the api is to allow the developers to make interesting applications based on what the site offers.
  • Ted Roden 5 months ago
    "So if I can just get a list of videos, that's something I could do by hyperlinking to a page or using RSS. What I want is something that goes beyond that."

    Currently it goes way beyond that. As you can see from the API documentation. Also the full method list: vimeo.com/api-docs/advanced-api-docs.html

    I don't see any reason to provide more functionality via the API than you could do on the site, why would we purposely cripple what our site could do?

    We're working on providing opening up the flash player a bit more so you can play/pause, setting the playhead and all that plus some more interesting stuff.

    Getting a thumbnail from the current frame probably wouldn't work, where would the image get stored when you "get" it? We get our thumbnails when we transcode the videos, not via flash. Plus, you can already the thumbnails via the API in any size you want: vimeo.videos.getThumbnailUrl.
  • Chris O'Shea 5 months ago
    "We're working on providing opening up the flash player a bit more so you can play/pause, setting the playhead and all that plus some more interesting stuff."

    This would be perfect. And to be able to use Javascript to get the playhead position too.

  •  
  • Peter Kirn 5 months ago
    I'm sorry; I should have rephrased that. What I was trying to say is, if the API isn't *deep* enough, developers wind up just replicating what the site does already. And I will argue that, if you go and make an API, the ideal would be for developers to come along and provide a way of looking at and interacting with your content that you didn't think of. Now, obviously, that can't be methods that don't have *some* life somewhere on the site ... backend or otherwise. And it doesn't mean you "crippled" the site; it just means someone else might think of something you haven't yet in terms of how you look at the content and the data associated with it. Nothing's there that isn't already there, it's just that they would provide a different way of seeing what's there. And I'd say our job as developers is to take those methods and provide some view of that content that gives the content new usefulness beyond what it already has, that extends the site.

    But before I overcomplicate what I was saying, I'm with pixelsumo -- if you can open up the player itself, then I think developers can provide some very meaningful stuff. And it doesn't have to be complicated... just setting the playhead is really what I think we're looking for here. And that could be hugely powerful.

    Playhead position isn't the easiest example... another one would be how you take the data you've queried from Vimeo and try to give people a different view of what people are posting. So, for instance, you might want to go beyond just getting a list by tag, and try to triangulate tag information with what people like, when activity happened, etc.

    Right now, I think I could probably use the advanced APIs and put my money where my mouth is and build something that lets you, say, look at a 3D cluster of video thumbnails by tag, like, friend, other interconnections between videos.

    But there's another problem -- I need to be able to differentiate private from public information. And it looks like there isn't a graceful way to do that, beyond doing the query and getting an error message. (If I'm correct about that.)

    I'm not meaning to lecture here; I'm just saying -- I'm really excited about Vimeo for the long haul. So I'm enthusiastic about, even if it's just one simple method, anything that allows us to do something that interacts with the community beyond what the site does already, absolutely.

    Peter
  •  
  • Chris O'Shea 5 months ago
    Hi Vimeo

    "We're working on providing opening up the flash player a bit more so you can play/pause, setting the playhead and all that plus some more interesting stuff."

    I was just wondering if anything had moved forward on this front? It would be great to get the playhead position via javascript.

    Many thanks
  • Blake Whitman 5 months ago
    yep, still working on it!
  •  
  • Chris O'Shea 3 months ago
    How's it going Blake?
  •  
  • Chris O'Shea 3 months ago
    Any news on this? Its been a while since we heard anything.

    thanks
  •  
  • Chris O'Shea 1 month ago
    Are you guys still working on it? Thanks
  •  
  • Chris O'Shea 15 days ago
    Hi

    Any news on this?

    It would be so simple to do. If you had a variable on the flash route called timelinePosition for example, with the time in seconds, then I could easily make a javascript function to read this variable.

    Many thanks
  •  
This conversation is missing your voice. Take five seconds to join Vimeo or log in.
Need help with Vimeo?
Please check the Help page for general FAQ, video tutorials, and other helpful information

Sponsored by: