I am back at the studio and did some tests, here is what I can make out:
- I opened a new instance of cubase 10. I then opened the project where there was the freeze issue and ran a freeze on the mono kick channel. It bounced to no sound. I opened the freeze folder and it had created a freeze file called kick. A very small file though at 92 bytes in size. I was able to reimport that file by drag and drop but all it does is create a channel with nothing to see of course, but doesn’t say that it is corrupted or anything like that on import. It offers a 32bit to 24 bit conversion on import of the file as I suspect freeze files are 32 bit by default (my project files are 24 bit) I have stashed that 92 byte wav file to my desktop.
- I then tested by bouncing that kick channel in cubase (it was originally a bunch of events in a single lane) and then freezing that one. Result was a frozen channel all working perfectly.
- I went to snare, same process happened…So I bounced and it worked.
- I went to stereo overheads. That one froze with no issues at all and there was no need to bounce all of the regions or lanes to get a working freeze file.
All I can think is that (maybe?) bouncing an initial startup projects mono files (project created in 9.5 on win 10 opened in cubase 10) can cause freeze issues? Who knows might be just me!
I Will leave this with Steinberg. What I can see though is it doesn’t care about track versions etc what I initially thought might have been the problem.
I am happy here though as I can duplicate my versions, do a bounce (I should be bouncing every time anyways) and I can keep the lane takes on an alternate version (that’s how I normally work) and everything is working fine so I am happy moving on. I really like Cubase 10.
This could of course be a file permissions thing or some other weird thing here on my system, a plugin…who knows. Hopefully no one else has the problem but if you do it is easily fixed.
So if anyone see’s odd behaviour on a (possibly mono only) freeze attempt, try bouncing.
Thanks for answering and investigating Martin!
OK! I am back to the song at hand and will leave it solved at my end, over and out