Posts by JanneK

Hi,

I faced same problem that RPI 3 with LE 12 doesn't connect to WIFI after reboot and when entering connection details manually after reboot I got "Invalid Password" cycle.

With LE 9 it was working without any problems.. System was few years unused since I managed to corrupt system with some update, so I made clean install LE12 to new SD card.

I did try to fix this with scripting and creating service to find out if system has IP if not force it, since Connaman doesn't like too much forking it didn't work.

Next I tried via Connman doing autostart script, simply Connman enable wifi, that didn't work as expected either, behavior was strange. I have two wifi network 2,5 and 5 it was connecting to 2,5 and IP was visible, but no internet connection.. Trying to connect manually lead yet again to "invalid password" cycle.. After 30 seconds later system reboot itself, not fully and both networks were IDLE without IP. After that entering connection details password was accepted.

Running wifi details RSSI level was -69 or -70 which should be ok for packet delivery. With another RPI I tested in same spot (LE 9 installed ) no issues on connecting. So my assumption is that it is not HW issue..

Problem is a bit annoying since when scheduling TV recording WIFI might be lost some point and system clock somehow resets and recording fails..

I could try this out with RPI 4 as well even though I believe that situation will be exactly the same.

My experience is exactly the same, my RPI3 B+ Works perfectly with 2 dual tuner USB Dvb-c (Hauppauge). Some update mixed up my setup completely, so that I decided to gain Rpi4 due USB 3 ports and more processing power to cut commercials.

Long story short, Rpi4 didn't work too well with live TV, stream was pixelized and buffering hit in constantly. I tried many ways of settings, without any luck.

Finally got fed up with struggling and re-installed libreelec to RPI3 which works perfectly.

I use Tvheadend as frontend as well as backend to transcode.

Thx Iridium.. we will give it a try once our nas arrives:)

Quote from andy5macht

I am using comskip for months now. working really fine!

one thing woud be super amazing because new Odroid N2 has enough power to do comskip and record simultanious.

i want to use comskip while recording. it already does work if i use comskip from another computer while recording the same video file.

i just want to use both on one device. is this possible? as pre-recording command does not work maybe because filename is not clear on "pre-record-state"? how could we get this to work?

Andy I think you can use it as pre recording. I think that we tested that on rpi3 in the very beginning. Name of the file is created immediately recording is triggered. Our notice was that recording get lot of error due it sucked all the cpu / memory from rpi.

We have no experience other boards than rpi so far so our result was on rpi3 capabilities.

Next board for another TV set will be rpi4 which is more powerful in case of cpu/memory than rpi3. Just when they fix ps cord problem. Best thing there is usb3 ports which makes file transfer to external HDD fast.

Quote from Iridium

This is what I use in the UK - and it seems to work for most things. I don't use post processing but rather by batch file when nothing is happening 2am (As it is quite I/O intesive.)

comskip --quiet --ini=/storage/comskip.ini -t <filename>

The -t stipulates the stream is .ts

Change name to comskip.ini

comskip.txt

Iridium we were looking also for that batch processing function. Due comskip in windows didn't cut perfectly.

Is that script processing all recordings on specific folder? And folder path you put on that <filename> section?

How do you trigger that schedule?

Sorry for lot of questions.

Quote from gaston

i will use it

Yes just go for it. It is rather useful tool. skipping commercials when watching is good experience.

For some series we cut commercials out and store permanently to HDD for later use. We use tool in windows TSdoctor for that, it is paid tool but really good. We didn't find good tool as open-source which supports teletext subtitles and EDL file support. It makes cutting more faster.

Avidemux was pretty good but lacking those capabilites.

Hi,

Yes we figure it out that it is part of installation when we found ini file from configuration. Reason why we go for installation via zip was that it is more faster. It took ages to complete for 45 minutes recording, after installing from zip it was few minutes. At least it what happen to our case.

Few more notes what are useful to others.

Logfiles sizes are increasing significantly when you record a lot, like in our case TV series. We run out of space from SD card with no time. Solution was for us to clone installation from 16 Gb to 255Gb. I suppose system cleans old Logfiles, but there are still plenty of extremely old. We need to check that as well some point of time. Recordings we store on external HDD.

