PDA

View Full Version : ATI All-In-Wonder Tuning and other issues in latest beta


jwvanderbeck
11-28-2000, 02:31 PM
Hello,

I've finished playing around a bit with this latest beta 4, and have some issues to report.

I had a problem with the last beta, where anytime the system set up to record, the input got shifted to the video input on my card, away from the cable input.

This new beta has the exact same problem, but because we have more options to choose from I started experimenting. First of all, I tried using the old way, using Windows Media Encoder 7. This recorded fine (although from the wrong input) in the last beta, but not in this one.

I then tried using DirectShow with DX8 installed. for some reaosn here, every time a diagnostic recording got 3/4 done, I would get a "Capture Halted" message and SnapStream would lock in to recording mode and I would have to kill the task.

I then went back to WME7 and started fooling around. I ended up havint to manually edit the .WME profile I was using, to get the right video device in there. It is set up to use the default video device wich does not work for my system. Don't know why, but WME7 gives errors if I use the default device, even though it is the only capture device on my system.

I tried using the ATI specific tuner, but I had the same problem as last beta with it changing inputs on me. So I then tried using WME7 with DirectShow tuning.

At first, I thought I finally had it. It recorded properly, off the correct input. But then I did some more testing.

It seems that it doesn't actually get tuned. It simply is recoding off whatever channel was last used in the ATI Player.

I also have a wierd problem with the configs. The primary settings page seems to have "lost" the field where I select my card. I mean, its totally gone http://discuss.snapstream.com/ubb/smile.gif

rkuo
11-28-2000, 07:05 PM
jwvanderbeck,

Thanks for the excellent feedback. We did not have a chance to address the problem you are experiencing with the ATI card before the beta release as we were focusing on testing DirectShow/WDM support.

Based on what is happening with your system, it appears to me that our accessing the ATI drivers to tune the card is inadvertently resetting the input. We have not experienced this problem on our testing machines but I will look through the ATI SDK to see if there is something we are missing.

The primary card setting was removed for this beta as the capture and tuning interface selection options meant that setting wasn't being used for anything. Before, the "card type" option roughly mapped to what the tuning interface option is now. Because of the new ability to tune cards generically via DirectShow, the Card Type option no longer made much sense.

The former "Recording Engine" setting roughly maps to the current "capture interface". The engine option formerly named "Windows Media Format 7" is now AVICap.

[This message has been edited by rkuo (edited 11-28-2000).]

HiRoller
11-28-2000, 08:11 PM
I'm using the AIW as well. When I try to record, I get the following in the log:

[11/28/2000 20:48:00] Slave: Received execute command for "test3".
[11/28/2000 20:48:00] Jobs.Save: 1 jobs were saved.
[11/28/2000 20:48:00] Record: No recording engine has been selected.
[11/28/2000 20:48:00] Slave: RecordStart failed.
[11/28/2000 20:48:00] Master: FDUNAYER encountered a problem recording "test3".
[11/28/2000 20:48:01] Master: Dispatched "Talk Soup".
[11/28/2000 20:48:01] Slave: Next recording - "Talk Soup"

The recording configuration is showing 'AVICAP' and ATI TV Wonder Drivers....

read2000
12-10-2000, 05:27 PM
Hi,

I have the same setup and the same symptoms as jwvanderbeck, is there a fix already for this ???