pichlo | # 1251 | 2014-05-25, 00:29 | Report

It did not, BUT then I followed the CSSU-Thumb official upgrade which brought back a few previously removed packages and that fixed it. I don't know which one was the crucial one.

Funnily enough, the problem still reccurs from time to time. Downloaded video plays in Media Player once, twice, five times, then out of the blue stops playing although it keeps playing fine in CuteTube. Killing mafw-dbus-wrapper as you suggest helps in those cases. Which makes the issue OT in this thread, sorry.

This is from observation only so marxian may want to correct me. All paths are relative to MyDocs/cuteTube:
1. Downloading a video foo creates files foo.mp4 and .thumbnails/foo.jpg.
2. Dowloading foo again creates a copy named foo(1).mp4 and (1).jpg (note not .thumbnails/foo(1).jpg as one might expect).
3. foo(1).mp4 does not have a matching foo(1).jpg in the .thumbnails subfolder and thus it is shown in Archive with only the default thumbnail. So downloading it again is not going to help.
4. Deleting a video from Archiive deletes foo.mp4 but not .thumbnails/foo.jpg.

I have managed to reproduce your issue like this:
1. Download foo, creating foo.mp4 and .thumbnails/foo.jpg.
2. Delete foo, deleting foo.mp4 but leaving .thumbnails/foo.jpg behind.
3. Corrupt .thumbnails/foo.jpg (e.g. truncate it to zero bytes).
4. Download foo again: voila, no thumbnail in Archives!

Your use case may have been different but I would start by looking into your MyDocs/cuteTube/.thumbnails folder for leftover files.

chill | # 1252 | 2014-05-25, 06:38 | Report

My case may have been slightly different in that the first download only partially succeeded, and then I repeated it. I wasn't suspecting a bug so I wasn't paying attention. I can confirm that it does create (1). jpg (note the blank space, if it matters) and subsequent downloads create (2),(3) etc.

However, even with the correct jpg in place, cutetube will not show the thumbnail. Here is the listing as proof:

Removing (1) .jpg didn't help, either.

pichlo | # 1253 | 2014-05-25, 08:22 | Report

Are you sure the .jpg in .thumbnails is valid? Have you opened it in a picture viewer?

Obviously removing (1).jpg won't help. However removing Pigs_Can_Fly_Etc*.mp4 and .thumbnails/Pigs_Can_Fly_Etc*.jpg followed by a new download might. As might renaming (1).jpg to Pigs_Can_Fly_Etc.jpg and moving it to .thumbnails, overwriting the one already there.

chill | # 1254 | 2014-05-25, 19:15 | Report

Correct and correct! The original .jpg was corrupt (how did that happen?) and replacing it with the renamed (1). jpg solved the problem.

Ta76eem | # 1255 | 2014-05-26, 17:06 | Report

does it support Live Stream ?

marxian | # 1256 | 2014-05-28, 00:24 | Report

I wasn't aware of those bugs, so thanks for raising them. The transfer code has been replaced for the forthcoming update, so those problems should be fixed. Thumbnails are now also deleted when the video is deleted from the archive.

marxian | # 1257 | 2014-05-28, 00:26 | Report

Either the server returned invalid JPEG data or there was an error writing to the file. Because such errors are non-fatal (the thumbnail is downloaded after the video download is completed), the download is not marked as failed.

marxian | # 1258 | 2014-05-28, 00:28 | Report

Not at the moment. I received a request for it recently, so I'll be looking at the possibility of implementing it soon. The stumbiling block is that not all media players support live streams.

Estel | # 1259 | 2014-05-28, 07:39 | Report

Just a little request that buggered me for a while - is it absolutely necessary, that every new version of cuteTube (no matter if it's a "small" bugfix-release) overwrites configuration to default? It's surely not a showstopper and I can live with it, but I'm just wondering if it's done on purpose, or effect of some overlook.

Thank you for your awesome work on cuteTube,
/Estel

marxian | # 1260 | 2014-05-28, 13:43 | Report

The original reason for removing the old config file was to prevent the loading of incompatible values due to changes in the code (mostly related to the video formats). There is no reason to continue doing this now, so the config file will be left intact in the forthcoming update.