YesVideo Incorporated v. IMR16 Incorporated

I'll research this case thoroughly before drafting the overview.

Let me dig into the parties, the patents, and the docket.

Let me get the docket details, judge, and the relationship between IMR16 and iMemories.

Case Overview: YesVideo Inc. v. IMR16 Inc., No. 2:16-cv-00865 (D. Ariz.)

Parties — an operating company suing a direct competitor. YesVideo, Inc. (Santa Clara, CA, founded 1999) was, by its own account, the largest personal-media transfer company in the world: it digitized consumers' videotapes, film reels, and photos and hosted the results for online editing and sharing, operating through ~30,000 retail drop-off locations (Walgreens, Best Buy, Kodak, The UPS Store) and serving 8+ million customers (YesVideo press release, 5/22/2015). Despite appearing in the Stanford NPE Litigation Database, YesVideo is classified there as a "Product company"/practicing entity, not an NPE/PAE — it monetizes a real service, and it has continued operating since (it rebranded to Capture, a brand of YesVideo, Inc., celebrating its 24th anniversary in 2023). The defendant is listed as IMR16 Incorporated, but the record is inconsistent on the name: the same docket number appears in the Stanford NPE database and on dockets.justia.com as "YesVideo Incorporated v. iMemories Incorporated," and the NPE database's iMemories party page lists case 2:16-cv-00865 among iMemories' alleged-infringer cases. On the public record reviewed here, IMR16 and iMemories appear to be the same enterprise (the "IMR16" name is consistent with an iMemories-derived entity), but I could not verify a formal name change from a primary source. iMemories was the competing mail-in/web service for transferring and cloud-editing home movies, offering DVD output plus online sharing — i.e., a competitor-vs-competitor suit within the same consumer digitization market, not a classic PAE shakedown.

Accused technology and asserted patents. YesVideo alleged that iMemories' online editing-and-distribution service — digitizing customer home movies, enabling web-based editing, and distributing the results on physical media (DVDs) and online via social media/email — infringed its rights. The press release confirming the earlier Texas complaint identifies U.S. Patent No. 8,867,894 as the asserted patent; the Arizona docket and case record identify both 8,630,529 and 8,867,894. '894 ("Video Processing System," Fu et al., issued Oct. 21, 2014, from App. No. 13/919,825 filed June 17, 2013, assignee YesVideo, Inc., prosecuted by Fish & Richardson P.C.) claims, in one line: acquiring video data (digitizing if needed), automatically detecting scenes and generating a representative still per scene, then packaging the video, the scene index, and a software media player onto a video disc so the player can play a scene on a client computer while displaying the stills of the other scenes. The '529 patent is the direct parent of the '894 patent — the '894 front page recites that it is a "continuation of application No. 12/683,370, filed on Jan. 6, 2010, now Pat. No. 8,630,529," which itself claims the same June 16, 2000 priority date; it is thus best characterized as the parent (not merely "sibling") in the same "video processing system" continuation family (I did not independently verify the '529 title/abstract in this research). This family lineage matters: the '894 patent's specification and claims trace to a priority date of June 16, 2000, which YesVideo's GC characterized as reflecting "pioneering innovation" in online editing and distribution.

Procedural posture and venue. Filed March 30, 2016 in the U.S. District Court for the District of Arizona, Phoenix Division (the "2:" prefix), with counterclaims filed by the defendant; the case went closed, with docket activity noted only through August 10, 2016 — roughly four months of life, consistent with an early settlement or voluntary dismissal (I could not confirm the specific disposition, and I could not verify the assigned judge from the sources reviewed). The Arizona filing was immediately preceded by YesVideo, Inc. v. iMemories, Inc., No. 2:15-cv-00809 (E.D. Tex.), filed May 21, 2015 and closed March 29, 2016 — the Arizona complaint landed the very next day, strongly suggesting (inference, not confirmed) a refiling on the defendant's home turf after the Texas action terminated. Venue here matters on several axes: (1) it is an operating-company plaintiff suing its competitor, so the "NPE" framing the databases apply is misleading; (2) the sequencing shows how plaintiffs in 2015–16 could reset venue by refiling pre-TC Heartland, before the Supreme Court's May 2017 decision curtailed forum-shopping in patent cases; and (3) both parties were small, specialized consumer-services companies for which litigation cost likely drove quick resolution.

