Leaderboard

Hi mate, Will look into this today for you.

Hopefully with the next update it'll be fixed, then

Got the second machine back online and installed Channels and added it to emby and recorded the same movies as on my normal machine last night. I am running the stable emby and the beta on my normal machine and only the beta on the second machine. The beta servers are both portable installs where the stable is an actual install. My main machine is Windows 11 and the second is Windows 10. Upon editing the same movies this morning on both machines recorded using the beta servers I get interesting results. My main machine's beta server records movies will small errors that are detected by VRD6 but the same exact movies recorded on the second machine do not show the same errors. So the problem is NOT the beta server but something else. Could the problem be running 2 servers on the same machine? Could it be as simply as just reinstalling the beta on the main machine? I will have to try this when I have time. I am now stumped, any ideas Luke?

Issue resolved thanks

Can't seem to edit my posts...use to be able to, anyway ignore my post, just realised I had to scroll down further

Click Up 2-3 times to bring title in focus>OK or three-dot menu there>Go to series.

Hit this problem when attempting to offline content for a trip. Will try some of the workarounds mention.

Thanks Luke, I used ffmpeg -i 1030_20250909005300.ts -c copy 1030_20250909005300.mp4 to convert the file to an mp4 container. Interestingly, this is still not smooth at all, in fact similar if not worse. Now the container is not coming up as unsupported, but oddly it is still converting the audio (mp3) in software. I don't really understand why that would be. 2 thoughts, when I used that ffmpeg line above, there was 1 or 2 logs indicating errors in frames that ffmpeg corrected. Maybe something is not quite right with the files as you suspect, but usually a once over with ffmpeg fixes that. The other thought I have right now, is regardless of why, when the audio is not playing via hardware it somehow causes the video/audio syncing to be modified enough that the jittering video is quite noticeable. I'm not sure there is anything specific we can further do with this, for now, I am playing the myth recordings in a myth client so it is not a major problem for me, and it only occurs on my new TV. My hope to replace myth as a client with emby is not going to happen at the moment, but unless you want to chase this further, suggest we close this ticket.

when i see again ill add some logs.

Here is my latest log Emby 3.5.02. Blank screen, I have to click Next Episode to play the next episode. * 01:46 * Blueskies * Log emby_android_1757724101976.txt Thanks

In the context of an M3U playlist, a pipe character () is an unofficial convention used by some media players to append custom HTTP headers to a URL. The syntax is not part of the standard M3U format, but it is widely supported by IPTV clients like Kodi's IPTV Simple Client and VLC. [1, 2, 3] The pipe character is placed at the end of the stream URL, followed by one or more pairs for the headers. [2] General format: http://some.iptvserver.any/subfolder/master.m3u8|X-Forwarded-For=123.45.67.89

Panel de control > Carpeta cmpartida > Permisos > Selecionas usuario interno del sistema > nombre "emby" y selecionas lectura/escritura Espero que sea eso. Un saludo

Buenas. Instaló el Emby en una Sinología 423+. Creo que el problema es tema de permisos. Dentro de la Sinología dale permisos a la alfombra al servicio Emby como Lectura/Escritura y ya lo tienes solucionado. Una vez des permisos, no solo vas a seleccionar dentro de Emby la unidad, sino también las alfombras que hay dentro. Es ahi cuando te aparecen todas . Cuando tengas los permisos, entras otra vez a esa unidad y ya puedes poner "Peliculas" , "Series" , etc. Eso me paso a mi, pero he tenido Plex con anterioridad y aprendiz de eso. Un saludo

Hi, it’s just around the corner.

It would be nice to have a way to disable the channel when we dont want it shared to anyone. This way, we could make it where no users are checked it is shared to everyone. Soon as a user has a checkmark it restricts to only those checked. This will save us from place check marks in each user for each new channel and will default to any new users to Emby getting them shared as well so it save us from having to go back in each channel and at them and save. Unless of course there is already an easy way to do all this and I am missing it

It shouldn't be, according to the Dev.

Unfortunately, the defined metadata tags that would make that possible have been historically misused. I did a whole diatribe on this a few years ago in a feature request in the Plex forums, but they never did anything about it. The ID3 specification (which, technically, only applies to mp3 formats) has four tags that are supposed to be used for the relevant artists for any release. They are defined like this: TPE1 Lead performer(s)/Soloist(s) TPE2 Band/orchestra/accompaniment TPE3 Conductor/performer refinement TPE4 Interpreted, remixed, or otherwise modified by In theory, the orchestra would go in TPE2, but way back at the "beginning," the makers of the WinAmp media player decided to use TPE2 as the "Album Artist," rather than for "Band/orchestra/accompaniment," because the ID3 specification failed to include a specified tag for "Album Artist," and that failure has never been corrected. The whole industry, with a few attempted exceptions, has basically followed suit ever since. Few are willing to buck the system and use the TPE2 tag as it was originally intended. So in tags, orchestra is no different than the band name, and it's impossible (or logically difficult) to segregate the orchestra into its own category. It could be done in formats that use Vorbis tags, such as flac, but that tag system is very flexible (which has both good and bad consequences), and it would depend on everybody using the same tag name. It could even be done in mp3 files using user-defined tags, but that, again, would depend on everyone using the same custom tag name. Most developers/product designers I've talked to are reluctant to do this because of that dependency.

You two go get a room, and leave us rest bitching about 5+ years of waiting for functional IP TV in emby. I think there has been enough bitching for the moment. Feel free to resume later, but for now I think, the message has been received. Let me share some gossip instead... You have no idea what an important role the WebStreams plugin is playing in the context of TVnext. Initially, it was meant to be integrated in TVnext, but hardly anybody was able to follow or visualize and imagine what I was talking about exactly, so for me, this had become... The Hardest Sell We've all learnt that there's nothing worse you can do than (actually or seemingly) taking away an existing feature in a new/updated version of a software application. And yet there was exactly one such kind of removal that was inevitable in the making of TVnext, which is - simply said - about dropped support for VOD streams as (fake) TV channels. The below conversation is fictional but roughly resembles the average of the kind of conversations that I had with many people at that time - not just internally, but also with external people and with some of our beta participants as well: Feature Removal? softworkz: "Please be prepared that VOD streams are not supported and not handled by TVnext. TVnext is about live TV streams and also supports non-TV live streams but not playback of static files that are just disguised as live streams" other: "What? You cannot do that! Users expect that to work, all other apps are doing it like that, you must not take this feature away!" softworkz: "Yes, I'm fully aware about how people are reacting when they feel that a feature is taken away from them. That's why I have the following great plan:" other: (already stopped listening) softworkz: "The plan is to replace the lacking VOD playback feature with something that is so much better and nicer and unique and even unprecedented, that nobody will ever be missing it." other: "No - people expect this to work like everywhere else." softworkz: "What do you mean - what exactly are people expecting? That the first episode of series XYZ, season 1 is on channel 1456153 and the second on 1456154 while the first episode of the next season is on channel 1623214?" other: "Yea, that's how it works everywhere." softworkz: "But we are Emby - our mission is to present media content in the best possible way, enriched with all kinds of metadata - who would want to access series content via non-memorable, 6- to 10-digit channel ids without any other metadata than a short description and a single image - if at all? We can present this in a much better way!" other: "Nah, people will freak out when they cannot do like that anymore, this won't be accepted" softworkz: "But how can that be? This is so clearly inferior to everything else. This doesn't even allow having saved playback positions, neither any kind of 'watched' indications etc. There are no series and season entries for grouping - in sum: you get almost none of the features that Emby provides normally." other: "All others are doing it the same way; people are used to it and expecting it to work like that." softworkz: "Why should people prefer Emby then, when it doesn't do better than any of the other apps? And I still can't imagine how anybody would be seriously using it that way: How do you navigate a TV guide when it has 10k, 20k, or even more channel rows? And all of those rows (unless actual live tv) having a single 'program' that is repeating 24/7? When you want to play an episode or film, you search for a TV channel of that name? And when you have 50k TV channels due to that, how can you find an actual TV channel when you get so many search hits? And how is channel management supposed to work? When you want to bring a certain channel from the end to the middle, or from the middle to the start or end? You hold down your finger on the mouse button for several minutes when drag-drop sorting? For every single channel that you want to move?" other: "Sure it's not ideal, but that's how it has always worked, and people want that!" softworkz: "Yes, but..." other: "No, this must continue working!" softworkz: "But the WebStreams concept is so cool - nobody else has that! I'm sure, people will love it. Anyway, TVnext cannot handle VOD - it's impossible unless we drop so many essential features that it's not even worth proceeding." other: "Hmm, well, err, but no...etc etc." softworkz: (sigh) WebStreams Plugin After all those discussions, I had realized that I couldn't get that idea sold as such. The sole promise of providing something better in the end wasn't sufficiently convincing. Yet, there wasn't an alternative to dropping VOD from live tv either. At the same time, this had grown and become a really hot topic, putting the project on the edge, even though it had been explicitly documented and discussed early that this split between live and vod streams will need to happen. The only way out that I had seen at this time was to turn the sole promise of "providing something so much better that nobody would ever complain about lacking VOD channels" into a reality - outside of TVnext, independent of TVnext and delivered even before TVnext. That's how the WebStreams plugin came to life. Some got convinced quickly, for others it still took a while, but as of now, I don't think that there's any remaining doubt that the WebStreams plugin is the way to go for handling VOD content in Emby - even though it's been a long way...

Most users do not have massive libraries. I would think that we could just auto mix tracks with similar genres and the results would not be that much different from using an external service.

Hi, we are working on it. Thanks.

YouTube music has a ridiculous amount of data about a ridiculous number of people, and a ridiculous amount of music. Emby lacks, and should continue to lack, that.