Have your USB source on the left showing the files and enter the Profile directory showing its files on the right.
Highlight advancedsettings.xml and hit the c.
Martin
Posts by emveepee
-
-
If you insert your USB drive you should be able to go to Settings -> File Manager Add source and then on the right side select Profile Directory for your target and copy it.
Martin
-
the new addons get build tonight and pushed tomorrow
Do you know when these will be updated online? 10.80.6 is still May 6. I wanted to get netcore 6.0.5 so that arm will work on this test build. 6.0.6 is out now too. I can do it manually but I'd rather do it using the package you created for NextPVR
Martin
-
Not sure I understand the question, I've told you I am running LE on the RPi3. That dotnet is simply because the NextPVR server is a netcore app. I could run it in a docker and hide all that, but I figure running the service natively would be more efficient, the RPi3 has only 1GB and the Docker is on SD card. Jellyfin and Emby native would look like that too.
What I was getting at is the RPi3 kodi.bin is running 58% CPU, yours is running 13%. My test RPi3 doesn't get close to that even at ideal.
-
I don't know if it is much comparison, look at the Kodi difference mine ideals much higher and I don't think it is because of v18. You might use emmc too. I'll try CE on a vim3l or n2 and see.
Martin
-
That
NextPVR was running on LE 10.0.2 RPi3 and it is all direct play and Kodi was playing fine as where the other On the Kodi summary page it was under 100% by quite a bit so 4 streams were not "impossible" although the OSD from the summary definitely bumped out the CPU. I don't now the load with TVHeadend and 4 HDHR network streams.
Thanks for htop here is with Live TV with 2 clients plus Kodi. Again with 3 recordings and Kodi live TV it is even lowered All of this is buffered to an SD card so I would expect a real setup would be better.
-
I just set up NextPVR for a simple test on a RPi3 with the LE service addon with two HDHR tuners and was able to play one channel in Kodi and stream 3 other 1080i channels to other clients. I think caching to the the SD card would be my big bottleneck here two.
From top
2491 root 20 0 752420 103188 33204 S 222.4 10.9 21:05.28 dotnet
1929 root 20 0 641076 93252 20084 D 51.0 9.9 39:23.09 kodi.bin
LE doesn't have htop but the 224% CPU seems about right for these slower SoC's. Recording 3 streams and watching one is much less CPU intensive which is probably a better use case. TVHeadend on the RPi3 might be a little lighter, though if this troubles you but I'd probably go with a bigger box myself for this kind of use.
Martin
-
Are you running NextPVR in Docker or via CvH's addon from the NextPVR forum? The addon works great IMO.
Since you mentioned zap2epg, I assume you are in US or Canada. NextPVR doesn't support ATSC OTA EPG on Linux and even if it did it the data is awful many times 8-12 hours of data or even no data at all. In addition to the SD-JSON (which is actually worth paying a cup of coffee a month if you are serious about PVR) you can always use XMLTV from zap2epg. If you have any questions post on the NextPVR forum.
Martin
-
emveepee I did some test boots from an SD card yesterday using the image in my web-share (5.17-rc4 and u-boot 2022.01) and it worked fine from a boot perspective. I'd recommend getting an emmc module; they're faster and more reliable than SD cards.
Thanks and I agree, but I made a mistake only ordering one when I originally got my N2 and while the drives themselves are priced ok it is hard to justify paying 3x the indicated prices for extra shipping taxes and duties for a postage stamp sized item just to test. These same cards themselves work in my RPi's and VIMs so it is my SD reader that appears faulty so put me on the list for wanting tftp support.
-
The odroid-n2 image includes mainline u-boot which uses FDTDIR in extlinux.conf (not FDT and dtb name or uEnv.ini) to auto-determine the correct dtb to use from hardware data read at boot time. I haven't tested a clean install from SD card that recently but the image should boot both SD and eMMC with no config required. NB: You need the SPI boot switch on the N2 set to the right. If set to left, petitboot will be active and it does not understand exlinux boot configs and the device will not boot. The latest image in my testing share is running fine on an N2+ (see http://ix.io/3Ps4) although the emmc module it's booting from might have an older u-boot installed.
Ok thanks my SD card reader on my N2 must be going, I can't get reliable boots off any SD media I have, and console showing it trying to boot via tftp.
-
I tried to run the nightly for the N2 from SD card, but nothing happpens. I don't see a uEnv.ini file to edit either. I build the image from source and tried that too but same thing.
Does this image only run from emmc? If is there a command way of building it to run from SD?
Martin
-
In general you guys appear to be pretty hard on someone who has obviously spend a lot of time on this for PVR users and willing to offer help. The mods don't care about IPTV "subscriptions" most with stolen EPG data source, using mc2xml, zap2xml etc so this is really surprising. To say scraping is inherently wrong would break many of the official Kodi addons, some of this is based on a the user decision reading a site's TOS.
Of course any software could contain malware, but no one asks asks for closed-source before using it. It could also include log4j etc. Caveat emptor.
Martin
-
In relation to the VHF band, I challenge you to tell me the name of a single public TV broadcast that broadcasts in this band in ATSC, DTMB, DVB-T/DVB-T2 and ISDB-T digital format anywhere in the world ( I obviously exclude military and industrial applications). Will not be able!
ATSC 2-13 are VHF https://git.linuxtv.org/dtv-scan-table…ies-8VSB-062009 and still active.
Martin
-
If the streams works in 10.0.1 but not 10.0.0 that would indicate that you are tackling the wrong problem. I would change the post to address the CEC "bug" that you are talking about.
Martin
-
lack of sparetime
No worries and it wasn't meant as a complaint, it is working well now. I appreciate what you did since some people do like NextPVR more than TVHeadend.
Martin
-
Why can't I use what was working perfectly before though?
Fair point, just saying there is no reason to discount it as not working just because there are many TVHeadend LE users and it is just as easy to install (some users say easier). I'd be glad to help you get it to work.
-
I disagree with the statement to simply ignore NextPVR since it is can easily be installed via a zip package that CvH started for us but unfortunately abandoned, as it is working quite well in my testing on LE and CE platforms. Alternately you can install using Docker but configuring /dev/dvb devices in Docker takes a bit more expertise and potentially more resources although on an x64 device I doubt that would be a concern.
Martin
-
