Apologies
To those of you who have posted comments here, I’m terribly sorry it has taken so long to respond to them. Responding to them here is a bit more of a hassle than simply replying to an email. As a result, Email support is very quick, sometimes even near instant. While comments here can take me a very long time to get to because, well, I can be lazy at times about certain things. If you need support, I highly recommend using the feedback/bug report item in iDentify’s help menu. Not only is it faster, but it will provide added information about how you have iDentify configured that can aid in the troubleshooting of your problem. I you use this method however, please make sure your preferences include a valid email address. Nothing is worse than spending time typing a reply to help someone only to have it bounce back because the address was fake.
Additionally, I need someone who can reliably cause a file to become unplayable after feeding it through identify. I believe I have a way that can recover the file and need to test it.
Loading ...
If you find it easier, I’m at clclementsj@gmail.com.
There is nothing I can do. Unless the files you are having the issue with are NOT from the FoV release group (as mentioned in the post immedately after this one); which has been releasing malformed files that they are lucky play at all. iDentify is not the only app rendering files unplayable from this release group (subler is as well). My two recommendations are to either avoid this release group, or convert them using handbrake first.