Thanks a lot for the answers.

𝕳𝖊𝖓𝖗𝖎𝐤 𝕱𝖑𝐲𝖒𝖆𝖓

npub1n3ejxm6kt6ush4rgrs57hvkecxuqunscfndlsntd5apwnyr8pjmqrme7su

hex

9dadbe2a9047d2a5253ee35ba4129a52925440192a171b8434ac4ef0fdb96b19

nevent

nevent1qqsfmtd792gy0549y5lwxkayz2d99yj5gqvj59cmss62cnhslkukkxgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsfcuerdat9awgt635pc20tktvurwqwfcvyeklcf4k6wshfjpnsedsxnruxe

Kind-1 (TextNote)

2026-01-17T17:50:34Z

↳ Reply to sunamiold (npub1vpf582eklpnh5rf47l3c0ynmmtl53z5jk0tj07e2g08h49tner2qhu2z8c)

Hi Henrik, thanks a lot for your kind words! 1) Yes, EPs and Albums can be published as well. See example https://sunami.app/release/naddr1qvzqqqy9tvp...

Thanks a lot for the answers.

  1. Ah, got it, maybe... so you just keep adding tracks and it automatically becomes an EP or album? In Sunami Studio, I see the “Create New Track” option where I can upload a track, and then I’m prompted to click “Create Track.” I assumed that pressing this button would immediately publish the track (I haven’t tried it yet). So to clarify: clicking “Create Track” doesn’t publish anything yet, but instead creates the track within a release, allowing me to add more tracks to the same release if I want?

  2. I see. It’s up to the artist to choose the format that best suits players like Fountain, etc. I’m very used to the legacy distribution world (DistroKid, TuneCore, CD Baby, etc.), where I just upload a CD-quality file (16-bit / 44.1 kHz) and the necessary conversions happen automatically. I’m wondering whether Wavlake works the same way as Sunami. If it does, I may have ended up with a lot of unnecessarily bloated WAV files… 😅 This is probably something that should be explained in more detail on the upload page, especially for artists coming from the legacy distribution world.

  3. I understand that I can choose whether or not to use RSS. I’m mainly curious about what happens when multiple RSS feeds are involved. For example, if Artist A publishes songs 1–3 via Wavlake (RSS) and songs 4–6 via Sunami (RSS), can a player like Fountain merge those into a single artist page? Or would it create duplicate artist pages, one per RSS feed?

In the legacy world (DistroKid, TuneCore, CD Baby, etc.), using multiple distributors for the same artist is no problem. If Artist A releases songs 1–3 through TuneCore and 4–6 through DistroKid, everything still appears seamlessly on a single Spotify artist page. Since RSS-based music distribution works very differently, I’m unsure how this is handled on the listener side.

Raw JSON

{
  "kind": 1,
  "id": "9dadbe2a9047d2a5253ee35ba4129a52925440192a171b8434ac4ef0fdb96b19",
  "pubkey": "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6",
  "created_at": 1768672234,
  "tags": [
    [
      "e",
      "c965b4652ed5467f88ca3736859d91eeb57280de59e984996137d59714934d56",
      "",
      "root"
    ],
    [
      "e",
      "7fb2e14a84f9a7a43554b8a18208bf07b682e75bac698b3cf98c082f255dca98",
      "",
      "reply"
    ],
    [
      "p",
      "6538925ebfb661f418d8c7d074bee2e8afd778701dd89070c2da936d571e55c3",
      "wss://eden.nostr.land",
      "mention"
    ],
    [
      "p",
      "605343ab36f8677a0d35f7e387927bdaff488a92b3d727fb2a43cf7a9573c8d4"
    ],
    [
      "p",
      "cbd2ff2aca546769a8da6b2d3876da47a01ee6902a8ce060a955471b0b92b116"
    ],
    [
      "p",
      "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6"
    ],
    [
      "r",
      "wss://pyramid.fiatjaf.com/"
    ],
    [
      "r",
      "wss://nos.lol/"
    ],
    [
      "r",
      "wss://relay.snort.social/"
    ],
    [
      "r",
      "wss://relaypag.es/"
    ],
    [
      "r",
      "wss://relay.primal.net/"
    ]
  ],
  "content": "Thanks a lot for the answers.\n\n1) Ah, got it, maybe... so you just keep adding tracks and it automatically becomes an EP or album?\nIn Sunami Studio, I see the “Create New Track” option where I can upload a track, and then I’m prompted to click “Create Track.” I assumed that pressing this button would immediately publish the track (I haven’t tried it yet).\nSo to clarify: clicking “Create Track” doesn’t publish anything yet, but instead creates the track within a release, allowing me to add more tracks to the same release if I want?\n\n2) I see. It’s up to the artist to choose the format that best suits players like Fountain, etc.\nI’m very used to the legacy distribution world (DistroKid, TuneCore, CD Baby, etc.), where I just upload a CD-quality file (16-bit / 44.1 kHz) and the necessary conversions happen automatically. I’m wondering whether Wavlake works the same way as Sunami. If it does, I may have ended up with a lot of unnecessarily bloated WAV files… 😅 This is probably something that should be explained in more detail on the upload page, especially for artists coming from the legacy distribution world.\n\n3) I understand that I can choose whether or not to use RSS. I’m mainly curious about what happens when multiple RSS feeds are involved.\nFor example, if Artist A publishes songs 1–3 via Wavlake (RSS) and songs 4–6 via Sunami (RSS), can a player like Fountain merge those into a single artist page? Or would it create duplicate artist pages, one per RSS feed?\n\nIn the legacy world (DistroKid, TuneCore, CD Baby, etc.), using multiple distributors for the same artist is no problem. If Artist A releases songs 1–3 through TuneCore and 4–6 through DistroKid, everything still appears seamlessly on a single Spotify artist page.\nSince RSS-based music distribution works very differently, I’m unsure how this is handled on the listener side.",
  "sig": "fcc660b075ef2f710fe6673b7c3e4dc76bc068705c922a9f9fa8d2ad16c5d20ceddb786c6b22f8005f1c6eee59b89a0481af222ec8586e3ca28a05b16d1ef2fb"
}