The Sword and Laser discussion

187 views
Help with Audible

Comments Showing 1-9 of 9 (9 new)    post a comment »
dateUp arrow    newest »

Jenny (Reading Envy) (readingenvy) | 2898 comments So while I have the Audible app on my iPad, I use an old school iPod mini (pre-screen) to listen to my audio books, because I can clip it to what I'm wearing and go out for a walk without worrying about it.

Audible divides the books up into huge tracks that are larger than chapters, for instance Good Omens is in two parts. I have already listened to the first two hours of the second track twice since there wasn't a way to sync between the app and the old-school iPod.

When I got back from my walk today, I pushed BACK instead of PAUSE, and heard the Audible intro and groaned... is there any way to find my way back to where I was?


message 2: by Jeremy (new)

Jeremy Paine | 13 comments I've run into the same issue enough times that I quit using my shuffle to listen to audiobooks. However, there are a couple of coping strategies...
Audible books typically have chapters, and iTunes/iPods can see these, as does the audible app. If you have the book in your iTunes library, you can use the "Chapters" menu to jump chapters until you find your spot. You'll want to sync with the ipod, which will update your (negative) progress in iTunes, then use iTunes to find your place again with the chapter menu, and re-sync. This should get your ipod back to where you want to be. In the end though, the screen-free ipod models are just not ideal for audiobook duties.


message 3: by Sean (new)

Sean O'Hara (seanohara) | 2365 comments Jenny wrote: "So while I have the Audible app on my iPad, I use an old school iPod mini (pre-screen) to listen to my audio books, because I can clip it to what I'm wearing and go out for a walk without worrying ..."

Nice to know I'm not the only one still using that antique.

If you hold down the next-track portion of the scroll pad on the very inside, right next to the hub, it'll fastforward, but it's extremely awkward. It might be easier to use iTunes to find the right place and then sync back to the iPod.


message 4: by terpkristin (new)

terpkristin | 4407 comments I also use an iPod shuffle for this kind of thing (though I admit I also have a classic, an iPhone, and a Nano as well....). I think the only way I've successfully not "screwed" myself was by using iTunes to get to the right place...man I hate it when I accidentally hit the buttons and skip. :(


message 5: by Tony (new)

Tony Victorine (tonyv) | 1 comments I listen to audiobooks on my nano as well and have run into this issue, if you click the center button twice a diamond should appear on the progress bar then you and run your finger around the wheel to fastforward or rewind faster then holding the forward button down.


Jenny (Reading Envy) (readingenvy) | 2898 comments Mine is so old I don't have a spinning wheel or a progress bar, haha. Anyway, I really appreciate the advice. I'll try syncing it in iTunes tonight!


message 7: by Tom (new)

Tom (tomcamp) | 34 comments Audible books are separated into chapters. A file can (and usually does) contain multiple chapters. If you sync your iPod with iTunes, you can use the Chapters feature in iTunes to get back to where you were, at least to the start of the chapter. I think Chapters are under Controls in iTunes.


message 8: by Paul (new)

Paul | 26 comments Jenny wrote: "Mine is so old I don't have a spinning wheel or a progress bar, haha. Anyway, I really appreciate the advice. I'll try syncing it in iTunes tonight!"

I had a simular problem, always having to relisten to things. I got around it by buying a new MP3 player.


message 9: by Simon (new)

Simon Wetz | 5 comments Has anyone found a fix for when you get a new phone and load the Audible app every thing is unfinished and I cant get it to show the details off the old phone. Audible support were sympathetic but said that this is just the way that it is but I seriously cant believe that. Any one found a work around for this really annoying time wasting issue?


back to top