Why it is notable. Three angles stand out. First, it is an instructive counter-example in NPE datasets: Stanford's own taxonomy codes YesVideo as a product company, illustrating that "patent asserter" entries in NPE databases sweep in genuine operating-company enforcement, a pattern worth flagging for anyone using those datasets to measure PAE activity. Second, no IPR/PTAB linkage was identified — I found no inter partes review of either the '529 or '894 patent in the sources searched, and I flag that as unverified rather than confirming non-existence; the patents' very old 2000 priority date is the kind of art-rich vintage that would have made an IPR or Alice challenge attractive had the case not resolved quickly. Third, the market context: by 2016 these patents were near the end of their nominal term (a 2000-priority family would ordinarily expire around June 2020 — an inference from the asserted priority date, not a sourced holding), so the assertion window was narrow and the dispute was a short-lived market-share fight between the two leading U.S. home-movie digitization providers, one of which (YesVideo/Capture) still operates today.

I'll research this case systematically across dockets, PTAB records, and legal press.

Let me dig into specific dockets and the iMemories connection.

YesVideo, Inc. v. IMR16, Inc., No. 2:16-cv-00865 (D. Ariz.) — Chronological Development & Outcome Analysis

Analyst's note on source quality: This is a very thin docket. The case ran roughly four-and-a-half months and was closed before any substantive motion practice matured. Below I separate (a) confirmed facts from (b) items I could not verify. I have deliberately not filled the gaps with plausible-sounding detail — no judge, counsel, Markman ruling, MSJ, or trial event is asserted here, because I found no record of any. Where I infer, I label it as inference.

---

1. Predicate: the Texas suit against iMemories (2015) and the patent at issue

Before the Arizona case, YesVideo filed a materially identical infringement action in the Eastern District of Texas:

