Microsoft has an opportunity here to support a codec that free browsers-- such as Firefox-- may not be able to support, given the codec's licensing restriction.
If YouTube never works with free browsers, the proprietary browser makers all get a major boost.
Likewise here. I'm tired of trying to share the wisdom of Python and open-source solutions to problems. This place will always be a Microsoft shop, and heck, I'm sure they deserve it.
See the various busybox lawsuits, where they found strings related to the busybox source in various products. I believe you can be compelled to show your source code in response to a subpoena, but it won't necessarily become public record.
It also scares me that you think there could be "some weird loopholes in copyright law." If you don't know what copyright does for you, why the heck are you in a creative industry? Go! Read! Learn how copyright works and how and why the GPL works within it.
That's actually something Linux does well at the moment, in my opinion. There's no fancy interface to it, true, but when I issue a dvgrab command, it gets *done*.
I'm coming to this with a different perspective-- I'm actually an editor, too, and I want my editor to focus on, well, EDITING. We're getting all of these open source editors with bells and whistles, but they don't edit very well at all.
With any luck, I'll be back here in a year promoting my way of doing it.
I agree completely, which is why I'm actually in the middle of writing one for Linux (+ maybe other OS's). A lot of work.
If anyone's interested, I'm working on a two-fold project: a video framework that works in 4:4:4 linear floating-point RGBA with OpenGL acceleration, and a video editor built on top of it, all scriptable via Python.
The framework is coming along nicely. I've just begun on the editing interface. You can see recent (but not current) framework code at: http://www.fluggo.com/redmine/projects/show/fluggo-media
I would be absolutely happy for someone to take the framework and build their own editor on top of it. I would love to provide support for that case. If anyone's interested, drop me a line at brian@fluggo.com.
Diamond manufacturing is already possible. The synthetic stuff is way cheaper than the stuff the cartels sell.
Their reaction? Build better detector machines that can find the flaws present in a "natural" diamond vs. a synthetic one to tell whether it's worth anything. See http://en.wikipedia.org/wiki/Synthetic_diamond
If you were to tell me that Little Endianness was simply the result of someone putting something on an overhead projector the wrong way, I'd believe you (because it seems like an extremely fucking stupid idea otherwise: "2 ^ 16 equals five-hundred-thirty-six, sixty-five thousand"
Little endianness allows you to do type casts without adjusting pointers.
Then wouldn't it be handy for the ISP to state the normal bandwidth vs. the burst rate? If they told me that up front, rather than just the full bandwidth of the pipe, I wouldn't have a problem.
That's what I also thought when I heard them on the radio-- Verizon was just asking for a lawsuit with that phrase. I was confused at first and thought it was an iPhone ad until I recognized the Verizon music.
- Video. The PAL standard is better quality than NTSC (Never The Same Color), so why did the Americas adopt an inferior option?
PAL was invented after color NTSC, and thus had the advantage of knowing NTSC's weaknesses.
Not that it matters anymore, because digital television standards pretty much wipe out those problems. Now it's ATSC vs DVB.
- DVDs. Take away the PAL and NTSC thing, and you've still got to deal with the DVD+R, DVD-R, DVD+RW, DVD-RW, DVD-DL+R, DVD-DL-R, DVD-DD+R, DVD-DL-R, the majority not compatible with all burners, drives and/or players.
Slashdot Mirror
Does it help you to know that you misread the summary?
The *crater* could be 100 km across. The *asteroid* could be "between 5 and 10 km in size."
First amendment literature usually uses it as an example of unprotected (inciting) speech.
If you thought the headline was clever, you should have read the summary, where you might-- *might* have found out who Taylor Momsen is.
Which you easily managed to do by not reading the summary.
But then the same goes for actual information.
Microsoft has an opportunity here to support a codec that free browsers-- such as Firefox-- may not be able to support, given the codec's licensing restriction.
If YouTube never works with free browsers, the proprietary browser makers all get a major boost.
Likewise here. I'm tired of trying to share the wisdom of Python and open-source solutions to problems. This place will always be a Microsoft shop, and heck, I'm sure they deserve it.
See the various busybox lawsuits, where they found strings related to the busybox source in various products. I believe you can be compelled to show your source code in response to a subpoena, but it won't necessarily become public record.
It also scares me that you think there could be "some weird loopholes in copyright law." If you don't know what copyright does for you, why the heck are you in a creative industry? Go! Read! Learn how copyright works and how and why the GPL works within it.
With great power comes great responsibility, even if it is just a comedy channel.
That's actually something Linux does well at the moment, in my opinion. There's no fancy interface to it, true, but when I issue a dvgrab command, it gets *done*.
Ack!! No! I've disabled the sign-in barrier.
I'm coming to this with a different perspective-- I'm actually an editor, too, and I want my editor to focus on, well, EDITING. We're getting all of these open source editors with bells and whistles, but they don't edit very well at all.
With any luck, I'll be back here in a year promoting my way of doing it.
I agree completely, which is why I'm actually in the middle of writing one for Linux (+ maybe other OS's). A lot of work.
If anyone's interested, I'm working on a two-fold project: a video framework that works in 4:4:4 linear floating-point RGBA with OpenGL acceleration, and a video editor built on top of it, all scriptable via Python.
The framework is coming along nicely. I've just begun on the editing interface. You can see recent (but not current) framework code at: http://www.fluggo.com/redmine/projects/show/fluggo-media
I would be absolutely happy for someone to take the framework and build their own editor on top of it. I would love to provide support for that case. If anyone's interested, drop me a line at brian@fluggo.com.
I keep hoping I can get half textures/framebuffers in Mesa. SGI or Microsoft still has the patent on that one.
Diamond manufacturing is already possible. The synthetic stuff is way cheaper than the stuff the cartels sell.
Their reaction? Build better detector machines that can find the flaws present in a "natural" diamond vs. a synthetic one to tell whether it's worth anything. See http://en.wikipedia.org/wiki/Synthetic_diamond
If you were to tell me that Little Endianness was simply the result of someone putting something on an overhead projector the wrong way, I'd believe you (because it seems like an extremely fucking stupid idea otherwise: "2 ^ 16 equals five-hundred-thirty-six, sixty-five thousand"
Little endianness allows you to do type casts without adjusting pointers.
Next up for Linux, media production software.
Sweet, that's what I'm working on.
Then wouldn't it be handy for the ISP to state the normal bandwidth vs. the burst rate? If they told me that up front, rather than just the full bandwidth of the pipe, I wouldn't have a problem.
This is 2009, wake up to the real world.
This sentence adds zero value to your reply.
That's what I also thought when I heard them on the radio-- Verizon was just asking for a lawsuit with that phrase. I was confused at first and thought it was an iPhone ad until I recognized the Verizon music.
- Video. The PAL standard is better quality than NTSC (Never The Same Color), so why did the Americas adopt an inferior option?
PAL was invented after color NTSC, and thus had the advantage of knowing NTSC's weaknesses.
Not that it matters anymore, because digital television standards pretty much wipe out those problems. Now it's ATSC vs DVB.
- DVDs. Take away the PAL and NTSC thing, and you've still got to deal with the DVD+R, DVD-R, DVD+RW, DVD-RW, DVD-DL+R, DVD-DL-R, DVD-DD+R, DVD-DL-R, the majority not compatible with all burners, drives and/or players.
Blame it on the DVD Consortium.