Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: How I was able to get mamewah 1.62 to work on my component t.v.  (Read 2193 times)

0 Members and 1 Guest are viewing this topic.

mccoy178

  • It's hard to work with a straight jacket on
  • Trade Count: (+9)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3127
  • Last login:September 03, 2021, 10:23:42 am
  • Go Bucks!
I used the layout editor from mamewah 1.61.  I resized the layout to 640x432.  I also set a custom resolution of 30 hz.  Here are the results:




cdbrown

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1241
  • Last login:October 16, 2017, 09:52:03 pm
  • Bowowow
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #1 on: June 08, 2006, 03:30:44 am »
Any chance of making a small video clip to show the two screens in full action.  I like it  :cheers:

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:July 13, 2025, 11:38:27 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #2 on: June 08, 2006, 03:52:28 am »
Hmm... looks like the typical overscan I would expect.


Is mame doing this too?  Cause if not the easiest way to fix just the fe is to just create some "buffer" space around your skin by making a border around the background image and repositioning all of the  elements to match.  Not the most elegent solution, but it works. 


mccoy178

  • It's hard to work with a straight jacket on
  • Trade Count: (+9)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3127
  • Last login:September 03, 2021, 10:23:42 am
  • Go Bucks!
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #3 on: June 08, 2006, 08:58:18 am »
The t.v. has about 5% overscan which concurs with others who are using component.  Some have used the secret menu on the t.v. to adjust this, so I'm gonna give it a shot, but I like the idea.  The only problem I am now worried about is other emulators.  I have seen threads where guys say SNES for example goes to a 640x480 I believe.

Hiub1

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 439
  • Last login:June 05, 2011, 11:43:25 am
  • www.sleepyjack.com
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #4 on: June 08, 2006, 01:00:16 pm »
Why would Mamewah not work on a component TV anyways? Did you get it to work in non interlaced mode or something? And what is going on with the 2 screens? That looks neat!

mccoy178

  • It's hard to work with a straight jacket on
  • Trade Count: (+9)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3127
  • Last login:September 03, 2021, 10:23:42 am
  • Go Bucks!
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #5 on: June 08, 2006, 02:40:12 pm »
Why would Mamewah not work on a component TV anyways? Did you get it to work in non interlaced mode or something? And what is going on with the 2 screens? That looks neat!

Because my resolution was 640x432.  If someone didn't know that they had to grab the layout designer from 1.61 if they are using 1.62, then there is a headache.  My issue came from having the wrong refresh rate.  60 didn't work, but 30 did.  With 60, the screen was split in two and it took me a minute to figure it out.  Just trying to save some headaches.  If you are interested, click on the pic in my footer.  I made a dual screen cabinet much like the Golden Tee Live cabinet from IT.  I'm just now getting to the software end of things.

Hiub1

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 439
  • Last login:June 05, 2011, 11:43:25 am
  • www.sleepyjack.com
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #6 on: June 08, 2006, 04:07:51 pm »
I know ArtMAME has a component TV in his cab, and I don't think he had any problems loading MameWah on there. If anything, an easy way to change the resolution and refresh rate on the layout is just to open the .lay file with notepad and you'll see the first 3 rows of numbers there correspond to the resolution and refresh rate. Just change those to your delight and you should be good to go!

mccoy178

  • It's hard to work with a straight jacket on
  • Trade Count: (+9)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3127
  • Last login:September 03, 2021, 10:23:42 am
  • Go Bucks!
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #7 on: June 08, 2006, 06:05:20 pm »
Well, there ya' go.  An acceptable way to change resolutions on a .lay. :applaud:  Another member asked me to tell how I did it if I got it to work, so thus the thread.  You would still need the layout editor to adjust the information boxes.

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:July 13, 2025, 11:38:27 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #8 on: June 08, 2006, 06:07:39 pm »
I'm curious, does mamewah lock the aspect ratio of a layout or does it just stretch to fill the screen?  I do the latter and it seems to work well because people with odd aspects still get a full screen. Mind you it might be slightly distorted, but that can be adjusted in the skin.


I think this is just an overscan issue though, ie the layout is being displayed properly but part of the picture is beyond the visible range of the monitor.

mccoy178

  • It's hard to work with a straight jacket on
  • Trade Count: (+9)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3127
  • Last login:September 03, 2021, 10:23:42 am
  • Go Bucks!
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #9 on: June 08, 2006, 06:11:09 pm »
Yes, that is the issue entirely.

hypernova

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2753
  • Last login:November 25, 2016, 12:52:48 pm
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #10 on: June 08, 2006, 06:59:07 pm »


Me being a grammar ---smurfette---, that capitalized "G" would bother me to no ends...Fix that! ;D

I have component as well, as I followed skadar's thread.  I personally used 640x480.  I don't see why you need the 432.  Using the TV service menu along with Powerstrip makes overscan almost disappear.  (You can't use Powerstrip to make it perfectly fit, because the picture will screw up once you try to make it small enough.)  Plus, as Howard said, you can just move the layout parts a tad inward to compensate anyways for Mamewah.  All in all, I'm happy with my very small overscan.
I'll exercise patience when you stop exercising stupidity.
My zazzle page.  I've created T-shirts!

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:July 13, 2025, 11:38:27 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How I was able to get mamewah 1.62 to work on my component t.v.
« Reply #11 on: June 08, 2006, 09:06:37 pm »
Me being a grammar ---smurf---, that capitalized "G" would bother me to no ends...Fix that! ;D


That's not a capitalized g, it is a small letter g.  LED signs don't have under-hang for p's q's and g's so they look like that. 


Btw...

You can compensate for overscan in mame by using artwork files as well. There's a thread I made over in the monitor forum a while back.