Actually, all of the cheapest home automation devices are powerline-based (especially X10).
Pretty much all of the RF-based systems are far more expensive than powerline.
It's sad that X10 didn't do an "X10 Version 2" or something that added improved modulation and ECC to their system. Improve the reliability of X10 and add some address bits (both relatively cheap things to do) and it would be an amazing system.
I saw this article, and my first thought was "What's the per-node cost going to be?"
Pretty much the only reasonably priced system out there is X-10, and for many of the reasons you describe, X-10 kind of sucks.
Everyone wants to go with RF-based wireless systems, but X-10 established that powerline automation was feasible, and with just a few improvements to the comm protocol (error correction, improved modulation) it could become MUCH more reliable, and with minor improvements to the protocol (more address bits, 16 house codes + 16 devices is not enough, esp. since a lot of devices don't do "cross-housecode" operation.) it would be massively more flexible.
While it's a HUGE improvement compared to any other video editing solution I've worked with, it's still not even remotely commercial-grade yet, especially when working with AVCHD video.
Last I checked (about 3 years ago), SOLAS regulations had quite a bit about using GPS as a primary navigation system. At that point, I think it was still not permitted to be primary unless the system met very specific reliability and integrity monitoring requirements.
They're already open. A huge part of any government contract is paperwork, accounting, auditing, and program management.
It's EXTREMELY rare, if not impossible, for a contractor in today's environment to outright bilk the customer. There are simply too many rules and regulations in place. In many cases, when a program gets into that much trouble, the customer is as much to blame as the supplier.
Problem is that in many of these cases, the customer is as much to blame as the contractor.
"Some of the problems stem from government acquisition methods that didn't provide for enough oversight, and added requirements that resulted in cost and schedule overruns."
Note that second half of the sentence. That's typically a customer-driven problem, not a contractor-driven problem. Scope creep is a bitch.:(
Um, users are supposed to disconnect from the VPN when doing personal tasks.
Typical corporate network connections are slow enough compared to a typical home user's highspeed connection (due to the corporate connection typically being shared and running everything through a proxy server) that the first thing a user is going to do when they want to stream video is to disconnect from the VPN.
Downloading a video game patch while connected to the VPN would be grounds for dismissal at most companies.
That's a hell of a security risk, having a client connected to both your internal network and external networks simultaneously.
Every corporate VPN I have ever used has, as part of its function, disabled all network interfaces other than the one it was using once a connection was established. In addition it would prevent any traffic from going through the "normal" connection. The idea was that a machine should never have connectivity to both the internal network and the outside world simultaneously.
The article poster doesn't need to fix their users' ISPs, they need to fix a horrifically broken and insecure VPN system.
Some forms of mold can be toxic even to those not specifically allergic to mold.
A friend of mine and his wife got quite sick after cleaning out her brother's fridge, and he still has some lingering health effects from the mold exposure.
A lot of non-Trekkies are probably thinking "I haven't seen anything else Star Trek so I might not understand it.", but as the reviews come in I think a lot of them will say, "It sounds good anyway, I'm going to go see it."
I know my girlfriend is NOT a trekkie and was apprehensive about the movie, thinking she wouldn't understand any of it. In the end, she really liked the movie. The movie managed to keep the Trekkies happy, AND it also stands on its own and doesn't require having watched any earlier Trek to understand.
Keep in mind that there's a limitation of source content. If your source content is compressed, that's the limit on quality. Right now the best source content generally available to consumers is Blu-Ray. 1x Blu-Ray is 36 megabits/sec.
Redcode RAW (used by the RED ONE) maxes at 288 megabits/sec for 4K cinema video.
It means that there is a 7 GHz wide range of frequencies that is free somewhere around 60 GHz.
e.g. 60-67 might be a possibility, or it might be 57-64.
It's easier to use 7 GHz of spectrum at 60 GHz than 7 GHz of spectrum centered at 10, because the range is a lower percentage of the center frequency of the range.
That said, the range at 60 GHz is going to be insanely short.
It's about stabilization - keeping the camera steady when taking a picture with a long lens to reduce motion blur.
It's not as steady as a tripod or monopod but gives a lot more flexibility/aimability.
Rifle stocks were designed in the first place for the same purpose - resting the rifle against the shoulder increases stability, making aim more accurate.
I think many people have things the other way around.
Content is king. Creating an alternative engine for existing artwork (and likely in WoW's case, scripted content) is a lot easier than creating new artwork from scratch for an existing engine.
Even if they don't have server/client engine source, the sorts of things The9 was doing would require them to have the *content* and that's far more important than the engine source most likely.
Re:Photo Sniper
on
Tactical Camera
·
· Score: 4, Informative
Darn, you beat me to this.
Modern equivalents (which probably function better for camera purposes but don't have the "cool factor" of using an actual rifle stock) are the BushHawk (highend unit) and the Agonic Stedi-Stock (relatively cheap, doesn't have the trigger switch and cabling the BushHawk has)
P.S. Yes, I know I shouldn't be eating that cookie, but I've gotten good at calculating the insulin required for it. The other "unknown" items I normally don't eat are a whole other story.
Actually the problem with the 1918 flu virus was that it had unusually high mortality rates for people with strong immune systems.
The reasoning was that a lot of people died not from the infection itself, but from an *excessive immune response* (cytokine storm).
The whole swine flu paranoia is getting out of hand, especially since so far the actual severity of the swine flu is nowhere near what people are making it out to be. I now have to eat offsite at work because all of the food that I like to eat has been pulled from the cafeteria (all self-serve foods have been pulled except prepackaged items, I almost always eat a build-your-own sandwich and a cookie).
Funny thing is, as a Type I diabetic, who is at unusually high risk for problems if I catch influenza, I'm far more worried about the health effects of this damn menu change than the possibility I might catch H1N1.
1) The laptop may be permitted to enter/exit the "super high security" areas. i.e. wifi isn't used in the same place the cameras aren't allowed, but it is used elsewhere.
2) Most corporations assume WPA/WPA2 is not secure enough and treat the WiFi network as an untrusted external network (despite the WPA/WPA2) and require VPNing into the corporate intranet in addition to WPA2 security.
For a while the T650 was only available with camera - the no-camera version was released by Verizon 3 months after the camera version (which was held back 9 months so they could cripple the phone, after that contract expired I happily became an AT&T customer).
When I started my current job, I couldn't bring a phone with camera into the building. So I popped the back off, yanked the camera module, and popped it into a film canister in case I ever wanted to use it again. Never did in the end.
2 years later my company changed their policy so that cameraphones were allowed if you took a training course on proper use of a camera device within the facility. (30 minutes of training to basically say "don't use it at all":) )
Slashdot Mirror
Actually, all of the cheapest home automation devices are powerline-based (especially X10).
Pretty much all of the RF-based systems are far more expensive than powerline.
It's sad that X10 didn't do an "X10 Version 2" or something that added improved modulation and ECC to their system. Improve the reliability of X10 and add some address bits (both relatively cheap things to do) and it would be an amazing system.
This is the problem.
I saw this article, and my first thought was "What's the per-node cost going to be?"
Pretty much the only reasonably priced system out there is X-10, and for many of the reasons you describe, X-10 kind of sucks.
Everyone wants to go with RF-based wireless systems, but X-10 established that powerline automation was feasible, and with just a few improvements to the comm protocol (error correction, improved modulation) it could become MUCH more reliable, and with minor improvements to the protocol (more address bits, 16 house codes + 16 devices is not enough, esp. since a lot of devices don't do "cross-housecode" operation.) it would be massively more flexible.
I see no releases since 0.7.3
While it's a HUGE improvement compared to any other video editing solution I've worked with, it's still not even remotely commercial-grade yet, especially when working with AVCHD video.
I think you missed it because it's nonsensical.
A documentary crew that isn't doing video editing? Something is VERY strange here.
Also, nowadays even for middle and high school, kids are going to use a computer to do work and study.
Ball or not, they're gonna alt-tab to Facebook, etc.
Someone didn't have RAIM.
Last I checked (about 3 years ago), SOLAS regulations had quite a bit about using GPS as a primary navigation system. At that point, I think it was still not permitted to be primary unless the system met very specific reliability and integrity monitoring requirements.
They're already open. A huge part of any government contract is paperwork, accounting, auditing, and program management.
It's EXTREMELY rare, if not impossible, for a contractor in today's environment to outright bilk the customer. There are simply too many rules and regulations in place. In many cases, when a program gets into that much trouble, the customer is as much to blame as the supplier.
Problem is that in many of these cases, the customer is as much to blame as the contractor.
"Some of the problems stem from government acquisition methods that didn't provide for enough oversight, and added requirements that resulted in cost and schedule overruns."
Note that second half of the sentence. That's typically a customer-driven problem, not a contractor-driven problem. Scope creep is a bitch. :(
Um, users are supposed to disconnect from the VPN when doing personal tasks.
Typical corporate network connections are slow enough compared to a typical home user's highspeed connection (due to the corporate connection typically being shared and running everything through a proxy server) that the first thing a user is going to do when they want to stream video is to disconnect from the VPN.
Downloading a video game patch while connected to the VPN would be grounds for dismissal at most companies.
That's a hell of a security risk, having a client connected to both your internal network and external networks simultaneously.
Every corporate VPN I have ever used has, as part of its function, disabled all network interfaces other than the one it was using once a connection was established. In addition it would prevent any traffic from going through the "normal" connection. The idea was that a machine should never have connectivity to both the internal network and the outside world simultaneously.
The article poster doesn't need to fix their users' ISPs, they need to fix a horrifically broken and insecure VPN system.
Some forms of mold can be toxic even to those not specifically allergic to mold.
A friend of mine and his wife got quite sick after cleaning out her brother's fridge, and he still has some lingering health effects from the mold exposure.
Most likely it was a toll-free 800 number, to which landlines also have unlimited calling.
(But it does cost the recipient of the call money...)
Watch there be a Windows 7 RC botnet worm that includes a crackfix so that it can keep taking advantage of whatever W7 RC security holes there are.
If their software shuts down, the machine may as well be shut down.
Anyone who tried to sue MS wouldn't have a leg to stand on. By installing the software, they agreed to the licensing terms.
It's their software. When you installed it, you agreed to their licensing terms.
You don't like the terms, don't install the software.
I think that's going to be a big thing.
A lot of non-Trekkies are probably thinking "I haven't seen anything else Star Trek so I might not understand it.", but as the reviews come in I think a lot of them will say, "It sounds good anyway, I'm going to go see it."
I know my girlfriend is NOT a trekkie and was apprehensive about the movie, thinking she wouldn't understand any of it. In the end, she really liked the movie. The movie managed to keep the Trekkies happy, AND it also stands on its own and doesn't require having watched any earlier Trek to understand.
Keep in mind that there's a limitation of source content. If your source content is compressed, that's the limit on quality. Right now the best source content generally available to consumers is Blu-Ray. 1x Blu-Ray is 36 megabits/sec.
Redcode RAW (used by the RED ONE) maxes at 288 megabits/sec for 4K cinema video.
It means that there is a 7 GHz wide range of frequencies that is free somewhere around 60 GHz.
e.g. 60-67 might be a possibility, or it might be 57-64.
It's easier to use 7 GHz of spectrum at 60 GHz than 7 GHz of spectrum centered at 10, because the range is a lower percentage of the center frequency of the range.
That said, the range at 60 GHz is going to be insanely short.
It's about stabilization - keeping the camera steady when taking a picture with a long lens to reduce motion blur.
It's not as steady as a tripod or monopod but gives a lot more flexibility/aimability.
Rifle stocks were designed in the first place for the same purpose - resting the rifle against the shoulder increases stability, making aim more accurate.
I think many people have things the other way around.
Content is king. Creating an alternative engine for existing artwork (and likely in WoW's case, scripted content) is a lot easier than creating new artwork from scratch for an existing engine.
Even if they don't have server/client engine source, the sorts of things The9 was doing would require them to have the *content* and that's far more important than the engine source most likely.
Darn, you beat me to this.
Modern equivalents (which probably function better for camera purposes but don't have the "cool factor" of using an actual rifle stock) are the BushHawk (highend unit) and the Agonic Stedi-Stock (relatively cheap, doesn't have the trigger switch and cabling the BushHawk has)
P.S. Yes, I know I shouldn't be eating that cookie, but I've gotten good at calculating the insulin required for it. The other "unknown" items I normally don't eat are a whole other story.
Actually the problem with the 1918 flu virus was that it had unusually high mortality rates for people with strong immune systems.
The reasoning was that a lot of people died not from the infection itself, but from an *excessive immune response* (cytokine storm).
The whole swine flu paranoia is getting out of hand, especially since so far the actual severity of the swine flu is nowhere near what people are making it out to be. I now have to eat offsite at work because all of the food that I like to eat has been pulled from the cafeteria (all self-serve foods have been pulled except prepackaged items, I almost always eat a build-your-own sandwich and a cookie).
Funny thing is, as a Type I diabetic, who is at unusually high risk for problems if I catch influenza, I'm far more worried about the health effects of this damn menu change than the possibility I might catch H1N1.
1) The laptop may be permitted to enter/exit the "super high security" areas. i.e. wifi isn't used in the same place the cameras aren't allowed, but it is used elsewhere.
2) Most corporations assume WPA/WPA2 is not secure enough and treat the WiFi network as an untrusted external network (despite the WPA/WPA2) and require VPNing into the corporate intranet in addition to WPA2 security.
For a while the T650 was only available with camera - the no-camera version was released by Verizon 3 months after the camera version (which was held back 9 months so they could cripple the phone, after that contract expired I happily became an AT&T customer).
When I started my current job, I couldn't bring a phone with camera into the building. So I popped the back off, yanked the camera module, and popped it into a film canister in case I ever wanted to use it again. Never did in the end.
2 years later my company changed their policy so that cameraphones were allowed if you took a training course on proper use of a camera device within the facility. (30 minutes of training to basically say "don't use it at all" :) )