Receive audio and prepare a video for publication

What this chapter helps you decide

This chapter combines official technical material with a proposed production exercise. Generation, performance, pricing and listening comparisons have not been run. It is a supplement to the creative production course and can also be read independently.

• Distinguish file receipt from permission to publish.
• Record the usage conditions of a musical work.
• Check processing and playback after an authorized upload.

1. 1File receipt
2. 2Material provenance
3. 3Publication permission

1. 1Permission confirmed
2. 2Delivery package
3. 3Authorized upload
4. 4Processing check

1. 1YouTube playback
2. 2Receiving-page playback
3. 3Record URL and verification date

1. 1Unknown rights or failed playback
2. 2Hold publication

This is an original conceptual workflow. The arrows show review order, not a product’s hidden architecture; a failure sends the work back to the responsible stage.

A received file still needs a publication decision

Receiving a music file or folder does not establish permission for a destination, audience or monetization. Check audio, artwork, video and lyrics separately. Establish the required author, performer or voice consent for the particular materials. Keep a file with unresolved permission out of the publication package. The producer chooses the work and acceptance reason, the editor checks the export, and the publisher checks permissions and destination status.

Check the applicable Suno terms

The terms checked here were revised August 10, 2026 and effective September 3, 2026. They condition commercial use on a permitted download through an approved channel under the applicable tier allocation, and separately restrict jointly owned remixes to non-commercial use. The paid-subscription FAQ, revised September 3, describes commercial rights for songs downloaded during subscription. Read both with the actual song’s acquisition history; a paid plan does not settle every material or remix restriction.

Record distinct permission questions

Permission under a service contract, permission for third-party materials and copyright protection of generated output are distinct. Suno does not guarantee copyright protection. Preserve the generation and download dates, plans at both dates, model, song ID, terms URL and effective date, source materials, remix parents and permission record. Do not remove provenance markings to conceal origin. This is a record-design exercise, not a legal clearance of an actual song; leave contradictions unresolved until the applicable conditions are established.

Prepare a publication package

Keep source audio, an editing project, release MP4, images, description and provenance note distinct. Version filenames and identify the accepted version. Export only the public information needed for delivery; do not paste billing records or private consent documents into a description. A complete package makes the release decision reviewable before any upload, account change or external posting.

Check YouTube settings when posting

The upload-limit help states a default fifteen-minute limit, longer uploads for verified accounts and a maximum of 256 GB or twelve hours, whichever is reached first. The GenAI disclosure help includes AI-generated music and music as the main focus of a video. Check the relevant AI-use disclosure and audience settings for the intended release. These are provider conditions checked on October 4, 2026, not evidence that an upload occurred.

Separate upload completion from delivery completion

Confirm the channel, visibility, schedule, description and monetization intention before an authorized post. Afterwards inspect processing, copyright checks and playback from beginning to end. An absence of warnings is not proof of permission. Treat limited visibility as a sharing decision rather than a guarantee of confidentiality. No audio, MP4 or YouTube URL has been created in this exercise.

Test the actual receiving page

Check the video on YouTube and in its intended page, including a narrow mobile view and deliberate user-started playback. The official IFrame API reference distinguishes private or removed videos (100), disabled embedding (101/150), and missing HTTP Referer or equivalent client identification (153). A working YouTube page therefore does not establish working embedded playback. Provide an ordinary watch link when a real authorized video exists. The Learn article renderer does not accept arbitrary iframes; this exercise specifies delivery checks without adding an embed or changing the renderer.

Use and revise the production record

The input is a brief naming the use, duration and destination, plus materials whose usage conditions can be checked. The outputs are the production note, review sheet and the exercise deliverable. Keep the selected original separate from the editing and release copies.

1. Confirm the exact files, destination and scope of publication permission.
2. Check the audio and image sources, applicable terms and generation/acquisition records.
3. Preserve source audio, prepare an MP4 and inspect the whole file.
4. Check duration, size, disclosure and audience settings at posting time.
5. After an authorized upload, verify upload and processing completion.
6. Test playback on YouTube and on the receiving page.
7. Record the video URL, visibility and verification date.

Symptom	Likely cause to investigate	Revision
Permission review was skipped because the plan was paid	The plan was assumed to settle material and remix restrictions.	Check the applicable terms, acquisition path and material provenance for each song.
Playback works on YouTube but fails on the receiving page	Visibility, embedding permission or client identification was not checked.	Inspect the actual destination and the player error; do not infer embedding success from upload success.

Make a publication checklist with empty deliverables

Assume receipt of an original 30-second instrumental cue and prepare a checklist from receipt to embedded playback. Leave the audio, video and YouTube URL uncreated. Name three conditions that stop publication.

Deliverable: A delivery list, provenance fields and publication checklist.

Completion criterion: The checklist identifies the stop points for unknown rights, missing permission and failed playback.

Execution status: not-run. This chapter contains no generated audio, timing log, listening result or completed publication.

Review checklist

• Receipt alone is not treated as publication permission.
• The effective terms date and acquisition conditions are recorded.
• The public URL and receiving-page playback have explicit verification fields.

Preserve null until there is evidence

This is the original supplement’s production-record template, preserved without filling its unknown values. not-run means the exercise has not executed. not-collected is reserved for a real run that failed to collect a particular value. Zero requires an observation; an empty URL must not become a fake playable sample. A permission record can refer to a private review record, while public exports contain only appropriate public attribution.

{
  "status": "not-run",
  "model": null,
  "modelVersion": null,
  "generatedAt": null,
  "downloadedAt": null,
  "generationPlan": null,
  "downloadPlan": null,
  "termsUrl": null,
  "termsEffectiveDate": null,
  "sourceMaterials": [],
  "remixParents": [],
  "permissionRecord": null,
  "audioFile": null,
  "sampleRateHz": null,
  "channels": null,
  "durationSeconds": null,
  "integratedLufs": null,
  "truePeakDbtp": null,
  "generationLatencySeconds": null,
  "editingMinutes": null,
  "costAmount": null,
  "costCurrency": null,
  "creditUse": null,
  "sampleUrl": null,
  "videoFile": null,
  "youtubeUrl": null,
  "embedVerifiedAt": null
}

Stop the release if the image permission is unknown, the exact file/destination is not authorized, or receiving-page playback fails. The deliverable is the reviewable package and checklist. Generating audio, buying a plan, signing into an account, uploading a video and verifying a real embed are later actions with their own evidence; none was performed for this port.

Use the local experiment ledger

Open the browser-local experiment ledger. Start with a planned record. Unknown values remain blank, and an executed record requires saved output evidence. The ledger does not run models or upload records. You can keep using the worksheet above as a separate document.