[Digital Jedi]

Originally Posted by Dr.H

I decided to run it as a locally hosted Quick time .mov instead which works fine but I can't get the video to show at full 1280x720 size. I did try changing the Quick Time definition replacement to that size but it still stayed at the smaller square size.. Any Idea how to make it show videos in full size?

So far, QuickTime videos are not resizable. And, to be truthful, I haven't been able to figure out why. This is the most recent information I've found on the subject, but I have not gotten a chance to test it out: http://lists.apple.com/archives/Quic.../msg00024.html

Originally Posted by Jaxel

I'm having a little trouble creating a definition for youtube HIGH DEFINITION (fmt=22, not fmt=18)

HD: http://www.youtube.com/watch?fmt=22&v=LQwC0t3rFAQ
SD: http://www.youtube.com/watch?v=LQwC0t3rFAQ

By adding fmt=22& to the URL, you can view 1280x720 versions of the videos in flash. I want to be able to let users add this code to their URL, and have the system read it no problem...

This is what I have tried:

[http://]*[a-z]*?[\.]?youtube\.[a-z]*?/watch\?fmt=22\&v=([A-Z0-9._%-]*)[&\w;=\+_\-]*

<object width="670" height="400">
<param name="movie" value="http://www.youtube.com/v/$p1&hl=en&fs=1&rel=0&ap=%2526fmt%3D22"></param>
<param name="allowFullScreen" value="true"></param>
<embed src="http://www.youtube.com/v/$p1&hl=en&fs=1&rel=0&ap=%2526fmt%3D22" type="application/x-shockwave-flash" allowfullscreen="true" width="670" height="400" wmode="transparent"></embed></object>

It APPEARS to work, using RegexBuddy... AME seems to read in and extract the destination data as well (it adds the title to the video) as in:

[url="http://www.youtube.com/watch?fmt=22&v=LQwC0t3rFAQ"]YouTube - SoulcaliburIV: 2008-SEP-06 W1 SEB VS Jaxel[/url]

However, it does not print out the Replacement text. It prints out the URL to the video (not in a link, just plain text)... but nothing else. Why is the replacement not working?

So that's how their handling HD now. That's good to know. That may change the way I handle the next update.

As to your question, this happens often. And most of the time it's because of the addition of the ampersand (&) in the RegEx. Have it match the HTML ampersand command instead, but make the command itself optional: &[amp;]* That should fix any parsing issues.