Origin of the "Plex Dance"

Has Plex ever considered allowing for exporting meta-data as well? Based on the last roundtables, one thing @elan mentioned was that people should be just editing in plex for issues found. In a perfect world this would be great, however, in the 5 years I have used Plex I have had to rebuild my libraries 5 or 6 times due to corruptions of random sorts (whether on me or Plex, that’s irrelevant and I don’t know why they corrupt). Sometimes Plex keeps these updates in the new data, sometimes it does not. My media is 100% to Plex standards in terms of naming and whatnot, I have .nfo files and everything as well, but to someone who doesn’t wouldn’t it be in Plex’s best interest to update the file names when indexing has issues? Drop an NFO/update one with better data? Maybe this doesn’t 100% pertain to the Plex dance, but if a Plex dance is needed, it sure as hell makes it a lot easier :slight_smile: for large content re-writing.

@Gdr56 said:
Your “noise” is definitely slanted to a must do project. Sensitivity to your cause is heard from the top of Himalayas all the way across the Globe bouncing off the Andes then slipping across the Pacific for a rebound.

LOL! Now who’s being overly dramatic? Every software company I’ve ever worked for has considered data destruction a serious issue. If you don’t agree, it only makes me laugh again at your earlier accusation that I don’t understand software.

Please don’t suggest you don’t feel a death roll for the “Dance”.

“Death roll?” What?

“My real priority/Xmas wish…”

…is a matter for your own thread. In this one, it’s off-topic.

If all you’ve got left to contribute are personal comments and straw man arguments, I think we’re done here.

@beckfield said:

@Gdr56 said:
Your “noise” is definitely slanted to a must do project. Sensitivity to your cause is heard from the top of Himalayas all the way across the Globe bouncing off the Andes then slipping across the Pacific for a rebound.

“My real priority/Xmas wish…”
…is a matter for your own thread. In this one, it’s off-topic.

If all you’ve got left to contribute are personal comments and straw man arguments, I think we’re done here.

Sensitivity…

I’m amused at your banter. Please explain personal comments? Did I call you names, I’m not crying here.

All I have addressed is that the “refresh” debate is not paramount, you have agreed. Crying from the tallest mountain will not
produce a “new” or as you put it “working” version of Refresh.

So off topic is opposing, my conclusion is it is really not necessary. Then again It would be nice but would not miss it much.

Cheers

Whatever, dude. We’re done.

A defeated discussion? Are done now, why? Do you feel your call for a Refresh revamp is worth it?

Yes it is?

But you won't fight for it, you have given up.

Obviously you have not worked at executive level, you must provide statistical proof, NUMBERS. Proof the issue exists and the causes you imply. Beckfield You must provide proof along with substantiated evidence that it is required.

My argument was pushing you to prove just that, but you just see the negative. Get a grip....

Glass and half full not half glass my friend. FIGHT...

You may find this odd but I was trying to trigger your passion

Merry Christmas and really you need to lighten up.

@Gdr56 said:
My argument was pushing you to prove just that, but you just see the negative. Get a grip…

Glass and half full not half glass my friend. FIGHT…

You may find this odd but I was trying to trigger your passion.

Yeah, not really. You haven’t been here long enough to see others post about using the “Dance” to fix issues we had with Refresh. Issues we STILL have, rather than fixing the bug. And now Ninjas and employees alike using this as a semi-official fix to a set of bugs that prevent what most new users expect the feature to do.

That’s OK… Some day you are going to understand… It’s obvious you haven’t gotten there yet, though… :frowning:

Hey Beck… One of these days, this is going to get revisited and we might get things working as expected. Probably about the time we get blacklisting, collections and user management tools.

@MikeG6.5 said:

@Gdr56 said:
My argument was pushing you to prove just that, but you just see the negative. Get a grip…

Glass and half full not half glass my friend. FIGHT…

You may find this odd but I was trying to trigger your passion.

Yeah, not really. You haven’t been here long enough to see others post about using the “Dance” to fix issues we had with Refresh. Issues we STILL have, rather than fixing the bug. And now Ninjas and employees alike using this as a semi-official fix to a set of bugs that prevent what most new users expect the feature to do.

That’s OK… Some day you are going to understand… It’s obvious you haven’t gotten there yet, though… :frowning:

Hey Beck… One of these days, this is going to get revisited and we might get things working as expected. Probably about the time we get blacklisting, collections and user management tools.

