1708 - FLAC to OGG conversion fails

[GD3771730]

Hello,
I am using MM 4.1.3.1708 with a portable setup.
My library is made of FLAC files. I decided to use again a COWON J3 player in MSC mode because my iphone is out of order.
My laptop PC runs Windows 8.1.

As I formerly did, I have set sync rules that auto converts any file to OGG. When I sync the Cowon, the conversion fails after a few songs (around 30).
I tried to use the debug version to produce the logs you could expect but this version triggers a memory problem in NTDLL.DLL as soon as the conversion starts. SO I can not reproduce the problem with the debug version.

Using Tools->Convert Format to produce ogg files brings the same problems.

I had to reinstall 4.0.7.1511 to retrieve the ability to convert my library to ogg.

Thank you very much for your help.

Gil

[Peke]

I could not replicate, maybe it is problem with some of FLAC files. Can you open ticket and post one the affected files.

Use some cloud service if file is bigger than 4Mb

[GD3771730]

I have just done the following:
I have replaced the current Plugins\f_ogg.dll (345kB, 19 june 2014) with the one delivered with MM version 4.0.7.1511 (242kB, 12 nov. 2012).
Everything works well.

Gil

[Peke]

Ok, but I still can't replicate. please supply us with sample file that do not work in 4.1.4.1709

[GD3771730]

It seems that the problem comes with 24-bit 96kHz FLAC files.
MM produces the ogg file and aborts at the end letting XXXXXX files in the target folder.

The produced ogg file can be read by MM.

I post you such a file within minutes.

Gil

[GD3771730]

One sample file is here: http://dl.free.fr/vXwdKo0qA

Gil

[GD3771730]

Hello,

No more problem with version 4.1.4.1709.

Thank you very much!

[etnoy]

Hello!

I am using MMA pro to sync over wi-fi with Mediamonkey. I have a big music collection and have selected several thousand tracks to be synced to my Android device, a Galaxy S5 running CM12 (Lollipop) with a 128 GB sd card. At first, syncing went well and a few thousand tracks got synced to the phone.

However, now I have about 1200 tracks left to sync. Everytime I start the sync, it sync maybe 10-20 tracks, then stalls for 10 minutes and then stops, saying "X tracks failed to download" (or something to that effect) where X is a number around 20-40.

I have plenty of SD card space left, and the music is mostly FLAC and MP3. Tracks with a bitrate about 225 kbps are converted to ogg using auto-conversion rules.

I have tried everything. Why can't I sync my remaining tracks?

Thanks

[etnoy]

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.

[Lowlander]

Which version of MMA and MMW?

[etnoy]

I have tried MMW 4.1.6 and 4.1.6 prerelease, MMA 1.1.1.0412.

[etnoy]

The same issue happens with MMA beta 1.1.2.0415, too.

It seems that the sync process stalls, which results in the above exception thrown in catlog. Then it just sits there for a few minutes before finally exiting with an error. Each time I sync I get a few tracks over, but since the sync order is random you don't know which. Now I'm down to 1165 tracks left, but getting them all over would require hundreds of syncs.

It is possible that certain tracks are problematic. i don't see any specific pattern, but I do recognize certain artists from the "failed to download" error message again and again. I have tried deleting the MMW database and starting over on that end to no avail.

[Lowlander]

Send a debug log from the About screen in MMA right after the sync fails. You may want to post the logID here for reference.

[etnoy]

Send a debug log from the About screen in MMA right after the sync fails. You may want to post the logID here for reference.

Will do. I'm unable to do this before Friday, though.

[etnoy]

I found that MMA was still running and submitted a debug log even though I'm not at the desktop. Hopefully the log contains the relevant data even though the error occured 12 hours previously. Log ID KKRSN83EAO.