Widescreen (16:9) via Composite?

[Rob van der Does]

Just setup Solo2 --> Composite (yellow cinch, multi) --> Sony TV: when zapping between 16:9 & 3:4 services the TV-picture switches perfectly.

Maybe you could try the same (so without the modulator)?

[Timbo]

Sorry, I didn't get time to test it last night but just wondering which image you have installed on your Solo2 that works on the yellow cable?

Would the image have any bearing on the problem of WSS switching?

[Rob van der Does]

ViX 4.1.009
I think WSS is driver-driven, not E2; not sure though.

[Joe_90]

As Rob says - unlikely to be image related. It's almost certainly a setting error on your side somewhere. Try a direct connection. Won't (shouldn't) be the modulator, though as that just takes the video and audio and modulates an RF carrier with it. Usual issues with modulators are with the sound sub carrier being on the wrong offset spacing (PAL-G vs PAL-I as used in UK/Ireland).

[Timbo]

Just remembered, at home I am using a Scart to RCA adapter to convert into the Modulator.

One of these SCT-PPPSW-150x150.png - That's not going to matter is it? (I'm using one on the Sky+HD box too so that's exactly the same setup cable wise)

[Joe_90]

No - that adapter just connects the L and R audio and the composite pins from SCART to the phono sockets.

Just remembered, at home I am using a Scart to RCA adapter to convert into the Modulator.

One of these SCT-PPPSW-150x150.png - That's not going to matter is it? (I'm using one on the Sky+HD box too so that's exactly the same setup cable wise)

[Timbo]

Thanks for confirming!!!

[Timbo]

Another thought - will having a HDMI cable attached at the same time stop / suppress the WSS-flag from being sent down the analogue cable?

[Joe_90]

Another thought - will having a HDMI cable attached at the same time stop / suppress the WSS-flag from being sent down the analogue cable?

No - you're clutching at straws at this stage Just test a direct connection from the receiver to the TV composite AV input and play with the settings on the TV

[Timbo]

haha - I've been clutching at straws since I noticed I had this problem with the Vu+ Solo2 and not the Sky+HD box when using the same cables / ports etc.

[ronand]

What is the video output on the solo2 set to? HDMI?

[Rob van der Does]

As I said before: just use a single yellow cable to connect the box directly to the TV; then you're sure it's (not) the modulator.

[Timbo]

OK guys - ready for this?

Spent hours last night going through all the various possibilities with the Solo2 box, LG TV and cables. I used BBC One HD as the channel to test each scenario with as being a HD channel is by default outputted at 16:9. Apologies for the glare on the TV screen - it was a bit sunny yesterday evening.

Here are the results (basically, I still stand by my first post about WSS only seeming to occur when using a SCART cable (PIN 8??) and not when using the RCA cable):


LG TV Set to output ORIGINAL for all Ports = IMAG2014.jpg


Solo2 Information = IMAG2019.jpg


Test 1) Solo2 > SCART 21 pin cable > TV SCART SOCKET


Rear Connections on Solo2 = IMAG2017.jpg


LG TV Output = IMAG2016.jpg


RESULT = ALL WORKING OK AS EXPECTED


Test 2) Solo2 > SCART to RCA Adapter > Yellow RCA Cable > TV Yellow RCA Socket


Rear Conenctions on Solo2 = IMAG2018.jpg


LG TV Output = IMAG2012.jpg


RESULT = OUTPUT DISPLAYED INCORRECTLY AS 4:3 (black bars down sides)


Test 3) Solo2 > Yellow RCA Socket > RCA Cable > TV Yellow RCA Socket


Rear Connections on Solo2 = IMAG2010.jpg


LG TV Output = IMAG2013.jpg


RESULT = OUTPUT DISPLAYED INCORRECTLY AS 4:3 (black bars down sides)


HELP! Can anyone with it working on a Solo2 provide a backup image that I can try on my box? Or at least provide screenshots of their "A/V Settings" in Setup so I can copy them?

[judge]

Not that it might help, but if you want more people to reproduce, use a current image, not an old build.

[Timbo]

Forgot to mention that I thought it might be the Image so I installed the latest ViX image from www.openvix.co.uk - 4.1.009 - the issue still occured and the version of driver (kernel) was the same.