That's a troubling problem. H.264 is played entirely through the QuickTime subsystem - ClickToFlash just tells Safari where to find the H.264 version.
If it's causing problems, you can disable the H.264 features for YouTube, and just have the ClickToFlash part enabled - YouTube will then just load the normal Flash videos when you click.
That's a troubling problem. H.264 is played entirely through the QuickTime subsystem - ClickToFlash just tells Safari where to find the H.264 version.
If it's causing problems, you can disable the H.264 features for YouTube, and just have the ClickToFlash part enabled - YouTube will then just load the normal Flash videos when you click.
Yes, I already did that 🙂, I re-installed ClickToFlash and will not use the H.264 codec again untill I have a clue what causes it to freeze.
I have two '264' components: X264Codec.component placed in /Library/QuickTime H.264.component placed in System/Library/QuickTime
Maybe it is the '3rd party' x264Codec component that causes the problem?
Well dragging it to the trash the Youtube movies no longer load in H.264.
Is there a way I can get Apple's version of the x264Codec back?
I wonder if it may have been Flash that caused some people to get 70-90% CPU loads from Firefox. Did anyone here have the CPU issue with Firefox after upgrading to 10.6? I do know there were some MR members that mentioned it after release day.
I wonder if it may have been Flash that caused some people to get 70-90% CPU loads from Firefox. Did anyone here have the CPU issue with Firefox after upgrading to 10.6? I do know there were some MR members that mentioned it after release day.