New Edision OS nino Pro Grey 1x DVB-S2X + 1x DVB-C/T2 Linux Enigma 2 Combo Tuner Digital Multi-Stream Receiver H.265 HEVC HD 1080p

el bandido

Member
Joined
Feb 25, 2009
Messages
111
Reaction score
125
Points
43
Age
61
My Satellite Setup
1.2 meter KU band
3.6 meter C band
Enigma2 Receivers
My Location
Atlanta, Ga. USA
Again,
There are a couple of code lines in some blindscan plugin versions that set all DVB-S transponders to FEC Auto. (Remarks about these lines suggest it was done to satisfy Vu+ driver issues)

And,
Any transponder that is logged with a FEC of 0 will return FEC Auto. This applies to both DVB-S and DVB-S2 transponders.

So it depends on the blindscan plugin version, and what the receiver actually logs as to what FEC will be displayed.
 

MCelliotG

Specialist Contributor
Joined
May 10, 2015
Messages
1,012
Reaction score
1,199
Points
113
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
Again, I know that!
What I continue to claim is that this behaviour is not right! In no case other than FEC 0 or unsupported parameters, the wrong ones should be returned. If the problem is with Vu, then that should be made specific for Vu and not affect other receivers that return the correct parameters.
 

stephan94

Specialist Contributor
Joined
Jun 30, 2008
Messages
853
Reaction score
1,275
Points
93
Age
66
My Satellite Setup
1.80 Channel master with 6 LNB KU KA C Band 1200 Laminas KU
Openbox SX6 and S3 Mini, Dr HD 15, GTCombo ; Octagon SF 4008 , TBS 6983
My Location
Bavaria
Here are some screenshots from 28 east (Astra 2) with filters set to ignore known transponders.
First MIS transponder I've ever seen on that satellite.

This transponder is not an MIS, it is a transponder in ACM and in continous; no receiver can read this data well, even TBS cards can not read them properly.12524v.jpg
He found this frequency, but it's a freqency with data, it's normal that the receiver can not read it.
 

stephan94

Specialist Contributor
Joined
Jun 30, 2008
Messages
853
Reaction score
1,275
Points
93
Age
66
My Satellite Setup
1.80 Channel master with 6 LNB KU KA C Band 1200 Laminas KU
Openbox SX6 and S3 Mini, Dr HD 15, GTCombo ; Octagon SF 4008 , TBS 6983
My Location
Bavaria
The frequencies shown on the screenshoot of huevos, are good.
the three frequencies 10935 V 22000; 11223H 27500 and 11780V 27500 are indeed frequencies in DVB-S,
none of these 3 frequencies is in DVB-S2.
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
Again, I know that!
What I continue to claim is that this behaviour is not right! In no case other than FEC 0 or unsupported parameters, the wrong ones should be returned. If the problem is with Vu, then that should be made specific for Vu and not affect other receivers that return the correct parameters.
Ok, I removed that clause for this receiver and rescanned. Transponder is 5/6.

Scannned 5 times. Twice the tuner returned FEC Auto, and 3 times it returned 7/8.

That clause was added years ago when the only two enigma boxes with blindscan were the Vu+ Ultimo and the ET9000. The Ultimo used to return 3/4 for everything. Anyway I have checked now with this box and it is also returning false FECs.

When the transponder exists in satellites.xml the correct FEC will show.
 

MCelliotG

Specialist Contributor
Joined
May 10, 2015
Messages
1,012
Reaction score
1,199
Points
113
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
This is a very different issue, if indeed the driver returns Auto in OSnino Pro. As far as I know, it does not, so why would that reflect on blindscan?
Now, the question is, what about DVB-S2? Screenshots I saw from OE-A all return DVB-S Auto!
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
No, the blindscan binary is returning wrong values.
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
Here is the output from the blindscan binary for vertical low on 28 east. So you can see it is nothing to do with OE-A. Obviously a weak link either in the hardware or blindscan binary.

