• 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: Documentation for public utility classes?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation for public utility classes?


  • Subject: Re: Documentation for public utility classes?
  • From: Guy Shaviv <email@hidden>
  • Date: Tue, 28 Sep 2010 19:48:59 +0200

The inMaxFrames parameter of the constructor is not clear to me. Should it be st to the max files size? if so, why do I need to pass the inNumFrames in the Process method? is the inMaxFrames the largest inNumFrames I can pass, and if my file is bigger, I can call process repeatedly with more data as long as it's no more than inMaxFrames frames?

CASpectralProcessor(UInt32 inFFTSize, UInt32 inHopSize, UInt32 inNumChannels, UInt32 inMaxFrames);

Too bad. "as is" typically means you accept to use with all the bugs it may have and no warrantee on the results, not no documentation. You guys made some nice work to offer these utilities, offering no docs is like doing half the work, would have been a lot more useful with it. (Not complaining, just trying to motivate someone to write docs...)

Thanks.
Guy

On Sep 28, 2010, at 19:38 , William Stewart wrote:

> We don't have any. This is sample code provided with an "As Is" license.
>
> We're happy to answer questions about this as we can (and as time permits)
>
> Bill
>
> On Sep 28, 2010, at 12:05 AM, Guy Shaviv wrote:
>
>> Hi,
>>
>> Where can I find some docs or sample code for the public utility classes to help understand their usage and each argument in their methods? Specifically I'm interested in the CASpectralProcessor class, but docs for the rest of them would be useful. They seem to do a lot of useful tasks and there is no need for me to "reinvent the wheel" if I can use what's provided. I have a feeling they can do a lot more than I'm currently aware of due to the missing docs...
>>
>> Thanks.
>> Guy _______________________________________________
>> 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

  • Follow-Ups:
    • Re: Documentation for public utility classes?
      • From: William Stewart <email@hidden>
References: 
 >Documentation for public utility classes? (From: Guy Shaviv <email@hidden>)
 >Re: Documentation for public utility classes? (From: William Stewart <email@hidden>)

  • Prev by Date: Re: Documentation for public utility classes?
  • Next by Date: Re: Documentation for public utility classes?
  • Previous by thread: Re: Documentation for public utility classes?
  • Next by thread: Re: Documentation for public utility classes?
  • Index(es):
    • Date
    • Thread