I have a strange issue. I just purchased Elements 8 after the trial period. The software worked flawlessly during the trial, but a troublesome issue has now arisen.
When I record a track, I see a waveform, but there is no sound on playback. If import the audio file associated with the track, playback will happen. However, I also see another file in the audio folder with a similar track name that is 0 bytes. This is happening all the time.
Furthermore, if I import the problem tracks, get them all working, save the project and close it, when I reopen the project, different tracks than the problem ones will have this issue. It is extremely strange.
Anyhow, here is what I am running hardware wise:
i7
Windows 8.1
16Gb Ram
256 SSD (running the software)
4TB WD external (project disk)
Scarlett 2i4
Are you sure the Monitor button is switched Off after the record is done?
The next file with the 0 bytes is the “buffer” file. Cubase is always recording in the background. There is a default buffer length 1 second. This is because of the safety, to don’t miss the important beginning of the recording.
import track2 from the audio files of the project folder.
All three tracks are audible
Save the project and close it
Re-open.
Track 3 is silent, the other tracks are audible.
This is happening all the time. I used the product for the demo period and it worked flawlessly. During those thirty days, I learned how to appropriately monitor tracks. Is there any one with a similar problem or a potential solution? What would be my next steps if this continues to happen?
This is weird. Once you import the track2 from the Audio folder… Does Cubase ask you, if you want to overwrite the file? The file should be already in the Pool. What happens, if you import it from the Pool only?
On import, it will ask if I want to reuse it, or if I want a new version.
If I select reuse:
NO sound
If I select new:
Sound
My routing is as simple as simple can be:
Stereo in Left and Right to input 1 and 2 on the Focusrite Scarlett 2i4.
Stereo Out Left in right to output 1 and 2 on the Focusrite Scarlett 2i4.
Tracks with and without sound are being recorded into a microphone connected to the left input.
Input routing says; “Left stereo in”
Output routing says: “Stereo out”
Reuse = no sound. If you double-click to the audio file in Pool to open it in the Sample Editor. Is the sound audible?
If you move the audio event from the track1 to the track2 (when the track2 is not audible), is the track1 audio event audible? I.e. is it on the track level or on the event level?
Mute doesn’t have any effect. It is not frozen and there is no processing on the tracks. This is bizarre. I have to be away from the computer for a while, but I appreciate your help and I hope we can eventually figure this out.
Okay. I have some news and am wondering if maybe you could help. I don’t know how to use Dropbox, or whatever to share the link, but…
I had some old project files on my system hard drive (256 SSD). I copied the project to my external and then opened the project from the external and some of the tracks had no audio. When I opened it up from the system drive, all of the files had audio. So I found a failure point. What could this mean?
When you had no audio, Cubase should display the warning, some audio files are missing. You should be able to see the path of the original audio file. Make sure the path is still valid, please.
Was there ever a solution to this?
I am having the same problem as Darp, and strangely, like him I am having the Focusrite Scarlett 2i4.
Using Cubase 7.
I notice that I can listen to my audio track (while it is still inaudible) by opening the event and using the “play” tool. (from pop-up menu on right-click)
Exactly this issue on Cubase 12.40 / 12.50.
No sound on some tracks, others are fine.
Play tool on event windows plays the sound just fine.
Playing from the pool is just fine.
Opening the wav externaly with a player, plays fine.
Export of stems are all ok.
I checked the complete signal path, but everything is configured right.
This was a working project I re-loaded and then the problem started.
Miraculously this works again. I did nothing to fix it. It just happens… I am also on 12.0.52. It proves that this software is far from stable. Could happen again tomorrow.