Hey metatablecatmaid, it’s surprising that just renaming the file to .mp3 would cause the upload to succeed – is that the case both via studio & the web?
Ogg is a container format that can hold a variety of different codecs – of these, the audio engine expects ogg-vorbis. It might be that the file extension is .ogg, but the codec that the file is using is non-vorbis
I just had this issue as well. Luckily, thanks to @ReallyLongArms’ response, I got the idea to import my ogg into Audacity and export it, where I could specify it as an Ogg Vorbis. The resulting sound successfully was uploaded. I suggest doing the same if this happens again.
Ogg supports wrapping a variety of codecs – Audacity might be choosing something like opus or flac, which are totally legitimate formats, but the audio engine doesn’t support them at this time.
My audacity is configured to use Vorbis already, so I feel like its a different issue (the audio played in-engine as a local asset), let me generate a sample audio that also fails with an upload
Here’s a sample that also fails on upload, encoded with Vorbis
Interesting; this file looks fine according to the audio engine
I tried uploading it on my end, and it actually seems to work, but I noticed that it took significantly longer for the file to become “ready to use” when uploaded with an .ogg extension than the version that was uploaded with a .mp3 extension.
The mp3 file extension was processed immediately, whereas the ogg file required refreshing https://create.roblox.com/marketplace/asset/YourAssetIdHere for a couple minutes before the length got populated and the file became usable in studio.
Does this match the behavior you are seeing, or did the .ogg file never get processed?
Genuinely any updates to ogg supporting on the website? Its been forever and I could really use it as audios downloaded from the Marketplace auto to ogg and can’t be re-uploaded without conversion. I don’t see why many aren’t on this issue as its really a struggle when you’ve got tons of audios to upload.
I am discussing with folks who maintain the website – for the time being, uploading through studio might be the best viable workaround, but we are looking to get this fixed