tsduck: [BUG] Not possiple to run multiple tsp processes with different vatek devices.

Bug description:

Hi all and @lelegard

I am currently using a setup where i have 2 TV’s and 2 vatek modulators to send a transport stream to my tv’s. Both of these vatek devices are connected to my laptop and when i list the devices using tsvatek -a i get the following output:

Found 2 VATek devices
 - Device 0: .//4-0//vatek-usb
 - Device 1: .//4-0//vatek-usb

I use the following tsp command: tsp -I file generic-HbbTV-Teststream.ts -i -O vatek --device 0 --frequency 474000000 --modulation DVB-T --bandwidth 8. This command works perfectly fine with both devices, when run by itself.

The problem happens when i try to start multiple tsp processes, by running the above tsp command with both device 0 and device 1.

What happens is that once i have run the command tsp -I file generic-HbbTV-Teststream.ts -i -O vatek --device 0 --frequency 474000000 --modulation DVB-T --bandwidth 8 , it runs fine, and i then move on to the second device by running, tsp -I file generic-HbbTV-Teststream.ts -i -O vatek --device 1 --frequency 474000000 --modulation DVB-T --bandwidth 8. This is where the error happens and it tells me that it is unable to detect any vatek devices. It seems like the first tsp process is locking both vatek devices for some reason.

Expected behavior:

I expected to be able to have 2 tsp processes running simultaneously, using 2 different vatek modulators.

Errors and logs:

The error i get when i run the second tsp command is the following:

* Error: vatek: no VATek device found

Environment:

  • OS: Kubuntu
  • OS version: Ubuntu 22.04.4
  • TSDuck full version: 3.38-3820
  • Installation type: I build the one from github.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 24 (15 by maintainers)

Most upvoted comments

Thank you @Ravnholt7507 for your feedback. I will close this one.

Thank you @a83912a for your work on the bug fix.

@Ravnholt7507, one last point, could you update issue #1508 to indicate whether or not the VATek + Dektec conflict is solved with the new version?

@phil-net, there is still an issue with libvatek (see issue https://github.com/VisionAdvanceTechnologyInc/vatek_sdk_2/issues/9), up to the point that an unfortunate side effect of its last version broke the compatibility and broke TSDuck builds. I had to temporarily disable VATek support in TSDuck until a definitive fix is available in libvatek.

If you want to use one VATek device, use TSDuck version 3.38. If you want to simultaneously use several VATek devices, wait for the libvatek fix. In intermediate versions, VATek support is completely disabled.

@Ravnholt7507 I apologize for the delay due to my busy schedule recently, which has caused the task to remain incomplete. Once the issue is fixed, I will upload a version higher than 3.11 and pull a new version of the TSDuck source code to update the tsvatek plugin. I will inform you when it’s ready for functionality verification.

@lelegard Thank you for your suggestion. I will make the modifications based on your advice and complete the testing.