Production management

Scheduling, budgeting, asset tracking, review, collaboration and production automation

• articleIf a production has a sync or library licence, which rights does that leave to other licences (performance/broadcast), and how does the cue sheet connect the pieces?
  Corrected 2026-10-24 - see C3-B1129-01; the original statements below are kept for history and are superseded where the correction says so. UK sources separate three things: the right to copy and synchronise (MCPS, issued through PRS for Music), the right to perform or broadcast the composition (PRS, often through a broadcaster's blanket arrangement), and the recording rights (PPL for commercial recordings; included in MCPS library licences). A cue sheet carries the usage data that lets societies pay performance royalties; it is not a licence. The MCPS FAQ gives the clearest example: a library licence excludes the public-communication right in the musical work, which matters if the licensee itself hosts or broadcasts. Whether a broadcaster's blanket applies is not stated in the pages read.
• articleWhen breaking down a script that contains intimate scenes, what should an agent flag for the producer, ADs, IC, costume, post and legal/contract teams, and which flags come from which source?
  Corrected 2026-10-24 - see C3-B1108-01; the original statements below are kept for history and are superseded where the correction says so. No single source gives an agent-ready breakdown template, but the pinned union documents together imply a flag list: scene identification (nudity or semi-nudity, sexual activity, other exposing factors), required roles (IC; stunt coordinator and IC where sexual violence is depicted), people involved (performers, background and doubles who appear nude, minors), contract dependencies (rider with script pages and body-part list, 48-hour delivery before call time), schedule and call-sheet items (IC on schedule and day-out-of-days, closed-set marking and crew list, start-of-day placement for sexual-violence scenes, rehearsal slots), cross-department items (costume, prosthetics, digital additions) and downstream flags (take usability for editors, promotion consent, retention). The list is synthesis; each flag cites a source statement.
• articleWhat does YouTube's own text say changes in the YouTube Partner Program from 1 Feb 2027 (new-creator thresholds, who is affected, terms deadline), and what is still not stated?
  Corrected 2026-10-24 - see C3-B968-05; the original statements below are kept for history and are superseded where the correction says so. Problem: C3-B566-01 recorded only the help-page banner. Primary text now read: the YouTube Official Blog post 'New opportunities to earn and changes to the YouTube Partner Program' (The YouTube Team, 10 Aug 2026), plus the YPP overview Help page. Source statements: (1) New creators applying for YPP will need 8,000 qualified watch hours in the last 365 days, or 20 million qualified Shorts views in the last 90 days, for ads and Premium revenue sharing. (2) 'This update won't impact creators already in YPP.' (3) Entry thresholds for Fan Funding and shopping products remain unchanged. (4) Creators can review and sign the new terms in YouTube Studio; the terms take effect 1 Feb 2027. (5) The Help page banner says to review and accept the updated terms in Studio by 31 Jan 2027 to continue fully monetizing. Not stated or not verified (checked 2026-10-23...
• articleWhere do SAG-AFTRA (US), ACTRA Toronto (Canada), MEAA Equity (Australia) and Bectu (UK) agree and differ on auditions, rider timing, body doubles, third-party support, and retention of intimate footage?
  Corrected 2026-10-24 - see C3-B1078-01; the original statements below are kept for history and are superseded where the correction says so. Four union or union-branch documents set a 48-hour advance-notice convention in different places: before call time (SAG-AFTRA Quick Guide, Bectu), before signing or rendering services (ACTRA Toronto), and before the audition for the audition script (MEAA). They differ sharply on nudity at auditions: SAG-AFTRA permits one final modesty-garment audition, ACTRA permits a closed callback for viewing the body with at most five producer-side people, MEAA says nudity or semi-nudity should never be required, proposed or agreed to in an audition. MEAA adds a retention limit (destroy non-final-cut intimate recordings within five years); ACTRA gives performers approval over 50 percent of proposed body doubles.
• articleWhen must a YouTube creator disclose AI-generated or altered content, and how is it labelled?
  Corrected 2026-10-24 - see C3-B1072-01; the original statements below are kept for history and are superseded where the correction says so. YouTube requires disclosure (Studio upload > Attributes > "AI use") for realistic AI-generated or meaningfully altered content: making a real person appear to say or do something, altering footage of a real event or place, generating a realistic scene that did not occur, or creating music that is the main focus. Not required: clearly unrealistic content, minor/aesthetic edits, and production assistance (outlines, scripts, thumbnails, titles, captions, upscaling, cloning one's own voice). Labels appear in the description or on the player (music and photorealistic content). YouTube may auto-label content made with its GenAI tools, content carrying C2PA metadata, or content its systems detect; creators can usually correct it. The page states disclosure alone does not limit reach or monetization. Implication for AI music videos (frequent in creator ...
• articleWhat are YouTube's rules for remixing other videos into Shorts and editing your own long-form into a Short?
  Corrected 2026-10-24 - see C3-B1037-01; the original statements below are kept for history and are superseded where the correction says so. YouTube Help (captured 2026-10-23): with YouTube's Shorts tools you can remix others' content via Green Screen (sample as background, visual only or audio+video), Cut (a 1-5 second audio+video segment) or Sound (up to 90 s of audio; some partner content limited to 30 s); sources are credited automatically (sound page / link in the player). Remixing is opt-out: creators' Shorts and long-form are available to remix by default unless they turn off "Shorts remixing" in Studio; private videos and some third-party-claimed videos are unavailable. Copyrighted material used outside YouTube's tools can get Content ID claims or removals. Edit into a Short: only the owner can do it, for public long-form uploads (not private/unlisted or third-party-claimed); select up to 60 s and optionally record more segments up to 60 s. Completes CA-DR-0001-04 (C3-B336-04).
• articleEU AI Act Article 50 for creators (in force 2 Aug 2026): who must label deepfakes, the lighter regime for evidently artistic or fictional work, and why "personal use" rarely covers monetised channels
  Corrected 2026-10-24 - see C3-B1049-01; the original statements below are kept for history and are superseded where the correction says so. Primary (Commission guidelines, 20 July 2026, non-binding; CJEU has final say). Four duties: 50(1) providers tell people they interact with AI; 50(2) providers mark synthetic image/video/audio/text outputs in a machine-readable, detectable way (exception for assistive standard editing that does not substantially alter input); 50(3) emotion recognition/biometric categorisation notices; 50(4) DEPLOYERS must disclose deep fakes (and AI text published to inform the public on matters of public interest, unless under human editorial control). Applies from 2 August 2026; disclosure must be clear and distinguishable at the latest at first exposure and meet accessibility requirements (50(5)). Personal-use carve-out (Art. 2(10)): only "purely personal, non-professional" use by natural persons is excluded; any activity yielding economic benefit on a regula...
• articleWhat is an intimacy coordinator on a film or TV production, when does a guild say one should be hired, and what are they expected to do in preproduction, on set and in post?
  Corrected 2026-10-24 - see C3-B1058-01; the original statements below are kept for history and are superseded where the correction says so. SAG-AFTRA's Standards and Protocols (cover-dated February 2024) define an intimacy coordinator (IC) as an advocate and liaison between actors and production who may also act as movement coach or choreographer, and say ICs should be hired for scenes with nudity or simulated sex, or on request for other intimate and hyper-exposed scenes. The protocols list preproduction duties (script-breakdown discussion, one-on-one consent confirmation on rider language, continued consent in rehearsal, coordination with costume, props and makeup), on-set duties (rider and closed-set review, continued consent, minors) and a single optional post-production duty. Bectu's UK guidance (Oct 2022 edition) agrees on early hiring but says IC services usually stop before post unless negotiated.
• articleWhat happens to file names when several ComfyUI runs write with the same filename_prefix at once, and how do I keep outputs unique and traceable?
  Problem. Parallel jobs may collide on output names. Conditions. Core SaveImage; label: inference from code, not tested. Method. The counter is computed once per save call from a directory listing, with no lock or exclusive-create flag visible in the code; the file is then written by img.save to the computed name. Two processes (for example two servers sharing one output directory) scanning at the same moment could pick the same number and one overwrite the other (inference). Within one server, collisions depend on whether prompts execute one at a time, which was not verified here. Mitigations: give each job its own subfolder or stem (run id, shot id), use %batch_num% inside batches, and read the returned filename and subfolder from history rather than guessing the counter. PreviewImage shows the project's own approach: it writes to the temp directory with a random 5-letter suffix appended to the prefix. Metadata: unless --disable-metadata is set, the prompt and workflow are embedded...
• articleHow does ComfyUI SaveImage turn filename_prefix into a path and file name: subfolders, counter, 5-digit padding, and which % tokens does the server substitute?
  Problem. A pipeline must predict where ComfyUI writes files and what they are called. Conditions. Core SaveImage at commit fb3befd. Method. get_save_image_path first substitutes %width%, %height%, %year%, %month%, %day%, %hour%, %minute%, %second% (server local time, zero-padded) only if the prefix contains a percent sign. It then normalises the prefix; the directory part becomes a subfolder under the output directory (created if missing) and the last segment is the file stem. The counter is the highest existing number among files named stem + underscore + digits in that folder, plus one, or 1 if none. SaveImage writes stem_NNNNN_.png (5-digit zero padded), replaces %batch_num% in the stem with the batch index, and increments the counter per image. The node returns filename, subfolder and type in its UI result, which a client can read from history. Example. Prefix 'proj/shot01/take' gives output/proj/shot01/take_00001_.png. Failure modes. The input tooltip also advertises %date:yyyy...
• articleWhich ComfyUI flags redirect the input, output and temp directories for a pipeline, and which gotchas apply?
  Problem: keeping job outputs and inputs in controlled locations. Conditions: fb3befd. Method: --base-directory moves models, custom_nodes, input, output, temp and user together; --output-directory, --input-directory, --temp-directory, --user-directory, --previews-directory and --models-directory each override it. Output, input and previews paths are made absolute. Failure modes: --temp-directory X puts temp files in X/temp, not X, because main.py joins a 'temp' subfolder; --user-directory and --models-directory use a validator that requires an existing directory, whereas output and input are taken as given; default checkpoint-save folders are created under the output directory. Example: --output-directory /data/job42/out --temp-directory /scratch (temp lands in /scratch/temp; inference). Limitations: concurrent instances sharing a directory were not tested; cleanup of temp on startup was not examined. Version: fb3befd.
• articleDoes ComfyUI expose its console log over HTTP, and how much does it keep?
  Problem: reading server logs remotely from a pipeline. Conditions: fb3befd; reachable ComfyUI server. Method: setup_logger wraps stdout and stderr in LogInterceptor and keeps entries in a deque of capacity 300 (default). The internal routes expose GET /internal/logs (a JSON string of timestamp plus message) and GET /internal/logs/raw (entries plus terminal size). Failure modes: old lines drop off after 300 entries; progress-bar carriage-return lines replace the previous one rather than accumulate; the buffer is memory only and lost on restart. Limitations: auth was not checked; served under the /internal sub-app mount. Version: fb3befd.
• articleHow do I schedule a YouTube Premiere, what do viewers see before it starts, and what does YouTube advise on lead time?
  Problem. Using a scheduled Premiere to concentrate early viewing. Conditions. Not for Shorts; not for 360/VR180 or output above 1080p. Method. Upload, click Schedule, enter date and time, check Set as Premiere, optionally Set up Premiere for countdown theme and length. YouTube creates a public watch page before the start that can be shared; viewers can set reminders and get a notification about 30 minutes before and again at start. Premieres appear in search, home and recommendations like regular uploads. Tips page advises scheduling at least 24 hours ahead so audiences worldwide see it in subscriptions. Failure modes. Strikes make a Premiere private. Limitations. The 24-hour advice is from a tips page and is a recommendation, not a requirement; no data given. Version/date. Fetched 2026-10-24; undated.
• articleHow does YouTube scheduled publishing work (time zone, editing, strikes) and what date does the watch page show?
  Problem. Releasing a video at a set time. Conditions. Video set to scheduled or private on the upload page. Method. In Studio: Create > Upload videos > upload > Schedule card > choose date, time and time zone > Schedule. To change the time, keep visibility Private, Edit Draft, pick a new time; set Public to publish immediately. Failure modes. A Community Guidelines strike freezes publishing: the video goes private for the penalty and must be rescheduled. The watch-page date uses Pacific time, so a time zone ahead of PST can show a different date on the watch page than in Studio. Limitations. Page does not state lead-time minimums. Version/date. Fetched 2026-10-24; undated.
• articleDoes YouTube say upload time affects recommendations or long-term performance, and for which formats does it say timing matters?
  Problem. Whether to optimise the clock time of a normal upload. Conditions. Stated for YouTube search and discovery generally. Method. Treat clock time as low-leverage for regular uploads: YouTube says publish time is not known to impact long-term performance and that recommendations aim to match the video to viewers regardless of upload date; treat timing as relevant for Live and Premiere, where viewers gather at one moment. Publishing when the audience is active may help early viewership, per YouTube, without long-term effect. Failure modes. Reading 'not known to impact' as 'proven no impact'; reading early-viewership benefit as a ranking boost. Limitations. The FAQ gives no numbers or experiment. Version/date. FAQ fetched 2026-10-24; undated.
• articleWhat does YouTube Help say the 'When your viewers are on YouTube' report covers (28-day window, purpose), and what does that page not state about time zone or thresholds?
  Problem. Choosing a Premiere or live-stream slot from audience activity. Conditions. YouTube Studio > Analytics > Audience. Method. Open the Audience tab; the report shows when viewers are online across YouTube (not only on your channel) over the last 28 days; YouTube names Premiere and live-stream planning and community building as uses. Failure modes. The fetched Audience page gives no time-zone basis, minimum-audience threshold or refresh cadence for this report, so do not assume the displayed hours are in your local zone or that small channels get a populated chart (inference, see E3). Limitations. Other Audience reports use 28-day or 7-day windows (monthly audience: previous 28 days from latest selected day). Version/date. Page fetched 2026-10-24; page carries no revision date.
• articleHow do I run a generation worker with Hugging Face offline mode, and what does it do to a cache hit versus an API call?
  Problem. Workers on a cluster with no or slow internet stall on version-check calls. Conditions. Cache already populated (ideally by a pinned prefetch). Method. Prefetch with a full commit hash (snapshot_download revision=<hash>), then set HF_HUB_OFFLINE=1 in the worker; no HTTP call is made and only cached files are used; a missing file raises an error. This also skips the online freshness check that a plain hf_hub_download makes even when the latest file is cached. Failure modes. Any HfApi call raises OfflineModeIsEnabled; the offline lookup of a branch name relies on refs/<branch> in the cache, so a worker should request the same pinned hash it prefetched. Limitations. Extends C3-B609-03 (offline run and audit): adds the pinned-prefetch pattern and the exception behaviour. Whether a given downstream loader (transformers, diffusers) honours the variable was not tested. Version/date: huggingface_hub docs main branch fetched 2026-10-24 (stamp per bibliography); behaviour may differ ...
• articleWhat happens if --front-end-version cannot be fetched, and does --front-end-root get any fallback?
  Problem. A pinned frontend fails to download, so what UI do you actually get. Conditions. --front-end-version set to a non-default value and no --front-end-root. Method. FrontendManager.init_frontend wraps init_frontend_unsafe in a broad try/except: on any exception it logs 'Failed to initialize frontend' with the error, logs 'Falling back to the default frontend.' and returns the pip-package frontend path. Server startup does not abort. --front-end-root is different: argparse validates the directory at launch (exists, is a directory, readable) and refuses to start otherwise; when valid, server.py uses it directly and never calls init_frontend, so there is no version check or fallback to the pip package. Failure modes. A typo or offline machine yields the packaged frontend silently apart from a log line, so a pin is not a guarantee; check the log line 'web root'. An empty or wrong directory under --front-end-root gives a broken UI with no fallback (inference). Limitations. Interacti...
• articleWhat values can --front-end-version take, where does ComfyUI download that frontend from, and where does it store it?
  Problem. Pinning the ComfyUI web frontend independently of the core install. Conditions. Any launch of main.py without --front-end-root. Method. Pass --front-end-version owner/repo@version. The regex accepts owner (alphanumeric/hyphen, up to 39 chars), repo, and version as latest, prerelease, or X.Y.Z with optional v prefix and suffix. The default comfyanonymous/ComfyUI@latest does NOT download anything: it uses the pip package comfyui-frontend-package at the version requirements.txt pins. Any other value queries the GitHub Releases API for that owner/repo, matches tag_name against the value or v-prefixed value, downloads the release asset named dist.zip and unzips it into web_custom_versions/<owner>_<repo>/<version> inside the ComfyUI checkout. A v-prefixed pin reuses an existing folder without network. Failure modes. A missing release raises ValueError; a release without dist.zip raises ValueError. GitHub rate limits or no internet also fail (see C3-B807-02). Limitations. Third-pa...
• articleHow does Take Recorder's slate and take numbering turn a recording into a Level Sequence with subsequences?
  Problem. Keeping takes organised for shot-by-shot work. Conditions. Take Recorder panel open. Method. Set slate name, take number, description, fps and Record Speed; record via the red button, stop with Esc. The pending take is a Level Sequence; sources record into a subsequence (colour-coded per source); Takes Browser lists saved takes with metadata in column view; Review Last Recording opens the result; Root Take Save Dir and Take Save Dir use {take}/{slate} tokens; auto-save keeps sequences and subscenes. Failure modes. Reusing a take number triggers a warning (click to jump to next number); unsaved assets are lost. Limitations. How a take is placed into a Level Sequence with Shots is not shown in this page. Version/date. Current page as fetched.
• articleHow do Take Recorder timecode, clock source and Live Link 'Use Source Timecode' settings affect sync with mocap and other devices?
  Problem. Takes from different devices must line up later. Conditions. A timecode provider (defaults to UE's) and Live Link subjects. Method. Set Recording Clock Source (Audio, Relative Timecode, Timecode, Play Every Frame); enable Start at Current Timecode to begin at the current timecode instead of time 0; enable Record Timecode to write timecode metadata into track sections; on a Live Link source enable Use Source Timecode so the subject's timecode is used, and Discard Samples Before Start to drop earlier samples. Failure modes. With Use Source Timecode off, data is keyed on the Live Link thread using engine time and no timecode track is created, so source-to-sequence relation is lost. Limitations. Clock modes listed do not respond to pause states. Version/date. Current page as fetched.
• articleHow is a mobile live stream archive created and what privacy default can it get, beyond the 12-hour archive limit?
  Problem. Knowing what exists after a live stream ends. Conditions. Streams under 12 hours archive automatically for encoder, webcam and mobile; 1440p and 2160p streams also archive. Method. On mobile, tapping Finish creates an archive on the channel and a recap; a Short highlight can be saved and lands as private by default. Privacy can be edited, or the archive deleted, from My videos or the Content page. Failure modes. A stream over 12 hours may not be captured at all; for restricted streams the archive defaults to private and can take weeks to reflect. Limitations. Prior finding covers the limit itself; this adds privacy defaults and highlights. Keep a local recording as YouTube recommends. Version/date. Fetched 2026-10-24.
• articleCan a Premiere or live stream redirect viewers, and what happens to viewers and chat when it ends?
  Problem. Moving an audience from a Premiere or stream to another event. Conditions. Sender has over 1,000 subscribers and no Community Guideline strikes; redirecting to another channel's stream needs that channel's permission. Method. In Studio hover the video, Edit, Redirect > Add; a live stream can redirect to a Premiere, and a Premiere can redirect when it ends (viewers are sent after the Premiere ends). The receiving channel sets who may redirect: subscribed channels (default, unless subscriptions private), all channels, or a specific list of up to 100. Live Chat tools (pin one message at a time, polls, Q&A) apply to Premieres as well as streams, and Q&A sessions appear in Chat Replay. Failure modes. The all-channels setting cannot be combined with the subscribed-channels setting or the manual list. Limitations. The page does not say what happens to the chat window at the moment of redirect. Version/date. Fetched 2026-10-24.
• articleWho can add a trailer to a YouTube Premiere, what must the trailer be, and which ads and fan-funding work during a Premiere?
  Problem. Adding a teaser and monetising the pre-start page. Conditions. Trailer: more than 1,000 subscribers and no Community Guideline strikes. Method. Upload the trailer as a normal video; in Studio schedule the main video as Premiere, Set up Premiere, then Add a trailer. Trailer must be 15 seconds to 3 minutes, any supported video type, ideally the same aspect ratio and resolution, non-infringing, guideline-compliant and not a previously premiered video. Ads: if eligible, pre-rolls only during the Premiere; mid-roll and post-roll are unavailable; Super Chat, Super Stickers and memberships (members-only chat) can be on before and during. Failure modes. Reusing a premiered video as the trailer is disallowed. Limitations. Ad eligibility defers to separate channel pages. Version/date. Fetched 2026-10-24.
• articleWhat do viewers and the video itself experience during and after a YouTube Premiere (countdown, seeking, chat, view counts, reminders)?
  Problem. Designing a Premiere so the countdown, chat and later watch behaviour match expectations. Conditions. A Premiere that has reached its start time. Method. Before start the public watch page exists, appears in search/home/recommendations, and accepts reminders, comments and chat. At start the chosen countdown theme runs for the chosen length, then the video plays for everyone together. Afterwards the video stays as a regular upload without the countdown, chat replay is available and the Premiere view count transfers to the video. Failure modes. Viewers can rewind but cannot skip ahead past what has been shown live; do not bake a countdown into the edit, since YouTube adds its own. Limitations. The two Help pages describe the countdown differently (a chosen length on one, two minutes before start on the other), so treat length as a setting to verify in Studio. Version/date. Fetched 2026-10-24.
• articleWhat can and can't be a YouTube Premiere, and what happens if I create one with a strike or a Short?
  Problem. Choosing whether a finished upload can be premiered. Conditions. Uploading through YouTube Studio. Method. Create > Upload videos, then either set as instant Premiere (premieres when processing finishes) or schedule a date and time and tick Set as Premiere; optionally Set up Premiere for countdown theme and length. Failure modes. Shorts are not supported; 360/VR180 or output above 1080p is not supported; with a Community Guidelines strike the Premiere is set private for the penalty period and must be rescheduled. Limitations. Help page does not state a maximum video length or minimum subscriber count for basic Premieres (a subscriber minimum is stated only for trailers). Version/date. Help page fetched 2026-10-24.
• articleWhat conditions must hold to record Unity Recorder Accumulation successfully, so a render does not silently fail or show a progress bar?
  Problem. Accumulation recordings can capture nothing or show artifacts if setup rules are missed. Conditions. Recorder 5.1.7. Method (checklist). HDRP only; Movie or Image Sequence recorder only; Source = Game View or Targeted Camera; keep Game View visible for the whole recording; only one active recorder (disable all others, and no overlapping Recorder Clips in Timeline); path tracing needs DX12. Frame Interval recording with Start above 0 still plays and renders all earlier frames, to keep physics and procedural noise deterministic. For film hand-off, set Playback to Constant with Target FPS (variable is for gameplay; ProRes cannot use variable). Failure modes. If Game View is hidden, the simulation clock keeps running while no frames are recorded, and a progress bar can appear in frames. Cannot run in -batchmode. Limitations. Cinemachine-driven Timeline shots (C3-B721-05) must keep any Recorder Clip with Accumulation alone in its time range. Version/date. Recorder 5.1.7 docs, fe...
• articleWhat chapter format, count and title rules does Apple Podcasts state, when does it auto-create chapters, and how do chapters relate to transcripts?
  Problem: make chapters display well in Apple Podcasts. Conditions: chapters provided in the episode description, in the RSS feed via the podcast:chapters tag (through a supporting host), or in file metadata (MP4 header, ID3 on MP3 or AAC). Method: in a description, start the first chapter at 00:00:00 with at least three chapters. Stated guidelines: at least three chapters; no more than six per hour; provide chapters for episodes over 10 minutes; chapters no shorter than two minutes; titles at most 45 characters and fewer than five words; avoid repeated words; title case; numbers one to nine spelled out, digits above 10. If none are provided, Apple creates chapters (iOS 26.2 onward, English full and bonus episodes, not trailers or episodes under 10 minutes) labelled Automatically Created; the TXT list can be downloaded in Apple Podcasts Connect, edited and added to the description. Chapter titles appear as section headers in the transcript view. Failure modes: chapters shorter than t...
• articleHow do I supply my own transcript to Apple Podcasts, what does Apple generate itself, and which languages, formats and limits apply?
  Problem: control whether Apple Podcasts shows auto-generated or publisher-provided transcripts. Conditions: episodes distributed to the Apple Podcasts catalogue (private feeds are not processed, so show no transcripts); iOS 17.4 or later; supported languages English, Danish, Dutch, Finnish, French, German, Italian, Norwegian, Portuguese, Spanish and Swedish. Method: by default Apple generates transcripts after publication and labels them Automatically generated; to use your own, change the show's transcript setting in Apple Podcasts Connect (Availability tab), link the file with the RSS transcript tag, and set episodes to Display transcripts I provide; the app then shows Provided by the show name. Accepted file types are VTT or SRT, and a VTT lets every speaker be named per line. For subscriber episodes upload VTT or SRT in Connect. Apple lets you download its transcript, edit and relink it. Best practice: correct language, spelling of host and guest names in descriptions, correct e...
• articleWhat protections and recourse do YouTube channel members have: slow mode, perk reports, refunds and notification timing?
  Problem: Creators should know what members are entitled to. Conditions: paid channel members. Method: slow mode does not apply to active paid members. Members can report perks that breach the Community Guidelines (sexual, violent, hateful, misleading or spam) via Join or See perks. Refunds are available for defective, unavailable or non-performing perks through support, but not for partially elapsed billing periods; Apple-billed members go to Apple. Notifications fire for new members-only posts, videos and live streams and 30 minutes before a scheduled members-only stream. Failure modes: perks that are not delivered can trigger refunds. Limitations: undated; Apple path outside YouTube.
• articleWhat do YouTube's membership analytics numbers mean: total vs active vs lost members, billing period length, notifications for new members and CSV export?
  Problem: Membership counts differ by definition, so reports can mislead. Conditions: Studio Memberships tab and Analytics Audience. Method: Total members includes cancelled members still inside the paid period; Active members are only those with live subscriptions, so total minus cancelled equals active. Members Lost are cancelled members whose access ended. A billing period can be 28, 30 or 31 days by calendar month. The tab shows revenue for the last period, members by level and cancellation feedback; the member table can be exported to CSV. Offline sign-ups send no notification, so check the tab. Failure modes: using Total as retention overstates active base. Limitations: the CSV and Members API fields were not tested; undated page.
• articleWhat destructive or delayed steps exist in managing YouTube memberships: level review time, deleting a level, turning memberships off, and the free trial?
  Problem: Setup changes can wipe members or delay launch. Conditions: creator in YouTube Studio, Earn, Memberships. Method: new or edited levels and perks are reviewed against the membership policies before going live, about a day. Memberships may take up to 2 days to activate after Partner Program acceptance. Removing a level deletes its members, who lose perks at once and are refunded their last month. Turning memberships off does not save levels, members or perks, cancels recurring payments, and members must rejoin if you turn it on again. A one-month free trial is offered automatically to eligible viewers, one per viewer across all creators; creators can opt out with the toggle. Failure modes: deleting a level to restructure removes paying members. Limitations: the page does not describe a way to migrate members between levels (inference); undated.
• articleHow do members-first (members-only to public) videos and members-only Shorts behave: what do non-members see, who is notified, and what does YouTube report about performance?
  Problem: A creator needs to know how restricted-visibility uploads surface and notify. Conditions: memberships on; levels optional. Method: for early access set visibility to Members-only to public and pick the date and time it flips public; members are told it is members-first and all subscribers are notified at the flip. Members-only videos can appear in members' Home and subscription feeds and on the Memberships, Content and Posts tabs; non-members may see thumbnail and title but cannot watch, and the URL can be shared publicly via cards, posts and playlists. Members-only Shorts are up to 60 seconds, square or vertical, and send no notification; if upload-and-record in one flow hides the option, upload unlisted then switch. YouTube reports early-access videos performed the same after going public, and 20 percent of new members came via promotion. Failure modes: Shorts have no notification, so tell members elsewhere. Limitations: YouTube's figures have no stated n and are for Jan-...
• articleHow does YouTube bill a membership upgrade, downgrade, cancellation and reactivation, and does the help page's upgrade example match its own prose?
  Problem: Changing level mid-cycle has billing consequences that affect how a creator should advise members. Conditions: web or app billing; downgrades are blocked on Google Play. Method: an upgrade gives immediate access, charges an adjusted amount for the remaining days, moves the billing date to the upgrade day and charges the new price next cycle. A downgrade keeps the original level until the next billing date, leaves the billing date unchanged and applies the lower price then. Cancelling stops future charges but perks stay to the end of the cycle; reactivating in the same cycle is not charged again until it ends. Badge loyalty is kept on both changes. Failure modes: the page's worked example ($4.99 to $9.99 with half a month left, charged $7.50) does not equal the prose 'only charged the difference', which would be half of $5.00, i.e. $2.50. Limitations: treat the example as unreliable; actual amounts, tax and platform fees were not tested.
• articleWhat is YouTube's 'paused mode' for channel memberships, what triggers it, and what happens to members' payments, including the 120-day limit?
  Problem: A channel's membership program can stop delivering without the creator choosing to cancel it. Conditions: a channel changes MCNs, is set made for kids, or cannot monetize. Method: while paused, the channel cannot earn from memberships or deliver perks and benefits, and active members' recurring payment, billing cycle and access are paused. A pause and unpause within one billing cycle changes nothing in billing. Memberships can stay paused at most 120 days, after which memberships and recurring payments are cancelled. Failure modes: members who signed up on iOS or Android may have recurring payments cancelled if the pause is still on after their billing period ends, and must rejoin once unpaused. Limitations: this page is written for members; it does not say how a creator is notified or how quickly an unpause follows a fix.
• articleHow long do Gemini and Vertex keep Google-side files and interaction results, and where must a pipeline save outputs?
  Problem. Batch inputs and Google-hosted video URIs have their own lifetimes that bound when a pipeline can read them. Conditions. Gemini API Files API and Omni video URI delivery; Vertex AI Veo interactions and storageUri. Method. Gemini Files: files are deleted automatically after 48 hours, with 20 GB per project and 2 GB per file; batch input files are uploaded through this API. Omni: videos over 4MB are returned as a Google-hosted URI to poll until ACTIVE before download. Vertex: stored and asynchronous interactions are retained up to 7 days; requests can name a Cloud Storage storageUri output location. Save outputs into your own bucket or storage on completion. Failure modes. Re-reading a 48-hour file after expiry. Limitations. The Omni page read does not state the lifetime of the delivery URI. Version and date. Docs read 2026-10-23.
• articleHow does a widely copied idempotency implementation (Stripe) behave on retries, validation failures, concurrent requests and key expiry, and which parts differ from the IETF draft?
  Problem. Teams copy 'Stripe-style' idempotency for job APIs without knowing what is stored and for how long. Conditions. Stripe is a payments API, not a generation API; it is the reference implementation the IETF draft cites. This record keeps Stripe's statements separate from the draft's. Stripe's documented behaviour (API v1). The server saves the status code and body of the first request that actually starts executing and replays them on retry, including 500 errors; keys are up to 255 characters; keys may be pruned after at least 24 hours and a reused key then creates a new request; incoming parameters are compared with the original and a mismatch is an error; requests that fail validation or that conflict with a concurrently executing request are not saved, so they can be retried; all POST requests accept keys and GET/DELETE ignore them. API v2 instead retries failed or partially failed work to completion and does not repeat successful operations. Contrast with the IETF draft. T...
• articleHow do YouTube gift memberships work: who can gift, where, at what price, who can receive, and what the recipient gets?
  Problem: A creator or viewer wants to give others a channel membership and needs the documented mechanics. Conditions: channel has gift memberships turned on; gifting is done in the Android app per the cited steps. Method: the gifter must be watching a live stream or Premiere on that channel and use Membership gifting in live chat, choosing the number of recipients. Gifts are priced at the closest highest level up to and including $9.99. Recipients must have opted in (signed in with a non-Brand-Account channel) and be subscribed; current channel members are not eligible. A gift is one month of perks, non-recurring, non-refundable and not cashable. Failure modes: a viewer on a Brand Account cannot opt in; the creator may end the stream before the gift is announced, but the gift is still distributed; gifter name, count and picture are public and may reach the channel via the Data API. Limitations: help page lists steps for Android; the page is undated.
• articleDo official ComfyUI templates really avoid third-party custom nodes, and how should a template author record node versions?
  Problem. The docs rule says official templates avoid third-party nodes so users need no extra installs, yet a portable-workflow plan needs to know which templates still need packs. Conditions. Contributing to or consuming official templates. Method. Docs: official templates must not use third-party nodes. README authoring steps: create the workflow with --disable-all-custom-nodes so extensions do not add metadata to the saved JSON, and optionally embed the node version in the node's properties (cnr_id, ver) the same way as models. Check reality in the manifest: 79 of 718 entries list requiresCustomNodes, led by comfyui-kjnodes x41, comfyui_essentials x29, comfyui-videohelpersuite x24. So the rule describes the intent of the core category set, while packs appear on those entries (cause not stated in the sources; they may be custom-node or Applied templates, inference). Failure modes. Assuming every template runs on a bare install; saving a template with custom nodes enabled and shipp...
• articleThe docs Templates page shows version pins for updating templates: can I copy them, or are they out of date?
  Problem. The docs page tells users to update the template dependency when new templates are missing, and shows an example trio of pins. Conditions. Following that page's 'How to update templates?' section. Method. Treat the three pinned numbers in the docs as an illustration of the three packages (frontend package, workflow templates, embedded docs) and read the real pins from ComfyUI/requirements.txt of your checkout. At fetch time the docs example read frontend 1.24.4, templates 0.1.52, embedded-docs 0.2.4, while ComfyUI master's requirements.txt read frontend 1.57.1, templates 0.11.96, embedded-docs 0.5.14. Failure modes. Pinning the docs numbers would downgrade a modern install by many versions. Limitations. Docs example is an example, not a claim of current numbers; the page itself says to check requirements.txt. Version/date. 2026-10-24 UTC.
• articleHow are the official ComfyUI workflow templates packaged and versioned for pip, and which pin do I check when templates look stale?
  Problem. Template pickers show different workflows on two machines, and the cause is a package pin rather than the workflow file. Conditions. A ComfyUI install that gets templates from the Python package comfyui-workflow-templates, not from a git checkout. Method. The repo is organised package-per-media: a core manifest/loader package, per-media packages holding JSON and previews, a blueprints package, and a meta package (root pyproject, version 0.11.96) that pins each part with exact == versions. Extras (json, assets, api, video, image, other, all) select parts. Five media wheels are 'frozen' (not rebuilt in routine PRs) because PyPI limits a wheel file to about 100 MB; new media goes to media-assets-02. ComfyUI master's requirements.txt pins comfyui-workflow-templates==0.11.96 next to comfyui-frontend-package==1.57.1. To compare machines, read the meta-package version, not individual media wheels. Failure modes. Frozen wheels keep old content by design, so new templates arrive in ...
• articleHow do I turn my own long-form video into a Short, what are the limits, why is the option missing, and how is it credited?
  Problem. Repurposing long-form into Shorts has hard limits. Conditions. Own, public, long-form videos without third-party claims, opted in to sampling. Method. Watch page, Remix then Edit into a Short, select up to 60 seconds, add text or filters, upload; if you select under 60 seconds you can record more with the Shorts camera, e.g. 45 plus 15. The Short links back to the original. Audio Library music cannot be used. Missing option: Studio, Content, video, Show more, Shorts remixing, tick Allow people to sample this content, Save. Only the owner can do this, unlike general remixing. Failure modes. Private, unlisted or claimed videos do not offer it. Limitations. 60-second cap is stated here although Shorts can be 3 minutes (inference: help pages updated separately; unconfirmed). Version and date. Undated.
• articleHow do I opt my Shorts out of remixing, what notifications and analytics do I get when others remix, and who can opt out in bulk?
  Problem. Shorts are remixable by default; creators need to know the control and the feedback loop. Conditions. Own videos in YouTube Studio; Content Manager partners have extra controls. Method. Studio, Content, open the video, Show more, Shorts remixing, choose allow or not, Save; the setting can also be edited in bulk and at upload. Creators can opt out of video remixing; Content Manager partners can opt out of audio and video, and restricting all of a partner's videos needs the partner manager. Remix notifications are one summary a day, at most three times a week. Views from visual remixes appear in reach reports under the Remixed video traffic source. Failure modes. Opting out later mutes, unlists and schedules deletion of audio remixes (see C3-B673-14). Limitations. Page gives no remix counts or benchmarks. Version and date. Undated.
• articleHow does YouTube decide that a square or vertical video up to three minutes is a Short, which uploads stay long-form by date and channel type, and how do I keep a short vertical video out of Shorts?
  Problem. Whether a clip lands in the Shorts feed or as long-form depends on upload date, shape and length. Conditions. Standard channels: uploads on or after 15 Oct 2024, square or vertical, up to 3 minutes, are categorised as Shorts and monetised under Shorts revenue sharing; earlier uploads stay long-form. Official Artist Channels: same rule from 8 Dec 2025. Method. Upload via the app or Studio; from a computer, Studio takes up to 15 files at a time, each up to 3 minutes and square or vertical, and each needs its details completed before publishing. To avoid Shorts classification, use a wider ratio such as 16:9. Failure modes. A 2:50 vertical clip meant as long-form becomes a Short. Older uploads are not reclassified. Limitations. Page gives no minimum length and no resolution cap; see C3-B791-02 for claim handling. Version and date. Help pages undated; text as fetched.
• articleHow did the 24 August 2026 view-count change affect the Data and Analytics APIs (viewCount versus engagedViews), and what does it mean for time series an agent stores?
  Problem. A long-running series of 'views' may have a definitional break. Conditions. Any view series spanning 24 August 2026. Method. Data API states that starting 24 August 2026 viewCount for all formats (long-form, Live, Shorts) counts a view the moment playback begins (including autoplay, hover-play and click/tap). Analytics adds engagedViews (past the first frame or click/tap). The revision history table lists: View (updated), Engaged View and Thumbnail Impression (unchanged); engaged views anchor monetisation and most core analytics such as CTR and average view duration. Practical rule (inference): flag 24 August 2026 as a break in stored series, store viewCount and engagedViews separately, and compare Shorts and long-form only after that date on the same definition. Failure modes. Treating a jump in public views as audience growth. Limitations. Size of the effect per channel is not reported. Version and date. Fetched 2026-10-23.
• articleWhat breaks if I send a workflow that uses subgraphs or subgraph blueprints to someone on an older ComfyUI frontend, and which minimum versions does the documentation state?
  Problem: sharing a workflow with a collaborator on an older install silently loses structure. Conditions: recipient frontend older than the first subgraph release. Method: the user guide states subgraphs need frontend 1.24.3 or later, the parameters panel needs ComfyUI v0.3.66, and publishing a subgraph to the node library (blueprints) needs frontend 1.27.7. The frontend stamps extra.frontendVersion when converting a graph for the API, and the schema carries a version number whose bumps are handled in deserialisation. Pre-flight check: read definitions.subgraphs and any node whose type is a GUID; if the recipient frontend is below 1.24.3, expect those nodes to show as missing node types (a UUID is not a registered class); on intermediate versions, expect promoted widgets or blueprints to be missing. Safer alternatives: export API-format JSON (flattened, no subgraph dependency, but it loses layout and subgraph structure), or pin the same frontend package version on both sides. Failur...
• articleGiven only these public pages, how should an agent build and caveat a cost estimate for an AI-assisted shot list?
  Corrected 2026-10-24 - see CUR-0618-01; the original statements below are kept for history and are superseded where the correction says so. Proposed procedure (synthesis): list shots with duration, resolution and audio; map each to a price cell in one unit family; round durations up to the vendor allowed values; multiply by an assumed take count (no source states a retake rate); add stills at per-image prices; check against spend and concurrency caps; report a range with capture dates. Worked example, 12 shots x 6 s x 3 takes = 216 generated seconds at 720p: Veo 3.1 Lite $10.80, Gemini Omni Flash about $21.89, Veo 3.1 Fast $21.60, Runway gen4.5 $25.92, Veo 3.1 Standard $86.40 (arithmetic in work/estimate.py; assumptions, not measured). The sources limit this: failed-generation billing, retakes, taxes and account discounts are mostly unstated, and some pages disagree with themselves.
• articleWhat do the public pages state for video generation price per second by resolution, audio and duration tier, across Google, Runway, Luma, fal, Replicate and Pika?
  Corrected 2026-10-24 - see CUR-0618-01; the original statements below are kept for history and are superseded where the correction says so. Dated 2026-10-22 captures: Gemini API Veo 3.1 Standard $0.40/s (720p and 1080p), $0.60/s 4k; Fast $0.10/$0.12/$0.30 per s at 720p/1080p/4k; Lite $0.05/$0.08 per s; Omni Flash about $0.10/s at 720p from a token rate. Runway API lists per-second credits (credit = $0.01) for many third-party models, e.g. veo3.1 with audio 40 credits/s and gen4.5 12 credits/s. Luma Ray3.2 lists per-clip prices at 540p/720p/1080p. fal lists Kling v3 Standard at $0.084/s audio off and $0.126/s audio on on the model page. Pika sells consumer credits. Resolution, audio, and duration tiers change the unit price; Veo 1080p and 4k are limited to 8 s.
• articleWhat fields do publishers and libraries ask for in a sync quote request (portion, use, term, territory, media, dates, budget), and where do their term and territory defaults disagree?
  Corrected 2026-10-23 - see C3-B622-04; the original statements below are kept for history and are superseded where the correction says so. Wise Music's 2024 web-video request form lists: composition, composer, publisher(s), portion used, timing of each portion, description of use (platform and handle), paid-media flag, term (up to three years, no perpetuity), territory (world by default unless geo-blocked), requested posting date, budget, number of other works, and says to submit 4-6 weeks ahead. Atomica's FAQ says a licence states use, territory and term and that for broadcast, streaming or theatrical it asks for territories, campaign duration, episode count and audience reach. Media Music Now's standard licence is any territory with no time limit. The pages disagree on term defaults (no perpetuity vs perpetual vs unlimited), so term and territory must be asked of each holder, not assumed.
• articleHow does Comfy API v2 let one client talk to Comfy Cloud, a dedicated deployment and a self-hosted ComfyUI, and what are its poll-first and output-URL rules?
  Problem. Orchestrating ComfyUI jobs from an application with durable job ids. Conditions. Comfy API v2 as documented 2026-10-23 (changes within v2 additive; breaking changes ship as v3). Method. One contract is served by three surfaces: Comfy Cloud (cloud.comfy.org), per-deployment endpoints (https://{deployment}.run.comfy.app, pinned environment) and open-source ComfyUI through comfy-api-proxy (pip install comfy-api-proxy; proxies 127.0.0.1:8188 and serves v2 on 127.0.0.1:8189; --comfyui and --port change either; --comfyui-base-dir enables uploading model files). Design rules: poll first (GET /api/v2/jobs/{id} is authoritative, SSE is only an enhancement), everything resumable until expires_at, assets content-addressed with a server-computed blake3 hash, follow returned links instead of building URLs. Output.url on a job output is an authenticated content route (401 for a third party); a signed storage URL is the shareable one but short-lived (the docs give about 6 hours on Comfy C...

More