[ddots-l] Re: CakeTalking not talking
- From: "Kevin L. Gibbs" <kevjazz@xxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Fri, 16 Mar 2007 08:53:37 -0700
24 bit might be the problem. You could test it out by trying 48K 16 bit.
Then you'd really know.
K.
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Phil Halton
Sent: Friday, March 16, 2007 7:45 AM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: CakeTalking not talking
Hi kevin,
I wasn't able to really try this out because other things started happening.
right now I get complete system crashes after about 8 seconds of audio
recording. I'm using 44.1khz and I'm going to try today once more going
back to 16 bit recording(had been using 24 bit when things started going
bad). Everything was fine when I was using 44.1 16 bits. when I changed to
48khz 24 bit everything went south. even when going back to 44.1khz 24 bit
i get system crashes. So, My last hope is to use 44.1 16 bits again.
----- Original Message -----
From: "Kevin L. Gibbs" <kevjazz@xxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Thursday, March 15, 2007 2:30 AM
Subject: [ddots-l] Re: CakeTalking not talking
> Change your FA66 back to 48K and see if CT comes back up. If it does,
> change your sample rate in Sonar to 44.1 BEFORE changing the FA66 back
> to 44.1 and see if you then still have Sonar and CT working. K.
>
> -----Original Message-----
> From: ddots-l-bounce@xxxxxxxxxxxxx
> [mailto:ddots-l-bounce@xxxxxxxxxxxxx]
> On
> Behalf Of Luis Elorza
> Sent: Wednesday, March 14, 2007 8:53 PM
> To: ddots-l@xxxxxxxxxxxxx
> Subject: [ddots-l] Re: CakeTalking not talking
>
>
> did you try ctrl f12?
> can you open the inspector?
> and are you sure your track view is not minimized?
> did you try opening different projects?
>
> ----- Original Message -----
> From: "Phil Halton" <philhalt@xxxxxxxxxxx>
> To: "ddots-l" <ddots-l@xxxxxxxxxxxxx>
> Sent: Wednesday, March 14, 2007 5:16 PM
> Subject: [ddots-l] CakeTalking not talking
>
>
>>I have a problem wherein cake talking scripts are loaded (as reported
>>by pressing insert+Q), but none of its functions work. I.?E., refresh
>>with F6, the skip to track/field hotkeys etc.
>>
>> Everything was fine until I did the following:
>>
>> Wanting to see the difference in sound quality with higher sampling
>> rates, I switched my FA-66 sample rate to 48khz from 44.1khz, Cycled
>> the power as
>
>> suggested by edirol for the new rate to take effect, and started up
>> sonar.
>
>> I checked audio options in sonar and it recognized and listed the new
>> sample rate on the general page of audio options(I'm using ASIO
>> driver mode, so I didn't have to do any wave profiling etc) . I
>> recorded a track, played it back to see how much better 48khz would
>> sound compared to
>
>> 44.1khz and what I heard was total chaos--like clipping on steroids.
>>
>> So, I tried backing off the gain on the mic and re-recorded--same
>> result. Figuring it was something to do with the new sample rate, I
>> closed sonar, reset the fa66 to 44.1khz, and started sonar again.
>>
>> That's where the trouble began. I tried refreshing the screen with
>> f6 and nothing. I tried moving to a column with the shift numpad
>> keys, and got a
>
>> message of "no hot key". I rebooted the system figuring I really
>> fried something in the OS, but upon reboot, the same problem
>> persists.
>>
>> So now, although cakeTalking is loading with sonar, its not
>> functioning--as though it wasn't loaded.
>>
>> I won't worry about the sampling rate problem right now, I'd just
>> like to get CakeTalking back again. Any help or suggestions?
>>
>>
>> ** To leave the list, click on the immediately-following link:-
>> ** [mailto: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:-
>> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
>> ** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the
>> Subject:- faq
>>
>
> ** To leave the list, click on the immediately-following link:-
> ** [mailto: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:-
> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
> ** or send a message, to
> ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
> ** To leave the list, click on the immediately-following link:-
> ** [mailto: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:-
> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
> ** or send a message, to
> ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
>
>
** To leave the list, click on the immediately-following link:-
** [mailto: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:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto: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:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
Other related posts:
