Bottom line:Road-trip playlists work best when mapped to phase-based emotion curves, not random “best songs” lists.

Why this approach works

Most weak AI playlists come from under-specified prompts. When the prompt lacks constraints, outputs drift toward generic popular songs.

A stronger method is to define scenario, exclusions, version preference, and strict output format before generation.

Then run a pilot set first, validate quickly, and expand only after direction is correct.

Execution workflow

1. Define scenario variables (time, context, energy curve).
2. Set constraints (language ratio, era, exclusions, version preference).
3. Force output format: one line per song, "Song - Artist" only.
4. Test with a small pilot list, then scale and import to Apple Music.

Copy-ready Prompt Template

Use this as a base and replace scenario variables:

请生成一个自驾歌单，总时长约90分钟，分三段：
1) 出发前20分钟：稳定情绪，BPM 80-105
2) 中段50分钟：保持专注与提神，BPM 100-125
3) 末段20分钟：收束与放松，BPM 75-100

约束：
- 中文65%，英文35%
- 不要过于激烈的电子/重金属
- 避免同一歌手连续出现
- 输出24首

输出格式：每行“歌名 - 歌手”，不要解释。

Support Boundaries (important)

Playlist-link import supports Spotify, YouTube Music, Deezer, NetEase, QQ Music, KuGou, and Qishui/Douyin (douyin.com entry). Single-link conversion supports Spotify, YouTube Music, Deezer, and NetEase only; QQ Music, KuGou, and Apple Music links return unsupported.

Frequently Asked Questions

How many songs should I generate first?

Start with 15-20 as a pilot. Expand only after direction is validated.

Why enforce "Song - Artist" output?

It reduces ambiguity and improves import matching quality.

Should I optimize for one model only?

Not necessarily. Keep one master structure and tune model-specific phrasing.

Is small mismatch after import normal?

Yes. Cross-platform licensing/version differences are expected.

Continue Reading (AI Playlist Hub)

• AI Playlist to Apple Music (Main Guide)
• Text-to-Playlist Import Guide
• Playlist Sync Troubleshooting
• ClipTunes
• Song Link Converter