2062 replies to this topic

[roxette]

Hey, i can verify that 16x16 issue occurs when using Nvidia card too,

Switch to any 4K channel and you'll see it. 

Edited by roxette, 15 February 2020 - 17:26.

[RevPir]

Ubuntu 19.10 fresh install and the same error as the user ozzsurf compiling gst-plugin-dvbmediasink.

 

make[1]: *** [Makefile:618: libgstdvbaudiosink_la-gstdvbaudiosink.lo] Error 1
make[1]: Leaving directory '/usr/src/OpenPLi-PC/libs/gst-plugin-dvbmediasink'
make: *** [Makefile:909: install] Error 2

 

How can I solve it?

 

[1455]

It’s strange. I installed 19.10 on formatted media.

Show the full log before this error, please. I don’t understand how it happened. Maybe you didn't add yourself to the group sudo (/etc/sudoers)?
Of course, some preliminary steps are needed, but u should not do anything except run scripts in terminal #. Moreover, don't make unnecessary absurd actions, such as 'chmod -R 755 /usr/src/OpenPLi-PC'. But I don't claim that you did it.

[roxette]

Switches the metronome. It previously didn't work by type of stream at all, since the concept of HD / SD (like hex or dec) cannot be defined. More precisely, constantly the same number was. This radio screensaver has nothing to do with reliability. What graphics card do you have? What is this channel on which 16x16?

 

 

Hey, i can verify that 16x16 issue occurs when using Nvidia card too,

Switch to any 4K channel and you'll see it. 

 

@1455,

I don't understand why you're ignoring my comments?

You asked me which channel that has 16x16

I replied but you ignored it completely and also ignored vdr xineliboutput issue.

You even didn't like my comment about radio mode and said that

Is this really the first task? Nothing more to improve? Well, let's break the metronome and the sound will disappear. 

Then you reported the same bug afterwards

What's wrong?

[roxette]

If you have Nvidia card, use opengl driver and you will see 16x16 when switching to HD channels

Or use vdpau and you will see 16x16 when switching to 4K channels

Can you fix that?

[roxette]

I forgot about the poll you created here

https://forums.openp...dpost&p=1162847

I wrote a commnet then you ignored it too.

 

If you will keep doing that i would prefer not to waste my time replying in this thread anymore!

[RevPir]

Hi 1455, thanks for the answer. I didn't do anything strange and nothing strange happened.

Fresh install ubuntu 19.10, install all updates and activate nvidia driver.

Install git and:

 

 

sudo -s

cd /usr/src

git clone https://github.com/ag1455/OpenPLi-PC.git

cd OpenPLi-PC

 

I run scripts 1 ... 6 step by step, so:

 

./1_build_libs.sh 2>&1 | tee build_libs.log
./2_build_libxine.sh 2>&1 | tee build_libxine.log
./3_build_openpliPC.sh 2>&1 | tee build_openpliPC.log
./4_build_plugins.sh 2>&1 | tee build_plugins.log
./5_build_oscam.sh 2>&1 | tee build_oscam.log
./6_build_lirc.sh 2>&1 | tee build_lirc.log

 

Stopped in the first script with this error.

Here's the log:

 

https://pastebin.com/nxEPF3pr

 

Thanks in advance.

Regards

[1455]

I have problems with the stationary internet. Sometimes I can open the forum page. The forum works on a mobile, but writing in a foreign language is very inconvenient. I will check and answer all your questions. Sorry for the inconvenience.

[1455]

Hi RevPir, this happened by accident. Thanks for the real report. Fixed. If the script deleted the /~ lib link in U 19.10, then create a new one or create it with live cd. Strange things happen. Nowhere in the script is there any mention of removing /lib, but this happens if the script breaks off at this point. However, on the 6th and higher generation hardware, viewing encoded channels is not possible. I still hope for help.

I think you will agree that in U 19.10 making links /usr/lib to the root folder, and hiding boot links to /boot wasn't the best idea for the developers.

[1455]

