rausch101 Wrote:Didn't have anything to do with a full disk (200GB free). I thought the same thing when I saw the memory error. Problem solved though, so thanks.
Also, not sure if you still intended to send me a new version, but I didn't get an e-mail. Fine by me though since turning off image caching solved it. Just FYI.
Grrr... not sure why I can't send attachments to some people. I uploaded to my server instead:
http://www.cube3studios.com/EMM/EMMTest.zip
Note, due to changes in this version, a new flags folder (and accompaniments) is required. It's best to delete (or move) the current flags folder and replace with the one in the package. Also, studio tags are no longer supported in this version. You may experience some whackiness with the media flags unless you update the media info. But keep in mind, if you use a skin that supports studio tags instead of native media flagging, you will lose that functionality.
Also, this version should (hopefully) fix the problems people were experiencing with scrapers.
EDIT: If you decide to keep this version, you can delete mediainfo.dll from the bin folder as it is no longer needed.
rusten Wrote:Don't know if this applies to the issue I mentioned ... By default, I was under the impression I started with caching off; however, I've tested it with both options.
For the record, I too made it very clear in my post that I think Ember outshines all others -- not only from it's capabilities, but in it's very methodology and design paradigm. This has nothing to do with my point earlier, about not having to continue replying to the same questions / or the need for explicit questions to debug. And it certainly doesn't suggest that I feel the software is any less viable and to anyone whose read the forum, just about everyone here can appreciate the early stage of the app.
With that said, here are some quick suggestions (some of these may already be addressed) in the event you see benefit in them:
* Option for More verbose/finite logging (not only on-error). This is all the more important as you're seeing, where the app works perfectly for one person and doesn't for another. In this development stage, verbose logging will be well worth the upfront overhead to author.
Agreed.... might try to work this in as an option to the next release.
rusten Wrote:* Feature Request. Probably the most intuitive feature I've noticed missing, is the inability to multi-select (Cntrl-A / Shift-Click / Cntrl-Click) and then either proceed with those movies selected, or mark those movies selected. Because you're already using the "Mark" paradigm, might as well stick with it, but multi-select should be enabled at least for purposes of marking multiple rows at a time.
This is already on the feature request list. Might make it into the next release, but with limited functionality.
rusten Wrote:* Minor Unexpected Behavior. When switching between line-items in the Movie-Metadata list (to choose the specific movie when multiples exist), the process (which appears to be async) is not terminated when the user clicks to a different line item. To the untrained user, this causes a bit of confusion as it appears the results are being rendered for the newly selected item (when they are not).
It is canceled, but of course, you can't cancel loading of images while in mid process.... so it may appear that it's not.
rusten Wrote:* False Matches that are not a result of the data provider. I noticed some strange behavior with roughly 1-in-20 movies, where the data provider was returning "exact matches" or preferred matches, yet Ember was not choosing them. I only ran the first 200 movies in my collection (since I'm forced to explicitly right-click each, at this early stage) -- but some movies, such as "Baby Momma" "Better Off Dead" "Bookies" "Edward Scissorhands" had exact matches, and yet Ember used alternatives or marked them as unavailable.
Ember uses the first "popular match" as priority, as for 99% of the movies it is the best match. If there are not popular matches, it uses the first exact match.... if not exact matches it will use the first regular result in case of auto mode or will ask for the proper result in case of ask mode. Is this not the behavior you are seeing? If not, it may be a problem of your configuration, specifically the need for custom filters. Take "Baby Momma" for example... how does it appear, exactly, in the media list in Ember?
garvani Wrote:Have just updated 10 or so more tmdb pages with trailers.. and forced a rescan in emm, no joy.. i read on the api forum of tmdb that its refreshed every 4 hours? well i think thats what he was referring too. Thats not too bad.
Hmmm... must have updated his system finally then. lol If they still don't appear later, let me know what movies you added trailers for and I will check the api to see if they are available. If not, we know it's a delay with the API refreshing. If they are available in the API but not displaying in Ember, we'll know it's a problem in Ember.