ERROR: SQL: [TV29] Successful result

December 28, 2017, 12:34 pm

≫ Next: unable to open clientspecific settings after update

≪ Previous: VDR on LibreELEC with Wetek play2

Hello,

I am running the latest LibreELEC 8.2.2 with Kodi 17.6 and the Kodi VNSI-Client. Unfortunally the log is filled with SQL errors. I turned on debug and got the following:

Code:
27:03.269 T:139680564528896    INFO: PVRChannelGroupInternal - AddAndUpdateChannels - updated TV channel 'Real Time HD'

27:03.278 T:139680564528896   DEBUG: CPVRChannelGroup - Persist - persisting channel group 'Alle Kanäle' with 2709 channels

27:03.278 T:139680564528896   DEBUG: Mysql execute: REPLACE INTO channelgroups (idGroup, bIsRadio, iGroupType, sName, iLastWatched, bIsHidden, iPosition) VALUES (21, 0, 1, 'Alle Kanäle', 1514495091, 0, 0)

27:03.310 T:139680564528896   DEBUG: Mysql Start transaction

27:03.311 T:139680564528896   ERROR: SQL: [TV29] Successful result

                                            Query: REPLACE INTO channelgroups (idGroup, bIsRadio, iGroupType, sName, iLastWatched, bIsHidden, iPosition) VALUES (21, 0, 1, 'Alle Kanäle', 1514495091, 0, 0)

27:03.313 T:139680564528896   DEBUG: Mysql rollback transaction

27:03.313 T:139680564528896   ERROR: CommitInsertQueries - failed to execute queries

27:03.317 T:139680564528896   DEBUG: CPVRChannelGroups - PersistAll - persisting all changes in channel groups

Before the first line quoted here all other 2709 channels are listed. I also see these errors with the radio channels. And these messages do repeat themselves at least every minute, most of the time a lot more often.

What I really don't understand is why I get an ERROR and a successful result behind. Also the query does work, I tested it in my MySQL console. Oh, by the way, I switched to MySQL for the TV29 database, but these errors are not new, they existed also before I switched from the default database system.

Any idea?

Cheers,
Roi

↧

unable to open clientspecific settings after update

January 10, 2018, 5:03 pm

≫ Next: Info Text during Live TV auto-closes after a few seconds

≪ Previous: ERROR: SQL: [TV29] Successful result

After installing a new build of kodi 18 I am no longer able to open clientspecific settings in pvr & tv section. It seems liks kodi is totally unresponsive when selecting the entry. Settings have remained unchanged and vdr/kodi is running smoothly as before. Just that I can't access the vdr osd and settings any more.

vdr 2.3.8 is installed locally with currently only vnisserver and ddci2 plugin active

When selecting the menu entry only these lines are added to syslog:

Quote:Jan 11 01:17:11 kodi-mc vdr: [1240] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf
Jan 11 01:17:11 kodi-mc vdr: [1240] VNSI: Client with ID 31 connected: 127.0.0.1:36136
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI Client 31->127.0.0.1:36136 thread started (pid=933, tid=1992, prio=high)
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI: Welcome client 'XBMC osd client' with protocol version '12'
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI: cxSocket::read(fd=24): eof, connection closed
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI Client 31->127.0.0.1:36136 thread ended (pid=933, tid=1992)
Jan 11 01:17:11 kodi-mc vdr: [1244] VNSI: Client with ID 31 seems to be disconnected, removing from client list

Is this a known issue wth the recent code or what else can I do to help troubleshoot?

Edit:
It's interesting, though, that when I open the clientspecific settings menu from another vnsi client (RPI3 running kodi 17.6/LE 8.2.2) which accesses the same vdr on the above host, I am getting the osd and settings displayed correctly and syslog shows:

