SeedanceCheap — Builder Notes

https://seedancecheap.com AI-assisted technical note from the SeedanceCheap team, with Codex. A reporting window meant to start at 16:00 UTC can accidentally start at 13:00 UTC. The trigger is a small type change: parse a UTC timestamp from JSON, cast the resulting date to a string without a zone, then interpret that string in UTC+03. We encountered this class of bug in a reporting script. The example below uses invented input and an in-memory time zone. It contains no customer records, makes no network calls and does not change your computer's time zone. The zone disappears at the string boundary With PowerShell's default ConvertFrom-Json behavior, an ISO timestamp ending in Z becomes a DateTime with Kind set to Utc . That typed value still identifies the intended instant. A later [string] cast can produce a date such as 10/16/2026 16:00:00 , which no longer says UTC. A consumer must now guess the missing zone. If it treats 16:00 as local UTC+03, the corresponding U...

https://seedancecheap.com A video-delivery check can report the dimensions of cover art instead of the moving picture. Reading the first stream is the mistake: a stream marked as video can be an attached image. Here is a small, reproducible developer note using an invented metadata report. It contains no customer footage or records, makes no generation request, and uploads nothing. A quick local check With an existing ffprobe installation, run this against your downloaded file: ffprobe -v error -select_streams V:0 -show_entries stream=index,width,height -of json "delivered.mp4" The uppercase V is deliberate. The official ffprobe stream-specifier documentation distinguishes all video streams ( v ) from video streams excluding attached pictures, thumbnails and cover art ( V ). The :0 selects the first matching stream; it does not prove that this is the intended main picture in a multi-angle file. Use V without :0 to list the matching picture streams and choose the ri...

SeedanceCheap.com — from our team, with Codex. We operate the AI-video service discussed here and have a commercial interest in it. This is a practical account of a change to our free, local API request builder. A free request-planning tool can still prepare a request that requires paid funding. Its interface should make that boundary clear before someone copies JSON into a terminal. Our public cookbook previously put free_trial: true into every prepared pilot. That was a safe choice against accidental paid fallback, but it left developers with an awkward path when introductory trials were paused: the only prepared example selected a trial, even if the reader intended to use existing credits. We changed the builder to require an explicit funding choice. It starts with neither route selected. The JSON preview stays empty and its download button stays disabled until the reader chooses trial or paid funding. The page still collects no API key and sends no generation request. Ca...