Jump to content

LuIzA

Members
  • Posts

    361
  • Joined

  • Last visited

Posts posted by LuIzA

  1. I'm planning on using CDBaby.com to release my album when the time comes. They take care of most of the formalities. It costs like $50 an album, and they keep some of the income. You can also use them to press CDs and sell them.

    There's also Tunecore, but they are mp3 only. They don't keep any of the income of the songs, but it costs like $50 a year to have an album there. They also have a random art generator, and can use Amazon's CD on demand service.

    As for mastering, what I do is, I import every song on a separate track in Cubase (formerly Sonar), order them, match loudness and apply other treatments, such as compression, limiting and eq.

  2. 64bit DAWS still don't run completely efficient on the new wave of intel CPUs, so run whatever you have in 32bit mode for better CPU optimization.

    interesting. I wonder if this also has anything to do with the fact Sonar x64 had been a bitch lately.. I always felt my pc wasn't as well as it should've, but ever since I switched to Cubase (using 32 bit, because of Waves) it's all been pretty smooth.

  3. What I mean is, for instance, when I record gang vocals, I'll make many takes of a single line and combine it into one track... in sonar, you can have more than one lane active, so no such thing is needed. In cubase, I'd need an obscene amount of tracks, so I'd like to bounce all these into a single track.

  4. To properly use Cubase in an x64 environment you have to make sure that you go into the shortcut properties and click so that it's always running with Administrator privileges. That way when the Waves plugins need access to the Waves shell, they'll get it and the plugins will work. This also makes sure that all your plugins run correctly and all your product registrations match up every time you run Cubase, otherwise you may install something that changes the Cubase profile a little bit and then you'll no longer be connected to the registry and you'll have to re-authorize all of plugins again, and if the Cubase ID doesn't match with the old Cubase ID stored in the product registration in the registry then that plugin wont work till you completely remove it from the system and reinstall. It's a huge mess, so yeah just run Cubase in administrator mode at all times.

    I just tried doing this, I ran Cubase 64 bit as the administrator, went to Plug-in manager, selected my paths, and updated. I then got a message saying "Waveshel-vst is not compatible with current application. waveshell-vst and the waves plugnis can only run in applications that support VST shell plugins (kPlugCategShell)".

  5. According to this, Ctrl+Click to return to the default value. I haven't tried it myself and don't have my Steinberg key within reach to confirm, but I remember reading that somewhere previously too.

    it does work, thanks!

    EDIT:

    more questions:

    a) Can the markers be seen from within the Piano roll?

    B) Can you select via the ruler (especially for copying a whole measure of midi sequence)? I'm aware there are other ways to achieve the same result, but that's one thing I used to do in sonar a lot.

    c) I've heard you can use the waves plugins (which are 32 bit) with Cubase 64-bit, anyone have any luck with that? my waves plugins don't show up in 64 bit cubase.

    d) can you monitor a track and listen to what's already recorded at the same time?

  6. I'm beginning a gradual change to Cubase 6 because of some of it's features, but I've encountered a few problems and/or miss some things good ol' Sonar has.

    a) with Waves plugins, namely the C1, I'm unable to send another track to its sidechain.

    b)in Sonar, if I double click a parameter, like the fader in the mixer, it returns to 0dB, or the pan, it returns to center. Is there anything like this in Cubase?

    Thanks in advance

  7. I only bothered with theory when I bought those books. my Teacher tend to teach in a "mind-closing" way... I felt I was being limited by knowing theory. Those books tend to open your mind as you read.

    ...But then, after awhile, I found I was thinking too much theory instead of letting the music flow.. it's contradictory, but it still helped with my job.

  8. there are some good books out there, like the "composing/harmony/music theory for computer musicians", I own two of those.

    but in all honesty, these books were recent additions to my collection, it was entirely filled with books on audio and mixing and that sort of stuff. if you plan on recording and what not, one I really recommend is "mixing audio: concepts, practises and tools".

    What I mean is, what helped me the most was making covers and trying to emulate the originals.

  9. A couple of minor criticisms: I would have had difficulty knowing what the lyrics were without reading them, so either the ennunciation or production on the vocals could have been better to make them clearer. I think it is especially important in a song like this, where the words are so critical to the meaning of the song (and so amusing and clever that they deserve to be showcased prominently).

    Thanks for your input. I'm aware I have an accent haha, other than that, the vox on the chorus are doubled, so I guess that plus my accent makes it a bit hard to understand. Still, I can try and do something about it for the project version.

  10. So here we are again, it seemed people dug our little game last time... So here you are, the 2nd edition!

    This time, I recorded a cover of "Found" by my favorite band, Span (RIP). If you've never heard of them, they're definitely worth checking out. Here are the files:

    http://www.mediafire.com/?emlqbbfh1sadm1k

    Recording:

    Again I must apologize for my shitty drumming, some tempo correction, again, was needed, but I didn't bother with it too much. The drums were recorded in a similar fashion from last time, the same mics were used for the same purposes with slight differences in position. The Overheads are more like "sideheads" this time, they were placed 2'-3' farther than last time to avoid "cymbal tremolo". The snare was mic'd somewhere in between the top and shell, and the kick drum was played with a felt beater and the mic was not angled.

    I decided against including DI's for the guitars this time. The SM57 was placed off-axis and the AKG was placed further away as a room mic (you can even hear the strings being strummed). So to "replace" the DI's, I decided to try out a little trick I've heard of, I recorded an overdub for every guitar part using a small battery amp with 57, it seemed fitting for the song.

    Bass and vocals were recorded direct and with the AKG, respectively.

    The Rules:

    If you are going to post a mix of your own, you must critique on the mix before your post. Making a little write up of how you did your mix is also cool, but optional.

    Happy Mixing!

    My mix:

    http://tindeck.com/listen/fktf

    I went ahead and replaced every drum with Trigger EX, I blended the snare and kick with the samples, and cropped 3 copies of the OH track so I could replace the toms. All drum tracks were then treated with EQs (except the tom tracks) and the OH used some parallel compression for more meat. In addition to that, the snare and kick peaks were tamed with a compressor.

    The guitars were basically left alone, just blended the sound of each mic to taste. Every lead guitar used some reverb and slapback delay. Bass was pretty heavily processed, I used the Waves GTR bass amp sim and the CLA Artist Bass plugin and used the kick to feed the sidechain in its compressor. everything below 300Hz or so was nuked and boosted a bit at 3Khz for the vocal bus and some reverb was added, some vocal tracks used a bit of delay and saturation as well.

    And finally, the mix was processed with a multiband compressor for the mid range, a small cut at about 500Hz and a limiter.

  11. Likewise if you record at 48kHz, you should dither for your 44.1 export.

    technically, dither only has to do with the noise floor, and dynamic range. Going down on sample rate can cause aliasing, to prevent that, some processors use anti-aliasing filters, which are basically LPF around half the sampling rate (22.05 KHz for 44.1KHz). check out for more info: http://en.wikipedia.org/wiki/Aliasing

    Other than that, for recording like most of us do, there's no real point in working at a higher sample rate your work is going to end up on (44.1 KHz for CDs and mp3s). You won't get a huge difference, or maybe even a noticeable one in most cases.

×
×
  • Create New...