Yes, if I play it from the recordings window. There was a fix for a supposed break in edl handling in 17.1 but I don't comprehend why it makes a difference whether you start it from Files or from Recordings. I walked back to 4.2 for now. Maybe I'll revisit in a few weeks.
Posts by iophobia
-
-
Now I remember why I ditched comskip a while ago. It just won't do the autoskip from the recordings view. Only seems to work from files menu with both .edl/.txt cutfiles. If anybody knows a fix, that'd be much appreciated.
-
Short question: comskip seems to work as files are generated. I don't see ongoing/finished recordings in KODI anymore, though. (Kodi 17.3 on Win 10 + Kodi/SPMC 17.3 on Shield TV). Is there a new client version needed? B/c TVHClient on Android has no trouble listing these recordings.
-
Considering trsqr's OE implementation you might not need to specify the .ini path and don't need the quotation marks for the %f parameter:
QuoteOpen your TVheadend web interface and go to tab Configuration -> Recording. Make sure the following is configured:
- Remove all unsafe characters from filename: YES
- Replace whitespace in title with '-': YES
- Post-processor command: /storage/.kodi/addons/tools.comskip/bin/comskip %f
-
Thanks for including comskip! I used to repackage the old OE comskip binaries. Good to finally have a more recent one. Build 295 is running smoothly as far as I can tell after being installed over a 4.2 install. Will test comskip now. Tuning the ini is quite a pain, though.
-
Fun fact: with 1931 only one of my sticks works. But I guess that's hardware-related. So yeah, 1931 for the masses
-
Interesting. While not getting anything to start in 1928, TVH build 1891 showed at least "scan no data, failed". With the latest 1931 you just linked it suddenly started scanning and found all known services. This is true for imx6/Cubox-i on DVB-C in Germany of course only is what I can see. I have to check further whether the functionality is the same though.
Thanks so far, CvH
-
Maybe also imx6. Then I could conclude it in my tests this evening.
Gesendet von meinem A0001 mit Tapatalk
-
ah okay so its most likely that it is an Tvh problem - I post you an imx build later what maybe fix thisgreat to hear. until then, TVH 4.0.9 it is.
Edit: Any insights on the possible reasons yet?
-
The one for the Cubox-i is from the repository, the other for the RPi3 was either one of your builds (linked over at kodinerds) or from Milhouse. I don't recall now.
-
It is build 1928. What is ab6115?
BTW: The only thing flooding the TVH log is "mpegts: 362MHz in DVBC - add raw service"
-
So far nothing changed. It's weird as a 4.2 test build used to work on a RPi3 I own. But it shoud also with the Cubox-i.
-
in shell:
dmesg > /storage/logfiles/dmesg.txtthis would create an dmesg.txt at you log directory - pls upload
Btw the 292e, Edison and the TT 4400 are nearly the same sticks
seems like they use the same chipset which is weird if you look at the price difference. dmesg attached.
-
Code
[ INFO] linuxdvb: adapter added /dev/dvb/adapter1 [ INFO] linuxdvb: adapter 1 setting exlusive flag [ INFO] linuxdvb: adapter added /dev/dvb/adapter0 [ INFO] linuxdvb: adapter 0 setting exlusive flagSounds like that the dvb stick gets found - could you make an screenshot from the adapter configuration menu (in Tvh 4.2)?
Btw which card do you use ? could you pls upload also the /storage/logfiles/some.zip ?As I said, I don't have a logfiles folder in storage (at least none I can see in WinSCP). Screenshot attached.
Edit: Sticks are a 292e and an Edision Optimuss DVB-C/T/T2. Which work nicely again once I go back to TVH 4.0 (deactivating 4.2 of course before)
-
/storage/.kodi/userdata/addon_data/service.tvheadend42/service.logand the latest log from here /storage/logfiles/
I've attached the log file from kodi and the last service logs from TVH 4.0.9 and 4.1/2. Hopefully it helps.
Edit: Interestingly, I don't have a logfiles folder under storage. So I assumed you mean the general Kodi log.
-
Hey CvH, could you specify where to find the log? I'm guessing somewhere buried in /storage/.kodi/ ?
Edit: At least in .kodi/temp/kodi.log I didn't see anything. TVH writes to system log, right?
-
Don't know whether to put it here. Just installed TVH 4.2 on my Cubox-i4pro. Before I already deactivated the 4.0 version in addons. First everything seemed fine. Both my DVB-C sticks detected. However, although I did the whole procedure (Creating network, choosing predefined muxes, enabling tuner, linking network to tuner) the tuners won't scan for services even when forced. Also already did a restart of the Cubox-i to rule out any post-installation hiccups.
I'm running out of ideas. Glad if somebody could help.
Edit: Going back to 4.0 works without problems but of course I'd like to switch to 4.2 on the long run.