Version 1.3.0 is out and there are a lot of new features, including the so desired option to detect the set symbol from the card.
Quick changelog list
- Added feature to detect the set image for each card
- Added option to specify which set we're working on
- Added option to set Camera exposure settings to a fixed value (experimental)
- Added "Safe grab" mode
- Fixed freeze while sorting by price trend and get a "Card not found" message
- Fixed sorting by price when we get a Card Not Found
- Fixed rare case where the stop token card was ignored
Now, let's dig inside the main features for a better explanation.
Detect set
Previously, Magic Sorter had issues with reprints that have the same art. Consider for example Negate: the same art is used both on M20 and RIX. How can we understand what's the correct card? The best thing to do is to extract such info from the set logo. In this way the machine will exactly know which set the card belongs to and handle it accordingly (useful when you're sorting by set).
However, please note that this feature will increase recognition time, since two operations are needed (one for card art and one for set art). This is why you can decide to turn it on or off inside System settings. If you're not interested in detecting a set or you're working on a specific set (more on this later), you can safely turn off this feature.
Specify working set
Let's say that you already have your cards divided by set, so you know you're working on a specific set only. You can pass this information to the machine, so it will force the correct result. This is useful in the case of reprints with the same art: continuing with the previous Negate example, let's say you're working on M20 only and you specified such set in the Organize command.
If the recognition engine thinks that the card belongs to RIX, it will be automatically converted to M20, saving you some headaches.
Next steps
I'm currently working on implementing a plugin system within Magic Sorter engine, in this way power users can tweak the machine behavior without the need to perform changes to the core. Stay tuned for further info!