4:3 screen instead of 16:9

Asked by mustis

First thank you very much for excellent application !

I have 4:3 display at home and unfortunately MeTV shows most of the tv-programs in 16:9 mode. Is it possible to change the aspect ratio so that also people who have 4:3 display can see tv-programs without black boxes (up and down in the screen) ?

Changing aspect ratio doesn't have to happen automatically by pressing certain button. I would be very happy if I could manually change setting permanently to 4:3 in one of configuration files in MeTV application. Is this possible ?

Question information

Language:
English Edit question
Status:
Solved
For:
Me TV Edit question
Assignee:
No assignee Edit question
Solved by:
Michael Lamothe
Solved:
Last query:
Last reply:
Revision history for this message
Scott Evans (vk7hse) said :
#1

Hi...

In Australia the standard set for Digital Broadcast is 16:9 whereas for
Analogue it's still 4:3

So what you would be asking for here would be essentially a zoom
feature ? Like what some DVB set-top boxes have. is this correct ?

On Sun, 2009-03-29 at 13:44 +0000, mustis wrote:

> New question #65762 on Me TV:
> https://answers.launchpad.net/me-tv/+question/65762
>
> First thank you very much for excellent application !
>
> I have 4:3 display at home and unfortunately MeTV shows most of the tv-programs in 16:9 mode. Is it possible to change the aspect ratio so that also people who have 4:3 display can see tv-programs without black boxes (up and down in the screen) ?
>
> Changing aspect ratio doesn't have to happen automatically by pressing certain button. I would be very happy if I could manually change setting permanently to 4:3 in one of configuration files in MeTV application. Is this possible ?
>

Scott Evans VK7HSE
Phone: +61362291658
Mobile: +61417586157
Skype: vk7hse
<email address hidden>
http://www.vk7hse.hobby-site.org
PGP/GPG Key ID 74639624

--
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately
by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified
that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

Revision history for this message
mustis (timomustonen) said :
#2

Also in Finland standard set for Digital Broadcast is 16:9. Anyhow some of the programs are still in 4:3 format.

Yes, I'm basically asking for a scaling/zooming option like some dvb set-top boxes have. Only difference is that they have several zooming options but in this case only one option (16:9 -> 4:3) is needed. Maybe also in some other counties this option would solve most of the challenges with the ratios.

Solution doesn't need to be fancy. The key thing is that it works even if I need to edit some configuration files.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) said :
#3

Let's see if we can get xine to do it for us,

* Use xine to work out which setting in the ~/.xine/config file changes the aspect ratio
* Copy that setting into the ~/.me-tv/xine.config and see if that works

Revision history for this message
mustis (timomustonen) said :
#4

I found ~/.me-tv/xine.config - file but I didn't understand this : "Use xine to work out which setting in the ~/.xine/config file changes the aspect ratio".

I was able to change the ratios of the screen by pressing "a" when Xine was playing but I don't understand what I should copy to xine.config-file.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) said :
#5

I guess that xine doesn't persist this setting. If you feel like busting-out gcc, you could just add,

 argv.push_back("-r");
 argv.push_back("4:3");

to line 64 of src/xine_engine.cc.

Revision history for this message
mustis (timomustonen) said :
#6

You wrote that I should add lines to src/xine_engine.cc - file. Which release are you referring to ? I'm still using 0.5.30 because I'm Ubuntu 8.10. user and 0.5.30 is the latest release in their reposities. I tried to update to the newest release "manually" but something went wrong and I returned back to 0.5.30 release.

To which line (in xine_engine.cc-file) should I add those lines in 0.5.30 release ?

Thanks for your very valuable help !

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) said :
#7

I'm referring to 0.7 or 0.8, I don't know how to do that in 0.5. I will not be adding any new features to 0.5, especially Lenny or Intrepid because they are now stable. If you want to new features then you need to be using the latest development version. 0.5.30 is about a year old now and I will only supply security fixes for it. Sorry.

Thanks,

Michael

Revision history for this message
mustis (timomustonen) said :
#8

xine_engine.cc - file isn't the same in 0.7.0 and in 0.8.0 versions.

Would you please give me new detailed instructions where I should add those lines in 0.7.0 and 0.8.0 versions ?

 I'd like to test both versions (0.7.0 and 0.8.0) with my Ubuntu.

Thank you ...

Revision history for this message
mustis (timomustonen) said :
#9

Any time to look at my question ?

Thanks for your help !

p.s. I have now upgraded my Ubuntu to Jaunty.

Revision history for this message
Best Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) said :
#10

Sorry mustis, the reason why I haven't answered is because I figured that if you had issues working out where to put those lines, then maybe I had asked you to step beyond your skill level.

0.8 has been released, we're already at 0.8.4, you should change the xine_engine.cc in the latest version.

Revision history for this message
mustis (timomustonen) said :
#11

Thanks Michael Lamothe, that solved my question.