2072 replies to this topic

[1455]

<- I remember that the dual card is visible differently than two singles.
ls -a /dev/dvb/adapter0

.  ..  ca0  demux0  dvr0  frontend0  net0

ls -a /dev/dvb/adapter1

.  ..  ca0  demux0  dvr0  frontend0  net0

Show your ls output.

 

[roxette]

My dual-tuner card is the same.

ls /dev/dvb/adapter0

ca0        demux0     demux1     dvr0       dvr1       frontend0  net0

ls /dev/dvb/adapter1

ca0        demux0     demux1     dvr0       dvr1       frontend0  net0

demux1, dvr1 appeared after running pre_start script.

 

 

[roxette]

Yes, there is everything. Well, let's try. But no one answered about their new dvb card models and SNR.

 

Sorry, didn't see this post

If you were happy with your Technisat Skystar card then your next upgrade would be DD Cine S2 V7A.

Edited by roxette, 15 May 2021 - 18:18.

[1455]

I see the wrong definition of frontends in the script. If there are two dvb cards, then nim_sockets should look different.
For example:

NIM Socket 0:
      Type: DVB-S2
      Name: Montage Technology DS3000
      Has_Outputs: no
      Frontend_Device: 0

NIM Socket 1:
      Type: DVB-S2
      Name: Technisat SkyStar USB HD (DVB-S/S2)
      Has_Outputs: no
      Frontend_Device: 1

But in both cases we have frontend0. Most likely, changes hase accumulated in the kernels and enigma2.
First of all, you need to make sure that your dvb cards order is always the same. At me after 5 cold starts, PIC-E was detected first, and then USB. If there are two PCI-E cards, the order may be random. What will be the order in the case of a dual card, I don't know. If it changes from start to start, then you will have to write somesing like "/etc/udev/rules.d/99-dvb-symlinks.rules" with the assignment of links frontend2 and 3.
You can check the current order either by looking at the links properties of /sys/class/dvb/dvb0.demux0 and /sys/class/dvb/dvb1.demux0 or by the commands:

udevadm info -a /dev/dvb/adapter0/frontend0

 and

udevadm info -a /dev/dvb/adapter1/frontend0.

In this case, I will not be able to automate the recording of the nim_sockets file. But I made some changes in prestart.sh. Now need for the second card to have a link ~frontend1 in the /dvb folder.

The channels will probably need to rescan. So far I have not noticed any glitches in switching from card to card. Regarding ca0 on the second card, you need to check it yourself.

[1455]

<- I have dvbsoftwareca working fine on frontend0 and frontend1. True, I watch encoded channels only on one satellite. There's just nothing more to watch, everything is the same everywhere.

[NadjmGharib]

Hello I have some questions

Can the remote control be used?

When updating the program. Did I reinstall the program again?

How do I make the video fill the screen?

Sorry, I use Google Translate

[1455]

Can the remote control be used?

 

Lirc + any remote.

 

When updating the program. Did I reinstall the program again?

 

Yes, surely.

 

How do I make the video fill the screen?

 

F11 temporaly or in OSD menu constantly.

[roxette]

<- I have dvbsoftwareca working fine on frontend0 and frontend1. True, I watch encoded channels only on one satellite. There's just nothing more to watch, everything is the same everywhere.

Yes it works in a specific order ... that's the problem.

If you switch the coaxial cables it will work on adapter0 only.

I tried the new prestart script, if i restart dvbsoftwareca it creates 3 CA devices

 

dvbsoftwareca: registering adapters
dvbsoftwareca: register adapter0/ca0 @ minor: 0000
dvbsoftwareca: registered CA0 device for adapter0
dvbsoftwareca: register adapter1/ca0 @ minor: 0004
dvbsoftwareca: registered CA0 device for adapter1
dvbsoftwareca: register adapter1/ca1 @ minor: 0005
dvbsoftwareca: registered CA1 device for adapter1
dvbsoftwareca: registered 3 CA devices

But i can't see any difference, oscam can decrypt channels on adapter0 only.

If switch the coxial cables it will work on both adapters even without using the prestart script.

By the way, i don't have adapters order problem using dual-tuner card.

adapter0 and adapter1 will be the same no matter how many times i boot my pc.

 

Can you describe the SNR problem?

Do you use media_build?

Edited by roxette, 22 May 2021 - 19:42.

[1455]

