Page 3 of 3

Re: 1708 - FLAC to OGG conversion fails

Posted: Fri Sep 04, 2015 6:19 pm
by leithal
I am having a similar problem. When I convert FLAC files to OGG files it will seem to work just fine in MM, but when I check the directory where the OGG files are created, some will not have been done and others will have an associated .XXXXXX temporary file there as well. The OGG files that have an associated .XXXXXX file will not be found by my music player on my phone. I am using version 4.1.6.1736 which I believe is the latest.

Re: 1708 - FLAC to OGG conversion fails

Posted: Mon Sep 21, 2015 3:44 pm
by leithal
Can someone please respond and help with my issue?

Re: 1708 - FLAC to OGG conversion fails

Posted: Mon Sep 21, 2015 9:02 pm
by Peke
4.1.9.1759 is latest MMW version (in RC sytate currently).

If you see .XXXXXX filenames it means that MMW could not rename tracks to .OGG

LOG file should show why, so please open support ticket and create debug log as described in http://www.mediamonkey.com/forum/viewtopic.php?f=3&t=69

Re: Sync with MMA stalls and then stops

Posted: Fri Sep 25, 2015 2:58 pm
by rusty
fyi, we tried syncing 2500 tracks and auto-converting them to OGG, but couldn't replicate this bug using MM 4.1.9.

-Rusty

Re: Sync with MMA stalls and then stops

Posted: Fri Sep 25, 2015 4:31 pm
by Peke
Hi,
Than you all for report, I just finished Testing of MMW OGG sync which ended in 2960+ track converted and no issues.

There is a delay when doing Manual Sync but that worked like that from start and it is expected. I agree that there is space to improvements which are noted in our to do.

Re: Sync with MMA stalls and then stops

Posted: Thu Oct 01, 2015 7:16 am
by linda0012
etnoy wrote:It appears that logcat reports SocketTimeoutException with a long stacktrace ending at com.ventismedia.android.mediamonkey.a.a@c.run(Sourcefile:245). This error is thrown when the syncing finally stops. There is no issue with wi-fi as far as I can tell.
Yeah you are right it is not the problem with the wi fi connection it is looking like problem in the device.