Open koying opened 7 years ago
Kodi 17.4 is getting released at the end of the month. I thinking why would you not wait for the bug fixes that comes with 17.4 and then release SPMC. I'm thinking sometime in August depending on his work and personal schedule, since he is only one man Sent from my BlackBerry - the most secure mobile device - via the Koodo Network From: notifications@github.comSent: July 22, 2017 9:16 AMTo: SPMC@noreply.github.comReply-to: reply@reply.github.comCc: atkelly1@telus.net; comment@noreply.github.comSubject: Re: [koying/SPMC] Test builds for SPMC 17 (Krypton) (#936) Why do you think that?
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
As above 99rook99. Let's await Kodi Team's release of 17.4 and @koying can then realise SPMC version.
New build in the folder dated today.
Takes me to a 404 page saying no link
hmm try the folder link already given above:
Build updated:
Before you ask, no, there is no way to browse for SMB servers when SMB3 is activated, only with SMB1. When using SMB2/3, you have to enter ther server address.
@classicjazz
Another bug: you are supposed to define your MySQL config in advancedsettings.xml.
That GUI takes precedence over AS was already in 16, just that you probably didn't notice ;)
For all those who reported issues with the Alpha, I surely lost it in this thread. Please open separate issues with a "[SPMC17]" prefix and tag
Given that HQ Scalers are back, what are the recommended settings for 4K and HDR on NVidia Shield?
cant connect to smb with this build...
Amilogic S905X 2GB 8GB box. New build fail to start. Back to the RC1.
The latest update on spmc17 crashes on startup
"It crashes" without logcat is useless. Obviously, it doesn't crash for me...
Doesn't crash for me either
That's weird, I test it on my phone and my amlogic s905 Qbox android box and it does crash on both of my devices for me. When i launch the app it will load on the spmc loading screen for a second, then it will just exit out of app. I didn't have this problem on the last alpha build update which was on july 3rd.
@koying
Thank you so much for adding Samba 4. I disabled SMBv1 on my Synology NAS and it works very well, with no changes required on either NAS or Shield to support SMBv3. In theory the performance improvements should justify using this as a preferred networking protocol.
I plan to test the HQ scalers to see if Lanczos 3-Optimised is still the best or if we should switch to Lanczos 3 (which logically should work better).
What's lanczos optimised best for?
S905X TV Box Android v6
Black screen with sound when playing 8bit h.265, 10bit plays fine, we had this problem before when amicodec was enabled, but it was fixed now the problem is back.
For video upscaling, it is covered here: http://kodi.wiki/view/Video_playback (video scaling methods).
In theory, Lanczos3 should be sharper than Lanczos3 Optimized. (It uses a 6 tap rather than 4 tap filter). In practice, for SPMC 16, Lanczos3 Optimized was much sharper than Lanczos3 at least on an Nvidia Shield. I am retesting now with SPMC 17 and the latest version of Android TV software.
If you really want to dive down the rabbit hole, here are a few more links: https://github.com/mpv-player/mpv/wiki/Upscaling
https://forums.plex.tv/discussion/188836/high-quality-video-rendering-planned
https://github.com/mpv-player/mpv/blob/master/video/out/opengl/video_shaders.c
(MPV on Android is much further along than Kodi. Not just in terms of upscaler optimizations but also preliminary work to switch from OpenGL to Vulkan for better upscaler performance).
Graphics downscaling (for assets using a 4K GUI) is different. My understanding is that it currently uses bilinear and should at least use bicubic for downscaling from cache. https://forum.kodi.tv/showthread.php?tid=200401&pid=2150625#pid2150625
@TinderboxUK you just have to disable Amlogic acceleration codec : open settings/ video acceleration and uncheck the first acceleration codec you will use only the two other media codec and surface Amlogic codec are good for S912 device, its a good thing they reappear ...
@koying SPMC 17 crash on start with logcat.
My 10c worth (and relatively minor issues compared to what others have). Have just installed and run the latest SPMC. Australian OZ Weather addon with Advanced Features and updated DialogSeekBar and MyWeather xml replacing original files no longer causes SPMC to crash at Startup. However the radar sequence in this addon does not show the topography background. Secondly Merlin Auto Cleaner Addon won't start and comes with an error message at Startup.
Hi. until today I had shared folders that worked with SMB1 and SPMC until today. 1. today's build changed to SMB3 protocol by default. with this way I couldn't connect to my shared folders. so I went and change the setting "Maximum Protocol Version" of the SMB settings to "SMBv1". now comes the problem. I still cant connect to my shared folders. even if I try to manually set a shared folder in SMB1 I got a screen says Lock Preferences in SMB and asks me for a username and pass. I have to say that I don't have a username/password in Windows 10. in Sharing settings I have the username/password at off. how to make it work again at SMB1? any help?
@classicjazz
I plan to test the HQ scalers to see if Lanczos 3-Optimised is still the best or if we should switch to Lanczos 3 (which logically should work better).
To me it seems like Lanczos 3 (and Spline36) have no effect / don't work (on a Nvidia Shield TV) - but the "optimized" variants do. Wonder what your experience is.
Do we still have to turn Mediacodec Surface off to get the HD Scalers? Since Surface engages HDR for 4K is there any chance in the future they can all work together?
I thought I would copy/paste addons and userdata folders from the new SPMC over to Kodi Krypton 17.3 on my Shield. I did so and found the two hassles I mentioned above (Merlin Auto Cleaner and Oz Weather) worked perfectly in Krypton 17.3. Usually my SPMC setup is around 290MB. During the copying over of files I saw the total size of the new SPMC setup was now 1.3GB. In it was a wizard.log file measuring 1,048, 577KB. I deleted this file and restarted the new SPMC. The wizard.log file returned at its original size after the SPMC restart.
I ran Kodi 17.3 (290MB) which started fine and then shut it down. Checked the Kodi files and still 290MB. I did a search again for the Wizard.log file in Krypton and found it at 1.45kb.
Back to the July 3rd SPMC for me.
Eventually I totally uninstalled SPMC. Reinstalled the July 3rd SPMC and copy/pasted from an SPMC backup I made prior to anything I did this morning. Ran SPMC July 3rd and all worked OK again. Shut down the reinstalled SPMC and checked the wizard.log file and saw it was around 98kb now rather than the 1MB it had been.
Latest build crashes on my firetv but works perfect on my shield TV. I'll try tomorrow to get logcat for you as I'm about to sleep now .
There is an issue of circular dependencies with the newest Samba on Lollipop/Android 5 devices (like the FireTV). See https://github.com/koying/SPMC/issues/963 for tracking.
Those should stay out of the latest alpha
The latest build no longer engages HDR for 4K material; however the prior 17.3 version from July worked fine with that.
@koying not sure if you could help, when using spmc jarvis it no longer auto marks something as watched in trakt and then displays the next episode as a widget like it used to, yet krypton does it just fine! Any ideas?
Forgive my ignorance - if it's only me - but for the benefit of those of us who can't figure out what's going on with SMB, Windows 10 sharing and Kodi right now, could someone please give us a crash course? Thanks
you are not alone in this Gertbucket. I have the same problems as u. I cant make it work with latest build and Windows 10. neither SMB3 or SMB1. someone can help us please?
@Gertbucket Same issue here, I have to import my old backup to make this build work through SMB1. If I try to configure manually my SMB1 or 3 it will not work. And even imported sometimes I can not log in in my windows SMB1 account...
I have folders shared on up to date Windows 10. Shares are working, but I don't know which version of SMB.
Kodi/SPMC/SPMC 14 RC1 all work but need to enter more specific host details than previously (doesn't see Workgroup). Running Fire TV so not touching latest alpha.
What I don't understand is the prevailing advice that I'm seeing is to disable SMB1, but the instructions I keep seeing appears to disable all SMB. I've also read Microsoft has already phased out SMB1, but that doesn't appear to be true. Trying to figure out what the advice is for those of us wanting to continue using Windows folder sharing.
What I don't understand is the prevailing advice that I'm seeing is to disable SMB1, but the instructions I keep seeing appears to disable all SMB. I've also read Microsoft has already phased out SMB1, but that doesn't appear to be true. Trying to figure out what the advice is for those of us wanting to continue using Windows folder sharing.
SMBv1 is decades old, slow, complex, and has security holes.
SMBv2 (introduced ten years ago with Vista and Server 2008) is a complete rewrite that simplifies the protocol and is better suited, performance-wise to video file serving (including large reads and pipelining). SMB 2.1 supports large MTU.
SMBv3 adds more performance improvements and end-to-end encryption.
So, the intent is to preserve Windows folder sharing as the default. Just using a later version of the SMB protocol. Indeed, SMBv2 or v3 would be preferable over NFS due to user authentication.
Koying's updates bring SMBv2 and v3 to Android.
NFS has authentication as well... would love a performance benchmark between all versions of NFS and SMB. NFS seems to have less overhead, easy to setup, but since I got a Synology... wouldn't mind to switch.
Gertbucket to see your Workgroup in Windows 10 latest 1703 15063.483 fully updated you have to put another device as Master. if Windows 10 set as a Master you cant see Workgroup. its a bug in Windows 10 that hopefully will be fixed by Microsoft. I set a router that has a usb port as a Master with just putting a usb memory stick. you can check which is Master with this program. u just run it. https://scottiestech.info/download/LANscan_v1.68.zip
If your client PCs/Macs connect to your Synology NAS, then you likely have SMB enabled by default. You can enable NFS too for Kodi/SPMC but that adds overhead, potential security issues, and network management complexity.
The difficulty securing NFS is covered well here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/Reference_Guide/s1-nfs-security.html
For SMB3 v NFS4 performance, particularly reading large files, see here (starting pg 28): http://2016.texaslinuxfest.org/sites/default/files/slides/Texas-Linux-Fest-2016-Future-of-NAS-draft5.pdf
Note: does Kodi/SPMC support NFSv4 on Android yet?
Here is how I have configured my NAS now that SPMC supports Samba v4:
Synology DSM 6.1 is running samba 4.4.13.
Under advanced SMB settings:
Under Advanced (SSDP):
For more, see here: https://www.synology.com/en-us/knowledgebase/DSM/help/DSM/AdminCenter/file_winmacnfs_win
New build, fixes crash on start on FTV
I just tried new build. http://download.semperpax.com/spmc/android-arm/SPMC-spmc-krypton-1f5c175-armeabi-v7a.apk I have same problem. i was using 3rd July build and all worked fine. I installed this latest build and changed the setting "Maximum Protocol Version" of the SMB settings to "SMBv1". it doesn't work. mr.Koying how can I help you to fix this problem? please check this your self in Windows 10 to reproduce the problem so to understand and fix this. thank you!!!
@djstx2003 Please stop duplicating all your posts. I got your point. I'll do tests when possible.
Unfortunately, I also have to manage details like day job, family, ... above SPMC.
I have a Minix Neo U1 (based on Amlogic S905) under Android 5.1.1, with Kodi 17.3 playback suffers from bad jitters.
I tried loading SPMC-spmc-krypton-5e3c0fc-armeabi-v7a.apk
and it installed all right, prepared itself for first run but then silently quit. Further attempts to run it just immediately quit without error messages.
I then loaded SPMC-spmc-krypton-3295bca-armeabi-v7a.apk
, it worked without unexpected quits. I also tried upgrading this to the later version, in case it was the "first run" code which failed, but it still failed to work the same way as earlier. Downgrading to the earlier version also restores functionality. How should I try to debug what is happening here?
Now for the actual beef: video playback results are somewhat mixed. 720p or 1080p videos typically start all right, but after a while (skip/ff, or maybe even scene change) will develop the jitters. This can be rectified by stopping playback and resuming it again. I seem to remember some problems like this already under Kodi 16, but I don't think they started on their own, only by skipping. Suggestions?
Fire TV2: Can't access SMB. Error: Operation not permitted.
@ExTechOp
A wild guess regarding stuttering playback: it's the network ... in case you've set up network buffering, you may also have to adapt your advancedsettings.xml
- with v17 some things did change there - for an example see here.
@ExTechOp
The Minix Neo UI had a firmware update released on Thursday. The release notes seem to address issues that you raise including changes that they made to their custom builds of Kodi 16 and 17.
http://minixforum.com/threads/neo-u1-fw013-20170629.17083/
Ideally, they would upgrade to Nougat instead of crafting proprietary Kodi builds on 5.1
@djstx2003, in you windows pc go to the users folder and check name of the folder of your user, then insert in kodi, with the password of the account, using SMB V1. its worked for me.
Thanks RisingStar1 but I already found the solution here by ziggy73701: https://github.com/koying/SPMC/issues/961 now running SPMC latest with SMB3 protocol.
@koying I'm currently running the latest build on my 2015 Nvidia shield TV. I can't set the GUI to 4k. I've changed the setting to unlimited but I only get 1980 resolution. Is 4k GUI supported by the build or is it skin related? I'm running fuse(Neue)...
I would test it with another skin and double check your Shield didn't somehow switch from 4k back to 1080.
As the tile says.
20171202: 17.6 Alpha 2 http://download.semperpax.com/spmc/android-arm/SPMC-17.6a2-spmc-ed022ef-armeabi-v7a.apk