Print

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

[Dragyn]

I'm starting a new thread because the other one was mixing the 2 versions together.

Since I've been tagging my images for the last few hours, I think MC saved the database about 50 times. This is definately slowing me down (large database) and I really don't think it's necessary. Only thing I see is incase of a crash but 11 has rarely crashed on me and if it did, it wasn't because of any tagging.

I really think there needs to be an option for saving the database (on exit or something). Even a defined interval for saves would be a start. It seems to be doing it on every tag change.

I have more stuff. Again, I know my system isn't the greatest but you guys are excellent when it comes to coding so I know little things like this will become better in the end. At least that's how v10 went anyway.

[hit_ny]

The choice is either MC does it or the user does.

When one is in a tagging session. If there is a crash, all changes could be lost. What is the best interval to do a save ? Saving at the end is fine, but wont work if there was a crash. So one would have to close/re-open MC at regular intervals to be safe.

Or it could save at each step, in which case, given a crash, its easier to resume where one left of.

Offering the option is welcome. I would set it to save at each step. You might chose otherwise.

[Dragyn]

I see your point. I don't know what the best solution would be. All I know is that when I play songs, videos, tagging, etc, it always seems to be saving the database and it's starting to get old. In v10, this wasn't really a problem cause it would only take like 1 sec, but in v11, it takes a lot longer (5-10secs). Maybe it just needs to be fine tuned or it's saving too much at a time.

SA #2

When tagging a file and changing like 'Artist', MC starts the tag changing right away. In v10, I thought that it waited until you left the action window / selected files.

So what I'm seeing is this (for images anyway).

Change Artist.
MC gets ready for tag change. (frozen, 1-5secs)
MC starts tagging. (unfrozen)
Save Database (1-5secs)
Change Album
MC gets ready for tag change. (frozen, 1-5secs)
MC start tagging. (unfrozen)
Save Database (1-5secs)

So for me to change these 2 fields, I have to wait about 15secs before it's done. Now it doesn't matter if it's 1 file or 2000. The time is the same because once MC starts the tagging process, I'm able to do other things.

[darkAngelChild]

another idea would be that instead of making all changes to the files the second you make them, they could all be saved to a log file. the user then clicks a button and all the saved changes are made. if mc crashed after 3000 tag changes it wouldnt matter because they would all be in the log file when it was re-opened. the user then clicks a button or is prompted every so many changes or every so many minutes asking them if they want to apply all the changes they have made.
this would let you tag thousands of files instantly, when u had finished u could say 'now do all these changes' and mc just starts plodding away tagging hundreds or thousands of files while u are off having your dinner. this would also mean that no tag changes were ever lost as they would all be saved so could be applied between various sessions. in theory, using the same idea, u could save all changes made so that any individual change could be undone or all changes up to any given point could be undone similar to how photoshops history palette works.

[Dragyn]

SA #3

When doing a 'Rename from File Properties', MC takes a very long time.

It usually takes 1-3secs per file. This isn't actually renaming anything. This is before the rename/tag change process occurs. Only fields modified were 'Date Modified' and 'File name'.

After MC asked to keep the changes, then the rename process went very fast.

[JimH]

dragyn,
Are your changes done over a network?

[Dragyn]

no. it's a local drive(s). I'm 99% positive is has to do with the size of the library.

[TAFKAFEX]

...Change Artist.
MC gets ready for tag change. (frozen, 1-5secs)
MC starts tagging. (unfrozen)
Save Database (1-5secs)
Change Album
MC gets ready for tag change. (frozen, 1-5secs)
MC start tagging. (unfrozen)
Save Database (1-5secs)...

Disabled AlbumView (the only plug-in I have). It takes approx. 4 seconds after a tag change before I can make a next change.
Updated: I can make tag-changes one after another immediately, but they show on screen with a delay of approx. 4 seconds...

