2009-07-15, 23:26
mark007 Wrote:Very interesting. BUT, (with my limited knowledge, correct me if I am way off), but if you are downloading jpeg's from say imdb, I don't see any reason why your software should have to worry about quality at all. OK if you load a jpeg object into memory for viewing in the gui, and then save that jpeg object to disk, maybe you would need the quality setting, but if a user wants an exact copy, i would imagine you could change the behaivour to just dump exactly what was downloaded from the website as a file... just like a wget, instead of writing that image / gui object to disk.
Put another way, downloading a jpeg from say google images, to disk, I would just save the file directly to disk, not open it in an image editor after saving, to resave with a certain quality value.
I hope you understand what I am saying here..... does what I say make sense. Can you dump exactly what you download, straight to disk as a 1:1 copy, removing the need for a quality setting at all, and we will have 1:1 copies of what was scraped.
Yes, but just for ease of programming, everything was passed through the encoder. I'll re-work some stuff to be able to disable it.
Cosmor Wrote:From V.730 have the German Mpaa Rating a error
and the Mediainfo.dll from V.718 works not correct
The DVD´s with VTS_01_1.VOB (no VIDEO_TS.VOB in the folder) have a Duration of Duration: 0h 0Mn
Dvd´s with VIDEO_TS.VOB have the Correct Duration
And the error would be Just saying something doesn't work doesn't help us to fix it. lol We need to know the "whats, whens, whys, and hows".
mark007 Wrote:Ah cool. Maybe quality settings could be greyed out in the GUI, if no resizing is specified? Would this make things clearer?
EDIT: Unfortunately with the latest version, I get the same error in the log file. Can you make it more verbose? You can see below when i try to reopen the movie and rescrape fanart, I get another error in the log, like the trouble some image isn't there at all or something.
Title: Error
Message: A generic error occurred in GDI+.
StackTrace: at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
at Ember_Media_Manager.Images.Save(String sPath, Int64 iQuality)
Date/Time: 14/07/2009 21:23:28
===========================================================================================
Title: Error
Message: Object reference not set to an instance of an object.
StackTrace: at System.Drawing.Bitmap..ctor(Image original)
at Ember_Media_Manager.dlgImgSelect.GetFanart()
Date/Time: 14/07/2009 21:23:52
===========================================================================================
Unfortunately, that's as verbose as it gets. Those are the complete output of the errors. That's one reason why it makes it so difficult to fix image related errors sometimes because it doesn't tell you exactly what the error is.
patkhoo Wrote:I agree.. If a user did not ask to resize the image, then it should be the exact raw file as downloaded from the net. The quality setting should only come into play if the user asked to resize all the fanart/posters etc..
Sizing != quality. What if I wanted the original size, but with reduced quality? Just having an option to disable the quality encoder will suffice I think.
cheeky Wrote:Quick bug report: Using one movie per directory, if the movie's folder name contains a comma, then the "Open containing folder" action on the left context menu thinks that the folder name is the substring proceeding the comma.
E.g. Folder name:
Animatrix, The (2003)
Error:
The path 'The (2003)' does not exist or is not a directory
Note that images, nfos and extrathumb dirs are all created ok. This open folder action must be using a different code path to get the folder location.
Ah, yes, good catch. Reworked to fix this and to also highlight the selected movie (handy if you have all your movies in one folder).
clock2113 Wrote:I mean some movies (like "Deuce Bigalow, Male Gigalo") were not showing up in EMM...
They should still show up if there's a valid movie in the folder. Is the extension for the video file in that folder listed in your valid extensions list? The comma problem only affected "open containing folder" because of the way the path was being sent to explorer (without quotes around it). Explorer assumed the part after the comma was a second path to process.