Production notes
Where music enters the project when AI helps make your video or game
Working across image, code and video tools makes it easy to treat music as another interchangeable input. Map where the recording actually goes before adding it to that workflow.
More tools mean more asset handoffs
Images, code and final editing may live in separate tools. A single finished scene can conceal several services and copies of the source files.
For music, write down where you found the track and where it enters the finished work. Using AI elsewhere in the project does not automatically change permission for that recording.
Separate the final mix from model input
Adding music to a completed video in an editor differs from uploading it to another model to generate new audio. The latter introduces a separate input use that needs permission.
Kominami's public license distinguishes background use from restricted uses including AI training and redistribution. Compare the actual movement of the file with the terms, rather than assuming a convenient tool makes every use available.
Sharing the project changes the handoff
An exported video and an editable template can contain different assets. Including the original recording in a project archive raises a different permission question from showing a finished work.
Keep the track URL, acquisition date, license reference and scene notes together. Check permission if a handoff requires the original audio. Those small records become more useful as the number of tools grows.
Source: Kominami