iOS magiccookiedata error and intermittent audio stream errors

[Andrew Meinert]

I'm trying to implement a basic player in iOS and the player only works intermittently. 

I'll get this error, hear a second of audio, then nothing. 
info kAudioFileStreamProperty_MagicCookieData err ?knu 1970170687

It'll be followed by these errors when trying to play another track:
info kAudioFileStreamProperty_MagicCookieData err ?knu 1970170687
AudioQueueStart err \207\373\376\377 -66681
2013-09-14 13:27:57.738 -[AudioStreamer startInternal](915): Audio stream error

I'm using the player from within a collectionView.  All I'm doing is calling a function from the view controller cells that calls [rdio.player playSource:track_id];  I'm stopping the player when the collectionViewController disappears. 

This error persists through application stop/start (in debugger), and resetting iOS simulator content and settings.  It has worked previously with all the track_ids I'm testing. 

[Andrew Meinert]

I am of course initializing with the key and secret before the first stream attempt.  I really can't figure out rhyme or reason to when it works.  Any ideas?

[R. Kevin Nelson]

Hi Andrew,

I've seen the MagicCookieData error pop up in the course of normal functionality before, so while it's alarming, I don't think it's actually relevant.

The "AudioQueueStart err" on the other hand, probably is relevant.  Do you mind sharing some of the actual code you're using?  If you'd rather not share it publicly, you can email us at develope...@rd.io.

It would also be helpful if you send over the track keys you're testing with, and what region you're testing in.

Thanks!

Kevin

-- -- --

R. Kevin Nelson

API Engineer @ Rdio, Inc.

--
You received this message because you are subscribed to the Google Groups "Rdio API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdio-api+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rdio-api/b8b43d01-ab1c-4414-9698-8d5093b50d81%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Sharif Ahmed]

Hi Kevin,

I'm receiving the same errors that Andrew described. Would you mind sharing what issues caused the errors and if/how the errors were resolved?

Thank you,

  Sharif Ahmed

[R. Kevin Nelson]

Hi Sharif,

We haven't heard back from Andrew, and haven't been able to reproduce the issue.

If you can provide the details I requested above (track keys and region, or better yet, sample code that exhibits the bug), I'd be glad to investigate further, and will let you know how it goes.

Best,

Kevin

-- -- --

R. Kevin Nelson

API Engineer @ Rdio, Inc.

To view this discussion on the web visit https://groups.google.com/d/msgid/rdio-api/4235b765-c982-4780-8ba7-975dff595ab8%40googlegroups.com.

[Pavan More]

Hi Kevin,

I am same kind of issue regrading the streaming the song one by one. I want to know when streaming stops due to any reason for eg less internet speed . Is any rdio delegate method fired at that time . 

Thanks 

Pavan 

[al...@tiptopspeakers.com]

Kevin,

Same issue here. I've been able to reproduce the same warnings in the "Hello" Rdio sample app available on GitHub without any modifications. The console logs the following:

2014-01-31 11:21:39.048 Hello[37397:4f0b] -[RDSongStream rdioRequest:didLoadData:](182): track is not streamable.
AudioQueueStop err \316\377\377\377 -50

2014-01-31 11:21:39.050 Hello[37397:4f0b] -[AudioStreamer startInternal](915): Audio stream error

info kAudioFileStreamProperty_MagicCookieData err ?knu 1970170687

info kAudioFileStreamProperty_MagicCookieData err ?knu 1970170687

 

More importantly, the CPU usage skyrockets when streaming. On the simulator, the simple Hello app pulls about 200% utilization. Screenshot below. This basically makes implementing any sort of Rdio playback in my app a no-go. For comparison, I've used other streaming libraries that pull about 3-5%...

[R. Kevin Nelson]

Thanks for the info, Alex.

I haven't noticed the CPU usage spike, but the "track is not streamable" error is telling.  We do have a known bug with prebuffering unstreamable tracks, and there is a fix in the works.

Some more info on github: https://github.com/rdio/api/issues/112

I'll have a look at the CPU usage issue this week and let you know what I can come up with.

Best,

Kevin

-- -- --

R. Kevin Nelson

API Engineer @ Rdio, Inc.

--
You received this message because you are subscribed to the Google Groups "Rdio API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdio-api+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rdio-api/0fc5e72e-646d-45ae-a87a-550c1c27b3e1%40googlegroups.com.

[R. Kevin Nelson]

I've added a github issue for the CPU spike and will be following up with more information over there.

https://github.com/rdio/api/issues/113

-- -- --

R. Kevin Nelson

API Engineer @ Rdio, Inc.

[R. Kevin Nelson]

The CPU spike issue has been fixed in the v1.3.6 release.  More info at http://on.rdio.com/1hgwyRF.

-- -- --

R. Kevin Nelson

API Engineer @ Rdio, Inc.

[al...@tiptopspeakers.com]

Thanks so much! You guys rock.

[al...@tiptopspeakers.com]

Hey (again) Kevin,

The update did a great job of fixing the CPU draw bug and no longer throws any errors to the console. However, there still seems to be something fishy going on - a number of exception breakpoints (typically 4-6) are triggered by any sort of playback. Is this an issue you all have on record?

[R. Kevin Nelson]

Hi Alex,

I'm guessing you're seeing the same C++ exceptions that are mentioned in this issue: https://github.com/rdio/api/issues/69

As mentioned in that issue, changing your breakpoint to break on Objective-C exceptions only seems like a reasonable workaround to us right now.  Is that something that will work for you?

I've also updated the github issue with some more details from my recent investigation.

Best regards,

Kevin

-- -- --

R. Kevin Nelson

API Engineer @ Rdio, Inc.

On Mon, Feb 24, 2014 at 11:47 PM, <al...@tiptopspeakers.com> wrote:

Hey (again) Kevin,

The update did a great job of fixing the CPU draw bug and no longer throws any errors to the console. However, there still seems to be something fishy going on - a number of exception breakpoints (typically 4-6) are triggered by any sort of playback. Is this an issue you all have on record?

--

You received this message because you are subscribed to the Google Groups "Rdio API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdio-api+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rdio-api/45159edb-c33c-43cf-b502-8b0e6c612fd2%40googlegroups.com.

[al...@tiptopspeakers.com]

Kevin -

Looks to be the same issue. I'll change my exception breakpoint and rest easier knowing it's a known fluke. Thanks!