Code:
< 48922.120> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '10729000', '22001000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.122> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '10758000', '22000000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.124> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '10788000', '22001000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.126> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '10817000', '22000000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.128> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '10847000', '23000000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_ON', 'FEC_3_4', '8PSK', 'ROLLOFF_35', '1', '-1', '0', '-1']
< 48922.129> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '10935000', '21998000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_7_8', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.131> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '10906000', '22000000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.133> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11038000', '21998000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_7_8', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.134> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11097000', '23001000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_ON', 'FEC_3_4', '8PSK', 'ROLLOFF_35', '1', '-1', '0', '-1']
< 48922.136> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11067000', '23000000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_ON', 'FEC_3_4', '8PSK', 'ROLLOFF_35', '1', '-1', '0', '-1']
< 48922.138> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11126000', '21999000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.139> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11225000', '23001000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_ON', 'FEC_2_3', '8PSK', 'ROLLOFF_35', '1', '-1', '0', '-1']
< 48922.141> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11265000', '27497000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.142> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11343000', '27499000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_2_3', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.144> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11386000', '29500000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_3_4', 'QPSK', 'ROLLOFF_35', '1', '-1', '0', '-1']
< 48922.146> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11426000', '27500000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.148> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11479000', '22000000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.149> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11508000', '23001000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_ON', 'FEC_2_3', '8PSK', 'ROLLOFF_35', '1', '-1', '0', '-1']
< 48922.151> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11538000', '22002000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.152> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11567000', '22000000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.154> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11597000', '21998000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.156> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11626000', '22002000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
< 48922.157> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11685000', '22998000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_ON', 'FEC_2_3', '8PSK', 'ROLLOFF_35', '1', '-1', '0', '-1']
< 48922.159> [Blindscan][blindscanContainerClose] cnt: 14 , data: ['OK', 'VERTICAL', '11656000', '21998000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_AUTO', 'QPSK', 'ROLLOFF_35', '0', '0', '0', '0']
 

el bandido

Member
Joined
Feb 25, 2009
Messages
111
Reaction score
125
Points
43
Age
61
My Satellite Setup
1.2 meter KU band
3.6 meter C band
Enigma2 Receivers
My Location
Atlanta, Ga. USA
As a test, I deleted all the transponders from a few satellites, followed by blindscans of the same satellites. My results were pretty much similar, except some DVB-S transponders returned a FEC that was not Auto. Some of the FEC's for the DVB-S transponders were obviously wrong.

I started watching some regular tv programs and noticed the correct FEC had returned to the DVB-S channels that were found in the blindscans. What is this????

So I deleted the channels for one of these test satellites, and rebooted the box. Another blindscan was done, this time without any stored channels for the satellite, and without any stored transponders for the satellite in satellites.xml.

What happened next is pretty simple: The DVB-S channels that had been scanned as Auto in the blindscan were assigned FEC's as the channels were viewed in the scanned channels list.

Bottom line is this:
Channels that are found on DVB-S transponders with FEC Auto will be assigned the FEC (if one is available) once the channel is viewed. You can clearly see the FEC change from Auto to what the FEC is supposed to be or to what the tuner thinks it is supposed to be. I see nothing wrong with this arrangement, but it would be nice if the FEC's were displayed correctly in the tp data. At the end of the day, this is a hundred dollar box, and I do not expect it to be perfect in this area.
 

el bandido

Member
Joined
Feb 25, 2009
Messages
111
Reaction score
125
Points
43
Age
61
My Satellite Setup
1.2 meter KU band
3.6 meter C band
Enigma2 Receivers
My Location
Atlanta, Ga. USA
I've done it based on symbol rate so the changes only affect transponders with symbol rates below 5000.

You can get the latest version of the plugin code for testing from github.
Code:
https://github.com/oe-alliance/oe-alliance-plugins/commit/b6c34079f11083f17fbb5f794d14d66ec16d63ef


Seems Perfect!
I think you missed putting the new variable in this line, so I added it:
abs(t.symbol_rate - k.symbol_rate) < (freqSyncTol*multiplier):

I added a debug line to print the tolerance, then the symbol rate.
Here is a 42 transponder scan with the debug results (Tolerance, Symbol Rate/1000)

