<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Formavide</title>
    <description>The latest articles on DEV Community by Formavide (@formavide).</description>
    <link>https://dev.to/formavide</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209754%2F6fb10544-99db-416b-ba31-aae62a6913b6.png</url>
      <title>DEV Community: Formavide</title>
      <link>https://dev.to/formavide</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/formavide"/>
    <language>en</language>
    <item>
      <title>Why Your DIY Acapella Sounds Shaky (and What Actually Helps)</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:12:13 +0000</pubDate>
      <link>https://dev.to/formavide/why-your-diy-acapella-sounds-shaky-and-what-actually-helps-4l8h</link>
      <guid>https://dev.to/formavide/why-your-diy-acapella-sounds-shaky-and-what-actually-helps-4l8h</guid>
      <description>&lt;p&gt;You split the song, solo the vocal, put headphones on — and instead of a clean acapella you get a voice that shimmers on every sustained note, hi-hats rattling somewhere inside it, breaths that smear instead of landing. Nothing crashed, no error message; the result is just... shaky. That shakiness has specific causes, and they're not equally fixable. Here's the honest breakdown: which part is physics, which part is your source file, and which fix actually moves the needle.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-diy-acapellas-sound-shaky" rel="noopener noreferrer"&gt;Split a song in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;2-stem and 4-stem AI separation that runs on your device. Free daily quota, no sign-up to try.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Three problems people call "shaky"
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Bleed&lt;/strong&gt; — other instruments faintly audible inside the vocal stem: hi-hats riding every consonant, snare hits ghosting through the verses&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Warble&lt;/strong&gt; — the vocal shimmers or wobbles on sustained notes, the infamous "underwater" sound. This is the one that makes a stem unusable for release work&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Smeared breaths and sibilance&lt;/strong&gt; — S sounds and breaths swirl or blur instead of staying crisp. Usually the mildest of the three&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All three trace back to how these models actually work — but your source file and your engine choice decide how far each one goes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the model is actually doing
&lt;/h2&gt;

&lt;p&gt;Separation isn't subtraction and it isn't magic. The song gets chopped into thousands of time-frequency tiles — a spectrogram — and a neural network predicts, tile by tile, how much of each tile belongs to the vocal. A mask keeps that share; the rest stays with the instrumental.&lt;/p&gt;

&lt;p&gt;Two failure modes follow directly from that design. Where the guess is wrong, tiles from other instruments slip through the mask — that's bleed. Where the model hedges, the mask half-opens and closes between neighboring tiles, and that flickering boundary is the warble you hear. In our implementation the instrumental stem usually comes out cleaner than the vocal stem for exactly this reason: a few mis-guessed tiles disappear into the wall of instruments, while a vocal stem exposes every one of them.&lt;/p&gt;

&lt;p&gt;There's a phase footnote worth knowing: the output reuses the original recording's phase information. Unevenly masked energy leaves faint ripples in the waveform — which is why even a "clean" stem can feel slightly softer than the same vocal inside the full mix. That softening is normal across every mask-based separator.&lt;/p&gt;

&lt;h2&gt;
  
  
  The biggest lever is the file you put in
&lt;/h2&gt;

&lt;p&gt;A 128 kbps MP3 has already thrown away its highest frequencies and most of its fine detail — permanently. The separator still runs, but it's reconstructing from mush: warble deepens and cymbal bleed gets louder, because the model is guessing over a blurred spectrogram.&lt;/p&gt;

&lt;p&gt;In our tests, the jump from a low-bitrate rip to a 320 kbps or lossless file is the single most audible improvement you can make — bigger than any setting inside the tool. Sparse, well-recorded material (acoustic takes, older masters) separates remarkably cleanly; a loudness-war modern pop master, where the vocal is glued into a wall of compressed instruments, is where every model earns its keep or falls apart.&lt;/p&gt;

&lt;p&gt;Before you blame the tool, run the 30-second pre-flight:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Check the source bitrate — file properties on Windows, Get Info on a Mac. Below 192 kbps, expect artifacts no matter what you use&lt;/li&gt;
&lt;li&gt;320 kbps MP3 is a reasonable floor; FLAC or WAV if you have it. YouTube rips are the worst common source — usually 128–160 kbps with a low-pass filter on top&lt;/li&gt;
&lt;li&gt;Stuck with a marginal source anyway? Plan around it: the instrumental stem hides the model's small mistakes much better than the vocal stem does&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Engine choice matters — less than forums claim
&lt;/h2&gt;

&lt;p&gt;The fast 2-stem split handles most jobs: karaoke tracks, practice-along, pulling a vocal for sampling — a typical song lands in under a minute. The 4-stem engine keeps more detail and lets you mute drums, bass and other separately, which matters for remix work; in our browser implementation it trades speed for that detail and wants a desktop Chrome or Edge with WebGPU. &lt;a href="https://formavide.com/blog/spleeter-vs-demucs?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-diy-acapellas-sound-shaky" rel="noopener noreferrer"&gt;How the two engines actually differ&lt;/a&gt; comes down to model size and what each one was trained to preserve.&lt;/p&gt;

&lt;p&gt;What no engine fixes: vocals drenched in reverb (the reverb tail belongs half to the voice, half to the room — the model makes an arbitrary call, and you hear the seam), stacked ad-libs and doubles, and vocals mixed so low they're part of the fabric. Those sources sound shaky everywhere. Any tool claiming perfection on them is marketing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Repairing what can be repaired
&lt;/h2&gt;

&lt;p&gt;Small EQ cuts beat re-running the whole job. Cymbal bleed usually lives in a narrow high band — a gentle dip there cleans the stem without touching the voice. Light broadband denoising can settle warble on sustained notes, at the cost of some air. Deep, structural warble can't be repaired; the fix is a better source, not more processing — which is why producers who need a pristine &lt;a href="https://formavide.com/tools/acapella-extractor?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-diy-acapellas-sound-shaky" rel="noopener noreferrer"&gt;acapella&lt;/a&gt; obsess over the source file before the model ever runs.&lt;/p&gt;

&lt;p&gt;Calibrate to the use, too. A stem backing a karaoke night loses its occasional ghosts in the sound of a room singing — &lt;a href="https://formavide.com/tools/karaoke-track-maker?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-diy-acapellas-sound-shaky" rel="noopener noreferrer"&gt;turn the instrumental into a karaoke track&lt;/a&gt; and let the crowd handle the rest. A stem destined for a release gets held to the standard above.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Is the shakiness the tool's fault?&lt;/strong&gt; Mostly no — it's frequency masking plus your source file. Every separator shares the failure modes above; tools differ at the margins&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does lossless really beat 320 kbps MP3?&lt;/strong&gt; Slightly — cleaner high end, a touch less bleed. The dramatic jump is from sub-192 kbps rips to anything 256 or better&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2-stem or 4-stem?&lt;/strong&gt; 2-stem for karaoke, practice and simple vocal pulls. 4-stem for remix work or dense mixes — budget the extra time&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can artifacts be removed afterwards?&lt;/strong&gt; Narrow-band bleed: usually, with EQ. Light warble: partly, with gentle denoise. Heavy warble: no — re-split from a better source&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Why did the same song split better on another site?&lt;/strong&gt; Before crediting the engine, compare the source files — different uploads carry different bitrates, and source quality explains most "it worked better there" stories&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-diy-acapellas-sound-shaky" rel="noopener noreferrer"&gt;Split a song in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;2-stem and 4-stem AI separation that runs on your device. Free daily quota, no sign-up to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>machinelearning</category>
      <category>ai</category>
      <category>tutorial</category>
      <category>music</category>
    </item>
    <item>
      <title>What Is an NCM File? How to Open It on Any Device</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Fri, 13 Nov 2026 04:00:45 +0000</pubDate>
      <link>https://dev.to/formavide/what-is-an-ncm-file-how-to-open-it-on-any-device-5h6o</link>
      <guid>https://dev.to/formavide/what-is-an-ncm-file-how-to-open-it-on-any-device-5h6o</guid>
      <description>&lt;p&gt;Every music player refuses the file — except exactly one app. That's the .ncm experience: NetEase Cloud Music hands you a song that behaves like it's corrupted everywhere else. It isn't corrupted, it's locked, and the lock is thinner than you'd expect. This is the container pulled apart: what's actually inside an NCM file, why opening it costs zero audio quality, and how to do it on any device without the file ever leaving your machine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/tools/ncm-to-mp3?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=what-is-ncm-file" rel="noopener noreferrer"&gt;Unlock NCM files in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Decryption runs locally in JavaScript — MP3/FLAC out bit-for-bit, metadata and cover art kept.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  NCM is a lock, not an audio format
