MediaBay freaked out on me last night and took out Cubase 13 and some of my audio samples with it. First bit of trouble with 13 so far.
Cubase Pro 13.0.30/Sonoma 14.4.1/Mac mini M2 Pro/MOTU 828x
Brand new Cubase session, opened an empty project to start playing around. Had one track created with a Groove Agent SE instance on it, no other plugins at all. Had MediaBay open looking for breaks and got some weird pauses and freezes while selecting files, but eventually it came back. At some point some of the files stopped playing back after the freezing. If I left the folder and came back, it was empty and MediaBay would start rescanning it.When it finished only some of the files came back. Eventually while rescanning/refreshing/going to different folders and back/etc, Cubase crashed.
Didnāt think much of it but I just now opened Wavelab and wanted to trim/edit some of those same loops. Apparently those files that stopped showing up in MediaBay, turned into corrupted 4.29GB files. Whatever crashed, ate 10 of 27 files in a folder. They went from like 3MB files to 4ā¦29GB hah. All I really did aside from audition samples, was add the beats/tempo data to the files while I was listening to them. Not sure if that caused it, but the files that are still there have the info still so it didnāt break everything.
I donāt know if this is related but it seems awfully suspicious. I found a couple other directories that had some corrupted 4.29GB samples too.
These were samples I recently edited in Wavelab 12 Pro, they were audio cd format discs I had to chop up by hand and whatnot, PG taught me all about the split by silence command haha. In those directories, Wavelab seemed to have left a bunch of its .$$$ temp files (even though I set it to NOT do that). Maybe those files threw MediaBay into a weird loop or something? Iāve had this happen before quite awhile ago, but didnt do any digging on it, I assumed it was a fluke last time.
Just another quick updateā¦ I am going to take a wild guess this is all MediaBayās fault. I had Halion 7 do the same thing last night, killed a bunch more samples and blew them up to 4.29GB. I had restored all my samples that were damaged using Time Machine last night, and I decided to open up the standalone Halion to see if adding tags and whatnot in the Media Bay browser was a little smoother. Halion lasted for one directory, I selected 15 files, changed the category and style tags to Beats and Jungle/DnB. Right away Halion āfrozeā up trying to preview a sample. While it was still spinning, I opened the folder in the Finder, and it had already corrupted 4 of the samples in there. I didnt bother waiting for it to crash, just force quit it so no DMP or anything.
For now it appears I just cant use Media Bay at all until this is hopefully fixed, or they can figure out why my machine does this. There is no telling when it does this and Iāve found a couple other random samples this happened to at earlier dates/times while digging for this. Last night I basically spent all night looking at folder sizes in my sample directories. Anything over 4GB, meant there was probably a corrupted 4.29GB sample sitting in the folderā¦ Found a few of them from this year, last year, etc and some of those were so long ago, no Time Machine backups aside from the corrupted file, so I have to go ārebuildā some of my sample library now.
Hi there! Catching up from your recent message in the other thread about C14.0.20. Found this post and the report (ref.: CAN-59819) with the crash that I already had on my desk for investigations. We did not find a reproduction and asked to get an update with an updated MediaBay that was released meanwhile. The crash happened with Cubase 13.0.30 and MediaBay 1.1.50.
Please let me know if you still have these problems with the recent version which is 1.2.40.
Is it correct that you were editing WAV files in Wavelab while Cubase was running and MediaBay was open? There was no tagging from MediaBay involved, just rescanning?
IIRC - No Wavelab was not open when Cubase was (I rarely ever do that in the middle of a session). That was just how I initially chopped up my CD, in case it had any bearing.
Wavelab used to have this habit of leaving is temp files around on my drives but that seems to have cleared up with one of the last updates. I wasnāt sure if that may have had anything to do with the issue so I mentioned it.
Unfortunately I have no way of getting any files or reports. When this happens, there arenāt any crashes, no warnings, it just corrupts the wav file. Iām usually in the middle of working when this happens so I end up restoring my directories/files from Time Machine right away.
The next time I can get it to happen, Iāll save the 4GB wav file and see if anyone can find anything wrong with it.
Thanks for your response. If something like that happens, I expect some bytes in the beginning of the audio file got corrupted. I would only need the first 1000 Bytes or so. Could be accomplished with a Hex Editor, but 4GB of noise is also welcome, as long as it leads to any insight
I remembered an easy way to make it happen. If I select a bunch of wave files and edit their tags at once, eventually something will get corrupted, I just have to wait it out and find it in the list.
MB_BadWaves.zip (2.9 MB)
Unfortunately (or fortunately?) this time it didnt blow them up to 4+GB, the file size stayed the same, but it damaged them none the less. I selected a whole directory of files in Media Bay, changed the Category to āSound Fxā, then did another, then anotherā¦ I found two for you to look at.
I can likely make it happen again and see if I can get one of the huge corrupted files if you want to check one of those out too? These two samples are from a Goldbaby sample pack, but I figured since theyāre damaged and wont play, theyāre ok to upload.
Thanks! Iāll take a look at these files now. Which version did you use to tag? MediaBay & Cubase? The database server does only scanning, no writing into the files. That is always done by Cubase or HALion, depending on where you do the tagging.
There is one ugly thing to mention tagging lots of files (I think I remember you ran into that bug): When selecting loads of files, having the Attribute Inspector open in the MediaBay, that is checking if tags are all the same for all files selected, it takes the longer the more files are selected, limitless. That is something we need to fix, filed an issue for that (ref: CAN-59846).
I see the problem, it looks like the problem we identified to be released with 14.0.20 ā¦ after ādataā there should only be data but what we see is āLISTā ā¦
If you were using any other version then 14.0.20, please let me know asap.
I wonder if I want a bit after selecting the files if it will work a little smoother? Either way, glad to be of help, if you need anything more just let me know.
Thanks! Then you ran into the issue from the thread I picked up on you:
We ware actually working on that and will provide a fix.
For the moment I recommend to NOT use Cubase nor Nuendo 14.0.20 MediaBay Window for tagging. Tagging from HALion, Groove Agent, or earlier versions of Cubase / Nuendo should be fine and the new tags will be available in the global MediaBay (Server).
Thank you very much. Glad I was in the right place/right time and could contribute finally!!
On a related note, in Halion and Groove Agentās MediaBay, I seem to be able to add new sub categories when I need them. Is there anyway to make these show in Cubaseās Mediabay? I only have the āstockā set of options in Cubase, and the MediaBay windows donāt have the little ā+ā features to add things to like Halion does..
This is awesome news either way, looks like Iāll be spending some time in Halion today tagging and NOT worrying about losing my data.
Uh-oh, I just got it to happen in Halion 7.0.30 too, and it made a bunch of ~200k drum loops into 4.29GB files again.
I was tagging stuff in the browser in Halion, went through five or six directories without any issue and then I got the Mac ābeachballā after adding a bunch of tags to a folder of loops and when I checked the folder itself, there they are..
Now here is the REALLY fun part.. While I was typing this, Halion is still open and I have the Finder window open where the samples are visible too. As I am typing this, I noticed the Finder doing āsomethingā and its updating the āDate Modifiedā entry. Halion isnāt ābeach ballingā anymore, and I am not even touching it, itās hidden under my browser, but it is still running and corrupting more and more of the files. I just went to close it now and it decided to crash on close. That folder just went from 87MB to 180.47GB haha. Time to hit the Time Machine again, Iāll save one of these just in case someone wants to look at it (or I can figure out how to get what you need in a hex editor).
Are there any logs anywhere I can get to send someone to look into this?
EDIT: Opened no problem in a hex editor. This is the beginning of the data, somewhere a few pages down is part of the BWF data that was left behind but other than that, the entire file is all 0000000
Looking at the hex-dump, bext seems OK, then the āFakeā Chunk of hex B6 bytes is OK, then only zeroes, thatās wrong.
You could activate the MediaBay logging, here the client-side might be of interest, but the tagging code in the host (here HALion) is not logged, so that might not give much insight. Anyways, you can: create a folder called āMediaServerā containing a folder āLogsā, inside folders āServerā and āClientsā. Before restarting, wait until the process āSteinberg MediaBay Serverā was shutdown. Here a screenshot from my system:
Could you send me a copy of the original file āZG_JW1_Together.wavā for investigations?
I would immediately debug the tagging routine and give you feeback.
Thanks for the help hehe. Weird thing is, these are supposed to be āACID loopsā but about half of them show up as that, the other half show up as āBroadcast Wavesā. Iām not sure if I messed these up at some point tagging the or if thatās how they really are. Itās an old no longer available sample pack so Iām stuck with my old archive I managed to save all this time.
When I restored them last night, I converted them all to AIF to get rid of the header, and then back to a regular WAV file, now they all show up as ACID loops again, no BWFs.. The one below is the original version that corrupted (I went a few days back in my Time Machine backup)
Err yes thats it, the latest version hehe. I was being a bit lazy and didnāt check the actual number, thought it was 7.0.30. Iāve been working at home the last couple of days so Iām moving back and forth between my work Windows machine and my Mac hehe.
and everything sluggish now, likely because MediaBay catches it via filesystem-monitoring and scans to death reading the 4GB of nonsense ā¦ now we can work on a fix, that is great! Iāll keep you updated!
If I select a bunch of wave files and edit their tags at once, eventually something will get corrupted, I just have to wait it out and find it in the list.
