| Message |
Details |
You should use episode dividers both for the seasons and for the individual episodes.
That goes for both cast and crew. | Posted: Topic Replies: 9, Topic Views: 198 |
 |
| An overview should describe the story of the film(s). This just describes the physical contents of the package. I'm not sure if I would call this a tagline, but it's not an overview, in my opinion. | Posted: Topic Replies: 5, Topic Views: 297 |
|
TmdbInfo 2.7.1
Fixed a problem with the country list for "Where to watch". | Posted: Topic Replies: 32, Topic Views: 5041 |
|
Quoting WoJe:
Quote:
Incomplete: yes. But XSD can be used for code generation. Assumptions about me: false
The generated code wouldn’t be any more complete than the XSD, so you would have to modify it manually.
Since you don’t have a Profiler license, I assumed you were not familiar with the peculiarities of the Profiler export XML. Maybe I was mistaken. Anyway, good luck with your effort, whatever you need the XML for. | Posted: Topic Replies: 16, Topic Views: 808 |
|
Quoting WoJe:
Quote:
I use DVD Profiler XML built my own XSD now.
I don't think you appreciate how complex the Profiler XML is. Deconstructing a sample XML file into a schema will give you an uncomplete schema. It will almost certainly have minOccurs="0" for each node, and maxOccurs="unbounded" for nodes with child nodes. That would not reflect the true structure of a valid XML export.
An XML schema is meant for validation. It can only tell you if an XML document meets certain specifications. It doesn't tell you how to create an XML document that satisfies the requirements for a specific application.
I don't know how well mediadogg's BulkEdit plugin works in this regard, but it certainly seems like a much more likely way to succeed, and I know that mediadogg will help you in any way he can. But this does of course require that you buy a Profiler license, but that just $14.95 so if this is important for you, it's worth it. | Posted: Topic Replies: 16, Topic Views: 808 |
|
I'm pretty sure that Invelos never published an XML Schema. Some enterprising user may possibly have created one, but I have never seen one online.
Out of curiosity, why would you need one? | Posted: Topic Replies: 16, Topic Views: 808 |
|
Quoting scotthm:
Quote:
Regarding media companies, the rules say, "Enter in the following order:
Publisher (Content)Licensor (Home Video Rights)Distributor
If "Metro-Goldwyn-Mayer Studios" is the publisher then list them.
The rules then go on to say, "Some companies (using similar but different names) may serve more than one function. List such companies only once". This tells me that the "Licensed from Metro Goldwyn Mayer Studios" shouldn't be listed because that company is already listed as publisher.
Sounds right to me. | Posted: Topic Replies: 5, Topic Views: 493 |
|
TmdbInfo 2.7
- "Where to watch" added for movies and tv shows, showing which streaming services that have the title in question.
Four categories (if available); To buy, With Ads, With Subscription and Free.
- Setting for countries that can be selected in "Where to watch"
- Search for Company added.
- Company windows shows all Movies and TV Shows from the company.
- Links to movies/tv shows from Company listing.
- Links to company from movie/tv show listing.
- New tab Images
- For Movies and Tv Shows: Shows all available Posters, Backdrops and Logos
- For Movies and Tv Shows: Default poster image removed from Info tab.
- For Persons: Shows all available portraits.
- All images can be copied via the context menu (right mouse button).
- Several cosmetic fixes.
PS. Happy Easter, everyone!  | Posted: Topic Replies: 32, Topic Views: 5041 |
|
DJ Doena's CastCrewEdit and my TmdbInfo are quite different programs. CastCrewEdit has one main function - fetch cast and crew from IMDb for inclusion in a profile. TmdbInfo is more a way to browse TMDb (The Movie Database), but also lets the user fetch cast and crew.
So, if we just compare the fetching of cast and crew, CastCrewEdit is way more complex than TmdbInfo. But there are cons and pros to both programs. IMDb and TMDb have very different views on sharing their data. IMDb actively tries to make it hard for unauthorized copying of its data. TMDb on the other hand provides an API that let's others share its data. This means that programs that use TMDb need a lot less maintenance since the API doesn't change (or at least is kept backwards compatible), whereas the web pages that are the source at IMDb keeps changing.
When it comes to comparing the quality of their data, TMDb has an advantage in that it doesn't include fake data like IMDb seems to do in order to spot "stolen" data. But how do they compare in other regards? Neither seems to bother about keeping roles exactly as in the credits. Not sure which one is better or worse in that regard. As regards coverage, TMDb's greatest weakness is in crew data from older TV shows.
But back to the two programs. TmdbInfo does not handle "common name" (at least not in the current version). I have to confess that I'm not quite sure how CastCrewEdit handles them, but I know it does. When it comes to birth year, TmdbInfo handles them by comparing the birth year in TMDb's data with the online birth year list. If there is a match, then TmdbInfo keeps the birth year. As long as the birth year list is kept relatively up-to-date, this works fine. CastCrewEdit seems to have a much more complex system, but I'm not sure how the two programs compare in that regard.
So, which of the programs should you use? When it comes to cast and crew, you'll just have to chose whichever works better for you. If you are really using CastCrewEdit to it's fullest potential, then TmdbInfo probably isn't good enough (as long as Carsten can keep up with IMDb). Otherwise, why not at least give TmdbInfo a try and see what you think. And you can always use TmdbInfo for an interesting browsing experience through TMDb's data.
In closing, let me just say that I'm totally in awe of what Carsten has accomplished with CastCrewEdit. TmdbInfo is not an attempt to outdo CastCrewEdit. It just offers another source of data, and possibly a more stable program, for reasons stated above. Still, if there is anything you would like to see added to TmdbInfo, please let me know! | Posted: Topic Replies: 0, Topic Views: 250 |
|
TmdbInfo 2.6
Changes for Televison:
All cast and All crew have been added to show total number of episodes for each person.
First date aired has been added to episode listings.
Status info has been expanded. Note that vote info is from TMDb, not from IMDb.
Integration with CastCrewCheck 3.2 or later.
Cast and crew data can be directly transferred to CastCrewCheck. See help file for details. | Posted: Topic Replies: 32, Topic Views: 5041 |
|
CastCrewCheck 3.2
- Fixed a bug that sometimes showed birth year as (????) even though an actual birthyear was used.
- Removed integration with CastCrewEdit since I could not get it to work satisfactorily. Note though, that you can still copy/paste cast and crew from CastCrewEdit.
- Added integration with TmdbInfo (version 2.6 or later). See the help file for TmdbInfo for details. | Posted: Topic Replies: 1, Topic Views: 1497 |
|
Quoting rdodolak:
Quote:
The custom backup shows 9 main things to backup, one of which is for cover scans. 8/9 is 88.88% so it's possible it's based on that.
Ah, that makes sense. But it's still not very useful information. | Posted: Topic Replies: 9, Topic Views: 1298 |
|
| Two scans to each profile (assuming thumbnails are not backed up). Not sure how percentage of tasks could be 88% profiles. | Posted: Topic Replies: 9, Topic Views: 1298 |
|
I agree that reporting progress can be tricky. But backup isn't terribly tricky. You have a know number of profiles and a known number of cover scans. Empiric testing on my collection shows that approximately 1/3 of the time is spent backing up profiles and 2/3 of the time is spent backing up covers. I guess covers may take longer if you have a lot of covers that are locally scanned at more than 100 dpi. Still, it shouldn't be too hard to show an overall progress that is a bit more realistic than 88% for the profiles.
Estimating time of completion for this type of backup would be more complex, but Ken didn't try to do that. | Posted: Topic Replies: 9, Topic Views: 1298 |
|
I have noted that when I backup my collection (which we all do regularly, right?) the overall progress shows 88% when the profiles have been backed up and the backup of cover scans starts. I always wondered what algorithm Ken used that comes to that conclusion. 
That's not really important, but it does remind me of an old developer saying: "When you're 90% done, half the work remains." What that means is that you always underestimate the time it takes to test, correct, test again, etc.
And, if you're anything like me, there will usually be very late realizations during testing, such as "Oh, it would be better if it was done like this", "Ah, we need to be able to configure that", "Hm, that user interface looks a bit awkward. I should fix that", "Wait, I should add such-and-such feature!"
And then you need to document the stuff (fun, fun, fun  ). So when you have coded 90%, you think you're almost done, but you really aren't.
PS. "An old developer saying" means that the saying is old, not the developer. Or does it ...?  | Posted: Topic Replies: 9, Topic Views: 1298 |
|
Quoting agent_bitter:
Quote:
Every person that has 'credited as' is listed under director and not in the appropriate department.
I get that as well. For Star Trek: The Motion Picture I get 20 extra directors. | Posted: Topic Replies: 657, Topic Views: 63667 |
|
Quoting mreeder50:
Quote:
Quoting GSyren:
Quote:
Personally I tend to use DvdpScheduler for exporting, but that's a bit of overkill unless you also intend to use its scheduling and other functions.
I personally use DvdpScheduler for Backup, Export and Upload, but not for Repair Profile Database only because it does not give you the option to check full. I love it.
With DvdpScheduler version 3 you can select Basic or Full database repair. | Posted: Topic Replies: 5, Topic Views: 4592 |
|
Quoting Medieval Guy:
Quote:
The download page is still on 2.1.13.0...
But the program is actually 2.1.13.1. DJ just forgot to update the text on the download page. (Been there. Done that.  ) | Posted: Topic Replies: 657, Topic Views: 63667 |
|
QuickExport 1.1.0
Fixed so it works without HTTPJolie.
Changed so export through HTTPJolie is smoother.
Changed Window type so QuickExport is visible in the task bar. | Posted: Topic Replies: 5, Topic Views: 4592 |
|
TmdbInfo 2.5.1
Fixed a bug in formatting cast/crew names that contain quotation marks, when copying for DVD Profiler. | Posted: Topic Replies: 32, Topic Views: 5041 |
|
ProfilerQuery 5.0.10
Apparently the problem occurred because Microsoft Defender misidentified the program as a threat. Personally I use Avast, that's why I didn't see the problem.
I have recompiled for a newer version of .Net Framework, and now the problem seems to be gone.
However, if anyone has any problems, do please let me know!
P.S. If you don't have any problem with version 5.0.9 there is no reason to upgrade to 5.0.10. | Posted: Topic Replies: 315, Topic Views: 43516 |
|
| It's really frustrating when programs work for me, but not for others. I'm looking into this and hope to have a fixed version available soon. | Posted: Topic Replies: 315, Topic Views: 43516 |
|
Quoting mediadogg:
Quote:
Ummm ... unless it has been broken, BulkEdit can import everything. Hundreds of hours of work, it should be able to import Mark-style CSV and official DVD Profiler XML exports. But I haven't tested for awhile. And the CSV import has a mapping function to allow for non Profiler headers.
Yeah, but Mark's CSV Export doesn't include cast and crew. It does export Directors, but only full name and no birth year. Not sure how one would export full cast and crew to CSV. So I stand by my statement that it's iffy. | Posted: Topic Replies: 11, Topic Views: 1899 |
|
I agree with mediadogg. Exporting everything to CSV is iffy. Cast and crew especially, but also Overview and Other Features. Not ideal for transferring to another program. XML is better for that purpose, but I haven’t seen any program that can import everything.
There are some programs that import just a subset of data - like UPC and personal info - and fetches the rest from IMDb or other sources. They may import from CSV.
That said, I don’t think people ought to abandon DVD Profiler unless they have a very compelling reason! | Posted: Topic Replies: 11, Topic Views: 1899 |
|
It was just pointed out to me that Mark’s CsvExport can indeed be configured the same way that ProfilerQuery can. I had missed that when I tested it. So the advantage with ProfilerQuery isn’t that big when it comes to just export to CSV.
That said, ProfilerQuery is so much more than just exporting to CSV. It’s a very advanced query tool that can also produce simple text-only reports. And it offers statistics and other useful functions. So if you have ProfilerQuery there is no need for a separate CSV export program.
And, for what it’s worth, Mark has stopped developing for DvdProfiler, but I’m still here supporting and improving my programs. | Posted: Topic Replies: 11, Topic Views: 1899 |