&lt;/h2&gt;

&lt;p&gt;The confusing part — and the key to everything — is that &lt;strong&gt;NCM is not an audio format&lt;/strong&gt;. It's a container NetEase Cloud Music wraps downloaded songs in. Inside sits a completely ordinary music file: an MP3, a FLAC, sometimes an M4A. The wrapper never touches the audio; it only scrambles who's allowed to read it. That's why every attempt to "play" the file elsewhere fails so strangely — players hit a wall of encrypted bytes where they expect an MP3 header. The song isn't damaged; it's locked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inside the container
&lt;/h2&gt;

&lt;p&gt;After a short magic header identifying the format, an NCM file carries four things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Key material&lt;/strong&gt; — the data needed to recover the file's AES key, itself hidden under a well-known obfuscation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Metadata as JSON&lt;/strong&gt; — title, artist, album and the music IDs, stored as readable fields once decrypted&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cover art&lt;/strong&gt; — the embedded album image, extracted alongside the audio&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The audio payload&lt;/strong&gt; — a standard, unmodified music stream: MP3s keep their ID3 tags, FLACs keep their lossless data&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why opening one is lossless by nature
&lt;/h2&gt;

&lt;p&gt;Because the payload is never re-encoded, unlocking costs nothing: a 320 kbps MP3 comes out as the same 320 kbps MP3, and a lossless FLAC as the identical FLAC. Any tool that "converts" NCM files by decoding and re-encoding is damaging your music for no reason — the lock was never part of the audio.&lt;/p&gt;

&lt;h2&gt;
  
  
  Opening one on any device
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Get the file out of the app's download folder — on desktop it lands next to the cache; on mobile it's usually in the app's own directory&lt;/li&gt;
&lt;li&gt;Open an NCM-aware unlocker. The &lt;a href="https://formavide.com/tools/ncm-to-mp3?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=what-is-ncm-file" rel="noopener noreferrer"&gt;browser-based one we build&lt;/a&gt; runs the entire decryption locally in JavaScript, so the file never leaves the device&lt;/li&gt;
&lt;li&gt;Drop the file in. The tool recovers the key, reverses the encryption, and reads the true format from the audio's magic bytes — ID3 → MP3, fLaC → FLAC, and so on&lt;/li&gt;
&lt;li&gt;Save the unlocked MP3/FLAC with title, artist, album and cover art intact. It now plays in any player, car stereo, DJ software or editor&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why don't players just support NCM?
&lt;/h2&gt;

&lt;p&gt;Supporting it would mean implementing the lock, not the music — and the lock exists specifically to keep playback inside the licensed app, so players have no incentive to bless one store's wrapper. Worth knowing: NCM is technically an obfuscation rather than sanctioned DRM, which is exactly why independent unlockers are possible at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  The wider family
&lt;/h2&gt;

&lt;p&gt;NCM isn't alone. QQ Music wraps songs in QMC/MFLAC/MGG, Kugou in KGM/KGG, Kuwo in VPR — same concept, different locks, and the same local approach opens the older generations. The honest edge of the map: the newest schemes (Kugou's KGG, QQ Music's musicex) fetch keys from a server at play time and can't be cracked offline — no local tool handles those, ours included. &lt;a href="https://formavide.com/tools/ncm-to-mp3?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=what-is-ncm-file" rel="noopener noreferrer"&gt;Our converter covers NCM, QMC, KGM and more&lt;/a&gt; under the same no-upload, no-re-encode rule.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Does the quality drop?&lt;/strong&gt; No — the audio payload is never re-encoded, so a 320 kbps MP3 stays a 320 kbps MP3 and FLAC comes out bit-identical&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Are tags and cover art kept?&lt;/strong&gt; Yes — title, artist and album come out of the container's JSON metadata, the album image is extracted alongside, and MP3s keep their ID3 tags&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is my file uploaded?&lt;/strong&gt; No — the entire decryption runs in JavaScript on your device&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What about QMC or KGM files?&lt;/strong&gt; Same concept, same tool: QQ Music's and Kugou's older wrappers open the same way. The newest server-key schemes can't be opened offline, and no honest tool claims otherwise&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is this legit?&lt;/strong&gt; Unlocking music you legitimately obtained — playing your own library on devices and in software the store's player doesn't reach — is the intended use. Uploading, sharing or monetizing the decrypted audio is another thing entirely; the recordings still belong to their rights holders&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/tools/ncm-to-mp3?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=what-is-ncm-file" rel="noopener noreferrer"&gt;Unlock NCM files in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Decryption runs locally in JavaScript. Bit-for-bit output, nothing uploaded.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>webdev</category>
      <category>music</category>
      <category>beginners</category>
    </item>
    <item>
      <title>How to Make a Karaoke Track from Any Song</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Fri, 13 Nov 2026 03:24:30 +0000</pubDate>
      <link>https://dev.to/formavide/how-to-make-a-karaoke-track-from-any-song-3cce</link>
      <guid>https://dev.to/formavide/how-to-make-a-karaoke-track-from-any-song-3cce</guid>
      <description>&lt;p&gt;Friday night, living room, and the only thing missing is the version of the song without the singer in it. Making a karaoke track used to mean hunting for an official instrumental that usually doesn't exist — or muting one channel of a stereo file and hoping. AI stem separation replaced both hacks, and it now runs in a browser tab without the song going anywhere near a server. Here's the honest version: what separation can and can't do, which engine fits your night, and the whole flow in four steps.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-make-a-karaoke-track" rel="noopener noreferrer"&gt;Split a song in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI vocal removal that runs locally — instrumental and vocal in one pass. Free daily quota, no sign-up to start.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Three jobs, three quality bars
&lt;/h2&gt;

&lt;p&gt;"I need the vocals gone" is three very different jobs, and each judges the result differently:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The host&lt;/strong&gt; — Friday night, people singing over the speakers. The instrumental only has to hold up behind live voices in a room, which is exactly where separation artifacts are least audible. Speed and plays-on-anything beat perfection here&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The cover artist&lt;/strong&gt; — you want the original vocal out so yours can go in, or isolated to study how the singer phrases the bridge. Your judge is a pair of headphones up close, and artifacts that vanish at a party get exposed here&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The producer&lt;/strong&gt; — stems for a remix or a sample flip, the least forgiving audience of the three: every ghost vowel left in the instrumental is one you'll EQ around for the rest of the project. There's a &lt;a href="https://formavide.com/tools/acapella-extractor?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-make-a-karaoke-track" rel="noopener noreferrer"&gt;dedicated acapella route&lt;/a&gt; for exactly this crowd&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What separation actually does — manage the expectation once
&lt;/h2&gt;

&lt;p&gt;No tool reaches into a finished mix and lifts the microphone off the singer; the recording is already blended. What the model does is estimate, moment by moment, which energy belongs to the voice and which belongs to everything else — then hand you two reconstructions. On a clean mix the estimate is startlingly good. On a wall-of-sound production with drenched reverb, the edges blur: faint vocal residue can haunt the instrumental, and a little cymbal shimmer can travel with the vocal. Knowing this beforehand is the difference between "the tool failed" and "that mix is genuinely hard." &lt;a href="https://formavide.com/blog/spleeter-vs-demucs?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-make-a-karaoke-track" rel="noopener noreferrer"&gt;Why the two engines differ&lt;/a&gt; comes down to model size and hardware.&lt;/p&gt;

