Page 1 of 1

Converting old Pro24III (midi-only) .sng files to .cpr questions

Posted: Fri May 22, 2020 2:21 am
by Achord
I have a bunch of .sng files created on Pro24III in the late 80's on an Atari ST. These are midi-only. I was able to extract these from the old ST diskettes using ST Recover (to recover the disk image) and FloImg (to recover the .sng files from the .ST images. Links...

I'd like to convert these to .cpr format to be able to load and use them into Cubase Elements 10 (which I have yet to buy) Some questions...

1. Apparently Cubase SX3.1 is available for download because it was the late version that could read .sng files to convert them to .cpr that correct?

2. If I buy Cubase 10 Elements, is that license good enough to also download + use SX3.1 for the files conversion?

3. Can I install the "XP mode virtual machine" on a Win10 laptop and run SX3.1 on that? Will the license work? (All I'm doing is loading .sng files and saving them as .cpr... no editing or whatever)

4. Will all the "parts" of the midi-only .sng files still be preserved in .cpr files? Thanks.

Re: Converting old Pro24III (midi-only) .sng files to .cpr questions

Posted: Sat May 23, 2020 8:54 pm
by Achord
I was messing around with Steem and a version of Cubase Lite 1.0 that sorta works on it. It seems the default file format for that is .all

I tried to load a .sng file into it, but I couldn't tell if it worked because the screen resolution was weird. I tried saving it as an .all file - it took it -- but it's much smaller than the .sng file (from about 32k to 5k in size) so I'm not sure what happened.

And what was the difference between the .sng vs .all vs .arr files? Anyone know?

And instead of having to mess with old versions of Cubase to bring these file formats into today, wouldn't it be easier for Steinberg to create a standalone program that simply converts these old formats to .cpr?

Re: Converting old Pro24III (midi-only) .sng files to .cpr questions

Posted: Sat May 23, 2020 10:10 pm
by Achord
Also how does one retrieve the knowledgebase link in the 3rd post of this thread: