In case anyone is curious, I just checked the Wavlake RSS fe...

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

npub1n3ejxm6kt6ush4rgrs57hvkecxuqunscfndlsntd5apwnyr8pjmqrme7su

hex

ff338e70a380676bd418dce867b9b0b95826dc4bf312ecd0b3e401c8d0b0291a

nevent

nevent1qqs07vuwwz3cqemt6svde6r8hxctjkpxm39lxyhv6ze7gqwg6zczjxsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsfcuerdat9awgt635pc20tktvurwqwfcvyeklcf4k6wshfjpnsedsl6lwse

Kind-1 (TextNote)

2026-01-19T17:54:08Z

↳ Reply to sunamiold (npub1vpf582eklpnh5rf47l3c0ynmmtl53z5jk0tj07e2g08h49tner2qhu2z8c)

1) Creating track actually publishes it (we've just updated button names so it make more sense). Then you need to assemble your release from publishe...

In case anyone is curious, I just checked the Wavlake RSS feed for one of my releases and it seems the original 16-bit/44.1 kHz WAV file was automatically converted to a 191 kbps MP3. That is a bit on the low side, I would say, but it was reassuring to see I have not been unintentionally pushing out WAV files.

It is a good reminder of the importance of knowing both what you upload and what is actually delivered. If I had uploaded a 256 kbps MP3 to Wavlake and ended up with a 191 kbps MP3, the original audio would have been compressed twice, which probably would not have been ideal. In this case, it was fortunate that I provided the WAV file.

On the other hand, for a platform like Sunami, as you explained, I would much rather upload a 256 kbps MP3, or even 320 kbps, since I am responsible for the conversion myself. This avoids pushing very large files to the RSS players.

Raw JSON

{
  "kind": 1,
  "id": "ff338e70a380676bd418dce867b9b0b95826dc4bf312ecd0b3e401c8d0b0291a",
  "pubkey": "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6",
  "created_at": 1768845248,
  "tags": [
    [
      "e",
      "c965b4652ed5467f88ca3736859d91eeb57280de59e984996137d59714934d56",
      "",
      "root"
    ],
    [
      "e",
      "0161fc648d757c25597a322de8d0df7269598d36db00dc39b5a57617f1e0753d",
      "",
      "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.primal.net/"
    ],
    [
      "r",
      "wss://relaypag.es/"
    ],
    [
      "r",
      "wss://relay.snort.social/"
    ]
  ],
  "content": "In case anyone is curious, I just checked the Wavlake RSS feed for one of my releases and it seems the original 16-bit/44.1 kHz WAV file was automatically converted to a 191 kbps MP3. That is a bit on the low side, I would say, but it was reassuring to see I have not been unintentionally pushing out WAV files.\n\nIt is a good reminder of the importance of knowing both what you upload and what is actually delivered. If I had uploaded a 256 kbps MP3 to Wavlake and ended up with a 191 kbps MP3, the original audio would have been compressed twice, which probably would not have been ideal. In this case, it was fortunate that I provided the WAV file.\n\nOn the other hand, for a platform like Sunami, as you explained, I would much rather upload a 256 kbps MP3, or even 320 kbps, since I am responsible for the conversion myself. This avoids pushing very large files to the RSS players.",
  "sig": "1e164947e801c6655712c74b5042623c1f116202e363813fdf9bb57816606414c7962b381d6615bd6ebf3c1403fe0016fc3b9811e0012321a23878bc0b7e27a9"
}