search

Notalib / LYT

m.e17.dk
GNU Lesser General Public License v3.0
10 stars 12 forks source link

Going back a section in the player -> sometimes jumps to start of file on iphone ( IOS 6 ) #466

Closed LDHgithub closed 11 years ago

LDHgithub commented 11 years ago

If you open a book on iphone and try to jump back from one section to a previous section aka (from one mp3 file to the end of the previous mp3 file), the correct text is shown but the sound starts from offset=0

I think this have something to do with the " seeked event" in player.coffee......

simmoe commented 11 years ago

This is also apparently a new issue - at least I can't reproduce in the live version. To reproduce, pick "Gummi-Tarzan" and choose "Afsnit 6" from the index. Start listening and then hit "back" a few times until it skips to previous chapter. On my iPhone the text is now the end of chapter 5, while the sound is the beginning.

LDHgithub commented 11 years ago

There were also a possible raze condition, which was fixed in SHA-hash f94917118de20f5a74c3be27309953a196be9433

NajaWulff commented 11 years ago

I've just checked this issue on Nota's iPhone (with iOS6), and I get a seemingly different bug: when I click the backwards button at the beginning of a new chapter, I can only get it to skip to the very last segment of the previous chapter - no matter how many times I click. This goes on my 'to test' list, and will be thoroughly checked out Friday 4th, 2013.

LDHgithub commented 11 years ago

This issue is a real pain in the **. I tested on live m.e17.dk and the same problem is there, going from afsnit 6 -> back to afsnit 5 - and it starts over from the very start of afsnit 5...hmmmmm...

But only sometimes :-) :-)

LDHgithub commented 11 years ago

if you this in coffeescript

"if isNaN event.jPlayer.status.duration or event.jPlayer.status.duration == 0"

it will translate in to something else than this

"if isNaN( event.jPlayer.status.duration ) or event.jPlayer.status.duration == 0"

That is why i like these "((((((((((((((((((((((())))))))))))))))))))))))))))))))"

mzedeler commented 11 years ago

The commit above should have fixed this issue.