• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:


  • Subject: Re: Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
  • From: William Stewart <email@hidden>
  • Date: Wed, 03 Nov 2004 14:52:36 -0800

Are the glitches at these lower buffer size conditions also occurring with
the built-in driver, or just with the M-Audio FW interface?

Bill

On 3/11/04 10:37 AM, "seb_plogue" <email@hidden> wrote:

> I did some more investigating with a M-Audio FW 410
> and the behavior I experience with Bidule is
> reproducible with both Live and Rax
>
> I chose Live because Stephan posted about his problems
> yesterday and Rax because from what I gather it's using AUGraph and
> the Audio Output Unit (which I guess should be the closest
> to a "perfect" implementation for accessing CoreAudio)
> All of these apps AFAIK would be making all the work for
> the requested buffer inside the IOProc using the same
> buffer size everywhere which would be different than some DAWs
> that would use different buffer size throughout the tracks
> depending on which one(s) have focus/external MIDI input.
>
> (All these done with an eMac G4/700 as it is easier to
> reach these cpu usages quickly)
>
> I get glitches/dropout if I set the buffer size to 256 and
> the cpu reaches about 70-something% (according to each app
> display, not using top/Activity Monitor), if I increment the
> buffer size to 512(or more), no glitches occur. If I use the
> built-in audio @ 256, no glitching there also.
>
> If I lower the buffer size to 128, it starts glitching
> way sooner (i'll say around the 50-something) and 64
> is even worse (40% or so)
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

--
mailto:email@hidden
tel: +1 408 974 4056

__________________________________________________________________________
Culture Ship Names:
Ravished By The Sheer Implausibility Of That Last Statement [GSV]
I said, I've Got A Big Stick [OU]
Inappropiate Response [OU]
Far Over The Borders Of Insanity And Still Accelerating [Eccentric]
__________________________________________________________________________



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
      • From: seb_plogue <email@hidden>
References: 
 >Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error: (From: seb_plogue <email@hidden>)

  • Prev by Date: Starter
  • Next by Date: Re: Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
  • Previous by thread: Re: Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
  • Next by thread: Re: Dropouts/Glitches with FW interfaces was Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
  • Index(es):
    • Date
    • Thread