---1364 BS---- frequency Sync Tolerance = 3 3080
---1364 BS---- frequency Sync Tolerance = 1 1875
---1364 BS---- frequency Sync Tolerance = 5 11601
---1364 BS---- frequency Sync Tolerance = 5 10832
---1364 BS---- frequency Sync Tolerance = 4 4166
---1364 BS---- frequency Sync Tolerance = 5 29999
---1364 BS---- frequency Sync Tolerance = 5 19165
---1364 BS---- frequency Sync Tolerance = 5 6660
---1364 BS---- frequency Sync Tolerance = 4 4200
---1364 BS---- frequency Sync Tolerance = 5 17917
---1364 BS---- frequency Sync Tolerance = 5 7501
---1364 BS---- frequency Sync Tolerance = 2 2850
---1364 BS---- frequency Sync Tolerance = 2 2550
---1364 BS---- frequency Sync Tolerance = 1 1860
---1364 BS---- frequency Sync Tolerance = 1 1550
---1364 BS---- frequency Sync Tolerance = 5 5000
---1364 BS---- frequency Sync Tolerance = 3 3715
---1364 BS---- frequency Sync Tolerance = 3 3328
---1364 BS---- frequency Sync Tolerance = 3 3000
---1364 BS---- frequency Sync Tolerance = 3 3000
---1364 BS---- frequency Sync Tolerance = 1 1809
---1364 BS---- frequency Sync Tolerance = 5 15000
---1364 BS---- frequency Sync Tolerance = 3 3255
---1364 BS---- frequency Sync Tolerance = 5 30001
---1364 BS---- frequency Sync Tolerance = 5 30002
---1364 BS---- frequency Sync Tolerance = 5 31353
---1364 BS---- frequency Sync Tolerance = 5 5000
---1364 BS---- frequency Sync Tolerance = 2 2803
---1364 BS---- frequency Sync Tolerance = 2 2416
---1364 BS---- frequency Sync Tolerance = 1 1667
---1364 BS---- frequency Sync Tolerance = 3 3255
---1364 BS---- frequency Sync Tolerance = 2 2400
---1364 BS---- frequency Sync Tolerance = 2 2400
---1364 BS---- frequency Sync Tolerance = 2 2150
---1364 BS---- frequency Sync Tolerance = 1 1660
---1364 BS---- frequency Sync Tolerance = 4 4800
---1364 BS---- frequency Sync Tolerance = 3 3500
---1364 BS---- frequency Sync Tolerance = 3 3400
---1364 BS---- frequency Sync Tolerance = 2 2876
---1364 BS---- frequency Sync Tolerance = 1 1167
 

stephan94

Specialist Contributor
Joined
Jun 30, 2008
Messages
853
Reaction score
1,275
Points
93
Age
66
My Satellite Setup
1.80 Channel master with 6 LNB KU KA C Band 1200 Laminas KU
Openbox SX6 and S3 Mini, Dr HD 15, GTCombo ; Octagon SF 4008 , TBS 6983
My Location
Bavaria
Hello,
When I look at the screenshots of huevos, it is with an openvix image, I can not find this image available for the OS nino pro.
When I read all the improvements you make to the blindscan, will they be available later in the different images or lights?
I am not a specialist in Enigma2, that's the reason for my questions.
Thanks for all the work you are doing .
 

moonbase

Small Dish Man
Joined
Mar 29, 2004
Messages
4,370
Reaction score
4,470
Points
113
My Satellite Setup
.
My Location
UK
If I understand it correctly, the commit created by Huevos and updated by El Bandido need to be added by a coder to the image distro?
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
Seems Perfect!
I think you missed putting the new variable in this line, so I added it:


I added a debug line to print the tolerance, then the symbol rate.
Here is a 42 transponder scan with the debug results (Tolerance, Symbol Rate/1000)
No, that is wrong wrong wrong. We are only trying to lower the frequency tolerance.
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
If I understand it correctly, the commit created by Huevos and updated by El Bandido need to be added by a coder to the image distro?
No. The plugin is built from the repo so the commit will be in the next build of every OE-A image.
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
Hello,
When I look at the screenshots of huevos, it is with an openvix image, I can not find this image available for the OS nino pro.
When I read all the improvements you make to the blindscan, will they be available later in the different images or lights?
I am not a specialist in Enigma2, that's the reason for my questions.
Thanks for all the work you are doing .
I built that image myself for my own OS Nino Pro, which is why it says "5.2.010.001(Experimental)" in the screen grab.
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
As a test, I deleted all the transponders from a few satellites, followed by blindscans of the same satellites. My results were pretty much similar, except some DVB-S transponders returned a FEC that was not Auto. Some of the FEC's for the DVB-S transponders were obviously wrong.

