[Grimlin]

Originally Posted by ValB626

On another note, I added a bunch of music to my media card last evening. When I opened audible later on, the start-up was extremely long. Instead of hovering at the 3/4-7/8 position on the progress bar, however, the long hover occurred at about the 9/10 position. I'm thinking the app read through all the new files on the media card?

If this continues past the first load, you might want to consider removing the app and reinstalling.

[Ripley 29]

Originally Posted by Grimlin

Is there a pattern to either of these? I haven't experienced them. Have you sent them to Audible? If not, I would like to add them to my list and submit them next time.

I'll look into this in some more detail, but here's what I think is happening:

- When I pause, then play, many times it will show the time being the same, and yet the audio will be 30-40 seconds behind (Like it's basically rewound 30 seconds and started playing). What it seems to be doing is speeding up the audio to 'catch up' to where it's supposed to be time-wise.
- If I pause, then play, and repeat this a few times, it seems to lose 30-40 seconds at a time. So sometimes it could be 5 minutes behind, and doing the sped up audio until it 'catches up'.

I have not sent this to Audible yet, so feel free if you think we should keep all issues together.

I have not heard this issue since .68, but I haven't listened too much since I've got it. I will tomorrow, and try and isolate exactly how to recreate this issue.

[Grimlin]

Originally Posted by Ripley 29

I have not heard this issue since .68, but I haven't listened too much since I've got it. I will tomorrow, and try and isolate exactly how to recreate this issue.

If it happens in .68, let me know. I will try it on mine as well to see if it is device/OS specific. I'll add it to the "Big List" and send it in with my next report.

[Grimlin]

Got a message from Audible this evening. Their current priorities are the popping/stuttering between buffers and the end of book issues. Once those are stabilized, I would think we will see some of the other issues resolved. I was told however, due to device and OS limitations, the popping may be as good as it gets for now without a major overhaul of the streaming code. I sent this in response.

Originally Posted by Grimlin's Email to Audible

I see two options here. One is that all will be a field of roses with
the streaming additions of OS 4.5 (previously 4.3.1). The other is for
your folks to write a native codec and have RIM sign it.

[sowhynot]

I've been using .68 all weekend and I concur with most of the observations already posted. My three major issues are:

- the FF resets back to the beginning of section 1. Major issue. It probably took me close to 10 minutes to be able to successfully get back to the section I wanted to listen to.

- the popping/skipping noises worse than in .66 although there doesn't seem to be the major loss of dialogue that was in the original version.

- start-up time longer than before.

[DallasFlier]

Originally Posted by Grimlin

Got a message from Audible this evening. Their current priorities are the popping/stuttering between buffers and the end of book issues. Once those are stabilized, I would think we will see some of the other issues resolved. I was told however, due to device and OS limitations, the popping may be as good as it gets for now without a major overhaul of the streaming code. I sent this in response.

Happy to hear that's their priorities, I totally agree. But hasn't .68 fixed the end of book issues? I heard the end of one on .68 myself, all the way to the end.

Also agree with your note to them - I admit if I were them, with 4.3.1/4.5 due out apparently in 90 days or less, I probably wouldn't start down the path of codec development until determining whether that fixes the issue. Some here have advance betas of 4.5, Audible needs to get one of them to try it. I know that one of the mods - jibi - has it.

Originally Posted by sowhynot

I've been using .68 all weekend and I concur with most of the observations already posted. My three major issues are:

- the FF resets back to the beginning of section 1. Major issue. It probably took me close to 10 minutes to be able to successfully get back to the section I wanted to listen to.

- the popping/skipping noises worse than in .66 although there doesn't seem to be the major loss of dialogue that was in the original version.

- start-up time longer than before.

Agree with all the above. And the resets - a new issue I think - is quite frustrating and time consuming, as you say.

[sowhynot]

Has anyone been successful in downloading daily subscriptions with .68? It appears that it downloads, but I get an error message "failed to open file."

I know I can download via my computer and transfer to my SD card but would like the other option to work as well.

[ValB626]

Originally Posted by sowhynot

Has anyone been successful in downloading daily subscriptions with .68? It appears that it downloads, but I get an error message "failed to open file."

I know I can download via my computer and transfer to my SD card but would like the other option to work as well.

Once I got into civilization from central PA last night, .68 downloaded the current issues of my subscriptions just fine and I could play them this morning.

This further indicates some of these issues are a function of signal strength.

ALSO, the speed with which the app comes up is MUCH faster down here than up in PA (another signal strength indication?).

Listened to a book for the 3.5 hour drive down from central PA to DC last night. No episodes of garbling/speed changes or skreetching. Navigated to another app only once, forgot to set a bookmark, but got back to the audible player at the correct place with no problems.

Did a bunch of FF'ing and using the 9 button to move forward to later sections when starting to listen to the book. Daughter and I had listened to about half of it on an iPod before, so it took some time to find where we'd left off. No incidents of resetting to section 1 during our search efforts. We also navigated backwards in the book at various points to hear portions we'd missed because of loud trucks or other distractions. No resets.

Much hilarity associated with the 4-minute pops. Actually, the 4-min pops seemed to occur at intervals longer than 4 mins, but we could have simply missed some of them because of external noise, conversation, or other distractions.

The player volume is just too loud for listening in a silent room through earbuds when trying to go to sleep. The correct volume is somewhere between no sound and the first volume bullet. I think this is an 8130 problem, rather than an audible app problem because it's the same with the BB mediaplayer and another third-party media player I have. I have a continuous volume control device from Radio Shack and plugged it in last night between the BB and my earbuds. It enabled me to decrease the volume to a tolerable/sleep-inducing level. Am still hoping, long down the road, for a sleep timer function.

btw, because of the size of the 8130 output jacks, we were able to plug the BB into my daughter's hardwired MP3 player system in her car last night, and I can also plug it into my JBL speakers that I got for my iPod, and listen to audio media from the BB just fine.

I'm thinking that the transition to the new 4.5 OS isn't going to solve the problems those of who have 8130s are seeing with .68. Our 4.3XXX OS already supports most of the functionality I'm seeing described for 4.5, but these are CDMA devices, so that may make a difference. However, I'm looking forward to hearing audible's recommendations for dealing with VZW...

[sowhynot]

Originally Posted by ValB626

Once I got into civilization from central PA last night, .68 downloaded the current issues of my subscriptions just fine and I could play them this morning.

This further indicates it's a function of signal strength.

For me it downloads just fine (or appears to) but it won't open the file.

[armandinho]

Hi Everyone... just installed the new beta today (1.0.68)... it was on the support website. I've got an 8100 on a BES running OS 4.2.064

Got an
"Error Starting AudibleRIM: Symbol 'RadioInfo.areWAFsSupported' not found"

What on earth is a WAF!? Thanks for any help!

Armando

[Grimlin]

Originally Posted by armandinho

Hi Everyone... just installed the new beta today (1.0.68)... it was on the support website. I've got an 8100 on a BES running OS 4.2.064

Got an
"Error Starting AudibleRIM: Symbol 'RadioInfo.areWAFsSupported' not found"

What on earth is a WAF!? Thanks for any help!

Armando

In your settings, is it set to WiFi preferred(It shouldn't be)?
What happens to it if you go into options/advanced/service books and delete Desktop [IPPP]?

You can press menu and undelete it afterwards as long as that is the only service book you delete.

[Grimlin]

Originally Posted by armandinho

Hi Everyone... just installed the new beta today (1.0.68)... it was on the support website.

Where on the support site? I cannot find anything on the support site. Are you certain you didn't download 1.0.58? The links we have been using are hosted by the developer.

[Grimlin]

Originally Posted by Grimlin

Where on the support site? I cannot find anything on the support site. Are you certain you didn't download 1.0.58? The links we have been using are hosted by the developer.

OK, Got a PM with the support article. I am checking with our contact at Audible to see if it was supposed to be out there or not. If it is, we can point people to that article.

[Grimlin]

OK, there is a config file we could be using.

AudibleProfile.xml

Drop into /music/audible folder in main memory.

0 = forced mode and will ignore the other values.

We can also try changing packet sizes and enabling the logs...

<connection>

  <defaultProfile>N</defaultProfile>

  <customProfile>

    <HTTP>1</HTTP>

    <BIBS>0</BIBS>

    <MDS>2</MDS>

  </customProfile>

  <BIBSpacketSize>512</BIBSpacketSize>

  <MDSpacketSize>512</MDSpacketSize>

  <enableLog>N</enableLog>

</connection>

[hokie123]

I loaded 1.0.68 yesterday, and have been able to successfully download from my library OTA, as well as transfer books from my computer to the media card.

I have one book, The Screwtape Letters by C.S. Lewis, which seems to have problems with this version of the software. When I start to play from the beginning, I hear "This is Audible", then after waiting for the buffering to complete, I get complete silence (but I see the timer incrementing, so it thinks it's playing).

If I forward to the next section of the book, it begins playing just fine from that point. I tried fast-forwarding to a middle segment of the first section, but still get silence.

The only way I was able to get the book to play from the beginning was to press 7 to index to the beginning, then press 6 two times to move the timer to 00:03. If I play from that point, it works just fine. If I just move forward to 00:02, I still get the silence.

I tried downloading the book OTA numerous ways (five minutes, 30 minutes, 60 minutes), and also loaded my copy from the computer to the media card (even tried re-downloading the copy I had on my computer). All of these exhibited the same symptoms.

So far I've tried three other books, along with their weekly free download. None of the others have this problem.

I have played The Screwtape Letters successfully on two other mp3 devices, as well as the older Blackberry version of Audible on my Curve, so I know the file works on their other software.

[Grimlin]

Originally Posted by Grimlin

I am checking with our contact at Audible to see if it was supposed to be out there or not. If it is, we can point people to that article.

I got a mixed response. He would rather we not post a link (Although anyone reading this can probably find it easily enough) . He is working with support on why it was posted. They had previously only been giving it out on an individual basis and reporting the customer information to him.

[Grimlin]

Anyone play with the XML config file yet? I plan to tonight if I can get the time to do it.

[armandinho]

Deleted

[armandinho]

Deleted

[armandinho]

Originally Posted by armandinho

Hi Everyone... just installed the new beta today (1.0.68)... it was on the support website. I've got an 8100 on a BES running OS 4.2.064

Got an
"Error Starting AudibleRIM: Symbol 'RadioInfo.areWAFsSupported' not found"

What on earth is a WAF!? Thanks for any help!

Armando

Hey Grimlin, thanks for the messages...

Here's the article where I found the beta:
Answer

This article actually exactly describes my problems with Audibleair... I managed to install an older version (1.0.55?) and it loaded fine, recognized the books I loaded on the SD alright, but I wasn't able to activate my account.

I got my hopes up with 1.0.68 but clearly it's got a glitch! Thanks for forwarding to the audible guys and any advice! Cheers!