Page 3 of 23
Re: Testing MrMC 3.7.1
Posted: 25 Oct 2018, 16:52
by davilla
The libsmb2 bump/changes are rather important for the future.
In MrMC 4.0, libsmbclient will vanish
There will be only libdsm for smb1 usage and libsmb2 for smb2/3 usage.
Re: Testing MrMC 3.7.1
Posted: 25 Oct 2018, 17:49
by cosmoxl
davilla wrote: 25 Oct 2018, 16:52
The libsmb2 bump/changes are rather important for the future.
In MrMC 4.0, libsmbclient will vanish
There will be only libdsm for smb1 usage and libsmb2 for smb2/3 usage.
Re: Testing MrMC 3.7.1
Posted: 25 Oct 2018, 20:33
by Andi75
Hello Koying and the mrmc team!
I use a lg oled55e7n with built-in dolby atmos soundbar and ShieldTV.
Passthrough without iec
Unfortunately, the TV shows only briefly the Atmos logo then the sound starts to stutter the Atmos logo disappears and the TV remains silent.
Under Spmc it works great. Maybe you can help?
I hope google translate translates understandable.
Thank you
Re: Testing MrMC 3.7.1
Posted: 26 Oct 2018, 10:32
by Ted377
Andi75 wrote: 25 Oct 2018, 20:33
Hello Koying and the mrmc team!
I use a lg oled55e7n with built-in dolby atmos soundbar and ShieldTV.
Passthrough without iec
Unfortunately, the TV shows only briefly the Atmos logo then the sound starts to stutter the Atmos logo disappears and the TV remains silent.
Under Spmc it works great. Maybe you can help?
I hope google translate translates understandable.
Thank you
I think you will be better helped
here!
Re: Testing MrMC 3.7.1
Posted: 26 Oct 2018, 12:20
by Andi75
Oh, thank you
Re: Testing MrMC 3.7.1
Posted: 26 Oct 2018, 15:00
by davilla
ok, time to get serious... At this time, we have 50 users in this testflight and have only heard from 10.
The reason we have a Testflight is for fixing issues and testing to make sure we don't break something in the process. If Testflight users do not provide feedback, then doing Testflight is just a waste of our time...
If you have no intention of providing feedback, do not request entry into Testflight. This is a warning. We will be trimming Testflight users again soon. If you have not posted feedback, you might get trimmed.
Re: Testing MrMC 3.7.1
Posted: 26 Oct 2018, 18:06
by TheBrother
If there is a bug - I will post it - be sure of it. But if there is no bug and everything works fine should I just respond with "All is fine"?
Also if the application crashes don't you get more info on Testflight with more users in it?
Re: Testing MrMC 3.7.1
Posted: 26 Oct 2018, 18:20
by amet
TheBrother wrote: 26 Oct 2018, 18:06
If there is a bug - I will post it - be sure of it. But if there is no bug and everything works fine should I just respond with "All is fine"?
Also if the application crashes don't you get more info on Testflight with more users in it?
We do get info from crashes but we fixed quite a few bugs and it would be good to know that those fixes didn’t make a mess in other areas... so a quick “plex works... that’s all I use” would be good so that we know people are actually checking it ...
We obviously see no issues on our setups, the issues we see are the easiest to fix since we can reproduce, but different setups that users have might trigger different bugs
Re: Testing MrMC 3.7.1
Posted: 26 Oct 2018, 18:36
by Ted377
davilla wrote: 26 Oct 2018, 15:00
ok, time to get serious... At this time, we have 50 users in this testflight and have only heard from 10.
The reason we have a Testflight is for fixing issues and testing to make sure we don't break something in the process. If Testflight users do not provide feedback, then doing Testflight is just a waste of our time...
If you have no intention of providing feedback, do not request entry into Testflight. This is a warning. We will be trimming Testflight users again soon. If you have not posted feedback, you might get trimmed.
Does not make sense otherwise. In addition, Apple also releases only a limited number of beta testers.
Re: Testing MrMC 3.7.1
Posted: 26 Oct 2018, 19:37
by Ted377
davilla wrote: 25 Oct 2018, 02:25
(181024.2339 @20181024-a83b6d5)
smb2: sync to upstream
smb2: add browse for server shares
smb2: hide “Windows network (
SMB)” if smb2 is used
smb2 is actually only interesting for Win10. Or am I wrong ? Concerning smb1 I have "still" no problems