ClipCastClipCast

FAQ

Frequently asked questions about ClipCast.

What is Auto Plan vs Auto Upload?

Auto Plan (⏰) — When ON, newly imported videos get publish times assigned automatically based on your plan defaults (start date, time slots, time zone). When OFF, imported videos are not scheduled.

Auto Upload (🚀) — When ON, the app runs in the background and executes due scheduled jobs from the queue: YouTube uploads automatically; Instagram/TikTok use Manual Assist (opens browser, copies metadata). The app must be running for Auto Upload to work.

What is Silent Mode?

When Auto Upload is ON and a scheduled job is due for Instagram or TikTok:

  • Silent Mode OFF — The app opens the browser and Explorer, copies caption+hashtags automatically.
  • Silent Mode ON — No automatic opening. Use the Assist Next overlay to trigger assist when you are ready.

Can I have different publish times per platform?

Yes. Each video can have different schedule times for YouTube, Instagram, and TikTok. Click Schedule in each platform column to set times independently.

What are Targets (YT / IG / TT)?

Targets are per-video switches. Turn a platform ON to include it when you schedule or apply a plan. Targets persist per row but do not create scheduled jobs until you use Schedule or Plan.

What formats are supported?

Supported video formats: MP4, MOV, AVI, MKV, WEBM, FLV, WMV, M4V.

Where are exports stored?

By default, pipeline outputs (transcripts, metadata, exports) go to your Outputs folder. You can change this in Settings.

I have an NVIDIA GPU — why does ClipCast still use CPU / CUDA fails?

The app ships components that expect recent NVIDIA drivers and a working CUDA 12.x–compatible stack on Windows. If drivers are outdated, mismatched, or the CUDA smoke test fails, ClipCast falls back to CPU even though a GPU is listed. Update drivers from NVIDIA (or your OEM), reboot, then check Settings → Developer mode → Compute backend (CUDA smoke test, Fallback reason). See Troubleshooting on the site.

Do I need my own Google Cloud project for YouTube?

Yes. ClipCast does not bundle OAuth credentials. Create a Desktop app OAuth client in Google Cloud, enable YouTube Data API v3, configure the consent screen, then enter Client ID and Client secret under Settings → Integrations. Details: YouTube Connect & Upload.

YouTube won't connect — what to check?

  1. You added your own OAuth client (not a shared ID from this repo)—type Desktop app (not Web application).
  2. Settings → Integrations contains the correct Client ID and Secret (paste fully).
  3. YouTube Data API v3 is enabled in Google Cloud Console.
  4. OAuth consent screen is configured; add yourself as a test user if the app is in Testing.
  5. Then use the YouTube chip → Reconnect. Legacy: google_oauth_client.json in user data still migrates—see YouTube Connect & Upload.