Second note which might be helpful.

Some recordings were not passed to comskip at all. It took us long time to figure it out. For some reason when recording via rule based recording system added folder name for recording. Like e.g. Amazing Race, my son was debugging something else when that recording took place. When we checked debug log, we saw that comkip started after recording, but was trying to write in folder Race/program name.txt that failed due folder does not of course exist. Solution was to remove folder name from rule based recording and leaving it empty. As result when first recording was finished folder Amazing_Race was created and comskip files created. Comskip fails if you have whitespace or special characters either in filename or folder name, that's why you need to put those ticks in tvheadend backend filename options.

Hopefully this is useful to someone else too., struggling these kind of issues we did as well.

Hi,

We got it working sorry for delay.

Download comskip zip from tools.comskip-8.1.2.zip

Install to libreelec via zip installation.

Access to tvheadend configuration with web browser.

Go to settings.

Recoding settings.

Insert in post prosessing box following

comskip --ini=/storage/.kodi/userdata/addon_data/service.tvheadend42/comskip/comskip.ini %f

Tick boxes (if you don't see selections activate expert mode in settings)

Remove all unsafe characters from file name

Replace white spaces..

Use windows compatible file names

Save and reboot..

Then it should work

Ok so maybe I answer to my own question what we have found so far..

Looping seems to come from edl file format for some reason is not readable for player..

Format is like this

29.72 336.00 0

943.16 1249.60 0

1798.80 2137.60 0

2196.20 2197.56 0

but when changed edl as testing purposes is like this when it works

0:00:29.18 0:05:36.00 0

0:15:43.04 0:20:49.15 0

0:29:58.20 0:35:37.14 0

0:36:36.05 0:36:37.13 0

Needs some more studying when we have time to play around.. maybe it is some ini parameter which we missed, maybe something else.

Lets see.. but this would be great function in case of cutting out commercials from live tv if we get it working since cutting software is capable to read edl file..

Hi,

We installed Comskip tools to LE9 together with my son. We finally get it working, with many trial error type of approach since there were not too many instructions available.

Now with test file recorded from live tv we ran manually commercial detection and it seems to find those correctly (based on timestamps on vdr file) we checked from recording.

Issue is actually in playback of video. When entering first commercial video playback jumps back on beginning of video and this is endless loop. Player which is in default on LE behaves like this.

Anybody has similar experiences than us? Even better if someone has resolution to this. It would be nice to get this working since same approach would work nicely on realtime recording cutting commercials automatically when recording:)

Logfile

hastebin

Hi,

This is what df -H returns

##############################################

# LibreELEC #

# LibreELEC – Just enough OS for KODI #

##############################################

LibreELEC (official): 9.0.1 (RPi2.arm)

LibreELEC:~ # df -h

Filesystem Size Used Available Use% Mounted on

devtmpfs 368.4M 0 368.4M 0% /dev

/dev/mmcblk0p8 511.7M 138.4M 373.3M 27% /flash

/dev/mmcblk0p9 36.4G 279.0M 34.3G 1% /storage

/dev/loop0 125.5M 125.5M 0 100% /

tmpfs 373.9M 0 373.9M 0% /dev/shm

tmpfs 373.9M 9.4M 364.5M 3% /run

tmpfs 373.9M 0 373.9M 0% /sys/fs/cgroup

tmpfs 373.9M 2.6M 371.4M 1% /var

tmpfs 373.9M 0 373.9M 0% /tmp

/dev/mmcblk0p11 37.9G 781.1M 35.2G 2% /var/media/root-rb

p2

/dev/mmcblk0p10 78.8M 23.4M 55.3M 30% /var/media/boot-rb

p2

/dev/mmcblk0p7 40.3G 5.1G 33.2G 13% /var/media/root

/dev/sda1 7.2T 153.3G 6.6T 2% /var/media/Toshiba

/dev/sdb2 7.3T 330.1G 7.0T 4% /var/media/Seagate

