4K, at 1.79 Mbps.
The eye cannot tell.
Slime-Boy: let me explain what that number means — gently ▾
“4K at 1.79 Mbps” — what does that mean?
- 4K = ultra-sharp video filling your TV screen (3840 × 2160 pixels, four times Full HD)
- Mbps = how much data flows per second. Bigger number = thicker water pipe
- Normal 4K video needs a thick pipe (25 – 50 Mbps) — Wi-Fi or fiber territory
- But JAVATEL's NormAV1 flows 4K through a tiny 1.79 Mbps pipe!
- That's roughly 1/14 to 1/28 of normal — one LTE 4G line is enough
How? Math (the commutator norm) finds where your eye is paying attention — and where it isn't — then sends bits only where they matter. We'll explain more further down the page!
Live switch demo → 30-day trial → Latest news →
Patents pending: JP 2026-046898 / 046609 / 046620 / 046625 · Paper: Commutator Norm as a Continuous Criterion for GOP Safety and Perceptual Quality Redistribution in Video Encoding — IEEE TCSVT v8 submission
SlimeNENC — Legacy modernization
BLACKBOX — bring it on.
COBOL modernization does not need a “understand the business logic” phase.
Treat the source itself as the specification, and transpile bit-exactly under a deterministic rule base. That’s all.
Discard meaning extraction
The industry’s classic failure — have BAs reverse-engineer 30 years of implicit specifications — does not scale. CBA, IRS, TSB Bank failed at the hundred-million-dollar mark trying to “understand first, migrate later.” Treat the source as the spec; preserve the bytes.
We do not violate “No Silver Bullet”
Brooks (1986) says essential complexity cannot be removed. The industry’s add-on premise — “therefore re-expression by humans is required” — is not in Brooks. Preserve-and-transport without re-expression is the reuse / off-the-shelf lineage Brooks 1995 acknowledged, isomorphic to virtualization, containers, WASM.
Meaning is algebra, not probability
GitHub Copilot for COBOL / IBM watsonx Code Assistant for Z / AWS Q Code Transformation operate via probabilistic inference (LLMs) — same input, different output every time, bit-exact provably impossible. SlimeNENC captures meaning algebraically in Slot IR (Core64+Ext32 fixed bits); no LLM at runtime; SHA-256 identical output every run.
Interrupt-less polling loops surfaced
CALL STIMER / EXEC CICS WAIT / DB2 cursors / S/370 channel programs carry implicit timing contracts. SlimeNENC’s S5 Acceptor auto-detects and audit-marks every call site. SlimeASM-rev / SlimeELF-rev / SlimePE-rev recover structured C from the binary layer (ELF 25/25 + PE 21/21 byte-exact validated).
Measured (updated 2026-05-20 PM):
[byte-exact axis] NIST CCVS85 + Portfolio Mgmt 501 / 501 = 100.000% (program-level bit-exact, full audit, no sampling) + 11 external corpora 4,595 / 4,595 = 100.000% (919 files × 5 target languages byte-exact, including ACAS 3.01.07 production ~100K LOC GnuCOBOL, third-party reproducible inside a WASI sandbox).
[new axis: emit success] US Federal Medicare Pricer Suite, 7 systems, 675 / 675 = 100.000%
(135 standalone programs × 5 target languages, 12.5 MB COBOL, via SlimeCOBOL-MF, measured 2026-05-20 PM. “Emit success” = Java/Rust/C#/Kotlin/Go skeleton generated + dialect auto-detected + fields inferred. Behavioural byte-exact (output-level match against CMS's hand-converted Java) is being verified incrementally in the next phase).
A rare implementation that can honestly say “100% is a measured count, not a probability.”
SlimeCOBOL product → Japanese mainframe PoC → Legacy conversion service →
Four product pillars — led by shortest market reach
PSDP — Same-Language Parallelization
For financial trading, regulated industries (J-SOX/SEC), cloud cost reduction, HFT, scientific computing, ML inference. Hash-chained audit trail, 378 runs all bit-exact (100% determinism), 90/90 fault-injection rollbacks.
Slime-Boy: 4× speedup without changing my source? I don't believe it... ▾
“No source rewrites” — how is that possible?
- Your
OrderBatch.javastays byte-for-byte identical (git diffshows nothing) - At build time, PSDP reads the bytecode and injects a parallel version alongside (Java agent / .NET profiler / Rust proc-macro)
- 4 cores → parallel path. 1 core → sequential. No dispatch code on your side
- PSDP’s proprietary mathematical synchronization mechanism excludes the “parallel changes my answer” failure mode by theory (details in patent filings; redacted here)
- Every production run, bench compares sha256 of sequential vs parallel; mismatch → instant rollback
Result: not one line of your code touched / just rebuild / output bit-identical / 4× on 4 cores (measured 2.97–4.23×). For audit, “zero code change” is the selling point. PSDP overview →
PSDP overview → SlimeNENC customers: PSDP tool deployment is free; PSDP runtime is 2%/year of conversion cost.
NormH.264 / NormAV1 — 4K to 1/4
Commutator norm finds where the eye looks, then takes bits from flat regions and gives them to texture and edges. NormH.264 is production; NormAV1 is a research preview.
Legacy → Java bit-exact
COBOL / JCL / MUMPS / PL/I / RPG / FORTRAN / Natural / HLASM+MASM (SlimeASM) / Linux ELF reverse (SlimeELF-rev) / Windows PE reverse (SlimePE-rev). Shared S2-S5 / S7-S9 backbone, 100% pass on NIST CCVS85's 501 programs, hash-chained audit + 100.000% determinism bound. Source-free output. See the price table.
Sub-second WebRTC + 48h time-shift
JAVATEL OEM of Unreal Media Streaming. Plugin-free browser end-to-end playback under 1 second, 48-hour rolling archive per channel, absolute time seek. Modern REST API + React management console.
Evidence — measurements
| H.264 plain | 25 – 50 Mbps |
| AV1 plain (AOM) | 12 – 15 Mbps |
| NormH.264 | 6 – 8 Mbps |
| NormAV1 | 1.79 Mbps |
CityHall 3840×2160 60fps · transcoded from AV1 source · VMAF 84.36 mean / 79.22 min · perceptual limit 0.97 Mbps at VMAF 75.99
Verified across 3 arch classes: Apple A15 (iPhone 13, ARM 2C) / Intel i5-1145G7 (Tiger Lake x86 mobile 2C) / AMD Ryzen 5 GHz (x86 desktop) — all play 4K 30 fps smoothly
- Commutator norm &lVert;A·B − B·A&rVert;F = perceptual saliency
- Bit redistribution per-block QP offset, 8×8 granularity
- Codec-native dispatch libx264 ROI + SVT-AV1 roi-map (no new decoder)
- Source-aware already-AV1 input compresses 8.43× further
NormAV1 sweep demo · dav1d WASM live demo · 2-core verified on real devices
Latest news
All news →- NIST CCVS85 fully cleared — 10 external corpora, 782 files × 5 languages = 3,910 / 3,910 byte-exact (100.000%). FIPS 21-3 federal COBOL validation 459 files + AWS CICS/VSAM CardDemo + IBM CICS Banking + Rocket BankDemo + sentientsergio portfolio + mainframed DOGECICS + real-world defects + tutorial sets, third-party reproducible inside the WASI sandbox.
- SIer / Reseller Partner Programme launched — online application open at /partners/register/.
- PSDP 4-way pricing finalised — see the price table.
- PSDP released as an independent product line — same-language parallelization, separated from SlimeNENC family.
- SlimeASM released — z/Architecture HLASM + x64 MASM → Java bit-exact.
- NormH.264 v0.4.2 released — Trial Signature Mode bundled; AV1 moved to NormAV1.
- SlimeNatural released — Software AG Natural / ADABAS → Java + PostgreSQL bit-exact.
- SlimeFORTRAN 9-language multi-target completed.
JAVATEL Inc. has delivered surveillance camera systems, video management, and media streaming across Japan since 1997. Headquartered in Nishinomiya, Hyōgo. The Video Intelligence in our company logo is not a recent trend — it is the direction we have walked for more than 29 years.
Partners: Genetec (longest-tenured authorized partner in Japan) / XEOMA AI NVR / Planet Networks (Taiwan) ·
Why Javatel · Partners · Contact