&lt;h2&gt;
  
  
  The whole job in one browser tab
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the &lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-make-a-karaoke-track" rel="noopener noreferrer"&gt;splitter&lt;/a&gt; and drop the song in — an audio file, or the audio pulled straight out of a video (&lt;a href="https://formavide.com/blog/get-audio-out-of-a-video?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-make-a-karaoke-track" rel="noopener noreferrer"&gt;that trick, explained&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Pick an engine — the fast default runs on any CPU including phones; the heavier one wants a WebGPU browser (Chrome or Edge) and a shorter song&lt;/li&gt;
&lt;li&gt;Split. Both stems arrive in a single pass — instrumental for the party, vocal for everybody else&lt;/li&gt;
&lt;li&gt;Download, then listen once on the equipment the room will actually use — before the room fills up&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The split runs free on a daily quota per tool; signing in raises it. The song never leaves the machine — for unreleased masters and not-yet-announced covers, that's the only acceptable arrangement anyway.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choosing the engine in one line each
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Default engine (Spleeter)&lt;/strong&gt; — the host's choice and the cover artist's first draft: runs on any CPU including phones, takes songs up to ~30 minutes on desktop, and at a karaoke night the gap to the premium engine disappears behind the singers&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Heavy engine (Demucs, 4-stem)&lt;/strong&gt; — the producer's pick and the headphone-auditioning artist's: visibly cleaner on dense mixes and reverb-heavy vocals, songs up to ~8 minutes, wants a WebGPU-capable browser&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Phones&lt;/strong&gt; — fine for a quick split, but songs cap at 3 minutes and the heavy engine is off the table. Real karaoke prep happens on a laptop&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Finishing touches that make it play like a real karaoke track
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Trim before you split&lt;/strong&gt; (either order works). The 12-second silent intro and the long outro tail are dead weight at a party — &lt;a href="https://formavide.com/blog/how-to-trim-large-video-without-uploading?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-make-a-karaoke-track" rel="noopener noreferrer"&gt;cut the segment first&lt;/a&gt; so the file getting passed around starts where the singing starts&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mind the loudness gap.&lt;/strong&gt; An instrumental inherits the original mix's balance and can sit a touch quieter than commercial karaoke tracks; a quick level check before guests arrive beats apologies mid-chorus&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The key stays the key.&lt;/strong&gt; Separation changes what's in the file, not where it sits — if your singer needs the song lower, that's a pitch-shifting player feature, not something splitting should ever do to the audio&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Is it really free?&lt;/strong&gt; The split runs on a free daily quota per tool — enough for a night's setlist — with no sign-up to start; signing in raises the cap&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is my song uploaded?&lt;/strong&gt; No. The model loads into the browser and runs on the device; the audio never leaves it&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How long can the song be?&lt;/strong&gt; Around 30 minutes per song on desktop with the default engine, about 8 with the 4-stem one; phones cap at 3 minutes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do I get both stems in one pass?&lt;/strong&gt; Yes — one run produces the instrumental and the vocal together&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can I perform or post the instrumental?&lt;/strong&gt; Private parties, practice and remix sketches are what these tools are for. Public performance or monetizing the stems steps into licensing territory — separating them doesn't change who owns the song&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-make-a-karaoke-track" rel="noopener noreferrer"&gt;Split a song in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI vocal removal that runs locally. Free daily quota, no sign-up to start.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>machinelearning</category>
      <category>ai</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Isolate Vocals from Any Song — Free, No Upload</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Wed, 11 Nov 2026 01:04:49 +0000</pubDate>
      <link>https://dev.to/formavide/how-to-isolate-vocals-from-any-song-free-no-upload-4c4f</link>
      <guid>https://dev.to/formavide/how-to-isolate-vocals-from-any-song-free-no-upload-4c4f</guid>
      <description>&lt;p&gt;You want the voice without the band — or the band without the voice. AI stem separation used to mean uploading your music to a random web service or installing a GPU toolchain. It no longer does: here's how the free local routes work, what quality to honestly expect, and what to do with the stems once you have them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-isolate-vocals-free" rel="noopener noreferrer"&gt;Separate vocals in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI stem separation that runs locally — vocals and instrumental in one pass. Free daily quota, no sign-up to try.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What "isolating vocals" actually produces
&lt;/h2&gt;

&lt;p&gt;The output is called &lt;strong&gt;stems&lt;/strong&gt;: separate audio files, one per ingredient. The basic split is two stems — a vocal track and an instrumental track (everything else: drums, bass, guitars, synths). More advanced models go to four stems — vocals, drums, bass, other — which matters if you want to remix or mute just the drums. Either way, the source song is untouched; separation copies the ingredients out, it doesn't edit your original file.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three free routes, honestly compared
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Browser AI separation (local)&lt;/strong&gt; — quality: good, modern AI models with occasional artifacts on dense mixes · privacy: file never leaves your device · effort: low, open tab and drop file&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The phase-cancel trick (invert the instrumental)&lt;/strong&gt; — quality: poor to unusable, only works on perfectly synchronized mixes · privacy: fully local · effort: medium, needs an audio editor and the exact instrumental&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Upload separation sites&lt;/strong&gt; — quality: good, same class of AI · privacy: your music lands on a stranger's server, often with size caps and watermarks · effort: low, until the caps hit&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The phase-cancel trick deserves its honest score: it subtracts an existing instrumental from the full mix, and any timing or EQ mismatch leaves ghost vocals behind. It only ever worked on specific stereo masters. For real-world songs, AI separation is the only route that holds up — and it now runs without uploading anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to isolate vocals in your browser (no upload)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the &lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-isolate-vocals-free" rel="noopener noreferrer"&gt;vocal splitter&lt;/a&gt; and drop your track — MP3, WAV, FLAC, M4A all work. The file is processed inside your browser; nothing uploads.&lt;/li&gt;
&lt;li&gt;Pick the model: the fast 2-stem split (vocal + instrumental) for everyday needs, or the 4-stem model for remix work — it uses WebGPU acceleration, so a desktop Chrome or Edge gives the best speed.&lt;/li&gt;
&lt;li&gt;Let it run. A three-minute song usually lands under a minute on a recent laptop; the heavier 4-stem engine trades speed for detail. &lt;a href="https://formavide.com/blog/spleeter-vs-demucs?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-isolate-vocals-free" rel="noopener noreferrer"&gt;Why the two engines differ&lt;/a&gt; comes down to model size and hardware.&lt;/li&gt;
&lt;li&gt;Preview both stems, then download the ones you need — vocal, instrumental, or all four parts.&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;What quality to expect — no marketing&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;On clean, well-produced mixes the vocal stem comes out remarkably usable — good enough for karaoke tracks, practice-along, and sampling&lt;/li&gt;
&lt;li&gt;On dense, loud, heavily-compressed masters (modern pop, metal) you'll hear faint ghosts of other instruments in the vocal stem. Every AI separator has this; claims of perfection are marketing&lt;/li&gt;
&lt;li&gt;Lossless sources (FLAC/WAV) separate a little cleaner than low-bitrate MP3s — the model sees more detail&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What people actually do with the stems
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Karaoke and sing-along tracks&lt;/strong&gt; — the instrumental stem is your backing track. &lt;a href="https://formavide.com/blog/how-to-make-a-karaoke-track?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-isolate-vocals-free" rel="noopener noreferrer"&gt;A full guide to making one&lt;/a&gt;, or jump straight to the &lt;a href="https://formavide.com/tools/karaoke-track-maker?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-isolate-vocals-free" rel="noopener noreferrer"&gt;karaoke track maker&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cover practice and transcription&lt;/strong&gt; — mute the vocal to learn the arrangement, or isolate it to work out the melody and lyrics by ear&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sampling and remixing&lt;/strong&gt; — producers pull vocal phrases or isolate drum buses for loops and mashups&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cleaning up narration&lt;/strong&gt; — a lecture or interview with background music becomes usable once the music is stripped into its own stem&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dance and fitness edits&lt;/strong&gt; — instrumental-only versions for choreography videos&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Is it really free?&lt;/strong&gt; The browser separator has a free daily quota — enough to try it and split a handful of tracks — with no sign-up needed to start. Heavy daily use is what the paid tiers cover&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is my music uploaded?&lt;/strong&gt; No. The AI model loads into your browser and runs on your device — the audio never leaves it&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How long can the track be?&lt;/strong&gt; Up to 30 minutes per song on desktop; phone browsers handle short clips&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can I get vocals and instrumental separately in one pass?&lt;/strong&gt; Yes — that's exactly what a 2-stem split delivers: one vocal file, one instrumental file&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does it work on a phone?&lt;/strong&gt; For short tracks, yes. For full songs and the 4-stem model, use a desktop Chrome or Edge&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-isolate-vocals-free" rel="noopener noreferrer"&gt;Separate vocals in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI stem separation that runs locally. Free daily quota, no sign-up to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>machinelearning</category>
      <category>ai</category>
      <category>tutorial</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Why Your GIF Turns Into a Still Image in Chats — and the MP4 Fix</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Mon, 09 Nov 2026 10:31:06 +0000</pubDate>
      <link>https://dev.to/formavide/why-your-gif-turns-into-a-still-image-in-chats-and-the-mp4-fix-37g2</link>
      <guid>https://dev.to/formavide/why-your-gif-turns-into-a-still-image-in-chats-and-the-mp4-fix-37g2</guid>
      <description>&lt;p&gt;You send a GIF and it lands as a frozen frame, gets rejected for size, or takes a minute to creep across on mobile data. The GIF format itself is why — and converting it to MP4 fixes every symptom at once. Before publishing this we ran two test conversions, so the size numbers below are measured, not folklore.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/convert?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=gif-to-mp4" rel="noopener noreferrer"&gt;Convert GIF to MP4 locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;H.264 output, runs in your browser, nothing uploaded. Free — unlimited uses, no sign-up.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The chat app isn't broken — GIF is a 1987 format
