Thanks for the update. I was able to reproduce the crash. I missed it before because it only happens on Windows. It was a bug in logging code and it will be fixed in next beta.
Great, thanks a lot!
The mpeg ts files that you have sent me do not have PMT. Our demuxer absolutely needs PMT (program management table) in order to parse mpeg ts files. Which usually isn't problem given that PMT is mandatory. I'm not sure why it is missing from those files, maybe it is supposed to be delivered out of band (i.e. from other file) or maybe there is exception in bluray specification.
OK, I just did some digging, too (TSDoctor and Transport Stream Packet Editor) and there is indeed something strange about these particular files. I am not sure how they could end up on a professionally mastered Blu-ray. Let's hope this is just a rare case.
Air Video Server HD does parse files in parallel, but we limit it on external drives and it shouldn't cause parse error (it might cause "file analysis took too long"). If the second files are same kind as the first, they shouldn't be parsed at all. The error, as explained above, is expected. What I don't understand is why the same files work for you on second try. That's very weird.
Since I couldn't recall something like this happening in the previous beta2 I did another test.
I did the following with beta3:
1) I deinstalled the Air Video HD client on the iDevice and Air Video HD server beta3 and restarted my PC and my iDevice
2) I reinstalled the Air Video HD client on the iDevice and Air Video HD server beta3
3) I directly changed to the directory with the mentioned files without doing anything else
4) Like already mentioned, when Air Video HD client scans the directory with the mentioned m2ts files _for the first time_ the "Failed to parse file." error happens (00000.m2ts or/and 00003.m2ts or/and 000004.m2ts give the error, all other files in the folder work 100% of the time)
5) Now I leave this directory and go up one level in the directory tree
6) I change the directory again to 3)
7) Now Air Video HD scans the m2ts files that previously gave the error "Failed to parse file." and does that without any problems whatsoever. The difference to 4) is that Air Video HD does only need to actively scan the files with the errors, the other files are already cached in the .db, so there is a lot less to do.
I re-did this whole procedure 2-3 times to be sure.
I then also scanned the m2ts files with Transport Stream Packet Editor and they don't give any errors (so I'm not sure if samples help).
I then removed beta3 completely (and rebooted) like mentioned in 1) and installed Air Video HD server beta2 and re-did my configuration. I also re-installed the Air Video HD client on the iDevices (download from iCloud).
Now, I started the beta2 server and the client on the iDevice, connected to the server and directly changed to the mentioned directory with the m2ts files. And, like I remembered, I could not trigger that problem with beta2. All the m2ts files in the folder will get scanned without problems. I also deleted thumbnails again, deleted the .db files in the server data directory and re-did this 2-3 times to be sure. It works flawlessly every time.
Is it possible that some of the changes you did with m2ts playback or rather thumbnail generation caused this? This seems to be a regression somewhere.