Jump to content
SpesoftPinballXConvert-It

RIP-Felix

Elite Member
  • Content Count

    1168
  • Joined

  • Last visited

  • Days Won

    18

RIP-Felix last won the day on August 2 2018

RIP-Felix had the most liked content!

Community Reputation

219 Excellent

About RIP-Felix

  • Rank
    Most Appropriate Profile Pic

Profile Information

  • Gender
    Male
  • Location
    USA

Recent Profile Visitors

1771 profile views
  1. RIP-Felix

    The Fastest Xbox of All Time

    That's actually pretty legit. I've thought about doing that with an OGXB. Set that bad boy up with GameEX, steam, retroarch, and keep a wireless mouse and keyboard handy. I likes it.
  2. I like the idea of "GAMEFLIX", if you will, It just can't compete with retroarch IMO. It is good to see that Nintendo is starting to realize the value retro games still have, instead of neglecting them. It would be nice to see a more robust library of games from across many systems. Not having to navigate the virus laden basements of the internet for roms is the biggest appeal. BUT! Does nintendo have run-ahead latency reduction like retroarch does? Nope. I don't think I'll be replacing RA anytime soon.
  3. And we're heading down that same path. Scary!
  4. A very small percentage of women coming forward are lying. That said, defamation law needs to be adjusted to include social media. The burden of proof seems to be on the one accused to prove their innocence - in the court of public opinion. Even if they can win a defamation counter-suit, in a legal courtroom, the social consequences of the accusation are worse than the penalty of defamation. It's unlikely to happen if your a descent person, but I just stay clear of social media as much as possible regardless. Seems wrong to judge others through a phone or a single news piece.
  5. Remember that freedom of speach is a constitutional right that only protects you legally, not socially. And it doesn't cover seditious speach or that which incites to violence. In the case of Snowden or publications releasing classified documents, it shouldn't cover them if it leads to the death of an informant or operative. If you have access to sensitive information, you have a responsibility to protect it, and are culpable if your careless action gets someone killed. Classifying shouldn't be used to cover up crimes, but it always has been. Hense whistle blowers. Again it's a balancing act between oversight and protecting sensitive information. It's a battle between privacy and security. The potential for abuse is ever present. You can still be convicted in the court of public opinion. Just because you can't be legally deprived of your freedom, doesn't mean there aren't social consequences. Say something insensitive or stupid, even if it was an honest mistake you apologize for, and it could ruin you socially - even if there was nothing illegal about what you said. People are too quick to judge and too slow to forgive nowadays.
  6. I do agree with what you're saying, actually. When I got alexa I was expecting more. But the stuff I use it for is a nice convenience, especially at work. My situation may be different than yours and her limitations might make it not worth the risk for you. It's not good to just throw caution to the wind, but we cant live under a rock either. Its a ballance. A personal one. Draco's right. This is just a spirited exchange. No ill will on my part. I too really dislike the trend of privacy mining. it's frustrating that no one seems to take it seriously. I'm just making the point that I have caved in a little. I'm not the only one and unless the trends or laws change, then we have to accept increasing privacy liability.
  7. The point is, I use the services I want. I accept the privacy policies accordingly. I may not like them, but I accept them if I want the service enough to take the risk. Otherwise I don't. Many people don't and that's good, because it makes companies respect privacy concirns in order to earn more users. True, there are alot of sheep. Probably so many that companies will do fine regardless of the policy. So unless I want to live under a rock, or go to extraordinary lengths to protect my security, I have to accept that privacy is dead.
  8. Most people relinquish some security for convenience. We can't all have a moat filled with electric eels and hippopotomus', steel reinforced concrete bunkers with 10foot thick walls and nuclear blast proof war doors. Probably more than the expense, the inconvenience of living that way is untenable. While it's surely less secure, a deadbolt suits my needs. If that doesn't cut it, law enforcement and community will - for the greater number anyway. We form community and Law for the purpose of security and privacy. That's your best chance of survival in a disaster, seek out others and work together (not that lone wolf crap Hollywood likes to dramatize). Sure, technically echo devices could be used to "listen" in the home. TV's and appliances are starting to go down this path now too. My new TV just made me agree to their TV analytics as a precondition of use. What am I going to do, take it back? Nope, because there isn't much I can do about that. It seems everyone is making us implicitly agree to their privacy policy by continued use. What exactly does my TV have access to? Can it send video of whatever is displayed on it? My gaming consoles? Or computer? Do I just have to "trust" this is not a very likely privacy liability? Sort of. We don't have to "trust" it wont be used in that way, we have to make it not worth the penalty. Law is the deterrent. Being completely normal and uninteresting is your protection. The litmus test is the smart phone sitting in your pocket. It goes with you everywhere, has forward and rear facing cameras, biometrics, accelerometers, wifi and cellular network connections, as well as GPS. If you use a smart phone, you're like most people - willing to sacrifice some security and privacy for convenience and other services. How is Alexa different?
  9. RIP-Felix

    Zero input Lag in Retroarch?

    I got some input lag numbers from my TV using a GoPro shooting @ 240 FPS. Methodology: Times in milliseconds represent the amount of time it took for Mario to jump after my finger hit the bottom of the button. The number of frames from ten jumps were averaged to obtain the results. Each frame is 1/240th of a second, or 4.166ms. Note, I do not have an LED wired to light up when the controller registers the button press, so the results are not as accurate as they could have been. The CRT results used an actual North American SNES and physical copy of the game. The VIZIO TV tests used Retroarch on my windows 10 HTPC, with and without run-ahead enabled. I also included the SNES Classic results for comparison. Results are organized by the lowest to longest input latency. Results: Super Mario World Jump Test. 50ms = Original SNES on CRT with wired controller 70ms = Retroarch w/Run-Ahead latency reduction set to 2 frames, VIZIO 55P-F1 via HDMI5 low latency port w/Game mode on, [email protected], Wired X-Box 360 controller. 74ms = Retroarch w/Run-Ahead latency reduction set to 2 frames, VIZIO 55P-F1 via HDMI5 low latency port w/Game mode on, [email protected], 8BitDo SN30Pro wireless Bluetooth controller. 75ms = Original SNES on CRT with 8BitDo SN30Pro Wireless blutooth controller 83 ms = SNES Classic, VIZIO 55P-F1 HDMI5 low latency port w/Game mode on, and wired controller 102 ms = SNES Classic, VIZIO 55P-F1 HDMI5 low latency port w/Game mode on, and 8BitDo SN30Pro wireless Bluetooth controller. 133ms =Retroarch w/o latency reduction, VIZIO 55P-F1 via HDMI5 low latency port w/Game mode on, [email protected], and 8BitDo SN30Pro wireless Bluetooth controller. Unfortunately the component/composite port on my VIZIO 55P-F1 does not support 240p. It only accepts 480i and above. I don't have an OSSC yet, so I can't compare the original SNES on my modern TVs. I have not tested a wired controller on the PC yet, but am curious to see if it can match or beat the 50ms I measured for wired CRT result.***EDIT*** Just added the results for a wired x-box 360 controller, it only shaved 5ms off the time. I suspect that there are just more electronics in the way. Trying various USB ports (I used a USB3 port on my PC) might make a difference, or various USB controllers...I don't know. Discussion: The HTPC on a modern TV equaled the results on a CRT, with a wireless controller! That's a mind blowing result! Also of note is the latency without run-ahed. 133ms is a very noticeable amount of lag. That is what I've been noticing and having trouble accepting all this time. The 8bitDO controller adds about 22ms. The difference between 50ms (wired controller) and 75ms (wireless controller) playing the original with the CRT is just barely discernible to me. It's not distracting and very playable, but speed runners would likely prefer the least lag possible (OG SNES, wired controller, and CRT = fastest and easiest combo). I notice a bit of lag when playing on the SNES classic with the 8Bitdo controller, so more than 85 ms is my limit. That's why 133ms is unacceptable. The extra 3 frames of lag makes the difference from enjoyably playable and "why am I so bad at this. I must be rusty." Surprisingly, the SNES Classic Edition is quite good (wired), even without run-ahead latency reduction, and it performs admirably with an 8bitdo controller. It's not quite as enjoyable with the extra frame of lag, but it's fine for casual nostalgia. Lastly, I wanted to mention that the jump test has more lag than you would think. I noticed that Mario doesn't jump immediately. If you hold a shell and release the button to kick it, that action happens about 1 frame (16.6ms) faster than a jump command. That must be programmed into the game. So all of these input lag times are about a frame behind the real input latency.
  10. ouch...I'm intellectually and emotionally conflicted on this one. I have 4 echos...and like them. I knew off the bat they were collecting more than just my responses and could be abused. I guess I wanted the convenience of automating my lights, music, and timers. I'm the first to admit my total hypocrisy. I'm outspoken about hating data mining and analytics, while inviting smart bulbs and echo spying devices into my living/bedroom. I think the reason this one is so hard for me, is that I really do like the services voice recognition provides. It's more convenient than a remote or app for controlling lights. "Alexa, bedtime" and the lights go off. "Alexa, wake me up at 5:30" and she sets an alarm. "Alexa, set a timer for 4 minutes" instead of navigating the menu to set a timer on the microwave. "Alexa, resume audiobook" and she resumes Ready Player One on Audible where I left off in my Car via bluetooth to my phone a few minutes earlier. "Alexa, play electronic for studying on Pandora", "Alexa, how do you spell [insert that word you can't get close enough for spellcheck to recognize]", and so on... It's just way more difficult to give up. I have no desire to view more relevant ads in Firefox, so I can easily block them. But alexa is different. I like what she offers me...But more than privacy? Sigh... I have a hard time believing it's really that bad. While there exists a potential for abuse and human error. Emotionally, I want to believe Amazon is sincere in their desire to respect user Privacy. Intellectually, I'm not naive enough to believe they won't sell us out. Having said that, however...and this is going to be bias by my desire to keep using echo devices...I doubt anyone is actually listening outside the times it thinks it heard the wake word. While it may technically be possable to activate recording, it would require someone delibratly breaking the law to do so. I'm not likly worth the effort, so I'm not too worried about it. I agree with one of the readers who commented, "if you ask alexa for a weather report while having sex, I think the privacy implications should be less of a concern than the relationship implications." Another commenter pointed out that Apple store less data, keeping siri recordings for a period of 6-18 months, and anonymizes it. Amazon, by contrast, stores non-anonymous user data and keeps recordings for an indefinite period of time. So, I guess the lesson is it's prudent to choose an assistant from a company with better privacy policies.
  11. RIP-Felix

    Killer Instinct for WIndows 10

    "Offers in app purchases" I passed when I saw that. Maybe I'm just being prejudice, but that ruins the game for me. Maybe it's not all that bad, I've just heard horror stories about other classic titles being ruined by free to play mechanics. Why sell a game for a one time $60 when you can give it away for free and make millions of microtranactions.
  12. RIP-Felix

    Zero input Lag in Retroarch?

    Yeah, I didn't really notice lag as much before. I was playing more modern consoles and emulating old games for convenience. More recently I got nostalgic for the authentic experiance and I started pulling out my old consoles and hooking them up to a CRT. I immediatly realized how much more fun these games are when they respond as intended. Zelda felt noticeably more responsive, which makes Darknuts much easier to defeat. They are a PITA on emulation, especially blue ones. Now, it doesn't have to be. I think it's like becoming nose blind. You don't notice it until you come back from vacation.
  13. RIP-Felix

    Zero input Lag in Retroarch?

    I came across this while researching input latency for my gaming setup. I just bought a VIZIO p55-f1 for it's dedicated low latency HDMI5 port touting 10.5ms 1080p120Hz. While it's not as good as 240Hz computer monitors, it's the best you can get for a big screen at the moment. Price was good too. I'm still waiting on it to be delivered, so I'll have to test on my current TV for now. Now, I wasn't expecting a miracle. I figured it might help but at the cost of something. I didn't believe it could compare to a CRT. No way. I just DL'ed Retroarch 1.7.5 and it's frack'n awesome. When I turn the Run-Ahead Feature on and follow the steps in the video above, it takes 2 frames to completly eliminate the lag, but otherwise I haven't noticed any performance hit in the few minutes I've tested it. It does cause audio glitches, but the second instance feature fixes that (this may be a problem for slower devices like the Pi or classic consoles). WOW...I'm blown away! It feels like I'm playing on my CRT. I Know because I have one right underneath my big screen comparing the same game side-by-side.... ...Gasp! Let me put this another way: I have my Super Mario World on my OG SNES running on a CRT. I am using 8BitDo bluetooth controllers for both. I'm using the DIY for SNES controllers on my OG, but I'm using the SFC30PRO for the PC. Same lag for each. I notice very little lag for the OG SNES with the bluetooth, it's acceptably low IMO. I did break out the OG Super Famicom Controller just to be sure (My favorite). It does feel more responsive than the 8bitdo wireless controller. I mean it's not huge, but it's just to me (it could be the placebo effect, I'm not sure). I just spent $700 on a TV prioritizing low input lag. With one update Libretro redifined the limits of what I thought was possable via emulation. I thought we were going to have to accept that emulation take time to process, framebuffer, and etc. Add that to modern TV's inherent Input lag and I didn't think CRT like performance was possible. This is a GREAT feature!!! Easily one of the best features Retroarch has released yet. Now NES runs ok on retropie, maybe even the classic consoles, but Genesis and SNES don't fair so well from what Ive read. Maybe there will be room for improvement. I shot some 240Hz video to estimate input lag, but I don't have the numbers yet.
  14. RIP-Felix

    Getting a Better Picture from Retro Consoles

    N64 Update: I just got in on the December batch for an UltraHDMI kit. From preorder to shipment is 3 - 5 months, so I'm not anticipating having it in hand sooner than March or April. I'm not paying those e-bay scalpers $400+ for a pre-moded console. $166 for the kit shipped, but I'll have to solder it in myself. I'm confident enough with my soldering tools and ability. Things I want to investigate: Compare the RGB mod to the ultraHDMI on my new Vizio P55-F1 TV, since it has a component input. I imagine it depends on how well the Vizio upscales 15kHz signals (240p/480i) to 31kHz (480P), if at all. I'm torn on getting an OSSC. The OSSC doesn't give me Composite or s-video like the RetroTINK, but they suck compared to component anyway. The SNES, RGB moded N64, and Dreamcast stand to benefit from the OSSC, so that's good incentive. If the Vizio can't handle 240p/480i then I'll get the OSSC for sure. I'm curious about the lag performance between inputs (HDMI ports 1-4, low latency HDMI port 5, and strait up Component). I also want to see how removal of the 1st and 2nd pass of antialiasing looks. I've already disabled the 1st pass through an IPS patch on the Everdrive. The second pass is automatically applied by the N64's hardware and only deblur removes it (either the advanced RGB mod or ultraHDMI). Instead of magnifying the smear, I want AA and/or scanlines applied after a lossless upscale. The UltraHDMI does this well. In direct mode it adds zero lag, as it just upscales 240p/480i to 480p, but the deblur, further upscaling to 720p/920p/1080p, scanlines and other options aren't possible without adding a frame of lag (~16ms). So that's why I wanted a TV with the lowest possible lag to begin with. 15ms (Vizio HDMI5 input lag) + 16ms (ultraHDMI) = 31ms, still under the safe limit where lag may become noticeable (using a wired controller).
  15. RIP-Felix

    Getting a Better Picture from Retro Consoles

    The Television, Part 1: Selection I'm trying to get the best experience out of my gaming consoles, so the TV is probably the biggest factor. For retro gamers there are 2 schools of thought, CRT and Modern TVs. In my setup I use both. I keep a late model Sony Trinitron around for all my retro consoles. Sure it's nostalgic to see the games the way they were meant to be viewed, but that's not the main advantage. CRTs have no lag. CRT's don't do any sort of image processing, they just take the analog input and display it at the speed of an electron gun exciting phosphors (practically instantaneously). Modern TVs have to take a variety of input signals and upscale them to the screens native resolution. They also do other advance image processing to make thing look better. The main difference is they trade input response for image quality. All that image processing takes time, introducing input lag. As a retro gamer, I can't stand lag. When I replay old games on a CRT, it's way more enjoyable. After all, the games were designed to be challenging when Mario jumped exactly when you told him to! What about game mode you ask? That's where things get tricky. Game mode turns off all those fancy image processing features and just upscale the image to the TV's native resolution, greatly reducing input lag. However, it can't remove all of it. Theoretically, a modern display can't match a CRT in lag performance. Practically, modern TVs have come a long way at reducing input lag, to the point where it should not be perceivable. If you combine a low latency TV with the OSSC or RetroTINK then image fidelity doesn't have to be a problem either. They can accept retro consoles (with mods & adapters) outputting 240p and 480i/p. They line double or triple it and spit out 480p/720p Via HDMI, a signal the TV can properly handle with minimal processing in game mode. They can do this almost lag free. The first step however is choosing the right TV. There are so many great Modern TV's out there. So what's important to look at for as a Retro Gamer? Here's my take. Input latency. I've read differing opinions about where the limit for noticeable lag is. As far as human reaction time is concerned, 101ms is the current world record. But that's from perception (from eye to the brain) to reaction (from brain to muscle contraction). So lag perception should be less than that. It's probably not correct to assume that perception takes the same time as nerve conduction + muscle contraction. So I can't just say that perception is half of reaction time (50ms). So lets go off something more concrete - framerate. 24Hz (FPS) is about the slowest frame rate possible before you start to see individual frames. That deals solely with perception, so it's the better number to go off. 1/24 = 0.0416s or about 42ms. Wireless controllers adds lag too. From what I've read that's less than 8ms. Subtracting that should give me the maximum input latency a TV can have before it's noticeable by a gamer sensitive to lag (42 - 8 = 34ms). From what I've read about TV input lag, less than 30ms is considered unnoticeable. My calculation closely agrees. So I'm assuming 30ms is safely unnoticeable. Above that, I've read that increases in steps of 15ms are noticeable. So a TV or setting with an input latency of 45ms would be just noticeable if you're sensitive. Refresh Rate and Response time. These affect the smoothness and clarity of the image during fast pace action, like sports or games. High refresh rate and fast response time will remove ghosting and image trails. It also gives rise to the "soap opera" effect. Before my plasma died I had become used to it. I didn't novice it after awhile, but my Dad did when he came over. I lost it when I bought that cheap TCL Roku TV. I now see it as a sign of a quality picture, but understand why some may not like it at first. IMO, it make sports and fast pace action a better experience. Burn in. Since I use my TV as a computer monitor there is an increased risk of burn in. Static screen elements like huds in games, or browser tabs in Firefox, can permanently damage screen if left on for long periods, which I often do. I generally leave my screen saver off, because it tends to interrupt my emulation gameplay if I take a break. Then I can't regain focus without closing, losing where I was in the game. So I would be wise to choose a TV not at risk for Burn in. Black performance. My TV will not be placed in a room with lots of light that can wash out the screen. So brightness is less important to me than good blacks. The cheap TCL roku TV I replaced my plasma with has poor blacks. The backlight changes brightness constantly to provide appropriate contrast, but in a dark room watching content with black bars above and below, the flickering is almost seizure inducing. It's quite distracting, but if I turn off the auto-brightness feature then dark details get lost and gradients band more than they already do. My plasma had great blacks and I never noticed gradient banding or lost details in dark areas. I greatly desire good blacks again. Analog inputs. I'd like some legacy inputs to make connecting retro consoles easier. Component and Composite are much appreciated. This is not an absolute need, the OSSC or RetroTINK can accept retro consoles (with adapters) and output clean HDMI the TV can handle. Also, with less to process for upscaling, input lag decreases. So it may be better to use these solution instead. I recently redecorated a guest room at my Dads place and want to put my TCL roku TV in there. So now I'm ready to upgrade my TV for Retro Gaming! I narrowed down the list to three candidates: LG OLEDB8PUA. Pros OLED screen provides an infinite contrast ratio. Blacks are pure. This is the best picture quality possible for my needs. It also has a very consistent low input lag profile, 21ms for most resolutions and scenarios (SDR vs HDR). Outside of game mode, it has a surprisingly low latency compared to other TVs (42ms for [email protected]). That might be noticeable to someone sensitive to lag, but it's better than any other TV available and they can always turn game mode on. This TV's lag profile is ideal for a wide range of gaming scenarios. Native 120Hz Refresh Rate Cons OLED is at risk for Burn in. It uses many features to reduce the risk, but is really intended for use as a TV where it will display variable content for a few hours at a time, not a computer monitor. This isn't a problem in modern LED TVs. While the input lag is acceptably low and consistent across a wider range of resolutions and scenarios, it isn't the lowest possible. Since I want to use this display for retro consoles, achieving the lowest possible input lag for 1080p SDR is my primary goal. No Component input. No Roku features Built in (this isn't really a big deal) Price is about $1000 more than the LED alternatives. VIZIO P55-F1 Pros LED screen provides no risk of burn in. Blacks are great on this LED, thanks to local dimming. This is the best black performance possible besides OLED. Has a dedicated low latency HDMI port (HDMI5) which provides the lowest input lag of any TV, 1080p120 at just 10ms. HDMI5 doesn't support HDR and only accepts YUV4:2:0 due to it's bandwidth limitations. It does lower latency for 1080p60 and 4k60 to just 15ms, however. That makes it faster than OLED for my primary goal. The other ports support HDMI2.0 at ~27ms, about 3-4ms more than the OLED. While the lag profile is less consistent than the OLED across a wide range of gaming scenarios, all scenarios experience less than 30ms of lag in game mode and should thus be unnoticeable. Has Component input. Cost is about $1000 less than the OLED Native 120Hz Refresh Rate Cons Not as good at blacks as an OLED. Outside of game mode, it has a fairly high latency that will be noticeable to someone sensitive to lag, so it's best to stay in game mode. No Roku features Built in (this isn't really a big deal) I'll need an HDMI switch to get all of my consoles to output to HDMI port 5, in order to take advantage of the lowest possible latency. Otherwise, I'd be better off with the OLED. HDMI port 5 supports 1080p/[email protected] with 15ms of lag and 1080p120Hz with 10ms of lag, but due to bandwidth limitations the lumanance compression is YUV4:2:0. Ports 1-4 can support YUV 4:4:4 and HDR thanks to full bandwidth HDMI2.0, but the lag jumps to 27ms for 1080p/4k60Hz and 1080p120Hz jumps to 30ms. The best input lag performance (1080p120Hz YUV 4:2:0 at 10.5ms) can really only be taken advantage of by a computer. The YUV 4:2:0 compression does cause some artifacts in text, but is unnoticeable in games. Arguably, 1080p120Hz with 10ms of lag is better than 4K60hZ, as long as I'm seated more than 5 feet from the TV - which I am. At that distance the difference between a 55 inch 4K and 1080p screen can't be discerned by the human eye and sacrificing YUV4:4:4/HDR to gain ~20ms of lag seems like a good trade off to me. All of this assumes the switch plays nice. I already have an HDMI switch, but it's limited to 4k30Hz (~3Gbps). I don't know if it will suffice. Worst case, I just upgrade to a HDMI2.0 certified (18Gbps) switch. I've got some high speed (18Gbps) HDMI cables on the way too. TCL 55R617 Pros LED screen provides no risk of burn in. Blacks are good on this LED, thanks to local dimming. It also has a consistent low input lag profile, 17-19ms for most resolutions and scenarios in game mode (SDR & HDR). It's lag profile is better than the OLED does, but not as good as the Vizio. Outside of game mode, it has a fairly high latency. While the lag profile is less consistent than the OLED across a wide range of gaming scenarios, all scenarios experience less than 30ms of lag in game mode and should thus be unnoticeable. Best price of the three and TCL's best TV Roku OS Built in Cons Not as good at blacks as the VIZIO P-series or OLED. Outside of game mode, it has a fairly high latency. That will have noticeable lag, so it's best to stay in game mode. No Component Input Does not have a native 120Hz refresh rate. Consequently, the Vizio and OLED have better motion handling. The TV I'm replacing is a cheap TCL Roku TV I bought on sale after my Plasma died. The cheap Roku TV is surprisingly good for $250. It sold me on TCL and when my Mom wanted an upgrade later, I got her one. The ease of use and familiarity of the Roku OS is a huge selling point. The controller is simple and the Netflix and Hulu apps are well designed, unlike other implementations I've seen. For streamers, it's nice to have a Netflix or hulu button on the remote. Having a roku built in to the TV itself doesn't just save an HDMI input, it puts all the TV inputs on the roku home screen as tiles, right next to your favorite streaming apps, making changing inputs very easy and intuitive. It's a user friendly OS my Mom can learn to use with ease. I nearly went with the TCL 55R617 because of the Roku OS and it's reasonable price. It should be a damn good TV, but I decided against it in favor of the VIZIO. The 120Hz native refresh rate gives it better motion handling, it has better black performance, a dedicated low latency HDMI5 port, and component input. That put it over the top for me. I got it for $700, which is not too bad either. For $1,400 I could get the LG B8, but it's advantages over the Vizio p-series don't justify the price IMO. PS: There in more on this topic once I get the TV and have a chance to test it out. So look out for the second part. To be continued...
×