Continuity error repeating with excactly 4½ min interval (1 Viewer)

[pilehave]

Hi

Multiseat MediaPortal 1.8 with DVB-C through 50 mbit fibrebox with COAX output from router (IP-TV -> DVB-C).

No matter what I do with my cable signal, both increasing and decreasing signal (adjustable amplifier and resistance) my logs on the TV-Server shows continuity errors at excactly every 4½ minute. I therefore doubt that it actually is a signal error. Signal is also perfect on two regular TV-sets in my house.

Timeshift is on dedicated "drive" which is a 4 GB RAM-drive.

TVCard is Digital Devices Cine CT V6

All antennacables are triple-shielded with HF-shielded housings - in other words; it is not an installation issue.

TsWriter and TVService logs attached - please help

 

[RonD]

need wait for @mm1352000 to get an informed comment, but a couple things I would try if I had this problem.

1. use TV Server config and modify the filesize setting by a factor of 2, change 256 to 512, 512 to 256 etc. Does the time between errors change by a factor of 2?
http://wiki.team-mediaportal.com/1_...ation/TV-Server_Configuration/08_Timeshifting

2. put the timeshift on a good old fashion hard drive "HDD" and see if you still have problems.

 

[pilehave]

Good suggestions RonD, will try both of them tonight

 

[RonD]

not sure how you have timeshift setup, but 512MB/(4.5*60) = 1.9 MB/sec = 15.2 Mbps. I'm in the USA use ATSC, this is around the bandwidth used for a full bandwidth TV channel. Not sure what speed DVB-C uses, but wonder if the errors happen when one timeshift buffer/file fills and switches to the next file.

 

[pilehave]

Ok, changing file number or size for timeshifting didn't make any difference. Moving the timeshift to a physical drive hovever did!
Now it's been runinng 32 million ts packets without a single drop. Usually it would drop 3-4 packets for each 3.2 million packets.

So - since I like the idea of my RAM drive (and have been using it for 3 years) I think i'll look into alternative software than the one I'm using now which is Dataram RAMDisk.

I had no clue whatsoever that this could be the issue, so thanks for the input

 

[breese]

I'm using now which is Dataram RAMDisk

Very Interesting.... I am also running that same RamDisk... Hold old is the system / Ram? Possible you have a stick going bad?
I have put mine under some Very Heavy loads testing everything you can think of.... Now I am going to start looking into Speed References to and from it....

 

[pilehave]

System is based on an AMD E350 1.6 GHz board with picoPSU and 4 SATA drives + 2 USB-drives. Works really well and is ~ 25W on full load. About 3 years old I guess.

Could also be bad RAM, yes, will try other software and report back

 

[pilehave]

Currently using a 30-day trial of Primo Ramdisk Standard Edition and 25 million packets and no drops so far. Two things could have been wrong with previous setup;
- Image was corrupted somehow. Dataram RAMDisk loads a previously saved image of the disk on boot. Perhaps it was damaged somehow?
- Dataram RAMDisk handles file reading/writing differently than expected causing read or write errors.

If Primo Ramdisk works fine in the trial-period I think I'll use the $30 a 2-machine license cost.

 

[RonD]

I've never tried a ramdisk, just use a dedicated 2TB WD "green drive" for recordings and timeshift with up to 5 simultaneous recordings and watching 1 program. I figure there is not a big difference between disk WR/RD activity for recordings/watching and using the same drive, same type of traffic for timeshifting.

Have you looked at the ramdisk config setup for your original setup? Maybe some settings get messed up. Does the setup have a way to clear or reinitialize the disk image? Maybe just try doing a little ramdisk cleanup.