AVS › AVS Forum › Video Components › Home Theater Computers › FusionHDTV 3.3 official version has been released
New Posts  All Forums:Forum Nav:

FusionHDTV 3.3 official version has been released - Page 29  

post #841 of 1215
In XP your best bet is a "system restore" to the closest date. If no workie then pull the card and boot up and shutdown and reinstall the Fusion app.
post #842 of 1215
Thread Starter 
rpf--

It's possible, but not very likely, that the power glitch fried the Fusion card. Another possibility is that the card needs to be reseated in the socket to make better contact. The error message is telling you that the Fusion sw can't see the card, so it's either not well connected or it's dead.
post #843 of 1215
Quote:
Originally Posted by rpf717
... I was watching TV with my Fusion 5 Lite tuner (3.301), when my sister in law "accidently" turned off the power supply while pluging in her cell phone.

No big deal, I reboot, and now upon launching FUSION its says: EP45: Authentication Error

The program will load, but gets no signal. Interestingly the "Channel" tab under the configuration setting has mysteriously dissappeared (ie you can't run the channel scanner etc).

On FUSION's website FAQ it says:

The error you encountered is that the device driver is not installed properly.
You must see devices properly installed under the "Sound video and game controllers".
Please refer to FusionHDTV's FAQ for installed driver.

It states that I must see certain device drivers under my Device Manager which it goes on to list here:

Ok, so I don't see those drivers on my device manager, and reinstalling the application multiple times has not caused the drivers to reappear?

So the FAQ tells me what I should see, but not what I should do if it's not working.

Aside from kicking the In-Laws out of the house, any other ideas?
I'm new at all this so, any help would be greatly appreciated!
Thanks in advance,
rpf717
sounds like an electrical glitch(my guess is the power was put back quickly and might have caused a surge) has caused your motherboard to not see the fusion card. try removing the fusion card entirely from the computer, then turn the computer on and check the bios to make sure all settings are correct. then reinstall the fusion card again. then do a remove and re-install of the fusion app using my procedure. try a different version of the fusion app.

it's difficult to diagnose a problem like this, but it could be a low cmos battery has lost your bios settings when you lost power. or you may have to clear your cmos and then put in the correct settings again, because the glitch has caused a corruption in the bios.

do you have another computer to test the fusion card in? just to see if it is recognized as being installed in the socket.

ep45 is the same error you get when running the software with out a card in the computer, so it's difficult to tell if its hardware or software.
post #844 of 1215
Thanks for the advice,

After uninstalling, pulling the card, booting, shutting down, placing the card, and reinstalling,

Its now working,
Thanks again
post #845 of 1215
Quote:
Originally Posted by gcmsking
Was just at the DVICO site again and noticed the new "Fusion HDTV5 RT GOLD" which sounds like it would address at least one of the complaints mentioned here (locking of the file being recorded) as it allows you to watch from the beginning while recording... any brave souls care to test the alpha 3.4 version to see if that function is now there?
Not there. Files are still locked. :(
post #846 of 1215
Thread Starter 
Quote:
Originally Posted by gcmsking
Hi... new here, been doing much much lurking and hopefully some learning.

Recently got the DVICO F5USB and after several fits and starts, found and followed the install technique recommended in this thread. I am able to do most everything at this point but am not yet able to tune NBC and ABC HDTV, which in my area (COX-Fairfax VA) I understand to be OOB. Something like 843MHz.

I saw some earlier posts about a registry hack to enable upper frequencies above the default channel scanning limit, by pointing/remapping unused channels to new, higher channels. Can anyone provide step by step guidance... that hopefully will minimize the risk of n00bie errors whilst hacking away at the registry?

Thanks... E.
You'll find a specific example of the Reg hack here and a discussion of the technique as well as a nifty calculator tool to convert the MS knowledgebase decimal frequency values into the hexadecimal base and format needed in the Registry key TS0-1 here.
post #847 of 1215
Today we seem to have Alpha2:

ftp://ftp.dvico.com/Products/FusionH....01_Alpha2.exe

It took them more than a month for any update, now it looks like we are back to an almost daily affair.


Tim
post #848 of 1215
Thread Starter 
...but at least now they're more appropriately named so as not to snare the unwary. ;)


BTW, I haven't yet looked at the state of the PVR functions in the new alphas, but my impression is that the channel scanning problems in 3.30.01 have been fixed. So folks who are having trouble tuning one or more stations with 3.30.0x may want to give these a try to see if my guess is right and they do tune better.

Just make sure that you rigorously follow KAXKID's installation recipe when testing, and be prepared for going back to the old version.
post #849 of 1215
Quote:
Originally Posted by TPeterson
Just make sure that you rigorously follow KAXKID's installation recipe when testing, and be prepared for going back to the old version.
As a data point, I've never used anything but Add/Remove programs to uninstall the software and never had any issues uninstalling or installing new versions.
I'm just sayin'.


Also, I never did get a copy of Alpha1 downloaded yesterday. It repeatedly failed after about 2.5 MB. I'm attempting Alpha2 now.
post #850 of 1215
Thread Starter 
When it works, Add/Remove Programs is the same as the equivalent step in Steve's recipe. The problem is that sometimes it fails, but his way seems so far bulletproof.
post #851 of 1215
Quote:
Originally Posted by TPeterson
...my impression is that the channel scanning problems in 3.30.01 have been fixed. So folks who are having trouble tuning one or more stations with 3.30.0x may want to give these a try to see if my guess is right and they do tune better.
Is this info from DVICO or a guess? I'm loathe to go through the uninstall/install deal if I'm just going to wind up blocked from 1/5 of my clear QAM channels again, but I'm generally a "keep up with the versions" kinda guy.
post #852 of 1215
I haven't followed this thread for a long time and it's too long for the search to even return something useful. So forgive me if this is an FAQ type of question.

Does the latest softwae allow custom naming of QAM channels? It maps subchannels in an unhumanly fashion in the last version I tried, which made it even worse than just main.sub combination.
post #853 of 1215
Quote:
Originally Posted by stephenju
Does the latest softwae allow custom naming of QAM channels? It maps subchannels in an unhumanly fashion in the last version I tried, which made it even worse than just main.sub combination.
Nope, the crazy mapping is still there. For channels with proper PSIP information it maps to a recognizable name, but there are so few of those it's practically worthless. There basically hasn't been anything substantive changed/fixed related to QAM in quite a while now AFAIK.
post #854 of 1215
Quote:
Originally Posted by gcmsking
Hi... new here, been doing much much lurking and hopefully some learning.

Recently got the DVICO F5USB and after several fits and starts, found and followed the install technique recommended in this thread. I am able to do most everything at this point but am not yet able to tune NBC and ABC HDTV, which in my area (COX-Fairfax VA) I understand to be OOB. Something like 843MHz.

I saw some earlier posts about a registry hack to enable upper frequencies above the default channel scanning limit, by pointing/remapping unused channels to new, higher channels. Can anyone provide step by step guidance... that hopefully will minimize the risk of n00bie errors whilst hacking away at the registry?

Thanks... E.
Terry Peterson is the correct source for help on your inquiry. However, I am attaching an image of my Registry after editing under the supervision of Terry to demonstrate a working unit for frequencies greater than allowed by FusionHDTV.
The numbers in the ( ) are the frequencies of the clear QAM channels I wish to receive. These frequencies are also in hex(2e90edd0=781250000), and they must be entered as hex. The numers 2,3,4,5,6,7,8,9 are the numbers I chose to replace the RF numbers used by Fusion to select a given frequency. I chose these small digit numbers, because they permit me to do an auto scan and stop the scan at 10 or higher and avoid getting the 350 channels I don't use as well as save a lot of time.
I use TsBrowser2 to identify the frequencies I wish to insert into my Registry. Note that a number of the frequencies are above 800MHz, and not available in the FusionHDTV. Your frequencies will not be the same as above unless you are connected to Comcast cable in P.G. County,MD. Many of my channels have sub-channels, and some of the sub-channels are encrypted, which seems to confuse my FusionHDTV5USB software. At the present time I find Ver. 3.30.00 as best in sorting out the clear channels and avoiding the encrypted channels.
I hope this will be useful to those trying to extend the frequency range of Fusion tuners. Our requests for a software upgrade have been ignored.
LL
post #855 of 1215
Quote:
Originally Posted by knnirs
I use TsBrowser2 to identify the frequencies I wish to insert into my Registry. Note that a number of the frequencies are above 800MHz, and not available in the FusionHDTV. Your frequencies will not be the same as above unless you are connected to Comcast cable in P.G. County,MD. Many of my channels have sub-channels, and some of the sub-channels are encrypted, which seems to confuse my FusionHDTV5USB software. At the present time I find Ver. 3.30.00 as best in sorting out the clear channels and avoiding the encrypted channels.
I hope this will be useful to those trying to extend the frequency range of Fusion tuners. Our requests for a software upgrade have been ignored.
THANKS!

Can you elaborate on how you use TSBrowser2 to identify the frequencies? My use of TSBrowser, when using autoscan, does the same scan as autoscan in FusionHDTV.

Incidently, I did use your keys from your earlier post because I knew Cox in Fairfax also used the 843Mhz for some channels. Simply followed the instructions at the snapstream site... copied the block of text, renamed reg, good to go. But I am seeing several keys in my registry besides TS0-1... can they be deleted, anyone know? Looks like the results of previous autoscans or something.
LL
post #856 of 1215
Thread Starter 
Quote:
Originally Posted by frankz1
Is this info from DVICO or a guess? I'm loathe to go through the uninstall/install deal if I'm just going to wind up blocked from 1/5 of my clear QAM channels again, but I'm generally a "keep up with the versions" kinda guy.
It's a semi guess based on (1) observing the channel scan here, (2) Karl's report that he was able to view the channels that weren't working with 3.30.01, and (3) the fact that DVICO specificially asked me to try the scanning as one of the areas of interest with this alpha version.
post #857 of 1215
Quote:
Originally Posted by gcmsking
THANKS!

Can you elaborate on how you use TSBrowser2 to identify the frequencies? My use of TSBrowser, when using autoscan, does the same scan as autoscan in FusionHDTV.

Incidently, I did use your keys from your earlier post because I knew Cox in Fairfax also used the 843Mhz for some channels. Simply followed the instructions at the snapstream site... copied the block of text, renamed reg, good to go. But I am seeing several keys in my registry besides TS0-1... can they be deleted, anyone know? Looks like the results of previous autoscans or something.
I don't see those other keys, and I don't feel safe in removing things from Registry.

I am attaching a small image from my TsB2, which can tune to RF channels up to 135.
I entered the number 126 into the CH window, and then clicked twice on Live TV. The program tuned to 805,250 KHz, listed the signal level, and entered the channel info into Sub-Channels window. Note that D1260 is encrypted, but D1261 is not. I then enter 127, 128,129, 130, 131, 132, 133, 134, and 135 to find which channels are available along with the info about encryption. You can also enter numbers below 126 to get similar info.
LL
post #858 of 1215
Quote:
Originally Posted by TPeterson
Tim, I think that you must have a bad installation of 3.30.01. Have you been using the KAXKID procedure? In any case, I suggest a second (or third) careful attempt using that.

The attached TSB2 (which needs to be renamed "zip" from "txt") works with my 3.30.01 installation.
Is the TSB2 file you attached to this post still the latest? I never got it to work and the file size is slightly different expanded (641K) versus the other one that does work (647K). Anyway, I wondered if another updated TSBrowser was coming especially if they tweaked the channel scanning in 3.4.alpha.
post #859 of 1215
Thread Starter 
That TSB2 worked for me with 3.30.01 and there is no "new" one for the alpha codes, AFAIK.

BTW, if you're running TSB2 just to get the channel frequencies...don't. Go back and look at the references to the MSFT KB in that Snapstream article that I linked, because they give all the frequency data that you need.
post #860 of 1215
Quote:
Originally Posted by TPeterson
That TSB2 worked for me with 3.30.01 and there is no "new" one for the alpha codes, AFAIK.

BTW, if you're running TSB2 just to get the channel frequencies...don't. Go back and look at the references to the MSFT KB in that Snapstream article that I linked, because they give all the frequency data that you need.
I'm running it to see what frequencies have active QAM channels from my cable provider. I suppose I could just map all the lowers to uppers and from the articles and do a channel scan in FusionHDTV, catch them in my favorites, then remove the mapping...
post #861 of 1215
Quote:
Originally Posted by TPeterson
It's a semi guess based on (1) observing the channel scan here, (2) Karl's report that he was able to view the channels that weren't working with 3.30.01, and (3) the fact that DVICO specificially asked me to try the scanning as one of the areas of interest with this alpha version.
Terry,

A2 did not work for me; I had to revert to the 01 in the usual three plus hour procedure of manually cleaning the registry of 100’s of DVICO, BLUEBIRD, ZULU et al. entries manually.

That three-hour procedure is because that DVICO does not know how or does not care to program in a method, style, or format that is recommended by Microsoft using current tools and third party libraries and/or object code that is designed and compliant for a Windows XP in a post Service Pack 2 operating environment. DVICO is using very old development tools.

DVICO needs to use a MSI 3.X compliant installation routine, and be working on a MSI4.X routine (needed for x64 and Windows Vista). If DVICO is going to produce such “dirty†code, they need to provide a tool (with full logging) that would remove and deregister all reference to their product and applications. Other manufacturers already are doing so for their products; it just may not be “publicâ€, but still available.

The scanning on A2 is “brokenâ€; it “trapped out†at the end of the initial first scan of the digital channels. I attempted several installs.

DVICO needs to get their act together, forget about everything else (such as PVR, EPG and so forth) and just produce an application that does work correctly with QAM, and all US major MSO’s. This idea of just one application for the product line worldwide is ridiculous; we are probably going to need a highly customized version just for the US, considering the uniqueness of the US MSO’s, and their tendency not to adhere to specifications 100%.

We still have not a good explanation for the six-week hiatus in application development from DVICO.


Tim
post #862 of 1215
Quote:
Originally Posted by TheGreatOne
Today we seem to have Alpha2:

ftp://ftp.dvico.com/Products/FusionH....01_Alpha2.exe

It took them more than a month for any update, now it looks like we are back to an almost daily affair.


Tim
Is there a Readme online that discusses the functionality in these Alpha's?

-- Rich
post #863 of 1215
Thread Starter 
Quote:
Originally Posted by RichB
Is there a Readme online that discusses the functionality in these Alpha's?
No, evidently they're true alphas, not intended for public consumption and not even fully tested on DVICO's own hardware. I only pointed out the possibility that those who have trouble with channel scans with the 3.30 code may find them to work better after others had posted here of their existence. (And I tried to emphasize the risk of playing with them to discourage the hapless)

To be perfectly clear: I recommend that most people sit on the sidelines until there's a new code that's at least called a "beta" again.

Tim: DVICO "needs" to do as you suggest about as much as all those U.S. MSOs "need" to follow specifications 100%. ;) As for explanations, can you say "TViX"?
post #864 of 1215
Quote:
Originally Posted by RichB
Is there a Readme online that discusses the functionality in these Alpha's?

-- Rich
No README or CHANGELOG, typical of what I expect from DVICO.


Tim
post #865 of 1215
Quote:
Originally Posted by TPeterson
Tim: DVICO "needs" to do as you suggest about as much as all those U.S. MSOs "need" to follow specifications 100%. ;) As for explanations, can you say "TViX"?
Not true, they are using a Korean programing style, that is not typical anywhere else in the world. I also suspect something else, and I beleive that may very well the reason that DVICO has not upgraded.

