About

I know how synthetic speech fails.

My name is Tym Rabchuk and I'm building Yazyk. What follows is my working history rather than a mission statement: on a product that takes a room's audio and is built out of the same tools as a convincing fake, who built it is part of what you are deciding about.

Built for believers, by a believer.

Years of watching these systems break.

The demo is never the hard part. Real input is.

The tools behind Yazyk are the tools I already work in every day:

Text-to-speech benchmarking. Measuring what a synthesis engine actually does with real speech: how far behind it runs, where it stutters, where it seams two utterances together badly.
Voice cloning. Building a speaker's voice from a short reference and learning, repeatedly, that the clone can never be better than the audio it was taken from.
Lip sync and dubbing. Putting a translated performance back onto a face and a timeline.
Face swap and generative video. The deepfake side of this field, run locally on my own hardware rather than through somebody's API.
Voice isolation. Pulling a single speaker out of music, room noise, and a full mix, which is the same problem a live sound desk hands you on the day.

Every one of those systems looks flawless in a curated clip. Finding out where each one falls apart is most of the actual work, and it is the part nobody puts in a demo.

Why it stays on your machine

8 years

I spent eight years breaking into Fortune 500 companies.

That was the job: get in, reach the data nobody thought was reachable, and write up how. You learn quickly that the weak point is almost never the lock everyone is looking at. It is the convenient thing somebody added later, and the copy of your data sitting somewhere you forgot to ask about.

So Yazyk runs the pipeline on the computer in your room, and the Privacy page names what leaves it: the speech services, and the relay behind Internet listeners. I keep no copy of it. Not because it is a feature, but because I have spent a career being the person who goes looking for the copy you forgot about.

Voice cloning: the feed decides.

Yazyk can speak the translation in the speaker's own voice, built from a short reference. Whether that sounds better than a stock voice depends entirely on the feed it is taken from.

The limit

A clone cannot beat its source

Cloning reproduces whatever the reference contains, including room reflections and mix noise. From a room microphone, a good stock voice sounds better than the clone.

The gate

Off until each service is confirmed

Voice cloning requires an isolated speaker feed: one close microphone, with no music, room microphones, congregation, reverb, or other speakers. If that feed is unavailable, leave cloning off and use the stock voice. Even when an eligible speaker is selected, Yazyk will not capture a reference until the operator confirms that feed for the service.

The likeness

Someone's voice is theirs

A cloned voice is a copy of a real person. It is built for that event from a reference you supply, and the software deletes the vendor side copy when the run shuts down cleanly. A crash, a slow vendor response at shutdown, or a failed delete can still leave one behind, so the runbook carries a manual check.

Rules I would want applied to me.

Four commitments

A voice is only cloned from a reference the speaker knowingly gave. Yazyk asks that of you; it cannot enforce it for you.
The audio pipeline runs on the computer in your booth, and the Privacy page names what leaves it.
A failure Yazyk recognises appears on the receipt, in the same place as what worked. It recognises a silent input, a dead output, a run that produced no audio, a busy device, and a clone that failed. A fault outside that list is one the receipt will not name, and that list grows every time a real event finds a new one.
Claims on this site say what is running today and what is not.

The last one is why this page tells you that voice capture fails closed without a confirmed isolated feed, why the usage report sent when a run ends is not retried if the network is down at that moment, and why the vendor side voice can still outlive a run that crashed. Those are the current state, not the intended one.

A small operation, named plainly.

Yazyk is built and operated by Tymeless Technologies LLC. The honest description of the product today is early software running real events and reporting what it measured of them.

Talk about your event