[4.1-Unstable] Bug reports

[jackalpret]

I'm having troubles with audio output in pc 64bits version of recalbox 4.1 unstable.
In desktop computer I tried with mini jack output and hdmi ... but the "menu options" shows volumen in 0% and I tried to change output but noone works ...

If I open console (ALT F4 and ctrl alt F2 or F3) I saw:
lvl0: VolumeControl::init() - Failed to find mixer elements!

That the only message that I can read about sound ...

[azvarel]

@Substring

After I put the command appeared this information and it has been 15min and so far it has not given any more.
['/usr/bin/reicast.elf', '/recalbox/share/roms/dreamcast/Daytona USA - DCRES.cdi']
Powering on HDMI with explicit settings (DMT mode 9)

[azvarel]

@Substring

https://pastebin.com/aBVzWT08

[Substring]

@jackalpret the next unstable should allow to select the audio output

[Substring]

@azvarel it's definitely using ALSA. Except a volume set to 0% (check with alsamixer), i have no idea why this is happening

[azvarel]

@Substring

[Substring]

@azvarel no idea then

[azvarel]

Is this problem on my television?

I went to see if she had compatibility with DMT

tvservice -m DMT

Group DMT has 19 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
           mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive
           mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
           mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive
           mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
           mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
           mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
           mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive
           mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive
           mode 32: 1280x960 @ 60Hz 4:3, clock:108MHz progressive
           mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive
           mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive
           mode 39: 1360x768 @ 60Hz 16:9, clock:85MHz progressive
           mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive
           mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive
           mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive
           mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive

in recalbox.conf is:

## Dreamcast emulator
## Like N64, such a CPU intensive emulator needs a small resolution
## Consider DMT 4 HDMI or DMT 9 HDMI. Mode 9 is selected for a better screen compatibility
dreamcast.videomode=DMT 9 HDMI

replaces in dreamcast.videomode=DMT 9 HDMI with dreamcast.videomode=default

reicast opens in CEA, in 4: 3 and with sound, however with many freezes in the games and choking in the sound

The gameplay was disgusting

This is Satan's thing, disrupting my gambling.

Did I have any idea, @Substring ?

[Substring]

@azvarel setting to default makes you run reicast at 720p, which will be of course a pain for the pi cpu and gpu. That's why we force a lower resolution. You could eventually try DMT 4

anyway, don't expect too much from reicast on a pi3, there are only very few games that will give a good gaming experience. Not only the emulation is hard, but the overall compatibility is not so good.

[azvarel]

I put it on DMT 4 and also the sound did not work, so I put it on DMT 10 and to my surprise it worked perfectly the gameplay of Ikaruga and Marvel vs Capcom 2 is fine

The odd thing is it's running at 72Mhz well instead of 60Mhz, though this my samsung tv is old for over 10 years, I believe this is it.

Thank you for your patience and dedication, @Substring.

[jackalpret]

@Substring said in [4.1-Unstable] Bug reports:

@jackalpret the next unstable should allow to select the audio output

thats a very good notice ! thanks and thanks !

[Substring]

@jackalpret though you may need to manually set the sound volume in àlsamixer`because i never ever could find a way to link an audio device with its mixer(s) (and on PC, that's even worse : a device can have several mixers, what a pain)

[jackalpret]

@Substring said in [4.1-Unstable] Bug reports:

@jackalpret though you may need to manually set the sound volume in àlsamixer`because i never ever could find a way to link an audio device with its mixer(s) (and on PC, that's even worse : a device can have several mixers, what a pain)

but I tried to change in menu of ES ... but nothing happend.
Did You tellme that I need to enter via ssh and try to change output with alsamixer ? I can test it ...

[Substring]

@jackalpret yup : SSH > alsamixer (sadly ...). That would just show you which audio output is active, you definitely some changes inside recalbox to make this "saved" and survive after reboot (this, at least, will come the the audio output selection)

[azvarel]

1. controller snes30 8bitdo firmware 2.70
I can pair but if it hangs up for lack of use or if you turn off rpi3 the pairing is lost

After this last unstable update, the controller was finally paired even after shutting down the rpi3

Solved!

[azvarel]

@Substring

When it is inside the reicast and the control turns off (be it bluetooth or xbox 360) you can not continue the game anymore, having to restart the recalbox.

[Substring]

@azvarel just kill the process with SSH, don't unplug the power cord ...

[azvarel]

@Substring I do not pull the power cord, I have a reset button in my #SNESProject

[azvarel]

My brother's wifi key starts with 0 (zero) the recalbox for some reason, removes this initial 0 and leaves the correct remaining sequence.
I had to change the wifi key on the router so that the recalbox could connect

[Chris Johnson]

My bugs ive ran into using latest unstable version, off a RPi3

Dreamcast Emulator:

• Couple of games crashed on me during setting up the current date and time for controller
• Lags, frameskips

PPSSPP Emulator:

• VERY SLOW!!! Havent been able to play any roms because of how slow it is.
• Even changed the settings to max performance and barely reached 16 frames.

Moonlight

• Paired, scraped the roms, worked the first time. shutdown console, hasnt worked since. tried to pair again after removing device from nvidia and doesnt work. checked moonlight.conf everything looks right. so its a bug im assuming.