Re: AUGraph deprecation

[Admiral Quality]

*I'm* out of line? Just... wow. And oh no, I might get removed from
this list and (maybe, if I care to bother) have to sign up again from
a different email? Horror of horrors!

We don't all play the forced upgrade game, there are some honest
business left out here and we don't make any money from this extra
work you force on us for absolutely no good reason other than to milk
customers to buy the same products over and over again. (And again,
why doesn't this *ever* happen in Microsoft's ecosystem?)

Anyway, the public is catching on, finally. Apple don't have much more
time left if they don't smarten up soon. With Jobs thankfully dead
you'd think that would have happened already, but I apparently he
wasn't the only c-word higher up there. Your corporate culture is
poison and rotting from the head down.

https://www.youtube.com/watch?v=AUaJ8pDlxi8

https://www.youtube.com/watch?v=UVzigC33sGc

https://www.youtube.com/watch?v=qNghvlAqzaA

You know I'm right. All you Apple employees and remaining loyal
fanboys should be ashamed of yourselves.

Repent, before Darwin gets you! (And I don't mean the kernel code you stole.)

- AQ


On Fri, Jul 13, 2018 at 4:28 PM, Chris Adamson  wrote:
> Dude, seriously, chill. You’re way, way out of line with the Terms of Use,
> and basic professional behavior.
>
> https://discussions.apple.com/docs/DOC-5952
>
> Be polite. Everyone should feel comfortable reading Submissions and
> participating in discussions. Apple will not tolerate flames or other
> inappropriate statements, material, or links. Most often, a "flame" is
> simply a statement that is taunting and thus arbitrarily inflammatory.
> However, this also includes those which are libelous, defamatory, indecent,
> harmful, harassing, intimidating, threatening, hateful, objectionable,
> discriminatory, abusive, vulgar, obscene, pornographic, sexually explicit,
> or offensive in a sexual, racial, cultural, or ethnic context
>
>
> —Chris
>
>
> On Jul 13, 2018, at 4:25 PM, Admiral Quality  wrote:
>
> And you should strongly consider not being planned obsolescence
> flogging asshole hypocrites.
>
> - AQ
>
> On Fri, Jul 13, 2018 at 4:22 PM, Doug Wyatt  wrote:
>
>
>
> On Jul 13, 2018, at 13:17 , Admiral Quality  wrote:
>
> Meanwhile we can still run Windows software written in 1995 on their latest
> OS.
>
> I can't wait to see you people go out of business.
>
> - AQ
>
>
> Deprecation doesn't mean removal.
>
> Carbon components have been deprecated for many years but still work.
>
> Deprecation just functions as a warning that you should strongly consider
> another API in new code, and a deterrent to complaints about missing
> features. For example, Audio Unit extensions are not supported by AUGraph,
> and won't be (couldn't be, without new API).
>
> Doug
>
> ___
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/invalidname%40gmail.com
>
> This email sent to invalidn...@gmail.com
>
>
 ___
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: AUGraph deprecation

[Admiral Quality]

And you should strongly consider not being planned obsolescence
flogging asshole hypocrites.

- AQ

On Fri, Jul 13, 2018 at 4:22 PM, Doug Wyatt  wrote:
>
>
>> On Jul 13, 2018, at 13:17 , Admiral Quality  wrote:
>>
>> Meanwhile we can still run Windows software written in 1995 on their latest 
>> OS.
>>
>> I can't wait to see you people go out of business.
>>
>> - AQ
>
> Deprecation doesn't mean removal.
>
> Carbon components have been deprecated for many years but still work.
>
> Deprecation just functions as a warning that you should strongly consider 
> another API in new code, and a deterrent to complaints about missing 
> features. For example, Audio Unit extensions are not supported by AUGraph, 
> and won't be (couldn't be, without new API).
>
> Doug
>
 ___
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: AUGraph deprecation

[Admiral Quality]

Meanwhile we can still run Windows software written in 1995 on their latest OS.

I can't wait to see you people go out of business.

- AQ

