a little help

[Nanakai]

Man I cant even begin to tell you what it feels like to have as much software as I have and feel so overwhelmed.

Just bought damage and installed it and havent even touched it.

This is exactly why you should stop buying things. Just stop for a bit, until you have learned every other piece of technology you own. What you're doing makes no rational sense. When you install things, go through the manual, every page of it. Watch videos if any are available. If the problem is that you don't quite know how to make music, then you should work on that before buying anything else. New gear will not help you. Try covering a song you like or something.

I just installed Damage and I'm having a ball with it. Going through the manual tonight and hopefully working out a track before going to bed.

[Trakstar]

No hard feelings either, with the samples, choose 1 set and ignore all the rest.
I spend a session going through tons like you have and if a sample sounds good I copy it into a seperate folder for later. This way I build a collection of my own sounds which are unique and what I like, you can then spend the next session mixing from your ready made sample toolbox. Some time or other your going to have to sit down and go through them, listen to the ones you like and ditch the others. In your own words the trauma drum samples are the worst buy you evermade so get rid of. Ive heard this story many times before, the person who had everything but couldnt do nothing with it, and the person who had the minimalist of equipment but could create anything he put his mind to within the certain boundaries of what he owned. If you want some good start up stuff, watch the video guides from computer music of how people make their tracks, its about 1 hours viewing but they sure cover a lot of stuff from beginning to end. You also listen to all their individual tricks of the trade and learn a great deal of things you wouldnt hear elewhere.

[thecontrolcentre]

Hey guys i am for real confused. No troll, and don't mean to be if I am. I do promise I own all that gear 100& and no I'm by far not done buying stuff.

So why do you keep starting "how do I do it?" threads, then ignoring the questions people trying to help you are asking? Stop buying stuff you don't need or understand, and spend some time learning what you already have. Who buys 4 DAWs when they can't even understand how to install them properly?

[Mutant]

Do you have passion for all this ?

If you have the passion, you will enjoy learning all about it, your brain will be absorbing new knowledge like a dry sponge sucks up water.

Copypasted from another thread:

http://www.berkleemusic.com/school/cour ... fcode=2285

http://www.styluscollege.com/sound_design.html

http://www.vfs.com/fulltime.php?id=11

http://www.pointblankonline.net/sound-design-course.php

http://www.pointblanklondon.com/sound_d ... tion_1.php

http://www.flashpointacademy.com/programs/recording.asp

[kbaccki]

Hey guys i am for real confused. No troll, and don't mean to be if I am. I do promise I own all that gear 100& and no I'm by far not done buying stuff.

Who buys 4 DAWs when they can't even understand how to install them properly?

Somebody with compulsive hoarding and/or compulsive buying disorder. Seriously dude. No joke.

OP... learn the difference between 32-bit and 64-bit DAWs and plugs running on the same 64-bit OS. Mix and match, or not. J-bridged, bit-bridged, whatever-bridged, or not. You seem to be confused by the 32/64 bit thing, but you don't realize it... admittedly, it's confusing, so figure that out first. You mentioned jbridge more than a couple of times... figure out what it's for and why you might need it.

Once you figure out 32/64 bit... separate your VST plugs into "C:\VSTPlugins" and "C:\VSTPlugins(x64)" folders... only use those two folders. That'll solve a couple of other problems that seem to be the cause of much distress -- VSTs all over the place, too many VST folders. Put your 32-bit plugs under C:\VSTPlugins, 64-bit plugins under C:\VSTPlugins(x64) ... in your 32-bit and 64-bit DAWs/apps, set the VST path to either the 32-bit or 64-bit VST folder, as appropriate.

Next, find the ***one DAW app*** that you will use for creating music. In the future you will have more than one DAW, I can guarantee that... but to start you need to focus on at most one. It needs to make sense to you, but at the same time you need to look at these things with somewhat of a clue as to what exactly you want to do with them: recording tracks (e.g., w/ a guitar, microphone, whatever), dropping and manipulating loops and one shots, integrating soft synths, applying FX (chorus, delay, reverb, EQ, etc.) to tracks? How will you be creating your music, and what tools do you need to carry that out? They all pretty much do the same stuff, but some DAWs are better than others depending on what you want to do with them. First, figure out what exactly you're trying to accomplish, then ask around and demo the DAWs that fit your usage profile. It could be FL, Ableton, Reaper... who knows... depends on what you want to do.

