Crackling Sound mame2003
-
@grant2258 Final fight is the worse.
-
@und3r6r0und So your power supply is ok which leads you to the HDMI cable and settings next. I use the 3.5 jack and have never had crackle unless you are stressing the CPU with games that can't be handled by the hardware.
-
@rbaker May I ask what application makes the 3.5mm jack a preferable audio source? Do you run Retropie on a monitor without sound? I've always wanted to use it for a purpose to say I've used all of the ports but on my television the HDMI handles it all.
-
@und3r6r0und ill compile the latest on the pi and test(i usually test on linux or windows for development). I just done some updates to mame2003 a few days ago ill make sure its isint that causing it.
Please make sure your using the latest mame from source.
update compiled the latest mame source and its all good my end on a pi3 b+
I had problems myself when using the audio jack our resident pi guru has advice on a fix for this.
https://retropie.org.uk/forum/topic/17828/rampage-sound-issue-retropie-4-4/3
-
@thedatacereal I use Retropie in an arcade cabinet with a 19" monitor. I then use a hacked apart old set of speakers with a built in amplifier. See this photo. This plugs straight into the 3.5 inch jack plug. Once you set up Retropie, there is a bit of tweaking to be done. First, I set the volume in setup to about 75%. I then edit the config files according to this link. I use 75% instead of 100% as the amplifier acts as a very good inline volume control. The results are of a high quality if the amplifier that you choose is decent in terms of both gain and noise suppression.
-
@BuZz here is one issue that would be solved by updating the mame2003 binary
-
@markwkidd Not sure if you are intentionally trying to wind me up ? You have tagged me in three different threads with the same message?
-
First I stared with a plain github issue. You asked instead to be tagged in the forums to help explain why I'm asking for a binary update. These are all threads that I'm monitoring because of issues relating to the build date of the mame2003 binary.
I could have just tagged you in only one of them, but then we might as well have talked about it in the issue. I apologize that my communication style is seemingly different than yours.
-
@markwkidd The issue tracker clearly says to use the forum first and if directed then open an issue. You ignored that when opening an issue.
I then asked you to tag me if you need something updated that you think is important. I also said I had already seen the thread. I didn't ask you to tag me three times with the same request in three different threads (with one being totally unrelated as it was already confirmed not a problem with the binary).
It's not difficult.
-
@BuZz said in Crackling Sound mame2003:
@markwkidd The issue tracker clearly says to use the forum first and if directed then open an issue. You ignored that when opening an issue.
I then asked you to tag me if you need something updated that you think is important. I also said I had already seen the thread. I didn't ask you to tag me three times with the same request in three different threads (with one being totally unrelated as it was already confirmed not a problem with the binary).
It's not difficult.
I would not agree that ignored those instructions and I find your tone very discourteous considering that we are peers -- both people who volunteer substantial amounts of time to helping make RetroPie a positive experience for users.
I'm not interested in arguing the nuances of whether I followed your instructions. I will simply say that -- as someone who also receives many notifications from users every day about my emulator work -- that your policies for how people can communicate with you are a little beyond the pale.
Please feel free to ignore me but I will tell you a fellow volunteer developer, I don't benefit from you taking the time to write me one sentence back if it is purely to critique my communication approach.
-
the less i say the better ive already been banned on the github page. I couldnt agree more ive never met such a discourteous attitude reminds me of people in london they have this exact superiority attitude. The further you get north from london the nicer the people are.
-
Hi guys, I'm experiencing the same problem with a pi0 and gpi case, the games executed through lr-mame2003 have crackling sound. In principle I though that it was a problem with the performance of pi0, but when I execute the same roms in lr-mame2000 the sound is perfect, and for compatibility issues, I want/need to use lr-mame2003 instead lr-mame2000.
Any idea? maybe I need an extra config.
-
@fumanxu i think it's very possibly a performance issue. even if they are the same games, mame2003 includes 3 years of emulation improvements over mame2000, so they cpu requirements will be more. this is why we recommend mame4all for pi0/1: https://github.com/RetroPie/RetroPie-Setup/wiki/Arcade#step-1-choose-your-arcade-emulators
-
@dankcushions my problem with mame4all is that is not based on libreto so I cannot configure the buttons via retropie/retroarch. How can I configure manually the buttons of the gpi case (in fact, it is using xbox 360 controller driver).
-
@fumanxu You can configure it like any other MAME based emulators - you can use a keyboard and access the configuration menu of the emulator.
-
Hi @mitu
My problem is that it's difficult to connect a keyboard in gpi case, so I was wondering if there is a way to configure via ssh the x360 controller in the mame4all config. -
@fumanxu it is not, but if you are getting ok performance in lr-mame2000 you can continue using that. it's the same romset and should only perform marginally worse. maybe imperceptibly so.
-
Yes, the problem with lr-mame2000 is that is not compatible with all games. :(
In any case I will try to configure the gpicase controller searching in the config files for mame4all
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.