TBSDTV Community Forum

Hi.

When using OScam, MuMudvb, Phoenix card reader and the TBS6909 I get this error...
(dvbapi) ERROR: Read error on fd 18 (errno=79 Value too large for defined data type)
I have tried adding option dvr_thread=1

This error does not happen on the TBS6985 just on the TBS6909
Does anyone know how to fix it.....Its driving me mad.

hi ,

you can try to add the value of dvr_buffer_size.

dvr_buffer_size=40 or lagre .

same problem i have
tvheadend astra all give error
not buy this shit card
price/performance=0
if need 4 tuner model buy 6905

Yes seems to be a problem.
Tbs6909 add one stream it kicks out the error.
Used my old tbs6985 with 18 extra steams no error.
I heard it may be of congestion but thats not correct as i can steam 18 more with the tbs6985
Maybe i can get a replacement as its no good for streaming.

Also added the dvr_buffer_size=40 and played with the amounts but it did not help

nightshadow36 Wrote:Yes seems to be a problem.
Tbs6909 add one stream it kicks out the error.
Used my old tbs6985 with 18 extra steams no error.
I heard it may be of congestion but thats not correct as i can steam 18 more with the tbs6985
Maybe i can get a replacement as its no good for streaming.

Also added the dvr_buffer_size=40 and played with the amounts but it did not help

dvr_buffer_size=40
where add this options ?

Hello.

Sorry I made a mistake. I "put dvr_thread_buffer_size=40"

If I put "dvr_buffer_size=40" should that fix the error?

I have so many cards its complicated to change all the cables just to test again with out knowing.
Are you 10% 50% 100% sure adding "dvr_buffer_size=40" will fix the problem.
Its a productive server so I cannot just switch off to test any time.

Well i connected up the TBS6909 again and added the dvr_buffer_size=40 made no difference still the same error.
Also when it does work for a moment i get ecm times of 12000 on the 6985 ecm times are 90 so a big difference

nightshadow36 Wrote:Well i connected up the TBS6909 again and added the dvr_buffer_size=40 made no difference still the same error.
Also when it does work for a moment i get ecm times of 12000 on the 6985 ecm times are 90 so a big difference

The solution is very simple... and its not card related than more software related
Astra Cesbo due to the lack of multithreading at some point overload very quickly the dvr buffers.
Astra was also created/programmed to deal mainly with no more than 4 tuners and thats why with quad tuners is working ok

Depending on the number of cpu cores you have and the number of cards / tuners you use:

The solution is to launch multiple Astra instances

Example of best practice and usage scenario:

You have 1 x xeon cpu with 6 or 8 cores and 2 x TBS6909

launch one astra instance and setup 4 tuners (it will pick up one cpu core and 4 tuners)
launch second astra instance and setup 4 more tuners (it will pick up one cpu core and 4 tuners)
launch third astra instance and setup 4 more tuners (it will pick up one cpu core and 4 tuners)
launch fourth astra instance and setup 4 more tuners (it will pick up one cpu core and 4 tuners)

Simple math
4 astra instance x 4 tuners = 16 tuners / TP's all will work ok
4 cores busy with astra instances
2 or other 4 cores free for system and other needed stuff.

For correct balancing the resources consumption keep htop under your eyes and do not load on cores astra instances more than 85%.

Plain and simple guys

I have a duel CPU motherboard total 36 core 72 threads.
And i dont use Astra Cesbo. I am using MuMudvb.

I can start 2 different channels with MuMudvb no errors
When i start more than 2 i get the error in OScam