[ddots-l] Re: suggestions needed, audio dropouts in sonar5

  • From: "hf" <neep23@xxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Mon, 24 Apr 2006 03:41:11 -0400

Hi John
I read the CPU meter by using the Jaws cursor.
I should be using 16 bit, although as you pointed out, jaws doesn't properly read the control right before asio button. All I get is 0 percent and I don't know what that means. Don't have a sited person right here to look at things right now. But reading the box with the Jaws cursor, says that I'm at 24 bit and next to it is a scroll down button. But clicking on it does nothing. So if in fact I'm at 24 bit, either I can't change it or this is the wrong place to do so. Changing the buffer size from 0 to 100 doesn't seem to do anything. When I bring back the dialog box, buffer size is back at zero.
Besides all that, Using Jaws 5.1 or narrator give no drop outs at all. I'm using Jaws 7.


HF
HF
----- Original Message ----- From: <fioresq1@xxxxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Sunday, April 23, 2006 11:31 PM
Subject: [ddots-l] Re: suggestions needed, audio dropouts in sonar5



hf: I have all those setting in sonar 4 and I'm still getting some
crackling. The only thing I can't check is the cpu meters with caketalking,
I've been told in the tutorial to present insert+controll+page dow, but when
I do that it says nothing. How did you read them? Also, I suppose you
could be having a conflict problem since you had the card working in sonar
4Are you using 24 or 16 bit? Also, be aware that in the audio options
general tab jaws doesn't properly read the controll right before asio butto,
which is called buffer size. I had a sighted person look at that area, you
might want to check it. John
----- Original Message ----- From: "hf" <neep23@xxxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Sunday, April 23, 2006 8:34 PM
Subject: [ddots-l] Re: suggestions needed, audio dropouts in sonar5



i/o buffers are set to 128.
Most I've seen the CPU usage meter go up to is 24 or 25 percent.
I was able to get to 40 percent in Sonar 4 before I started to get any
kind
of drop outs.
HF
----- Original Message ----- From: "Gordon Kent" <dbmusic@xxxxxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Sunday, April 23, 2006 8:18 PM
Subject: [ddots-l] Re: suggestions needed, audio dropouts in sonar5



> Have you checked your disk i/o buffers in the advanced tab of the audio > options dialog? The setting of 128 should be good. Have you checked
the
> CPU usage meter when you have a project loaded?
> Gord
> ----- Original Message ----- > From: "hf" <neep23@xxxxxxxxxx>
> To: <ddots-l@xxxxxxxxxxxxx>
> Sent: Sunday, April 23, 2006 8:12 PM
> Subject: [ddots-l] Re: suggestions needed, audio dropouts in sonar5
>
>
>> Yes
>> ----- Original Message ----- >> From: "Gordon Kent" <dbmusic@xxxxxxxxxxxx>
>> To: <ddots-l@xxxxxxxxxxxxx>
>> Sent: Sunday, April 23, 2006 8:01 PM
>> Subject: [ddots-l] Re: suggestions needed, audio dropouts in sonar5
>>
>>
>>> Are you using asio?
>>> Gord
>>> ----- Original Message ----- >>> From: "hf" <neep23@xxxxxxxxxx>
>>> To: <ddots-l@xxxxxxxxxxxxx>
>>> Sent: Sunday, April 23, 2006 7:58 PM
>>> Subject: [ddots-l] suggestions needed, audio dropouts in sonar5
>>>
>>>
>>>>I recently started working in Sonar 5 and I am having lots of audio
drop
>>>>outs. The strange thing is that, these are the same projects that I
was
>>>>working on in Sonar 4, except I didn't have any drop outs in Sonar 4.
>>>> I kept reading as to how much faster Sonar 5 was to Sonar 4 and I'm
>>>> finding quite the opposite.
>>>> Although, it was suppose to have migrated my settings from Sonar 4, >>>> I
>>>> must have either changed something or it did not migrate properly.
>>>> I'm running out of ideas. Please help.
>>>> This is mostly for audio, haven't tried too much midi yet.
>>>> Which settings should I be aware of in Sonar 5 that may have changed
>>>> from Sonar 4?
>>>> HF
>>>> ** 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


** 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: