Organization Techniques

Author
Post
Essentials Only Full Version
GigaGreenGad
Max Output Level: -87 dBFS
  • Total Posts : 160
  • Joined: 2009/12/14 16:09:36
  • Location: Calgary, AB, Canada
  • Status: offline
2010/01/28 00:12:46 (permalink)

Organization Techniques

Over the years, I've found that organization is the key to coming back to unfinished projects.  A lot of the time, I will just throw away a project just because I can't understand what's going on and things are unorganized.

What techniques are employed to achieve maximum organization in Sonar 8.52 Producer Edition?

Thanks.

Sonar Producer Edition 8.53 x64, FL Studio 9.10, Cubase 5.1.2, Reaper, Windows 7 x64, Gateway FX P-7805u
#1

7 Replies Related Threads
    Jeff Evans
    Max Output Level: -24 dBFS
    • Total Posts : 5139
    • Joined: 2009/04/13 18:20:16
    • Location: Ballarat, Australia
    • Status: offline
    Re:Organization Techniques 2010/01/28 03:20:48 (permalink)
    I think doing things that will enable you to open a session later if need be and have everything come back as it was with lots of information present to help you remember what was going on etc.

    Taking the time to name tracks and clips is a good start. How you organise the complete project folder is a good start. Getting into a routine that you back up often with different names and versions and dates in the title of the Cakewalk projects etc. Make sure any settings for plugins are stored in the project folder. Making sure all audio files are present and accounted for.

    All information regarding what plugins and virtual instruments are present and what sounds are loaded into them.

    External devices can be used and in my case they are often. Synths and samplers must have information as text stored within the Sonar Project file. Information about what sounds are loaded into what samplers etc. Any unsual signal routings etc.. Volume settings etc. Make sure that you turn any external performances eg synths and samplers into audio (in case you dont have the instruments at some later stage) and you make a complete consolidated version of your project so you can load things up into any DAW.

    If you are careful with the backup you should be able to restore any project very easily and much later if required. if I keep thinking of things I will keep adding. I am sure many of us here are very adept at these things.


    Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface 
     
    Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
    #2
    ohhey
    Max Output Level: 0 dBFS
    • Total Posts : 11676
    • Joined: 2003/11/06 16:24:07
    • Location: Fort Worth Texas USA
    • Status: offline
    Re:Organization Techniques 2010/01/28 10:52:05 (permalink)
    GigaGreenGad


    Over the years, I've found that organization is the key to coming back to unfinished projects.  A lot of the time, I will just throw away a project just because I can't understand what's going on and things are unorganized.

    What techniques are employed to achieve maximum organization in Sonar 8.52 Producer Edition?

    Thanks.


    1. User per project folders. That way all files for a project are neat and easy to copy (backup).
    2. Bounce all software synths to audio before archiving. You may not have the same ones next time.
    3. Have an external drive or flash just for Sonar projects and label it. That way it doesn't get erased or used
        for something else by mistake.
    4. Keep another copy off site if you care about being safe.

    Frank Coffey - Songwriter
    http://www.soundclick.com/bands/default.cfm?bandID=790131
    #3
    gamblerschoice
    Max Output Level: -43 dBFS
    • Total Posts : 3226
    • Joined: 2005/02/25 15:55:05
    • Location: Johnstown, Pa
    • Status: offline
    Re:Organization Techniques 2010/01/28 12:40:28 (permalink)
    Hand written notes are invaluable. It takes time and discipline, but having notes saves things that cannot be saved in other ways. A pen and tablet, very old school, works wonders.

    Later
    Albert

    http://www.showcaseyourmusic.com/lothlorienfantasy
    http://www.gamblerschoice.us/



    He's a walking contradiction,
    partly truth and partly fiction, takin' every wrong direction on that
    lonesome road back home.
    #4
    Guitarhacker
    Max Output Level: 0 dBFS
    • Total Posts : 24398
    • Joined: 2007/12/07 12:51:18
    • Location: NC
    • Status: offline
    Re:Organization Techniques 2010/01/28 14:49:31 (permalink)
    I agree with Al... I don't do it however, and that comes back to bite me...especially when I decide to change or punch in... if the guitar or vocal settings are not exact... you will hear the difference.

    Write it down....

    My website & music: www.herbhartley.com

    MC4/5/6/X1e.c, on a Custom DAW   
    Focusrite Firewire Saffire Interface


    BMI/NSAI

    "Just as the blade chooses the warrior, so too, the song chooses the writer " 
    #5
    Dave King
    Max Output Level: -46.5 dBFS
    • Total Posts : 2862
    • Joined: 2005/11/13 14:19:48
    • Location: Connecticut, USA
    • Status: offline
    Re:Organization Techniques 2010/01/28 14:55:56 (permalink)
    You can use the Info tab in the File menu to keep notes on changes you make to a project as it progresses.

    Incremental saving that includes brief notes can be very helpful.  I've never done this, but heard about it recently and it seems like it could be helpful.

    For example, files couls be saved as:

    SongTitle 01 scratch
    SongTitle 02 ezdrummer
    SongTitle 03 bass

    etc.

    This way you can see what you did along the way and go back to any point you want without too much guessing.

    Dave King
    www.davekingmusic.com

    SONAR X2 Producer 64-Bit 
    StudioCat PC
    Windows 7 Home Premium, Service Pack 1 
    Intel Corel i5 3450 CPU @3.10 GHz 
    RAM 8 GB
    M-Audio Delta 44
    M-Audio MidiSport 2x2
     
    #6
    GigaGreenGad
    Max Output Level: -87 dBFS
    • Total Posts : 160
    • Joined: 2009/12/14 16:09:36
    • Location: Calgary, AB, Canada
    • Status: offline
    Re:Organization Techniques 2010/01/28 20:13:32 (permalink)
    Jeff Evans


    I think doing things that will enable you to open a session later if need be and have everything come back as it was with lots of information present to help you remember what was going on etc.

    Taking the time to name tracks and clips is a good start. How you organise the complete project folder is a good start. Getting into a routine that you back up often with different names and versions and dates in the title of the Cakewalk projects etc. Make sure any settings for plugins are stored in the project folder. Making sure all audio files are present and accounted for.

    All information regarding what plugins and virtual instruments are present and what sounds are loaded into them.

    External devices can be used and in my case they are often. Synths and samplers must have information as text stored within the Sonar Project file. Information about what sounds are loaded into what samplers etc. Any unsual signal routings etc.. Volume settings etc. Make sure that you turn any external performances eg synths and samplers into audio (in case you dont have the instruments at some later stage) and you make a complete consolidated version of your project so you can load things up into any DAW.

    If you are careful with the backup you should be able to restore any project very easily and much later if required. if I keep thinking of things I will keep adding. I am sure many of us here are very adept at these things.


    Can you detail how to do this, using examples?

    Sonar Producer Edition 8.53 x64, FL Studio 9.10, Cubase 5.1.2, Reaper, Windows 7 x64, Gateway FX P-7805u
    #7
    NoKey
    Max Output Level: -71 dBFS
    • Total Posts : 974
    • Joined: 2008/10/28 15:30:19
    • Status: offline
    Re:Organization Techniques 2010/01/29 07:40:08 (permalink)
    One simple thing that has helped me a lot is to document the input/output as part of the name of each track:

    Partial example:
    Track1's name is: "Mic {L1/MicL} {RearL/R}"
    ----------------
    Track 3's name: "B4 {Yoke-5} {Yoke-6}"
    ----------------

    The first set of curly brackets is the Input, while the second set is the output.

    The Yoke's are MIDIYoke/MIDI-Ox related.

    This solved a nasty problem I had when trying different in/outs/Devices as I change devices globally, or experiment/learn.

    Looking at the track's names, it also orients me into troubleshooting what's where, and what should record where and not, etc.

    With the tracks documenting the previous set up, I can easily go back if I don't like what I try. If I like the changes, I rename the tracks, and save under a different template name.

    I do have a quad sound system, and various simultaneous sound modules, so I found this way indispensable here, along with the MIDI-Ox map screens.


    post edited by NoKey - 2010/01/29 07:44:57
    #8
    Jump to:
    © 2025 APG vNext Commercial Version 5.1