[ViX_Misc] New transponder to satellites.xml

[Orlandox]

Hello,

is it possible to add new transponder to satellites.xml to the next version of the image ?

 

[Huevos]

Satelites.xml is updated automatically weekly based on lyngsat content.

 

[Huevos]

Was already added by the last update 2 days ago.

https://github.com/oe-alliance/oe-a...0e65c883e3bfffbbf311ec9258a672bd5796b694R2333

 

[abu baniaz]

And users can update to it using the xml update plugin pre-installed in OpenViX without waiting for image to be updated.

 

[gh_n]

Hi
New :
Amos 3/7 at 4.0°W
11604 V DVB-S
27500
5/6
Yes Packages

 

[Huevos]

Hi
New :
Amos 3/7 at 4.0°W
11604 V DVB-S
27500
5/6
Yes Packages

we don't add adhoc entries to satellites.xml. The file is created automatically.

 

[ArloGuthrie]

If the question is. If an option can be added. Be aware that any .xml updates will almost certainly wipe your previous satellite.xml file.

Case in point. My satellites.xml is tailored by me to include only satellites that I am able to receive in my region. In the USA and from 34W to 131W. None others.

Further. Blindscan results that show new transponders for wild feeds (games, events) are added to the existing satellite section in the .xml.
This way instead of doing continuous blindscans. Opening Signal finder and finding that a saved tp has become active. Shows if there are any active channels. Some transponders may be "alive" but show no channels.
And then when the uplink becomes active. Channels populate.
For, let's say, a football game. As cameras are setup around different areas of the arena. "Camera 1", "Camera 2", "Sideline Packers". They suddenly appear in the channel. Or Service. List.
It's fun!

Different transponders and different encoding. Symbol rates, etc. Might be only a one-shot for the event. Or they can be repetitive.
And only if you believe or are curious if any new tp's are "turned on" a particular satellite. Then you can perform a blindscan.

I rarely and if at all perform a channel scan in blindscan. Instead, search for transponders. Either new only or override those already present.
Then in notepad++, open both satellites.xml and the blindscan file in /tmp.
Move the /tmp file to a new instance. Move and resize the windows.
Enable show all formatting characters in ++. And definitely enable the XML Tools plugin.

