If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Enjoy an ad free experience by logging in. Not a member yet? Register.

I just tried "http://www.youtube.com/watch?v=2ZCUtnuAXg8" and it works fine for me...I'm not sure if anything other than "v" in the query string would cause the app to fail, but like the app front end says:

If other types of YouTube URLs dont work for you, then you'll need to write your own code to handle those URLs, or write some code to validate URLs so that they conform to the example URL format. (I didn't really program any validation because I'm just using this app recreationally, for my own personal use.)

But one question, could you show us how to do this ourselves just incase youtube updates again?

Unfortunately, I can't really give you a magic formula for how to tweak the regex when YouTube updates their site...It's mostly just "educated" guessing and a vague familiarity with how YouTube stores and encodes video data in their source code.

What I can say is that, this time, video data is found in this part of the source code (of any given video page):

The code in red is the URL-encoded FLV file location (I think I highlighted the right code -- it's hard to tell when it's encoded like that -- but that is the general vicinity in the source code)...It's just a matter of picking out the correct URL from that garbled mess and then URL-decoding it...

Also, as an aside, the series of regular expressions that I used in SetFlvUrl() could probably be made more efficient (from a coding perspective), but:

1) I wrote the code quickly, and
2) The code does what I need it to do, so I guess I don't care

As always, if something (namely, the regex) doesn't work, let me know and I'll try to fix it....But as long as it works, no matter how ugly it might look, I'm good with it