Quote:Jan 11 02:08:14 kodi-mc vdr: [1239] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf
Jan 11 02:08:14 kodi-mc vdr: [1239] VNSI: Client with ID 27 connected: 192.168.178.15:55962
Jan 11 02:08:14 kodi-mc vdr: [2533] VNSI Client 27->192.168.178.15:55962 thread started (pid=848, tid=2533, prio=high)
Jan 11 02:08:14 kodi-mc vdr: [2533] VNSI: Welcome client 'XBMC osd client' with protocol version '10'
Jan 11 02:08:14 kodi-mc vdr: [2533] VNSI: new osd provider

So to me it looks like the issue is only present in the new kodi 18 code. With previous kodi 18 alpha code, like from a week ago, I am pretty sure it was also still working.

↧

Info Text during Live TV auto-closes after a few seconds

January 14, 2018, 5:51 pm

≫ Next: v18 - Thumbnail pictures for recordings

≪ Previous: unable to open clientspecific settings after update

Probably not unique to Live TV with vdr/vnsi, but I noticed that unlike in previous releases the info text that appears when pressing "i" in LIve TV auto-closes after a few seonds. However, when playing movies it works as expected and only closes after pressing "i" once again.

Nothing severe, but since Kodi 18 is surprisingly mature and stable for an alpha release this is one of the few flaws that caught my attention.

Let me know if this needs to be reported in a different section of the forum.

↧

v18 - Thumbnail pictures for recordings

January 28, 2018, 4:32 am

≫ Next: v18 - fast forward and rewind issues in live tv with recent nightly

≪ Previous: Info Text during Live TV auto-closes after a few seconds

This is not an actual issue and more out of curiosity: I think there was a vague announcement that with kodi 18 there will be autoextracted thumbnails for recordings.

Installing the latest kodi 18 nightly which already looks pretty mature and "final" to me, I cannot see that this has become available yet. Has this feature been completely abandonned or will it be introduced with later releases or even in kodi 18 final?

↧

v18 - fast forward and rewind issues in live tv with recent nightly

February 18, 2018, 5:00 pm

≫ Next: v18 - Show channel info setting delays channel switching

≪ Previous: v18 - Thumbnail pictures for recordings

I am running on Kodi-18.0-ALPHA1 Git:20180216-0fcc225-dirty.
It seems at least rewind is broken in live-tv with timeshift activated (I tested both FILE and RAM setting). Also fast forward produces some strange artefacts/flashing. Playing recordings or videos it all seems to work just fine.

↧

v18 - Show channel info setting delays channel switching

March 4, 2018, 5:30 pm

≫ Next: Interesting discussion regarding handling of scrambled packets in vnsiserver

≪ Previous: v18 - fast forward and rewind issues in live tv with recent nightly

This is propably not specfic to VNSI/VDR, but as it occurs only in Live TV and since there is no general PVR section I thought I might tryi my luck here. Please move this thread to different section if appropriate.

I also tested this with two different skins (Confluence and Estuary) to make sure it is not a single skin issue.

What I observe is that when I set 'Show channel info when switching channels' in PVR settings to anything > 0 secs it seems to (significantly) delay channel switching; sometimes up to several seconds. This seems due to the previously reported fact that the channel info is initially displayed with an empty text and then populated with the actual channel info which also delays appearing of the Live TV stream.

Furthermore, while the info box appears for the set amount of time, the actual info appears for much less time due to the delay, making it sometimes unreadable in the remaining seconds.

I've now set 'Show channel info' to 'off' and channel switching is acceptably fast. Not sure if the appearance of the info text can be accelerated, however, I think it is not meant to delay bringing up the live tv stream.

If I remember correctly from previous releases, e.g. Kodi 17, the correct channel info was displayed instantly and zapping was without delay. Looks like it is handled differently in Kodi 18.

↧

Interesting discussion regarding handling of scrambled packets in vnsiserver

March 7, 2018, 2:13 am

≫ Next: v18 - Frequent segfault in PVR after system resumes from standby

≪ Previous: v18 - Show channel info setting delays channel switching

Hi FernetMenta,