The DVICO application will not work under the final released version of Windows Vista; thus they need to get moving real fast.

IMHO, all DVICO software has been "beta", and what they (DVICO) call "beta" is really "alpha".

Any word as to why the six-week break?

Thanks,


Tim
post #866 of 1215
Thread Starter 
I already told you the word. It's "TViX". (They know as well as you and I that tinkertoy add-ons for PCs are a chump-change market when compared to TV appliances like TiVo or X/Sling/younameit-Box)
post #867 of 1215
Quote:
Originally Posted by TPeterson
I already told you the word. It's "TViX". (They know as well as you and I that tinkertoy add-ons for PCs are a chump-change market when compared to TV appliances like TiVo or X/Sling/younameit-Box)
Unfortunately for us HTPC enthusiasts, I agree with you, that DVico's most valuable time is probably spent developing the more consumer friendly products that would sell more in mass, and I can't blame a company for wanting to make money. However, I also feel DVico is doing a huge disservice to both itself and its customers first off because they cannot seem to get the software right after years of practice, and secondly by deciding to not let other 3rd party developers work on a program that could actually make their PC "tinkertoy add-ons" into awesome products without those developers having to pay a lot of money for DVico's tools.

I have several PCs with TV tuners, but only 1 with a Fusion because of the software, and I have many friends who have tuners now but were interested in the Fusion at one time, and I even know quite a few more that would purchase one for their own PC if the software wasn't so flakey. It's too bad, as in this case I believe DVico is cutting of their nose to spite their face!

