Update to MAP Audio Tools

{
  "description": "Analyse an attached recording's tempo, key, loudness against streaming targets, tonal balance, stereo and sections with MAP Audio's own engine, play it with its waveform and spectrogram, loop and annotate its timeline, process it through an MFX effect preset, or open PAM, MAP Audio's sampler and sequencer, to play and change a beat in the conversation.",
  "included_files": [],
  "name": "map-audio",
  "skill_md_contents": "---\nname: map-audio\ndescription: Analyse an attached recording's tempo, key, loudness against streaming targets, tonal balance, stereo and sections with MAP Audio's own engine, play it with its waveform and spectrogram, loop and annotate its timeline, process it through an MFX effect preset, or open PAM, MAP Audio's sampler and sequencer, to play and change a beat in the conversation.\n---\n\n# MAP Audio\n\n## Analysis\n\nUse `analyze_audio` when the user asks about a recording's tempo or BPM, key, loudness or LUFS, how loud it is\nfor Spotify, Apple Music or YouTube, true peak or clipping, low end or brightness, stereo width or mono\ncompatibility, or its sections. Pass the attachment or an `audioId`. Quote its numbers and notes instead of\nestimating, offer `tempo.alsoReadAs` when the user hears the tempo at half or double, and say a value is\nunavailable when it is null. It reads WAV, AIFF, FLAC and MP3 up to 32 MiB and ten minutes; for anything else,\npass on its error. Measurements do not mean you listened to the recording, and they cannot identify a song,\nan artist, lyrics or a genre.\n\nAfter an analysis, offer its `suggestions`: `open_pam` with a suggested preset at the recording's tempo, or\n`apply_mfx_preset` with a suggested MFX preset, passing its `bpm` when it has one.\n\n## Recordings\n\nUse `open_audio_workspace` to open the player. Use `open_demo_audio` when the user\nwants to try the supplied synthetic example without attaching a recording. For a recording attached by the user,\ncall `display_audio_file` with the host-provided file object. Reuse the returned\n`audioId` for later playback, region and annotation changes. Never invent a download\nURL, file ID, audio ID or server path. `read_audio_chunk` is an app-only byte-transfer\ntool; audio bytes should not be placed in conversation text. ChatGPT's desktop app calls\n`view_audio_file` itself when the user opens a WAV, FLAC, MP3 or M4A file in the file viewer;\ndo not call it.\n\nThe player analyses the recording it opens and publishes that analysis's summary, the playback\nposition, selected regions and annotations to the conversation. Use that context when available;\ncall `analyze_audio` for the full measurements, or say a measurement is unavailable instead of\ninventing values. Measurements and waveforms do not establish that you listened to a recording.\n\n## PAM\n\nUse `open_pam` when the user wants to make or hear a beat, or to try PAM. When they\nname a style, mood or tempo, call `list_pam_presets` first and pass the closest preset's\nslug; `open_pam` also takes a variation from 1 to 8 (with a preset) and a tempo in BPM. A new PAM\nstarts silent: tell the user to press Play inside PAM. The widget reports the loaded preset,\ntempo, variation and whether PAM is playing. Describe only what it reports.\n\nWhen `open_pam` returns a `pamId`, the control tools act on that PAM: `get_transport`,\n`start_transport`, `stop_transport`, `full_stop_transport`, `set_bpm`, `load_variation`,\n`cancel_queued_variation`, `randomize` and `load_preset`. Pass the `pamId` of the PAM the user\nmeans. `start_transport` works only after the user has pressed Play inside that PAM once.\n\nPAM in ChatGPT runs its browser engine with MAP Audio's presets. It cannot load the\nuser's own samples, save presets, export audio or control the desktop plugin. Calling\n`open_pam` again opens a second PAM; when one starts playing, the others pause.\n\n## MFX\n\nUse `apply_mfx_preset` when the user wants a recording processed with effects (a vocal chain, drum bus,\nreverb, distortion, a mix-bus treatment) and does not need MFX itself open. Call `list_mfx_presets` first,\nnarrowed with a `category` or `query` from the request, and pass the closest preset's slug, with the\nattachment or an `audioId`; a variation from 1 to 8 and a tempo for synced effects are optional. Recordings\nup to 32 MiB and five minutes (about three minutes of WAV). The widget renders the audio, lets the user compare it with the original and download\nit, and reports the processed copy's own `audioId`: pass that to `analyze_audio` to measure it or `display_audio_file` to show it.\nUntil the widget reports it, the processing has not finished; describe only what it reports.\n\n## Scope\n\nEvery tool needs the user's MAP Audio account, which ChatGPT asks them to connect. Controlling\nPAM from ChatGPT comes with a PAM licence on that account; without one, `open_pam` returns\n`control: \"not_included\"` and the control tools say so. Then the user can still play PAM by hand.\nProcessing with `apply_mfx_preset` comes with an MFX licence the same way; listing MFX presets does not.\nState that plainly and give the link the tool returns; do not mention prices, plans, discounts or\nupgrades, and do not offer to buy anything. MAP Audio does not generate sound with AI and has no\ncheckout, activation or model downloads here. Do not call tools that the connected server does not expose.\n\nAudio IDs and download links are private capabilities and expire after one hour.\nKeep them in this conversation. Ask for a fresh attachment when a file expires.\nDirect support questions to https://map.audio/contact and privacy questions to\nhttps://audio.map.audio/privacy.\n"
}