&lt;/h2&gt;

&lt;p&gt;GIF predates the web itself, and every chat app is acutely aware of it. The format stores every frame in full with a hard 256-color ceiling, so a three-second animation that would weigh 300 KB as video routinely arrives as a 5–15 MB GIF. That's the root of every symptom: the "cannot send" error for size, the frozen first frame while the rest downloads, the painful upload bar on mobile data.&lt;/p&gt;

&lt;p&gt;The platforms themselves have voted. Several major messengers already &lt;strong&gt;silently re-encode your GIF into an MP4 on their servers&lt;/strong&gt; before delivery — because video is simply the better container for animation. Your GIF was converted anyway; the only part they added was a round trip to their servers.&lt;/p&gt;

&lt;h2&gt;
  
  
  What converting to MP4 actually changes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Size for the same animation&lt;/strong&gt; — GIF: baseline · MP4: roughly 3–10x smaller&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Color depth&lt;/strong&gt; — GIF: 256 colors per frame, gradients band · MP4: true color&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sending reliability&lt;/strong&gt; — GIF: size-cap rejections, long uploads · MP4: fits where GIFs bounce&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Playback in chats&lt;/strong&gt; — GIF: depends on the app · MP4: autoplays and loops in most modern clients&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Transparency&lt;/strong&gt; — GIF: supported (1-bit) · MP4: not supported, transparent areas fill white&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The measured part
&lt;/h2&gt;

&lt;p&gt;We converted the same 4-second, 640×360, 20fps animation both ways to sanity-check the size row:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Static-background clip (the typical meme shape)&lt;/strong&gt; — 890 KB as GIF → &lt;strong&gt;125 KB as MP4&lt;/strong&gt;, 7× smaller&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deliberately nasty case (full-screen rolling gradient, every pixel changes every frame)&lt;/strong&gt; — 971 KB → &lt;strong&gt;371 KB&lt;/strong&gt;, only 2.6×&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Real content sits between those poles and almost always nearer the good end, because real captures have static areas and repeating frames — exactly what H.264 is built to exploit.&lt;/p&gt;

&lt;p&gt;The transparency row is the only real trade: if your GIF relies on transparency (a floating sticker with no background), converting puts a white box behind it. For everything else — memes, clips, reactions, screen recordings — MP4 is strictly better: smaller, smoother, true-color, and it loops in WhatsApp, Telegram, Discord and most social feeds exactly like a GIF did.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to convert a GIF to MP4 in your browser (no upload)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the &lt;a href="https://formavide.com/tools/gif-to-mp4?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=gif-to-mp4" rel="noopener noreferrer"&gt;GIF to MP4 converter&lt;/a&gt; and drop your file in — it is read locally by your browser, never uploaded.&lt;/li&gt;
&lt;li&gt;Pick MP4 (H.264) as the output format.&lt;/li&gt;
&lt;li&gt;Hit convert. A few seconds later you get a file a fraction of the original size.&lt;/li&gt;
&lt;li&gt;Send it in any chat — it plays inline and loops automatically in most clients.&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Two things worth knowing before you convert&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Loop behavior is decided by the receiving app, not the file: most modern messengers autoplay and loop short MP4s by default, which recreates the GIF experience. A plain video player may show playback controls instead — that's normal.&lt;/li&gt;
&lt;li&gt;If your source GIF is genuinely transparent artwork (a sticker), keep it as a GIF — that's the one job MP4 can't take over.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  GIF, MP4, WebM — when each still makes sense
&lt;/h2&gt;

&lt;p&gt;GIF keeps exactly two niches: transparency-dependent stickers, and ancient contexts where only GIF renders (some email clients, legacy forums). MP4 is the answer for everything you send to another human. WebM plays in browsers and Discord but stumbles on iOS messaging — MP4/H.264 is the only format that plays everywhere with zero friction. The same logic applies to camera and broadcast formats: &lt;a href="https://formavide.com/blog/ts-vs-mp4?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=gif-to-mp4" rel="noopener noreferrer"&gt;TS files have the same "won't play outside its home turf" problem&lt;/a&gt;, with the same local-conversion fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Will the converted MP4 loop automatically?&lt;/strong&gt; In WhatsApp, Telegram, Discord and most social feeds, yes — short silent MP4s autoplay and loop by default there&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How much smaller, really?&lt;/strong&gt; Depends on the content. Our own test conversions: 7× smaller on a static-background clip (890 KB → 125 KB), 2.6× on a worst-case full-motion gradient&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Why is the MP4 so much smaller?&lt;/strong&gt; GIF stores every frame in full; H.264 stores only what changes between frames, plus true color&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is quality lost?&lt;/strong&gt; No — usually the opposite: true color removes the banding GIF's 256-color ceiling causes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does the file get uploaded anywhere during conversion?&lt;/strong&gt; No. The converter runs entirely in your browser tab — you can watch the network monitor stay silent&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/convert?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=gif-to-mp4" rel="noopener noreferrer"&gt;Convert GIF to MP4 locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;H.264 output, runs in your browser, nothing uploaded. Free — unlimited uses, no sign-up.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>performance</category>
      <category>tools</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How We Run FFmpeg, Whisper and ONNX Models Entirely on Your Device</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Mon, 09 Nov 2026 10:26:47 +0000</pubDate>
      <link>https://dev.to/formavide/how-we-run-ffmpeg-whisper-and-face-detection-entirely-on-your-device-1cg8</link>
      <guid>https://dev.to/formavide/how-we-run-ffmpeg-whisper-and-face-detection-entirely-on-your-device-1cg8</guid>
      <description>&lt;p&gt;Nothing about processing media locally requires a server. We built a full media toolkit — conversion, trimming, denoising, vocal separation, subtitles — where the entire pipeline executes inside the browser tab, and your files never leave the machine. This is the engineering tour: what each engine actually is, why it fits in a tab, and where the limits sit. No marketing, just the machinery.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ffmpeg-whisper-in-your-browser" rel="noopener noreferrer"&gt;Try the toolkit →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Conversion, trimming, denoising, subtitles — everything runs in your browser. Files never upload.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The engines, one by one
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Format conversion, trimming, audio extraction&lt;/strong&gt; — FFmpeg, the same engine professionals use, compiled to WebAssembly and run multithreaded inside the tab&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watermarks, subtitle burning&lt;/strong&gt; — streaming pipelines built on WebCodecs: hardware-accelerated decode, one processed frame at a time, re-encode on the way out&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Denoising&lt;/strong&gt; — DeepFilterNet3, a speech-enhancement network, executed by ONNX Runtime Web on a worker thread&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vocal separation&lt;/strong&gt; — Spleeter as ONNX, with the STFT/ISTFT spectral math implemented directly in the browser; a heavier 4-stem engine (Demucs) runs on WebGPU for desktop Chrome and Edge&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Subtitles&lt;/strong&gt; — Whisper via transformers.js, GPU-accelerated through WebGPU when the browser offers it, WASM otherwise&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why this became possible at all
&lt;/h2&gt;

&lt;p&gt;A browser used to be a document viewer; it is now a runtime with four capabilities that together close the gap with native software:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;WebAssembly&lt;/strong&gt; — C/C++ codebases like FFmpeg compile to a sandboxed instruction format that runs within striking distance of native speed&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Threads via SharedArrayBuffer&lt;/strong&gt; — the browser's version of pthreads. It requires cross-origin isolation (COOP/COEP response headers), which is why the site sends them — and why local tools that skip those headers silently run single-threaded&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WebCodecs&lt;/strong&gt; — direct access to the browser's hardware video decoders and encoders, so a pipeline can decode, touch every frame, and re-encode without a general-purpose media framework in the middle&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WebGPU&lt;/strong&gt; — compute shaders in the tab. Speech and separation models stop being CPU-bound and start finishing in something like real time&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The trick that keeps memory flat: streaming
&lt;/h2&gt;

&lt;p&gt;The naive approach — load the whole file into memory, process, save — collapses at feature-length inputs, because a browser tab gives you a finite address space, not a server's RAM pool. So the frame-by-frame features are built as streaming pipelines: the decoder hands over one frame, the effect draws onto it, the encoder writes it out, none of it accumulates.&lt;/p&gt;

&lt;p&gt;The consequence: a 2-hour video costs roughly the same memory as a 2-minute one in those tools. The limits that do remain — around 500 MB for tools that hold the whole file at once — are honest ceilings of a 32-bit address space, not marketing numbers dressed up as features.&lt;/p&gt;

&lt;h2&gt;
  
  
  Models travel so files don't have to
&lt;/h2&gt;

&lt;p&gt;The AI features invert the usual data flow. In the upload model, the multi-hundred-megabyte video crosses the internet to reach a model on a server. Here, only the model travels — a tens-of-megabytes download fetched once from our own CDN and cached by the browser — while the video sits on disk where it started. After the first use, the AI features run with no network involvement at all.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;The ten-second verification&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Skeptical by default? Good — we would be too.&lt;/li&gt;
&lt;li&gt;Open your browser's network monitor, drop a file into any tool claiming "local", and watch the transfer column. Ours stays at zero while the work happens. Every claim in this piece is checkable that way.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The honest limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Memory model&lt;/strong&gt; — tools that hold the whole file at once cap around 500 MB–1.5 GB (the trimmer takes 1.5 GB); that's the wasm32 address space talking, not a paywall&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mobile&lt;/strong&gt; — phones get 3-minute caps. A phone tab has neither the RAM nor the thermal budget for hour-long work&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GPU availability&lt;/strong&gt; — WebGPU is desktop Chrome and Edge today; elsewhere the same models fall back to WASM — slower, identical output&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Files beyond a tab&lt;/strong&gt; — no browser-sized tool handles a 20 GB raw capture; the local trick is cutting the section you need first. A native Windows app with the same no-upload rule is what we built for that tier&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Is it really FFmpeg?&lt;/strong&gt; The genuine article, cross-compiled to WebAssembly — same demuxers, filters and encoders, sandboxed by the browser instead of an installer&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does any file content reach your servers?&lt;/strong&gt; No. Only anonymous numeric usage metadata (file size, duration) is recorded; content and filenames never leave the device&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does it work offline?&lt;/strong&gt; After the first load, engines and models are cached by the browser — the processing itself needs no network&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Why should I trust the "local" claim?&lt;/strong&gt; Don't. Verify it — the network-monitor check above takes ten seconds and works on any tool that makes the claim, including ours&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ffmpeg-whisper-in-your-browser" rel="noopener noreferrer"&gt;Try the toolkit →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Everything above runs in your browser. Files never upload. Free to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webassembly</category>
      <category>ffmpeg</category>
      <category>showdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>Soft vs Hard Subtitles: Which One Your Video Actually Needs</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Thu, 05 Nov 2026 07:31:59 +0000</pubDate>
      <link>https://dev.to/formavide/soft-vs-hard-subtitles-which-one-your-video-actually-needs-48pn</link>
      <guid>https://dev.to/formavide/soft-vs-hard-subtitles-which-one-your-video-actually-needs-48pn</guid>
      <description>&lt;p&gt;Same video, same subtitles — two completely different fates. One lives as a switchable text track inside the file; the other is painted onto every frame. Which one your video needs depends on where it's going, and picking wrong costs you either the captions or the reach. Here's the honest breakdown.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/subtitle?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=soft-vs-hard-subtitles" rel="noopener noreferrer"&gt;Add either kind, in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Soft-embed in seconds without re-encoding, or burn in styled subtitles. Import SRT or transcribe locally. Free to try.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The one-sentence version
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Soft subtitles&lt;/strong&gt; are a separate text track packed inside the video file — viewers can turn them on or off, and the picture itself is untouched. &lt;strong&gt;Hard subtitles&lt;/strong&gt; are drawn into the frames during a re-encode — permanent, unswitchable, visible anywhere the video plays. Same words, opposite mechanics.&lt;/p&gt;

&lt;h2&gt;
  
  
  The full trade-off
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Viewer can toggle&lt;/strong&gt; — soft: yes · hard: no, it's part of the picture&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-encoding&lt;/strong&gt; — soft: none, a pure stream copy that takes seconds · hard: one H.264 pass to paint the frames&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quality impact&lt;/strong&gt; — soft: zero · hard: one re-encode generation (practically invisible at good settings)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Styling&lt;/strong&gt; — soft: chosen by the player · hard: yours — font, size, colors, position&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plays on social platforms&lt;/strong&gt; — soft: usually stripped or ignored · hard: everywhere, guaranteed&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-language in one file&lt;/strong&gt; — soft: yes, many tracks side by side · hard: no, one language per export&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Best for&lt;/strong&gt; — soft: archives, personal playback, YouTube · hard: Instagram, TikTok, feeds, clients&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What each platform actually does
&lt;/h2&gt;

&lt;p&gt;This is where most guides go vague. Platform behavior is the deciding factor, so concretely:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;YouTube&lt;/strong&gt; — keep them soft. YouTube reads the subtitle track, lets viewers choose languages, makes captions searchable, and can auto-translate them. Burning English text into a video YouTube could have captioned in thirty languages throws that away.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instagram, TikTok, Snapchat, most feeds&lt;/strong&gt; — burn them in. These apps re-encode your upload and routinely drop subtitle tracks. Viewers also scroll with sound off; if the captions aren't painted on, they don't exist.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Client delivery / broadcast&lt;/strong&gt; — ask, then assume hard. Professional delivery specs usually mandate specific burned-in elements or precisely formatted subtitle files; soft tracks rarely survive the chain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Personal archive&lt;/strong&gt; — soft, always. Toggleable, reversible, smallest possible change to the file.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The cost nobody mentions: re-encoding
&lt;/h2&gt;

&lt;p&gt;Burning in means the video is decoded, every frame gets text painted on it, and the video is re-encoded. That's minutes instead of seconds, and one generation of compression on top of the original. At sensible quality settings the visual difference is something you'll have to squint to find — but the time cost is real, which is exactly why "embed in seconds when possible" matters: &lt;a href="https://formavide.com/tools/add-subtitles-to-video?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=soft-vs-hard-subtitles" rel="noopener noreferrer"&gt;a local embedder&lt;/a&gt; does the soft path as a pure stream copy with no quality loss at all, and reserves the re-encode for when you've actually chosen to burn.&lt;/p&gt;

&lt;h2&gt;
  
  
  A hybrid worth knowing
&lt;/h2&gt;

&lt;p&gt;Creators who post the same video to YouTube and TikTok often do both from one source: soft-embed the master for YouTube, then burn a styled copy for feeds. It sounds like double work, but with a tool that does both paths from the same subtitle file it's two clicks — and each platform gets the format it actually respects. Style tip for the burned version: white-on-black-outline ("classic") or high-visibility yellow survives compression and bright footage best; thin delicate fonts don't.&lt;/p&gt;

&lt;h2&gt;
  
  
  Accessibility: the tiebreaker that isn't
&lt;/h2&gt;

&lt;p&gt;Some guides claim soft subtitles are "better for accessibility" because viewers control them. In practice a hard-burned caption that's always visible beats a soft track a platform deleted. Accessibility is served by captions existing wherever the video is watched — which usually means burned in for feeds, soft where platforms honor tracks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Can I convert soft to hard later?&lt;/strong&gt; Yes — embed soft now, burn the same video later from the same subtitle file.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do I have to transcribe at all?&lt;/strong&gt; No — if you already have an SRT/VTT (from an editor, another tool, or a previous export), import it and skip transcription entirely.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do burned subtitles survive re-uploads and re-encodes?&lt;/strong&gt; That's their superpower: they're pixels; every platform re-encode carries them along.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SRT, VTT, ASS — does it matter?&lt;/strong&gt; For soft embedding, SRT is the universal floor (VTT for web players); styling only matters once you're burning.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/subtitle?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=soft-vs-hard-subtitles" rel="noopener noreferrer"&gt;Add either kind, in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Soft-embed in seconds without re-encoding, or burn in styled subtitles. Import SRT or transcribe locally. Free to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ffmpeg</category>
      <category>tutorial</category>
      <category>webdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>How to Get the Audio Out of a Video (MP3, WAV, FLAC)</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Wed, 04 Nov 2026 06:46:43 +0000</pubDate>
      <link>https://dev.to/formavide/how-to-get-the-audio-out-of-a-video-mp3-wav-flac-33h2</link>
      <guid>https://dev.to/formavide/how-to-get-the-audio-out-of-a-video-mp3-wav-flac-33h2</guid>
      <description>&lt;p&gt;The song, the interview, the lecture — it's already inside your video file, fully compressed and ready. Getting it out is not a conversion marathon; it's one decode-and-save pass. Here's what actually happens to the audio along the way, and which format deserves the bytes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/extract-audio?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;Pull the audio out in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;MP3, M4A, WAV, OGG, FLAC or Opus. Files up to 1 GB and 4 hours. Free — unlimited uses, no sign-up.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The 30-second version
