[ddots-l] Re: Sluggish behaviour!
- From: "Studio Montebello" <studiomontebello@xxxxxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Sat, 5 May 2007 11:46:12 -0400
Hey Mat!
Try unloading the audio meters by hitting control F2 twice quickly and see if
that brings you any joy!
Jean
Please visit my site at http://www.studiomontebello.com
You can also visit my girlfriend's art gallery at
http://www.marie-helenemasse.com
----- Original Message -----
From: "Matt Brown" <matthew_brown@xxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Saturday, May 05, 2007 4:13 AM
Subject: [ddots-l] Sluggish behaviour!
> Hi everyone, this may have been discussed prior to me joining this list I
> don't know, but I know something like this was mentioned on Midimag although
> no conclusion was reached as I recall.
>
> OK basically, I'm getting amazingly sluggish behaviour in Sonar 6.2 with CT.
> Having done some playing around, this problem occurs only when there is
> audio loaded on to at least one track as far as I can tell.
>
> I did experience something like this with JSonar and Sonar 5, although it
> wasn't as severe. Basically the worsed behaviour is with stopping playback
> with spacebar. One can hit space to stop playback, and using my stop-watch I
> timed Sonar's response at nearly 30 seconds yesterday. This is completely
> random however; sometimes it's 5 seconds, sometimes it's 30, I haven't
> worked out why this is.
>
> I have also noticed with CT, that moving up and down in the track view
> between track strips is faster over midi tracks than over audio tracks. This
> makes me wonder if the sluggish behaviour has anything to do with the
> graphical representations of peaks displayed on audio track strips.
>
> I have also noticed that using the transport controlls on my FW1884 causes
> an instant response for stopping and starting audio as far as Sonar is
> concerned, but CT takes an age to catch up; like I press stop on the FW, and
> CT takes up to 6 or 7 seconds to anounce the fact. Could this possibly mean
> that the problem has to do with the way Sonar and CT process keystrokes?
>
> This is really pretty serious as it's slowing down my work considerably, and
> I am trying to run a business here!
>
> Insedentally, my DAW is a 3.4 GHZ Intel Core-2 Duo, 2 gigs of DDR 2 ram, 3
> 120 gig 7500 Sata harddrives, 4 meg cache, 256 meg ATI Duel-head graphics
> card (with one head disabled), Intel Firewire PCI card, Taskam FW1884
> system, Windows XP SP2, no anti-virus or spyware active.
>
> Also can anyone tell me why CT has been written so that switching to
> controll-surface mode is easy enough, but that as soon as you hit any key on
> the keyboard, you're switched back to keyboard mode again? That's stupid!
> You need to be able to use both the keyboard and the controll-surface in
> order to work efficiently! You shouldn't have to keep manually switching
> into controll-surface mode every time you want to use it!
>
> I do hope some usefull feedback comes soon.
>
> Many thanks in advance,
>
> Matt
>
> ** 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úq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
Other related posts:
