View Full Version : Container documentation
emmel
9th August 2006, 21:20
Yes, works for libebml, but not for libmatroska.
Well, there you have cygwin and macosx also to choose from. Anyways, it works fine.
It's not that I can't do it, but I don't *want* to. I will *not* download all that crap again and install it ad polute my system because it can't reside in a directory which has spaces in it. And I won't pollute my system with a stupid dos-like prompt that uses linux commands & directory syntax. This is windows. We like GUIs and not to type commands ourselves.
If you don't like it, then use vc6, vc7 or do your own port.
All MinGW -stuff is located in one single diretory and your system is supposed to remember only one single environment variable (path). No fooling around with the registry. It is not spread all over the disk and system and it does not pollute anything. Using spaces in names is a bad practise anyways.
Just use it to build the libs, and then continue with the tools you prefer. Knowing linux or mingw is simply a must whether you like it or not. GUIs are supposed to make life easier, but if and when they do not, it is better to forget about them and get back to basics.
Eretria-chan
9th August 2006, 21:52
If you don't like it, then use vc6, vc7 or do your own port.
I tried, but it didn't work did it?
All MinGW -stuff is located in one single diretory and your system is supposed to remember only one single environment variable (path). No fooling around with the registry. It is not spread all over the disk and system and it does not pollute anything. Using spaces in names is a bad practise anyways.
I know it might not be a good idea, but programs that have issues with it needs to be fixed. All my programs are installed into a directory which has a space (Yes, a SPACE!).
Just use it to build the libs, and then continue with the tools you prefer. Knowing linux or mingw is simply a must whether you like it or not. GUIs are supposed to make life easier, but if and when they do not, it is better to forget about them and get back to basics.
We're not living in DOS anymore, so grow up. That's all the advice I can give to linux. It's quite pathetic. No wonder no one but hard-core savvy users use it.
Sirber
9th August 2006, 22:06
We're not living in DOS anymore, so grow up. That's all the advice I can give to linux. It's quite pathetic. No wonder no one but hard-core savvy users use it.Linux ain't dos... :mad:
Linux ain't easy
Life ain't easy
so Linux is Life! :D
Eretria-chan
9th August 2006, 22:08
Linux != user friendly
Linux == pathetic
On a second note, let's stop this pointless discussion. I just want to build parser for container but it isn't easy. Especially not thanks to all the linux crap out there.
Sirber
9th August 2006, 22:09
Linux != user friendly
Linux == pathetic
Windows == user friendly
Windows === pathetic
=== is php style, means equal and same type
foxyshadis
9th August 2006, 22:19
Well, to be honest, open msys and typing
cd /ffdshow
make
has never been a particular burden on me, even though I vastly prefer IDEs and only use msys when forced. (Using fstab to symlink the folder.) I save that for useless compiler errors. If it's an affront the process of running the commands can be automated into a batch file. But most free container/codec formats are developed on *nix and use their conventions.
Once you have the dll all you need is the .mak to use it to link with any other compiler.
Putting spaces into folder names is not "bad practice", and not supporting them is just stupid in 2006 - but mingw/msys/cygwin has never given me trouble with them, for all their occasional dire warnings. Dev-C++ (and some ancient win16 crap) is the only software I know that refuses to read them. C'mon, it's not 1986 anymore, even unix supports them. Assuming everything's going to be in /bin is about as laughable and hackish as software that assumes everything goes in C:\Program Files or C:\Windows. [/rant]
Eretria-chan
9th August 2006, 23:56
Windows == user friendly
Windows === pathetic
=== is php style, means equal and same type
Well, in C++ == means equal and != means not equal and I'm a c++ user.
Aside from that, is there any doc that tells how to use libmatroska? There is none from what I could see in the source download.
Oh and did I tell you that it's extremely stupid not to provide binary downloads? Not everyone has a compiler y'know... or the knowledge to use 'em.
I can copy the stupid dll and libs and includes from mediainfo and screw msys/mingw completely.
squid_80
10th August 2006, 10:03
Well, in C++ == means equal and != means not equal and I'm a c++ user.
Aside from that, is there any doc that tells how to use libmatroska? There is none from what I could see in the source download.
There's example programs in the test directory.
Oh and did I tell you that it's extremely stupid not to provide binary downloads? Not everyone has a compiler y'know... or the knowledge to use 'em.
No, providing binary downloads is stupid since practically every compiler has different standards. And what would you do with them if you didn't have a compiler?
Haali
10th August 2006, 10:11
There are few layout rules for matroska containers:
* The EBML header must precede other elements in the file
* It's preferable to have the CRC element at the start of its parent node
* Blocks in clusters must be properly interleaved and should appear in coding order
All other elements can occur in any order, though most files will have SegmentInfo, Tracks, SeekHead and other similar info about the file near its start, and some of it at the end (like tags).
Eretria-chan
10th August 2006, 12:46
There's example programs in the test directory.
I'll check them out but I don't have much hope.
No, providing binary downloads is stupid since practically every compiler has different standards. And what would you do with them if you didn't have a compiler?
Providing binary downloads is the smartest things anyone has done... yeah...
Do I need to bother myself with what is inside the source? So far as I can tell - I only need the dll, headers and libs and that's all.
Eretria-chan
10th August 2006, 15:19
On a side note, the avi index (idx1) seems to refer data out-of-order. If I scan the file manually and find all the audio samples, then write them to a file, then it can be played back. But when I do it with the index, it doesn't play. I noticed that the first found sample in the file was not the same as the first sample referd to in index. Is it supposed to be like that?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.