Mike that’s shallow, good luck with that misguided attitude i have witnessed through the forums.

As I said, positive aptitude will result in a good result. Your time explanation only destroys your forum credibility.

Then again the Forum criers need to focus on reality, Stop the hype

@Gdr56 said:
A defeated discussion? Are done now, why? Do you feel your call for a Refresh revamp is worth it?

Yes it is?

But you won’t fight for it, you have given up.

Obviously you have not worked at executive level, you must provide statistical proof, NUMBERS. Proof the issue exists and the causes you imply. Beckfield You must provide proof along with substantiated evidence that it is required.

My argument was pushing you to prove just that, but you just see the negative. Get a grip…

Glass and half full not half glass my friend. FIGHT…

You may find this odd but I was trying to trigger your passion

Merry Christmas and really you need to lighten up.

If you really believe all that, then you’ve overstepped your bounds in my opinion. I have stated my case clearly and professionally, and I’ve had civil discussions with Plex representatives about it. I feel no need to defend my position to the likes of you.

Personally, I think you’re full of crap, and this is just a juvenile attempt to excuse and rationalize your unsuccessful trolling.

4 Likes

@“MikeG6.5” said:
Hey Beck… One of these days, this is going to get revisited and we might get things working as expected. Probably about the time we get blacklisting, collections and user management tools.

I do think this issue is a bit more urgent than most, since data destruction is a factor. But yes, I am confident that Plex will continue to improve, and I hope my participation is seen as contributing to that.

@beckfield said:
I do think this issue is a bit more urgent than most, since data destruction is a factor, and the trolls are not. But yes, I am confident that Plex will continue to improve, and I hope my participation is seen as contributing to that.

Oh, trust me, I’m not arguing the value of fixing this. The biggest reason this bug hasn’t been fixed yet, is it’s so much easier to make the users hop through the hoops of the “Dance” then it is to actually find and fix the errant code. Too many other things are way more popular or not nearly as boring as fixing something that has a workaround already available.

It’s not elegant, nor is it really fixing a problem. but what it does do is put more work on the individual admins, and less on the developer’s plates. End result? We still have buggy code more than 2 years after the problem was first diagnosed, and a workaround that is now considered “official”.

We’ve seen this same attitude before. And I’m sure we’ll be seeing it again. It’s Plex’s M.O. after all…

@MikeG6.5 said:

Well, I don’t like going down the “They don’t care about me” stinkhole. I’ve probably made my share of comments like that, but it just makes me unhappy, and I really don’t think it applies anyway, and it certainly doesn’t do anything but alienate the people I’m trying to work with.

@beckfield said:
Whatever, dude. We’re done.

Really are you claiming i called you names. So read your posts, I can not believe you have denigrated to that level.

Your mission is now compromised by your posts
This is really a curler “Personally, I think you’re full of crap, and this is just a juvenile attempt to excuse and rationalize your unsuccessful trolling”. Ok where did that come from.
As I said you need to lighten up…

The term Plex Dance should not be used IMO because so many people know/believes what it does. And for that reason alone would cause headaches across the board “re-training” people. I always hated the terms “update” and “refresh”… But that’s what we have.

In all fairness, if the UI just had a button that said “Dance!”, I would totally press it.

Another new user bitten by the Plex Dance bug:

I’m not sure what that user’s issue ended up being, but you shouldn’t need to do the dance for local extras. I’ll have to try and recreate that issue to see what’s going on.

I deleted the Artist from the library and updated the whole Music Library again, and that seemed to work. Music and Artist videos showed up again. So I’ve been applying this solution (or workaround) when videos don’t show up using the refresh button.
I’m personally convinced this should be seen as a bug, as it’s only a workaround, so I’m with @beckfield on this. I shouldn’t need to delete an object from my library in order to refresh its content.

Just to weigh in, but I too believe that the refresh should rediscover changes in metadata. Any song/album/etc that is part of a music playlists that I do the “plex dance” for to correct a tag, will be removed from any playlist it is part of.

This is challenging and unintuitive as I may not even know which playlists I need to add the songs back to. I realize that I can change the tag in PMS, but I believe it’s proper to maintain the file tag and not the DB tag.

Thanks

How about “purge”. Sounds good. After “purge” completes then, update libraries.

The plex dance doesn’t need to be renamed. It is a workaround for a bug. Once the bug is fixed, the workaround will no longer be needed. It never should have been needed long enough to acquire the name it has now.