All Activity

Emby Server 4.10.0.8 Emby for android 3.5.31 Logs included where I start the movie, no subtitles. I go to the cogwheel and select fix playback issues and after that the subtitles kick in. embyserver.txt

It was not listed in the Series tab... It just showed up in the Guide as set to record, with only the option to cancel the recording, not the series. Thats why I had to edit the Json file

Hello, first of all thank you for your work. I got it to run after reading through everything written here and in your emby.md Readme in your Github. I realized AniDB wasn't working, i always got the error "AniDB.authorize() takes 2 positional arguments but 4 were given" when running with AniDB configured in the yaml. Since I want to have the ratings from AniDB as overlays for my Anime posters and episodes I tried to fix it myself. I think I fixed it by taking the part for AniDB from the newest main version of Kometa's config.py (under modules) and pasting it instead of the AniDB part in your config.py. So far the Script is running without giving me that error and in the logs I can also see "AniDB API Connection Successful" but I will have to wait and see if it applies the AniDB ratings. I can update here when it's done.

@Lukehave you any update ? problem to dev it ? Need something ? Please keep us in touch we-re waiting it from 6 years ago

@justinrhA fix is planned for Emby Server Beta 4.10.0.9

A fix is planned for Emby Server Beta 4.10.0.9

Gracenote appear to have fixed the duplicates on the "Sky Q London" - GBR-100197-DEFAULT lineup The only remaining duplicates in the lineup are for "321 Great! Mystery" and "323 Great! Action" Please refresh the guide and check the channel numbers and mapping in LiveTV Setup / Channels (Note that there is 24 hour caching in Emby Server after the last fetch of EPG data) These are correct now and agree with https://www.tvchannellists.com/w/List_of_channels_on_Sky_Q_(United_Kingdom_%26_Ireland) 404 Sky Sports + HD 405 Sky Sports Cricket 407 is correct as Sky Sports F1 HD and there does appear to be a schedule for channel 407 Sky Sports F1 e.g. as example 10th Aptil 09:30 AM BST "Gabriel Bortoleto IV" Sky F1's Rachel Brookes chats to Audi driver Gabriel Bortoleto. 507 is correctly set as "NHK World News" in the lineup.

@gillmacca01Thank you for reporting this. I have referred it to Gracenote

I did, and that didn't appear to work either.

Hi, did you try removing the series schedule from the series tab?

Thanks for your answer. Please provide me with some information about it and we'll see if we can use it.

You would honestly be better served to drop the Firestick and move to a actual Android device like an Onn box, or a Shield. Amazon will continue to break things, forcing the dev team to address them, taking them away from more important problems. The fact Amazon has decided to go this route is stupid, and is a slap in the face to consumers.

Its late and I'm rambling.... sooooo.... heres the scenario. A manually-specified IPTV recording for a specific channel is created. That's fine, works perfectly as intended. However - If that IPTV channel for which that schedule is based on is deleted or renumerated as something else, that manually specified recording schedule becomes an "orphan" meaning it shows up in the Schedule as to be recorded which never happens because the programmed channel has vanished. It just remains in the list of Scheduled recordings, even AFTER a Guide Refresh. The solution I found for this is to shut down Emby, then backup and manually edit the "Seriestimer.json" file in data\livetv to remove the reference AND delete the Timers.json file. Then restart Emby and do a Guide Refresh - The orphan scheduled recording is gone, and the schedule correctly repopulates. Am I missing a step here in this scenario? I'm hoping this explanation makes sense. It seems that by deleting Timers.json, Emby is forced to rebuild that file when Guide Refresh is done and perhaps renumerates the schedule..... ??

If you go into those two data folders that you found, then underneath that there is a logs folder. See which one is getting written to.

Updated the first post with some instructions on how to install on the docker version of Emby.

So it turns out I was wrong on two fronts. 1) I'm not done with it, and 2) It's not vibe-coded. I filed a bug report, and a new release should land soon to address the file descriptor exhaustion. I'm relieved, because I'd sunk quite a bit of time into setting up channels...the issue I experienced only manifested after I tried setting up music stations.

The song I was playing just stopped. Do the logs reveal anything telling? It stopped playing at 7:19/20. ffmpeg-transcode-6ec5cace-acd2-4e2b-af74-acf763f62f8c_1.txtembyserver-63911203200.txt

how do I find that out ?? I'm only open at the start up wizard, mot a lot of info there..

New version up (v2.4.7.0) Changed: 1) Removed Credit Edit as it is now a separate plugin (found at: yocksers/TimeMarkEdit: Edit chapter time marks in Emby) Fixed: 1) Small bug fixes not noticeable to users.

Looking forward to it Luke because the random songs suddenly not playing problem has been spreading ^^ (sometimes even shows won't play in a browser but they will play in the app for example or after a reboot it suddenly will play an episode but then the next one won't. It's been annoying but i'm looking forward to the end of the forced beta state) And i had a feeling it wasn't a proper update because every single app had an update not just 1 or a couple which is why i figured it would be best to ask here first.

OK please attach the complete emby server log. Thanks.

bro i would have to fix one piece by hand 0_o. thats over 1000 episodes. im just tired of logging into my server and wanting to watch one piece only for it too play the damn thing out of order due to the metadata that the server is getting to be wrong lol.

Never use autoupdate myself. I want things right now

As far as what you see in the store, this is correct. However, the app will not auto update unless you install from the store.

Hi, this should resolve your issue if you delete the entire parent folder, run a scan to clean out the database, and then add it back. I think this issue is likely caused by an older server version, meaning I don't think you'd see it happen on a fresh install.