One major deciding factor for picking a DAW is 32-bit vs. 64-bit. Some DAWs are only available as 32-bit... this may or may not be a problem, as plugin bridging can aleviate most 32-bit limitations (see comments below about 32-/64-bit plugs, bridging, etc.).

Next, assuming you picked a DAW and that is available as both 32- and 64-bit...
figure out which version of the DAW you need to run -- in most cases, you can just run the 32-bit version, even on 64-bit Windows 7... it works just fine. The reason you might run the 32-bit version is that you have "native" compatibility with all of those 32-bit VSTs. If you run the 64-bit version of the same DAW, then you can only natively see the 64-bit VSTs.

This is where "bridging" comes in... a plugin bridge is a level of complexity, but gives you the ability to run 32-bit plugs in a 64-bit host, or 64-bit plugs in a 32-bit host.

Your choice of 32-bit host vs. 64-bit host should be driven by one factor: how much runtime memory do you need available to you during the creation process?

If one of your key tools is Kontakt, for example, or BFD, or Battery, or something like that that makes heavy use of (potentially) very large streaming samplesets, then you might consider running 64-bit throughout. OR run 32-bit DAW and just 64-bit bridge only those memory consuming plugs... keep everything else 32-bit native.

Next... get a sample/loop organizer app. Then you'll need to spend a bunch of time organizing your sample/loop database by attaching meta info like manufacturer, genre, BPMs, instruments, style, whatever. In the end you'll be able to call up all your electro kick one shots with one keyword search... Some DAWs already have such utility (like a "media library" sorta interface), so maybe just going with such a DAW is a good idea... have the tools you need directly at your disposal.

Finally, keep all your plugs installed, but until you get rolling ignore 99% of it... ignore Waves, NI Reaktor, etc. Pick a ***small*** handful of synths to play with -- let's say FM8, z3ta-2, Diva, and a simple drum machine of some kind... maybe a drumsynth plugin that came with the DAW of your choice.

Learn how to drop and manipulate loops, call up synths and record/program MIDI, and finally add some very simple FX... a reverb here, a chorus there. To begin with only use the FX that came with your DAW of choice. You need to figure out what they all do and why they exist before you start asking about which Ozone preset to use on your master bus. Please don't start a thread asking for recommendations on Ozone presets for your master bus. Learn what EQ, delay, and reverb is first.

Spend a solid month or two or three developing a musical idea. Start with a drum loop or a simple drum MIDI track... add a bassline, come up with a melody idea, add some supporting chords that outline the overall song structure, develop sections of the song, etc. etc. After many months of actually using your tools you'll start to see the bigger picture... and you'll start looking to expand your toolset. You might find that you own a bunch of stuff that you actually have no real use for... which would be a sign of maturity, IMO.

[BDeep]

^^
kbackki, hats off.

[gamecat666]

Try and use stuff for more than 5 minutes before buying something else - its an obscene waste of money imho.

[Kaboom75]

I was like this guy when I started I was ok learning Omnisphere and Live 8 then I went and baught everything that was the best and ended up in a muddle.

One DAW one Synth one drum plugin learn that all month when you know alot about them only buy another if you have time to learn how to use it and it sounds better than what you already have. You and me are what are known as gearslutz.

You can end up not learning muisic and not making any of your own music because you have too many knobs to learn.

In your first six months collect tutorial videos on one DAW.

[highkoo]

Gearsluts lol.
Most of the 'gearsluts' I know read a shit ton of manuals and are pretty good at installing things and whatnot.

[thecontrolcentre]

[highkoo]

Looks like dads baby is smoking.

[fisherKing]

i just bought one of everything, and have made a 2-hour movie about my needs, what i want, how i need help getting started.

the trailer will show before 'the dark knight rises'...be sure to see it. my actual movie will open august; there will be a questionnaire to fill out afterwards...

[Trakstar]

http://www.kvraudio.com/forum/viewtopic ... 25#4983025
This is his first release, and I for one am completely amazed!!, this cannot be the same person from the video(but indeed it is!!)

[royaldeadman]

I appreciate the comments

[Trakstar]

I appreciate the comments

I actually enjoyed your song, keep going but do take some of the advice people have offered. At least you payed for the software, a lot of people just download the stuff for the sake of downloading it, and it will sit on their desktop and not even be touched(the pirate stuff that is)