[ddots-l] Re: What Have You Always Wanted to Know About Audio?

  • From: "Neville Peter" <neville@xxxxxxxxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Thu, 12 Jul 2012 18:23:25 -0400

Hello Chris
What is your blogging platform? I have tried to blog, but I can't seem to
find one that's accessible. 

May the Peace of God which passes all understanding guard your heart and
mind in Christ Jesus. God bless you! 

Website http://www.nevillepeter.com

Email neville@xxxxxxxxxxxxxxxx 

Phone 407-222-4488

Web store http://www.nevillepeter.com/store


-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Rui Vilarinho
Sent: Thursday, July 12, 2012 5:53 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: What Have You Always Wanted to Know About Audio?

Great idea Chris,

Side chain compressing, just one more  idea for a subject!

good luck,
Rui 


----- Original Message ----- 
From: "Chris Smart" <csmart8@xxxxxxxxx>
To: <midimag@xxxxxxxxxxx>
Cc: <ddots-l@xxxxxxxxxxxxx>; <jazz_guitar@xxxxxxxxxxxxxxx>
Sent: Thursday, July 12, 2012 8:22 PM
Subject: [ddots-l] What Have You Always Wanted to Know About Audio?


> Hi folks.
> 
> I'm developing a blog for my Website to attract more potential 
> clients.  Among other things, I will be posting regular columns 
> answering questions about audio, sound, whatever you want to know 
> really.  Perhaps you've never quite understood phasing, or how an 
> EQ or compressor work, or what harmonics are.
> 
> The posts will appear in a category called "sound advice", and 
> rather than guess what people want to know, I thought I would ask 
> here for ideas.  Of course, answer off-list with suggestions if you 
> want.
> 
> The blog isn't live yet, but I'm going to make sure it is populated 
> with lots of content by the time it does get incorporated into my 
> Website.
> 
> and yes, I know these sorts of basic questions are already answered 
> in a million places already, such as books, websites, wikipedia, 
> college courses, etc. But I enjoy the challenge of explaining 
> concepts simply and clearly, and let's face it, I want potential 
> clients to think I know what I'm doing. :)
> 
> So, have at it. The only stupid question is one you don't ask.
> 
> Chris
> --------------------------------------------------
> CTS MASTERING: http://www.ctsmastering.com
> Twitter: https://twitter.com/#!/CTSMASTERING
> Facebook: https://www.facebook.com/pages/CTS-Mastering/139114066128698
> Linked In: http://ca.linkedin.com/pub/chris-smart/46/824/536
> Dropbox: Have your stuff when you need it. 2GB is free: 
> http://db.tt/bQ2GuIt
> 
> PLEASE READ THIS FOOTER AT LEAST ONCE!
> To leave the list, click on the immediately following link:
> ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
> If this link doesn't work then send a message to:
> ddots-l-request@xxxxxxxxxxxxx
> and in the Subject line type
> unsubscribe
> For other list commands such as vacation mode, 
> click on the immediately following link:
> ddots-l-request@xxxxxxxxxxxxx?subject=faq or
> send a message, to 
> ddots-l-request@xxxxxxxxxxxxx
> and in the Subject line type
> faq
> 
>
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, 
click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or
send a message, to 
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq


PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, 
click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or
send a message, to 
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq

Other related posts: