@mitu said in No Audio From Samsung Tizen Smart TV:

Can you post the output of

aplay -l aplay -L

Output for aplay -l and aplay -L.

Use alsamixer and make sure the audio is not muted and/or the volume is set to something like 50% to hear something.

Tried AlsaMixer although I was a bit confused to how it worked. It was set to 66% with HDMI listed at the bottom. I pressed F3 for [Playback] thinking that was to test the audio but again, nothing coming out of the TV. I've double checked that it's not muted and the volume is turned up to a reasonable level.

I'm confused on what you thought that would be required. I think the noaudio option is clear enough on what it does.

I'm completely ignorant to computing, so when I was looking for a fix to the visual tearing through the kms video driver, every example code I saw online for that driver included the noaudio line. I felt it was best to follow those examples to the letter and not remove it, even though it stuck out as odd. Because it never interfered with my audio playback, I didn't think to question it afterwards.

EDIT: My apologies, I'm actually going to have to pack this in for now and return to it tomorrow. Fingers crossed for better results and a clearer head!

@mitu Thanks, that appears to have worked! Now the fun of getting SM64 to run smoothly.

Thanks!

@pojr said in RetroPie stuck in 4:3 (the interface, NOT the games):

@dankcushions
I don't think it would be 81, but you are correct that it's wrong. Shouldn't be 16 because my TV only displays up to 720p, not 1080p. Although it is a 16:9 TV (not 64:27 like it shows under #81). Also, my TV frequency isn't 30Hz, unless I'm missing something.

you've fixed it now so i guess this is irrelevant but yes, you'd need to use hdmi_group=2 for 81 - it doesn't seem to be supported under 1. but yes, @mitu 's suggestion would get show you the complete list of supported modes. given that it's less than 4k, i would always want to be running in the native panel resolution so you don't get scaling artefacts.

i assume now you've taken out hdmi_safe you can safely take out any hard coded modes and it should hopefully choose 1366x768 by default.

You can modify /boot/config.txt and add the following:

hdmi_group=2 hdmi_mode=68

See https://www.raspberrypi.org/documentation/configuration/config-txt/video.md for a list of supported video resolutions that can be set via config.txt.

I ran that and the tvs preferred res is group 1 mode 4 changed it in config.txt to that setting still nothing

A half related question :

While SD cards are awesome for size/weight/etc., how much of a speed advantage would using an external hdd be? I can't imagine an ssd adding any value over a simple 2.0/3.0 mechanical drive being that the transfer rate is bottlenecked by the shared usb 2.0 bus which apparently is divided up by the all ports and the sd card reader. Is a top of the line sd card just as good as an external hard drive or are there any advantages?

I don't want to start any arguments so if a mod can delete this whole topic please?

@rrs run the command in the post directly above yours. It tells you how to do it.

@jnbui79 Any update? I am having this identical issue on my Samsung set. RetroPie works perfectly on every other TV I try it on.....

Please let me know. Thanks!

-Craig