Re: Varispeed ios
Re: Varispeed ios
- Subject: Re: Varispeed ios
- From: tahome izwah <email@hidden>
- Date: Mon, 21 Nov 2011 09:38:03 +0100
Brett,
all I said was that I was unable to get the Apple varispeed unit to
work due to the lack of proper documentation and example code. I have
said similar things about the CAClock documentation, their AudioUnit
templates etc which are consistently broken in almost every OS version
that Apple has released. Due to the lack of an alternative, I have not
been able to recommend something over the built-in AU templates, but I
know that Apple has a track record of producing code that just doesn't
work. When iOS 5 came out my goal was to compare its varispeed unit to
the solution we use in our code, which is the Dirac mobile pro
algorithm. My only connection to the DSP guys is that I have licensed
Dirac and that I am a fan of it (can't you tell). Perhaps I should get
paid for recommend it over and over, but I am pretty fed up by level
of documentation that Apple provides, so yes, I may be accused of
being a bit quick at recommending something else when hitting a bump
in the road.
I love using time stretching in my music as an artist and as soon as
something new comes out you can be sure I'll check it out. With the
Apple iOS version I have been unsuccessful so far. That's all I said,
I didn't mean to discourage anyone from using the built-in iOS
algorothm if he can get it to work.
DiracLE is free, and quite powerful given the price tag :-) So I see
nothing wrong with recommending it as an alternative to the built-in
stuff, especially since its DiracFx API seems to be the fastest time
stretching for polyphonic music on the planet. Noone is forced to buy
something from them, and I don't get paid for being a fan, if that's
what you mean. I don't work for them either. I do like their stuff and
I am happy with the level of support that they provide though.
Hope this clears things up
--th
2011/11/19 Brett Denizon <email@hidden>:
> I'm not trying to pick a fight here, it just seems like the solution offered
> by Tahome is not to try, to give up because he didn't get it working. Not a
> solution in my books. Definitely not an answer to the question. (then again
> neither is this)
> As for whether or not Tahome works for or is associated with dsp dimension,
> I am still interested in the answer to that.
> I am not saying that dspdimension do not write good stuff, and I'm sure the
> support is on par with the cost of licencing their code. But before we move
> to a third party, it would be nice to hear some solutions on the core audio
> mailing list about the core audio components. And it frustrates me a little
> to hear the answer to getting the varispeed unit working is to give up and
> go and use something else.
>
> On Sat, Nov 19, 2011 at 10:54 PM, Paul Davis <email@hidden>
> wrote:
>>
>>
>> On Sat, Nov 19, 2011 at 6:13 AM, Brett Denizon <email@hidden> wrote:
>>>
>>> @Tahome,
>>> So we should just all give up trying to get the varispeed unit to work
>>> and go and pay dspdimension instead? Great solution. (heavy sarcasm)
>>
>> this is entirely unnecessary.
>>
>>>
>>> You seem to advertise for dspdimension quite a lot here on the mailing
>>> list, what is the nature of your relationship to them? Are you a personal
>>> friend of stephan, or an ex employee etc?
>>
>> the dspdimension stuff is good. that's it. i don't know stephan. i don't
>> use it because its impractical to do so with GPL'd code. its almost
>> certainly better than apple's code in terms of functionality, and i have
>> every reason to believe that you'll get better technical support.
>>
>> there's no reason to cast aspersion on tahome's motives.
>
>
_______________________________________________
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