LibreELEC:~ #

Well yeah setup is done with external psu leiche 19v 4,7A 90w.. That is connected to expansion board. From board rpi 5v is feeded to GPIO. Psu itself is brand new. I did measure with General electric measure tool that it gives to RPI 5 V.

Strange that it have been working nicely so far. Which is about month. Funny that copying files from NTFS drive to Ext4 No error occurs.. Even though I returned all the recordings back after formatting Ext4.

I am not sure if I have any other PSU which I can test. Since nowadays variations of psu plugs are too many.

Annoying issue to be honest

Sda refers to Ext4 drive then if I read those files correctly? Some sector error.. Even though that drive is also brand new

Edit:

Checking a bit further I ran disk check and Toshiba HDD seems to be good.

LibreELEC (official): 9.0.1 (RPi2.arm)

LibreELEC:~ # fsck.ext4 -ycv /dev/sda1

e2fsck 1.43.9 (8-Feb-2018)

sh: badblocks: not found

Toshiba: Updating bad block inode.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

Toshiba: ***** FILE SYSTEM WAS MODIFIED *****

93 inodes used (0.00%, out of 488382464)

1 non-contiguous file (1.1%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 41/44

71111100 blocks used (3.64%, out of 1953506304)

0 bad blocks

33 large files

52 regular files

32 directories

0 character device files

0 block device files

0 fifos

0 links

0 symbolic links (0 fast symbolic links)

0 sockets

------------

84 files

Edit 2:

Well I have spend some time on testing this.

1. Attach only NTFS drive to expansion board => copy recording from Ext4 to NTFS (failed)

2. Use another bridge from USB of expansion board to rpi =>

copy recording from Ext4 to NTFS (failed)

3. Connect bridge from USB of expansion board to rpi another USB port =>

copy recording from Ext4 to NTFS (failed)

4. Copy file from NTFS to Ext4 and same file from Ext4 to NTFS (failed)

For test 4 it is very strange that I can write the file on Ext4 without any error but I cannot write it back to NTFS without error.

Maybe I format Ext4 to NTFS and see if that works?

Edit 3:

I think I was able to solve the issue.

First I formated Ext4 disk back to NTFS. I run disk condition check on Win10. It was all good. I attached disk back to Rpi and copied some big files back and forth between disks. That worked fluently without any issues.

Second I ejected HDD and format with aomei disk tool to Ext4. Copied some files to Ext4 from NTFS. That worked fine, when trying to copy from Ext4 same files back to NTFS it failed again.

Third I ejected disk again and formatted disk with mini partition tool (which actually took 1,5 hour) to Ext4. I inserted disk back to Rpi. Rpi was not even able to find disk. When ejecting that again and checking disk in Win10 disk was in state unknown file format.

Fourth I downloaded tool DiskGenius checked disk and tool indicated also unknown disk format. I formatted HDD to Ext4 and inserted to Rpi. I copied few times rather big recordings (8Gb) back and forth between Ext4 and NTFS disks. Now it seems to work without errors... So far..

Only reason for us to have disk in Ext4 format is due TV service of tvheadend starts before NTFS is mounted. This causes recording information to dissapear

Hi,

problem still persist even when formatting HDD again in EXT4.

Logfile link hastebin

Dmesg link http://ix.io/1eyi

It is strange that earlier few weeks ago it worked file but now always error appears what ever method is used..

Hopefully it is something what can be fixed

Thx Iridium for answer.. I am now in phase of formatting HDD. I copied all I can(which was pain in the a**) and let's see if it is just the case of format. I highly doubt it was..

But if it persist I will run dmesg as advised👍🏻

That comskip we need to look since that is our aim with my son with this project. We are quite noobs with Linux. Mostly working on Win environment, but learning now Linux.

Hi,

My setup is following:

RPI3B+

X830 3,5 HDD expansion board

8 Tb Sata disk (Ext4) attached to expansion board with USB Bridge to rpi

8 Tb (Ntfs) usb hdd

Libreelec 9 as operating system

I store my live TV recordings to Ext4 HDD. I move files to Ntfs HDD to cut the commercials and then move it back to Ext4. Earlier that worked just fine. Now copy starts but ends up after some data copied in error.

I tried also via win10 pc with samba.. Same result after copying some time.

Just wondering if anyone else have faced similar and more better find resolution to this?

So now we were able to generate insert on tvheadend service start by using systemctl edit service.tveheadend42.service adding line

[Unit]

RequiresMountsFor=/mnt//Toshiba

We saved file in the editor and checked the contents that it was correctly saved

Then restarting kodi still the result is that THVHeadEnd starts before HDD is mounted and latest live tv recordings are not visible unless using in terminal systemctl restart service.tvheadend42 .service then those appear.

What we are missing here? Any Idea?

And still we are linux noob what comes to knowledge, but we try to learn new stuff:)