• 2015-05-21 — YesVideo, Inc. v. iMemories, Inc., No. 2:15-cv-00809 (E.D. Tex.) filed. Stanford NPE Litigation Database lists this as a separate case involving the same patent ('894) and the same accused infringer. (Stanford NPE DB, case 169192)
• 2015-05-22 — YesVideo press release announcing the E.D. Tex. filing. YesVideo stated it accused iMemories' "online video editing and distribution services" of infringing U.S. Patent No. 8,867,894, claiming a priority date of 2000-06-16 and 2014 issuance. YesVideo sought an injunction and damages. The release quotes YesVideo General Counsel Brian Knapp and touts the '894 patent as reflecting "pioneering innovation," including retail-channel distribution via Walgreens, Best Buy, Kodak, and The UPS Store. (WebWire, 2015-05-22)
• 2016-03-29 — E.D. Tex. case terminated/closed, per a litigation-analytics docket index. (ai-lab case index, 2:15-cv-00809)

The '894 patent ("Video processing system") claims methods/apparatus for acquiring video data, digitizing analog source material, generating scene indexes/stills, packaging the video with an on-disc media player, and distributing edited video — i.e., the home-movie digitization workflow both parties commercialize. (US 8,867,894)

Strategic read: The Arizona case is best understood as a re-filing against the same accused product after the Texas case was closed, not as an independent dispute. Notably, iMemories is an Arizona-based company (Scottsdale) — so the refiling venue is consistent with suing at the defendant's home forum. Caveat: the docket did not disclose a transfer order, and I found no TTAB/secretary-of-state record confirming the IMR16↔iMemories corporate relationship. Justice Dockets does list No. 2:16-cv-00865 under the party name "YesVideo Incorporated v. iMemories Incorporated," which is the strongest available indication that "IMR16, Inc." is the same enterprise or an affiliated/successor entity. (Justia Dockets, D. Ariz., NOS 830)

---

2. Filing & initial pleadings (2016)

Not verified: the specific counterclaim theories (I would expect declaratory judgment of non-infringement and/or invalidity, and possibly inequitable conduct or antitrust given the aggressive 2015 press posture — but I found no document confirming this and will not assert it). The identity of counsel for either side is also unverified; the only named attorney anywhere in the record I could source is Brian Knapp, YesVideo's General Counsel (2015 press release), who is in-house, not confirmed as litigation counsel of record.

---

3. Pre-trial motions of substance — none found

I found no record of any of the following in this docket:

• Motion to dismiss (Rule 12(b)(6)) or motion to strike counterclaims;
• Motion to transfer venue;
• Motion to stay pending IPR — see §7 below (no IPR exists to predicate a stay);
• Motion for preliminary injunction;
• Motion for summary judgment.

The docket-activity window (filing 2016-03-30 → last activity 2016-08-10) is too compressed for full motion practice, and the case terminated as "Closed" rather than proceeding to substantive adjudication. This absence is itself the key finding: the case resolved before any ruling of substance.

---

4. Claim construction (Markman) — did not occur

No Markman hearing, claim construction order, or Markman-stage briefing is discoverable. Given the four-month lifespan, the case never reached the claim-construction stage. Important context for the analyst: the '894 and '529 families were litigated without any controlling claim construction in this docket, which matters if the patents were asserted elsewhere.

---

5. Discovery milestones with strategic significance — none of record

No discovery motions (motion to compel, protective order dispute, Kewanee/Titan letter dispute, sealing motion) appear in the sourced record. Any early discovery was presumably exchanged prior to the termination, but nothing with strategic significance is documented.

---

6. Trial events, verdict, post-trial motions — none

• No trial date, trial, or verdict.
• No JMOL, motion for new trial, or fee motion under 35 U.S.C. § 285.
• No injunction issued (contrast with the 2015 Texas complaint, which sought one).

---

7. Final disposition / present posture

• Status: Closed. Docket activity last noted 2016-08-10. (Case metadata; ai-lab case index 2:16-cv-00865)
• Presumed mechanism: voluntary dismissal / settlement. This is an inference, not a confirmed fact. A case that (i) closes 4.3 months after filing, (ii) generates no motion practice or Markman activity, and (iii) is the second suit between the same two competitors over the same product, fits the profile of a negotiated resolution or a voluntarily dismissed re-filing. I found no dismissal order, settlement announcement, consent judgment, or license disclosure in press or court-opinion sources to confirm this. The docket entry that closed the case should be pulled from PACER to confirm (see §9).
• No appeal to the Federal Circuit is of record.

Note: the ai-lab index reports analytics windows ("04/05/16 – 08/10/16" and "03/30/16 – 04/05/16") alongside judge-level PO win-rate figures. These appear to be database tenure/assignment windows for the presiding judge, not docket events. I did not verify the identity of the assigned judge and therefore do not name one.

---

8. Parallel PTAB proceedings (IPR/PGR/CBM) — none found

• I found no IPR, PGR, or CBM petition involving US 8,867,894 or US 8,630,529 in PTAB sources. Searches for PTAB activity on these patents returned only unrelated material (notably Intel processor datasheets, where "IMR16" is a memory-region register name — a persistent false-positive hazard in searching this defendant's name).
• Consequently, there was no IPR-driven stay, no institution decision, and no PTAB estoppel effect to analyze.
• Caveat: PTAB search coverage for 2016-era proceedings via open web search is imperfect. A definitive negative requires a direct query of the PTAB Patent Trial and Appeal Board End-to-End (PTAB E2E) system / USPTO Patent Public Search "Proceedings" tab for both patent numbers. I recommend that confirmation step rather than treating "none found" as conclusive.

---

9. Summary timeline

---

10. Bottom line

This is a short-lived, early-terminated competitor-on-competitor suit between the two dominant players in home-movie digitization (YesVideo, the sector leader, against Arizona-based iMemories/IMR16). YesVideo sued on the '894 video-processing patent (and per the case metadata also '529), having already sued the same accused product in E.D. Tex. in 2015; the Texas case closed on 2016-03-29 and the Arizona case was filed the very next day. It was closed on or about 2016-08-10 without any Markman ruling, summary judgment, trial, verdict, or PTAB challenge — meaning the patents' validity and scope were never adjudicated in this docket.

Recommended verification steps (to convert inferences to facts)

1. PACER docket for 2:16-cv-00865 — pull the full docket sheet (likely ~20–40 entries) to identify the closing entry (voluntary dismissal under Rule 41(a) vs. stipulated dismissal vs. consent judgment), plus the answer/counterclaim pleading and any scheduling order.
2. PTAB E2E / Patent Public Search — confirm zero proceedings for 8,630,529 and 8,867,894.
3. RECAP/CourtListener — free mirror for the pleadings, which are the documents Justia's metadata references but does not display.
4. Confirm the IMR16 ↔ iMemories corporate relationship (Arizona Corporation Commission filings) — relevant to whether the Arizona filing was a tactical re-file at defendant's home venue after the Texas action ended.

I'll research plaintiff-side counsel of record for this case.

Plaintiff's counsel of record — YesVideo, Inc. v. IMR16, Inc., No. 2:16-cv-00865 (D. Ariz.)

Bottom line, stated plainly: I could not identify any attorney who appeared as counsel of record for YesVideo (plaintiff) on this docket. No publicly indexed source I could reach — Justia's D. Ariz. docket index, CourtListener/RECAP, the Stanford NPE Litigation Database, the ai-lab PACER-derived case index, firm websites, or 2015–2016 press — displays a complaint signature block, an appearance, or a pro hac vice motion for this case. I am not providing a name-and-firm list, because any such list would be fabricated. What I can give you is the one plaintiff-side individual who is verifiably connected to this litigation campaign, one unverified lead, and the precise steps to convert both into a confirmed appearance list.

---

Confirmed (but not counsel of record)

Caveat on Knapp: he is confirmed as the client-side GC directing this enforcement campaign; he is not confirmed as counsel of record in either the Texas or Arizona dockets. In-house counsel frequently appear on the pleadings, but I found no filing showing that he did here. Treat him as the client contact and the likely supervising in-house attorney, not as a verified appearance.

Unverified lead (do not rely on without checking)

The earlier research pass on this case surfaced a PTAB petition exhibit (a downloadable document in USPTO PTAB proceeding materials, ptacts.uspto.gov petition 1539645 documents) containing a law-firm attorney biography whose "representative matters" list includes "Yes Video, Inc. v. iMemories, Inc. (image transfer service) (E.D. Tex.)" — i.e., the predicate Texas action, not the Arizona case. That is strong circumstantial evidence that this attorney (or his firm) was YesVideo's outside patent litigation counsel in the Texas suit, and firms typically carry a case forward to a refiling. However:

• I could not independently verify the attorney's name, firm, or connection to the Arizona docket from a second source;
• the exhibit is a third-party document whose bio subject is identified only within the attached PDF, not in an index;
• no source ties him to No. 2:16-cv-00865.

I am therefore recording this as a research lead with a source URL, not a finding, and declining to name the individual.

What is not established

• No lead counsel, local counsel, of counsel, or pro hac vice entrant for YesVideo is identified in any source I could access.
• YesVideo's outside litigation counsel for the Arizona case specifically is unknown. (The Stanford NPE entry for YesVideo is coded "Product company"/practicing entity and contains no counsel field; Justia's index shows only "Counter_claimant / Counter_defendant / 35 U.S.C. § 271," with no attorney names. Justia Dockets, D. Ariz. NOS 830)
• I found no Law360, Reuters Legal, or other trade-press coverage of this specific case naming plaintiffs' counsel — unsurprising for a four-month, no-ruling competitor suit.