On Fri, Jul 13, 2018 at 4:15 PM, Doug Wyatt  wrote:
> I don't think we ever really knew when the deprecation be official. There are 
> yet a few things we want to add to AVAudioEngine for more feature parity, and 
> we don't want folks to be seeing warnings until that's done.
>
> I can say that there is now an availability mechanism so that we can mark 
> API's as "to be deprecated", and we have marked up AUGraph with that, to 
> appear ... someday.
>
> Doug
>
>
>> On Jun 8, 2018, at 7:59 , Benjamin Federer  wrote:
>>
>> Last year at WWDC it was announced that AUGraph would be deprecated in 2018. 
>> I just browsed the documentation 
>> (https://developer.apple.com/documentation/audiotoolbox?changes=latest_major)
>>  but found
>> Audio Unit Processing Graph Services not marked for deprecation. The AUGraph 
>> header files rolled out with Xcode 10 beta also have no mention of a 
>> deprecation in 10.14. I searched for audio-specific sessions at this year’s 
>> WWDC but wasn’t able to find anything relevant. Has anyone come across new 
>> information regarding this?
>>
>> Judging by how much changes and features Apple seems to be holding back 
>> until next year I dare ask: Has AUGraph API deprecation been moved to a 
>> later time?
>>
>> Benjamin
>
>  ___
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/aq%40admiralquality.com
>
> This email sent to a...@admiralquality.com
 ___
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: AudioUnit Instrument and FX in single bundle

[Admiral Quality]

Our Poly-Ana softsynth comes in two different flavors, one effect, one
instrument, exactly to get around this artificial barrier. Many VST
hosts have the same issue so making two versions is the best way to
go, IMHO.

- Mike/AQ


On Wed, Apr 6, 2016 at 7:23 PM, audioboy 77  wrote:
> Hi Tom
>
> Thanks, I tried that already but this does not give the same behaviour as
> FM8.  This also makes the AU appear only as an effect in Ableton Live.
>
> Even though FM8 only has a single bundle, it appears as two separate entries
> in both Logic and Live.   FM8 and FM8 FX.  In logic, you can scan each one
> independently in the Plug-In Manager and it reports one as 'aumu' and one as
> 'aumf'.  The bundle only contains a single executable.
>
> Im thinking maybe it has multiple entries in the .r resources file, but i
> dont know how to try that.
>
> Any ideas?
>
> Thanks!
>
> On Wed, Apr 6, 2016 at 8:36 PM, Tom Longabaugh 
> wrote:
>>
>> Hi-
>>
>> You can make your audio unit show up as both an instrument and effect by
>> making it’s AudioUnitType be kAudioUnitType_MusicEffect.
>>
>> Best,
>> T
>>
>> > --
>> >
>> > Message: 1
>> > Date: Tue, 05 Apr 2016 22:49:16 +0100
>> > From: audioboy 77 
>> > To: coreaudio-api 
>> > Subject: AudioUnit Instrument and FX in single bundle
>> > Message-ID:
>> >
>> > 
>> > Content-Type: text/plain; charset="utf-8"
>> >
>> > Hi
>> >
>> > I am currently trying to build an audio unit as both an instrument and
>> > FX.
>> > I have seen the Native Instruments FM8 appears as both an instrument and
>> > FX
>> > in Logic and Ableton Live, but I cant seem to figure out how they are
>> > managing this nice trick.  Does anyone know how to do this?
>> >
>> > Thanks
>> >
>> > AB
>> > -- next part --
>> > An HTML attachment was scrubbed...
>> > URL:
>> > 
>> >
>> > --
>> >
>> > ___
>> > Coreaudio-api mailing list
>> > Coreaudio-api@lists.apple.com
>> > https://lists.apple.com/mailman/listinfo/coreaudio-api
>> >
>> > End of Coreaudio-api Digest, Vol 13, Issue 57
>> > *
>>
>>
>>  ___
>> Do not post admin requests to the list. They will be ignored.
>> Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>>
>> https://lists.apple.com/mailman/options/coreaudio-api/audioboy77%40googlemail.com
>>
>> This email sent to audiobo...@googlemail.com
>
>
>
>  ___
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/aq%40admiralquality.com
>
> This email sent to a...@admiralquality.com

 ___
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Best practice for checking 64-bit AU support?

[Admiral Quality]

VST 2.4 and 3.x and any fully compliant hosts support 64 bit audio
data. (Cubase, Reaper, Ableton, etc...)

- Mike/AQ

On Wed, Mar 23, 2016 at 5:57 PM, James McCartney  wrote:
>
> On Mar 7, 2016, at 11:57 AM, Paul Davis  wrote:
>
>> The app I'm working on is an audio editor. It supports 32 or 64 bit files
>> natively.
>
>
> What format supports 64 bit sample depth? What program creates them?
>
>
> CAF supports double precision. I just tested that both Audacity and Sound
> Studio will open double precision CAF files.
>
>
> James McCartney
> Apple CoreAudio
> jmccart...@apple.com
>
>
>
>
>  ___
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/aq%40admiralquality.com
>
> This email sent to a...@admiralquality.com
 ___
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Fwd: How does one update a view position during a core audio render callback?

[Admiral Quality]

I'm totally guessing here as I'm not very knowledgeable in OS X
programming (I use VSTGUI3.6 RC2  and Symbiosis frameworks to do most
of it for me for our VST and AU plug-in products). But doesn't the GUI
system offer its own timer? An onIdle() function or something like
that? Basically, the GUI system calls YOU when it's ready to refresh
the frame. At that point you pull the values you need from the render
side, rather than have the render side push values to the GUI (the
vast majority of which would just get ignored anyway). The classic
example is a VU/peak meter (where you also reset the peak once you've
displayed it).

Sorry if that's not right or doesn't apply, but it's how the
frameworks I use do it.

- Mike/AQ



On Sun, Mar 8, 2015 at 1:36 PM, Patrick J. Collins
patr...@collinatorstudios.com wrote:
 It looks like your timer might not be firing consistently.  I would test 
 that first. I'm not sure
 what else is going on in your Application but if there is any tracking then 
 a timer will be
 blocked. If your timer isn't firing as expected try adding it like this:
 NSTimer *timer = [NSTimer timerWithTimeInterval:1.0 / 60.0 target:self
 selector:@selector(moveBox) userInfo:nil repeats:1];
 [[NSRunLoop mainRunLoop]addTimer:timer forMode:NSRunLoopCommonModes];

 Yeah unfortunately this didn't work either...  It seems that it fires
 properly until audio starts playing, and then the timer callback
 frequency goes down to the point that it only gets called 5 or 6 times
 over a 1.6 second period...  Super weird.

 Patrick J. Collins
 http://collinatorstudios.com

  ___
 Do not post admin requests to the list. They will be ignored.
 Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
 Help/Unsubscribe/Update your Subscription:
 https://lists.apple.com/mailman/options/coreaudio-api/aq%40admiralquality.com

 This email sent to a...@admiralquality.com

 ___
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list  (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to arch...@mail-archive.com