• 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: CAPlayThrough Unreliable/Busted?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CAPlayThrough Unreliable/Busted?


  • Subject: Re: CAPlayThrough Unreliable/Busted?
  • From: Christopher Liscio <email@hidden>
  • Date: Wed, 22 Dec 2010 11:53:47 -0500

Hey all,

I seem to have cleared up many of the issues I had with the sample code, and posted the results of my work here:

https://github.com/liscio/CAPlayThrough

The key differences are in CAPlayThrough.cpp and CARingBuffer.cpp. If you find any other bugs/etc, please contribute!

Cheers,

Chris Liscio
http://supermegaultragroovy.com
Learn _your_ music with Capo: http://capoapp.com

On Dec 21, 2010, at 1:03 PM, Christopher Liscio wrote:

> Tahome,
>
> Thanks for the links, and this extra bit of info. I'd appreciate more specific information whenever you happen to come across it.
>
> (I'm sure lurkers wouldn't mind hearing about it as well... :))
>
> Cheers,
>
> Chris Liscio
> http://supermegaultragroovy.com
> Learn _your_ music with Capo: http://capoapp.com
>
> On Dec 21, 2010, at 11:32 AM, tahome izwah wrote:
>
>> Actually, looking at the code now I recall having this rewritten by
>> someone else because I wasn't familiar with the CA internals back
>> then. The folks at the DSP Dimension did a terrific job implementing a
>> fix for us that not only got rid of the drop outs but also reduced
>> latency considerably. As I recall, the problem was with the AUPitch
>> unit that handles the rate conversion/drift but I'll have to re-read
>> all their comments/diff our code against the original to be sure what
>> they did exactly...
>>
>> HTH
>> --th
>>
>> 2010/12/21 Christopher Liscio <email@hidden>:
>>> Tahome,
>>>
>>> On Dec 20, 2010, at 4:53 PM, tahome izwah wrote:
>>>
>>>> CAPlayThrough never worked right and had long term stability issues,
>>>> especially when using anything other than the default built-in
>>>> devices. I ended up rewriting the whole thing because it was totally
>>>> unstable.
>>>
>>> Could you elaborate on the stability issues you came across, and how you overcame them?
>>>
>>> It's crazy that we don't have a working drop-in solution to enable software play-through on the Mac... :P
>>>
>>> Thanks,
>>>
>>> Chris Liscio
>> _______________________________________________
>> 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
>

 _______________________________________________
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

References: 
 >CAPlayThrough Unreliable/Busted? (From: Christopher Liscio <email@hidden>)
 >Re: CAPlayThrough Unreliable/Busted? (From: tahome izwah <email@hidden>)
 >Re: CAPlayThrough Unreliable/Busted? (From: Christopher Liscio <email@hidden>)
 >Re: CAPlayThrough Unreliable/Busted? (From: tahome izwah <email@hidden>)
 >Re: CAPlayThrough Unreliable/Busted? (From: Christopher Liscio <email@hidden>)

  • Prev by Date: Get application audio buffer
  • Next by Date: AU Instrument - Cocoa UI
  • Previous by thread: Re: CAPlayThrough Unreliable/Busted?
  • Next by thread: How to call GUI methods periodically?
  • Index(es):
    • Date
    • Thread