I just opened a project and there are MANY tracks where the clips are missing their waveforms. The colored clips are all still there, it's just that the waveform AND THE SOUND are suddenly missing.
The clip is there with the clip name and correct clip color, but it's like the file is missing, just a blank clip?
Seems like every week it's a brand new PROJECT DESTROYING problem with Cubase.
What to do, what to do?
Anyone ever had this one? Is there a fix?
Ever Heard Of THIS Cubase Bug?
-
- KVRAF
- 25172 posts since 20 Oct, 2007 from gonesville
The project-destroying problems I've experienced can mo' less be boiled down to corruption of files. Few and far between. I've seen this, it means the audio files aren't there in the pool.
IE: blank audio such as that should have had Cubase tell you to find missing files when you opened the project, it doesn't just fail to load audio from the project audio pool for no reason; so we're looking for a reason. First does the folder the project's audio pool corresponds to have these files?
(This I have never seen.*) If it does, something in your installation is borked. *: One thing this is not is a Cubase bug. It would have zero viability in a competitive market were it that broken.
Is your computer under-specced, does it run very hot for long sessions? Looking for things that corrupt files. Sometimes the project is corrupt; this is a difficult issue and I'll venture to say usually means it needs to be rebuilt. In a case that keeps happening you do want to have an idea why.
It could just be preferences are corrupt [not infrequent btw]; this is an easy one, remove everything (save what you can't stand to lose, such as key commands, RAM presets etc, and reinsert after launching it and it has rebuilt preferences.) Or more of Cubase was corrupted, meaning uninstall it as cleanly as you can figure to do and reinstall.
IE: blank audio such as that should have had Cubase tell you to find missing files when you opened the project, it doesn't just fail to load audio from the project audio pool for no reason; so we're looking for a reason. First does the folder the project's audio pool corresponds to have these files?
(This I have never seen.*) If it does, something in your installation is borked. *: One thing this is not is a Cubase bug. It would have zero viability in a competitive market were it that broken.
Is your computer under-specced, does it run very hot for long sessions? Looking for things that corrupt files. Sometimes the project is corrupt; this is a difficult issue and I'll venture to say usually means it needs to be rebuilt. In a case that keeps happening you do want to have an idea why.
It could just be preferences are corrupt [not infrequent btw]; this is an easy one, remove everything (save what you can't stand to lose, such as key commands, RAM presets etc, and reinsert after launching it and it has rebuilt preferences.) Or more of Cubase was corrupted, meaning uninstall it as cleanly as you can figure to do and reinstall.
-
- KVRist
- 319 posts since 24 Aug, 2017
It sounds like the wave previews have been screwed up. It doesn’t happen often but it does happen once or twice every year. The waveform displays is in the image folder I think. There could also be issues with edits/direct processing etc which Inthink are stored under edits. Bouncing the track or backing up the project can sometimes work. Applying direct processing also causes the file to update. A good old reboot should be tested firsts, and please backup before mocking with the project.
-
- KVRAF
- 25172 posts since 20 Oct, 2007 from gonesville
A problem from missing edits comes under 'Cubase informs you of missing audio files'. There is a folder created whenever audio file edits occur called "Edits" under the top project folder with the rest of the folders (EG: "Audio"), by default.
Again the first thing to look for is where are your files. Now, do the files fail to display or fail to audition in the project audio Pool?
"Applying direct processing also causes the file to update." and Cubase will append numbers to the edited audio, unless destructive editing is in effect* {*: Preferences: "on processing shared clips": "process existing"}; you now have two files, like 'Drums" and "Drums-01".
I've def. seen audio files in project that don't display right, but then they do. (The display of the file and the file producing audio are separate issues.) If they never do there is a problem of corruption. One test that can be done, nonetheless is that save as a backup and see what it does with the audio files.
Again the first thing to look for is where are your files. Now, do the files fail to display or fail to audition in the project audio Pool?
"Applying direct processing also causes the file to update." and Cubase will append numbers to the edited audio, unless destructive editing is in effect* {*: Preferences: "on processing shared clips": "process existing"}; you now have two files, like 'Drums" and "Drums-01".
I've def. seen audio files in project that don't display right, but then they do. (The display of the file and the file producing audio are separate issues.) If they never do there is a problem of corruption. One test that can be done, nonetheless is that save as a backup and see what it does with the audio files.
-
- KVRist
- Topic Starter
- 49 posts since 22 Aug, 2022
SOLVED!!!
Thank you all for your time and suggestions.
However, it turns out my problem was one of a simple oversight and user error.
It's not Cubase's fault, or a bug. It also explains why the missing audio was so random.
In this particular project, I had copy pasted some sections from another version of the project. I've done this a million times and never had any problem.
What I overlooked in this case is that the parts I copied over from a different project were on a completely different hard drive.
I was under the assumption that once something was in the sequencer, it was embedded into the project folder. Nope.
I hooked up the other drive and then tried to open the project, and Cubase automatically found all those files on that other drive, and the project loaded correctly.
I'm currently doing a Cubase "backup", as I believe this, is how I get Cubase to bundle all the parts, clips etc. into one new, collective project folder.
It's kind of shocking that all the years I've used Cubase, I've never run into this problem before. I guess I've never copy pasted from a different drive before.
But thanks, once again!
Thank you all for your time and suggestions.
However, it turns out my problem was one of a simple oversight and user error.
It's not Cubase's fault, or a bug. It also explains why the missing audio was so random.
In this particular project, I had copy pasted some sections from another version of the project. I've done this a million times and never had any problem.
What I overlooked in this case is that the parts I copied over from a different project were on a completely different hard drive.
I was under the assumption that once something was in the sequencer, it was embedded into the project folder. Nope.
I hooked up the other drive and then tried to open the project, and Cubase automatically found all those files on that other drive, and the project loaded correctly.
I'm currently doing a Cubase "backup", as I believe this, is how I get Cubase to bundle all the parts, clips etc. into one new, collective project folder.
It's kind of shocking that all the years I've used Cubase, I've never run into this problem before. I guess I've never copy pasted from a different drive before.
But thanks, once again!