WebTools-NG

Dev Community Apps & Creations
168

The field for that is named Audio Stream Display Title

And I’ll see what I can do here: [RFE] ET Audio Display title shorten · Issue #621 · WebTools-NG/WebTools-NG · GitHub so please review it, and see if I got it correct @fcapizzo

169

Using the same example I used for my original post, the first audio track for the movie lists the same information in the XML for both displayTitle and extendedDisplayTitle, which is English (DTS-HD MA 7.1). Plex is definitely constructing that information as the language of the audio track plus human readable information of the audio track details.

For the same movie I have a commentary track. On this track for displayTitle it lists English (AC3 Stereo), but for extendedDisplayTitle it displays Commentary with author Stephen Rebello (English AC3 Stereo), which is a combination of the Name field of the audio track from the metadata combined with language + human readable info for the track. Not sure if this is helpful, but wanted to provide additional information.

I checked out the issue, and certainly if you can truncate the info to remove the language name, then what should be left is correct. Looks good, thank you!

1 Like
170

And we have yet another release :wink:

As always, remember that this is 3rd. Party, and NOT plex

Version number has been increased, since we are proud to announce a new module named Download

From the change log:

V1.2.0 ( 20221203 )

In this release, all of our love is dedicated to our new module named download
For details, see Download Wiki entry
Currently only supports movies, but episodes and audio is on the roadmap