When I insert the new tp. Plant my cursor at the end of a line at the LF symbol. Smack <enter>.
Pay 100% attention to the spacing before the new line. I use E-Channelizer for channel edits. And it places four spaces. The stock .xml includes double tabs before the tp data. Don't know exactly why,
BUT. You Must stay with the formatting convention. It there are spaces. Use them. Four in my case. Backspace four (or two if that's the case) Hit the spacebar 4 times. Copy only the data from the blindscan line. And paste it into the new line in the satellites.xml. Continue until you're satisfied. Then before saving the file. In noteepad++ click the plugins tab. Click XML Tools. Click Check xml syntax now. If you get no errors. It's safe to save in your FTP program (Filezilla).

After. I always do anyhow. Shut the receiver down cold. Deep standby. Then start it up. There may be a slight delay as E2 is doing some house cleaning. I don't know what's going on in the background. The more blindscan lines you add in satellites.xml. The delay seems a bit longer.
Then you will see your saved transponders when you open your scanning options.
You must save the satellites.xml file off of the receiver. EHD, FTP to your pc. For me it's in C:\Temp\ViX Sats.
Because the very next update will replace it with the file in the update. Simply drag the backup to /etc/tuxbox. Cold boot the receiver. And you're golden.

For me. And I know that rallying for a useful option here is not easy. A better option. Like the disable background scanning. Because editing all of your channels from "Program 1, 2, 101, etc" to the proper names and suddenly finding they have been all renamed to original sucks. A "Disable satellites.xml updating" option would be more useful.

Sounds complicated? Not so much once you try it. And finding those Sunday games is a whole lot faster.
Is the source for the .xml update from satellites-xml.org? I dunno.

 

[abu baniaz]

If you have your own XML file, put it in /etc/enigma2.

Why edit the system version which gets changed on updates.

 

[Huevos]

If the question is. If an option can be added. Be aware that any .xml updates will almost certainly wipe your previous satellite.xml file.

Case in point. My satellites.xml is tailored by me to include only satellites that I am able to receive in my region. In the USA and from 34W to 131W. None others.

Further. Blindscan results that show new transponders for wild feeds (games, events) are added to the existing satellite section in the .xml.
This way instead of doing continuous blindscans. Opening Signal finder and finding that a saved tp has become active. Shows if there are any active channels. Some transponders may be "alive" but show no channels.
And then when the uplink becomes active. Channels populate.
For, let's say, a football game. As cameras are setup around different areas of the arena. "Camera 1", "Camera 2", "Sideline Packers". They suddenly appear in the channel. Or Service. List.
It's fun!

Different transponders and different encoding. Symbol rates, etc. Might be only a one-shot for the event. Or they can be repetitive.
And only if you believe or are curious if any new tp's are "turned on" a particular satellite. Then you can perform a blindscan.

I rarely and if at all perform a channel scan in blindscan. Instead, search for transponders. Either new only or override those already present.
Then in notepad++, open both satellites.xml and the blindscan file in /tmp.
Move the /tmp file to a new instance. Move and resize the windows.
Enable show all formatting characters in ++. And definitely enable the XML Tools plugin.

When I insert the new tp. Plant my cursor at the end of a line at the LF symbol. Smack <enter>.
Pay 100% attention to the spacing before the new line. I use E-Channelizer for channel edits. And it places four spaces. The stock .xml includes double tabs before the tp data. Don't know exactly why,
BUT. You Must stay with the formatting convention. It there are spaces. Use them. Four in my case. Backspace four (or two if that's the case) Hit the spacebar 4 times. Copy only the data from the blindscan line. And paste it into the new line in the satellites.xml. Continue until you're satisfied. Then before saving the file. In noteepad++ click the plugins tab. Click XML Tools. Click Check xml syntax now. If you get no errors. It's safe to save in your FTP program (Filezilla).

After. I always do anyhow. Shut the receiver down cold. Deep standby. Then start it up. There may be a slight delay as E2 is doing some house cleaning. I don't know what's going on in the background. The more blindscan lines you add in satellites.xml. The delay seems a bit longer.
Then you will see your saved transponders when you open your scanning options.
You must save the satellites.xml file off of the receiver. EHD, FTP to your pc. For me it's in C:\Temp\ViX Sats.
Because the very next update will replace it with the file in the update. Simply drag the backup to /etc/tuxbox. Cold boot the receiver. And you're golden.

For me. And I know that rallying for a useful option here is not easy. A better option. Like the disable background scanning. Because editing all of your channels from "Program 1, 2, 101, etc" to the proper names and suddenly finding they have been all renamed to original sucks. A "Disable satellites.xml updating" option would be more useful.

Sounds complicated? Not so much once you try it. And finding those Sunday games is a whole lot faster.
Is the source for the .xml update from satellites-xml.org? I dunno.

Channel names are nothing to do with satellites.xml. They are stored in lamedb.

Also, like Abu mentioned, put your satellites.xml in /etc/enigma2 and it won't be touched by updates.

 

[ArloGuthrie]

Abu. I wish this were 100% true.
Unfortunately whatever brain trust is in charge of an image release has wiped my .xm in /etc/enigma2.
Setting it to read only causes an update to puke all over the place
And therefore a backup of my image, etc. and periodic save of the 'custom' file is assured it will be available.

Huevos. Although as many have discovered and a not-in-your-face thing. Disabling background scanning is desirable. In situations where as my example would be channel listings of actual scans versus those in satellite charts
Where Program 1,2.....Or the actual frequency and sid (in hex) is displayed and a channel editor is used to properly name them. Forget to tick disable background scanning. You'll be reloading your channel list for a hopefully saved lamedb file from your channel editor du-jour.
It's really no biggie. You do it your way, I'll do it mine. As long as I don't experience a string of garbage if I ask for help. I appreciate sincere advice any day of the week. Always.

 

[abu baniaz]

An image release does not have one in etc/enigma2. If you flash a new image, you have to restore your personal items. ViX creates a settings backup by default if you flash using image manager. The whole of /etc/enigma2 is backed up. Even performing a software update creates a backup just in case things go wrong and you need to flash an older image.