Oh yeah I hear you bro😁

Well main goal with VPN would be access to TV recordings, slide show doesn't sound too temptating..

Correct I am also a bit frustrated all those windows updates and then booting PC waiting bsd or some funny error. It is too time consuming to be honest. That's why we decided to go for rpi in first place and not Win media center.

LOL I noticed new issue on our media center on RPI. Recordings on live TV is not showing up on reboot of the system. Recordings are though there on external HDD. I have no faintest idea how to solve it. I suppose root cause is that HDD is mounted later than tvheadend starts and kodi cannot find recordings path due that reason. I looked tvh settings if start of that can be delayed before HDD is mounted, but haven't find that kind of settings.

So running from one issue to another lol

Yes setup having os in one place and data in anther instance is very secure..

We have this kind of setup on HW currently

X830 - All for Raspberry Pi, Arduino, Lattepanda, Orange Pi, Pine64 | by Geekworm

We purchased also cooling elements to RPI and Toshiba x300 was selected due low temperature generation. Within case the he is fan. Yesterday we put heavy constant load to RPI and monitored temperature cpu and case was constant 40 Celsius so not bad:)

Next for us is to have vnc on RPI to be enable watch live TV and movies from internet. I saw that there is also in RPI firewall ip tables available, but finding info what my son tried to search yesterday was quite limited.

BTW your setup sounds pretty robust build. Linux though is not so familiar to us, requires lot of reading, try and error

Hi Klojum,

Heh typically we are not doing anything experimental HW with my son:) Being first one with this kind of expansion board here is though cool.

Yes my board still boots from SD card. Reason why kept it like that, mainly HDD will serve as movie storage as well as for live tv TV recordings and music. If LE gets corrupted it is very simple to unplug USB Bridge connecting HDD and Rpi. Contents of HDD then stays untouched:)

You are correct with Noobs, it actually creates lot of weird structures on SD. When we first tried with LE, Raspbian, OSMC and Lakka, there were many storages splitted to small junks. LE, Raspbian and OSMC was creating more nice file structure. We are learning by doing, luckily reinstall is not so big deal and time consuming.

I followed your advice by trusting that Rpi can fluently attach any Disks, if those are in correct format. We spend yesterday whole day to see how we can eliminate causes by inspecting disk first. Everything seem to be as manufacturer site was indicating, while inspection in win10 pc. We were completely puzzled and almost giving up, then final try I downloaded disk tool which is Mini tool partition wizard (freeware). When I attached disk via USB Bridge to PC it showed that disk has MBR and two slots of unallocated space within it. We were trying to wipe the disk, but it was giving some error. Finally we thougt that there is noting to loose and we partitioned first unallocated space to drive D. While second part refused to get formatted or partioned. With tool we converted MBR section to GPT type and vola we were able to extend D drive to cover also unallocated part. We attached disk to RPI and it worked like charm.

Reason why This originally happen having 2 sections on disk unallocated having MBR I am not sure. Only thing we could think is that during initial installation of Noobs USB Bridge was attached to RPI. Maybe that messed up HDD.

By the way I can recommend by short experience expansion board and case shipping alongside. Nice and compact how we wanted it to look. Also it fulfilled criteria to have separate power button, so that system is easy to start:)