Search the Community

Hi, let me start off by saying that Emby its the best streaming server out there! Nice job and keep going! I think it would be great to have an automatic feature that convert's .pgs subtitles inside .mkv files to .srt. Let me give you an example of use case that's actually what I'm dealing right now: I have a 55" LG 4K TV and i'm using the Emby app whis is beautiful btw. I have several 4K HEVC BluRay movies in .mkv files in the server that have .pgs subtitles and different audio tracks for langs., the thing is that for me to be able to watch those movies I had to turn off all the transcoding options in my user profile. If I turn on the transcoding options, it tries to burn the subtitles by transcoding the Video file. I think that instead of transcoding the video file, it should be doing something like converting those .pgs existing subtitles to .srt files that are compatible with most DLNA devices. I think it would be awsome if we could cron this to run on the less server busy hours so the .srt file is ready to play whenever is needed instead of doing it on the fly when maybe there's no enough CPU resources.

Hello, I use Emby server and my client use often the transcoding option. However, once in a while (like every 2 weeks), all my files failed. I can't watch any movie except if I restart the server. Here is a log fail just before this happen. You can see a Conversion failed at the end of the file. My question are : -Why is this happening ? - Is it because of the line "No space left on device" ? If so, how to program an autopurge of transcoding cache ? (Because it fill it up in 2 weeks, I don't need to keep it that long). - Why do I have to restart the server ? In this case everything are ok (including the movie I wanted to watch), does that mean a server reboot purge all transcoding temp files ? If so how to program it (see question above) The client used is a raspberry pi with embycon. Thank you in advance for the help Log.txt

Hi, I set up a conversion rule on my movies library, to convert to "original media folder, next to original files" and when I checked on the status I noticed that the conversion is making 31 additional copies of the same file in the directory. Screenshots attached. Any ideas on what's going on? Screenshots, server log, and ffmpeg logs are attached. Server is running on Windows pc, libraries reside on readyNAS, being accessed from linux laptop. I checked the files - they are all duplicates of the original media. They are also seemingly not following the conversion settings - I set for 2.5MBps and these are maxing out at maybe 250-300kbps bitrate. embyserver.txt ffmpeg-transcode-e4816630-7d67-4498-94a6-1e961f05e815_1.txt

Hi all, Recently, in order to more efficiently use my storage space I have been enjoying using emby's conversion feature to convert and replace less frequently watched content with lower bitrate hevc/mkv files. Although I have the conversion thread count and performance settings set to max, one conversion job running at a time barely uses 15% of my R730's 48 CPU cores. Would it be possible to add a setting in the conversion menu called "Maximum parallel conversion jobs allowed" that defaults to 1 (one)? This would maintain the existing behavior but would allow us with many spare CPU cores to have more than 1 conversion job running and take advantage of our hardware. I've attached a screenshot of an example of a batch conversion job for a season of television that I feel would benefit from this added feature. Thanks for your consideration

Hi, just purchased emby premiere (great work guys!), and tried converting some files. Unfortunatelly it turned out my hardware is just too old and cheap to do so, so after a day of having files at 0% conversion rate I just deleted the conversions. For reference, I had ticked to replace the original files, if it helps. Anyway, those media now won't play anymore, getting a file not found error in the logs (and a simple generic reproduction error in the UI). I tried cancelling and re-downloading the files, or even readding the original ones but I keep getting the same errors. Any other media plays fine, so it's not a general emby issue. I also tried cancelling the schedule for converting files, since I had also ticked the "convert any new added files option". Not sure what to do in this situation. Happy for a solution to just go back to square one, since I won't be converting any files any time soon. Thanks and keep up the great work! PS: didn't attach logs because of possible personal info popping up, but happy to attach snippets of them if you can tell me which specific logs or snippets might help.

I am in the process of converting some of my MKV files to play properly on Apple TV. I tried out the conversion tool and it works great and the quality is great, but the subtitles embedded in the MKV file are lost during conversion. Is there a way to keep those? Application version: 4.7.1.0 MacOS Not sure which log to provide.

Hello! I have several libraries with content to which I've been applying conversions to hevc/aac. The libraries are a mix of H264 content and hevc/H265 content. Up to now I've been manually evaluating each entry in the library before creating a new conversion task. However, it's pretty tedious. Does anyone know if it's possible to create a conversion task that will only convert content that is not already hevc/aac encoded? The options I am selecting are replace original, custom, mkv, hevc, aac, original quality. However, if the content is already hevc/aac encoded it looks like the task is still copying the data to a new container. The objective is to standardize the content format in my libraries to hevc/aac. Once the conversions are all complete I'll create a standing conversion task for each library to automatically convert new content. I appreciate any thoughts. Maybe I'm just doing something silly. As a side question, not super important, but I'm curious: one instance so far the original data was H264 encoded at 1 Mbps and the conversion to H265 increased the bitrate to 2 Mbps (same options selected as above), resulting in an overall increase in file size. I was able to correct it by modifying and performing the conversion job again. Can anyone point me to documentation that explains how the selection process for "original quality" works? I work with APIs day in and out at my day job so I've been toying with maybe writing some logic to automate submitting conversion tasks if nothing else.

Emby client started a conversion process and I noticed it and stopped the process on the server-side. Now, the client's device tries polling the server on the conversion/sync progress and it appears to make Emby refuse all connections from that source (from my nginx proxy, so basically any connections through my duckdns.org domain) and results in a 502 error. My setup is: Router port forward ports 80, 443 --> nginx-proxy-manager hosted on docker on my Ubuntu (192.168.1.13), which routes to my Emby Server on Docker Nginx logs attached, Emby Server logs attached as well. # EMBY SERVER LOGS 2022-02-08 02:27:26.449 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/6/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.450 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/3/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.451 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/4/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.453 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/5/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.455 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/7/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.462 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/8/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.464 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/9/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.464 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/10/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/14/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/12/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/13/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/15/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.466 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/16/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 # EMBY SERVER LOGS 2022-02-08 02:32:31.007 Info Server: http/1.1 Response 204 to 192.168.1.3. Time: 13ms. http://192.168.1.13:8096/emby/Sessions/Playing/Progress 2022-02-08 02:32:39.741 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313277ms. http://emby.mydomain.duckdns.org/Sync/JobItems/9/File 2022-02-08 02:32:39.955 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313501ms. http://emby.mydomain.duckdns.org/Sync/JobItems/5/File 2022-02-08 02:32:40.006 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313193ms. http://emby.mydomain.duckdns.org/Sync/JobItems/25/File 2022-02-08 02:32:40.130 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313313ms. http://emby.mydomain.duckdns.org/Sync/JobItems/24/File 2022-02-08 02:32:40.276 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313809ms. http://emby.mydomain.duckdns.org/Sync/JobItems/16/File 2022-02-08 02:32:40.675 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313840ms. http://emby.mydomain.duckdns.org/Sync/JobItems/38/File 2022-02-08 02:32:40.812 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312229ms. http://emby.mydomain.duckdns.org/Sync/JobItems/57/File 2022-02-08 02:32:40.897 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312303ms. http://emby.mydomain.duckdns.org/Sync/JobItems/59/File 2022-02-08 02:32:40.974 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312381ms. http://emby.mydomain.duckdns.org/Sync/JobItems/67/File # NGINX ERROR LOGS 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/3/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/3/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/4/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/4/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/5/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/5/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/6/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/6/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/7/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/7/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/8/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/8/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/9/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/9/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/10/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/10/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/11/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/11/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/12/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/12/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/13/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/13/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/14/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/14/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/15/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/15/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/16/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/16/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET embyserver_redacted.txt embyserver-63779937295_redacted.txt nginx_error_redacted.txt

Hello friends. Yesterday I started the conversion of a series (a kid cartoon); after some time, the conversion finished, but the operation is stucked with "Ready to transfer" message. I tried to force the transfer from the scheduled operations, but it is still in the same situation. I attach an image, but let me know if you need other info. Thanks!

Running The Nvidia Shield Emby Server 4.5.1.0 on a 2019 Nvidia Shield Pro. Attempting to use the Nvidia GPU to do hardware trans-codes has never worked for me. Ever hopeful, I wanted to test under 4.5.1.0 and discovered a completely different problem. I attempted to transode a file from H264 to HVEC. That first conversion failed as before. I also tried to convert the file to a 4MB/sec version. Hardware trans-coding of that failed as well. I did the same for 3 additional files to test whether or not it was a problem with that specific file. All failed to used the hardware encoder. However, when I went back and examined the logs, in all cases Emby attempted to convert the first file, NOT the file I asked it to convert. Conversions were started from the Movie page in some cases and from the library thumbnail for the movie in others. A screenshot of the Logs page and relevant logs are attached. (The screenhot to establish the order of the transcode logs). The Remux log came from playing the last movie to confirm its was not originally shot in 16 by 9 (it was however released letter-boxed) and mostly in monochrome. It's possible that the initial problem was caused by cancelling the first conversion from the dashboard. Allowing it to complete software a software trans-code in all cases would have tens of hours. embyserver.txt ffmpeg-remux-3b027453-a1da-4a8a-811f-c14d291c3ebe_1.txt ffmpeg-transcode-3cb5e847-7345-4bb5-b335-9a1e7e88e3c6_1.txt ffmpeg-transcode-8db60443-f8f7-4cc2-851e-aa53df25e619_1.txt ffmpeg-transcode-bd201aa7-eece-4a32-ae0c-3fe8ae75076a_1.txt ffmpeg-transcode-cc0c53cb-384f-47a0-92d2-8172e76f6c30_1.txt ffmpeg-transcode-d13fff65-36f7-48c7-b57a-9e29c7b38769_1.txt ffmpeg-transcode-d715900d-b7ae-4f42-8d84-a4a8d04c4ca2_1.txt ffmpeg-transcode-da1997bb-81b1-412e-ab21-10b73c21c3a5_1.txt

Emby Server is running on a 2019 Nvidia Shield Pro with and additional 128GB of flash on a USB 3.1 stick. All attempts to convert .ts (transport stream) files fail. The current status of the process is also inconsistently reported on the Dashboard "current tasks" vs the Conversions page. The embyserver log and a possibly relevant ffmpeg-transcode log are attached. The conversion was run by emby user "ram". I did put the logging into debug mode before attempting the transcode of "Japan Fried Chicken - Christopher Kimball's Milk Street Television". The logs are attached rather than sent directly because it is not at all clear what is meant by "the home page settings row" in the context of the webUI Emby screens. I was unable to find a "new tile" anywhere in any Emby screen accessible over the net. The "Remove Download" button on the Conversions page is also misleading. It implies that the converted file will be removed, which is clearly not the case. embyserver.txt ffmpeg-transcode-b2e611b9-10f3-4cf3-bb4e-e6440529ee63_1.txt

Hi, A few weeks ago, I renamed all my content according to the convention. I also renamed my moves with the right version (4k/hdr/1080p/x265) at the end. Here's an example: /Movies/Fury (2014)/Fury (2014) - 4K x265 HDR.mkv I've also setup to automatically make a low quality x264 copy for devices that doesn't support hevc or for LTE streaming. I used the "Mobile" Profile at 4Mbps Since then, the conversion took the file but added " -mobile" at the end of it instead of removing whatever is after the Hyphen. Ex: /Movies/Fury (2014)/Fury (2014) - 4K x265 HDR - mobile.mkv instead of: /Movies/Fury (2014)/Fury (2014) - mobile.mkv Then, it proceeded to also make a copy and transcode the new file. Now my directory looks like this: /Movies/Fury (2014)/Fury (2014) - 4K x265 HDR.mkv /Movies/Fury (2014)/Fury (2014) - 4K x265 HDR - mobile.mkv /Movies/Fury (2014)/Fury (2014) - 4K x265 HDR - mobile - mobile.mkv /Movies/Fury (2014)/Fury (2014) - 4K x265 HDR - mobile - mobile - mobile.mkv etc. I'm not sure what I did wrong or what logs you need, let me know and I'll edit this post.

Hi all, I am converting some SD quality AVI files to TV format at 1.5MB/s. However these are coming out 100MB larger. So 366MB->491MB. Can I get some help with the settings for the following... H.264 encoded MKV Files SD 480p ~350MB HD 720p ~ 1 GB FHD 1080p ~ 2-3 GB Appreciated.

Premise Emby is a media server which manages a media collection so the user does not have to do so. Basis for Feature Request Part of managing that collection is conversion to modern, appropriate media types that utilise better codecs, better encoding techniques. Presently people do most of this outside of Emby. Discussion The underlying tool being used for conversion is ffpmeg, see attached log. What I would like to see is an Advanced Conversion page which exposes some of these options to allow people to better manage their media conversion requirements. Then save these settings into a user-created named profile which can be exported or imported. This profile is then be applied it to a folder or file in the metadata of their collection. Doing so would initiate a conversion process with the settings of that profile. Benefits Current conversion options are limited. The Original Quality setting gives you files with 3MB/s bitrate from any source. Exposing more advanced options would allow the user to define specific conversion requirements and save them for use in their collection. The ability to export/import settings opens up a whole new class of community support. Conversion profiles can be shared between members and it is quite likely you will end up with a subculture of conversion expertise. As one person rightly said "giving advice on encoding is a lifetimes work" so its the community themselves who can do it best. Given the development of profiles and settings in a community of like minded people these can filter up to the Devs on which advanced features can be included in future releases. Reputation Given the right interest and gradual development Emby could easily become known for the best media management of all its competitors, something to distinguish itself in a competitive market. Devs Encoding and developing of such really is a work of passion. So its could easily become a pet project of some Dev to put together an advanced conversion page internally and slowly test out the options. Support Advanced encoding options are really out of scope when it comes to support. The core product does what it needs so if a forum is created for Advanced Conversion then right up front can be disclaimer that use of non standard profiles is at a users own risk. On the other hand, Emby devs working with the community are likely to develop some included advanced profiles that are supported when used for conversion. Thanks for listening. ffmpeg-transcode-a0dd4aa0-cce4-4e99-9e36-76d7599cc2e1_1 (4).txt

Bonjour, J'ai acheté Emby Premiere pour pouvoir utiliser la conversion de fichier, mes appareils ne permettant tout simplement pas la lecture de fichiers MP4. J’espérais que ça me permettrait de gagner du temps en m'enlevant cette charge de travail, j'avoue que je suis très déçu du résultat. Une fois la conversion terminée, tous mes fichiers sont en MKV sauf ceux qui étaient à l'origine en MP4. Résultat mes fichiers sont plus volumineux qu'à l'origine, ce qui me pose un problème de place, et j'ai toujours mes fichier MP4 illisibles sur mes appareils. Pourquoi Emby refuse-t'il de convertir les fichiers MP4 en MKV ? De plus il n'accepte de convertir que des médiathèques entières, impossible de le faire uniquement sur une série ou même un seul fichier. Pourquoi ?

I've having a lot of different codecs and file formats in my library, causing a lot of unnecessary transcoding and wasting space when older codecs are used. I'd like to convert those to modern codecs. I'd like to be able to create various conversion profiles instead of having to set these for every single file, including setting the new name if I select the new files to coexist with the original item. Also I'd like to be able to select multiple files at once and then just select convert from the menu and select the profile I previously created. With my library is probably going to take a year or more to get everything converted, but I believe it will be worth it. @@softworkz If you want any files for testing still, please PM me with what you'd like...

Hello People, What I am trying to do is to convert all my movies into smaller file for mobile devices. What I want to achieve is that emby to choose the appropriate resolution of the movie when I play it. Now what I see is that the conversion is name-ing the movies wrong. I read the https://support.emby.media/support/solutions/articles/44001159102-movie-naming movie nameing convention for merge multi versions but to do it manually for all the videos just not to be duplicated on media is a hard task to do What I want is to have 1 movie poster with 2 different movie for the appropriate device and also to make emby to choose the right one. Is this possible?

Hi there. Moving over from Plex I have set up Emby server on my shield (latest 16GB model) and it is all working well. I have all my media on a large external usb drive and have set all the temp folders (cache, transcode, metadata, sync etc) to said drive. When syncing files, larger mkv files especially seem to start converting at a good rate (about 4x ish) and then after around 20% (slightly varies per file) the conversion stage just hangs. The Device/sync settings page simply displays the percentage it is stuck on as does the same part of the iOS app. The ffmpeg log seems to cut off mid line and not be updated any further when this happens. Logs attached. Any help much appreciated. I have tried varying combinations of speed throttling, cpu cores etc to no avail. I have even opened the file in the sync folder on the server and it seems to play up until the point the conversion failed. Plenty of space on the drive and the file plays fine when simply watching via the iOS app or tv emby client (lg). Thanks, Richard. ffmpeg.txt HardwareDetection.txt embyserver.txt