INTERACT FORUM

More => Old Versions => Media Center 12 (Development Ended) => Topic started by: JetBlack on July 14, 2008, 11:39:23 pm

Title: Why does MC 12 hold while tagging?
Post by: JetBlack on July 14, 2008, 11:39:23 pm
When I am tagging music MC takes 5 to 7 seconds to take the information and then go to the next field. Why does it take so long?
Title: Re: Why does MC 12 hold while tagging?
Post by: JimH on July 15, 2008, 06:25:23 am
Virus checker?

Slow drive?
Title: Re: Why does MC 12 hold while tagging?
Post by: AoXoMoXoA on July 15, 2008, 07:49:35 am
Try using Media Jukebox 12, I expect you will find as I did that it will tag without the delay, but do not ask me why.
Title: Re: Why does MC 12 hold while tagging?
Post by: Matt on July 15, 2008, 11:38:56 am
Quote from: JetBlack on July 14, 2008, 11:39:23 pm
When I am tagging music MC takes 5 to 7 seconds to take the information and then go to the next field. Why does it take so long?

It shouldn't.

Please give more details about:


Note that Media Jukebox and Media Center are the same code base, so there will not be a performance difference.
Title: Re: Why does MC 12 hold while tagging?
Post by: rjm on July 15, 2008, 12:46:29 pm
I have noticed a similar delay when I have more than one "complex" view open in tabs. The solution is to have only one complex view open at a time. In my case I temporarily set the other tabs to a "simple" view like Playing Now and the delay goes away.
Title: Re: Why does MC 12 hold while tagging?
Post by: marko on July 15, 2008, 12:50:28 pm
I see a 1 - 2 second tagging lag here if I have several tabs open and there is a pane selection in one of the non-visible tabs. The lag is present even on tags that are held in the database only.

Example:
Playing Now view (plus another couple of open tabs, holding pane selections)
30k file library of all media types, mostly audio and image files.
Apply a rating by clicking in the rating column...

MC lags for a second or two.

-marko.
Title: Re: Why does MC 12 hold while tagging?
Post by: hit_ny on July 15, 2008, 01:04:24 pm
Quote from: rjm on July 15, 2008, 12:46:29 pm
I have noticed a similar delay when I have more than one "complex" view open in tabs.

Are the views parameters dependant on the tags being modified ?

So modify tag, refresh, view updates or

...independent.
Title: Re: Why does MC 12 hold while tagging?
Post by: AoXoMoXoA on July 15, 2008, 01:14:04 pm
Quote from: rjm on July 15, 2008, 12:46:29 pm
I have noticed a similar delay when I have more than one "complex" view open in tabs. The solution is to have only one complex view open at a time. In my case I temporarily set the other tabs to a "simple" view like Playing Now and the delay goes away.

Just tested and this is definately why I am seeing a difference between MC and MJ in tagging speed.

Quote from: marko on July 15, 2008, 12:50:28 pm
The lag is present even on tags that are held in the database only.

same here
Title: Re: Why does MC 12 hold while tagging?
Post by: rjm on July 15, 2008, 09:49:24 pm
I'm pretty certain the delay is caused by an auto refresh that occurs after each field edit. The delay is the same length of time as a manual F5 refresh. Perhaps auto-refresh could be disabled for tabs that are not displayed?
Title: Re: Why does MC 12 hold while tagging?
Post by: JetBlack on July 15, 2008, 10:23:02 pm
I had too many tabs open. I closed all the tabs and now it is pretty fast.

Thanks
Title: Re: Why does MC 12 hold while tagging?
Post by: glynor on July 17, 2008, 11:03:53 pm
Hmmm... It seems like it would be better for MC to release the "hidden tab" resources and rebuild them on the fly when switching tabs.  With "standard split views" you need to have the changes update all of the panes on the fly (as it were -- tag changes force a refresh on all open views) because each different view can be active at once.

However, with tabs, it leads you to open a bunch of them and you only ever see one at a time.  A short "building view" delay when switching tabs, which would only ever be as long as the F5 refresh lag, is acceptable.  Slowing the entire application down for 5-7 seconds though (based on the number of tabs and panes showing) doesn't seem like it makes as much sense.

Is this not how it is?