2019 Holiday Exchange!
 
A New and Exciting Beginning
 
The End of an Era
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    All the bugs related to png chunks & changed set definitions have been fixed (well, I hope so!) in 7.0d.
    I know the exif analysis of the scan quality slow down the loading (if scan status are shown). I am working on optimizing performance.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    Damn, for a strange reason, the set definition on Scryfall changed and should be 2XM*[+border%3Aborderless]*. In the meantime, you can edit it manually in Options > Sets. Of course, it will be corrected in the coming release.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @AnIzzetMage : Thanks for your report. This is a slight error with png exif from the dll. I fixed the bug in 7.0c. Quality tracking is currently enabled for jpg, but disabled for png scans, as exif are not supported by this format. I am working on tagging the pngs with quality characteristics as for jpg with exif.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @ nickman55 : thanks for your report. Double-sided cards are a mess on the Gatherer. The way those are managed is not always the same, and is regulalrly changing. I fixed the bug in 7.0b.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    Version 7.0 is released. Note you will need to update to Microsoft .NET Framework 4.7.2. (if not already done).

    The scan extraction routines have been fully recoded due to a server migration at scryfall. It is now more robust.
    In addition, it is now possible to extract the quality of scans from Scryfall. The saved scans will now have exif data related to their quality in the "comment" exif zone. This would help to better manage scans between the ones with low quality and the ones with high quality, as it appears in the pictures in attachment. You need to activate the option 'show scan status' to get advantage of those new functionalities!

    Moreover, a new panel has been created to get magnified views of scans or to rotate them. Just click on the magnifying lens in the toolbar, or double click on the scan. You will get the full path in the window title, and some image characteristics in the dedicated group (size, dimensions, resolution...)

    Transparency of the Scryfall's pngs are now correctly managed.

    Many minor bugs have been fixed as well.

    Enjoy and feel free to report any bugs you may find. Stay safe.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @ezellohar81: Good news. It will be implemented in release 7.0 to appear.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @ezellohar81: I understand. You obtain what you described because I did not implement anything specific to the naming of the scan file. The file has the same name as if it was stored direcly, in the "super folder" MPS.
    However, I agree with you: the alternate mark could be removed... but only if there are not multiple card copies with same name in the same subset. The case of multiples copies of "Island" in the same subset must be handled sowehow. If for example Island5 and Island6 of MPS have to be renamed Island1 and Island2 in subfolder PSPS0*, it will be a mess because the alternate marks stored are 5 and 6 (according to the GEx table), not 1 and 2. As a consequence The alternate markers 1 and 2 which have been locally redefined have to be stored somehow in the table for GEx to be able to find the correct file when displaying the scan.

    I am not really keen on overloading the data management/data table for this, but I will do it.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @verdealex79 & @ezellohar81 : The imporvement you requested are available in the last release. If you find a bug or something, feel free to report and I will fix it asap.
    Posted in: Third Party Products
  • posted a message on The Vault v0.23c (Deck & Collection Assistant)
    It is just a warning. Release-promo management has changed on Scryfall, and IDs have been redefined. Normally, cards have been automatically modified accordingly. Nonetheless you are invited to check.
    I can also see that one card is missing in the new database (Knight of New Alara) because ... there is a bug in Gatherer Extractor (now fixed) ;-).
    Posted in: Third Party Products
  • posted a message on The Vault v0.23c (Deck & Collection Assistant)
    Fixed! Thanks for having reported.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @ verdealex79 : I will add the possibility to extract XLHQ pngs from the scryfall api in the next large release. Thanks for having reported it was missing.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @ezellohar81 : Following the example, if pics are stored in subfolders inside the FNM folder, would it be OK for you? The subfolders would be named F18, F17 etc. following the scryfall set codes, but without the scryfall set name. Let me know.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @Mikori Games : I will see how I can fix the transparency issues of corners... provided the sources have transparent corners. Or force corners to be transparent.

    @ezellohar81 : The basic idea of gathering lots of scryfall codes is to avoid to have multiple "similar" sets composed of a small number of cards which differ only from the year of issue. For example, as you mentioned, I created a set named Friday Night Magic which gathers FNM cards of all years. As a consequence, there are not direct ways to force the creation of dedicated folders for F18, F17 and so on when extracting scans of the FNM set.
    The only solution is to erase the FNM set in the 'promo set' option menu and record manually a set for F18, F17 etc. Cumbersome.
    Maybe I can add an option to force the creation of such folders if you are interested in. However it makes the scan management even more complex afterwards, because scans are no more systematically stored according to their set (here FNM), but potentially according to their scryfall source (F19, F18 etc.). Let me know.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @nickman55:
    1/ Yes the list will has to be updated for all future double-face cards ....... but I will do it for you Wink
    2/ You have to first extract main data of KHM and CKHM. Then launch a full extract. I know it is a bit messy but the showcase/promo/special are not easy to deal with. (See screenshot).
    This is the only way to get them in the correct set. If you proceed differently, promos will be attached to KHM and not CKHM for instance because those are also available on the gatherer as alternates.
    Posted in: Third Party Products
  • posted a message on MTG Gatherer Extractor v7.3b (Database & Pics Assistant)
    @user-18041209 : Exporting spoiler to MWS is only possible when all data of a given set have been extracted (see image below). If you extracted only the main data (card IDs and names), MWS export is disactivated because some mandatory information are missing (mana cost, card text etc.)
    Posted in: Third Party Products
  • To post a comment, please or register a new account.