I see one oddity. We may don't make symlink to rontendN at all, but for the second adapter need to write in nim_sockets: "Frontend_Device: 1".
I don’t know why this happens, but dvb cards are switched faster. This is what I did in the last commit.

I have no problem with SNR. This was written by a user whose SNR is always 0 and I advised him to disable the EncryptedChannel plugin.

[roxette]

Hi, the last commit is good.

There was a bug in DVB adapter recognition.

My 2nd adapter was recognized as a DVB-T2 tuner in nim_sockets ... i don't know why.

I changed it back to DVB-S2.

I hope that one day e2 will work without libxine at all like vdr-softhddevice.

@milaebrothers said he is working on it but never showed up since then. 

It works as follows on Raspberry Pi.

E2 on Raspberry Pi depends on rpihddevice,so without it, it won't run.

The same will be on pc, e2 will depend on softhddevice.so.

Edited by roxette, 25 May 2021 - 16:41.

[roxette]

Sorry, in Raspberry pi e2 depends on librpihddevice.so hence e2 for pc will depend on libsofthddevice.so.

That way we can say goodbye to libxine. 

Edited by roxette, 26 May 2021 - 16:24.

[ptergrand]

In the right corner of the channel, it says Stopped, how can I fix it.

 

 

Attached Files

•  Screenshot_20210611_221856.png   1.22MB   6 downloads

[roxette]

I don't see the word "stopped" anywhere in the screenshot. 

However i figured out that "Durduruldu" means stopped 

"Uygulama durduruldu hatası yaşanırsa ne yapabilirim? "

 

Menu -> Plugins then enable Clear mem or whatever it's called.

[1455]

ptergrand, is DVB card single or multi? Is this message persistent? I don't remember the reason, but I saw this. This may be due to the absence of a second card in the /dev/dvb folder, for example. If there is a multicard, then the folder /dev/dvb should contain all the tuners. But my patch doesn't is reason this in any way.

 

[ptergrand]

TBS 6903 A-B Tuner there is ( Is this message persistent ) Yes How can I fix

 

 

Attached Files

•  Screenshot_20210612_234331.png   431.5KB   4 downloads
•  Screenshot_20210612_234412.png   248.44KB   2 downloads
•  Screenshot_20210612_234512.png   399.99KB   3 downloads
•  Screenshot_20210612_234601.png   1.57MB   2 downloads
•  Screenshot_20210612_235246.png   78.33KB   1 downloads

[ptergrand]

Which command should I use to update the program again?

[1455]

This problem has always existed or occurs in one of the newer versions of e2? Do you use both tuners or only the first one?

Which command should I use to update the program again?

I didn't understand the question.
 

[ptergrand]

This problem did not exist before. It appeared because e2 is constantly updated.

What command should I use to keep e2 constantly updated?

[1455]

Learn to attach logs, not screenshots. I have to pull information out of you as on interrogation to understand what's happening.

e2 is not updated by itself. What is the output of the command

git log

in the source tree or what is written in the Menu->About version e2?
What happens if you rewrite the settings file from the original directory and recreate your own?

What happens if you manually create symlinks ~frontend1 on frontend0 inside /dev/dvb/adapter0 folder and start e2 again without restarting the PC?

lsdvb

?
 

Edited by 1455, 14 June 2021 - 09:41.

[roxette]

What are you guys talking about?

The "stopped" message is related to clearmem plugin

 

def __chckState(self):   def subStart():   if cfg.enable.value:   self.state = cfg.enable.value   self.ClearMemTimer.start(int(cfg.timeout.value)*60000)   self['message_label'].setText(_("Started"))   else:   self['message_label'].setText(_("Stopped"))   if cfg.scrinfo.value and ClearMemAuto.dialog is not None:   ClearMemAuto.dialog.show()   self.ClearMemWatchDog.stop()   if self.instance and cfg.enable.value != self.state:   if self.ClearMemTimer.isActive():   self.ClearMemTimer.stop()   subStart()  

self.ClearMemWatchDog.start(int(cfg.timescrinfo.value) * 1000)

 

It's very weird that both of you didn't even care to read my reply.

I even wrote some turkish words from google but it seems that it was hidden to @ptergrand

By the way, @ptergrand if you come on the forum to talk with a specific person just let us know so i don't bother replying to your posts anymore.

Edited by roxette, 14 June 2021 - 17:10.