Hi, this is a comment.
To get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.
Commenter avatars come from Gravatar.
Our next collaboration starts with a generated backing idea and a remotely recorded bass part. It works as an arrangement sketch, yet its texture might make the recording brief less clear. Alongside the guide, I can send tempo information, chords, the key, and notes on bass entrances. Is it useful to provide both the untouched guide and a revised version? The wording I found was suno fix in that search, though I have no personal results from the linked resource to report. The goal is a clear musical brief that does not turn an unwanted texture into an instruction. The bassist will work in a different recording application, so I would also welcome advice on export format, a shared starting point, and whether a count-in helps prevent alignment mistakes. What would you put in a short delivery checklist for this kind of collaboration?
Hi, this is a comment.
To get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.
Commenter avatars come from Gravatar.
Our next collaboration starts with a generated backing idea and a remotely recorded bass part. It works as an arrangement sketch, yet its texture might make the recording brief less clear. Alongside the guide, I can send tempo information, chords, the key, and notes on bass entrances. Is it useful to provide both the untouched guide and a revised version? The wording I found was suno fix in that search, though I have no personal results from the linked resource to report. The goal is a clear musical brief that does not turn an unwanted texture into an instruction. The bassist will work in a different recording application, so I would also welcome advice on export format, a shared starting point, and whether a count-in helps prevent alignment mistakes. What would you put in a short delivery checklist for this kind of collaboration?