Should this be treated as [untitled] or literally titled "Blank Project"?

AetherealDream - MusicBrainz has two albums that are released on bandcamp and youtube with an empty title:

https://aetherealdream.bandcamp.com/album/-
https://www.youtube.com/watch?v=AnfPFpDlFBo

https://aetherealdream.bandcamp.com/album/--2
https://www.youtube.com/watch?v=kpYceWonZl4

However on soundcloud they are titled “Blank Project” and “Blank Project II” respectively, and their youtube playlists are that way too:

https://soundcloud.com/aetherealdream/sets/blank-project
https://www.youtube.com/playlist?list=OLAK5uy_nCM2nNviUIjytGsI0IQPEDUMBzlcQDUDM

https://soundcloud.com/aetherealdream/sets/blank-project-ii
https://www.youtube.com/playlist?list=OLAK5uy_nNfJRj-kPrzh-KicB9I47JhsHfVoGU8Yo

I’d argue that the MB entry titled “-” is completely wrong, but I’m not sure whether it should be changed to [untitled] or to “Blank Project”. On one hand “Blank Project” to me could mean that the artist explicitly wanted the albums to have no title at all (supported by the first set of links), but on the other hand “Blank Project” is a title from the artist directly so it could be seen to qualify for the “known title” that should be used instead of [unknown] or [untitled].

2 Likes

I’d go with “Blank Project” as MB literally can’t have no name for a Release. I expect this is why someone called it “-”. I’d add notes in the annotation about the different names on different platforms.

Interesting to see that Bandcamp allows a zero length album name. As MB can’t fit “artist intent” of no title, then “artist’s alternate title” seems a fair enough compromise.

I mean there is Style / Unknown and untitled / Special purpose track title - MusicBrainz (although that is about tracks, but the same logic would make sense for release titles)

“Blank Project” and “Blank Project II” would definitely be aesthetically nicer anyway.

“[Blank Project]” is also an option, if you’re unsure whether that title should be treated as official or not.

2 Likes

The Bandcamp titles aren’t actually empty; the titles (of all three of the blank-titled releases) are two of the Unicode character U+200E LEFT-TO-RIGHT MARK in sequence. That Unicode character is invisible, creating this effect.

It seems to not play nicely with the MusicBrainz edit form, though.

Same principle as Release group “𝅙” by HHSU 𓃚 𝕮𝖆𝖒𝖇𝖎𝖚𝖒, 𝕏𝕪𝕝𝕖𝕞, 🙴 𝓗𝓮𝓪𝓻𝓽𝔀𝓸𝓸𝓭 - MusicBrainz which also uses an invisible Unicode character (U+1D159 MUSICAL SYMBOL NULL NOTEHEAD) to achieve a similar effect. (That one works in MusicBrainz.)

You can track down Unicode shenanigans like this by (in Firefox) right clicking and choosing “View Page Source” on the Bandcamp page, searching for a line of text with the release data. That line will look something like:

{"albumReleaseType":"AlbumRelease","@id":"https://aetherealdream.bandcamp.com/album/-","mainEntityOfPage":"https://aetherealdream.bandcamp.com/album/-","@type":"MusicAlbum","name":"‎‎",

Then finding the "name":" key in it and selecting from there to the following ", copying it, and pasting it into What Unicode character is this ? and clicking “Identify”.

2 Likes

I guess you will find this invisible character on all non-empty titles, there, as well.
So this is indeed an empty title.

I don’t know what the artist above intended, but I do have one example where something that looks like an empty title is not supposed to be empty. When I released Release group “᠎” by David Mandelberg - MusicBrainz, I intended it to be specifically U+180E MONGOLIAN VOWEL SEPARATOR, not empty.

1 Like

Untitled release with 0:00 empty untitled track… :thinking:

I guess it’s just that bandcamp didn’t allow empty titles.

People browsing music don’t (and shouldn’t) care about how you technically tricked bandcamp to get an empty title, IMO.

I care about artist intent. If it’s purely to trick a service that’s something else, but the artist here has explicitly told us that it’s not an ‘empty’ title.

2 Likes

I haven’t seen any other Bandcamp pages with those characters in the name (checked a few because I had that same suspicion), so I think that may not be the case.

Neither Rave Down Babylon | SHYBOI nor Jump Discontinuity | Tooth Rust (both selected arbitrarily) contain U+200E LEFT-TO-RIGHT MARK when I paste the name attribute from the JSON into What Unicode character is this ?.

I also tried using wget to download the first one of those links and opened the file in a hex editor to double-check; the "name":"Rave Down Babylon" part didn’t have any bytes that would suggest the presence of any non-ASCII characters.

I don’t know whether artist intent is to include those left-to-right mark characters, versus the intent being a truly empty title, though! :slight_smile:

2 Likes

You’re right.
It’s just a way to obtain an empty title in bandcamp.
Bandcamp may block empty titles but those users can use any invisible character that is not blocked by bandcamp, to get their empty titles:

In MusicBrainz, these releases usually get the artist name as release title.

For releases where the cover art has the artist name and no other relevant text, and there’s no other indication of an intended release title, I agree. E.g., this vinyl record: https://www.discogs.com/release/7232971-Swallowtail-Swallowtail

In my release’s case, I thought about what I wanted the title to be, and picked Mongolian vowel separator[1]. I didn’t leave the field blank to indicate that I wanted the release to go by my own name.

In the U+200E LRM case, while I don’t know what the artist intended, I really doubt they would have put in the effort to find U+200E if they wanted the release to have the same name as the artist. With physical cover art, it makes sense to avoid duplicating the artist and release title if they’re the same. But on Bandcamp, you have to fill out both fields (I think), and copy/pasting is probably easier that finding an invisible unicode character for most people. Also, I’m guessing that artists using Bandcamp are at least somewhat thinking about file tags, so they’d put a release title that they want in the album tag.


  1. That character has some fun properties because it changed Unicode categories, which causes different versions of different software to sometimes disagree about how to sanitize text that contains it. So it can break software in fun ways that other invisible characters generally can’t. Plus using it was a bit of a running joke in a group I used to be in. All of which to say, it really was not an arbitrary choice. ↩︎

3 Likes