[MikesSite]

Originally Posted by Digital Jedi

The last time I worked with Flickr (and note, that I've had to frequently update AME 2.5 definitions for Flickr) the problem I ran into was their URLs strings for videos and photostreams were identical. And that was the problem. URL strings for different media types need to have at least on unique identifying pattern (even it's just in the HTML code) so AME can tell that one URL needs to convert to a video and another needs to convert to a slideshow. With Flickr, when I worked with it in October, the best I could do was create one that detected video. However, despite my best efforts, any definition I created to embed a slideshow would try to convert video URLs, too. You can imagine the weird Frankenstein embeds I got with that. Even with the video definition turned off, the slideshow def would still try to embed video URLs.

I'll probably add Flickr to the next set of updates for AME 3, but note that it will be video only. Unless Flickr has made, yet another, change to their website, then slideshows won't be in this set. I usually try not to release definitions that don't work the way they should. But we'll see what I can come up with.

Thanks for taking the time to respond to me. Will keep my eyes out for the update in AME 3 and in the meantime if you would like to share how you were able to detect at least the video then that's a good start for me