Note: In this version, the following is disabled:

  • Export to xlsx format (See #331)
  • Photo export

Changes:

Happy Plexing, and remember this is 3rd. Party, not Plex!
Get it here: WebTools-NG

And as always, we do welcome translators

2 Likes
171

Just came here to say thanks @dane22 for the inclusion of the Audio Stream Codec (Human) field. I just did an export, and now I can easily see which media is in TrueHD, DTS-HD MA, etc.

3 Likes
172

And we have yet another release :wink:

As always, remember that this is 3rd. Party, and NOT plex

From the change log:

V1.2.1 ( 20221206 )

Note: In this version, the following is disabled:

  • Export to xlsx format (See #331 )
  • Photo export

Changes:

2 Likes
173

Just d/l’d, thanks for the effort, looks good.
I was able to view Movies Library under “Download”, but unable to see/select my TV Shows Library.

174

Correct, since not avail yet :wink:

This first release of the Download module is for movies only

You can how ever follow progress here: [RFE] Download Module for shows · Issue #631 · WebTools-NG/WebTools-NG · GitHub

1 Like
175

Thanks, (I didn’t look too closely (or at all :slightly_smiling_face:) at the release notes)

1 Like
176

when exporting Posters, if you have multiple versions of a movie (“Editions”) the export will overwrite the poster with whichever edition comes last in the library, meaning that if you have 4 Editions of a movie and export Posters, you’ll only get a single poster exported (unless you manually export single items at a time from the library, which is beyond tedious).

Now that editions are officially supported and “Title (Year)” is no longer guaranteed to be unique, can the exporter be smart enough to append the edition to the title?

177

Heh, and you are 100% correct here :wink:

Added to the pile of work here:

178

any chance of adding “remove poster lock” to WebTools-NG?

as in the functionality asked for here:

179

Hello @dopefish3d

I’ve created this issue on GitHub: [RFE] Clear poster lock on a library for all items · Issue #673 · WebTools-NG/WebTools-NG · GitHub

Note though, that a valid workaround was mentioned in the thread, as well as I find the use case very low, so it’s sadly not a high priority, sorry

1 Like
180

Sorry for writing here, but I can’t seem to find where to post. I’m looking for how to install on Synology and/or Docker. I can’t seem to find anything. Again, sorry for posting here.

P.S. The tool is amazing!

1 Like
181

It’s a desktop app, so install it on your Windows PC, Mac book or Linux desktop

It’ll connect to your PMS like any other client

1 Like
182

I’m not sure where to post this, so I chose here since it refers to the version I think I tried. The program I downloaded and ran is ‘WebTools-NG-1.2.1.f962812.exe’. I assume this was the right thing to do. It seems to have installed the program.

Let me first explain how I got here. Lately, with more than 2000 movies, the ExportTools PlugIn has been dying once it’s almost done. I have to stop and restart Plex, and then ExportTools runs. It’s almost as if there’s a timer or something, and it just stops when the timer goes off. It does not help that PMS often insists on going through the movie metadata. It takes forever. Not knowing where the problem really was, I was looking for an update for ExportTools when I found this program. I finally tried it.

While I think I could be a good beta tester, it wants me to join Slack and other stuff I generally refuse to do, so that’s out.

I do have (what I think could be) useful feedback, and I don’t know where to put it. (Be nice.) Let me explain where I’m coming from. I use ExportTools to, well, export the database in XLSX format. So until that happens, I probably won’t do much with the NG version of ExportTools. (I link the XLSX export to MS-Access, and produce “beautiful” listings/reports of my content.) In the MS-Access reports I use a lot of the ExportTools fields (and call functions and produce strings based on them in the various SQL queries). So it’s important: if you want to replace ExportTools, at least be compatible. For example, I would put the titles close to the left so you don’t have to go searching for it. (Maybe custom levels would solve that. But I can’t produce them until I do some of the following work and commit to using NG.) And the selected audio is labeled “true” in NG but “1” in ExportTools. (I want my report to show the selected audio, not necessarily the first audio, so I used the '…Selected" field. Why make me change? And even if I and others could be convinced it’s a change for the better, please tell me what all the incompatible changes are. Another thing is the separator between fields (“Delimiter for multiple data in the same field”). This should allow the ExportTools value I use, namely, the 3-character " - ". This is very important for separating fields for, for example, when pulling the second sound field from a 4-sound-field movie. A single character, unless I change it perhaps to TAB, runs the risk of producing “odd” separations. (My VB code would actually check for that, so would probably reject a lot of what’s in my test export.)

I have been using Plex for years and ExportTools for years. I have been programming computers for decades. So I know a little (a lot) about ease-of-use and how much of a hardship incompatible changes can be. If you want any more advice from me, please tell me where and how I can deposit it. It wouldn’t be a real high priority for me until XLSX format is available. (Yes, I could conceivably load the CSV file in MS-Excel, and then export it as XLSX. A quick view suggests I would have to then analyze field names in the NG CSV and the ones ExportTools uses. I shouldn’t have to do that.)

Finally, for whatever reason, my matter-of-fact (but honest) posts are not popular (oftentimes not received well) on the Plex forum proper, so I hardly ever post there anymore. Along these lines, I infrequently update PMS and rarely update the client (because I’m used to, most of the time, being ignored). So I am using older versions of (at least) the client. If this matters for NG, “never mind.”

P.S. Try to remember values I placed in certain Fields. For example, most of the time I want to export Movies, but I have to fill it in. (Maybe there’s a feature I’m not using.) I do know I had to fill in my server name (top middle of screen in what looks like a Spinner but seems to function as a List Box) each time I load the program. Just remember it for me! And because I’m lazy, I’m going to see if I can use that token stuff to launch the GUI from the command line or shortcut (in Windows), the goal being to not have to manually enter my password.

183

Above is sadly no longer under development, since it’s a plugin

Yes, that’s sadly a problem with WebTools-NG currently not supporting it, but when said, Excel reads a CSV file just fine

So simply allow Excel to import it, and save as an xls file, and you should befine, or?

That’s a bummer by me, but sadly too late to change now, since if doing so, I would break it for everybody else

WebTools-NG is indeed the future, so I humbly ask you to adjust your post work to work with that, since the old ExportTools.bundle will sooner or later stop working

184

Thanks for your response.

I noticed ExportTools was (almost?) no longer supported when I went to look for an update to it; that is how I found NG.

I said essentially that in my message. However, when I looked at doing that, it would require making sure I cross-referenced the CSV and ExportTools column/field names. (I noticed there are some new columns that I had to write functions for in MS-Access, e.g., editing DTS-MA 5.1 from DCA, etc. (or whatever it is) in ExportTools. That’s something I could perhaps look forward to. I also use SQL to map all input fields to new names, weeding out the fields I don’t need/want. I might be able to use “Custom” to do that before any queries are done in MS-Access. I should perhaps add that I merge various tables from various sources. For example, there are Movies and what I call TV Movies in a TV Movies export. This isn’t by choice. Some made-for-TV movies are known as “movies” in their own right; some are not. I want them all in the reports. So I have Movies and TV Movies and two exports. (It’s actually more complicated than that.)) I also noticed that in the XLSX file, the columns “knew” what type of data they were, so all the dates appeared as dates, etc. This was not the case with the CSV file. I was using a newer version of MS-Excel, and it still didn’t know. Now, if you were to supply some VB code that (1) cross-referenced any new field names with (2) old ExportTools XLSX column names and (3) adjusted the data type of the column (in MS-Excel before I saved it as an XLSX file), I would use that until the XLSX file was available from NG. Keep in mind that when NG learns to support XLSX files for output, anything I do to work around the CSV-only situation would be a waste of my time.

I don’t have a problem with switching to NG from ExportTools, assuming (1) NG works as well as ExportTools does now and (2) there are limited changes I need to make. Of course it seems I will have to make changes, but I hope they are minimal. I see no benefit from changing field name (columns) or even changing the layout of the data in the fields. But since the separator of “-” is not really a unique-looking separator (but SPACE MINUS SPACE is – or at least “better”), when you add the ability to make the separator compatible with ExportTools, you can add a field that defines how “selected” looks, so I can switch it to “1” instead of the (new) default “true”. (I’m assuming the same underlying mechanism can be used for both. And if truth be told, I can convert from using “1” to using “true” or whatever these values are [I’ve been saying things from memory only]. I won’t likely bother until I see XLSX output or a converter as described above.)

It sounds like one of these days Plex is not going to support ExportTools, but you made it sound like the reason is it’s a plugin and not that it’s just no longer supported. (This suggests to me plugins will not work in some future PMS.) I guess I don’t care since I only use one plugin (ExportTools), and NG someday will replace it.

One final comment: I use Python to make global changes I won’t describe here to effect changes in the Plex database. I use a package called Python Plex API (or something like that). I sure hope THAT won’t become unusable. Along these lines, if there’s a document that describes the low-level, URL interface to PMS, I would love to see it. I’d probably write my own Plex API in Perl. I muddle through the Python code.

P.S. I figured out “select and click QUOTE” to get your comments in this message, but I don’t know how to make sure my original comments were included. That’s why they’re not there.

185

It’s in the settings

Please read the manual

See this Blog post from 2018

https://www.plex.tv/blog/subtitles-and-sunsets-big-improvements-little-housekeeping/

Since that is external, I would guess it would keep on working

186

I assume you’re referring to “Delimiter for multiple data in the same field” which I tried and it did not work. It only accepts one character, at least on my PC. Actually, I have multiple PCs. PSM is running on a Windows 7 Pro PC and I was experimenting with NG on a Windows 10 Pro PC.

I consider it an affront to be scolded to read the manual, implying I didn’t read it or at least I didn’t refer to the sections covering topics I have commented on. For the SPACE MINUS SPACE thing, I assumed “Delimiter for multiple data in the same field” was what I was looking for when I was inspecting the CSV file. So, yes, I probably did not look for that in the manual. If that’s not referring to [clarification: the separator chatacter(s) for] the “true/1” thing, however…

I say again: It would be nice if schema and URL command format were public knowledge. (Trying to figure it out from the Python Plex API is trying.) I would happily roll my own Perl interface to Plex to do exactly what I want when I want. Right now I use (1) the ExportTools plugin for reports and (2) the Python Plex API for bulk, or tedious, changes.

187

Correct

Everything WebTools-NG does, has been done by looking at the browser debug screen in the WebClient