Both happens in my case tagging on an internal drive. (Moved) files (around 53'000) are on external drives, no network, no plugins.

Media Center Registered 11.0.52 -- C:\Programme\Media Center\

Microsoft Windows XP  Workstation 5.1 Service Pack 1 (Build 2600)
Intel Pentium 4 1982 MHz MMX / Memory: Total - 523 MB, Free - 256 MB

Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1514 (xpsp2.040109-1800) / Shell32.dll: 6.00.2800.1556 (xpsp2_gdr.040517-1325) / wnaspi32.dll: 4.60 (1021) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-1999 Adaptec, Inc. / Aspi32.sys: 4.60 (1021)

Ripping /   Drive F:   Mode:Normal  Type:Auto  Speed:Max
  Drive G:   Mode:Normal  Type:Auto  Speed:Max
  Digital playback: Yes /  Use YADB: Yes /  Get cover art: No /  Calc replay gain: Yes /  Copy volume: 32767
  Eject after ripping: Yes /  Play sound after ripping: No  

Burning /  Drive G: YAMAHA   CRW-F1E            Addr: 1:0:0  Speed:44  MaxSpeed:44  BurnProof:Yes
  Test mode: No /  Eject after writing: Yes /  Direct decoding: Yes /  Write CD-Text: Yes
  Use playback settings: No /  Normalization: None

[JimH]

Both happens in my case tagging on a local drive. (Moved) files (around 53'000) are on external drives, no network, no plugins.

Are they firewire drives?

[TAFKAFEX]

Yes. Firewired Maxtors. But tagging on an internal drive.

[Matt]

The bottleneck shouldn't ever be library saving anymore.

In this case, I think the slowdown is because MC rebuilds the panes after each change.  It can't use the cache since there was a change.

The alternative would be to let the panes get out-of-step until the next hard update. (F5)  Would that be better?

[Dragyn]

I noticed that Album Artist, Rating, Comment, Genre...is fast when it comes to tagging, almost instant.

Album, Artist, Track #, takes about 4 times as long to complete. Even changing track #s in a file already tagged takes the same amount of time.

[Berto]

I noticed that Album Artist, Rating, Comment, Genre...is fast when it comes to tagging, almost instant.

Album, Artist, Track #, takes about 4 times as long to complete. Even changing track #s in a file already tagged takes the same amount of time.

Exactly the same experience here. See my post on August 9 on topic 'MC slow'
Jim, Matt, can you combine both topics in the Forum.

[Berto]

I noticed that Album Artist, Rating, Comment, Genre...is fast when it comes to tagging, almost instant.

Album, Artist, Track #, takes about 4 times as long to complete. Even changing track #s in a file already tagged takes the same amount of time.

Exactly the same experience here. See my post on August 9 on topic 'MC slow'
Jim, Matt, can you combine both topics in the Forum.

Jim, Matt, did you remove the topic 'MC Slow'?
I was just writing a post and when trying to send it I got a message that there is no such topic in the Forum.

[JimH]

No.

[Berto]

No.

Where has it gone then? Ten minutes ago it was still there.

[JimH]

No.

Where has it gone then? Ten minutes ago it was still there.

Kansas

[Berto]

No.

Where has it gone then? Ten minutes ago it was still there.

Kansas

I don't like this at all.

[JimH]

Have you ever been there?

[Berto]

Have you ever been there?

Jim, no I have never been in Kansas. I bet you have never been in Noord-Brabant, I think you don't even know where that is.
But Jim, I think you owe me an explanation for removing the 'MC Slow' topic.
I just asked you to combine it with the topic 'Slow areas in MC v11'.
Any new ideas/suggestions concerning my problems with tagging?
 

[JimH]

I said that I didn't remove it.

Noord-Brabant? -- moy provincie.

[Berto]

I said that I didn't remove it.

Noord-Brabant? -- moy provincie.

Wow!! Two Dutch words. One correct (provincie), one wrong (moy). Score of 50%.
Jim, you did'nt answer my most important question.
 

[JimH]

Lekker?

I'm sorry, but I can't answer your questions about speed.  I did notice that graham posted in the other thread that he discovered his speed problem was related to the network configuration.

[Berto]

Lekker?

I'm sorry, but I can't answer your questions about speed.  I did notice that graham posted in the other thread that he discovered his speed problem was related to the network configuration.

Jim, I don't use MC through a network.
I still would like to know why the topic 'MC Slow' was removed from the Forum. If you did not do it, who did (or could have done it) and why?
By the way, 'lekker' is delicious.  

[JimH]

As in lekker vifen?

I don't know.

[Berto]

As in lekker vifen?

I don't know.

vifen?
that's not a Dutch word.

[JimH]

wifen?

Sorry I can't spell.  I've only heard it spoken.

[Berto]

wifen?

Sorry I can't spell.  I've only heard it spoken.

You mean 'Lekkere wijven'?
How old are you?

[TAFKAFEX]

I was in Kansas as another post a few months ago. Since then I'm called TafkaFex.

Back to our problem now.

The bottleneck shouldn't ever be library saving anymore.
In this case, I think the slowdown is because MC rebuilds the panes after each change.  It can't use the cache since there was a change.
The alternative would be to let the panes get out-of-step until the next hard update. (F5)  Would that be better?

Seems to be a good solution. Most of my tagging is done within a playlist or smartlist (recently imported), so the panes are not visible. So it's worth a try!

[JimH]

You mean 'Lekkere wijven'?
How old are you?

145

[Berto]

You mean 'Lekkere wijven'?
How old are you?

145

Then I think no 'lekker wijf" finds you a 'lekkere vent'.

[Berto]

I was in Kansas as another post a few months ago. Since then I'm called TafkaFex.

Back to our problem now.

The bottleneck shouldn't ever be library saving anymore.
In this case, I think the slowdown is because MC rebuilds the panes after each change.  It can't use the cache since there was a change.
The alternative would be to let the panes get out-of-step until the next hard update. (F5)  Would that be better?

Seems to be a good solution. Most of my tagging is done within a playlist or smartlist (recently imported), so the panes are not visible. So it's worth a try!

Jim, Matt, any chance of implementing Matts suggestion?

[Matt]

If you aren't looking at the panes when it's slow, the panes aren't the bottle-neck.

It may be the album analyzer if it's only slow when you edit certain fields.

Let us know if that's the case, and we'll see what we can do.

[JimH]

My wijf is 150.

[Berto]

If you aren't looking at the panes when it's slow, the panes aren't the bottle-neck.

It may be the album analyzer if it's only slow when you edit certain fields.

Let us know if that's the case, and we'll see what we can do.

As Dragyn and I said before:
I noticed that Album Artist, Rating, Comment, Genre...is fast when it comes to tagging, almost instant.

Album, Artist and Track # however take about 4 times as long to complete tag-changing. Even changing track # in a file already tagged takes the same amount of time.

[Berto]

My wijf is 150.

She must be very pleased with such a young husband.

[Dragyn]

If you aren't looking at the panes when it's slow, the panes aren't the bottle-neck.

It may be the album analyzer if it's only slow when you edit certain fields.

Let us know if that's the case, and we'll see what we can do.

Same as in a playlist (no panes)...I think. I really can't remember anything anymore.

[TAFKAFEX]

Dont' know anything about 'album analyzer', but another ex.:

Tagging my recently imported files without any pane visible, just changing track numbers. Choose the first file, change track numer, hit down to go to the next field (track number) and have to wait at least 3 or 5 seconds 'til I'm able to edit the following field. Takes forever to change a few #.

[Dragyn]

just had another idea as in to have a thumnail/analize option in the import dialog. that way instead of going through all the tracks (like create thumbnails), it will just go through what was imported.

[Dragyn]

bumpity bump bump

starting to get even slower as the database gets even bigger....for simple things, like inline editing, rating, image viewing, playing from explorer, etc.
other stuff like displaying all files or running complex smartlists etc I can understand.

I know I complain a lot. :love:

ps. maybe someone can do some house cleaning in this thread. thx

[sirshambling]

I've found v11 to be very slow in tagging Artist, Album, Genre from the first time I used it - posted this before.

Perceptible (?) lag while MC11 thinks about the change before I can tab to the next field - even if I'm tagging just 1 track.

Library size - around 10,000 items so quite small.

John.

[Polonio]

I also feel Mc tagging is slow on some situations... On my case, probably, the bottleneck is my own system...

I think updateing the library goes fast, really fast, but get slower while is saving changes on files... As I suggested in other thread, I think a posible solution could be keeping a field in the libery that informs MC about "unsaved" changes... On demand, on close, or periodically, MC could save the unsaved changes on files. This way the nothing will be lost (even if a chash occurs) and the feeling would be a faster application...

[Dragyn]

what I find when doing tag changes....

the actual tag/rename is very fast and I'm able to use MC. The slow part is right before that. Sometime MC takes a good 10secs before you can do anything.

Adding a lot of images to playing now and viewing them takes a lot longer than viewing a few. It must be doing something on each image change. sometimes there's a 3sec gap between images.

inline edit is very slow. use shift-tab on a field takes a long time to get over there. same with tabbing. it's like it's trying to refresh the list after each change even though tagging isn't done.