All Activity

HI, apologies for the delay. We are working on getting a new server release out to resolve this. Thanks. You can't install old USB builds. Samsung expires them after 30 days.

Are you still able to reproduce this?

What do you see when you use the metadata editor on the individual tracks?

@BaNanaBlocks Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!

Hi @Kenacious_Dare you still having an issue with this?

Can you please show us how you configured all of the trakt plugin options? Thanks.

This is a tricky case because items always have names, therefore the missing metadata refresh ignores whether it currently has a name or not. What I would suggest doing is locking the name field for these.

Should this work on Unraid? My hardware log looks like this { "DeviceIndex": 1, "DeviceInfo": { "VendorName": "Intel Corporation", "DeviceName": "Battlemage G21 [Arc B580]", "SubsytemVendorName": "ASRock Incorporation", "VendorId": 32902, "DeviceId": 57867, "SubsytemVendorId": 6217, "SubsytemDeviceId": 24609, "DevPath": "/sys/bus/pci/devices/0000:03:00.0", "DrmCard": "/dev/dri/card1", "DrmRender": "/dev/dri/renderD129", ,"ExitCode":135},"QuickSyncCodecProvider":{"CodecProviderName":"QuickSyncCodecProvider","StandardError":"ffdetect version 5.1-emby_2023_06_25_p4 Copyright (c) 2018-2022 softworkz for Emby LLC\n built with gcc 13.4.0 (crosstool-NG 1.28.0)\n configuration: --cc='sccache x86_64-emby-linux-gnu-gcc' --prefix=/home/embybuilder/Buildbot/x64/ffmpeg-x64/package --disable-alsa --disable-doc --disable-ffplay --disable-gnutls --disable-libpulse --disable-librtmp --disable-libxcb --disable-openssl --disable-vdpau --disable-vulkan --disable-xlib --enable-chromaprint --enable-fontconfig --enable-gpl --enable-iconv --enable-libaribb24 --enable-libass --enable-libdav1d --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-mbedtls --enable-pic --enable-version3 --enable-libtesseract --enable-libwebp --enable-cuda-llvm --enable-cuvid --enable-libdrm --enable-libmfx --enable-nvdec --enable-nvenc --enable-vaapi --enable-opencl --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --enable-shared --disable-static --pkg-config=pkg-config --pkg-config-flags=--static --extra-libs='-ldl -lm -lstdc++ -pthread -lsharpyuv' --disable-debug --enable-lto\n libavutil 57. 28.100 / 57. 28.100\nBegin GetVaAdapterInfo\nFound 36 device entries\nBegin get_nodes\nFound 3 drm entries\nBegin get_nodes\nFound 3 drm entries\nEnd GetVaAdapterInfo\nInitialize MFX session: API version is 1.35, implementation version is 1.35\nAddDecoderProfiles - Profile not supported (1): MFX_PROFILE_AVC_HIGH_422\nAddDecoderProfiles - Profile not supported (1): MFX_PROFILE_AVC_CONSTRAINED_BASELINE\nAddDecoderProfiles - Profile not supported (1): MFX_PROFILE_AVC_CONSTRAINED_HIGH\nAddDecoderProfiles - Profile not supported (1): MFX_PROFILE_AVC_PROGRESSIVE_HIGH\nAddDecoders - Codec not supported: vp8\nAddDecoderProfiles - Profile not supported (1): MFX_PROFILE_AV1_MAIN\nAddDecoderProfiles - Profile not supported (1): MFX_PROFILE_AV1_HIGH\nAddDecoderProfiles - Profile not supported (1): MFX_PROFILE_AV1_PRO\nAddEncoders - Codec not supported. Out codec id: mpeg2video\nCheckEncoderResolutions: h264- Resolution not supported (1) 176x144 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 960x540 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 1280x720 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 1920x1080 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 2048x1080 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 3840x2160 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 4096x2160 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 7680x4320 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 8192x4320 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: h264- Resolution not supported (1) 8192x8192 (err: -3 - MFX_ERR_UNSUPPORTED)\nAddEnoderProfiles - Profile not supported (2): MFX_PROFILE_AVC_EXTENDED\nAddEnoderProfiles - Profile not supported (2): MFX_PROFILE_AVC_HIGH_422\nCheckEncoderResolutions - Resolution not supported (2) 960x540\nCheckEncoderResolutions - Resolution not supported (2) 1920x1080\nCheckEncoderResolutions - Resolution not supported (2) 2048x1080\nAddEncoderProfiles - Profile not supported (1): MFX_PROFILE_HEVC_MAIN10\nCheckEncoderResolutions: vp9- Resolution not supported (1) 176x144 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 352x288 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 352x576 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 720x576 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 960x540 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 1024x576 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 1280x720 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 1920x1080 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 1920x1088 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 2048x1080 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 2048x1088 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 3680x1536 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 3840x2160 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 4096x2048 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 4096x2160 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 4096x2176 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 4096x4096 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 7680x4320 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 8192x4320 (err: -3 - MFX_ERR_UNSUPPORTED)\nCheckEncoderResolutions: vp9- Resolution not supported (1) 8192x8192 (err: -3 - MFX_ERR_UNSUPPORTED)\nAddEncoders - Codec not supported: av1\nBegin GetVaAdapterInfo\nFound 36 device entries\nBegin get_nodes\nFound 3 drm entries\nBegin get_nodes\nFound 3 drm entries\nEnd GetVaAdapterInfo\n\n","Result":{ I am on the latest 4.10.0.8 My unraid version 7.2.3 sees the ARC B580 hardware_detection-63911091005.txt embyserver.txt

Hi, the reason for this is to ensure that you can still read the contents of the screen. Do you think you'd be able to do that if it wasn't dimmed?

Hi, not yet but we are working on getting it out soon. Thanks.

Anyone there?

Hi @SamES @Luke Do you have an estimate of when we will have an update on the Emby server?

Aperture v0.7.6 Release Notes This release improves deployment (multi-arch Docker images for amd64 and arm64), user sync with Emby (respect disabled accounts), setup wizard job triggers, and STRM library lifecycle (automatic removal of virtual libraries and output folders when recommendations are turned off). Summary for Users Apple Silicon Macs and 64-bit ARM servers (e.g. Raspberry Pi with a 64-bit OS) can run the same pre-built container image as x86_64; Docker pulls the matching architecture automatically. If your server admin disables your Emby account, Aperture stops treating you as eligible for recommendation jobs once sync-users runs (default every 30 minutes). Initial setup jobs such as Sync Movie Watch History no longer fail with a validation error when started from the wizard. Summary for admins Disabling recommendations and STRM output When you turn off movies, series, or all recommendations for a user (Admin → Users), or when sync-users detects a user disabled on the media server, Aperture attempts to: DELETE the corresponding virtual library in Emby (by library name). Remove that user’s folders under /aperture-libraries/aperture and /aperture-libraries/aperture-tv (inside the Aperture container). Delete matching rows in strm_libraries. Failures talking to the media server (e.g. library already removed) are logged; database and filesystem cleanup still proceed where possible. The scheduled sync-movie-libraries / sync-series-libraries jobs also run a reconciliation pass to clean up stale library records. Docker image architectures Published images are multi-architecture manifests. No separate tag is required per CPU; use your existing ghcr.io/.../aperture image reference. Note: 32-bit ARM (arm/v7) is not a build target; use a 64-bit OS on Raspberry Pi for parity with dependencies (e.g. native modules). API notes (operators) Setup jobs: POST /api/setup/jobs/:name/run — the documented allowed name values now match the server (includes watch-history, embedding, library, and related job ids). Update instructions For Docker users docker compose pull docker compose up -d Apply database migrations per your process (pnpm db:migrate or automatic on startup, depending on deployment). Operator checklist Expect one-time sync — existing users get provider_disabled = false until sync-users runs and reads the current media-server flags. Thank you for running Aperture and reporting setup and deployment edge cases in the wild.

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

HI there, can you please provide a specific example? How to Report a Problem Thanks !

Hi there, how are your files named and organized? What exactly makes you feel that none of the metadata is being read?

@nenchiiimoved to own topic.

Hi, yes this is something that we plan to add in future updates. Thanks.

Interesting... We have 6 Apple TVs around the house each setup with Emby and "Show Login Screen" set with a couple users logged in. However after testing, only 1 seems to show the login screen after being exited 10+ mins. I'll have to remove/reinstall it from one and try some different orders of setup or something.

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

That's not what I'm referring to. There should be no need for a third-party platform/integrations since these systems all support their own modi of notifications?

Hi, we are looking into it. Thanks.

1 & 2. FFmpeg Command and Background Hanging Regarding the malformed command, it's actually not missing a quote—that is just an artifact of how the parameter string is being outputted to the log. The root cause of the freezing and hanging FFmpeg processes you're seeing is the Audio Normalization feature. It can be quite unstable on certain platforms and, honestly, isn't really required anymore. Please go into the plugin settings and turn off audio normalization. This should completely resolve the hanging threads and server lockups you experienced without needing to inject -nostdin. 3. Crashing on Existing Files The plugin actually doesn't blindly download and move files. It specifically queries Emby for a list of all media that are currently missing themes. If the plugin is downloading and trying to move a theme into a directory where one already exists, it means something is wrong with your Emby setup and it isn't recognizing those existing themes in its database. I'd recommend double-checking your library structure or running a full library scan to ensure Emby properly registers the media you already have. 4. Network Exceptions and MediaFire Dead Links I completely understand that it looks like log spam, but I am leaving those 404s and network exceptions in the standard log intentionally. I actively report these dead links and network drops to MediaFire, and historically, they don't do anything to resolve them unless I spam them with the exact logs you are seeing. I might move these to a debug log level at some point down the road, but for now, having larger log files doesn't bother me, as it gives me the hard data I need to get MediaFire to act.

It should be possible. Install plugin for what ever notification system you want, lets say pushover. Have the user set up hes own notifications under app settings -> notifications.

Thanks! I'll get back to this this weekend. Since my post, I switched BACK to the Android app on my TV. Originally, I switched from it to the older Android TV app because that played AV1 files without transcoding or sometimes freezing. It seems now Android TV as of one of the last beta updates is transcoding AV1 and now the standard Android app works perfectly.