&lt;/h2&gt;

&lt;p&gt;Drop a video into &lt;a href="https://formavide.com/extract-audio?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;the local audio extractor&lt;/a&gt;, pick a format, press extract, download. That's the entire job. The rest of this piece is about making the two small decisions — which format, and where the work runs — with some idea of what you're doing.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;a href="https://formavide.com/extract-audio?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;the extractor&lt;/a&gt; and drop the video in. Audio files work too, when you just want a format change.&lt;/li&gt;
&lt;li&gt;Choose the output: MP3 to play anywhere, FLAC or WAV if the audio is headed into an editor, M4A for the Apple world.&lt;/li&gt;
&lt;li&gt;Extract and download. No account, no upload — the browser on your machine does the work, and nothing crosses the network.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What "extracting" actually does to the sound
&lt;/h2&gt;

&lt;p&gt;A video file is two parallel streams sharing one filename: pictures and sound. Extraction keeps the sound and discards the pictures. The honest detail most skip: the audio isn't simply copied out. It's decoded to raw samples first, then encoded into whatever container you picked. For lossless targets (WAV, FLAC) that round-trip is mathematically exact — the samples come back identical. For lossy targets (MP3, M4A, OGG, Opus) it's one extra compression generation, on top of the one the camera already applied.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which format deserves the bytes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;MP3&lt;/strong&gt; — it has to play everywhere: car, old stereo, messaging apps · encoded at high-quality VBR; the safest universal default&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;M4A (AAC)&lt;/strong&gt; — Apple devices, phones, smaller files at the same audible tier · 192 kbps; what video files usually carry inside anyway&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WAV&lt;/strong&gt; — the audio is going straight into an editor or plugin chain · lossless but enormous, roughly 10 MB per minute&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FLAC&lt;/strong&gt; — lossless archiving without WAV's disk appetite · identical samples to WAV at about half the size&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OGG&lt;/strong&gt; — open web players, game engines · great quality per byte, patchy support on Apple hardware&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Opus&lt;/strong&gt; — voice, meetings, anything size-sensitive and modern · the best sound-per-megabyte, but older software ignores it&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How much quality is actually at stake
&lt;/h2&gt;

&lt;p&gt;Less than the format wars suggest. Camera and phone audio is nearly always lossy AAC to begin with — the original recording already threw away what it threw away. One further generation at high settings (192 kbps AAC, high-quality VBR MP3) is transparent in blind listening for typical source material. Choosing WAV or FLAC doesn't recover anything the camera lost — it just guarantees nothing further is lost from here on. Rule of thumb: archive in FLAC, distribute in MP3 or M4A, edit in WAV if the project demands it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Long recordings and oversized files
&lt;/h2&gt;

&lt;p&gt;The local path takes videos up to 1 GB and up to 4 hours long on a desktop browser (phones handle short clips, up to 3 minutes). Because there's no upload, a two-hour lecture extracts in about the time the audio takes to decode — not the geological era an upload would take. For a file bigger than that, &lt;a href="https://formavide.com/blog/how-to-trim-large-video-without-uploading?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;cut the section you need first&lt;/a&gt; and extract from the cut; the audio you wanted was never in the parts you're dropping.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the audio usually goes next
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Editing and podcasting&lt;/strong&gt; — an extracted soundtrack drops straight into any editor. If a hummy room recording comes with it, &lt;a href="https://formavide.com/blog/why-your-podcast-sounds-noisy?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;clean it before it ships&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Karaoke and covers&lt;/strong&gt; — a song that only exists inside a video can become a singable instrumental: split the vocal out as the next step — &lt;a href="https://formavide.com/blog/how-to-make-a-karaoke-track?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;here's how that works&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ringtones and clips&lt;/strong&gt; — extract once, then &lt;a href="https://formavide.com/blog/how-to-trim-large-video-without-uploading?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;cut the exact 20 seconds&lt;/a&gt; instead of dragging the whole soundtrack around.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Transcription and notes&lt;/strong&gt; — a 90-minute lecture becomes a manageable audio file; most transcription tools are happier with a small M4A than a full video.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;The ten-second privacy check&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Curious whether "local" is actually local? Open your browser's network monitor before dropping the file in, then drop it.&lt;/li&gt;
&lt;li&gt;A tool that keeps its word shows zero upload traffic while the file processes. This one does — the video is read from disk by the tab itself.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/extract-audio?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=get-audio-out-of-a-video" rel="noopener noreferrer"&gt;Pull the audio out in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;MP3, M4A, WAV, OGG, FLAC or Opus. Files up to 1 GB and 4 hours. Free — unlimited uses, no sign-up.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ffmpeg</category>
      <category>tutorial</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>TS vs MP4: What's the Difference and Which Should You Use?</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Mon, 02 Nov 2026 07:59:40 +0000</pubDate>
      <link>https://dev.to/formavide/ts-vs-mp4-whats-the-difference-and-which-should-you-use-jbk</link>
      <guid>https://dev.to/formavide/ts-vs-mp4-whats-the-difference-and-which-should-you-use-jbk</guid>
      <description>&lt;p&gt;A .ts file and an .mp4 file can contain the exact same video and audio — yet one opens anywhere and the other baffles players, editors and upload forms. Here's what actually separates the two containers, and when it's worth converting.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/convert?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ts-vs-mp4" rel="noopener noreferrer"&gt;Convert TS to MP4 locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Auto-remux in seconds when the stream allows; no upload. Free to try.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Both are containers, not codecs
&lt;/h2&gt;

&lt;p&gt;First, the frame that makes everything else click: TS and MP4 are &lt;strong&gt;containers&lt;/strong&gt; — wrapping paper around video and audio streams. The actual picture inside both is usually the same codec (H.264). The container decides how the streams are chopped, labelled, timestamped and indexed — which sounds boring until it determines whether your file opens at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  TS: built for broadcast, born in the 1990s
&lt;/h2&gt;

&lt;p&gt;MPEG Transport Stream was designed for one job: carrying TV over unreliable airwaves where viewers tune in mid-broadcast. It chops streams into small, self-contained packets so a decoder can start anywhere — join a stream mid-football-match and the picture appears within a beat. That same resilience is why camcorders (AVCHD), DVRs and screen recorders love it: if the power dies mid-recording, the file up to that moment is still playable.&lt;/p&gt;

&lt;h2&gt;
  
  
  MP4: built for files, indexed for seeking
&lt;/h2&gt;

&lt;p&gt;MP4 takes the opposite bet: it assumes the whole file exists before anyone presses play. It writes an index (the moov atom) that maps every second of the file, which is what makes instant seeking, scrubbing and streaming-from-any-point possible. It's the container every platform, editor and device vendor agreed on — two decades of universal support.&lt;/p&gt;

&lt;h2&gt;
  
  
  The practical differences
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Designed for&lt;/strong&gt; — TS: broadcast and live capture · MP4: files, editing, streaming platforms&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Seeking &amp;amp; scrubbing&lt;/strong&gt; — TS: poor to nonexistent in players · MP4: instant, via the index&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Player &amp;amp; platform support&lt;/strong&gt; — TS: patchy, many apps ignore the extension · MP4: universal&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Editing software&lt;/strong&gt; — TS: often refuses or transcodes first · MP4: native&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Upload to social/editing clouds&lt;/strong&gt; — TS: frequently rejected · MP4: accepted&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Crash resilience&lt;/strong&gt; — TS: excellent (why cameras use it) · MP4: poor without finalization&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  So when is converting worth it?
&lt;/h2&gt;

&lt;p&gt;If the TS file works everywhere you need it, convert nothing. Convert when any of these is true:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;An editor or app refuses the file or wants to transcode it itself.&lt;/li&gt;
&lt;li&gt;You're uploading to a platform that doesn't accept .ts.&lt;/li&gt;
&lt;li&gt;Scrubbing in your player is broken or seeks jump strangely.&lt;/li&gt;
&lt;li&gt;You're archiving into a library that standardizes on MP4.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Does converting TS to MP4 lose quality?
&lt;/h2&gt;

&lt;p&gt;Here's the part most guides get wrong: conversion quality depends entirely on &lt;strong&gt;how&lt;/strong&gt; the converter works. Because the video inside TS is usually already H.264 — the codec MP4 expects — a good converter doesn't re-encode anything. It &lt;strong&gt;remuxes&lt;/strong&gt;: copies the existing streams into the new wrapper untouched. That's bit-identical output in seconds.&lt;/p&gt;

