The bug, garbled audio, occurs after viewing recordings and returning to live TV. I doubt there are even half a dozen folks in all of North America doing that!Ĭlick to expand.I've been living with a minor bug since I purchased my latest 3500STBII five months ago. The only novel info on it is the "Air/Cable" setting, which is irrelevant (they're all gonna be the same) unless you're one of the very few who use their iView with both OTA and cable signals (via an RF switch or by manually unhooking/hooking up cables). ![]() You can download the 3500 version from iView's Web site at the most part I think it's just "flash" to make the box a bit more attractive to new users. If it's not there, check System/Information iView may have mistakenly flashed 3200 firmware onto your unit. There should be a "Modulation" setting on the third menu page (Channel Search). Unfortunately I don't have an AVR to hook them to, so it's hard to be sure what each setting does.Yeah the manual still sucks. Since the iView has two digital audio outputs (HDMI and coaxial), I think the old units had a RAW setting where the coaxial was RAW but the HDMI was PCM, and a RAW HDMI ON setting where both were RAW. Generally, a tuner should have at least PCM (converted to stereo) and RAW (DD pass-through) settings. But even on the 3200, to be safe I still use a powered HDD or hub, or one of the SanDisk Ultra thumb drives known to work.I'm not sure. But you have to weigh that against the disadvantages (no component video output, no front panel). I think the signal strength scale varies a lot more than the actual tuner sensitivity.An advantage of the smaller 3200 model is its external power supply if it dies, just replace it. I've tried various iView and HomeWorx units over the years and they've all received pretty much the same channels and had trouble with the same channels. The last 3500s with this switch had a different chip and required different, incompatible firmware, so a change like that could lead to accidental brickings If they do, that's going to be confusing. That didn't work on the 1903 version for the 3200, and they didn't fix anything else.) Do the 3500s shipped with this version once again have a Channel 3/4 switch in back? That's the only reason I can imagine for dropping the Modulation setting. (Besides, I checked time-shifting and it worked fine. My first thought was that this firmware was actually meant for the 3200, but System / Information clearly shows 3500STBII. The only difference I've found is that the "Modulation" setting on the 1903 version isn't there in the 1911 version. As far as I can tell, they didn't fix a damn thing between 19. All the little annoying bugs I listed for 1903 are still there in 1911. In fact, I found almost no differences between the 19 versions of the 3500 firmware. ![]() ![]() I also didn't encounter the Channel Rescan bug. So it may only appear under certain unusual conditions. I was unable to duplicate the Schedule Edit bug, but did say that his box stopped having this bug too, after a power cycle. I'll see what I can find (besides the Schedule Edit bug and the fouled-up SW version string).Įdit: Flashed the new version (which I'll call the 1911 version) onto my 3200 and played with it a bit. (Typical mStar firmware quality control.)Īnyway, I downloaded this version for testing. Based on the file name, the correct date is apparently 20191121V5.0. Second, iView posted this firmware version on their Web site just a few days ago. It's supposed to be a date, in YYYYMMDD order, but there are nine digits, not eight. First, that SW version has an extra digit. Thus, to anyone having this bug, I strongly recommend updating your firmware.Ĭlick to expand.I just noticed a couple of things. (Ion affiliates seem to be some of the worst for triggering this bug.) Because the recording schedule for these channels is damaged, it's nearly impossible to record shows on those stations reliably. Most TV stations don't change the PSIP data that triggers a rescan very often, but a few seem to have some obscure change or other every few days, thus triggering frequent rescans. For instance, the new iView 3300STB has the bug. Iview actually got this fixed back in 2016 with the "1511" version I prefer, but it has come back occasionally. The worst part is, the recording schedule for those channels is usually lost or scrambled as well. If so, it's a bad one: whenever something in a station's PSIP data changes (aside from the time and EPG), the box rescans the station's frequency as if you'd gone into the menu and done a "Manual Search." Any customization you'd done to the channels on that station, such as deleting, skipping, renaming, etc. ![]() Click to expand.Uh-oh that sounds like the channel rescan bug.
0 Comments
Leave a Reply. |