I started watching some regular tv programs and noticed the correct FEC had returned to the DVB-S channels that were found in the blindscans. What is this????

So I deleted the channels for one of these test satellites, and rebooted the box. Another blindscan was done, this time without any stored channels for the satellite, and without any stored transponders for the satellite in satellites.xml.

What happened next is pretty simple: The DVB-S channels that had been scanned as Auto in the blindscan were assigned FEC's as the channels were viewed in the scanned channels list.

Bottom line is this:
Channels that are found on DVB-S transponders with FEC Auto will be assigned the FEC (if one is available) once the channel is viewed. You can clearly see the FEC change from Auto to what the FEC is supposed to be or to what the tuner thinks it is supposed to be. I see nothing wrong with this arrangement, but it would be nice if the FEC's were displayed correctly in the tp data. At the end of the day, this is a hundred dollar box, and I do not expect it to be perfect in this area.
Blindscan just does a sweep of the band and saves what it believes to be the correct parameters of every transport stream it finds on the way. Those parameters just need to be "good enough" so they can be used by enigma to open that transport stream.

When I rewrote that plugin years ago I added the "syncWithKnownTransponders" function to try to clean up the data returned by the blindscan binary, but that only works if the transport stream details are already in satellites.xml.

So if we want perfect output how can we get it? We have to read the SI tables of each transport stream we find. This means tuning the receiver to the transport stream, reading the SDT actual, finding the TSID of the current transport stream, reading the NIT, finding all the tuning parameters that correspond to the current TSID, and then using that data as the final parameters for each transport stream. (This assumes the SI tables are correct. For some transport streams, such as the MIS multiplexes on 5 west the data is completely wrong.)

So the question is, is this really necessary or is the data "good enough" and we are just being obsessive? Adding code to read each transport stream could be done but takes about 10 seconds per transport stream.
 
Last edited:

MCelliotG

Specialist Contributor
Joined
May 10, 2015
Messages
1,012
Reaction score
1,199
Points
113
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
Or make it an option. This way a DXer has full control of what they need. Speed over accuracy or vice versa!
Just think that if a DXer uses a pro PC card, would they want unknown auto values on a found transponder? Why would that be obsessive when they use a capable set top box?
One more suggestion would be to add optional additional scan ranges, for satellites that operate on different bands but not the whole spectrum. This could be useful for satellites such as 3W.
 

Huevos

Satellite Freak
Joined
Sep 11, 2008
Messages
6,036
Reaction score
1,273
Points
113
My Satellite Setup
57E to 58W, C-band and Ku, DVB-S2, 4:2:2 and blindscan.
My Location
38.5ºN, 0.5ºW
Or make it an option. This way a DXer has full control of what they need. Speed over accuracy or vice versa!
Just think that if a DXer uses a pro PC card, would they want unknown auto values on a found transponder? Why would that be obsessive when they use a capable set top box?
Ok, but that needs a lot of extra code and a reader (.so file) for the transport stream.
One more suggestion would be to add optional additional scan ranges, for satellites that operate on different bands but not the whole spectrum. This could be useful for satellites such as 3W.
You can already filter a range, but not a group of ranges. Easiest way to handle that would be scan the lot and run a filter afterwards. But obviously someone needs to know those ranges and be able to add them. Putting them all in an xml file would probably be a good idea for that.
 

World-of-Satellite

Regular Member
Joined
Jan 26, 2010
Messages
283
Reaction score
36
Points
28
Age
53
My Satellite Setup
VU+ Ultimo 4K
GiGaBlue UHD Qaud 4K
GiGaBlue UHD UE 4K
VU+ Zero 4K
My Location
UK
OpenViX image for the Edision OS nino Pro is now available for download HERE.
 

scopus

Specialist Contributor
Joined
Mar 25, 2005
Messages
3,174
Reaction score
3,807
Points
113
Age
59
My Satellite Setup
Primesat/Famaval 1.8 PF C/ku/Ka, Octagon SX8HD1, SX88, Openbox S3 Mini HD-V8S Freesat V7 HD-V8 Finder, Amiko A4K Combo, Satlook Colour HD Spectrum, Sansui A909 Amp and BOSE Acoustimass speakers for the audio.
My Location
Staffs UK
Top