[ddots-l] Re: Where to send debug reports for failing CT 5.2 functions
- From: "William R. McCann" <BillList1@xxxxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Mon, 13 Nov 2006 13:21:48 -0500
Hi, Jean,
Thank you for your report. David Pinto has updated CakeTalking 5.2 in
response. See
www.DancingDots.com/ct/5.2/
to download the latest update. After you install it, don't forget to run
the CONTROL+F12 configuration tests. INSERT+Q should tell you that you're
running
CakeTalking 5.2.9 after successful installation. Please do let me know if
this update addresses the problems you've been having.
If anyone wants to send a debug report that contains a screen shot, please
copy it to albert@xxxxxxxxxxxxxxx as he can actually see it. But do
continue to send all requests for support to support@xxxxxxxxxxxxxxx as
usual. Believe me, we're listening even if you don't hear from us right
away.
Here's an excerpt from a recent note David Pinto posted to the CakeTalking
Beta Testers.
...
I've fixed three bugs that have come to my attention. The fixes are in CT
5.2.9, which is now available for download. The bugs are the following.
1. When opening a real time effects dialog, CT was telling you to press F4
to access the SFZ options dialog. Oops! Sorry about that. I fixed it.
2. With keyboard help on, When pressing control extended up arrow, or
control extended down arrow, CT wasn't reporting what those keys do. I Fixed
it.
3. In the Inspector, on the Send pan and Send level controls,
CT was sometimes not discriminating between the Send's knob and the Send's
edit control.
It was calling both of those controls knobs. I Fixed it.
Now, Phil has also alerted me to discussions on the MIDI mag about CT.
Especially posts by Chi Kim. Here's my response to the issues that were
brought up.
1. When moving to the E Q enable/disable button or the band control that's
adjacent to it, CT Sometimes doesn't say anything. But this is not a CT bug.
Sonar sometimes doesn't provide the information in the accessibility string.
However, if you press ENTER on the enable/disable button, then move off of
it and back to it, then SONAR starts providing the information and CT can
report the control and its state.
2. In the Lexicon Pantheon dialog, CT provides the letter P to take you to
the preset box. Someone reported that they couldn't get to the preset box
without the JAWS cursor. They were trying to tab to it. However, because of
an odd behaviour of the Pantheon dialog, tabbing to the preset box is
problematical. What happens
is that when tabbing from the last control, or shift tabbing from the first
control, an about dialog box will keep popping up. This happens when you
shift tab from the reverb type knob. Or you tab from the bass frequency
knob.
So, pressing the letter P, is the reliable way of getting to the presets
list in the Pantheon dialog.
3. Chi reported sluggishness with CT in large audio projects, especially
when changing values on inspector controls. I can only duplicate this when
the continuous audio meters are displayed. Does anyone else
have sluggish response changing values in the Inspector?
4. Chi reported that in projects with large number of audio tracks, using
the skip to track hotkeys was sluggish. I can not duplicate this. The new
skip to track hotkey scheme is faster than the past CT scheme. For instance,
On my systems, in a project with 50 audio tracks loaded with audio data, if
I'm on say track 2, and I hold control and type 49, when I then press
ENTER, it takes one second or less to move to track 49. Does anyone else
have a sluggish response when skipping to a track?
5. Someone reported that in the clips pane, pressing CONTROL+ENTER to select
between the From and thru, was selecting from the beginning to the end. I
cannot duplicate this. Has anyone else had that problem?
...
Bill
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Studio Montebello
Sent: Friday, November 03, 2006 5:34 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
OK Phil.
Thanks anyway!
I'll keep plugging.
BTW I've reinstalled CT 5.2 many times with no success
Jean
Please visit my Web site at: www.studiomontebello.com
----- Original Message -----
From: Phil Muir <mailto:ddots@xxxxxxxxxxxx>
To: ddots-l@xxxxxxxxxxxxx
Sent: Friday, November 03, 2006 2:37 PM
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
Hi Jean!!
Sorry I can't help you out with this any further. Hmm, I guess you could
try uninstalling CT then, reinstalling it again. You never know, something,
may alter in Sonar's registry entries, if you do that.
Regards, Phil Muir
P J Muir Productions
Music And Audio Production
URL:
www.philmuir.com/
----- Original Message -----
From: Studio Montebello <mailto:studiomontebello@xxxxxxxxxxxx>
To: ddots-l@xxxxxxxxxxxxx
Sent: Friday, November 03, 2006 12:35 PM
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
Hi Phil!
No, that doesn't do it either!
It must be something real silly! I can insert a cakewalk EQ onto the track
no problem. It's only that inspector EQ that won't enable!!!
I really don't feel like reinstalling Sonar as everything works very well. I
use Sonar everyday with no problems other than that.
As for CT 5.2 clips pain not being accessible, I really dont care as I can
scrub with Tranzport or J Sonar where the new scrubbing is even better than
tranzport!!!
Thank you for your interest in my EQ problem though as no one else seems to
be!!!
Jean
Please visit my Web site at: www.studiomontebello.com
----- Original Message -----
From: Phil Muir <mailto:ddots@xxxxxxxxxxxx>
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, November 02, 2006 3:04 PM
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
Interesting. What happens if, when over the enable EQ button, you do a Jaws
key pass through then, press the enter key? Does the EQ get enabled then?
Regards, Phil Muir
P J Muir Productions
Music And Audio Production
URL:
www.philmuir.com/
----- Original Message -----
From: Studio Montebello <mailto:studiomontebello@xxxxxxxxxxxx>
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, November 02, 2006 5:23 PM
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
Hi Phil!
I can't activate it.
For one thing, CT 5.2 always report that the EQ is disabled and indeed, even
if I disregard CT's feedback, the EQ will not engage.
The only way I can use EQ on a track right now is to insert it on a track.
This is probably not a scripting issue as Gord says, but it's strange that
I'm having this problem since installing CT 5.2!
Jean
Please visit my Web site at: www.studiomontebello.com
----- Original Message -----
From: Phil <mailto:ddots@xxxxxxxxxxxx> Muir
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, November 02, 2006 11:53 AM
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
Jean, what probelm are you experiencing with the Track Inspector EQ?
Regards, Phil Muir
P J Muir Productions
Music And Audio Production
URL:
www.philmuir.com/
----- Original Message -----
From: Studio Montebello <mailto:studiomontebello@xxxxxxxxxxxx>
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, November 02, 2006 4:13 PM
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
Fine! if it's not a script issue, I will not bug you with that one anymore!
What about not being able to access the clips pain?
Jean
Please visit my Web site at: www.studiomontebello.com
----- Original Message -----
From: Gordon Kent <mailto:dbmusic@xxxxxxxxxxxx>
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, November 02, 2006 10:13 AM
Subject: [ddots-l] Re: Where to send debug reports for failing CT 5.2
functions
What do you mean by "unable to activate the eq" That really isn't a script
issue.
Gord
----- Original Message -----
From: Studio <mailto:studiomontebello@xxxxxxxxxxxx> Montebello
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, November 02, 2006 9:47 AM
Subject: [ddots-l] Where to send debug reports for failing CT 5.2 functions
Hi All!
I have taken debug reports of both failing functions of CT 5.2 namely:
1. Unable to access the clips pain, and
2. Unable to activate the EQ on the inspector view of an audio track.
Who should I send these 2 reports to. and what else can I do to get these 2
functions to work?
I have tried everything to get these to work, but I have found nothing wrong
in my windows settings nor in sonar 5.2. In fact, all tests are OK!
Jean
Please visit my Web site at: www.studiomontebello.com
Other related posts:
