Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bodiebill]

Last week i upgraded from MC23 to MC24 for mac, and since then MC works really slow. For instance, searching in the top right box can last for several minutes. This also goes for other operations such as imports, retagging etc. Everything is very much slower in MC24 than it was in MC23.

I do have a large number of user defined / calculated fields.

The log has many error-like lines that I do not understand (see below)

Any advice? Like this, I will have to go back to MC23. Is this a known problem for MC24, and will this be improved in a future version?

From log:
1878665: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878665: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878706: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878707: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878747: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878747: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878789: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878789: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878829: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878830: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878871: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878871: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878912: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878913: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878954: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878954: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
1878995: 164519936: Sharing Plugins: VSocketReader::Bind: Socket bind failed: Address already in use (48) Socket: 34 Size: 16 Address: 192.168.1.10 Port: 1900
1878996: 164519936: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes

[JimH]

I don't know what the vsocketreader is.  I went to Google and found this:

https://yabb.jriver.com/interact/index.php/topic,79185.0/nowap.html

I'll look some more, but it could be software you have installed.

[JimH]

I can't find anything, but my guess is that something with networking is broken.   Consider uninstalling any software you're not using or have recently installed.

[JimH]

Hendrik said this:

"The message just means that port 1900 is already in use, which is not that uncommon since MC is not the only application to want to implement SSDP."

Any other DLNA applications installed?  You could look up SSDP to get more information about it.

Turning off Media Network would be an interesting test.

[bodiebill]

Thanks for the recommendations. I deactivated Media Network but that had no noticeable effect.
For instance, when I search for an artist name, I do not get the usual suggestions dropdown list, but just a rotating beach ball for about 3 minutes, or sometimes MC24 even hangs.

So I went back to MC23 and there the search does show the suggestions dropdown list and gives a result in one or two seconds. Also the MC23 log does not contain the VSocketReader lines.

So I experience this as a difference between MC23 and MC24 -- all other things being the same -- and I now regret upgrading :-|
Any advice how to solve it for MC24 remains welcome of course!

[bob]

Can you try the latest build?
24.0.45

[bodiebill]

Thanks. I just installed 24.0.45, but the problem remains: when I do a search, MC24 freezes, and I have to force it to quit.
Can the problem be related to my many custom calculated fields?

[blgentry]

When I upgraded from 22 to 23 (or maybe 21 to 22?) one of my custom fields went all wonky.  It didn't cause any slowdowns, but it's values were wrong.

I copied the field definition, erased the field, and recreated it.  Boom!  Problem solved.  It started working again.

You could create an empty library and import some of your media files as a test.

Or you could go nuts and erase and recreate each field as I described above.  Since you have "many" custom fields, this might be a sucky time consuming solution.  Sorry I don't have any more insight for you.

Good luck.

Brian.

[bodiebill]

Thanks, I will try when I find the time (using MC23 in the meantime).

[bodiebill]

Yesterday I spent the day simplifying my library in MC23 by removing most of my custom calculated fields. I then backup-ed the resulting library and restored it into MC24. Alas, MC24 is still unusable: every simple navigation results in a beach ball that turns endlessly, and I have to force the program to quit. I don't know what to do next. Back to MC23.
Any ideas?

[JimH]

What happens if you start with a new library and import your files again?

[blgentry]

You might also consider exporting your MC23 library as MPL.  File > Export Playlist .  Tell it do do everything (include all) and export all fields.  Then you can import that into MC24 (File > Import).

It's not the same as File > Library > Restore library .  There's some possibility that something in your MC23 library is confusing MC24 making it behave strangely.  This "import" process should get all of the metadata, but it will miss your settings, playlists, and custom fields (I think).

I'm not saying this is *the* solution to your problem.  It's just something else to try.  With a fresh library as Jim suggested.

Good luck to you.

Brian.

[bodiebill]

I cannot pin-point the reason for this strange behaviour but by now I know that it has to do with the expressions (calculations) in my Library Views.

Here is an example of the type of a formula I used to generate the custom tag .Album based my file and folder naming convention:
If(IsEqual([.GenreHL],Classical),Regex(FileFolder(),/#(.+)_(.+)_(.*)#/,-1)[R1]_[R2]_[R3],If(Isempty(Regex(FileFolder(),/#(.+) - (.+)#/,-1)[R2]),FileFolder(),Regex(FileFolder(),/#(.+) - (.+)#/,-1)[R1]))

Due to the size of my library (almost 5TB), doing viewing and searching with such on-the-fly calculations appeared to be too much for the program and/or my system (iMac + NAS).

So I started from scratch as suggested, and minimised the on-the-fly calculations. The heavy workload is now when I populate the fields with values rather than when viewing and searching. The latter is now done based on fixed rather than calculated field values and everything is much faster now!

It is still a bit strange to me that MC23 was much faster with the same complex library than MC24, but I am happy now to work in MC24 in the new manner.

Thanks for your suggestions, which pointed me in the right direction!
 

[Scobie]

Nice result Three Seven.

[blgentry]

Bodiebill:  You should use those same expressions *once* by cutting and pasting them into the fields you want.  This will do the calculation, across all of the songs/albums you have selected, and populate those values statically.

That way you get the info you want, based on your rules, but MC won't have to recalculate them every time.

I'm glad you were able to make some progress on this. 

Brian.

[bodiebill]

Thanks bigentry, that is exactly what I am doing now and meant to describe by "The heavy workload is now when I populate the fields with values rather than when viewing and searching. The latter is now done based on fixed rather than calculated field values..."
I initially hoped to do this automatically rather than manually (once in a while I need to repeat this when the library has grown), but that seems too much to ask for :-)

[bodiebill]

sorry, double post