Hi!,
I'm setting up a VDR with a budget cinergy 1200 terratec dvb-t card. The mobo is epia-M (svideo out). I want to use svideo but while I'm setting up I would use my crt monitor(softdevice+FB?) to see my vdr output. Can I done this with softdevice? With which output method? What output methods have I to comment(to not be used) in softdevice makefile to do this? Finally when I put the VDR in my saloon what output method have I to choose to use the svideo out?(softdevice+DFB?)
Thanks
Leo Márquez a écrit :
I'm setting up a VDR with a budget cinergy 1200 terratec dvb-t card. The mobo is epia-M (svideo out). I want to use svideo but while I'm setting up I would use my crt monitor(softdevice+FB?) to see my vdr output.
The s-video and VGA and other outputs on EPIA-M output the exact same image. You can't have the VDR video on one output and the console on another. I think that's a limitation of the board, not of the CLE266. Said otherwise : the s-video + composite chip (VT1622) uses the VGA output and translate the signal type.
If you want to first use a CRT, then the TV, you're OK. That's what I did and it works.
If you want a console to control the vdr processes, you can either connect to a SSH server on your vdr box (from another PC, that you already have, haven't you ?), or add a second video card inside the box, make it primary, and make it work...
Can I done this with softdevice? With which output method?
This has nothing to do with softdevice.
What output methods have I to comment(to not be used) in softdevice makefile to do this?
You could use any output method you which, based on other criteria. I would suggest DirectFB (light, fast, etc.).
Finally when I put the VDR in my saloon what output method have I to choose to use the svideo out?(softdevice+DFB?)
Use the same as when testing. Softdevice has no problem to switch from one to another, but other criteria count : start an X server if you use X, thus stop it, get the right authorizations, etc.
En/na Nicolas Huillard ha escrit:
Leo Márquez a écrit :
I'm setting up a VDR with a budget cinergy 1200 terratec dvb-t card. The mobo is epia-M (svideo out). I want to use svideo but while I'm setting up I would use my crt monitor(softdevice+FB?) to see my vdr output.
The s-video and VGA and other outputs on EPIA-M output the exact same image. You can't have the VDR video on one output and the console on another. I think that's a limitation of the board, not of the CLE266. Said otherwise : the s-video + composite chip (VT1622) uses the VGA output and translate the signal type.
If you want to first use a CRT, then the TV, you're OK. That's what I did and it works.
This is exactly the thing I want. See VDR in the CRT (i have another computer to connect vis ssh)
If you want a console to control the vdr processes, you can either connect to a SSH server on your vdr box (from another PC, that you already have, haven't you ?), or add a second video card inside the box, make it primary, and make it work...
Can I done this with softdevice? With which output method?
This has nothing to do with softdevice.
And how know softdevice if has to use the vga cable to crt or the svideo to a TV?
What output methods have I to comment(to not be used) in softdevice makefile to do this?
You could use any output method you which, based on other criteria. I would suggest DirectFB (light, fast, etc.).
Finally when I put the VDR in my saloon what output method have I to choose to use the svideo out?(softdevice+DFB?)
Use the same as when testing. Softdevice has no problem to switch from one to another, but other criteria count : start an X server if you use X, thus stop it, get the right authorizations, etc.
I have no plan to use X but if I decide change softdevice to xine I think I will need it.
I'm just have built from source vdr 1.3.24 and try to make softdevice plugin. If I try the DirectFB the only thing I need is install directFB with apt? (i use debian) and comment the other output options in softdevice Makefile?
Thanks again.
Leo Márquez a écrit :
And how know softdevice if has to use the vga cable to crt or the svideo to a TV?
Softdevice doesn't decide : the motherboard does this. Just select CRT + TV on the BIOS. This will activate TV timings for all output, and "just works". WRT DirectFB, you have to use the viafb kernel frame buffer driver from patcher2k or DirectFB CVS (see related recent threads on the softdevice + directfb-users ML). This driver receive a TVon parameter you also have to set to 1.
I have no plan to use X but if I decide change softdevice to xine I think I will need it.
You will then have to use a xine + X enhanced for CLE266 HW decoding (if you really want something more than softdevice from that combination). You could also try the Unichrome X driver from CVS, that have improved TV-out settings, but that's another story...
I'm just have built from source vdr 1.3.24 and try to make softdevice plugin. If I try the DirectFB the only thing I need is install directFB with apt? (i use debian) and comment the other output options in softdevice Makefile?
You also need DFB++ (a C++ layer between softdevice and DirectFB). You can use my Debian source package at http://nicolas.huillard.net/vdr/debian/ (download, compile, install) I don't offer a Debian repository, but e-tobi will soon have a working softdevice package...
You should really subscribe to the softdevice ML on berlios.de if you're not already.
En/na Nicolas Huillard ha escrit:
Leo Márquez a écrit :
And how know softdevice if has to use the vga cable to crt or the svideo to a TV?
Softdevice doesn't decide : the motherboard does this. Just select CRT
- TV on the BIOS. This will activate TV timings for all output, and
"just works". WRT DirectFB, you have to use the viafb kernel frame buffer driver from patcher2k or DirectFB CVS (see related recent threads on the softdevice + directfb-users ML). This driver receive a TVon parameter you also have to set to 1.
I have no plan to use X but if I decide change softdevice to xine I think I will need it.
You will then have to use a xine + X enhanced for CLE266 HW decoding (if you really want something more than softdevice from that combination). You could also try the Unichrome X driver from CVS, that have improved TV-out settings, but that's another story...
I'm just have built from source vdr 1.3.24 and try to make softdevice plugin. If I try the DirectFB the only thing I need is install directFB with apt? (i use debian) and comment the other output options in softdevice Makefile?
You also need DFB++ (a C++ layer between softdevice and DirectFB). You can use my Debian source package at http://nicolas.huillard.net/vdr/debian/ (download, compile, install)
I try it but I don't know exactly what I have to do with .debs ans the sources. Then I have downloaded,compiled and installed directdb But when I try to do the same with DFB++ i get:
Library requirements (directfb >= 0.9.23) not met
The last version of directfb I see in directfb.org is 0.9.22
I don't understand what I'm doing and perhaps it's the problem I don't know if leave this way and change to xine... Sorry, I know I'm little lost.
Leo Márquez a écrit :
En/na Nicolas Huillard ha escrit:
You also need DFB++ (a C++ layer between softdevice and DirectFB). You can use my Debian source package at http://nicolas.huillard.net/vdr/debian/ (download, compile, install)
I try it but I don't know exactly what I have to do with .debs ans the sources. Then I have downloaded,compiled and installed directdb But when I try to do the same with DFB++ i get:
Library requirements (directfb >= 0.9.23) not met
My debs are made from DirectFB CVS, which is called 0.9.23 as of release of the previous one. So 0.9.23 means CVS. The best would be to grab latest DirectFB and DFB++ CVS snapshot, compile DirectFB as-is, and add my debian/ directory to the DFB++ extract you will then have, and package from this. Or you don not use Debian packaging at all, and follow standard directfb compile instructions...
The last version of directfb I see in directfb.org is 0.9.22
I don't understand what I'm doing and perhaps it's the problem I don't know if leave this way and change to xine...
Don't leave before you actually see softdevice !!!
Sorry, I know I'm little lost.
The list is here to help ;-)
En/na Nicolas Huillard ha escrit:
Leo Márquez a écrit :
En/na Nicolas Huillard ha escrit:
You also need DFB++ (a C++ layer between softdevice and DirectFB). You can use my Debian source package at http://nicolas.huillard.net/vdr/debian/ (download, compile, install)
I try it but I don't know exactly what I have to do with .debs ans the sources. Then I have downloaded,compiled and installed directdb But when I try to do the same with DFB++ i get:
Library requirements (directfb >= 0.9.23) not met
My debs are made from DirectFB CVS, which is called 0.9.23 as of release of the previous one. So 0.9.23 means CVS. The best would be to grab latest DirectFB and DFB++ CVS snapshot, compile DirectFB as-is, and add my debian/ directory to the DFB++ extract you will then have, and package from this.
Ok I have compiled and installed directfb cvs snapshot without problems. But when I try to compile DFB++ cvs snap i get this:
./configure: line 19750: syntax error near unexpected token `DIRECTFB,' ./configure: line 19750: `PKG_CHECK_MODULES(DIRECTFB, directfb >= $DIRECTFB_VERSION)'
Leo Márquez a écrit :
Ok I have compiled and installed directfb cvs snapshot without problems. But when I try to compile DFB++ cvs snap i get this:
./configure: line 19750: syntax error near unexpected token `DIRECTFB,' ./configure: line 19750: `PKG_CHECK_MODULES(DIRECTFB, directfb >= $DIRECTFB_VERSION)'
Did you run ./autogen.sh ? (PKG_* makes me think about that, but I really do not master that part).
En/na Leo Márquez ha escrit:
En/na Nicolas Huillard ha escrit:
Leo Márquez a écrit :
En/na Nicolas Huillard ha escrit:
You also need DFB++ (a C++ layer between softdevice and DirectFB). You can use my Debian source package at http://nicolas.huillard.net/vdr/debian/ (download, compile, install)
I try it but I don't know exactly what I have to do with .debs ans the sources. Then I have downloaded,compiled and installed directdb But when I try to do the same with DFB++ i get:
Library requirements (directfb >= 0.9.23) not met
My debs are made from DirectFB CVS, which is called 0.9.23 as of release of the previous one. So 0.9.23 means CVS. The best would be to grab latest DirectFB and DFB++ CVS snapshot, compile DirectFB as-is, and add my debian/ directory to the DFB++ extract you will then have, and package from this.
Ok I have compiled and installed directfb cvs snapshot without problems. But when I try to compile DFB++ cvs snap i get this:
./configure: line 19750: syntax error near unexpected token `DIRECTFB,' ./configure: line 19750: `PKG_CHECK_MODULES(DIRECTFB, directfb >= $DIRECTFB_VERSION)'
I also tried to copy your debian folder to the last cvs snap and when run debian/rules binary get the same error. If I try debian/rules in your DFB++ i get the same but in different message:
configure: error: Library requirements (directfb >= 0.9.23) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. make: *** [dfb++-build/configure-stamp] Error 1
Thanks.
Leo.
En/na Nicolas Huillard ha escrit:
Leo Márquez a écrit :
Ok I have compiled and installed directfb cvs snapshot without problems. But when I try to compile DFB++ cvs snap i get this:
./configure: line 19750: syntax error near unexpected token `DIRECTFB,' ./configure: line 19750: `PKG_CHECK_MODULES(DIRECTFB, directfb >= $DIRECTFB_VERSION)'
Did you run ./autogen.sh ? (PKG_* makes me think about that, but I really do not master that part).
Yes I have run ./autogen.sh. Is this bad?
Leo
Leo Márquez a écrit :
En/na Nicolas Huillard ha escrit:
Leo Márquez a écrit :
Ok I have compiled and installed directfb cvs snapshot without problems. But when I try to compile DFB++ cvs snap i get this:
./configure: line 19750: syntax error near unexpected token `DIRECTFB,' ./configure: line 19750: `PKG_CHECK_MODULES(DIRECTFB, directfb >= $DIRECTFB_VERSION)'
Did you run ./autogen.sh ? (PKG_* makes me think about that, but I really do not master that part).
Yes I have run ./autogen.sh. Is this bad?
No I'd qualify this "good"... You'd better continue to ask this on the directfb-users ML : there are developpers here that can help on this point.