Open-sasc-ng lock & multirec fix
| December 9th, 2008Ive seen alot of visits to this blog since my Mythbuntu post, and in particular search words like ‘2.6.27 open-sasc-ng’ are high up on the list.
My Mythbuntu backend have been stable and alot more responsive since I crawled up to 8.10. There have been issues tho, as the title suggests its been open-sasc-ng related. The problem was to locate the bugger. Which I seem to have found via slightly similar error messages.
My errors were random, all 3 tuners worked individually, and most of the time, they could all be utilized. I had certain channels I would get a lock on about 3/10 attempts when I jumped straight to its channel number. If they had lock issues, I could skip to a nearby channel(on same satellite) and jump back getting a lock.
Multirec did not work, it would initiate and record a few minutes on the ’second’ recording, then simply drop both, fantastic..
After countless patches, trials & cussing I came across a post giving similar(albeit not the same) errors. Since I had nothing to loose, I tried it.
Result? I have lock on all channels, multirec works, not a 0B recording since applied. Ive pushed all 3 tuners with multirec, its all good.
Now to the fun/annoying/ffs part.. the fix.. here’s the patch, but really, this you can do blindfolded..
Yes, you read right, a missing = …
Its been rock solid for 96hours on my box, and a friend of mine also confirmed it working on his DVB-C MythTV backend, he had similar lock issues on certain channels.
There is a ticket on the Open-sasc-ng trac, no idea when/if it will be fixed. The devs seem to focus on their own system, not giving us DVB lads a break..
So if this fixes your problems, do leave a message on the ticket above, they could use a kick in the arse. ![]()



