Homebase for Sonar users

Taurean_Mixing · January 2, 2018, 5:18pm

l3v3l6:

Taurean Mixing:

I’ve been familiarizing myself with Cubase 9.5 Pro over the past month or so and I’ve made the switch officially. I’m liking it. I am curious about 64-files. It seems Cubase can’t read them, is that something known already or am I experiencing an issue?

I have tested this directly with an audio wave file I export at 64-bit from Sonar.
I then import it into Cubase and you can see the container of the waveform but no waveform, rather a message that says it can’t reconstruct the image, along those lines. I go back to Sonar and re-export the same exact audio file at 32-bit, re-import into Cubase and works totally fine.

I primarily work with 64 bit WAV files in Cubase and never had a problem exporting them for use in other programs like Sound Forge. It’s a standard non-proprietary file format. Maybe Sonar is not exporting them correctly?

Odd. I imported the same 64-bit file into Reaper and Studio One without issue.

EDIT: to be clear, I’m only referring to importing 64-bit wave files into Cubase. If somebody can confirm that Cubase indeed doesn’t work with 64-bit floating point wave files. Because I’m noticing in the export, unless I missed something, I see options for 32-bit float as the highest bit depth, not 64. (I think you might have been referring to wave-64 file, being proprietary to soundforge should open fine. But I’m referring to 64-bit float wave file format).