Important Question !

[Guest hackbart]

Hi,

 

as you might be able to read between the lines of my last posts, you might recognized that we are heavily working on a brand new release which has a slightly modified engine. The first which will strike you is the new options dialogue, which offers more flexible and easier to find options.

The next thing are the dvb device based classes. You are now able to deal with Skystar/Airstar/Cablestar/ATSCstar cards, as well as with Network (Unicast/Multicast) and File Devices. File Devices are transponder dumps, resp. channel dumps and should include all required pid packets (PMT, PAT, EIT etc). In this case you are even able to emulate DVB cards without having one. Right now the Network works also very well (HDTV runs even via WLAN superb). The first client which is connecting the dvb server (seperate program, which could also run as service) is able to tune a transponder/channel. All other clients could request pids which are broadcasted either via Multicast (this is handy if more than 5 computers are receiving tv), or Unicast (saves a lot of traffic if you just have a few computers connected).

In the past i was talking with griga and the others about the way how to offer these new device features. Since he is also having a big part in the development and i honestly like his logic way to deal with problems i just want to discuss this special problem with other users

If you could take a look on to the attached image. As you can see, the i attached Marfis SkyAVC on to the Device List instead of placing it seperately. Is this a problem for you all? I'm just asking because if i put all Sourcefilters seperately i would need to add at least another combobox, plus some other stuff i honestly not really want to.

The problem is that i know, that a lot of you are using the SkyAVC Filter which is quite superb, so i don't plan to kick this filter completely, but unluckily it only supports the Skystar2 resp. Flexcop based chipsets. So i suppose it would be more confusing to add yet more boxes to the directx field..

 

Christian

 

PS: Restarting the program is also necessary while changing to Marfi's SkyAVC if you did not have the skystar2 as device selected (e.g. you are using the Filesource Device)

[Griga]

OK, my point of view:

 

Marfi's SkyAVC should appear as what it is in the options: A DirectShow source filter. It should not be hidden as a "device", which is misleading.

 

The warning "Changing a device requires a program restart" definitely does not apply to Marfis Filter, which is even more misleading.

 

So I would rather have a list for selecting the source filter, as we had it before - IMO much clearer for DVBViewer users.

 

The attached image shows my suggestion. If someone thinks something about it.... let us know.

[Gioxy]

I agree with Griga, I think that for the user is more clear...

 

Another solution is to put in the list simplier but (IMHO) autoexplainant voices, like:

• DVBViewer

• DVBViewer Classic

• SkyAVC

• SkyAVC Net (<- if this is of any sense...)

• Unicast Network Client

• Mutlicast Network Client

• File Player Only (<- or maybe Video File Render... mah!)

 

But this can work only if DVBViewer have only 1 source to manage... supporting other cards than FlexCopII based is still so far?

So maybe, for future use, Griga solution's is more flexible...

 

BTW: is there some space in the DirectX page for a drop down list to choise the MPEG splitter from those installed (or none at all...)? Moreover, IMHO, this is also the right place to put the choise of the "Render Type"...

 

 

Cheers

 

Gioxy

[Guest Oliver]

BTW: is there some space in the DirectX page for a drop down list to choise the MPEG splitter from those installed (or none at all...)?

There won't be support for third party demultiplexers. DVBViewer classic uses the MS demuxer and the new DVBViewer filter 2.0 features a proprietary solution. Classic mode is just intended to serve as backup solution in case the new one doesn't work (correctly).

 

Bye, Oliver

[Griga]

I guess Gioxy wants to select the demultiplexer for MPG file playback. Anything else wouldn't make sense.

[Gioxy]

DVBViewer classic uses the MS demuxer

 

Ehem, sorry, but I can't know that DVBViewer Classic claim *exclusively* the MS demuxer (and not the one with the highest merit)...

 

I made this pourpose after I noticed, in the image that Christian attached in the post, a check box for "Use Mpeg Splitter"; so I puorpose to change it in a "selection box", because I remebered that (at least for my config) Elecard demuxer had some plus (with AC3 or HDTV, if I remeber well) but also lead DVBViewer in some trouble; as a result I uninstalled Elecard and I can't (and don't want) test it anymore...

 

But if there is (as Griga say ) some other "useful usage"...

 

All in all my opinion is that's better if the DirectShow is "gently" directed in doing exactly what we want it does; maybe a day we can give up with Graph file...

 

Gioxy

[Griga]

I noticed, in the image that Christian attached in the post, a check box for "Use Mpeg Splitter";

 

Yes, that's another misleading thing (thanks for the proof ). Forgot to mention that.

[NameIt]

Hi developers,

 

after reading ALL Postings I think I understood the reasons of the posts of Christian and Griga.

 

First of all, I didn't testet any newer DVBViewer version as 2.2

 

To the point of interest:

Sorry Christian, but in my opinion the most self explanating solution seems to be Gioxys suggestion. As the second solution I would prefer Grigas suggestion.

 

But remember:

I didn't testet any newer DVBViewer version as 2.2

So I might be wrong.

 

Sincerely

NameIt

Edited November 18, 2004 by NameIt

[crypto]

Hi,

 

I would also count Marfi's filter in the source filter section and not in the device section.

 

The new DVBViewer architecture is impressive and seems open for new cards. I also thought about going global and always ran into BDA drivers when looking for support for digital cards. Most progress in this direction is currently going on in Mediaportal. I think when a new application is designed, one should count BDA into consideration.