You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After spending a lot of time correctly naming a batch of freesound uploads using the Universal Category System, a file-naming standard growing in popularity around the game audio and sound library ecosystem. Come to find out, the way sounds are identified and downloaded through freesound does break this standard.
Currently, files that are downloaded follow the following structure (this is anecdotal, correct me if this is wrong):
freesound-sound-id__freesound-user__filename-in-lower-case
Two issues arise with this format:
UCS relies on the file name following a standard order, separated by underscores (_). Systems like Soundly (Sound Library) that have UCS integration can decode this standard order to parse information about the recording from the file name. Appending freesound data to the beginning, rather than the end, of the filename breaks this structure.
UCS makes use of Capitalization to visualize Categories at the beginning of the file name, for example: CATEGORYsubcat_rest of name. Freesound converting a filename to all lowercase does muddy up this standard, and while it is still readable, it is slightly harder to understand upon first glance.
If these are baked into sounds as they are uploaded, this would obviously be an extremely difficult thing to fix, but seeing that the capitalization remains on all of the sounds I uploaded in the name of the sound on the browser UI (before download), I'm assuming the capitalization data is stored somewhere.
I understand this would probably create some ripple effects for users not using UCS, especially if anyone organizes their local library by the file naming order of freesound downloads. But updating these 2 issues would be massively helpful for the growing number of people using UCS. It could also be a profile setting, for example "UCS-friendly downloads" that applies these changes.
Edit: format
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. We're familiar with UCS and as part of our research we're looking at ways of annotating Freesound content with UCS categories. The reason for appending Freesound ID and username in the filenames is so that it is easy to identify sounds that have been downloaded from Freesound and to provide attribution at a later stage. I guess we could consider appending the Freesound ID and username at the end of the filename in a way which is compatible with UCS, although this would be a big change of user experience after almost 20 years of ID + username. Maybe an option to download using the original filename instead of the Freesound formatted filename would be feasible. We'll see!
Howdy!
After spending a lot of time correctly naming a batch of freesound uploads using the Universal Category System, a file-naming standard growing in popularity around the game audio and sound library ecosystem. Come to find out, the way sounds are identified and downloaded through freesound does break this standard.
Currently, files that are downloaded follow the following structure (this is anecdotal, correct me if this is wrong):
freesound-sound-id__freesound-user__filename-in-lower-case
Two issues arise with this format:
If these are baked into sounds as they are uploaded, this would obviously be an extremely difficult thing to fix, but seeing that the capitalization remains on all of the sounds I uploaded in the name of the sound on the browser UI (before download), I'm assuming the capitalization data is stored somewhere.
I understand this would probably create some ripple effects for users not using UCS, especially if anyone organizes their local library by the file naming order of freesound downloads. But updating these 2 issues would be massively helpful for the growing number of people using UCS. It could also be a profile setting, for example "UCS-friendly downloads" that applies these changes.
Edit: format
The text was updated successfully, but these errors were encountered: