Unable to install v5

[johnzered]

Does ffmpeg.exe exist?  It should have been installed by the Windows unzip but maybe you skipped it.

NextPVR is not open source.

Martin

No, no such file is available in the Zip-file. If it's supposed to be there, well then it needs to be added. I got ffmpeg.exe on my server from before anyway so I created a folder named "Other" and copied ffpmeg.exe into it. But still no success. I noticed I do not get any epg data either.

I've included logs where I:
1. Start the server
2. Log in to the web UI.
3. Trying to update EPG
4. Trying to watch a channel.

Any suggestions?

[mvallevand]

There is a problem on the server distribution for sure the zip doesn't include ffmpeg so a lot of other new users will have troubles.

I am not seeing any error 32 bit related in your logs. Ignoring transcoding if you try a recording is a file created and can you play it in another app like vlc or Kodi.

Martin

[johnzered]

I've actually somewhat managaed to get this working now.
I had to step back and test v4 instead as I'm new to NextPVR I needed a more stable ground to explore how NextPVR actually works and the functionality it offers.

I've then cleared everything and started fresh with v5 following the "guide" you wrote on how to get v5 running on 32-bit Windows. I think part of the problems I had before was that I was using a TBS-card as my primary card instead of my second tv-card which is a FireDTV/FloppyDTV Tuner. I found out during testing v4 that the CI module is not supported on TBS cards and toggling the setting for CI on and off in v4 gave me similar errors I was experiencing in v5.

Now using FireDTV/FloppyDTV as the primary tuner I'm able to update the EPG and stream through the webinterface in v5. But I'm subscribing to encrypted channels and I have a Conax card reader in my TBS 6618 tuner. Unfortunately I cannot use the FireDTV/FloppyDTV for this because for some reason it doesn't like the card reader I have/need to use in order to watch the encrypted channels. So my question is, is support for CI modules on TBS cards something that is coming to NextPVR?

[sub]

Sorry, there is no support for CI modules in NextPVR. In the past it did have some support for CI, but about 5 years ago my DVB-C cable provider moved away from irdeto, and I no longer have access to smartcard and encrypted signals to test against.

[Reddwarf]

I've actually somewhat managaed to get this working now.
I had to step back and test v4 instead as I'm new to NextPVR I needed a more stable ground to explore how NextPVR actually works and the functionality it offers.

I've then cleared everything and started fresh with v5 following the "guide" you wrote on how to get v5 running on 32-bit Windows. I think part of the problems I had before was that I was using a TBS-card as my primary card instead of my second tv-card which is a FireDTV/FloppyDTV Tuner. I found out during testing v4 that the CI module is not supported on TBS cards and toggling the setting for CI on and off in v4 gave me similar errors I was experiencing in v5.

Now using FireDTV/FloppyDTV as the primary tuner I'm able to update the EPG and stream through the webinterface in v5. But I'm subscribing to encrypted channels and I have a Conax card reader in my TBS 6618 tuner. Unfortunately I cannot use the FireDTV/FloppyDTV for this because for some reason it doesn't like the card reader I have/need to use in order to watch the encrypted channels. So my question is, is support for CI modules on TBS cards something that is coming to NextPVR?

You could move over to softcam and a cardserver like NewCS, Sub has promised to implement the remaining code needed for softcam to work on v5 and I'll be testing it as soon as it is ready

[Ludron]

Sorry, there is no support for CI modules in NextPVR. In the past it did have some support for CI, but about 5 years ago my DVB-C cable provider moved away from irdeto, and I no longer have access to smartcard and encrypted signals to test against.

Possible other way to skin this CAt would be to become such mini provider. Maybe most users are not even aware there is certain bridge for Linux:

The caX device associated with a CI device behaves just like any other caX interface. You usually use it through a library like libdvben50221 which is part of the dvb-apps package available at linuxtv.org.

But contrary to other hardware where the CI module is physically placed in the data path between the the demod and PCIe bridge, in the Digital Devices cards the CI module is separate hardware.

So, you have to feed data to the CI module by writing to the secX (in later kernel ci0) device and read it back from the same secX device.

The advantage is that the CI module can be used with any data coming from any frontend or file. The disadvantage is that the user application has to write/read the data to/from the module by itself.

• to connect 2 Digital Devices DuoFlex S2 or DuoFlex C/T (max. 4 Tuner)
  
  

or to connect TV cards from other vendors (only single transponder mode, 1 CI = 1 tuner)

 2 CI slots for two independent CAMS on one socket

Up to 2 X 4 decrypted pay TV channels
Only one CAM required to decrypt 4 encrypted pay TV channels. Supports watching one encrypted channel and record several encrypted channels simultaneously.

[sub]

Sorry, there is no support for CI modules in NextPVR. In the past it did have some support for CI, but about 5 years ago my DVB-C cable provider moved away from irdeto, and I no longer have access to smartcard and encrypted signals to test against.

Possible other way to skin this CAt would be to become such mini provider. Maybe most users are not even aware there is certain bridge for Linux:

The caX device associated with a CI device behaves just like any other caX interface. You usually use it through a library like libdvben50221 which is part of the dvb-apps package available at linuxtv.org.

But contrary to other hardware where the CI module is physically placed in the data path between the the demod and PCIe bridge, in the Digital Devices cards the CI module is separate hardware.

So, you have to feed data to the CI module by writing to the secX (in later kernel ci0) device and read it back from the same secX device.

The advantage is that the CI module can be used with any data coming from any frontend or file. The disadvantage is that the user application has to write/read the data to/from the module by itself.

• to connect 2 Digital Devices DuoFlex S2 or DuoFlex C/T (max. 4 Tuner)
  
  

or to connect TV cards from other vendors (only single transponder mode, 1 CI = 1 tuner)

 2 CI slots for two independent CAMS on one socket

Up to 2 X 4 decrypted pay TV channels
Only one CAM required to decrypt 4 encrypted pay TV channels. Supports watching one encrypted channel and record several encrypted channels simultaneously.

As mentioned above, unfortunately I have zero ability to test anything CI related these days, so I'm unlikely to do anything much in this area. Anything beyond trivial changes are not really practical to develop without a way to test as I go.

[greg in kansas]

I will vote for windows 32 bit

[mvallevand]

I will vote for windows 32 bit

The instructions I posted earlier should get you started on windows32 but you might have to use the macos zip until zip fixes the linux zip.

Mrtin