RE: [Deinterlace-discuss] Modify DScaler

[Victor L. <vi...@aa...>]

Hi,
First I'd like to thanks John and Rob for the Reply. Very helpful
information.

1. I tried "CCX2388xCard::ManageMyState()" and it does helped not crashing
the original Conexant driver(great!!). However, It also cause the hanging on
my system as mentioned. I'll be working on this hanging issue this week.
This may just solve my problem at once.

2. I understand the DirectShow is in the experimental stage, but I'd like to
ask some ideas of what I saw on the system.
 (1) the DirectShow option will only show if the Conexant driver is
installed.
 (2) DirectShow in my DScaler only has sound but no Display. It behaves just
like the crash problem I mentioned on the email, black screen with audio
working on AMCAP or other capture software after running DScaler.

With the above two things I see, I am guessing that DirectShow is using the
Conexant driver component interface and because Dscaler modified some parts
of the SRAM to crash Conexant's driver on the display, The DirectShow
doesn't work anymore. And this also makes DScaler's DirectShow not working.

Does this make sense? If this is the case maybe the whole problem happens in
the SRAM settings? Information in SRAM should be lost when power down, but
power down doesn't help to recover the failure in the next initialization,
why?

thanks,

Victor Lai
Software Project Manager
3 Crown Plaza, Hazlet, NJ 07730
AAEON Electronics Inc.
Tel: 732-203-9300 ext 265
Fax: 732-203-9311
WWW.AAEON.COM

-----Original Message-----
From: John Adcock [mailto:Jo...@ad...]
Sent: Saturday, October 25, 2003 2:38 PM
To: Victor Lai; dei...@li...
Subject: RE: [Deinterlace-discuss] Modify DScaler


> 1. Find out what component in DScaler changed the kernel part
> of the Cx2388X driver. Modify it and Prevent it to crash the
> original driver even if we may loose some display qualities.
> Try to have DScaler running the way it is now.
The cx2388x have an SRAM section with some important stuff in it as well
as the registers, I imagine the driver is setting up the SRAM at boot
and there is a problem after we go in and change it.

As Rob says in his previous post there was some code put in in an
attempt to fix this but it seemed to cause serious instabilities on some
peoples machines it did however work for me during testing so using that
code as a base is probably your best bet.

> 2. Change the driver interface in DScaler for the DScaler to
> work with Connexant driver.
One other approach might be to programmatically disable the connexant
driver at the start of DScaler and reenable it at the end.

> By the way, I am still waiting for the following link to
> work. Can anyone help on this?
> http://www.dscaler.org/devdocs/index.html

I was working on this on Friday and I expect it to be available on
Monday, but don't get your hopes up too high :)

John