Ik heb onlangs MCEBuddy bijgewerkt van 2.4.1 naar 2.4.9 (ik had Comskip donator 81.092, maar gebruik nu de ingebedde Comskip die standaard meekomt, 82.003). Ik merk dat al mijn “oude” EDL-bestanden UTF-8 gecodeerd zijn als ik ze open in Notepad++, maar dat alle “nieuwe” EDL-bestanden UTF-8-BOM gecodeerd zijn. Wanneer ik opnames in Kodi terugkijk, hebben de “UTF-8-BOM”-EDL’s een probleem waarbij de eerste waarde van de eerste regel wordt genegeerd, waardoor de video meteen naar het tijdstip van de tweede waarde springt. Bijvoorbeeld: “47.124 101.254 3” in de eerste regel van mijn EDL-bestand springt meteen naar 101,254 seconden in de opname. Kan iemand bevestigen dat de uitvoercodering is veranderd? Zo ja, is er een manier om UTF-8 als uitvoer te forceren? Bedankt.
That’s interesting. MCEBuddy does add a BOM while cleaning up EDL files.
Technically this would be a Kodi bug as UTF-8 files may include a BOM and Kodi should be able to process it.
I’ll open a ticket to see if we can skip adding the BOM to the UTF-8 file to patch around this.
With the next 2.4.10 BETA build it won’t include the BOM byte in the EDL file but you should report it to Kodi as the specifications allow for BOM bytes in UTF-8 files (it’s pretty standard)
Thanks for the quick response. Is adding a BOM new-ish to MCEBuddy? I have a friend who uses 2.4.7 and it sounds like his EDL files are straight UTF-8. Just curious. Also, it may be a specific PVR addon in Kodi with the issue, ServerWMC/pvr.wmc. In looking at their source, it appears that it expects 3 arguments on the first line, and perhaps the first bytes of the BOM-type file is interfering with that. I’ll post on Kodi PVR forums as well, but that may be a trickier fix to get implemented. From what I’ve read, BOM causes issues/confusion with lots of other apps, just wondering if it adds value to MCEBuddy. Thoughts?
It was automatically added while writing UTF-8 files when we upgraded some of the .NET libraries some time ago. I’ve disabled it as it doesn’t impact MCEBuddy either way currently. However in future if any of the supporting apps need it we may need to re-enable it so it’s better that Kodi fixes it anyways.
Cool, thanks for the explanation, and the fix. I’ve posted in one of the Kodi PVR forums about it. Let me know if you’d like me to test anything, I’d be happy to.
Just to follow up. I installed the 2.4.10 Beta from 3/13/19. So far, my EDL files are now UTF-8 and appear to play nicely again with Kodi. Thanks so much for the turnaround on this, I appreciate it.