Posts: 107
Joined: Dec 2014
Reputation:
3
kmarq
Senior Member
Posts: 107
So it seems to be an issue with the format of my edl files. I used yours and it works as expected. Mine are coming right from comskip so this is odd.
I seemingly can't get logging working. I turn on logging and go to the path shown on screen, but the log file isn't being updated. I deleted it, restarted kodi, and it hasn't recreated one. I'll have to try looking into that a bit more yet, but seems to be something on my side at least.
Posts: 215
Joined: Jul 2014
Reputation:
11
The Kodi log should be in %appdata%\kodi in windows and .kodi/temp in Linux I think.
Posts: 2
Joined: Feb 2019
Reputation:
0
I have been a long time WMC7 user and now am trying to get my new Shield setup and working well on Kodi. I'm using Kodi 18.1 and server 10.0.0.63 build 1255 and addon 2.4.4. All tv and playback functions work great. Thanks!
Comskip works great on my PC in WMC7, but I can't seem to get it to do anything in Kodi. So I'm not sure if comskip should now be working or if there is still a bug out there, or if it is just something I'm doing wrong. How do I activate (make it comskip) on a shield? Or what are my next steps.
Posts: 3,439
Joined: Aug 2012
Reputation:
91
I don't use comskip, but as far as I know it works. You just have to have the .edl file with the same name as the .wtv file and stored in the same folder.
Posts: 2
Joined: Feb 2019
Reputation:
0
Ok, found that the .edl files were in a different folder. And it sort of works. But it auto skips and then I cant even go back manually. Any way to make it a manual skip with a button press? Thanks for the quick reply by the way!
Posts: 3,439
Joined: Aug 2012
Reputation:
91
I don't know. But if there is it would be a feature of kodi, and not something I can control in the pvr addon.
Posts: 215
Joined: Jul 2014
Reputation:
11
Make sure you have edl_skip_field=3 in your comskip.ini. This sets it properly as a commercial break according to kodi. If you already have .edl files, you may edit by hand and replace the last digit with 3 so it looks like the following:
607.17 740.21 3
1416.53 1514.40 3
1942.17 2160.12 3
etc.
Hope that helps!
Posts: 81
Joined: Sep 2014
Reputation:
4
So I am now seeing the behavior kmarq mentioned earlier. Anytime I open a recording, it immediately jumps to the second time listed within the first line of my EDL file. For example: "47.124 101.254 3" in the first line of my EDL file skips straight to 101.254 seconds into the recording right away. I had recently updated my MCEBuddy from 2.4.1 to 2.4.9 (which in turn updated Comskip from 81.092 to 82.003) and I noticed this began to occur just after this upgrade. My "new" EDL files created with MCEBuddy 2.4.9/Comskip 82.003 are all showing up as UTF-8 BOM encoded when I open them in Notepad++. All "old" EDL files from previous install still work as expected and show up as "UTF-8" in Notepad++. I can also toggle the encoding in Notepad++ and the issue seems to follow the BOM encoded version of the EDL file. I've posted in comskip forum to see if anyone has any ideas, and may post in MCEBuddy as well. Can anyone else verify this?
Posts: 215
Joined: Jul 2014
Reputation:
11
2019-03-11, 23:43
(This post was last modified: 2019-03-11, 23:44 by sbthomas.)
Confirmed. I can reproduce by just changing the encoding on the EDL file in notepad++. I'm still on MCE 4.7 and comskip 0.81.092. All edl files are utf-8.
Posts: 3,439
Joined: Aug 2012
Reputation:
91
If there is no other way out, pvr.wmc could be changed to make it BOM friendly (at least I don't know why it couldn't...). Although we'll be back to wondering if the change would get into kodi.
Posts: 3,439
Joined: Aug 2012
Reputation:
91
Sounds good. Please save some of these edl files with bom, so we'd have something to work with.