I have done some research, and although the reports aren't very consistent, it looks like a 2 GB filesize limit when accessing content through Flash can be caused when either the browser, or Flash, or the interface between browser and Flash is only 32 bit.
Since Chrome ships with its own Flash plugin, larger files seem to work with Chrome, but with Firefox this is not possible, and there is simply no way for a web based player to work around this, because we are still bound by the limitations of the browser.
In any case, your real problem is that you're trying to play back an absurdly large file over HTTP. You need to use the right tool for the right job.
If your video is long (longer than 10-15 minutes), HTTP tends to be the wrong delivery method because the initial load time of a video goes up linearly relative to its length, so startup times become unacceptably long. This works much better if you use a streaming server (Wowza or Flash Media Server).
Also, if you serve up longer content, seek times will get longer if your video is longer too, and most importantly, a lot of time people tend to not watch the whole video, so if you serve up a 2 GB video over HTTP, this will likely result in terabytes of wasted bandwidth per month that is not viewed, but that you still need to pay for.
If your video is shorter than 15 minutes and yet >2 GB, you simply didn't compress it well enough.
I have done some research, and although the reports aren't very consistent, it looks like a 2 GB filesize limit when accessing content through Flash can be caused when either the browser, or Flash, or the interface between browser and Flash is only 32 bit.
Since Chrome ships with its own Flash plugin, larger files seem to work with Chrome, but with Firefox this is not possible, and there is simply no way for a web based player to work around this, because we are still bound by the limitations of the browser.
In any case, your real problem is that you're trying to play back an absurdly large file over HTTP. You need to use the right tool for the right job.
If your video is long (longer than 10-15 minutes), HTTP tends to be the wrong delivery method because the initial load time of a video goes up linearly relative to its length, so startup times become unacceptably long. This works much better if you use a streaming server (Wowza or Flash Media Server).
Also, if you serve up longer content, seek times will get longer if your video is longer too, and most importantly, a lot of time people tend to not watch the whole video, so if you serve up a 2 GB video over HTTP, this will likely result in terabytes of wasted bandwidth per month that is not viewed, but that you still need to pay for.
If your video is shorter than 15 minutes and yet >2 GB, you simply didn't compress it well enough.