I´m sorry where? Thanks
my fault, it’s called Active route
not Active source
. Try by disable this option.
I tried the setting but it doesn’t work.
Yes, I can add the source directly but just try to figure out why the discovery doesn’t work any more.
You can try deleting all your smb settings files and starting from scratch. A persistent setting can upset SMB. Just to be clear on my system I cannot browse a share via the Windows Network (SMB) source option and this is expected behaviour. I can however browse a share via the zeroconfig source option and this is the way I have always added SMB shares as sources.
Other than that I cannot think what happened, but i know that SMB is erratic at best in xxELEC’s.
Adding the source directly is the right way to do it in Linux, automatic discovery is a carry over from SMB1 which is over a decade old at this stage and has been deprecated because it opens a huge security hole in your whole home network. The only reason that SMB1 is still supported at all is because some servers and modems have it hard wired into their firmware.
Shoog
Windows-wise, I have close to none problem with ELECs SMB @Win7 @Win10, as long as minimum samba version is setuped at 2. (Win7 doesnt support >2, and 1 is insecure to that point that some KB’s disabling it within windows).
cd \\10.0.x.yyy
or persistent mapping to drive is what I am using on Windows clients.
Beelink GT King. Upgrade from 9.2.2 — severe frame drops. Choppy playback.
Returned back to 9.2.2 — everything is back to normal
Make an SD with a fresh install of 9.2.3
This will tell you if its the upgrade or a retained setting which is causingnyour frame drops.
Shoog
Tnx for meaningless info. In future take some logs of the problem so that your post has some meaning and we can see the cause for such abnormal behavior…
I set both the min and max version to smb 1.0 and then the discovery works.
several days (2-3 weeks) ago my Beelink GT King Pro player warned me about a new version of Coreelec. I have automatic updates turned on but it doesn’t update. Do I need to do it manually?
Go to settings/coreelec and download under 9.0 repo
@Portisch I have found a bug on vim3l with coreelec 9.2.2 & 9.2.3 (not sure if it existed before that). AAC is broken on ALSA: AML-AUGESOUND, HDMI. It has to be set to ALSA: AML-AUGESOUND, HDMI Multi Ch PCM.
All other audio formats work fine. Has this bug been acknowledged or is it a specific issue of the vim3l?
That is not a bug. The HDMI output is not capable of multichannel PCM, that’s what the HDMI Multi Ch PCM output is for.
OK, thanks for the swift response. I will have to research what that means further.
Is it possible for auto detection of AAC content and an output switch? Or is there a setting already existing for this that I have missed?
No. Set your output to HDMI Multi Ch PCM and forget it. It works just fine for L-PCM.
For passthrough you can keep HDMI selected at the passthrough section.
Ahh OK. So this will use PCM as default and then bitstream for Atmos?
I have tested AAC audio on this setting and the receiver shows PCM In (denon 6500h), Atmos shows as Atmos. All seems to be working fine just curious as I read that Atmos cannot be sent over PCM.
You can’t bitsteam AAC.
And you can ONLY bitstream Atmos. There’s no other way to get Atmos.
Thanks for confirming. My question is how is atmos being sent and received when I set PCM as per your suggestion?
I now have out set as ALSA: AML-AUGESOUND, HDMI Multi Ch PCM - I understand that this enables AAC to work but how is atmos working? This isn’t bitstream to my knowledge.
Passthrough works the same as before.