Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 2 days, 20 hrs ago - more...
|
2017-01-06
, 10:19
|
|
Posts: 171 |
Thanked: 337 times |
Joined on Jul 2010
|
#12
|
Thank you, hhbbap, that was really a good idea. I can confirm that my settings.json is, indeed, identical.
Originally Posted by hhbbap
Yes, I see these lines and they apparantly point to the right position. However, when I tap the play icon, sometimes it just starts from the beginning anyway. I'll keep an eye on it as more podcast episodes come in (only tried a couple).
The mediaplayer starts where the indicator of how much is played ends. Do you see these purple lines in your gpodder?
Originally Posted by hhbbap
Actually, I tried the same thing, including adding a softlink to ~/Music/gpodder. Which media player do you use? I tried Talefish (which BTW is a wonderful project on its own accord), but it seemed like the directory based approach of Talefish's playlist was "confused" by the constant adding and removing of audio files. However, just this morning velox released a new version with enqueing capabilities. I'll test it as soon as new podcast episodes arrive.
Now I check for new episodes, manually select and download episodes (at home). After I have listen to an episode I usually delete it manually unless I want to keep it for longer.
|
|
2017-01-07
, 13:49
|
|
Posts: 171 |
Thanked: 337 times |
Joined on Jul 2010
|
#13
|
Just a very quick update. According to Thomas, who designed gPodder, the problem may lie with the underlying infrastructure (Qt MultimediaKit using GStreamer).
Is there a way we could upgrade the GStreamer components (gst-av etc.) to a newer version?
Also he suggested we should try the Android version. If the problem does not occur there, it must be the multimediakit. Unfortunately, I do not have an Android device.
Is there a way we could upgrade the GStreamer components (gst-av etc.) to a newer version?
Also he suggested we should try the Android version. If the problem does not occur there, it must be the multimediakit. Unfortunately, I do not have an Android device.
|
|
2017-01-16
, 10:39
|
|
Posts: 426 |
Thanked: 1,812 times |
Joined on Dec 2013
|
#14
|
The android version has the same problem on some files.
Overall comparing the android version to the sailfishos version the latter seems much more mature.
It saves the last state of the file playback even if oom killer kills it.
On Android if the app gets killed I need to start from the beginning.
Overall comparing the android version to the sailfishos version the latter seems much more mature.
It saves the last state of the file playback even if oom killer kills it.
On Android if the app gets killed I need to start from the beginning.
|
|
2017-02-07
, 22:53
|
|
Posts: 171 |
Thanked: 337 times |
Joined on Jul 2010
|
#15
|
Originally Posted by llelectronics
@llelectronics, thanks for looking into this.
The android version has the same problem on some files.
@all, I was wondering whether any of the developers among you could maybe take a quick look at this file?
https://github.com/gpodder/gpodder-u...erPlayback.qml
It's where gPodder saves the positions within audio files.
In particular it might be interesting to see in what ways it differs from Talefish, where saving positions has been working flawlessly.
To build gPodder from source, you may want to follow these instructions detailed by Thomas.
https://github.com/gpodder/gpodder-sailfish/issues/46
According to Thomas the Sailfish and Android versions ought to be comparable (the same?). He suspects gstreamer to be at fault. Updating gst-av etc. might be an option (if I only knew how).
| The Following User Says Thank You to dubliner For This Useful Post: | ||
 |
|
2017-02-07
, 23:39
|
|
Posts: 394 |
Thanked: 1,341 times |
Joined on Dec 2009
|
#16
|
Originally Posted by dubliner
I don't think Talefish is comparable in this regard, because gPodder is a lot more complex. From a quick glance, I gathered it passes the value through signals and to python, where it's stored somewhere – didn't have the time or python-fu to check further. Talefish just sets it in a QML Object ("Appstate"), which is auto-saved to LocalStorage once in a while or on app exit.
In particular it might be interesting to see in what ways it differs from Talefish, where saving positions has been working flawlessly.
Originally Posted by dubliner
Assuming the correct values are saved (which they should as long as some kind of progress output behaves correctly in the gui), perhaps the initially scanned duration of the file is wrong and so gpodder thinks there's no way to seek that far into a file? (Please note I'm pulling all of this out of my… brain without checking and I have not even used gPodder in a while. So I could be utterly and completely wrong here!)
According to Thomas the Sailfish and Android versions ought to be comparable (the same?). He suspects gstreamer to be at fault. Updating gst-av etc. might be an option (if I only knew how).
__________________
slumber: sensors enabled sleep timer for SFOS (translations/input/… appreciated if you've got some spare time)
talefish: directory based audiobook player for SFOS
nofono: ofono restart for SFOS
___
list of i486/noarch packages on openrepos (jolla tablet)
slumber: sensors enabled sleep timer for SFOS (translations/input/… appreciated if you've got some spare time)
talefish: directory based audiobook player for SFOS
nofono: ofono restart for SFOS
___
list of i486/noarch packages on openrepos (jolla tablet)
Last edited by velox; 2017-02-07 at 23:48. Reason: clear up talefish stuff
Now I check for new episodes, manually select and download episodes (at home). After I have listen to an episode I usually delete it manually unless I want to keep it for longer.
PS! I have made a softlink from /home/nemo/.local/share/harbour-org.gpodder.sailfish to a harbour-org.gpodder.sailfish folder on the SD card (/media/sdcard/....) so gpodder download files to the SD card (this folder use 17GB for me now).
Last edited by hhbbap; 2017-01-05 at 21:40. Reason: be more specific vs. 17GB