All Activity

I provided logs every time when asked, i don't know what you're talking about there. There hasn't been a response stating that the issue can't be replicated, just that they're unsure what's causing it. Burning in the PGSSUBS on Roku is a feature that Emby offers and the whole point of this thread has been that it isn't working properly for me. I'm aware that I can buy other hardware or stop using PGSSUB but I actually wanted to see if the issue could be resolved. I'm glad that we consider bug reports to be "complaining"... If they can't figure out the problem, fine I guess. The frustrating part has been the process of request logs, I provide them, crickets for months until I bump the post, rinse and repeat.

Try "Test to replace: MaxBitrate=39000000" "Replacement Text: MaxBitrate=250000000" Last thing i can think of.

Not sure why this happens.. As a workaround you can clone your list, wait for it to populate and then enter your new link. Then you could delete the first list. I’ll see if can fix this bug

I will look into it.

You appear to be the only person who is experiencing this, which means it is limited to your hardware/software. You were also asked for ffpmeg logs back in 2024, which you did not provide. Luke also asked you for logs constantly, which you did provide. No one else has apparently reported your issues, so this "level of support" is to be expected as the dev team absolutely can not duplicate your problem. PGSSUBS are image based and Roku does not support them. From a user standpoint, if you demand to play pgssubs and your current hardware can't play them back properly, I would just replace the hardware with something that can and stop complaining, or stop using pgssubs altogether. As a server admin myself, I ended up buying Android devices for several family members to shut them up for other playback reasons. Those that refused, got booted.

This is the level of support I'd expect for free software but buying a license specifically to use hardware transcoding and getting the runaround for a year is insane. Don't even ask for logs and say you're "looking into it" if the final answer is just going to tell me not to use PGSSUB. I give up but this has been really frustrating.

I wrote a script to change this setting as it was enabled, seems to be enabled by default or it was a few server versions back. But as i changed it and refreshed my library, this solved my problem. Thanks a lot for this info

I think the community plugin would be an excellent starting point because it enables people to review where the timestamp has been set and can enable the feature on a per show basis. I’d wish it would be implemented regardless, maybe marked as „experimental“ to make clear that there could be unforeseen errors

@Lukeit happend again. Yesterday around 22:28 (a few times). I have attached the logs. My system is an unraid with the emby docker container and hw transcoding setup like this: https://forums.unraid.net/topic/101969-guide-setup-emby-with-hw-transcoding-on-unraid-remote-access-through-reverse-proxy-using-swag/ and checked by settings an low resolution on an client -> server dashboard is showing HW transcoding (green icon). I have an idea and test the following now: On my second client i have not noticed the issue (same nvidia shield pro incl. same firmware and emby app). But the android tv app setting: settings -> playback -> audio output -> is set to "Auto". On my client with the issue (see logs) it was set to something "Downmix to DTS...". The files i am playing have mostly aac audio. If i played the same file on both maschines, on one (without the issue) it says "Direct play" for video and audio. On the maschine with the issue it said direct play just for video and transcoding for audio. After changing the setting to "Auto" it also says "direct play" for video and audio. Can you please check the logs for an issue regarding transcoding? Any other hint why it begins to stutter (i have noticed mostly at the end of an ~40 min video - last few minutes). thx logs_emby_server.zip

As mentioned above, exact same problem on my G5 as well.

IMO I'm not really sure we should. An error in auto-skipping the intro is easily corrected with a back skip or two but the same cannot be said for auto skipping to the next item. If this were marked incorrectly it could be hard to even realize it and even harder to recover from.

This part is something for Emby to implement, the plugin will show you Credit skip after you have run through your library. But Emby has not implemented the auto skip part, so you need to click skip for now.

Yes, it's my own list. I probably entered the link BEFORE the list have populated. I deleted the cache (autotag_cache.json), restarted emby but still nothing for this one: "No tems found"

Ok, it all makes sense now. That was the missing piece. I added that tag to the filenames to keep them identical with the folder and it's all working like it should be now. Thanks folks!

@uncle_yuriI think you can still use this folder naming folder : Dawn of the Dead (1978) {tmdb-923} But then you media files will also need to be named like that. Dawn of the Dead (1978) {tmdb-923} - Extended Edition.mkv Dawn of the Dead (1978) {tmdb-923} - US Theatrical Edition.mkv And yes that will help Emby better to identify the movie, when you use {tmdb-XXXXXX}

Try using MCEBuddy, it uses Comskip (or ShowAnalyzer if you have a preference) will do it remove the commercials for you automatically.

Hi Luke, that did fix it actually. I also noticed that I had added {tvdb-923} when it should've been {tmdb-923}. I thought that would be the "other" fix, but when I tried using the right tag, it reverted to the problem behavior. Any idea why that is? (Basically I mean, I thought it would be 'best practice' to add a definitive TVDB/TMDB identifier tag, but if it's better to just use title and year, I'll stick with that)

That's exactly what I was thinking too because when something goes wrong as they mess to try to fix

That request does not mention auto-skipping. That's a question for the plugin's thread.

I hope it helps. Honestly, if actually skipping the credits is not an option anyway there's little reason for me to try to get the plugin to work properly EmbyCredits.xml

No option to automatically skip, it only adds a time stamp in the video metadata that tells Emby where the end credits are and Emby takes it from there. I sadly can't think of anything that might be wrong with out any logs. Give me some time and i will make a new version with some more logging to help diagnose the problem. For now though, can you please upload the EmbyCredits.xml file? That should at least help a bit.

So there is no option to actually automatically skip the credits? Which would be fine, just would like to know. I did set a custom folder and also gave both containers full rights to the custom folder.

It should log it, did you enable debug logging in Emby? The end credit markers added by the plugin triggers the "next episode" pop ups to appear. While Emby automatically shows should them the plugin makes them much more precise in when they should appear. The "OCR test failed: Error while copying content to a stream." fault you are getting could point to you not having set a "custom folder", not having given the right permissions to that folder or enabled direct stream without having hardware capable of it.

Yes you can but I also like how it is available on the Plex dash app. Just a suggestion.

I will do that as soon as Emby logged anything there. The error does not seem to trigger a log of any kind. Btw I got a question. I wouldn't even mind not using OCR at all because it's possible to set markers manually but then I can't seem to find any option to actually skip the credits automatically. The marker just seems to set when the "next episode" pop up appears. Or do I miss anything super obvious here?