Log in
Log in

or

Thread CUBASE Saving music to audio CD

  • 21 replies
  • 3 participants
  • 6,190 views
  • 0 follower
Classie83

Classie83

17 posts
New AFfiliate
First post
1 Posted on 09/07/2005 at 12:54:35
I'd like to save a projec to an audio CD. How do I go about doing that? Thanx in advanced.
KitC

KitC

243 posts
AFfinity Poster
2 Posted on 09/10/2005 at 19:14:54
Alrighty then! Now we're getting somewhere, du... ahem, Classie (I guess I should have noticed that one!):D

If you've got midi tracks in and they're of the general midi type, you can go completely virtual and use the included Universal Sound Module the comes with Cubase. I think it usually installs with Cubase but if it doesn't, just look for the Universal Sound Module folder in the install cd. You can drag copy it into your vstplugins directory on your harddrive. When you restart Cubase, the module should then appear in your VST Instruments popup. This helps you get started with virtual synths.

Once you call up the Universal Sound Module (USM), assign all midi tracks to it and you should be able to have midi sound without turning on a single external module (it also beats the MS GS synth hands down). The important difference between using USM over the MS synth is that your signal path is completely virtual and you can render "in-the-box" without having to wire your soundcard out to an input to capture sound. The Hypersonic demo that comes with Cubase is a fantastic sound source, but is only good for 30 starts.

I'm sorry if I was a bit harsh in my previous post, caffeine hasn't kicked in yet when I posted. Don't be afraid to ask more questions. It's how we all learn. Here's a bit of a tidbit - I usually render bass and drum midi tracks to separate audio tracks so I can add some of Cubase's included effects like compressors and delays separately to them. Once you learn about bussing, add an ambient reverb to that and buss all audio tracks there; makes for a more cohesive mix. Somewhat advanced. I know, but you'll get there.

Glad to have you aboard, Classie83!:)

EDIT: A bit OT. - I noticed that I previously helped you with your QS. How's it coming along? Have you been able to midi it to Cubase yet? Were you able to connect the QS outs to your soundcard?
KitC

KitC

243 posts
AFfinity Poster
3 Posted on 09/09/2005 at 19:15:42
If your midi is driving a softsynth, you will have to render them to an audio track before you can export the wave. If the sound source is from an external module, you will have to record that to an audio track as well.
Classie83

Classie83

17 posts
New AFfiliate
4 Posted on 09/10/2005 at 06:11:30

%1$s a écrit If your midi is driving a softsynth, you will have to render them to an audio track before you can export the wave. If the sound source is from an external module, you will have to record that to an audio track as well.


How do I go about rendering them to an audio track? Is there a way to automatically convert them?
Classie83

Classie83

17 posts
New AFfiliate
5 Posted on 09/10/2005 at 11:34:56
Thanx for the info. I have a manual, and I did go through it, but I guess I just didn't see that part of it. I'm new to all this stuff...and I'm not a dude. ;)
KitC

KitC

243 posts
AFfinity Poster
6 Posted on 09/08/2005 at 02:43:21
You can mixdown the project by exporting it from Cubase to an audio .wav file then dragging the resulting wav file into media player (if you're using windows xp) and burning if from there. The wav file should be in 44.1 khz 16 bit for cd burning.

Most burners come packaged with burning software such as Nero or Easy CD Creator - same process relatively. Nero has its own explorer type window, just open a new audio cd project, drag the wav from the right side of the explorer to the left, and just follow instructions from there.
Classie83

Classie83

17 posts
New AFfiliate
7 Posted on 09/09/2005 at 09:58:25
Hmm....I tried exporting the project to a disc, but it's not happening for some reason. BTW, the tracks are midi tracks.
KitC

KitC

243 posts
AFfinity Poster
8 Posted on 10/03/2005 at 12:06:10
Hi Classie83!

I didn't mean to slight you with my previous post. There's no mistake in recording to midi, however; as a matter of fact, it's a lot easier to edit a flubbed note in midi than in audio. I do believe, however, that as a classical pianist, flubbed notes are a rarity with you. :) Though Cubase cannot burn to CD, it can render to a wav file provided you record audio into it first. As I previously mentioned, you can use Windows Media Player to burn audio cds. Likewise, if your pc came with a cd burner, it should come with cd burning utilities like Nero, EasyCD or the like.

I've a feeling you're using the onboard sound of your pc. To check you can do the following:

Right click on My Computer, then Properties. Choose the Hardware tab, then press Device Manager. (Alternatively, you can click on Start > Control Panel > System to bring up the System Properties window, too.) Expand the Sound Video and Game Controllers branch by clicking on the plus (+) sign. Your soundcard should be listed among the devices there.

Assuming you're using a standard soundcard or onboard sound, the connectors on the pc will be 1/8" stereo jacks. If your pc is relatively new, the line in jack will be colored light blue (line outs are usually lime green - pls refer to your soundcard's manual). To connect your QS to your pc, you will need a 1/8" stereo TRS to 1/4" TR Y-cable. I don't know how you're monitoring your audio but I'm assuming you connected your monitors directly to your QS. In that case, you might need another Y-cable to connect your monitors to the soundcard's line out. Radioshack usually sells these Y-cables though the most common are 1/8" stereo to RCA male connectors, you will need RCA to 1/4" adapters.

The important thing is to get audio into your pc so you can record and massage it in Cubase. Once we've figured out your soundcard, we can go on to the next step, Recording Audio.
Classie83

Classie83

17 posts
New AFfiliate
9 Posted on 10/03/2005 at 10:32:01
Right I knew that midi wasn't audio. So I guess I've made a mistake in recording it in all midi? And I didn't know that Cubase SE doesn't burn to CD. That's kind of what I wanted to use it for? Is there an alternative way that I can get this music onto CD despite the fact that Cubase doesn't do it?

I'm going to try your suggestions...I don't know how I can check which soundcard(s) I have. I'm not too familiar with the various ones.
KitC

KitC

243 posts
AFfinity Poster
10 Posted on 09/29/2005 at 13:38:43
Hello again!

Midi isn't audio. It's only a series of control messages that commands your synth on what notes to turn on and off, when to do so and for how long (actually, it's more than that but let's not get into details). In short, midi has no 'sound' of it's own.

There are 2 ways to record your performance:

1) connect the audio outs of your QS to a recorder of some sort (casette, hard disk recorder, MD recorder, Pro Tools, etc.) or...

2) connect the audio outs of the QS to the LINE INPUTS of your soundcard. In Cubase, you can right click on an empty portion beneath the midi tracks and create an audio track. I forgot to mention that you must also configure cubase for your audio inputs and outputs. You can't burn to cd using Cubase, but you can use media player in a pinch.

I don't think you mentioned what soundcard you were using. Give us an idea and we can walk you through on what to do.
cookies
We are using cookies!

Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages and show you personalised ads (learn more). To configure your cookie preferences, click here.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent
These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
Audience analysis (Google Analytics)
We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
Advertising (Google Ads)
This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.
Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

Audience analysis (Google Analytics)

We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

Advertising (Google Ads)

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


You can find more details on data protection in our privacy policy.
You can also find information about how Google uses personal data by following this link.