&lt;p&gt;A re-encode only becomes necessary when the stream inside genuinely can't live in MP4 (old MPEG-2 broadcasts, for example). Then the video is decoded and re-compressed once — near-invisible at good settings, but real. The &lt;a href="https://formavide.com/tools/ts-to-mp4?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ts-vs-mp4" rel="noopener noreferrer"&gt;converter we build&lt;/a&gt; tries the remux first and falls back to re-encoding only when it must, showing you a 15-second preview either way.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Watch out for the conversion trap&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A converter that always re-encodes costs you quality and minutes, even when a 2-second remux would do.&lt;/li&gt;
&lt;li&gt;If your tool takes longer than a few seconds on a modern TS file, it's probably re-encoding when it doesn't need to.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The cousins: M2TS and MTS
&lt;/h2&gt;

&lt;p&gt;If your file ends in .m2ts or .mts (AVCHD camcorders, Blu-ray rips), it's the same transport stream idea with a folder structure around it. Everything above applies — including the fix. And if the recording is huge, &lt;a href="https://formavide.com/blog/how-to-trim-large-video-without-uploading?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ts-vs-mp4" rel="noopener noreferrer"&gt;trim the section you need first&lt;/a&gt; rather than converting hours of footage to get 90 seconds.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/convert?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ts-vs-mp4" rel="noopener noreferrer"&gt;Convert TS to MP4 locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Auto-remux in seconds when the stream allows; no upload. Free to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>webassembly</category>
      <category>showdev</category>
      <category>ffmpeg</category>
    </item>
    <item>
      <title>How to Trim a Large Video Without Uploading It</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Thu, 29 Oct 2026 06:44:22 +0000</pubDate>
      <link>https://dev.to/formavide/how-to-trim-a-large-video-without-uploading-it-agl</link>
      <guid>https://dev.to/formavide/how-to-trim-a-large-video-without-uploading-it-agl</guid>
      <description>&lt;p&gt;Every online video cutter hits the same wall with big files: the upload. Here's why that wall exists, how to get around it entirely, and how to cut the part you need from a multi-gigabyte recording without a single byte leaving your computer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/trim?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-trim-large-video-without-uploading" rel="noopener noreferrer"&gt;Trim a large video locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Frame-accurate, up to 1.5 GB, runs in your browser. Free to try.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The upload is the whole problem
&lt;/h2&gt;

&lt;p&gt;Look at what an upload-based video cutter actually asks of you: send the entire file to a server so that a machine far away can throw most of it away. You want a 90-second clip from a 2 GB recording — and the tool insists on receiving all 2 GB first.&lt;/p&gt;

&lt;p&gt;The math makes this painful fast. On a typical 20 Mbps home upload connection, 2 GB takes about 13 minutes to upload. Then the server processes (often behind a queue), then you download the result. For a 90-second trim, that's 20+ minutes of waiting for what should be seconds of work.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Free tiers usually cap uploads at 500 MB–1 GB — many raw recordings don't fit at all.&lt;/li&gt;
&lt;li&gt;Long videos fail or time out mid-upload, and you start over.&lt;/li&gt;
&lt;li&gt;Your footage sits on someone else's server — a real concern for client work, interviews and anything unreleased.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why local trimming sidesteps all of it
&lt;/h2&gt;

&lt;p&gt;A local trimmer flips the model: instead of sending the file to the software, the software loads in your browser and works on the file right where it sits. Modern browsers can run a full video toolkit (the same FFmpeg engine professionals use, compiled to WebAssembly) inside the tab. Nothing uploads, so there is no upload cap tied to your bandwidth, no queue, and no copy of your footage on a stranger's disk.&lt;/p&gt;

&lt;p&gt;The practical consequence: trimming time stops depending on your upload speed entirely. A 1.5 GB file is as quick to cut as a 150 MB one — the work is proportional to the segment you're keeping, not the file you're cutting from.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to trim a large video in your browser (4 steps)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the &lt;a href="https://formavide.com/tools/trim-video?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-trim-large-video-without-uploading" rel="noopener noreferrer"&gt;video trimmer&lt;/a&gt; and drop your file in — it is read locally; watch the network tab if you don't believe it.&lt;/li&gt;
&lt;li&gt;Find your segment: scrub the preview, drag on the waveform timeline, or press I / O to mark the exact in and out points. You can also type times down to the millisecond.&lt;/li&gt;
&lt;li&gt;More than one clip to keep? Add up to 10 segments and export them all in one pass instead of re-cutting the file repeatedly.&lt;/li&gt;
&lt;li&gt;Choose the cutting mode and hit Trim. Download — no watermark, no account.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Fast-but-loose vs slow-but-exact: pick the right mode
&lt;/h2&gt;

&lt;p&gt;Video is compressed in groups of frames anchored to keyframes, and that fact decides your two options — &lt;a href="https://formavide.com/tools/trim-video?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-trim-large-video-without-uploading" rel="noopener noreferrer"&gt;explained in detail here&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Lossless (stream copy)&lt;/strong&gt; — seconds · snaps to nearest keyframe, can be a second or two off · bit-identical to the original · use for rough cuts, splitting long recordings, archiving&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Precise (re-encode)&lt;/strong&gt; — minutes · frame-accurate, cuts exactly where you set · one re-encode, visually transparent at high settings · use for social clips that must open on the exact moment&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;A workflow trick for oversized files&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Most local processing tools handle bigger inputs than upload sites, but nothing handles everything: a 4K feature-length raw file still exceeds what a browser tab can hold.&lt;/li&gt;
&lt;li&gt;When a file is too big even for local tools, trim first — cutting a 1.5 GB section out of a 20 GB recording locally, then working on just that section, unblocks every other tool in the chain.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What about desktop video editors?
&lt;/h2&gt;

&lt;p&gt;A native editor (Premiere, DaVinci, even Shotcut) trims locally too, and for projects you're already editing, that's the right home. But for the "I just need this one clip out of this one file" job, an editor is a sledgehammer: project setup, import wait, export settings. A browser trimmer is open-tab, drop-file, done — with no install and nothing to clean up. It also works on a borrowed or locked-down machine where you can't install software.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;How big can the file be?&lt;/strong&gt; Up to 1.5 GB in the browser trimmer referenced above, with output segments up to 2 hours on desktop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does trimming reduce quality?&lt;/strong&gt; Not in lossless mode — the video stream is copied untouched. Precise mode re-encodes once; at high quality settings the difference is effectively invisible.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does it work on a phone?&lt;/strong&gt; Yes for short clips; hour-long segments want a desktop browser.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is my footage uploaded anywhere?&lt;/strong&gt; No. The tool runs in your browser tab — you can verify in your network monitor that nothing is transmitted.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/trim?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-trim-large-video-without-uploading" rel="noopener noreferrer"&gt;Trim a large video locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Frame-accurate, up to 1.5 GB, runs in your browser. Free to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>video</category>
      <category>webassembly</category>
      <category>showdev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Why Your Podcast Sounds Noisy (and How to Fix Each Cause)</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Wed, 28 Oct 2026 01:42:30 +0000</pubDate>
      <link>https://dev.to/formavide/why-your-podcast-sounds-noisy-and-how-to-fix-each-cause-526b</link>
      <guid>https://dev.to/formavide/why-your-podcast-sounds-noisy-and-how-to-fix-each-cause-526b</guid>
      <description>&lt;p&gt;You hit record, talked, played it back — and there it is: a wash of hum, hiss or echo under your voice. Noise in podcast audio always has a specific cause, and each cause has a specific fix. Here's how to diagnose yours and what to do about it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/denoise?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-your-podcast-sounds-noisy" rel="noopener noreferrer"&gt;Clean up your recording locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI denoising with an adjustable strength dial and A/B preview. Runs in your browser, nothing uploads. Free to try.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  First, identify which noise you have
&lt;/h2&gt;

&lt;p&gt;"Noisy" is four different problems wearing one label. Play a silent section of your recording with eyes closed — each noise has a fingerprint:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Steady low hum (50/60 Hz)&lt;/strong&gt; — electrical ground loop, unbalanced cables or mains interference · fixable in post: yes, denoiser or high-pass filter&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Smooth "sssshhh" layer&lt;/strong&gt; — self-noise of a cheap mic or preamp, hiss from high gain · fixable: yes, denoiser&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rumbling whoosh&lt;/strong&gt; — HVAC, fan, open window, traffic, wind on the mic · fixable: yes, denoiser with the strength up&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Voice "hangs" in the room&lt;/strong&gt; — hard parallel surfaces; reflections, not noise · fixable: partly — prevention beats cure&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The causes worth fixing at the source
&lt;/h2&gt;

