2024-03-06, 08:56 PM
(This post was last modified: 2024-03-06, 09:07 PM by flynnz. Edited 3 times in total.)
I get the same issue of transcoding all the time when using the Android JF app, not just browser. I assume that is what you mean, but correct me if there is another method on Android you are referring to.
I do notice a lot of transcoding just for audio and the like, and while it doesn't pin the processor, if I have a few people transcoding at once, it does still very much become an issue
and yes, of course, but the issue is, I have a huge library with tons of videos that arent supported as do many others from what I read, so I was just wondering more how people deal with it. When you get a file/codec that's not supported, do you just throw horse power at it? or do you re-encode it? I understand if you are using a client that works with everything you probably don't bother.
If your use case is just for viewing yourself I understand it's probably not an issue, but if you have a varied collection of users and files it makes using JF a bit more of a challenge, so I was specifically talking within that context. (and as far as I can tell, even if I had everyone switch to the Android app instead of browser I would still have tons of transcoding going on)
(2024-03-06, 08:34 PM)LambTalk Wrote: Container "transcoding" (remuxing) isn't an intensive task either, and happens pretty transparently. So if your device supports HEVC, but doesn't like mkv containers, then a simple remux to mp4 during playback shouldn't cause any strain.
Same with audio transcoding, it's not intensive at all.
I do notice a lot of transcoding just for audio and the like, and while it doesn't pin the processor, if I have a few people transcoding at once, it does still very much become an issue
(2024-03-06, 08:34 PM)LambTalk Wrote: The only time a client would transcode is if you're trying to play a stream (video, audio or subtitles) that uses a codec or format not supported by the client.
and yes, of course, but the issue is, I have a huge library with tons of videos that arent supported as do many others from what I read, so I was just wondering more how people deal with it. When you get a file/codec that's not supported, do you just throw horse power at it? or do you re-encode it? I understand if you are using a client that works with everything you probably don't bother.
If your use case is just for viewing yourself I understand it's probably not an issue, but if you have a varied collection of users and files it makes using JF a bit more of a challenge, so I was specifically talking within that context. (and as far as I can tell, even if I had everyone switch to the Android app instead of browser I would still have tons of transcoding going on)