jesica wrote:The new 3.1 release seems to be in beta for a long time.

It was released officially last Friday.

MediaMonkey could have 2 or more encoding threads and then place tracks in one queue to send them to MP3 portable player or other destination.
sonnerie portable gratuite

Btw, I don't really know what you expected in terms of auto-conversion and sync speed. As you must know, file conversion is a lengthy process no matter what program you're using...

Yes I know it is but I expected something a little faster. I just installed version 3.1 and it is converting/uploading to the iPod about 3 times as fast. So it will be finished in less than a day instead of > 3 days it was going to take. A big improvement - kudos to the developers.

wiz wrote:

nohitter151 wrote:This is already implemented in MM 3.1, currently in beta testing and available for download in the beta testing forum.

I just purchased MM Gold and am very disappointed in the sync speed. I have almost an 18,000 flac library and a dual core system and it is going to take days to sync to my iPod. The new 3.1 release seems to be in beta for a long time. Any time frame as to when it will be released?

Don

It is actually a release candidate now and will probably be released in less than a few weeks. You're free to use 3.1 at any time now, though...

Btw, I don't really know what you expected in terms of auto-conversion and sync speed. As you must know, file conversion is a lengthy process no matter what program you're using...

nohitter151 wrote:This is already implemented in MM 3.1, currently in beta testing and available for download in the beta testing forum.

I just purchased MM Gold and am very disappointed in the sync speed. I have almost an 18,000 flac library and a dual core system and it is going to take days to sync to my iPod. The new 3.1 release seems to be in beta for a long time. Any time frame as to when it will be released?

Don

tooscaredtotry wrote:Yes, except I'm unable to use it still because I cannot configure it using no skin.

I don't really understand what you have to configure. It uses all CPU cores by default.

Yes, except I'm unable to use it still because I cannot configure it using no skin.

This is already implemented in MM 3.1, currently in beta testing and available for download in the beta testing forum.

BUMP!!! Agreed!!

FLAC to MP3 for syncing my iPhone takes soooooooo long and I have a Core2Duo E8400. Only ~50% CPU usage the whole time! HOURS and HOURS to sync only 1200 songs

This feature will most likely appear in the upcoming MM 3.1.

Jiri

I'll just add that it's likely you can just call multiple instances of the encoders and the OS will sort out which core to put them on. So MM itself doesn't have to be necessarily multithreaded as long as it is aware of the extra cores enough to call extra encoder threads.

Multi-threaded encoding, and multi-core support in general, is a huge issue in MediaMonkey. Having 2 cores in my computer, I would love to have 2 encoders running side by side when syncing to my PAP. What would be even more ideal, is to be able to set the amount of encoding processes running at the same time, and then have that number divided evenly over the number of cores detected or that MediaMonkey is allowed to use (another setting that needs implementation, IMHO). Bump hugely.

Hi,
when running MM v3.0.3 on my system with Centrino Duo 2 MHz / 2 GB, the program takes all the capacity when updating the database. It is hard to run a second application ("small" or "big" ones will have the same boring problem).
Therefore it is also my opinion to have a Multicore support. I have absolutely no knowledge in writing programs, but is it possible to write a program in a way that the support is not fixed on 2 or 4 cores (a kind of "open end" code)? It seems to me that the development in the Multicore technology develops fast in the next years. What we have today as high-end in the consumer market with the Quadcores might be end of 2009 a 6- or 8core platform.

Well I was also thinking on scenarios like a harddrive that is already in use for other applications and possibly a slow harddrive like slow laptop drives. Also I don't know if it's as simple as using filesize or that more data flows between harddrive and MediaMonkey for this process.

I know for me that most of the time that I have a slow PC it's due to harddrive not due to CPU (single core) being to slow. This is due to slow laptop harddrive and lack of memory (thus using virtual memory extensively which is also on the harddrive). Add to that various applications that also like to use my harddrive I have the harddrive as the slowest part.

Move to a desktop with more memory (ie. less use of virtual memory) and a faster harddrive (SATA or even RAID) and the harddrive will be less of an issue, but still could be one if the CPU can process things fast (multi-threading).

Lowlander wrote:This should be the case for whatever feature of MediaMonkey. Although I wonder if the harddrive doesn't become the bottleneck.

Quick test using dBpoweramp for a 47.5MB flac file to 15MB mp3 v0 takes 27-28 seconds (28,27,27) with different source and destination drives.

So it only needs to read @ ~1.75MB/s per thread and write @ 0.5MB/s to keep up with the CPU. Easily done by most USB devices I'd think.