Internal Support of Haali Video Renderer

[czerro]

Internal Support of Haali Video Renderer would be great.

[adicoto]

BSPlayer uses it's own internal renderer, developped by the creators of the program. As far as I know, implementing a different renderer will be more difficult than writing down a new program based on Haali. And for what ? I think that BSPlayer's renderer it's one of the best in the world (could be the best one, but haven't yet tested all video players on the market. )

[speedtrap]

It should be possible to add support for Haali's renderer with just a few lines of code.

[J7N]

Then how come there are these VMR-7, VMR-9 and Vista renderers available?

[adicoto]

Because they are a part of DirectShow ?

[speedtrap]

Haali renderer is also a DirectShow filter ;)

[adicoto]

But it's not a part of DirectShow.

[speedtrap]

So? That does not make any difference.

[Tizio]

No, it does make a great difference, DirectShow is a set of APIs made available through Microsoft's DirectX to create DirectShow renderers (for example the BSplayer's one or Haali's one), and so if Haali doesn't provide the source code of its renderer it's impossible to use it for BSplayer authors.. plus BSplayer internal renderer is great and I see no reason to use another one ;)

[adicoto]

This question was asked in other player's forums. Generally the answer was the same I wrote here. It's difficult to re-write the program for another renderer. Most of the posters were offended, claiming that this should be simple. Programmers just replied, if this is so simple, why don't they write it down instead of asking. So, I believe them, that this work probably doesn't worth be done as long there is already a renderer written for BSPlayer (in fact 2 of them, as, IIRC, BSPlayer v2 uses the 2nd renderer developped by the team).

[speedtrap]

You are both wrong. Terribly wrong. There is no need to use any difficult APIs. There is no need to write complex stuff. Media Player Classic added support for Haali's renderer by adding just 12 lines of code!

Even GraphEdit is able to use Haali's renderer. And that program is older than Haali's renderer.

[Tizio]

Ok, maybe I and adicoto are speaking about something different from qhat you mean, or only I speak about something different...
Haali splitter internal support I think could be added with few lines of code, but if haali has its own renderer (I don't know if it has it), this can't be added so easily if haali's api calls are not of public domain ;)

[adicoto]

I think at this moment, we just have to sit and wait for a team member to post a reply in here.

[speedtrap]

Originally Posted by Tizio

... but if haali has its own renderer (I don't know if it has it), this can't be added so easily if haali's api calls are not of public domain ;)

His renderer is a DirectShow filter (like all other renderers are) and thus has a standardized API. So there is no need to know the source code. Just like the source code of the all the other renderers is of no importance.

[Tizio]

But this doesn't make sense...
also my BSP SkinMaker uses standardized Windows API calls, but you can't use it to read what you want from the registry (even if I use registry reading APIs in my application..)
You can't even make working plugins for BSplayer if BST removes the calls he made available to create them to work with BSplayer (read BSplayer's doc folder for more info)

Anyway I'll wait for BSP team member replies before adding more from myself, maybe I have misunderstood everything :P

[speedtrap]

Yes, you misunderstood everything.