In my opinion, if their PC products had good software, even if written by 3rd parties who didn't have to pay DVico for their development suite, they would be flying off the shelves and DVico would be making a lot more money on them just because of point of sale, and probably a lot more money than they are now with their current software package and all the time they have spent and are spending still trying to develope software that works properly and is stable ... it seems to be a waste of their time and effort spent on the PC software side of these cards if their other products like TViX are going to be their bread and butter going forward, so it's time for DVico to start giving their darn development tools away to companies the likes of Snapstream and SageTV or (insert your favorite company here), and let them develope working software for their cards, we would hopefully (probably) end up getting software that was acceptable , stable, and user friendly, causing sales of DVico PC products to rise dramatically IMO, and all the while DVico could then focus all their attention to their other bread and butter products even more cost effectively ... in the end the consumer is made happy and DVico should be making more money on the sales of the hardware, regardless if they don't make money licensing their tools (have they even sold 1 license to another developer yet!?!) ... am I way off base here or what?
post #868 of 1215
Quote:
Originally Posted by RichB
Is there a Readme online that discusses the functionality in these Alpha's?

-- Rich
i posted the portion of the readme included with the 3.40.01 that pertains to the newer versions in this post:
http://www.avsforum.com/avs-vb/showt...&&#post7460355
post #869 of 1215
Quote:
Originally Posted by TPeterson
I already told you the word. It's "TViX". (They know as well as you and I that tinkertoy add-ons for PCs are a chump-change market when compared to TV appliances like TiVo or X/Sling/younameit-Box)
Unfortunately, many companies lack the foresight to grasp that, if they get a reputation among us "noodlers" for putting out junky/clunky products, that reputation carries over into the mainstream entertainment product world when early adopters (again, us "noodlers") ignore their mainstream products or give the company bad word of mouth.

Bottom line is that any product a company puts out, no matter the intended audience, reflects upon the quality of all its product lines.
post #870 of 1215
Quote:
Originally Posted by KAXKID
i posted the portion of the readme included with the 3.40.01 that pertains to the newer versions in this post:
http://www.avsforum.com/avs-vb/showt...&&#post7460355

Thanks. Hmm. I do not see the allowing of other readers so I could play a recording with TheaterTek while it is being recorded.

Where are they coming up with the urgent need for zoom and slow motion :rolleyes:

-- Rich
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers
This thread is locked  
AVS › AVS Forum › Video Components › Home Theater Computers › FusionHDTV 3.3 official version has been released