&lt;p&gt;Post-processing can rescue a take, but three culprits are far easier to prevent than to repair:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Room echo.&lt;/strong&gt; Bare walls are the enemy. The cheapest fix in audio: record under a thick blanket, in a closet full of clothes, or facing an open bookshelf. No plugin fully un-echos a voice once reflections are baked in.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mic distance.&lt;/strong&gt; Every doubling of distance costs you ~6 dB of voice — which you'll compensate with gain, which raises the noise floor with it. A fist's width off-axis from the mouth (slightly to the side, dodging plosives) beats any de-noiser.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ground loops and buzz.&lt;/strong&gt; If the hum changes when you touch the mic or laptop charger, it's electrical — try a different outlet, unplug the charger, or use the second USB port before you reach for software.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The post-production rescue pipeline
&lt;/h2&gt;

&lt;p&gt;For the noise that made it into the take, order matters. Each step should happen once, in this sequence:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Trim the dead air.&lt;/strong&gt; Cut the silent head and tail first — there's no point denoising minutes of room tone nobody needs. &lt;a href="https://formavide.com/blog/how-to-trim-large-video-without-uploading?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-your-podcast-sounds-noisy" rel="noopener noreferrer"&gt;A local trimmer&lt;/a&gt; does this in seconds without uploading the episode.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Denoise with a dial, not a button.&lt;/strong&gt; AI denoisers work best with discretion: start around 60–70% strength for steady hum and hiss, and listen to a segment before and after at each setting. Full-power denoising on a light-hum recording is how voices start sounding like they're under water.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Normalize the loudness.&lt;/strong&gt; Denoising often reveals how quiet the take was. Bring it to a consistent level — but use a tool that leaves silence alone and caps the boost, or you'll amplify the noise floor right back into audible range.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Then, and only then, compress.&lt;/strong&gt; A compressor after cleanup evens out the performance. Compress before denoising and you've raised the noise into the compressor's grasp.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why "AI denoise" beats the old manual chain
&lt;/h2&gt;

&lt;p&gt;The traditional recipe — noise gate, notch filter, spectral repair — assumes you'll spend an hour learning parameters per episode. Modern speech-enhancement networks (like DeepFilterNet3) learned what clean voice sounds like from thousands of hours of examples, and simply remove everything that isn't that. For steady noise the result is a one-pass fix that used to take an afternoon.&lt;/p&gt;

&lt;p&gt;Two honest limits: it's voice-centric, so music under the voice gets treated as noise (that's a job for a &lt;a href="https://formavide.com/tools/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-your-podcast-sounds-noisy" rel="noopener noreferrer"&gt;vocal splitter&lt;/a&gt;, not a denoiser); and it can't recover a voice that was drowned completely — it makes marginal takes usable, not studio-grade.&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on where you run the fix
&lt;/h2&gt;

&lt;p&gt;Episode audio is personal: early drafts, unflattering outtakes, guest recordings under NDA. A browser-based denoiser keeps the file on your machine — you can watch the network tab stay silent. The &lt;a href="https://formavide.com/tools/remove-background-noise-from-audio?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-your-podcast-sounds-noisy" rel="noopener noreferrer"&gt;tool we build&lt;/a&gt; runs the AI model in your tab with an A/B preview, so you can judge the strength setting by ear before committing the whole episode. Free to try, and the same pipeline works on video files without touching the picture.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/denoise?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=why-your-podcast-sounds-noisy" rel="noopener noreferrer"&gt;Clean up your recording locally →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI denoising with an adjustable strength dial and A/B preview. Runs in your browser, nothing uploads. Free to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>podcast</category>
      <category>tutorial</category>
      <category>machinelearning</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Spleeter vs Demucs: Which AI Stem-Splitter Sounds Better?</title>
      <dc:creator>Formavide</dc:creator>
      <pubDate>Tue, 27 Oct 2026 03:01:05 +0000</pubDate>
      <link>https://dev.to/formavide/spleeter-vs-demucs-which-ai-stem-splitter-sounds-better-2l82</link>
      <guid>https://dev.to/formavide/spleeter-vs-demucs-which-ai-stem-splitter-sounds-better-2l82</guid>
      <description>&lt;p&gt;Most "which is better" answers repeat marketing. We ship both engines in one browser tool, run them on the same songs daily, and can tell you exactly where each wins — and why the difference exists.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=spleeter-vs-demucs" rel="noopener noreferrer"&gt;Try both engines in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Spleeter for speed anywhere, Demucs 4-stem on WebGPU. Nothing uploads. Free to try.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Two models, two generations of thinking
&lt;/h2&gt;

&lt;p&gt;Both networks do the same job — pull a song apart into vocals and accompaniment — but they look at the problem differently, and that difference explains everything about their results.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Spleeter&lt;/strong&gt; (Deezer, 2019) works like a picture editor. It converts the song into a spectrogram — a snapshot of which frequencies sound at which moments — and a compact network paints a mask over it: this
energy is voice, that is everything else. Fast and light, because masking a picture is cheap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Demucs&lt;/strong&gt; (Meta, evolving through 2022's htdemucs) works more like a musician re-performing the song. It processes the actual audio waveform through a deep encoder-decoder, modeling how each instrument
evolves over time rather than judging frequencies frame by frame. Heavier — much heavier — and that's where its quality comes from.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where you actually hear the difference
&lt;/h2&gt;

&lt;p&gt;On a clean mix with a dry lead vocal, both produce very usable stems — many listeners won't pick a favorite blind. The gap opens under stress:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Dense, loud mixes.&lt;/strong&gt; Spleeter's mask tends to leave ghostly vocal residue in the instrumental and take some cymbal shimmer with the vocal. Demucs keeps the sides cleaner.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reverb-heavy vocals.&lt;/strong&gt; Echo smears the vocal across time — a frame-by-frame mask smears its guess with it. Demucs' longer view of the audio tracks that trail far better.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fasts, transients, drums.&lt;/strong&gt; In 4-stem mode, Demucs' drum separation is decisively more musical — hi-hats stay hi-hats instead of turning into artifacts.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Speed, weight, and what it costs to run
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Spleeter (2-stem)&lt;/strong&gt; — vocals + instrumental · runs on any CPU, phones included · fast on any laptop · songs up to ~30 minutes · usable on hard mixes, with some artifacts&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Demucs (htdemucs, 4-stem)&lt;/strong&gt; — vocals, drums, bass, other · wants a GPU (WebGPU in Chrome/Edge) · heavier, GPU does the lifting · songs up to ~8 minutes · clearly cleaner on hard mixes&lt;/p&gt;

&lt;h2&gt;
  
  
  So which should you use?
&lt;/h2&gt;

&lt;p&gt;The honest answer is a decision tree, not a winner:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Quick job, long file, any device&lt;/strong&gt; — Spleeter. A 20-minute mix for a background track doesn't need (and can't run) Demucs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Karaoke night, casual covers&lt;/strong&gt; — Spleeter at default settings is usually indistinguishable in the room, over speakers, with people singing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Remix or sampling, vocals front and center&lt;/strong&gt; — Demucs. Every artifact you don't remove now is one you EQ around later.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Testing if a song "can" be separated at all&lt;/strong&gt; — Spleeter first for the shape of the result, Demucs for the keepable version.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why we ship both instead of picking one
&lt;/h2&gt;

&lt;p&gt;Single-engine tools make you fit the job to the model. The &lt;a href="https://formavide.com/tools/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=spleeter-vs-demucs" rel="noopener noreferrer"&gt;splitter we build&lt;/a&gt; puts both behind one drop-in, running entirely in your browser — Spleeter on any CPU, Demucs on WebGPU-capable machines — and both stems come out of a single pass either way. Because everything runs locally, you can A/B the engines on the same song as many times as you like, with unreleased material never leaving your disk.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What no stem-splitter can do&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Recover a vocal that was mixed into a single bounced file with full-band distortion — separation estimates; it doesn't un-mix physics.&lt;/li&gt;
&lt;li&gt;Beat stems delivered by the original studio. For release-grade work, cleared acapellas still win; for creative work, practice and remixing, modern separation is genuinely good.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://formavide.com/vocal-split?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=spleeter-vs-demucs" rel="noopener noreferrer"&gt;Try both engines in your browser →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Spleeter for speed anywhere, Demucs 4-stem on WebGPU. Nothing uploads. Free to try.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webassembly</category>
      <category>showdev</category>
      <category>machinelearning</category>
    </item>
  </channel>
</rss>