perhaps you are already aware. I'd like to direct your attention to an ongoing discussion at vdr-portal.de. If In understand correctly, they propose changes in vnsiserver to allow for a better handling of scrambled packets in combination with DD CI devices. I assume the language is not an issue for you Wink

↧

v18 - Frequent segfault in PVR after system resumes from standby

March 22, 2018, 2:24 pm

≫ Next: KODI, VDR and H.265 (5.1 Audio) and VNSI Plugin

≪ Previous: Interesting discussion regarding handling of scrambled packets in vnsiserver

When my System wakes up from standby I am repeatingly experiencing crashes with the below lines in the crashlog:

Quote:Core was generated by `/usr/local/lib/kodi/kodi-x11 --standalone'.Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000000000148ea86 in PVR::CGUIEPGGridContainer::GetItem(int) ()
[Current thread is 1 (Thread 0x7f2823601980 (LWP 1222))]
...

Thread 1 (Thread 0x7f2823601980 (LWP 1222)):
#0 0x000000000148ea86 in PVR::CGUIEPGGridContainer::GetItem(int) ()
#1 0x000000000148ebad in ?? ()
#2 0x0000000001491e89 in PVR::CGUIEPGGridContainer::UpdateItems() ()
#3 0x0000000001492216 in PVR::CGUIEPGGridContainer::OnMessage(CGUIMessage&) ()
#4 0x000000000101a2e9 in CGUIControlGroup::SendControlMessage(CGUIMessage&) ()
#5 0x000000000101b1bf in CGUIControlGroup::OnMessage(CGUIMessage&) ()
#6 0x00000000010ad0bb in CGUIWindow::OnMessage(CGUIMessage&) ()
#7 0x0000000000dd2923 in CGUIMediaWindow::OnMessage(CGUIMessage&) ()
#8 0x000000000147eb74 in PVR::CGUIWindowPVRBase::OnMessage(CGUIMessage&) ()
#9 0x00000000014866b6 in PVR::CGUIWindowPVRGuideBase::OnMessage(CGUIMessage&) ()
#10 0x0000000000dfd112 in CGUIViewControl::SetItems(CFileItemList&) ()
#11 0x0000000000dd1c08 in CGUIMediaWindow::OnFilterItems(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#12 0x0000000000dd41ce in CGUIMediaWindow::Update(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool) ()
#13 0x000000000147deaf in PVR::CGUIWindowPVRBase::Update(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool) ()
#14 0x0000000001486385 in PVR::CGUIWindowPVRGuideBase::Update(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool) ()
#15 0x0000000000dc740b in CGUIMediaWindow::Refresh(bool) ()
#16 0x0000000001486961 in PVR::CGUIWindowPVRGuideBase::OnMessage(CGUIMessage&) ()
#17 0x00000000010b2970 in CGUIWindowManager::SendMessage(CGUIMessage&) ()
#18 0x00000000010b9d28 in CGUIWindowManager::OnApplicationMessage(KODI::MESSAGING::ThreadMessage*) ()
#19 0x0000000000f85275 in KODI::MESSAGING::CApplicationMessenger:rocessMessage(KODI::MESSAGING::ThreadMessage*) ()
#20 0x0000000000f85a10 in KODI::MESSAGING::CApplicationMessenger:rocessWindowMessages() ()
#21 0x00000000012ff099 in CApplication:rocess() ()
#22 0x00000000013c4235 in CXBApplicationEx::Run(CAppParamParser const&) ()
#23 0x0000000000f5f4f2 in XBMC_Run ()
#24 0x00000000008a1902 in main ()

Kodi restart after the crash is faster than the tv coming up, so I usually don't really notice. However, I was puzzled by the amount of crashlogs in my home dir and found some were due to the same segfault.

The system shuts off vdr and unloads dvb drivers on standby and reloads drivers and starts vdr with a delay of approx. 5 secs after resume. I have other crashes due to a segfault in libcec4, but I assume this is unrelated.

Any hint?

↧

KODI, VDR and H.265 (5.1 Audio) and VNSI Plugin

August 31, 2017, 1:19 pm

≫ Next: Dependency issue with pvr.vdr.vnsi plugin

≪ Previous: v18 - Frequent segfault in PVR after system resumes from standby

I have the following setup: A small PC with VDR 2.3.8 as the server. As the client I tested a Vero4K and Linux Clients. On both clients with KODI 17.x (I tried several versions) there are dropouts in Sound when the Sound is 5.1. (Stereo sound works without problems).
This behaviour is found when playing Live TV or recordings from Live TV.
When I play the same over vlc, the sound is ok. So I think it's a problem with the plugin.
Has anyone experiences with this setup?

Thanks

Holger

↧

Dependency issue with pvr.vdr.vnsi plugin

April 16, 2018, 10:09 am

≫ Next: VDR 2.4.0 stable announced

≪ Previous: KODI, VDR and H.265 (5.1 Audio) and VNSI Plugin

I have downloaded and compiled the vnsi plugin from here:
https://github.com/FernetMenta/pvr.vdr.vnsi

I created a zip file of the pvr.vdr.vnsi directory from xbmc/addons/pvr.vdr.vnsi directory.
I attempt to install this addon using the install from ZIP file option in Kodi.

I get this error:
ERROR: CAddonInstallJob[pvr.vdr.vnsi]: The dependency on kodi.binary.global.gui version 5.12.0 could not be satisfied.

I am using Kodi 17.6 Git:Unknown

What should/can I do?

Regards,

Jim

↧

VDR 2.4.0 stable announced

April 16, 2018, 11:20 pm

≫ Next: Solved - Still getting invalid lock sequence error when starting vdr with latest vnsiserver

≪ Previous: Dependency issue with pvr.vdr.vnsi plugin

Hi, just for your information:

http://www.tvdr.de/changelog.htm

https://www.vdr-portal.de/forum/index.ph...ion-2-4-0/

Greetings Hoppel

↧

Solved - Still getting invalid lock sequence error when starting vdr with latest vnsiserver

May 4, 2018, 7:07 am

≫ Next: v18 - kodi crashes when fast forwarding a recording

≪ Previous: VDR 2.4.0 stable announced

This is the output I get in syslog when starting vdr 2.4.0 with latest vnsiserver:

Quote:May 4 15:51:19 kodi-mc vdr: [14298] --- begin invalid lock sequence report
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - W - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - U - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - W - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - U - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14273 - R - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14273 - * - - R - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14273 - * - - U - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14298 W W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14298 * - - - R - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14298 * - R - * - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14298 invalid lock sequence: 3 Recordings
May 4 15:51:19 kodi-mc vdr: [14298] full backtrace:
May 4 15:51:19 kodi-mc vdr: [14298] /usr/local/bin/vdr cStateLock::Lock(cStateKey&, bool, int) at thread.c:735
May 4 15:51:19 kodi-mc vdr: [14298] /usr/local/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.0 CVNSITimers::Action() calling cRecordings::GetRecordingsRead(cStateKey&, int) at recording.h:237 at cRecordings_Lock::cRecordings_Lock(bool) at recording.h:299 at CVNSITimers::Action() at vnsitimer.c:459
May 4 15:51:19 kodi-mc vdr: [14298] /usr/local/bin/vdr cThread::StartThread(cThread*) at thread.c:294
May 4 15:51:19 kodi-mc vdr: [14298] /lib/x86_64-linux-gnu/libpthread.so.0 at ??:?
May 4 15:51:19 kodi-mc vdr: [14298] /lib/x86_64-linux-gnu/libc.so.6 clone at clone.S:111
May 4 15:51:19 kodi-mc vdr: [14298] --- end invalid lock sequence report
May 4 15:51:19 kodi-mc vdr: [14298] --- THERE WILL BE NO FURTHER REPORTS UNTIL VDR IS RESTARTED!
May 4 15:51:19 kodi-mc vdr[14273]: invalid lock sequence at Fr. 04.05. 15:51

vdr-2.4.0 has both offical patches from klaus and vnsiserver is latest code (as of May 1, 2018). vdr is running on ubuntu 16.04.03.

Can this be ignored? What are the side effects of this?

↧

v18 - kodi crashes when fast forwarding a recording

May 4, 2018, 9:02 am

≫ Next: VDR Recording Length Incorrect in Kodi v18

≪ Previous: Solved - Still getting invalid lock sequence error when starting vdr with latest vnsiserver

koid crashes when fast forwarding a recording as documented in the below extracts of the kodi_crashlog:

Quote:[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/lib/kodi/kodi-x11 --standalone'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000c04409 in VideoPicture::SetParams(VideoPicture const&) ()
[Current thread is 1 (Thread 0x7fc43940b700 (LWP 2601))]

...

Thread 1 (Thread 0x7fc43940b700 (LWP 2601)):
#0 0x0000000000c04409 in VideoPicture::SetParams(VideoPicture const&) ()
#1 0x0000000000c26d45 in VAAPI::COutput::Flush() ()
#2 0x0000000000c27b2f in VAAPI::COutput::StateMachine(int, Actor:rotocol*, Actor::Message*) ()
#3 0x0000000000c280ac in VAAPI::COutput:rocess() ()
#4 0x0000000000f26a65 in CThread::Action() ()
#5 0x0000000000f29f62 in CThread:taticThread(void*) ()
#6 0x00007fc5035266ba in start_thread (arg=0x7fc43940b700) at pthread_create.c:333
#7 0x00007fc4fab0241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

I can reproduce this (often but not always) by starting playback of a recording, ff at 32x speed and then press play. Somtimes it crashes even before I press play or any other key.

Interestingly, sometimes after a crash I completely lose audio in kodi (via hdmi), requirung reboot to make kodi work again with audio output.

↧

VDR Recording Length Incorrect in Kodi v18

May 19, 2018, 7:24 am

≫ Next: Linux - VNSIServer - True Color OSD Support ?

≪ Previous: v18 - kodi crashes when fast forwarding a recording

I have a bunch of VDR recordings with the commercials removed via post-processing, but I have noticed the latest v18 nightlies show the original recorded length (say 30 min, when it's actually 22 min). If I seek past 22 min in the file, playback just stops (edit: nope, sometimes it crashes Kodi). I'm guessing the client addon now reads the recording's info file rather than getting the length from the recording itself? Any chance we could change it back?

I cut the files rather than using VDR "marks" files because marks files requires me to push a button each time to skip commercials.

Thanks!

↧

Linux - VNSIServer - True Color OSD Support ?

July 9, 2018, 6:24 am

≫ Next: v18 - Strange issue when tuning into CNBC

≪ Previous: VDR Recording Length Incorrect in Kodi v18

Hello everyone,
I am currently working on a complete LiveTV for LibreELEC and without using the Kodi player, which streams the audio/video, and thus causes slow zaps : https://forum.libreelec.tv/thread/12771-...thout-x11/
After several days of debugging, I conclude that the OSD of VNSIServer, does not support Skins which require in addition the activation of the True Color (skindesigner), but just the use of skin classic.
I would like to know if the plugin VDR VNSIServer, and its OSD in Socket (Server/Client), can support such a solution, and hope for a Roadmap for a next compatibility ?
I have a doubt about this exchange in Socket, which could pose problems on animations...

Looking forward to reading you, I tell you very quickly !

↧

v18 - Strange issue when tuning into CNBC

August 22, 2018, 1:40 pm

≫ Next: EPG data has 1 hr offset after end of DST

≪ Previous: Linux - VNSIServer - True Color OSD Support ?

I am observing a strange issue when tuning into CNBC which I receive via DVB-S/Sattelite.

When switching to CNBC channel, the picture freezes almost immediately while audio continues for a few secons and then stops. Then, I see the ring which indicates buffering filling upto 100% but no progress. The picture just remains frozen.

I can confirm this issue both on my Raspberry Pi with a recent Milhouse built (from August 20) and on my Ubuntu system which runs a recent self-compiled nightly built. PVR backend is a VDR 2.4.0 running on the same Ubuntu system in combination with a DD DVB-S/S2 dual tuner card.

For the time intervall I had switched to CNBC I see the follwing lines in my kodi log:

@Karellen - Log removed

↧

EPG data has 1 hr offset after end of DST

October 28, 2018, 11:24 am

≫ Next: v18 - VDR and "Replace filenames with library titles" don't work

≪ Previous: v18 - Strange issue when tuning into CNBC

With tonight's end of DST in Germany clocks were set back 1 hr. Unfortunately, instead of applying a correction to the EPG data (I'm using EPG date from DVB stream) the start and end times of all broadcasts are displayed with a 1hr offset (e.g. 'Tagesschau' starting at 9pm instead of 8pm). After manually reloading the data all times are displayed correctly.

I am aware of the current discussion pro/con DST and thus, this issue my soon become obsolete. However, a solution to this issue might be applicable for other regions where DST is still in use.

Would it be possible to implement correction of EPG data after start/end of DST automatically or, for the least, trigger an automatic reload?

↧

v18 - VDR and "Replace filenames with library titles" don't work

November 1, 2018, 11:27 am

≫ Next: EPG distributed on one channel DVB-C Canal Digital Norway

≪ Previous: EPG data has 1 hr offset after end of DST

Hi,

i am using Kodi since version 11 to view my recorded movies with vnsi on different OS. I have not enabled NFS or cifs shares.
The Version 14.2 was the last one with a full functional settings of "Replace filenames with library titles".
Version 15, 16 and 17 not working too ;-)

Now i am testing version 18 to get this feature back. But...

1) In the movie sektion
Example:
a movie show the filename "%Ice Age".
I "scan to library" -> the Fanart etc. will be shown
With Version 18, it change the filename to library title, great
But, if i exit kodi and check the ice age movie, fanart not shown.
With Version 17.6, nothing happend!

2) VDR Recordings
only show filenames and no fanart

3)No missing movie feature
I am not able to check if the movie is in the database or not.

I have tested this scenario with:
OS: linux, Windows and OSX
DB: sqlite and mysql (primary)

The error is not os nor database dependend
i need help.

Best regards

P0jn0A

PS: Many thanks to the developer team, without them i am not able to view my VDR movies remotly.

↧

EPG distributed on one channel DVB-C Canal Digital Norway

November 11, 2018, 9:59 pm

≫ Next: Problem with Center Channel on 5.1 Live TV Content

≪ Previous: v18 - VDR and "Replace filenames with library titles" don't work

EPG I only get the current and next program for each channel. On TV Mosaic/DVBlink I get all channels for about a week. On MediaPortal I had to select that all EPG data was on FOX HD to get the same. I read somewhere that you need to have a "modern" EPG scraper that supports getting all EPG data from a central channel to get all data. How can I do this with VDR? I have tried to install some plugins and change the settings but any plugin and setting just gives the same result.

Anyone have any experience with EPG distributed from on channel? Is there a plugin? Any other solution? And this is DVB-C.

Running VDR 2.4.0 on Linux Mint 19.

↧

Problem with Center Channel on 5.1 Live TV Content

November 15, 2018, 8:17 am

≫ Next: Solved - CAM error/re-tune on specific transponder

≪ Previous: EPG distributed on one channel DVB-C Canal Digital Norway

I've recently bought a new TV and now I've got some problems with the audio during Live TV.
My Setup now looks like this: HTPC(Kodi) -> HDMI: Audio/Video -> TV -> HDMI ARC: Audio -> AVR.
The problem now is that if I watch anything live with 5.1 Audio the center channel audio stream is missing, !!!!BUT!!!! if I record such a program and watch the recording 5.1 audio works fine as expected.
Other Audio format on video files also work as expected

I've tested this with the latest stable libreelec 8 as well as the current libreelec 9 alpha.

Maybe someone has an Idea??

Thank you in advance!!

↧