xine config read from $(app_dir)xine.config

Is there a question here?

Your description could be taken multiple ways depending on which version of Me TV you are talking about. Are you saying that you have an issue with the implementation and would like to discuss how to fix it? If so, I'm all ears.

The ~/.me-tv/xine.config is intentional. ~/.xine/config is only generated by the xine application (not libxine/xine-lib). Since Me TV 0.5 has nothing to do with the xine application then it shouldn't really use ~/.xine/config because it is in an application specific directory.

Thanks,

Michael

Sorry, I did'nt find a "proposal" section:-)

There is no configuration for xine video output available in me-tv but it starts xine as a subprocess.

But I saw you created a gstreamer engine for me-tv. I think it will use the gstreamer settings from gnome so it is possible to use i.e. textured video if it configured in the gnome settings.

If it is correct we can set this to "solved"

Regards,
Stephan

You can just email me ;)

So I'm assuming that you're hooked up to the development branch. You can set the xine video output in the preferences dialog. I'm just using a playbin with a video-sink of a xvimagesink, not sure which "setting" it will use. Where can I get the preferred video output setting for GNOME?

Thanks,

Michael

Ok, so I went and had a look and you are correct. The current development version of Me TV was looking at ~/me-tv/xine.config ... that must've been in there from a while ago. I've now removed those configuration lines from the xine engine.

Thanks,

Michael

To get the correct setting from gnome I think is to look in the totem video player. Totem should be use the gnome settings as a real "GNOME application". I will do this in the next days but it depends on time...

I've done some thinking about this and believe that I've done the wrong thing. I will revert Me TV to have its own xine.config file. There are a few cases where using the ~/.xine/config file isn't ideal.

I don't think that there is such a thing as a "GNOME Standard" for video output, it's up to the application. Happy to eat my words.

Thanks,

Michael

Make sense but in this case me-tv needs a more detailed video settings dialog.

And of course: There is the possibility to set the global gstreamer setting for gnome in a control center application. Totem compiled with gstreamer support will use this settings. Especially the gstreamer backend use this settings.

Please correct me if I'm wrong but I thought there is no possibilty to configure video output in totem i.e. video overlay vs. textured video.

Stephan

All engines use the Me TV's local configuration files.
There are several reason for that.
The common player (or a library) configuration does not suit the DVB-? playback in many cases.
Users commonly configure the particular player for example to shift the video picture a bit higher to move subtitles out of the video space here. The DVB-? signal varries, the data stream is frequently incomplete and players and libraries must be configured to cope with that using a different number of buffers or a stream processing queue.
Me TV is using standalone players in a GUI-less mode and the user is not currently able to change the player's configuration (which may not be created for the DVB-? playback), it only configures the vital parameters.

If you want to configure xine-ui/xine-lib to use specific parameters for Me TV, just pass it the local Me TV's config and modify it using the xinetk GUI:
xine --config ~/.me-tv/xine.config
Similarly you can configure VLC library using one of its GUI.
You can also copy or maybe symlink your particular configuration file for the use in Me TV.
Notice that Me TV will always override output parameters on the command line so that the particular configuration may not be functional as a result.

GStreamer is configured in advance by the distribution. You can change its outputs via the control panel, gstreamer-properties or using GConf's utilities.
Again the default configuration or already defined profiles will not probably suit the DVB-? playback requirements. Me TV is not a all-media-handling application (like totem), it is designed for DVB-? (e.g. the particular codecs and streams combinations) and it should do it better.
This engine will need the complete processing pipeline incorporating the best available deinterlace filter and user defined outputs.

I am sure Me TV will have some form of the engines' configuration GUI once it stabilizes enough.
Use the way of configuring the particular engine mentioned higher in the meantime.

You can also help with the development of course. :-)

Yeah, what he said ;)

OK. That's a statement. You are right with stable thing and so on...

But (:-)), I just talking about the video output and from my point of view if I want see a video it doesnt matter if the stream is a DVB or DVD or anything else.

On the other hand if xine backend used in me-tv it should be configurable in me-tv. The same for vlc. Like your suggestion me-tv could start the command xinetk or anything else in a first version. It's only a usability thing but it should be start from me-tv not from a terminal. Don't understand me wrong I'm fimilar with the terminal but some people "don't know how a keyboard works".

I can help to develop. How should it work? Sending patches...?

Stephan

Thanks Michael Lamothe, that solved my question.