Requests youtube chanel

[HERIGROSIR]

Jellyfin team should make a YouTube channel
With that, you can discuss or fix your bugs with the tutorial you created
rather than just being responded to by the team on the forum who doesn't solve any problems, just answers all the questions without providing any improvements
assuming all the blame is on the user, even though it's on the Jellyfin software itself


Jellyfin team must be divided into 3 groups on one YouTube channel

- Jellyfin Windows 7 and above and its problems
- Jellyfin Linux and its problems
- Jellyfin Android and its problems


Each team must be able to answer according to their field and expertise
with the videos you make
Of course you can collect likes and subscribers to profit from it, no problem


I suspect, Jellyfin seems to be waiting for someone else to fix it, after the problem is resolved
then it will be duplicated for emby,
because they have the same problem,
emby is obviously paid, jellyfin is free,
I hope my guess is not true.


Maybe developers are more serious about Emby because it's clearly paid there
Actually, for developers who have expertise, there will be a lot of benefits even though Jellyfin is free

You can help by solving all the problems on the forum, with your help on YouTube
You can have your own free channel, or the official Jellyfin channel,
Maybe you can provide code that can be run on Jellyfin, that's an opportunity

Don't always think that sharing has to be done for money, pay attention to the big company Google, almost all of them provide useful and free things first, the same thing with Jellyfin software,
including YouTube itself, everyone can upload videos for free


Don't because this is free software, all problems in the forum are ignored,
In my opinion, that is actually a good opportunity.
OK, this is just our input, it's up to you what kind of jellyfin you want in the future

Thank you

[Venson]

i dont think emby's codebase is nowhere near compatiable with JF by now.

[1hitsong]

Jellyfin team must be divided into 3 groups on one YouTube channel

- Jellyfin Windows 7 and above and its problems
- Jellyfin Linux and its problems
- Jellyfin Android and its problems

Checkmate Apple users!

[HERIGROSIR]

i dont think emby's codebase is nowhere near compatiable with JF by now.

To find out yes or no, you can check Jellyfin (view console)
there it says when your jellyfin starts to turn on

[Efficient_Good_5784]

i dont think emby's codebase is nowhere near compatiable with JF by now.

To find out yes or no, you can check Jellyfin (view console)
there it says when your jellyfin starts to turn on

Just because the code mentions "Emby" doesn't mean Jellyfin is the exact same code-wise at this point.

[Fate]

I think videos are one of the worst ways to convey technical information. Since jellyfin is an Active project, things change, thus video would need to be constantly rerecorded and cut again.

[HERIGROSIR]

I think videos are one of the worst ways to convey technical information. Since jellyfin is an Active project, things change, thus video would need to be constantly rerecorded and cut again.

yes...that's not a problem, the video is also updated according to developments. the same as other written tutorials, what's the difference??

in fact, with videos, people will understand better in more detail

it is very detrimental if you create a YouTube channel but the video is not updated, it will not add viewers and likes of course 

but you and others can also make simple tutorials tips and tricks about jellyfin on youtube, that's also possible.

it would be better if the channel was issued by jellyfin itself and more official


There is no need to cut the video on YouTube, but make a new video with a new title and date, month and year.

[Ted Hinklater]

Dunning-Kruger is real yo

[Venson]

Producing a video that is correct, somewhat enoyable to watch and even half organised takes time.

A LOT of time.

We really dont have that, we cant even keep up with PRs and issues nowadays and you expect us to manage a youtube channel as well? no.

[joshuaboniface]

This is something we have considered and rejected. Venson and Fate give the main reasons, but to sum up:

1. Videos take an extremely large amount of time to produce. As someone trying to make a video series for my own (non-Jellyfin) FLOSS project, I know. You have to research what you're talking about, write a script, record it (often many takes), edit it, respond to questions in comments (yet another fracturing of our information base which is something the Forum was designed to prevent), etc. This is "single person dedicated 'full-time'"-type work, all unpaid because of our philosophy. And it's not something that anyone on the team thus far has been interested or is knowledgeable in. This alone sinks the idea, but...

2. Jellyfin is a very fast moving project, even more so with our current plans to increase the major release cadence. Information presented in videos now would potentially be obsolete in another 3-6 months, which leads to...

3. Videos cannot be easily updated like written documentation can. It is not a trivial task to take an existing video and change parts of it to reflect the new reality after changes; this requires a lot of work to re-record new sections, re-edit and re-upload the video, etc. In contrast written documentation can be updated and immediately become the visible, live documentation immediately and with minimal effort. Sure, new videos could be recorded, but that's a huge amount of work (see #1) to repeat over and over again.

4. Videos are terrible for documentation. I know some people love them, but to be frank, they're a waste of time. Either the video is short and super-concise (good) and gets suppressed by the algorithm, or it's a long, redundant mess for "engagement" that wastes tons of time getting to the point and is worse in every way than written documentation. Further, video documentation can only cover an extremely narrow area in one video, necessitating an explosion in the number of videos required to cover every possible answer.

So, for documentation the answer is a hard "no".

Now, all that said, would something like "a video version of a major release blog post", highlighting the big features, be cool? Sure. But it's already a lot of work and struggle to even write textual blog posts, never mind all the extra work for a video. I just really don't see it happening, at least officially from us, any time soon.