Let me check the logs, because it doesn't matter if titles are identical, checking for duplicates uses file hashes/signatures, which means two different files and formats shouldn't end up with the same hash.
Another thought.
I had uploaded the full 3-song video prior to cropping the 2nd song to its own mp4. https://vid8.poal.co/user/Khro_/GyJAvhN
If the mp4 for the cropped 2nd song somehow maintained the hash of the full video, perhaps that was the video vid8 thought already existed. If that is the case, it should've given me the same 'already exists' error when I tried to upload it again with a different title, but it uploaded successfully with only the title for the upload being changed.
Perhaps it was just some odd set of circumstances with the upload that caused the upload to be detected as already existing.
Ah. That was the only thing I could think of that might've caused the issue, especially as it allowed it to upload after making the titles no longer match.
Yeah, it wasn't like I cropped the video first and then converted the mp4 to mp3. They were done at separate times with the mp3 done first from the longer video with one program, and I even re-encoded that, and then cut the mp4 from the long video.
Perhaps it was due to taking me like a half an hour to upload the 20mb video very slowly.
Much earlier I had uploaded the mp3 for the first song from the 3-song set. After I uploaded that I saw that it had the wrong duration and still said it was the full 13min+ of the full 3-song video. I deleted that upload, re-encoded the mp3 for that song and re-uploaded that song now that it had the proper duration.
Just noting that so you see what happened with me deleting an upload prior to doing this mp4 upload later on.
Alright, I found the culprit.
Upload code is checking for duplicate titles first, even if the files are different, then it compares hashes. But since it uses an async function, a race condition can occur (though it is very rare).
I'll update/fix that code later.
Thanks for the report!
I'm very, very relieved! I was starting to fear that I was wasting your time with a false report and that it was due to me making an error and misremembering what I uploaded and that I did try to upload the wrong file the first time with one that actually did already exist.
Thank you very much for looking at that and finding that there was a cause for what I experienced!
(post is archived)