Jump to content

John

Members
  • Posts

    758
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by John

  1. Think of a plugin as a tool you use to do to the sound what you think it needs.  I am often amazed at how many plugins a person will use in a project.  Unless you have a real issue to work on and you can define it then by all means use a plugin if not don't. Many things can be done with a little EQ and perhaps compression used with care. There is no reason to throw plugins at a mix hoping somehow it will sound better.  Know what you want then figure out how to achieve  it.  This often means listening very carefully to the mix as is and individual tracks soloed.  Add as little reverb as you can get away with. 

    As a real help listen to songs that you believe are mixed well.  Listen closely. Use the best gear you can for listening. Try to identify how they got the sound you hear.  Question the song and then question your own song. 

    • Like 1
  2. 14 hours ago, Chuck E Baby said:

    When I went from Sonar 8.5 to Sonar X1 I was lost. I was upset because I was basically learning a whole new DAW. I didn't want to interrupt my workflow. However, there were things in Sonar X1 that I knew would improve my workflow like the Pro channel, Sky light interface, Inspector and the Multidock. The control bar I wasn't as accepting to, but as time went on...I have learned to love it.

    What I did was finish projects in 8.5 and when I had time, opened up Sonar X1 and experimented. This turned out to be a fortune but was a work in progress. You are running into the same situation right now. My advice is to watch some YouTube videos.

    When Sonar X1 there was some videos for it, but not like now. Most of my research came way of reading the manual and more importantly, this forum (the old one).

    I remember those days well. It was difficult for me.  Not because of the new version but how so many were so upset with it.  My very first impression was not a favorable one for X1.  However, at the time I was able to get the manual and read it fully. That helped greatly with how I could make the transition. I also had a bit of an insight as to what Cakewalk was trying to do.  With that and the manual I could see where they were going with Skylight.  It also meant that Sonar was now a very unique DAW in that with the Pro Channel one could potentially configure it in ways that had a impact on the sound of it.  True one could use normal VSTs for this but to me the difference was the lower CPU usage the PC offered. An important issue with me. 

    At times it was a lonely place to be in favor of X1. In the end it proved to many it was a good move on CW's part. 

    An interesting point about users that were use to a particular workflow never was an issue for me. I had long ago moved from one DAW to another without much trouble thus workflow was not an important consideration for me. Heck, I learned Logic without a manual. It took them 3 months to send me the manual for it. In those days manuals needed to be printed and mailed.  Mine for Logic Platinum 4 came with a 3 ring binder in a separate bundle.  BTW, that manual was awful. Logic did not have a Help menu or help popups at that time.  Later, I went with Cubase SX 1. To me it all was much the same as long as it did MIDI and audio I could figure it out.  Sonar was a Cakewalk for me with Sonar X1 because I already knew Cakewalk's terms for things.  Plus Cakewalks manuals were always top notch.   

    Now we are in a new era with Bandlab taking good care of this great DAW. I can't see any reason for not embracing it as now it is the best it has ever been. 

    • Like 2
  3. Also what happens with a control surface that separates tracks and buses as a Mackie Control does?  If your buses are all over the track view how can a surface consolidate them to adjust them in a bus pane?  An MCU has a button to access the buses to control. 

    Further, when I setup a multi out VSTi all the outputs are in a folder as a default.  Many of those tracks would naturally goto a bus that maybe be different for other tracks in that folder. An example maybe a guitar and horns or strings and so on.   

    As it stands now an Aux track is treated like any other track on an MCU. 

    • Like 3
  4. There is nothing wrong with normalizing. However, in Cakewalk there is a trim control for each track, with it one has the option to adjust the input signal as one wishes. 

    Keep in mind that each track adds volume to the mix.  Lowering the faders so that the cumulative volume is not clipping may be the best way to get a good sound without distortion.  I have routinely placed my faders at infinity and raise one at a time readjusting as more tracks come on line for a preliminary mix. Also if you did not record the project it may be useful to raise and then lower each track to see what it has in it.  On occasion I have found tracks that were so low in a mix that they were unheard. When brought up they added greatly to the overall sound.  I guess I'm saying use the luxury of a real multi-track DAW to its fullest.   It beats a four track hands down.  

    • Like 1
  5. I would use a bit mapped editor. MS Paint will do the job.  You can take a  picture of an item you want to use as an icon. You can also take a screen shot with Windows' built in Snip & Sketch or the Snipping Tool. 

    • Like 1
×
×
  • Create New...