I would like to suggest, that if Mozilla implements H.264, Mozilla should also implement free codecs that Safari or Internet Explorer implement. This example of mine only uses a royalty free codec, works in OSX Safari, but does not work in Firefox: http://jjc.freeshell.org/turning_pages.html
It uses Motion JPEG video with uncompressed PCM audio in an AVI container. Admittedly, MJPEG with PCM uses something like a factor of 40 times more bandwidth than H.264, so it is completely impractical for a site like Wikipedia or Youtube (MJPEG is however currently used, for example in Axis Network Cameras). Another possibility (which would need to be verified by lawyers) might be MPEG-1 Video with layer II audio which might be royalty free and is also supported by Safari.
In short, if Mozilla is going to support patent encumbered formats, they should also support royalty free formats that are supported by other browers.
I think there are only two major patent free video formats right now, Motion JPEG and H.261. Theora and VP8 are patented, but the patents are allowed to be used royalty free.
I agree that it is good that patents will expire. That said, they last longer than 17 years in the US (and in plenty of other countries they last 20 years). But it will be awhile before they are finished. For example MP3 (and MPEG-1 that MP3 is a part of) will not be done till at least 2015 (and the draft standard came out in 1991), MPEG-2 is at least 2018 and H.264 is 2027. By that time, there will probably be some 3D video codec that everyone wants, so we still will have to deal with software patents. http://www.osnews.com/story/24954/US_Patent_Expiration_for_MP3_MPEG-2_H_264
I originally learned to programming on a Commodore 64 using BASIC. My second language was Logo on the C64. I have since programmed in over a dozen languages, and I don't think starting with BASIC harmed me. It's just a matter of learning that there are alternatives in the newer languages.
I do think that Logo is a better starting language than BASIC, since it has things like user defined functions and better list handling.
If they didn't develop the game engine, then just open sourcing the graphics and models would give a good start on developing a full open source replacement.
I don't know if the watts/kg are high enough to power high speed planes. (The new horizon one was about 55 kg and had 300 watts electrical output (from 4400 watts thermal output))
I agree that the removal of ppmtompeg is rather like reading tea leaves. My personal reading is that they think that there might be some legal issues, but that they are not sure enough to be specific.
I saw the ISO statement as well and right now it sounds like they are trying to start a discussion on the possibility. For the Layer 2 audio the major part that I had not found prior art for was the synthesis window.
Is there any good evidence for this? For example both OpenSuse and Fedora have yanked ppmtompeg from their netpbm packages. ppmtompeg is just a MPEG-1 video only encoder based on the old Berkley multimedia group's encoder. Feel free to email me (jrincayc with yahoo com) or reply to this.
If bandwidth is the problem, just use the same bit rate for each codec. H.264 will probably be a bit better, for the same bandwidth, but for the people who don't have a H.264 decoder, this may just be fine. Theora is probably about the same as H.263, which is what youtube was originally anyway.
I would recommend using pungi and Fedora. It can determine all the prerequisites of the programs you specify and download them as well. Basically, you just use the gather portion and it downloads all the files. I used it for maintain https://fedorahosted.org/pungi/
My theory is that slashdot has three problems. First is that now the only way to see which comments are new is to switch from the dynamic index to the classic index. This makes it harder than before to find the new comments and properly moderate them. It also means that discussions tend to spend a lot of time focusing on subthreads of the first few posts.
Second is that the requirement that you either moderate or post to an article means that people who actually know what they are talking about only get to choose one option.
Third is that people who know what they are talking about often have day jobs so by the time they can post, their comments get buried with the noise comments.
I would like to see a good comparison of Theora and MPEG-1 video. If there is one online, I will certainly link it to the wikipedia MPEG-1 article. After US 5,214,678 expires (which was the only patent listed in the discussion (besides my list of H.264 patents)) on May 31 of this year, I might be willing to try and do another discussion on the whatwg list (or somewhere else).
I think that ice is somewhat more slippery near 0C, because then the pressure from the tire or boot causes some melting. Friction is a function of the temperature of the point of contact.
Well, being able to encode and transmit H.264 baseline in 2024 would be a good start. I agree it would be interesting to know when much of the AVC technology was first discussed.
Slashdot Mirror
I would like to suggest, that if Mozilla implements H.264, Mozilla should also implement free codecs that Safari or Internet Explorer implement. This example of mine only uses a royalty free codec, works in OSX Safari, but does not work in Firefox: http://jjc.freeshell.org/turning_pages.html
It uses Motion JPEG video with uncompressed PCM audio in an AVI container. Admittedly, MJPEG with PCM uses something like a factor of 40 times more bandwidth than H.264, so it is completely impractical for a site like Wikipedia or Youtube (MJPEG is however currently used, for example in Axis Network Cameras). Another possibility (which would need to be verified by lawyers) might be MPEG-1 Video with layer II audio which might be royalty free and is also supported by Safari.
In short, if Mozilla is going to support patent encumbered formats, they should also support royalty free formats that are supported by other browers.
As Rob Glidden has pointed out, half of MPEG-2 patents expire in 2012, and a lot more in 2013:
http://www.robglidden.com/2011/12/half-of-mpeg-2-patents-expire-in-2012/
I think there are only two major patent free video formats right now, Motion JPEG and H.261. Theora and VP8 are patented, but the patents are allowed to be used royalty free.
I agree that it is good that patents will expire. That said, they last longer than 17 years in the US (and in plenty of other countries they last 20 years). But it will be awhile before they are finished. For example MP3 (and MPEG-1 that MP3 is a part of) will not be done till at least 2015 (and the draft standard came out in 1991), MPEG-2 is at least 2018 and H.264 is 2027. By that time, there will probably be some 3D video codec that everyone wants, so we still will have to deal with software patents.
http://www.osnews.com/story/24954/US_Patent_Expiration_for_MP3_MPEG-2_H_264
This is for recordings. Compositions are already longer. So if you record Bach at age 15, you can reap the benefits until age 85.
I wish using ulimits was taken more seriously. For example I have to remove memory ulimits every time I start an sbcl or a java program: https://bugzilla.redhat.com/show_bug.cgi?id=568753 https://bugzilla.redhat.com/show_bug.cgi?id=510344
I originally learned to programming on a Commodore 64 using BASIC. My second language was Logo on the C64. I have since programmed in over a dozen languages, and I don't think starting with BASIC harmed me. It's just a matter of learning that there are alternatives in the newer languages.
I do think that Logo is a better starting language than BASIC, since it has things like user defined functions and better list handling.
I live in Idaho, and I have to pay sales tax on Amazon purchases.
http://tax.idaho.gov/i-1018.cfm
"Will you create plastics feedstock from nuclear electricity?"
Yes, basically, if you have steam and a source of carbon (coal, waste plant material ...) you can produce any hydrocarbon you want.
http://www.world-nuclear.org/info/inf116_processheat.html
If they didn't develop the game engine, then just open sourcing the graphics and models would give a good start on developing a full open source replacement.
You are probably thinking of something like a Radioisotope thermoelectric generator http://en.wikipedia.org/wiki/Radioisotope_thermoelectric_generator
I don't know if the watts/kg are high enough to power high speed planes. (The new horizon one was about 55 kg and had 300 watts electrical output (from 4400 watts thermal output))
Publish your implementation, then wait 20 years to use it. The product needs to be described in the public 20 years ago to be guaranteed prior art.
I agree in principle, but three months might be too little time.
I agree that the removal of ppmtompeg is rather like reading tea leaves. My personal reading is that they think that there might be some legal issues, but that they are not sure enough to be specific.
I saw the ISO statement as well and right now it sounds like they are trying to start a discussion on the possibility. For the Layer 2 audio the major part that I had not found prior art for was the synthesis window.
Rob Glidden put up a summary at:
http://www.robglidden.com/2010/04/mpeg-resolution-on-royalty-free-standardization/
Is there any good evidence for this? For example both OpenSuse and Fedora have yanked ppmtompeg from their netpbm packages. ppmtompeg is just a MPEG-1 video only encoder based on the old Berkley multimedia group's encoder. Feel free to email me (jrincayc with yahoo com) or reply to this.
If bandwidth is the problem, just use the same bit rate for each codec. H.264 will probably be a bit better, for the same bandwidth, but for the people who don't have a H.264 decoder, this may just be fine. Theora is probably about the same as H.263, which is what youtube was originally anyway.
I would recommend using pungi and Fedora. It can determine all the prerequisites of the programs you specify and download them as well. Basically, you just use the gather portion and it downloads all the files. I used it for maintain
https://fedorahosted.org/pungi/
http://www.iipa.com/rbc/2010/2010SPEC301INDONESIA.pdf
I agree that Wikipedia often has too many rules. Here is an edit I found particularly stupid.
http://en.wikipedia.org/w/index.php?title=User:Rcooley/VCD&diff=next&oldid=240721783
Is there a good comparison available between MPEG-1 Video/Layer-2 audio and Ogg Theora/Vorbis?
The iphone does not support a single one of the codecs you listed that Mozilla could support:
http://www.apple.com/iphone/how-to/index.html#help.song-video-or-other-items-wont-play
(Okay, both Firefox and the iphone support PCM audio only.)
What do you mean Windows permissions are more powerful than Linux's? Take a look at setfacl. (or for that matter selinux)
My theory is that slashdot has three problems. First is that now the only way to see which comments are new is to switch from the dynamic index to the classic index. This makes it harder than before to find the new comments and properly moderate them. It also means that discussions tend to spend a lot of time focusing on subthreads of the first few posts.
Second is that the requirement that you either moderate or post to an article means that people who actually know what they are talking about only get to choose one option.
Third is that people who know what they are talking about often have day jobs so by the time they can post, their comments get buried with the noise comments.
I would like to see a good comparison of Theora and MPEG-1 video. If there is one online, I will certainly link it to the wikipedia MPEG-1 article. After US 5,214,678 expires (which was the only patent listed in the discussion (besides my list of H.264 patents)) on May 31 of this year, I might be willing to try and do another discussion on the whatwg list (or somewhere else).
P.S. I don't have good guess as to who you are.
I think that ice is somewhat more slippery near 0C, because then the pressure from the tire or boot causes some melting. Friction is a function of the temperature of the point of contact.
Well, being able to encode and transmit H.264 baseline in 2024 would be a good start. I agree it would be interesting to know when much of the AVC technology was first discussed.