macnb 32 Posted July 10, 2024 Posted July 10, 2024 The problem appears to be with either the Version FFMPEG or the its Usage within Emby server to extract the thumbnail. If I run manually run the latest release version of FFMPEG on macOS on the same home-movie file as in the Emby Library, there's no problem extracting a thumbnail (and it's very quick). The version built into Emby server seems custom and an older version. I used this example: ffmpeg -skip_frame nokey -i home-movie.mp4 -qmin 1 -qmax 1 -q:v 1 -vframes 1 -update 1 thumbnail.jpg this basically extract the first frame from the key frame and tries to get the best JPG quality.
sa2000 674 Posted August 7, 2024 Posted August 7, 2024 (edited) @macnbI have a later build of ffmpeg emby server binaries which I can make available to you to try out To test, shutdown Emby Server , save copy of the current ffmpeg Emby Server binaries (ffdetect, ffmpeg, ffprobe) that are installed in /Applications/EmbyServer.app/Contents/MacOS and replace the 3 files with the ones I send you Let me know if you are to happy to do that and please let me know which you are running on: arm64 (M1 / M2 ) or intel x64 Edited August 7, 2024 by sa2000
macnb 32 Posted August 7, 2024 Posted August 7, 2024 (edited) 8 hours ago, sa2000 said: @macnbI have a later build of ffmpeg emby server binaries which I can make available to you to try out To test, shutdown Emby Server , save copy of the current ffmpeg Emby Server binaries (ffdetect, ffmpeg, ffprobe) that are installed in /Applications/EmbyServer.app/Contents/MacOS and replace the 3 files with the ones I send you Let me know if you are to happy to do that and please let me know which you are running on: arm64 (M1 / M2 ) or intel x64 @sa2000Thanks for the offer to debug this further. I am sorry but I should have been more clearer in that I am not running Emby server on macOS but on Debian Linux natively. I was just seeing if the newer FFMPEG (running on macOS) produced a thumbnail on the same file and it does. So, I just tried running the same (my syntax) command on Debian using the Emby's custom FFMPEG and it works very well (i.e. quick): root@omv:/export/d3/stora/downloads/test# /opt/emby-server/bin/emby-ffmpeg -skip_frame nokey -i home-movie.mp4 -qmin 1 -qmax 1 -q:v 1 -vframes 1 -update 1 thumbnail.jpg ffmpeg version 5.1-emby_2023_06_25 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 10.3.0 (crosstool-NG 1.25.0) Execution Date: 2024-08-07 16:57:48 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'home-movie.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf61.1.100 Duration: 00:12:16.30, start: 0.000000, bitrate: 10269 kb/s Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67, progressive), 3840x2160, 9938 kb/s, Level 153, 59.94 fps, 59.94 tbr, 60k tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] encoder : Lavc61.3.100 libx265 timecode : 00:03:53;14 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default) Metadata: handler_name : SoundHandler vendor_id : [0][0][0][0] Stream #0:2[0x3](eng): Data: none (tmcd / 0x64636D74) Metadata: handler_name : VideoHandler timecode : 00:03:53;14 File 'thumbnail.jpg' already exists. Overwrite? [y/N] y Stream mapping: Stream #0:0 -> #0:0 (hevc (native) -> mjpeg (native)) Press [q] to stop, [?] for help [swscaler @ 0xd0de00] [swscaler @ 0xd1ae00] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd0de00] [swscaler @ 0x1ae3e00] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd0de00] [swscaler @ 0x1b59e80] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1b86d80] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1b58540] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1ae9480] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1b86d80] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1b39d40] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1ac9a40] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1b86d80] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1b39d40] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0xd3a940] [swscaler @ 0x1ac9a40] deprecated pixel format used, make sure you did set range correctly Output #0, image2, to 'thumbnail.jpg': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf59.27.100 Stream #0:0(und): Video: mjpeg, yuvj420p(pc, bt2020nc/bt2020/arib-std-b67, progressive), 3840x2160, q=2-31, 200 kb/s, 59.94 fps, 59.94 tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] timecode : 00:03:53;14 encoder : Lavc59.37.100 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A elapsed=00:00:01.83 frame= 1 fps=0.5 q=1.0 Lsize=N/A time=00:00:00.01 bitrate=N/A throttle=off speed=0.00908x video:1495kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown EXIT root@omv:/export/d3/stora/downloads/test# So it looks like you need to look at how your are using FFMPEG to generate the thumbnail. The way I am testing above runs every time and is very quick. Let me know if you need more info. Edited August 7, 2024 by macnb
Todd43081 1 Posted August 7, 2024 Posted August 7, 2024 So is it fair to assume this will be fixed in an updated version and I can just wait for that?
Happy2Play 9780 Posted August 7, 2024 Posted August 7, 2024 (edited) 1 hour ago, toddgoodsite@outlook.com said: So is it fair to assume this will be fixed in an updated version and I can just wait for that? Unless this is a platform specific issue has a problem actually been found? But specific examples are needed as it does not affect all platforms that I can see. Edited August 7, 2024 by Happy2Play
sa2000 674 Posted August 8, 2024 Posted August 8, 2024 On 10/07/2024 at 21:28, macnb said: If I run manually run the latest release version of FFMPEG on macOS on the same home-movie file as in the Emby Library, there's no problem extracting a thumbnail (and it's very quick). The version built into Emby server seems custom and an older version Well this definitely indicated to me that you were running Emby Server on MacOS !! And I am also aware that the ffmpeg Emby binary we have on MacOS is older than what we have on other platforms 15 hours ago, macnb said: I am sorry but I should have been more clearer in that I am not running Emby server on macOS but on Debian Linux natively. OK - so will need to look at a specific example and if you can crop a home video you can share with us - perhaps a 1 minute video then together with debug enabled Emby Server log showing the failure on your system and the file used for the test, we can then troubleshoot the problem I know you said you sent a log to Luke but best to repeat the test wit a sample 1 minute video where Emby Server fails but your specific manual run using the same Emby Server ffmpeg binary works
macnb 32 Posted August 8, 2024 Posted August 8, 2024 22 hours ago, Happy2Play said: Unless this is a platform specific issue has a problem actually been found? But specific examples are needed as it does not affect all platforms that I can see. Yes logs submitted showed the problem with FFMPEG (within Ember Server running on Debian Linux) failing to extract thumbnails.
macnb 32 Posted August 8, 2024 Posted August 8, 2024 14 hours ago, sa2000 said: OK - so will need to look at a specific example and if you can crop a home video you can share with us - perhaps a 1 minute video then together with debug enabled Emby Server log showing the failure on your system and the file used for the test, we can then troubleshoot the problem I know you said you sent a log to Luke but best to repeat the test wit a sample 1 minute video where Emby Server fails but your specific manual run using the same Emby Server ffmpeg binary works I'll try. Changing the "sample" may not produce the problem. 1
macnb 32 Posted August 10, 2024 Posted August 10, 2024 (edited) @sa2000and @Luke Please find attached logs and a sample 1 minute video file (called trimmed2.mp4) that fails during Ember server scan. If I manually run the same command that Emby Server uses then it works fine....but that it takes ~ 1.5 MINUTES to run...maybe that's the problem where some process is not waiting long enough. See it run manually : root@omv:# /opt/emby-server/bin/emby-ffmpeg -skip_list 20 -f mp4 -threads 1 -i file:"/export/d1/video/Test/Thumbnail/trimmed2.mp4" -an -sn -update 1 -vsync 0 -f image2 test.jpg ffmpeg version 5.1-emby_2023_06_25 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 10.3.0 (crosstool-NG 1.25.0) Execution Date: 2024-08-10 00:44:35 -vsync is deprecated. Use -fps_mode Passing a number to -vsync is deprecated, use a string argument as described in the manual. Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'file:/export/d1/video/Test/Thumbnail/trimmed2.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf59.27.100 Duration: 00:01:00.09, start: 0.000000, bitrate: 9655 kb/s Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67, progressive), 3840x2160, 9333 kb/s, Level 153, 59.94 fps, 59.94 tbr, 60k tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] encoder : Lavc61.3.100 libx265 timecode : 00:03:53;14 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default) Metadata: handler_name : SoundHandler vendor_id : [0][0][0][0] Stream #0:2[0x3](eng): Data: none (tmcd / 0x64636D74) Metadata: handler_name : VideoHandler timecode : 00:03:53;14 Stream mapping: Stream #0:0 -> #0:0 (hevc (native) -> mjpeg (native)) Press [q] to stop, [?] for help [swscaler @ 0x1041c00] [swscaler @ 0x104ebc0] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x1041c00] [swscaler @ 0x16b1040] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x1041c00] [swscaler @ 0x17270c0] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x1072400] [swscaler @ 0x107f400] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x1072400] [swscaler @ 0x16b1040] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x1072400] [swscaler @ 0x1728dc0] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x16cef80] [swscaler @ 0x1041c00] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x16cef80] [swscaler @ 0x1684880] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x16cef80] [swscaler @ 0x1709380] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x16cef80] [swscaler @ 0x1041c00] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x16cef80] [swscaler @ 0x1684880] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x16cef80] [swscaler @ 0x1709380] deprecated pixel format used, make sure you did set range correctly Output #0, image2, to 'test.jpg': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf59.27.100 Stream #0:0(und): Video: mjpeg, yuvj420p(pc, bt2020nc/bt2020/arib-std-b67, progressive), 3840x2160, q=2-31, 200 kb/s, 59.94 fps, 59.94 tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] timecode : 00:03:53;14 encoder : Lavc59.37.100 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A Skip-Option - Write output: pkt_pts_time:0 pkt_dts_time:0 input_pts_time:0 Skip-Option - Seek performed to: 20 input_cur_dts: 0.016683 Skip-Option - Write output: pkt_pts_time:20.0033 pkt_dts_time:20.0033 input_pts_time:20.0033=off speed=0.000179x Skip-Option - Seek performed to: 9.22337e+12 input_cur_dts: 20.02 elapsed=00:01:34.62 frame= 2 fps=0.0 q=0.0 Lsize=N/A time=00:00:20.02 bitrate=N/A throttle=off speed=0.212x video:847kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown EXIT I trimmed the same video file to only 1 second long (called trimmed.mp4 in the attached) and added it to the library; then a thumbnail is successfully generated and displayed. Here's a screenshot: If I run my "refined" command to extract the thumbnail then it takes less than 2 SECONDS to run (on the 1 MINUTE sample video): root@omv:/export/d3/stora/downloads/test# /opt/emby-server/bin/emby-ffmpeg -skip_frame nokey -i /export/d1/video/Test/Thumbnail/trimmed2.mp4 -qmin 1 -qmax 1 -q:v 1 -vframes 1 -update 1 test2.jpg ffmpeg version 5.1-emby_2023_06_25 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 10.3.0 (crosstool-NG 1.25.0) Execution Date: 2024-08-10 01:20:31 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/export/d1/video/Test/Thumbnail/trimmed2.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf59.27.100 Duration: 00:01:00.09, start: 0.000000, bitrate: 9655 kb/s Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67, progressive), 3840x2160, 9333 kb/s, Level 153, 59.94 fps, 59.94 tbr, 60k tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] encoder : Lavc61.3.100 libx265 timecode : 00:03:53;14 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default) Metadata: handler_name : SoundHandler vendor_id : [0][0][0][0] Stream #0:2[0x3](eng): Data: none (tmcd / 0x64636D74) Metadata: handler_name : VideoHandler timecode : 00:03:53;14 Stream mapping: Stream #0:0 -> #0:0 (hevc (native) -> mjpeg (native)) Press [q] to stop, [?] for help [swscaler @ 0x2ccd680] [swscaler @ 0x2cda680] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2ccd680] [swscaler @ 0x2d44900] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2ccd680] [swscaler @ 0x2dba980] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2d860c0] [swscaler @ 0x2d93080] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2d860c0] [swscaler @ 0x2cd1a80] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2d860c0] [swscaler @ 0x2d43e40] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2deaf00] [swscaler @ 0x2d675c0] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2deaf00] [swscaler @ 0x2db1440] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2deaf00] [swscaler @ 0x2d27440] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2deaf00] [swscaler @ 0x2d675c0] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2deaf00] [swscaler @ 0x2d94740] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2deaf00] [swscaler @ 0x2d08f80] deprecated pixel format used, make sure you did set range correctly Output #0, image2, to 'test2.jpg': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf59.27.100 Stream #0:0(und): Video: mjpeg, yuvj420p(pc, bt2020nc/bt2020/arib-std-b67, progressive), 3840x2160, q=2-31, 200 kb/s, 59.94 fps, 59.94 tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] timecode : 00:03:53;14 encoder : Lavc59.37.100 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A elapsed=00:00:01.93 frame= 1 fps=0.5 q=1.0 Lsize=N/A time=00:00:00.01 bitrate=N/A throttle=off speed=0.00863x video:1495kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown EXIT Hope you have enough to reproduce & determine the cause of the problem. Logs-n-sample.zip Edited August 10, 2024 by macnb added screenshot 1
Happy2Play 9780 Posted August 10, 2024 Posted August 10, 2024 Wonder by different platforms get different results on the exact same command? 2024-08-09 18:11:03.406 Debug App: Running VideoImageProvider for E:\Media\Photo\Test\trimmed2.mp4 2024-08-09 18:11:03.406 Info QuickSingleImageExtractor: ProcessRun 'quick-extract-image' Execute: C:\Users\Media\Desktop\TEST\system\ffmpeg.exe -skip_list 20 -f mp4 -threads 1 -i file:"E:\Media\Photo\Test\trimmed2.mp4" -an -sn -update 1 -vf "thumbnail=24" -vsync 0 -f image2 "C:\Users\Media\Desktop\TEST\programdata\cache\temp\ea4b7e58-57be-4821-8c48-6d27a9bd8b1e.jpg" 2024-08-09 18:11:17.283 Info QuickSingleImageExtractor: ProcessRun 'quick-extract-image' Process exited with code 0 - Succeeded 2024-08-09 18:11:17.283 Debug ProviderManager: Saving image to E:\Media\Photo\Test\trimmed2-poster.jpg
macnb 32 Posted August 10, 2024 Posted August 10, 2024 10 hours ago, Happy2Play said: Wonder by different platforms get different results on the exact same command? 2024-08-09 18:11:03.406 Debug App: Running VideoImageProvider for E:\Media\Photo\Test\trimmed2.mp4 2024-08-09 18:11:03.406 Info QuickSingleImageExtractor: ProcessRun 'quick-extract-image' Execute: C:\Users\Media\Desktop\TEST\system\ffmpeg.exe -skip_list 20 -f mp4 -threads 1 -i file:"E:\Media\Photo\Test\trimmed2.mp4" -an -sn -update 1 -vf "thumbnail=24" -vsync 0 -f image2 "C:\Users\Media\Desktop\TEST\programdata\cache\temp\ea4b7e58-57be-4821-8c48-6d27a9bd8b1e.jpg" 2024-08-09 18:11:17.283 Info QuickSingleImageExtractor: ProcessRun 'quick-extract-image' Process exited with code 0 - Succeeded 2024-08-09 18:11:17.283 Debug ProviderManager: Saving image to E:\Media\Photo\Test\trimmed2-poster.jpg Probably to do with different implementations of FFMPEG on Windows & Linux and also how they handle the input file. trimmed.mp4 is 1 Second long (60 frames) and trimmed2.mp4 is 60 seconds long (3600 frames). The FFMPEG command used by Emby is not searching for the first key frame so does not return consistent thumbnail (even on different platforms as witnessed by your screenshot). That's why I prefer the key frame search (my "refined" command above) because it produces identical thumbnails for both sample videos and is very fast.
macnb 32 Posted August 15, 2024 Posted August 15, 2024 20 hours ago, Luke said: Thanks, we'll take a look at it. Thanks. If you wish to send a test server to try, I am happy to test it (Debian Linux). Specifically, a version with my suggested FFMPEG command to extract the thumbnail.
Luke 42077 Posted September 10, 2024 Posted September 10, 2024 Are you able to try the beta server and see how things compare? If not it's OK as you can't roll back afterwards.
macnb 32 Posted September 12, 2024 Posted September 12, 2024 On 10/09/2024 at 23:46, Luke said: Are you able to try the beta server and see how things compare? If not it's OK as you can't roll back afterwards. hmmm. If the Beta server changes are related to this issue then I can try it. If there are other extensive changes then, I'd have to think about it. In worst case scenario (of the beta server failing), I would have to uninstall the server and rebuild all my libraries ?
Happy2Play 9780 Posted September 12, 2024 Posted September 12, 2024 (edited) 28 minutes ago, macnb said: hmmm. If the Beta server changes are related to this issue then I can try it. If there are other extensive changes then, I'd have to think about it. In worst case scenario (of the beta server failing), I would have to uninstall the server and rebuild all my libraries ? Realistically if Premiere do a full backup and rename that backup to say embyserver-backup-full (Release) as Emby currently only maintains one full backup. So, if your testing last more than a day or the backup task runs you have a full backup of release. Then install beta over release and test. If there are still issues you can restore the backup to revert back to release cycle as it is will have the unchanged databases and /metadata per your backup options. or Manually backup Emby programdata folder. Edited September 12, 2024 by Happy2Play
macnb 32 Posted September 12, 2024 Posted September 12, 2024 38 minutes ago, Happy2Play said: Realistically if Premiere do a full backup and rename that backup to say embyserver-backup-full (Release) as Emby currently only maintains one full backup. So, if your testing last more than a day or the backup task runs you have a full backup of release. Then install beta over release and test. If there are still issues you can restore the backup to revert back to release cycle as it is will have the unchanged databases and /metadata per your backup options. or Manually backup Emby programdata folder. Thx for the tip. I do not have Premiere. I'm Emby Server on Debian Linux (OMV NAS) so there's no Programdata folder. These are the folders I see under /var/lib/emby: root@omv:~# ls -l /var/lib/emby total 88 drwxr-sr-x+ 7 emby emby 4096 Sep 12 17:36 cache drwxr-sr-x+ 5 emby emby 4096 May 26 2023 config drwxr-sr-x+ 7 emby emby 4096 Sep 12 17:35 data drwxr-sr-x+ 2 emby emby 4096 Dec 8 2022 fonts drwxr-sr-x+ 2 emby emby 4096 Dec 8 2022 localization drwxr-sr-x+ 2 emby emby 12288 Sep 12 17:36 logs drwxr-sr-x+ 12 emby emby 4096 Dec 8 2022 metadata drwxr-sr-x+ 3 emby emby 4096 Jun 12 12:24 plugins drwxr-sr-x+ 3 emby emby 4096 Dec 8 2022 root drwxr-sr-x+ 7 emby emby 4096 Jun 29 19:08 transcoding-temp root@omv:~# Which folders would I back up if not the Emby folder itself ?
Happy2Play 9780 Posted September 12, 2024 Posted September 12, 2024 (edited) 7 minutes ago, macnb said: These are the folders I see under /var/lib/emby: That is your Emby programdata for that platform. Path also seen via Dashboard three dot menu I guess the only thing you will have to watch is folder permissions. Edited September 12, 2024 by Happy2Play
macnb 32 Posted September 12, 2024 Posted September 12, 2024 5 minutes ago, Happy2Play said: That is your Emby programdata for that platform. Path also seen via Dashboard three dot menu I guess the only thing you will have to watch is folder permissions. Ok got it. This is what I see from dashboard ... So backing up /var/lib/emby (including it's permissions/ownership) should be sufficient to be able to able to recover ?
Happy2Play 9780 Posted September 12, 2024 Posted September 12, 2024 7 minutes ago, macnb said: Ok got it. This is what I see from dashboard ... So backing up /var/lib/emby (including it's permissions/ownership) should be sufficient to be able to able to recover ? Yes as Emby server and programdata are separate folders. So if you need to downgrade you would uninstall beta, install release and restore your backup. 1
macnb 32 Posted September 12, 2024 Posted September 12, 2024 (edited) @LukeThere's a Beta version 4.9.0.30-Beta listed in the dashboard. Is that the version I should try to test the Thumbnail fix ? Edited September 12, 2024 by macnb
Happy2Play 9780 Posted September 12, 2024 Posted September 12, 2024 23 minutes ago, macnb said: where's the Debian download file ? On the download page, just change OS drop-down to your platform and go to beta versions. Emby Server for Linux - Emby Or directly from GitHub listed per Emby version Releases · MediaBrowser/Emby.Releases (github.com) But yes that is the latest beta version.
macnb 32 Posted September 12, 2024 Posted September 12, 2024 1 minute ago, Happy2Play said: On the download page, just change OS drop-down to your platform and go to beta versions. Emby Server for Linux - Emby Or directly from GitHub listed per Emby version Releases · MediaBrowser/Emby.Releases (github.com) But yes that is the latest beta version. Yes I just found that and deleted my question above just before you replied Thx. Just need to know if that contains a fix for the thumbnail issue in this topic
macnb 32 Posted September 14, 2024 Posted September 14, 2024 @LukeSo installed the available 4.9.0.30-Beta. That Beta does not solve the Thumbnail problem. Same behaviour as the release server version. Errors are the same. So there's no fix in the latest beta.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now