Disclaimer

Disclaimer and disclosure

This site publishes general information about AI-assisted audio and video workflows, Korea travel planning and eSIM buying checklists, and links to Korean household-product comparisons through the shopping directory. The technical notes describe our own files and settings. The travel and buying guides identify questions to verify with the operator or seller for your dates and selected product. Nothing here is legal, tax or other professional advice, and it is not tailored to your situation.

Measurements

Readings such as loudness, true peak or file hashes were taken on our own files with the tools named in each post. Different files, tool versions or settings can give different results. Test on your own material before relying on a number.

Platform rules

Upload limits, loudness targets, monetization and AI-content policies belong to each platform and change without notice. We link the official page we checked and the date we checked it. The platform's current page always wins over our summary.

Copyright and AI-generated content

Whether you may use, publish or earn from a piece of music, footage or an AI tool's output depends on its licence and the tool's terms. Nothing here grants rights or confirms that a particular use is allowed. Check the licence yourself.

Tools on this site

The duplicate file checker runs in your browser and compares exact file contents. It does not detect re-encoded, trimmed or visually similar copies, and it is provided as is.

Affiliate and referral links

Some pages contain disclosed affiliate or referral links, including links associated with Higgsfield, ElevenLabs, Airalo, Klook, Coupang, Toss or Naver Shopping Connect where actually present. A booking, purchase or subscription through an eligible link may result in a commission. The applicable page explains the relationship before the relevant link. A program list does not establish a conversion, a confirmed commission or a payment. Referral relationships do not change measured results.

Free checks

The commands and exact-file checker described on this site can be used without buying a product. They provide technical measurements and do not guarantee platform approval or rights.

Advertising and external links

Google AdSense is configured; ad serving depends on approval. Advertisers do not decide what gets written, and we do not accept sponsored posts. Links to other sites are not endorsements.

Start here · About · Contact · Disclaimer · Privacy · 한국어 글 모음

A referral click, an attributed order, a confirmed commission and a received payment are different observations. We do not treat a published page, a working link or a view count as proof of those later stages. General buying checklists do not establish current checkout prices, device compatibility or a particular refund entitlement. Historical technical results remain bound to their stated file, model, version and observation dates; new material can differ.

References

Comments

Post a Comment

Popular posts from this blog

FFmpeg Shows −1.5 dBTP. Did You Actually Fix the Audio?

An output_tp of −1.50 in an FFmpeg log does not mean your original audio has been fixed. A command can show that number without saving any corrected audio. Before uploading, measure the file you actually exported. This follow-up to our AI song quality checklist tackles one practical mistake: confusing filter output statistics with a saved deliverable. You need FFmpeg installed and a local audio file. These commands process files on your computer; they do not upload your recording. One recording, two different stages On September 18, 2026, we measured one newly generated, roughly 2-minute-20-second MP3. Its integrated loudness was −11.41 LUFS and its true peak was +0.84 dBTP . The same analysis log showed output_tp: -1.50 . input_i and input_tp describe the file supplied to that command. output_i and output_tp describe the signal after the filter in that execution. They do not establish the measured properties of a separately encoded final file. We then reduced gain by...
Read more

VoxCPM2 vs ElevenLabs for a 30-Second Science Short: We Timed Both on the Same Script

Image
Disclosure: DigitalHarvest (NSST) is an independent affiliate of ElevenLabs. We may earn a commission if you subscribe through the referral link in this article. ElevenLabs has not sponsored, reviewed, or approved this article. This relationship does not change the numbers below, and the free local option wins on cost in our own test. We make 30-second science Shorts from public-domain NOAA ocean footage, and every one needs about six lines of narration. On October 4, 2026 we took one finished script and voiced the same six lines twice: once with VoxCPM2, an open-source model running on our own Apple Silicon Mac, and once with ElevenLabs on the paid Creator plan we already use. Then we ran both outputs through the same Whisper check our pipeline uses before anything is published. Here is what came out. The script we used The episode is "Why doesn't hot water on the seafloor boil?" (a small black smoker vent filmed at 2,947 m by NOAA Ocean Exploration). Six lines, 428...
Read more

Before You Upload an AI Song or Video: The Checks We Run (Free Commands)

The FFmpeg and file-hash commands below run locally. No purchase is needed to follow them. In September 2026 we published a 140-second "music video" for one of our AI songs. It was one still picture with a small moving waveform along the bottom. Our pre-upload checks had measured the length, the resolution and the loudness. Nobody had checked whether the picture actually moved. We deleted it from our channel the next morning. This post shows the checks we run now. Every command below runs on your own computer with ffmpeg , and every number comes from files we measured ourselves. 1. Loudness and true peak (free, one command) ffmpeg -hide_banner -nostats -i song.mp4 -af ebur128=peak=true -f null - Read the Summary block at the end: I: is the integrated loudness in LUFS. Peak: under "True peak" is the true peak. ffmpeg prints the unit as dBFS. A test file we deliberately pushed too loud read I: -8.4 LUFS and Peak: 3.5 . Our own working baseline is ...
Read more