---

Why the plaintiff-side gap exists, and exactly how to close it

The record is thin for structural reasons: this is a 2016 closed D. Ariz. case, and appearance documents, complaints, and pro hac vice motions are among the least-mirrored items in free RECAP. The ai-lab index for both 2:16-cv-00865 and the Texas 2:15-cv-00809 contains an "Attorney" data field that is present but unpopulated in the retrieved page text, which tells you PACER does hold the information even though the public web does not surface it. (ai-lab, 2:16-cv-00865; ai-lab, 2:15-cv-00809)

To get plaintiff's counsel of record with certainty:

1. PACER docket for azd 2:16-cv-00865 (https://ecf.azd.uscourts.gov) — pull the complaint (Dkt. 1) and read its signature block. In a D. Ariz. patent case the filing firm is almost always on the face of the complaint; that single page yields lead counsel plus firm and office.
2. Rule 7.1 corporate disclosure statement filed by YesVideo — confirms corporate parentage and is signed by trial counsel.
3. Motions for admission pro hac vice — D. Ariz. practice is that out-of-state counsel (YesVideo is a California company; its Texas counsel would also be out-of-state) must be admitted PHV, and those motions name every attorney, firm, and bar number. This is the single most reliable document for a full counsel roster.
4. Cross-pull the E.D. Tex. docket, txed 2:15-cv-00809 — it ran a full ten months (2015-05-21 to 2016-03-29) and therefore has a far richer appearance record. The YesVideo litigation team in Texas is the best proxy for who filed in Arizona the next day, and will let you verify or discard the PTAB-exhibit lead above.
5. PTAB E2E / the cited petition exhibit — retrieve petition 1539645's documents directly and read the bio's header to name the attorney and firm; then confirm his Arizona appearance in the PACER docket.

Flag for cross-reference: this section's inability to name plaintiff's counsel is consistent with — and reinforces — the prior "Defendant representatives" section's finding that no counsel of record for either side could be sourced from open web materials. Both gaps share the same root cause (unmirrored 2016 D. Ariz. filings) and the same fix (PACER/RECAP pull). If you want, I can run a follow-up pass keyed specifically to PACER-derived docket text, the D. Ariz. PHV motions, and the E.D. Tex. appearance record for 2:15-cv-00809.

I'll research defendant-side counsel thoroughly. Let me run multiple targeted searches.

Let me pull the case index pages and try RECAP/CourtListener directly.

I hit the research-step limit before I could pull a PACER/RECAP docket sheet, so I'll report what I actually found — and, importantly, what I did not find. No tool output named any defense attorney.

Defendant's counsel of record — YesVideo, Inc. v. IMR16, Inc., No. 2:16-cv-00865 (D. Ariz.)

Bottom line, stated plainly: I could not identify any attorney who appeared as counsel of record for the defendant (IMR16, Inc. / iMemories, Inc.) on this docket. No indexed source I could reach — Justia's D. Ariz. IP docket index, the Stanford NPE Litigation Database party and case pages, or the PACER-derived ai-lab case index — displays an answer signature block, an appearance, or a pro hac vice motion naming defense counsel for this case. I am not supplying a name-and-firm list, because doing so would be fabrication. This is a documented null result with the method used and the exact steps to close the gap.

---

What the sources actually returned

Named attorney anywhere in the campaign (client-side, not counsel of record): none on the defendant side. The only attorney named anywhere in the record I could source is Brian Knapp, YesVideo's in-house General Counsel (WebWire, 2015-05-22) — and that is the plaintiff's GC, not defense counsel. I explicitly decline to name him here, because he is neither a defendant-side attorney nor confirmed as counsel of record.

---

Why the gap exists

• Unmirrored 2016 D. Ariz. filings. Appearance documents, answers/counterclaims, corporate disclosure statements, and pro hac vice motions are among the least-mirrored items in free RECAP. The ai-lab field-presence-without-content pattern confirms the information exists in PACER but is not in the open web.
• "IMR16" is a severe false-positive name. As flagged in the prior sections, "IMR16" is an Intel processor memory-region register name, so web searches on the defendant's name return Intel Atom/Celeron datasheets and unrelated Albuquerque police-monitoring reports rather than litigation records. Any open-web search keyed to "IMR16" is effectively poisoned.
• Structural inference (labeled as such, not a finding): iMemories was an Arizona-based (Scottsdale) company, and the Arizona refiling was the defendant's home forum. A D. Ariz. patent defendant of that era would typically have been represented by (a) an Arizona local-counsel firm and (b) one or more out-of-state PHV patent litigators, with in-house direction. I have no source confirming which firms those were, and I am not going to guess.

---

Exact steps to obtain the defense counsel roster (in priority order)

1. PACER docket for azd 2:16-cv-00865 (https://ecf.azd.uscourts.gov) — pull the Answer and Counterclaims and read the signature blocks. That single document names every defense attorney and firm. Also pull any motions for admission pro hac vice (D. Ariz. requires them for the out-of-state patent team) — these enumerate each attorney, firm, and bar number.
2. Cross-pull the E.D. Tex. docket, txed 2:15-cv-00809 — it ran ten months (2015-05-21 → 2016-03-29) and therefore has a fuller appearance record. The iMemories defense team in Texas is the best proxy for who appeared in Arizona the next day, and lets you verify the roster before asserting it.
3. RECAP / CourtListener (courtlistener.com) — free mirror; paste the docket number to retrieve pleadings that Justia's metadata references but does not display.
4. D. Ariz. local counsel firms — once the answer's signature block is in hand, confirm the local firm's current/former patent-litigation page; that yields the biographic "notable cases" line requested.

Cross-reference / consistency note: this null result is consistent with — and reinforces — the prior "Plaintiff representatives" section, which likewise could not source any counsel of record for YesVideo in this case. Both gaps share the same root cause (unmirrored 2016 D. Ariz. filings) and the same fix (a PACER pull of the answer/counterclaim and PHV motions). If you want, I can run a follow-up pass keyed specifically to the Answer/Counterclaim signature block, the PHV motions, and the E.D. Tex. appearance record for 2:15-cv-00809, which are the three documents most likely to name the defendant's counsel.