JellyfinTv Zidoo-Edition support post

Discussion in 'Jellyfin for Zidoo' started by andy22, Jun 18, 2022.

Tags:
  1. andy22

    andy22 Active Member

    Ah right, yes forgot about this.

    The new API also has no netbios/name resolution lookup, so use the server ip and it should work. I have no clue why i was told that the new API only supports ip's, since they clearly have already added the jcifs library for the older code path. I will try add jcifs myself, which seems kinda overkill just to get the name lookup, but as this case shows, users expect tobe able to use the names not just ip's.

    It has the new API.
    Easy test, just disable direct path and if you see a backdrop loading image than the FW has the new API, since this was added just there.
     
    Sledgehamma likes this.
  2. mattmarsden

    mattmarsden Active Member

    Perfect, that sorted it. Thank you!
     
  3. nc88keyz

    nc88keyz Active Member

    Is loading backdrop the movie logo art? before the movie plays ..?
     
  4. andy22

    andy22 Active Member

    Yes, need to see if we can add the jellyfin logo banners to the player overlay as well, since that's what the native jellyfin playback Ui would also show.
     
  5. mrgo

    mrgo New Member

    Further testing...

    Tried to migrate from NFS to SMB per earlier remarks

    Zidoo is throwing back SMB not mounting for 'Pass Direct Path for external player' without Legacy settings? (example path below)

    smb://zidoo:xxxxxx@192.168.1.xxx/volume1/Documentaries

    Fallen back to NFS with Legacy Settings and playback working. However if 'Pass Direct Path for external player' is ticked and 'use legacy Direct Path' is also ticked then .mp4 and .mkv files playback but .avi files are throwing a 'cannot play file' error
     
  6. andy22

    andy22 Active Member

    mhh smb path looks fine, not sure about the .avi case, need to test this myself.

    PS: BTW the default http stream logic should work fine for normal files, so mounting via smb/nfs network paths should only be needed for BR-disc folders?
    Can beta-users share why they need/want to use smb/nfs over http?
    I think i can detect BR cases and add a option that will only fallback to smb/nfs mounting if needed?
     
  7. mattmarsden

    mattmarsden Active Member

    My experience has been that seeking the file is quicker with SMB than http.

    edit: actually http seems to be just as good as smb now
     
    Last edited: Jul 22, 2022
  8. mattmarsden

    mattmarsden Active Member

    I've just found a bug with http mode - with grouped movies it will only play the first movie even if I select the other one. With SMB it will play which ever version I choose.
     
  9. mrgo

    mrgo New Member

    PS: BTW the default http stream logic should work fine for normal files, so mounting via smb/nfs network paths should only be needed for BR-disc folders?
    Can beta-users share why they need/want to use smb/nfs over http?

    Please find some real world stat's from my Synology NAS running Jellyfin in Docker

    Prior to playback: CPU (Container) is 0.28%

    Playback via NFS (Direct Play) - CPU (Container) stays at 0.28

    Playback via HTTP - CPU (Container) jumps to 14% (Transcoding Message)

    File size tested was a 2GB Mp4 Movie (1080p rip with aac)

    Overall NAS CPU is 4-5% but rises to 18% with HTTP

    Notes

    There is a difference with processing MKV Files (H265) vs MP4 (H264). With Pass Direct for External Player (unticked) and Use Legacy Direct Path (ticked) - the MP4 (H264) file throw a Transcoding Message while the MKV Files (H265) show a Direct Play message. Please not that I have no Transcoding Enabled Client or Sever Side.

    However if Pass Direct for External Player (ticked) and Use Legacy Direct Path (ticked) then the MP4 (H264) file plays back as Direct Play?
     
  10. mattmarsden

    mattmarsden Active Member

    Does the MP4 file have DTS sound and have you ticked that your receiver is DTS compatible?
     
  11. mrgo

    mrgo New Member

    No DTS.. AAC Only for the MP4

    DTS Sound on the App not ticked and receiver can decode DTS. DTS-MA, etc
     
  12. andy22

    andy22 Active Member

    Is it a 5.1 AAC track or stereo?

    If it's a 5.1 AAC you need to tick the "Enable none bitstream surround codecs" option, otherwise the audio gets transcoded into a 5.1 AC3 stream.
     
  13. andy22

    andy22 Active Member

    So what are the stats comparing nfs vs http on the same direct-play mkv file?
     
  14. mrgo

    mrgo New Member

    MKV - 30GB HDR 2160p

    With MKV with 'Pass Direct Path for External (unticked), Use Legacy Direct Path (unticked) and a All Transcode Fallback (unticked) - the user message shows 'Direct Play' and does not evoke HTTP stream like in previous Beta versions of the software?

    Both 'Pass Direct Path for External (ticked), Use Legacy Direct Path (ticked) and a All Transcode Fallback (unticked) and 'Pass Direct Path for External (unticked),Use Legacy Direct Path (unticked) and a All Transcode Fallback (unticked) yield the same cpu container results of

    - NFS:0.31% (Container)
    - HTTP: 0.31% (Container)

    However the CPU (NAS), shows a rises for 3% to 10% then drops to 6% with 'Pass Direct Path for External (unticked),Use Legacy Direct Path (unticked) and a All Transcode Fallback (unticked) and for Pass Direct Path for External (ticked), Use Legacy Direct Path (ticked) and a All Transcode Fallback (unticked) it stays at 3%
     
  15. andy22

    andy22 Active Member

    I mean, the br-disk/folder handling is enough for me to try fix all DirectPath related issues, since that's why many users bought a Zidoo in the first place.
    Its just a bit messy atm, with the old API having fully working SMB/NFS, while the new API still has some issues with NFS paths and need's IP's, sorry for the more confusing options as a result.

    So if you encounter issues atm, maybe temporary give http streams a try, since this bypasses all the smb/nfs mount logic.
     
  16. mattmarsden

    mattmarsden Active Member

    Any ideas why the grouped versions doesn’t work with http?
     
  17. andy22

    andy22 Active Member

    Net yet, had no time this weekend to work on jellyfin. Need to check whats going on.
     
  18. mattmarsden

    mattmarsden Active Member

    Thanks Andy, really appreciate it.
     
  19. mrgo

    mrgo New Member

    Will do and thanks for the status update regarding the new API having issues. Thanks again for all your Hard work. Much appreciated

    In relation to the trailer functionality, how is this aspect progressing?
     
  20. andy22

    andy22 Active Member

    I'm doing this in my spare time, so atm i focus on bugs. The trailer issue is a general JellyfinTv issue, so maybe can be fixed by upstream.
     

Share This Page