Transition iOS code to use AVAudioSession instead of AudioSession about novocaine HOT 12 OPEN

Good catch. Have you worked with AVAudioSession before? If so, do you
anticipate this being a big change?

On Wed, Jun 12, 2013 at 4:42 PM, Nick D. [email protected] wrote:

As of iOS7, the pure-C AudioSession API is deprecated. Not a high priority
here as a lot of the corresponding AVAudioSession capabilities were only
rolled out with iOS 5 or 6, but definitely an issue to have on record if
Novocaine is going to have a long lifetime.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48
.

from novocaine.

I find it a lot easier than the C API. It will only be a big change in terms of supporting specific ios versions, since a lot of the equivalent AVAudioSession stuff wasnt added until 6.

iOS 7 isnt out til fall and deprecations usually take about 2 releases to be dropped, so I don't think it's worth worrying about for a year or so.

from novocaine.

In the keynote, Tim Cook showed that 93% of people are on iOS 6. I'd be
fine with starting a "DEPRECATED" branch, and then moving everything to a
more modern setup.

On Wed, Jun 12, 2013 at 6:23 PM, Nick D. [email protected] wrote:

I find it a lot easier than the C API. It will only be a big change in
terms of supporting specific ios versions, since a lot of the equivalent
AVAudioSession stuff wasnt added until 6.

iOS 7 isnt out til fall and deprecations usually take about 2 releases to
be dropped, so I don't think it's worth worrying about for a year or so.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-19359702
.

from novocaine.

Sounds good to me. I have an ARC compatible, modernized branch on my fork.
No change to the API usage though. I will open a pull request sometime soon.

On Wednesday, June 12, 2013, Alex Wiltschko wrote:

In the keynote, Tim Cook showed that 93% of people are on iOS 6. I'd be
fine with starting a "DEPRECATED" branch, and then moving everything to a
more modern setup.

On Wed, Jun 12, 2013 at 6:23 PM, Nick D. <[email protected]<javascript:_e({}, 'cvml', '[email protected]');>>
wrote:

I find it a lot easier than the C API. It will only be a big change in
terms of supporting specific ios versions, since a lot of the equivalent
AVAudioSession stuff wasnt added until 6.

iOS 7 isnt out til fall and deprecations usually take about 2 releases
to
be dropped, so I don't think it's worth worrying about for a year or so.

—
Reply to this email directly or view it on GitHub<
https://github.com/alexbw/novocaine/issues/48#issuecomment-19359702>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-19359754
.

Nick Donaldson
[email protected]

from novocaine.

That sounds great.

On Wed, Jun 12, 2013 at 6:28 PM, Nick D. [email protected] wrote:

Sounds good to me. I have an ARC compatible, modernized branch on my fork.
No change to the API usage though. I will open a pull request sometime
soon.

On Wednesday, June 12, 2013, Alex Wiltschko wrote:

In the keynote, Tim Cook showed that 93% of people are on iOS 6. I'd be
fine with starting a "DEPRECATED" branch, and then moving everything to
a
more modern setup.

On Wed, Jun 12, 2013 at 6:23 PM, Nick D. <[email protected]<javascript:_e({},
'cvml', '[email protected]');>>
wrote:

I find it a lot easier than the C API. It will only be a big change in
terms of supporting specific ios versions, since a lot of the
equivalent
AVAudioSession stuff wasnt added until 6.

iOS 7 isnt out til fall and deprecations usually take about 2 releases
to
be dropped, so I don't think it's worth worrying about for a year or
so.

—
Reply to this email directly or view it on GitHub<
https://github.com/alexbw/novocaine/issues/48#issuecomment-19359702>
.

—
Reply to this email directly or view it on GitHub<
https://github.com/alexbw/novocaine/issues/48#issuecomment-19359754>
.

Nick Donaldson
[email protected]

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-19359956
.

from novocaine.

So, do you think starting from iOS6 we have all equivalents in AVAudioSession?
If Yes - it will be really easier to work with objC code instead on C
because now it a bit hard to fix something if need

from novocaine.

Given the fact that the C API is going to be deprecated, I would say yes. I
dont think they would do that without providing all the necessary config
options.

On Wednesday, June 12, 2013, Igor Khomenko wrote:

So, do you think starting from iOS6 we have all equivalents in
AVAudioSession?
If Yes - it will be really easier to work with objC code instead on C
because now it a bit hard to fix something if need

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-19360707
.

Nick Donaldson
[email protected]

from novocaine.

Sorry to be a bother, but is this likely to be worked on any time soon? I'd really love to use Novocaine for my project but if it's based on the deprecated AudioSession API I might have to figure something else out now that iOS 8 is already released. Thanks, really appreciate the work so far on this!

from novocaine.

@ndonald2 It's been quite some time, but have you ever done any work on this?

@mikeyzcai, I'm afraid I'm a bit out of the game when it comes to Novocaine, and I can't promise any time to this project in the near future. Hopefully there's an update floating around, and hopefully that comes in as a pull request, which I will gladly test and merge.

from novocaine.

@alexbw I have, it's a pretty straightforward migration to the new API. But I don't have a ton of time right now.

@mikeyzcai If you are familiar with AVAudioSession at all, I'd encourage you to fork novocaine and make the changes yourself, then submit a PR. There should only be a few places where the AudioSession is configured in novocaine.

If that doesn't work for you, The Amazing Audio Engine is another library that you might find useful for a modern iOS project.

from novocaine.

I am using Tonic + Novocaine on iOS 8 and experiencing weird audio tear issues, where the audio plays for 2-3 secs, then stops for a few secs, drops back in … Sounds like some other process is blocking the rendering process. Only happens on device (iPhone 5s), not in the simulator. I tried to find what the issue was and saw XCode warnings about the deprecations of the C audio API. Could they possibly be causing this sort of behaviour? Maybe it's being forced to work on a low-priority thread by the OS. I'm asking so I can decide whether I should try to replace it with AVAudioSession. Another weird thing is that audio seems to be playing in a semi tone higher pitch in simulator than on device, which is probably due to sampling rate issues.

from novocaine.

This is likely due to Novocaine using older APIs. If you transition Novocaine to the newer APIs, I would absolutely love a pull request so that everyone can benefit and Novocaine can continue to be useful for people.

On Oct 26, 2014, at 12:31 PM, Halldór Eldjárn [email protected] wrote:

I am using Tonic + Novocaine on iOS 8 and experiencing weird audio tear issues, where the audio plays for 2-3 secs, then stops for a few secs, drops back in … Sounds like some other process is blocking the rendering process. Only happens on device (iPhone 5s), not in the simulator. I tried to find what the issue was and saw XCode warnings about the deprecations of the C audio API. Could they possibly be causing this sort of behaviour? Maybe it's being forced to work on a low-priority thread by the OS. I'm asking so I can decide whether I should try to replace it with AVAudioSession. Another weird thing is that audio seems to be playing in a semi tone higher pitch in simulator than on device, which is probably due to sampling rate issues.

—
Reply to this email directly or view it on GitHub.

from novocaine.