[ddots-l] Re: problem with ProjectMix

  • From: Bryan Smart <bryansmart@xxxxxxxxxxxxxx>
  • To: "ddots-l@xxxxxxxxxxxxx" <ddots-l@xxxxxxxxxxxxx>
  • Date: Thu, 24 Mar 2011 01:55:44 -0400

For the benefit of the list, we worked this out. Doug had recently moved the 
ProjectMix, but accidentally re-attached his mixer and monitors to the outputs 
3/4 on the ProjectMix, instead of the main 1/2 outs. He was doing everything 
just fine in the software, but, of course, no connection to the monitors, then 
no sound.

No worries. It happens to the best of us. Yours truly has even had the common, 
but very embarrassing, experience of calling tech support about non-functional 
equipment (a printer, in this case), only to discover half way through the call 
that the power cord had wiggled just enough out of the connector on the back to 
prevent the printer from working. I've worked in all sorts of different 
technical support jobs over the last 15 years or more, and just about the first 
thing I want to know when I talk to customers with equipment that won't respond 
is "is it plugged in? Are you really really sure that all of the cables are 
attached?" Of course that's just such an obvious thing to check that it would 
never apply to me, right? I'd never be that dense! Hahaha.

Bryan

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Doug Daniels
Sent: Tuesday, March 22, 2011 8:16 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: problem with ProjectMix

Yes, Brian, I do have those recordings, and I have been going over them, to see 
what you said about starting a new project, to see if I am forgetting to do 
something. So, far I  can't can't find anything that I am not doing. 
Doug. P.S. I don't know how I would get my DAW to go on line, I don't have a 
long enough cord to go from the Quest modem. But, I wonder if you sit, with me 
on the phone, and listen to what my jaws says, that you might be able to check 
out some of the possible problems. 
Doug. 

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Bryan Smart
Sent: Tuesday, March 22, 2011 3:17 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: problem with ProjectMix

Hi Doug.

Do you still have the complete recordings that I made from all 5 days of 
training? If so, listen to the early part of day 2, when we discuss the general 
organization of Sonar in some greater depth. We briefly touch on the bus pane. 
Also listen to day 4, when we discussed mixing in depth. Remember when you 
placed effects on to buses, such as reverb? The master bus is also where we 
metered the level of the entire project, as well as added a compressor to help 
level out the entire mix.

I realize that was a challenging week. Typically, I structure the training to 
follow a few cycles through creating demo projects, starting with creating a 
very simple project in order to touch on concepts, progressing to using 
different synths and effects, and advancing to increasingly complex projects as 
time permits. I wish that we had time to go through a few project cycles. In 
your case, we were only able to make one cycle through a simple project that 
incorporated a lot of features, since I also had to help you learn procedures 
for using your mobile DAW, including its Onyx 1620I, for live recording, as 
well as the essentials for operating the ProjectMix.
It was unquestionably a huge amount of material to take in. That's why we 
recorded all of it, since, with the extensively involved list of training 
goals, and the short amount of time for covering it, there was only time to 
carefully explain, demonstrate, and have you demonstrate the work/repeat 
explanations back to me. A shorter list of goals, or a longer training period, 
would have permitted drilling on concepts. Hopefully, you still have the 
recordings, so that you can revisit my detailed explanations.

I've found that, when I'm learning something new, particularly when it is 
written, I miss a lot on my first pass. After reading the tutorial, you might 
find that listening to me explain concepts again will result in concepts 
clicking together that didn't click before. After that, reading through parts 
of the tutorial again, with your new understanding, will result in you picking 
up on concepts that slipped by you in the previous read.

Anyway, I think that we need to setup a time when I can connect to you over 
Tandem to troubleshoot this immediate issue. I'll follow-up with you about 
those arrangements off-list.

Bryan

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Doug Daniels
Sent: Monday, March 21, 2011 11:43 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: problem with ProjectMix

Thank you Cris. I had a week of hands on training with Bryan Smart, but I have 
found the tutorials to over whelming. I don't know what they are talking about. 
I don't know what a bus pain would be by name. I recorded with stand alone 
equipment for thirty five years. Everything in the computer realm has names I 
haven't heard of. Is there a place where I could learn what the terms mean? 
Like scrubbing I finally found out what that means.
Though I did it for years, with my analog tape deck. We never called it 
scrubbing. 
Thanks Doug. 

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Chris Smart
Sent: Monday, March 21, 2011 8:22 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: problem with ProjectMix

Doug, have you worked through the first few lessons in the CakeTalking tutorial?
For example, Lesson 7 covers the track columns specific to audio, and the bus 
pane.

Chris

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=subscribe
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?subjectzq 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úq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq

Other related posts: