For instance, I am a Windows user using the VLC GUI. I saw that VLC could stream video over the Internet or LAN and thought "hey, wouldn't it be cool to be able to stream an ISO file of a DVD on my desktop computer so I could watch it from any computer with VLC on it from anywhere in the world." Long story short, it took me nearly five hours of garnering bits and pieces from various outdated examples on the Web, in conjunction with much frustrating trial and error in order to successfully stream something via HTTP and to connect to the stream via VLC to watch it. Where as a simple version 1.0.0 how-to document on the subject would have had me up and running in five minutes instead of five hours.
This is exactly the part of programming that gets the least attention and is probably the most important. Such a shame so many dismiss this this as trivial. Right now I'm designing software to be used by the military. I keep having to remind my fellow engineers that the average readling level of our target audience is 6th grade, and not to overcomplicated the required steps. My peers simply cannot take themselves out of their own college educated, electrical engineers shoes and try and see the world from someone else's perspective, aka, the perspective of someone who has never used the "right-click" button, ever, or even tried the "Windows Explorer"I guess it depends on your priorities. If you want to be part of developing a program which will have the widest possible number of users, then making it easy to understand and use the basic features is an essential part of that development.
If you want to be part of a development team basically working for techies only, and aren't interested in having ordinary people use your work, continue as VLC developers do right now.
For example, I had so many problems trying to save a video one it was rotated that I gave up, earched for a free program that specifically did that, and now use that for that specific feature. A simple button to "save" the reconfigured video would make life easier but I guess developers have more interesting things to do than think of the rest of us.
Isn't it amazing how people don't understand that volunteer developers have more interesting and motivating things to do that write howtos that will get obsoleted in no time?
You're most welcome to work on the VideoLAN wiki if you find it incomplete.
Oh, I totally agree. In fact, I do write whichever documentation my employer asks from me. But would you care to tell me how much your fellow military-contracted engineers are paid every month? I spent somewhere between 5 to 10 man-year worth of effort on VLC. For two T-shirts and one return medium-haul flight ticket. And you pretend to tell me what I should work on?
If you want a VLC manual, write it yourself or pay someone to write for you.
... time is better dedicated to improving the software, which profits millions of users than helping a single person on the forum. As such, any non-trivial question is likely to be ignored. That's life.
Return to “General VLC media player Troubleshooting”
Users browsing this forum: No registered users and 9 guests