Oh yes they do. If I don't answer you get people screaming 'why doesn't no one answer my question. someone please answer my question, I really do need help.@The DJ
hey mr.president, take it "frekin'" easy because nobody forces you to answer my "freaking" thread. thanks
That's because these DLLs are compiled for intel/amd processors (so-called x86 CPUs), which aren't compatible with the ones, which are used in Macs (PPC CPUs). Furthermore, these DLLs are not compiled by MPlayer team, but copied from existing proprietory apps, so you cannot create a Mac version of them. Additionally you might have noticed that there are no DLLs on Macs (there's something similar, but technically not the same at all).Funny though that Linux users can view Indeo Video 4 and 5 files and OS X users can't.
But it should be possible to use proprietary DLLs in some way - just distribution along with VLC would be a violation of the license IIRC, or am I wrong here?As stated above, the source code of the DLLs is not accessible by the public, so they cannot used in VLC because its license forbids this.
I do not know whether the GPL supports this. I think even the FSF does not know this, as you can read in their FAQ on the GPL. This would have to be discussed by the team. As far as I understand the GPL, it forbids such a solution.So it would be great if I could put my proprietary DLLs into a codec-folder that VLC can access and use...
Not neccesarily the user violates the lizecense. He can have the dll legally.The player would only have the ability to load the lib, the user would download the proprietary dll and the USER would violate the license by loading the proprietary dll.
Is this a problem with YOUR license? I can't understand that this is a no-go.We see this more as a maze in the GPL license then that it is actually a possibility and an intention of the license. Therefore we choose not to pretend we don't know what would be going on if this were implemented and won't be adding it to VLC.
I want to look the videos with VideoLAN. They do not need to distribute the libraries.Well, you can take the Windows DLL and use it in Linux. This doesn't necessarily violate the license, although distributing it together with VLC might.
There is no need to write the encoder, the encoder is in the libraries.If someone wants to figure out IV50 encoding and write us a decoder then maybe it can be supported in VLC.
The player would only have the ability to load the lib
The webcam was only one point to use the encoder.But I don't see why anyone would waste their time when they could have bought a better webcam instead.
just search the postsI don't know about "a lot of interest" in IV50
just open a new threadI see a lot more interest in WMV3 and RV30/RV40.
Well hypothetically VideoLAN could use the codec if it was already installed. But this would only work for people who bought the quickcam and installed the logitech software. It wouldn't work for anyone else. You couldn't send the videos to anyone else and have them watch it. So this is rather pointless.I want to look the videos with VideoLAN. They do not need to distribute the libraries.
NOBODY cares about the webcam, I agree.But this would only work for people who bought the quickcam and installed the logitech software.
Yes, I understand this.The point is that reverse engineering a codec is a TON of work.
Return to “VLC media player Feature Requests”
Users browsing this forum: No registered users and 13 guests