roxette, hevc will not work through the fifo buffer, since the hevc stream is about 20 mbps, which not every HDD can do. Just ignore the '16x16' in the logs.
If xineliboutput doesnt work for u, then take old version 'release libxine-1.2.9' . I didn't break anything. Just not compatible with VDR anymore now. I want to note what that forum topic is different. Sorry.

[RevPir]

Hi 1455, thanks again for the answer.

Current build status, for me, with Ubuntu 19.10:

 

- 1_build_libs.sh now it's ok.

- 2_build_libxine.sh give me error according to the log

_hxxps://pastebin.com/BA1EbGQz

 

I managed to solve by installing libtool-bin.

 

For me, viewing encoded channels is not possible, oscam works fine but no image, it doesn't seem to care about enigma2pc. I have motherboard MSI B350 PC MATE and processor AMD® Ryzen 3 2200.

 

Thanks and best regards

Edited by RevPir, 19 February 2020 - 18:21.

[roxette]

I'm not concerned about hevc, i was trying to reproduce the error so you could fix it.

In xine.conf use opengl and you see 16x16 when switching to HD channels even if you're using Nvidia graphics card.

# используемый видеодрайвер

# { auto  vdpau  aadxr3  dxr3  xv vaapi opengl2  XDirectFB  DirectFB  raw  opengl  aa  xshm  caca  xxmc  none  fb  xvmc }, default: 0

video.driver:opengl

 

It's not something in the log that i can ignore, watching tv using intel + opengl driver is like pain in the ass because e2 must switch to 16x16 after that it switches to radio mode then it displays radio screensaver (all of that are very unnecessary).

[1455]

Hey, i can verify that 16x16 issue occurs when using Nvidia card too,

Switch to any 4K channel and you'll see it.

 

Who wrote this? OK, I will check. However, don't forget that I don't take money.

[roxette]

 

Hey, i can verify that 16x16 issue occurs when using Nvidia card too,

Switch to any 4K channel and you'll see it.

 

Who wrote this? OK, I will check. However, don't forget that I don't take money.

 

 

I wrote that in order to reproduce the error.

No one said you take any money, no one said that you must fix all bugs either.

I'm just posting the problem i have got, so does @RevPir & @ozzurf.

You could probably able to fix that problem, if not then it's Okay to say i can't then i must wait for someone else who can. 

[1455]

The pursuit of excellence is a very good property. But looking for imperfection everywhere is the prerogative of the employee control department to reduce premiums.

even if you're using Nvidia graphics card.

 

For what need to enable opengl with an nvidia card? How do I fix this? This is nonsense compared to the real problem.

[roxette]

 

even if you're using Nvidia graphics card.

 

For what need to enable opengl with an nvidia card? How do I fix this? This is nonsense compared to the real problem.

 

You'll do it temporarily to reproduce the error.

That problem occurs if you use intel + opengl driver.

Perhaps it's related to the opengl driver?

[1455]

Perhaps it's related to the opengl driver?

 

 

Rather, with the osd patch for its video out. Now I'm busy with the problem dvbsoftwareca + oscam. What I'll do when my old hardware fails?

[roxette]

That was awesome,

After too many arguments, results=0. 

Thanks anyway.

Edited by roxette, 22 February 2020 - 15:36.

[1455]

If someone is an advanced programmer, but doesn't have ability to watch encrypted channels, then try to achieve on socket 1151 + DDR4 that after closing enigma2 the command 'lsmod | grep dvbsoftwareca' replied:

dvbsoftwareca 16384 0

This will be a sign of the module working. In the current state it hangs with a message:

dvbsoftwareca 16384 2

because it was 2 oscam processes. It's not possible to kill. Only by reboot. This explains the message "device or resource busy".

By the way, you can simulate this situation on old hardware by writing in dvb_softwareca.c:

int devices_counter = 2;

instead of ' = 0;'

Sorry, but this is the most important now.

[1455]

It makes no sense to chanch anythig in dvbsoftwareca. I insert the usb stick into the old PC and everything works. Most likely, need ask developers to rewrite intel-microcode and iucode-tool.

Below is the part of kernel.log when I run enigma2 and trying to open an encrypted channel. The module is dying. The Internet is teeming with similar logs.

Attached Files

•  kernel.zip   2.4KB   4 downloads