[ViX_Misc] lamedb

[FireballXL5]

I am using a Vu Zero with 2 dishes attached. One points to Astra 28.2 the other at Intelsat 907. The trouble I have is that there is a common lamedb file for both dishes meaning that any custom settings entered for Intelsat 907 are lost when I have to rescan and so they have to be re-entered. Normally this wouldn't be a problem, but with so many changes to the Astra platform editing the lamedb file has become a real pain. What would be great is to have a seperate lamedb file for each dish.

The IceCrypt box I have manages to do this in that I can re-scan Astra without it affecting any Intelsat 907 settings.

Thoughts anyone?
Cheers

 

[judge]

Can't you do what you require using the inbuilt ABM for your 28.2E channels?
Why use such an old build?

 

[Huevos]

Like Judge says, use ABM for 28E scan. It will not modify any parameters in lamedb that don't belong to the current scan, and nor should E2.

 

[Rob van der Does]

....and nor should E2.

Indeed. I have no clue what problem op could possibly have.
I also have different tuner configs and I'm glad there is only one lamedb....

 

[FireballXL5]

Hah! Well I didn't know that about ABM. It nearly works for me- MUTV shows as 4808 in the Sports menu. Thanks for your help.

 

[Rob van der Does]

But this has nothing to do with your original issue. ABM is just one way to 'scan', E2 has more ways to do so and none of them should give you issues (interference between satellites).

 

[FireballXL5]

But this has nothing to do with your original issue. ABM is just one way to 'scan', E2 has more ways to do so and none of them should give you issues (interference between satellites).

Ah but it does. To get Intelsat 907 to work changes need to be made to lamedb, this is done manually. I use a DiSEqC and have Astra off Port A and Intelsat off B and previously when changes were made on Sky I selected Menu | Setup | Service searching | Automatic scan. This finds all of the Sky changes but re-sets the Intelsat settings which then have to be edited.

And why such an old build? Well 166 works perfectly and frankly I don't consider it to be an old build and feel no need to keep updating the system potentially introducing new problems. I did try one of the "newer" builds but in the update it included a newer version of TSmedia which didn't work. Who needs this extra hassle? If it ain't broke...

 

[Rob van der Does]

The stone age wasn't broke....