I read your original post and it was way to confusing for me to jump in and offer an answer. VLC offers a wide variety of streaming solutions for both an Infernet and Internet with a wide variety of transcoding options.It may be the best, but if the documentation isn't clear for newbies, what the use. I entered a post and got one little, not extremely helpful, reply. I have since then added to the post with more detail of what I have been trying.
So far, I'm not impressed with this forum, it seems if you don't know what your doing and have a "little" problem or bug nobody is willing to help.
I find most people want to jump to the end without starting at the beginning. You know, like does the file play? before you think about transcoding or streaming?
Have you learned to transcode into compatible formats and proved it before jumping into streaming? Have you discovered which containers are more applicable for streaming? Have you tried to stream locally before trying to jump onto the Internet?
Streaming is the end result of the learning process and certainly not a good place to start for beginners. VLC is a tool and it can be a good tool in the hands of someone that knows how to use it or it can be very frustrating for someone who doesn't. But this seems to be true about everything in life!
Most of the people that are here have some kind of hardware or operating system problem that is keeping VLC from working properly. Unfortunately, the descriptions they offer are less than informative and more often than not exclude the machine type (CPU & GPU), the version of VLC, even the version of the operating system. When you add to this formula, peer to peer networks as a source with the possibility of corrupted files, miss labeled files and the RIAA that has assigned some 30 - 35 machines dedicated to take down the networks, the source is becoming more and more the problem. Add to this the possibility of bad or improper encoding and you have a recipe for trouble.
When the end user wants to disregard all of this and just use there system without learning to do so is like trying to get on the Internet today with out any kind of protection and saying all I want to do is read my email but I don't understand why my computer keeps dying.
![]()
![]()
This is an open source project with a wiki available for anyone to add to, you just need to sign up. We have a 'section' of the wiki just for How to, and you are welcome to sign up and add a new article explaining how to do something and links to it where you see it is appropriate. The main problem we have with a sharing of information in an open source project such as this is that many consumers unfamiliar with open projects do not understand the concepts of a Wiki or the underlying concepts of a forum, we get five copies of the same question from the same poster on a different subforum each day, with others repeating the same exact quetion, people miss the "Search" feature, or are too busy to be bothered and expect the few people who are dedicated to answer questions to be able to anser them immediately. These same people also make posts with completely missing information, or they make a general post and then a few days later narrow it down, and maybe a month later ask why we don't have X Y and Z working on A B and C when they asked about it, and all they asked about was X on C which worked perfectly then and still does now. You seem to understand all of this, and we would welcome any input you give, however if there were to be a forum section for how tos and successes, I think the moderation of such a forum would be a nightmare, and it would need to have all posts thereto moderated.The experimentation required with VLC to figure out if a given setup will work given a certain processor/computer/horsepower configuration has been quite frustrating, without having some firm yardstick or clear guidlines as to how it is supposed to perform, and what can it *really* do in real-life scenarios. Maybe it might be wise to open up a section on the forum where people might post what they are *successfully* doing with VLC, and what equipment/setup/configuration options they have used to achieve that, as well as performance limitations/considerations. That way, I think you would have fewer questions here and/or could easily point to real-world examples, which would make anyone better understand what this extremelly complex, wonderful little program can do. If someone wants to "stream over the net", they could go there to quickly find out about issues such as unicast, multicast, streaming over webservers and streaming media servers - which are all things that successful users have been using VLC for - and basically also find out how they did it.
CG
Thank you for taking the time to write such a detailed response. Actually I agree with everything you say and or suggest. While I have not done much consulting within an academic environment, I have been a consultant within a commercial environment having helped build production a post production facilities around the world and consulted for many major manufactures over new product for more that 35 years. There is no one in this environment that would cope with VLC for any period of time. It is however a unique program with out peer. The unfortunate sided of this story is that there is to little time and or resources to do the testing necessary before each official release therefore what was working yesterday may be broke today. Many of the coded updates are not tested. Plus the fact that many of the modules were written by people no longer associated with VLC. While per-say this is not the developers fault, it is an organizational problem that greatly effects the program. The developers are doing the best they can with what they have, without taking the program commercial. Most of the developers will agree that the present documentation has become antiquated.Personally, I have been trying to use VLC for quite a while, and although it is obviously a very powerful program, it is a *very* difficult program to master, specially if one is not acustomed to programs as "low level" as this. Having recently spent many hours over many days researching open-source streaming solutions, and having poured over the posts here in the forum on the issues of streaming, I have to say that so far, although I saw some questions answered, a lot of them were not - or were answered in ways that a newbie wouldn't be able to understand, or which created more questions than answers.
This is an open source project with a wiki available for anyone to add to, you just need to sign up. We have a 'section' of the wiki just for How to, and you are welcome to sign up and add a new article explaining how to do something and links to it where you see it is appropriate. The main problem we have with a sharing of information in an open source project such as this is that many consumers unfamiliar with open projects do not understand the concepts of a Wiki or the underlying concepts of a forum, we get five copies of the same question from the same poster on a different subforum each day, with others repeating the same exact quetion, people miss the "Search" feature, or are too busy to be bothered and expect the few people who are dedicated to answer questions to be able to anser them immediately. These same people also make posts with completely missing information, or they make a general post and then a few days later narrow it down, and maybe a month later ask why we don't have X Y and Z working on A B and C when they asked about it, and all they asked about was X on C which worked perfectly then and still does now. You seem to understand all of this, and we would welcome any input you give, however if there were to be a forum section for how tos and successes, I think the moderation of such a forum would be a nightmare, and it would need to have all posts thereto moderated.
Thank you for taking the time to write such a detailed response. Actually I agree with everything you say and or suggest. While I have not done much consulting within an academic environment, I have been a consultant within a commercial environment having helped build production a post production facilities around the world and consulted for many major manufactures over new product for more that 35 years. There is no one in this environment that would cope with VLC for any period of time. It is however a unique program with out peer. The unfortunate sided of this story is that there is to little time and or resources to do the testing necessary before each official release therefore what was working yesterday may be broke today. Many of the coded updates are not tested. Plus the fact that many of the modules were written by people no longer associated with VLC. While per-say this is not the developers fault, it is an organizational problem that greatly effects the program. The developers are doing the best they can with what they have, without taking the program commercial. Most of the developers will agree that the present documentation has become antiquated.
Then there is the amazing ability to put all of these things under one roof so that anyone can use it. Outside of VLC, I haven't seen anything that tries. Let alone kinda sorta works. I would say let the buyer beware! But you didn't pay for it and this is also part of the problem. So all I can say at this point is let the user beware!
PS: There is a ton of information available regarding formats, containers, streaming and how to at: http://wiki.videolan.org/index.php/Main_Page
AFAIK that doesn't exist. (by "that" i mean something that works and is free to use in the USA.)We would like to experiment with VLC streaming starting tomorrow on I2 - obviously, I would like to use a protocol that is free and legal to use in the US, and hopefully compatible with other media players (specifically WMP and QTime). Can you recommend a "generic" plain vanilla setup for streaming/encapsulation of video AND audio that would not require licensing?
AFAIK that doesn't exist. (by "that" i mean something that works and is free to use in the USA.)
You can still experiment with VLC without paying the licence though.
In short, there is no way you can do audio/video streaming in the USA without being 100% sure someone won't pull you --please stay polite-- into court over a patent issue. Should you care is point 2. Especially in an educational environment, with MPEG1, MPEG2 and MP3, with an experimental character: DON'T CARE.
There is almost 0 risk, and everybody is doing it.
Note that Theora and Ogg Vorbis are NOT patent free, unlike what its profets advocate. There just currently are no CLAIMED patents. So as soon as someone says: He that little piece of code with that small for loop in theora is part of my patent, you will need to start paying up for theora as well.
Return to “VLC media player for Windows Troubleshooting”
Users browsing this forum: No registered users and 21 guests