Deeplinks Blogs related to Digital Video
Required Reading for "User-Generated Content" Sites: Io Group v. Veoh
Legal Analysis by Fred von LohmannIn an important ruling handed down yesterday, a federal district court threw out a copyright infringement suit brought by adult video producer Io Group against Veoh, concluding that the video hosting site qualifies for the DMCA safe harbor. The ruling should be required reading for the executives of every "Web 2.0" business that relies on "user-generated content."
Veoh, like YouTube, is a streaming video site that hosts videos uploaded by users. Io Group sued Veoh in 2006 after finding clips from 10 of its copyrighted adult films on the Veoh site. So far, this is a familiar story -- user-generated content site gets sued by copyright owner for naughty uploading habits of users (see, e.g., lawsuits against MySpace, iMeem, YouTube, Redlasso, Hi5, Multiply, Stage6, MP3tunes, Scribd, Usenet.com, Bolt, and Grouper). But this is the first case to get to a final ruling, and it's a total victory for Veoh.
The key to Veoh's victory was its scrupulous attention to the DMCA safe harbors. Veoh responded to compliant DMCA takedown notices on a same-day basis, it notified users of its policies against copyright infringement, it registered a Copyright Agent with the Copyright Office, it terminated users who were repeat infringers and blocked new registrations from the same email addresses, it used hashes to stop the same infringing videos from being uploaded by other users. These efforts actually go beyond the requirements of the DMCA safe harbors, and made it clear that Veoh was serious about responding to copyright infringement notices.
This ruling provides valuable guidance to companies that host video, audio, and text files on behalf of users (see, e.g., Muxtape). Too many "Web 2.0" start-ups are careless about the requirements of the DMCA safe harbors. They don't register a Copyright Agent, or keep good records of their responses to takedown notices, or have a demonstrable policy of terminating "repeat infringers." Sure, doing this "compliance" work costs time and money. But, as the Veoh decision demonstrates, the payoff can be enormous, since copyright is almost certainly the biggest liability risk these sites face.
The ruling also debunks some of the favorite anti-safe harbor arguments bandied about by entertainment industry lawyers (and gives a boost to YouTube in its fight with Viacom). The court specifically rejects the argument that "transcoding" content to facilitate access disqualifies a service provider from the safe harbor (Veoh automatically transcodes uploaded videos into Flash). The ruling also joins other courts in concluding that, even if Veoh made money from advertising around the videos, it still qualifies for the safe harbor because it lacks the "right and ability to control" (see Section 512(c)(1)(B) of the Copyright Act) the infringing activities of its users.
While there are still plenty of unexplored legal questions surrounding the DMCA safe harbors, this ruling provides important practical guidance for companies that host user-uploaded content.
EFF Opposes MPAA's Selectable Output Control FCC Petition
Deeplink by Michael KwunPublic Knowledge, joined by EFF as well as the Consumer Federation of America, the Digital Freedom Campaign, the Media Access Project, the New America Foundation and U.S. PIRG, yesterday filed an opposition [PDF] to the MPAA's FCC petition seeking a waiver of the ban against selectable output controls (SOC) (we have an explanation of what a "selectable output control" is on our Digital Video issue page).
EFF has long opposed selectable output controls. The basic premise of those who back SOC is that content owners should be able to decide not just who can watch their content, but how they can watch it. You want to watch my new movie on that digital TV you bought a few years ago? No, sorry, I don't like your TV (perhaps because I'm afraid of the analog component inputs it uses). You want to space-shift using your Slingbox (which lacks DRM-enabling controls on its outputs)? Oh, no, I don't think that's a good idea. You were hoping to TiVo that show that's on this afternoon so that you can watch it when you get home from work? Hm, not unless you upgrade to a new TiVo, because I won't allow the signal to make it to TiVos that don't have digital outputs. You want to record that program so that you can make a fair use of an excerpt? Dear dear, we can't have that.
Seems kind of crazy, no? That's what the FCC thought, too, which was why the agency forbade use of SOC when it last addressed this issue, in 2003. The FCC concluded that multichannel video programming distributors (MVPDs - companies like cable television providers) can't "attach or embed data or information with commercial audiovisual content . . . so as to prevent its output through any analog or digital output authorized or permitted under license, law or regulation governing such covered product."
Well, the MPAA is taking another crack at the issue, asking the FCC to grant it a permanent waiver from the SOC ban, to allow it to apply SOC to recently released movies that are being distributed to homes via video on demand. The MPAA's goal here seems clear: Increase its members' control over how you choose to watch their material. As the opposition we joined puts it, "Granting the waiver would put MPAA member companies on the path to controlling what types of connections will be used by all U.S. consumers, and to profiting from that control." The opposition offers this example of what this could mean:
A model of how this would work can already be seen. Sony Pictures recently announced it will be offering its new movie, Hancock, to some Sony television owners equipped with Sony’s Internet media connection before release on DVD and other home media. However, the movie will only be available to those who own the Sony box, and will only flow over Sony’s proprietary video connection to a Sony TV. This model could easily be extended to MVPDs by leveraging SOC controls - if the Commission grants this waiver.
Right now, your consumer electronics are designed by the consumer electronics industry, which reacts to consumer market demand in choosing how to innovate. That consumer-focused approach makes sense. But if the MPAA has its way, however, we'll be well on the way to a world in which every new feature to every home theater product has to be pre-approved by the content industry.
Watching the Detectors
Deeplink by Danny O'BrienIn the absence of NBC or Microsoft coming clean about what they've done - what flags NBC sent, and what flags Microsoft obeys, we've been doing some detective work of our own -- and we'd like your help.
NBC have already said that their activation of their copy-control system was a "mistake". But when the next mistake occurs is the best chance to uncover what copy-protection Vista obeys on digital, over-the-air TV.
We're looking to obtain raw data dumps of the ATSC stream next time your copy of Vista chokes on an over-the-air digital TV feed.
(Note that we're not looking for "Can't Record Program" errors with shows received via either CableCard units or analog TV tuners -- we know that Microsoft obeys copy controls on these systems. We just want cases where over-the-air, broadcast digital (HD) TV has been affected.)
Right now, we're asking owners of the HDHomeRun to watch out for this problem. We're concentrating on this device because many Windows users run this hardware in conjunction with Vista Media Center, so they'll be able to see when the problem arises. Also, it provides only digital HD information to your PC (allowing us to eliminate any analog copy-protection systems). Finally, it's relatively easy to make a complete copy of the digital TV datastream using HDHomeRun's command line utility. Here's how:
Go into Live TV mode in VMC and choose the problem NBC channel.
Check the HDHomeRun LEDs to determine if tuner 0 or tuner 1 is
being used. The LEDs are in this order: (Power) (Ethernet, Tuner 0, Tuner1).Record a 60 second sample of the stream:
Open a cmd prompt and run:
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF save /tuner0 sample.ts(specify tuner 1 if VMC is using tuner 1)
Wait 60 seconds then press Ctrl-C to stop.
When you've got your sample, mail EFF at info@eff.org with a specification of your setup, the date, time and channel of the show. We'll get in touch.
If you know how to record the raw datastream (not just the MPEG2 data, the whole transport stream) on other hardware, let us know, and we'll add it to this blog entry.
Microsoft's Masters: Whose Rules Does Your Media Center Play By?
Deeplink by Danny O'BrienWhile its customers are still puzzling over why Vista Media Center is suddenly refusing to record over-the-air NBC digital TV, Microsoft has come out with an astounding admission, courtesy of Greg Sandoval at CNet News:
"Microsoft included technologies in Windows based on rules set forth by the (Federal Communications Commission)," a Microsoft spokeswoman wrote in an e-mail to CNET News.com. "As part of these regulations, Windows Media Center fully adheres to the flags used by broadcasters and content owners to determine how their content is distributed and consumed."
Microsoft's statement shines light on how Microsoft expects Media Center to behave. If this is the company's explanation for what users are seeing when attempting to record digital NBC broadcasts over-the-air, then Microsoft is saying Vista obeys the broadcast flag: a requirement rejected by courts and Congress.
The FCC regulation that Microsoft's spokesperson says it follows is not in force - that is, there is no legal requirement for them to follow these rules. They were rejected by the D.C. Circuit of Appeals in a case brought forward by librarians, public interest and consumer groups (including EFF and Public Knowledge). Microsoft is not complying with the FCC: it is complying with the "broadcasters and content owners" who so dearly wanted the flag in place, and failed to manage it.
Even if Microsoft somehow believes the FCC regulations still apply, they are going far beyond mere compliance. Here's the FCC's rulemaking on the flag:
In light of our decision to adopt a redistribution control scheme and to avoid any confusion, we wish to reemphasize that our action herein in no way limits or prevents consumers from making copies of digital broadcast television content.
...
[The aim of the broadcast flag] will not ... interfere with or preclude consumers from copying broadcast programming and using or redistributing it within the home or similar personal environment as consistent with copyright law.
Here is Microsoft's interpretation of an over-the-air flag:
Note how Vista forbids recording this broadcast program at all: exactly what the FCC said the flag should not do. (The broadcast flag requirements allowed you to record TV, but required the recorded material be "protected" to prevent you from redistributing it beyond approved and locked-down devices). In Microsoft's attempt to "fully adhere', they have gone beyond what the FCC ever asked them to do: they have agreed to what broadcast and content owners could only dream of passing by fiat.
Microsoft's attempt to cover its behavior by claiming compliance with the FCC neither explains nor justifies the errors that their customers are currently seeing. The company needs to spell out exactly whose rules Vista is following, and exactly how they affect their customers computers' current and future behavior.
Update: Why is NBC Flagging Digital TV Programs - and Why is Microsoft Obeying It?
Deeplink by Danny O'BrienAfter further investigation of reports of Vista refusing to record NBC, we have found at least one case where a user receiving digital TV over-the-air has been blocked from recording TV shows. Justin Sanders, who took this screenshot, says he was recording Raleigh's HDTV channel WNCN-DT1 on his Vista machine when a popup stating that "restrictions set by the broadcaster ... prohibit recording of this program" appeared.
This is significant: this is the first case we've heard of equipment voluntarily obeying broadcast flag-like restrictions on TV content digitally broadcast over-the-air.
The broadcast flag is a small piece of data broadcast alongside a digital TV program. The ability to flag broadcast content was created by the ATSC standard which governs digital TV broadcasts in the United States. By itself the broadcast flag cannot restrict use of broadcast content. Instead, its force comes from a tech mandate law - an FCC regulation - which required manufacturers of DTV-receiving devices to detect and respond to "switched on" broadcast flags. EFF and others opposed the use of the broadcast flag and fought successfully to have the FCC regulation overturned by the courts. We did that because it handed control over your hardware to a remote authority, limited your right to your fair use of media, and would have made illegal open source products like MythTV. As a result of that victory, manufacturers are not legally required to force their devices to detect and respond to the flag.
It would now appear that Microsoft has voluntarily chosen to obey such content restrictions in Vista, despite the successful work of thousands of users to defend Microsoft's right to innovate and our right to fair use. Justin was attempting to record the program on Windows Vista Ultimate using Silicon Dust's HDHomeRun external tuner, which decodes the digital TV signal, and sends it over Ethernet to many types of digital TV receivers, such as MythTV or EyeTV. As Silicon Dust says on its website, their decoder merely passes on the datastream, and does not interpret data like the broadcast flag field itself, so we know that it is Windows alone that has declared that this program should not be recorded.
To be perfectly clear: Microsoft is under no legal obligation to look for and respond in any particular way when it sees the broadcast flag being sent by NBC's digital stations. Any DTV-receiving software technology or device - like MythTV - is free to take the same stream from HDHomeRun and ignore a broadcast flag transmitted with it. In other words Microsoft did not have to build its PC to look for and refuse to record a program which has its flag turned on.
Had consumers not stood up against the FCC'S mandatory flag rule three years ago, alternatives like MythTV would no longer be available. Back then, the FCC tried to force tech companies (and open source developers) to obey the entertainment industry's remote TV control. A coalition of librarians, public interest organizations, and consumer groups successfully challenged the FCC's jurisdiction to impose such a broad regulation in Federal court. After the rightsholders lost in court, they spent millions lobbying Congress to pass a law forcing receivers to obey their command. Your letters and calls stopped that bill.
So why, after all that work, does Microsoft's software appear to honor content restriction? It's hard to say. Was it a content licensing requirement? Microsoft didn't have to do so if it just wanted its devices to decode and display over-the-air digital NBC broadcasts -- just as you don't need to sign a contract in order to decode and display the signals sent over the public airwaves into your living room. American consumers can choose what to do with their digital broadcast TV, just as they have been able with analog broadcast TV.
Perhaps it was an unintended mistake by Microsoft caused by the extensive DRM systems Vista has in place elsewhere. Perhaps Vista has been confused into thinking this open NBC datastream is a restricted CableCard feed, which can (and does) block recording. Or perhaps it it part of Vista's system for obeying CGMS-A, another copy control system that Microsoft voluntarily agreed to implement .
If it's a technical problem, Microsoft should confess, and fix it as soon as possible, before many more digital TV viewers are inconvenienced (and users switch to less encumbered devices in droves).
If, however, it is a deliberate "feature", they have some explaining to do. That would amount to putting the desires of content holders above the best interests of its customers. Even worse, it would mean they kept the deal silent while they marketed their broken hardware to those same unsuspecting customers.
We're now working with Silicon Dust to try to replicate the circumstances in which Vista failed to record, and to do further analysis. We'll keep you updated on what we learn.
Does NBC Control Your TV?
Deeplink by Danny O'BrienReports are coming in of digital video recording systems refusing to record NBC programs - both on digital cable and over-the-air transmissions.
We're still investigating whether these involved over-the-air digital TV, which would mean that NBC was the first broadcaster to attempt to revive the abandoned ATSC "broadcast flag" (as opposed to cable and analog copy control signals like CGMS-A which have been used before).
Thanks to the activism of thousands of concerned tech users, hardware and software manufacturers that handle over-the-air digital TV do not need to obey the digital TV broadcast flag. There is no "broadcast flag" copy control requirement for these tuners, since the courts overturned the FCC's plans to enforce it in 2005; and despite the entertainment industry's bluster, it does not look like a broadcast flag law will be passed before the digital switch-over next year.
However, hardware and software could voluntarily obey the flag. Rightsholders are almost certainly lobbying behind the scenes to get tech companies to agree to obey copy controls for over-the-air digital TV. Software like Vista is already designed to comply with rightsholder restrictions when working with standards like CableCard which contractually require copy protection. Turning the same restrictions on when a message is received from an over-the-air tuner is just a small coding step away.
At this point no one knows which tech companies have sold out their users in this way. For understandable reasons, manufacturers keep their compliance details quiet -- which is why customers are so angry when they encounter it. ATI has previously reported that they will support the broadcast flag, but this news was buried in a driver change log.
Companies that implement the over-the-air digital broadcast flag are under no obligation, contractually or due to FCC regulation, to do so. They have a choice. And so do their customers.
Millions of dollars will be spent in the next few months as America switches to digital television. Prosumers like those at "The Green Button" are often the first to be bitten by TV's copy restrictions, but they will not be the last.
Perhaps electronics magazines and online reviews should look into exactly how digital TV equipment is dealing with the rightsholders' demands, and publicize which companies still obey the redundant and user-unfriendly broadcast flag -- and which still listen to their customers.
Adobe Pushes DRM for Flash
Deeplink by seth schoenThe immense popularity of sites like YouTube has unexpectedly turned Flash Video (FLV) into one of the de facto standards for Internet video. The proliferation of sites using FLV has been a boon for remix culture, as creators made their own versions of posted videos. And thus far there has been no widespread DRM standard for Flash or Flash Video formats; indeed, most sites that use these formats simply serve standalone, unencrypted files via ordinary web servers.
Now Adobe, which controls Flash and Flash Video, is trying to change that with the introduction of DRM restrictions in version 9 of its Flash Player and version 3 of its Flash Media Server software. Instead of an ordinary web download, these programs can use a proprietary, secret Adobe protocol to talk to each other, encrypting the communication and locking out non-Adobe software players and video tools. We imagine that Adobe has no illusions that this will stop copyright infringement -- any more than dozens of other DRM systems have done so -- but the introduction of encryption does give Adobe and its customers a powerful new legal weapon against competitors and ordinary users through the Digital Millennium Copyright Act (DMCA).
Recall that the DMCA sets out a blanket ban on tools that help "circumvent" any DRM system (as well as the act of circumvention itself). When Flash Video files are simply hosted on a web site with no encryption, it's unlikely that tools to download, edit, or remix them are illegal. But when encryption enters the picture, entertainment companies argue that fair use is no excuse; Adobe, or customers using Flash Media Server 3, can try to shut down users who break the encryption without having to prove that the users are doing anything copyright-infringing. Even if users aren't targeted directly, technology developers may be threatened and the technologies the users need driven underground.
Users may also have to upgrade their Flash Player software (and open source alternatives like Gnash, which has been making rapid progress, may be unable to play the encrypted streams at all). Third-party software that can download Flash Video, like the most recent RealPlayer, will also break. But Adobe now has an incentive to push the use of DRM: it's only available to sites that use Flash Media Server 3 software, which starts at over $4,000 (with extra fees depending on the number of simultaneous streams).
Furthermore, the prospect of widespread adoption of DRM restrictions on Flash threatens to squash a growing tradition of expressive fair use of online video -- a practice effectively in its infancy that, left unfettered, would be a dynamic solution to our failing effort to teach media literacy. Before we understand how to read media messages, we must first learn how to speak their language -- and we learn that language by playing with and remixing the efforts of others. DRM, by restricting the remixing of Flash videos, stands to bankrupt a rich store of educational value by foreclosing the ability of students and teachers to "echo others" by remixing videos posted online.
Take the example of "A Vision of Students Today" vs. "(Re)Visions of Students Today". The first "Vision" YouTube video is an artful critique of higher education's failure to come up with new models of instruction that engage the modern student; the second "(Re)Vision" YouTube video is an incisive observation of higher education's crisis in diversity (summarily expressed by the lack of diversity in the original "Vision" video). The original and the remix support each other to instruct with an influence above and beyond the power of either video alone.
Outside the halls of academia, we can see that the ability to openly download and remix video is part of a new ecosystem of amateur entertainment -- watch Drama Prairie Dog and its countless responses:
- "Dramatic Prairie Dog vs. Kung Fu Baby (Best Remix Ever)"
- "Hollywood Zombies Dramatic Prarire Dog"
- "Dramatic Look Bond Remix"
- Drama Prairie Dog - Zoolander
- "Drama Prairie Dog -- Kill Bill"
- (an obligatory Star Wars-related remix) "Darthmatic Chipmunk"
As we noted above, remixers who find and use tools that break the Flash Video encryption could be sued, even if their transformative creations would otherwise have been fair use.
Finally, there's a classic suite of arguments against DRM that will be as true for online video as they were for music. DRM doesn't move additional product. DRM is grief for honest end-users. And there's no reason to imagine that new DRM systems will stop copyright infringement any more effectively than previous systems.
2008: DRM continues to punish paying customers
Deeplink by seth schoenJust three days into the new year, we have another example of DRM punishing paying customers, rather than "pirates." Netflix subscriber Davis Freeberg ran headlong into an incompatibility between Microsoft DRM and ... Microsoft DRM.
The trouble all started when Freeberg bought a new monitor for his Vista computer. When he decided to watch streaming movies from Netflix, Netflix documentation warned him that the recommended means of fixing a problem with DRM-restricted Netflix programming "may remove licenses to other content using Microsoft DRM" -- including, in particular, restricted programming he had already purchased through Amazon Unbox. Trying to resolve this problem just got Freeberg a tech-support runaround, with each company involved pointing the finger at another.
Tech support problems are not unfamiliar to PC users, but where did this problem come from? Freeberg was just trying to use a new monitor with his computer; his reward, apparently, was broken DRM software, which couldn't be sure the new monitor met movie studios' arbitrary requirements (or perhaps just couldn't be sure whether it could be sure). Furthermore, the DRM industry -- which has already spent countless engineer-hours making "approved" and "licensed" products (seemingly at the expense of "compatible" and "interoperable" devices) -- couldn't even offer Freeberg a clear path out of this jam.
Is this mess stopping copyright infringement? Nope -- it's still easy to copy media and easy to find unauthorized copies. In fact, one commenter points out that the easiest "fix" for Freeberg's trouble appears to be downloading the movie from an unauthorized torrent tracker.
Freeberg's conundrum is likely the product of the Protected Media Path (PMP) (mis)features that have been added to Microsoft's Vista operating system. Thanks to PMP, Vista computers can now "audit" the video outputs, supposedly to ensure that only "authorized" (aka DRM-laden) video boards and monitors can receive Hollywood content. Unfortunately, these kinds of (mis)features generally (1) don't stop pirates and (2) result in compatibility headaches for paying customers.
Flags through Senate Committee Stage
Deeplink by Danny O'BrienWhile the Senate floor was
amendment, the Senate Commerce committee was letting another two—the broadcast flag and audio flag—slip
by. Senator Sununu spoke strongly against the flags, noting that we don't need technology mandates that inject federal bureaucrats into technology design decisions, but chose ultimately to withdraw his amendments to remove the audio and broadcast flags from the larger telecom package. But he said he may
propose to remove them again when—or if—the bill reaches the Senate
floor.
The bill still has
another day of mark-up in committee, focusing on the controversial
network neutrality proposals. But they won't be revisiting the flags. So, if the committee ultimately passes a telecom reform bill, the flags will be in it.
The good news for now is that the bill's chief sponsor, Senator Ted Stevens (R-AK), is
having second thoughts about the wisdom of sending the bill to the floor for a vote. "We have to get 60 votes, we don't have them right now," he told reporters after the mark-up hearing (60 votes are needed to defeat a filibuster in the Senate).
Meanwhile, in the House, the matching committee
the broadcast flag and audio flag. If
the flags get past the Senate, they'll have to pass muster in the House, too.
The MPAA and the RIAA sat on one side of the argument; satellite radio makers,
broadcasters, consumer electronics manufacturers and public interest groups on
the other. The best line? Gary Shapiro of the Consumer Electronics
Association:
"We have to stop measuring creativity by the financial interests of ten
companies."
Let your senators know what these technology mandates will do to the
creativity of technologists, tinkerers, and the rest of us.
tell them to vote against the flags, and stand against S.2686, the Stevens
telecom bill.
UPDATE: The Senate committee also apparently added a web labeling provision to the telecom bill during today's mark-up session. According to news reports, this provision would regulate the inclusion of sexually explicit material on web pages through restrictions on top-level homepages and labeling requirements on other pages.
Telecom Log Jam - Broadcast Flag Decision Postponed
Deeplink by Danny O'BrienAs if it wasn't convoluted enough, the 159-page Stevens telecoms reform bill -- which now includes broadcast and audio flag provisions -- got buried under an avalanche of 200 proposed amendments today. At the markup committee meeting, senators became quickly mired in discussions over a tiny fraction of these proposals. The remainder of the amendments -- including Senator Sununu's proposal to throw out the flags wholesale -- were postponed until next Tuesday.
It's certainly getting messy in there. With Senator McCain proposing that the broadcast flag be tied to broadcaster support for a la carte cable channels, and heavyweights like Intel balking at the current language, even the flag's proponents may be having second thoughts about entering this cauldron of competing special interests.
If you have a senator on the Commerce committee, keep calling or writing to tell them to do the sensible thing, and snip out the extraneous flags from an already overcomplex bill.
