yes I did, but at the moment, I can't remember what that was. Not trying to be funny, I just can't remember ----- Original Message ----- From: "Kevin L. Gibbs" <kevjazz@xxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx> Sent: Thursday, March 15, 2007 11:33 PM Subject: [ddots-l] Re: CakeTalking not talking
Did you do what I suggested in the message that preceeded yours? If you did, what happened? I don't have any other ideas. This might be one for Gord or someone else. K. -----Original Message-----From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] OnBehalf Of Phil Halton Sent: Thursday, March 15, 2007 10:10 AM To: ddots-l@xxxxxxxxxxxxx Subject: [ddots-l] Re: CakeTalking not talking Hi Kevin, It seems there's something screwed up with sonar or CT settings. CT wascoming up and telling me the control surface was ready, but none of the hot keys were working. So, I tried going into the buss pane just for laughs to see what would happen. Well, Shift+mid section down arrow caused CT to say "Track pane" (should have said buss pane if anything), and then the hotkeysstarted working as expected(more or less). At that point I could see that the buss pane popped up on the screen. Problem is, I'm on the master buss, but CT is acting like its in the track pane. With a Shift+mid section up arrow, CT says you're already in the track pane, but the buss pane doesn't close, and CT remains in the busspane. Doing a "say line" (insert+numpad 8) reads and reports audio track 1in the track pane, but moving with right or left arrows navigates through the fields of the master buss. I'm trying to explain this as best I can, but its confusing. As I move up and down from buss to buss (aux 1 aux 2 etc) CT reports mixed information from the buss & track panes. That is, as I press up and down arrows, CT says Aux 1, Midi track not recorded. Get it? its saying I'm landing on abuss, and telling me the status of a track in the track pane. Or, it thinksits landing on a track and giving me that tracks status, but giving me the busses name. Screwy huh? Additionally, As I right and left arrow, CT is reading and reporting the status of the Buss fields. So, I'm definitely in the buss pane, but CT is confusing track pane info with the buss pane. I can open the inspector, but there too CT says Audio track 1 named Master(audio track 1 is the name of the first track in thetrack pane) and obviously, Master is the buss name that I'm actually on. Icannot get into the track pane, as CT thinks its already there. With my limited sight I can see that the buss pane is open and cannot be closed with the CT hotkey (shift+mid section up arrow). Please Help if you have any insights. Would a re-install of CT be appropriate? I don't want to try to solve the problem with a drastic measure like re-installing CT before I understand its symptoms if you know what I mean. ----- 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 talkingChange 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 talkingI 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 assuggested 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 to44.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 amessage 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
** 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
