Yes you wrote a script great. But one has to download all of these developer tools which are over 2gb and macport to run linux programs when you can do it with apples native programs?
One does *not* have to download the developer tools. They are on the install disks for OS X that came with the computer. Furthermore, what comes through MacPorts are *not* linux programs. They are programs that can be run on multiple platforms. In fact, many of them run on Windows as well. Just because there development may (or may not) have started on a *NIX, doesn't mean it's a linux program. The GIMP is a good example of this. Its development started on linux, but it has been ported to Windows and Mac OS X and... i.e. it's now cross-platform *not* only linux.
I think that you are confusing "apples native programs" as bundles. This seems to be confirmed as I believe you are getting people to download 3rd party software for use in your tutorial (e.g. the mkv tools) which wouldn't exactly be considered from Apple.
The GIMP can be downloaded as a bundle. So, can many other programs that also run on other OS's. Just because something runs on linux, does that make it a "linux program"? I think not.
NOTE: If you were the Seda that commented on my blog, I
did give you an alternative that would have saved you the disk space required by the dev tools. Just saying as you seem to think that this dev tool disk space thing is required for all time. It's not.
"Please note that this script does not replace the tools that need to be installed as described in those tutorials. What this script does do is use those tools so you don't have to."
Those tools that you speak of MacPorts etc, etc. take up a lot of room that some people may not want on their computer, such as myself and being very tight about how much HD space is used.
With the sizes of hard-drives today, it would be rare and/or misuse of hdd resources to encroach on its limits. Honestly, if you're running a relatively modern Mac, which you pretty much would have to be if you're running 10.4/10.5, then you're most likely mismanaging your hdd. I would imagine that if you would burn the stuff that you want to keep yet don't use and remove the cruft, you'd have a lot more space to spare. I'll also point out that external hdds are really
really cheap these days. And if you're wanting to do a lot of this conversion stuff, with the size of those files...
Also, perhaps you misquoted me. "Step 2.) For those who are converting the ever-famous 720p movies that are usually under 4GB welcome to the show." The word usually is in there for a reason.
How about this wording: "IF YOUR MKV FILE IS SMALLER THAN 4GB ie. 720p films SKIP THE FIRST STEP (if you are using a 1080p file over 4GB please proceed)".
Your lack of consistency is not my problem, it's yours. The "i.e." "word" is used for a reason too. So, before you go around cherry picking your data, perhaps you should become familiar with the entirety of what I was looking at.
That detail is wrong.
I personally don't understand why I have to justify writing this tutorial, or why I'm being bashed for it. My guide isn't something you HAVE to do, just recommendations. Perhaps me labeling this a DEFINITIVE GUIDE, I should have put "EASY ALTERNATIVE" or "DIFFERENT WAY". But in no way, shape or form was I trying to put down everyones guides. People say why not use Parallels, or VMWare or something to that nature and run MKV2VOB. Because why do people have to have all of this software on their computer? Quicktime comes with your computer, simple as that. The other programs that are required are small to say the least.
I was explicit about why I said what I did. It's all there in black and white. If you can't see it, then I can't help you.
Also, there are problems with the emulation to run MKV2VOB; slower and time consuming. It would require another OS to be "installed" somewhere else which would incur extra cost ($). It would require more than just a little bit of hdd space (
far more than MacPorts btw). There would be quality loss. Similarly for use with bootcamp. Among other issues, one of which you bring up.
"But, you're late to the game reproducing old easily found work."
I've seen it. Seen in all in fact. I have yet to find one to be step by step, simplified. I wrote this guide so people didn't have to get frustrated like I did. I tried following the guides written by others for this Quicktime method. Failed everytime, or someone was using a combination of programs for no apparent reason. After I wrote this I told my girlfriend, "I think this is so easy you could probably do it if you read it step by step." It's a shame that you immediately go to putting others down for trying to help. To me this is not a pissing contest. I only signed up to help others.
You're assumption that this is about a "pissing contest" is a very bad one. If you would have been honest, reasonable and respectful about what you did and what others did, then I would have never commented. Also, please see my comment directly above.
It's a shame that you didn't get the reason of why I said what I did even though it was explicitly stated. I pointed out problems with your tutorial including taking credit for more than what you did, have some details wrong and your general tone. Yet, you're complaining about this and pointing the finger at me instead of fixing the errors. Quite frankly, I think that this reflects far more on you than me. Myself being only a little bit of a dick about it whereas you are doing nothing more than tossing accusations.
Furthermore, I'm not trying to prove my intelligence over you, because clearly you know more about this than me. I think the idea of your script was an excellent idea, although not the prime choice for everyone. Don't think I was trying to steal anyones thunder, or make anyone look ''dumb''. I was just simply trying to give others an option to do this more simply in words that normal folks could possibly understand. So MY apologies if I offended you, because it was not intentional.
I never said anything about proving intelligence. Where you got that I will never know. I also never said anything about my tutorial being the end all be all. I was just referencing it because it was not only in this thread, but referenced just a few posts above yours. I'll also mention that if you go to the being of this thread and read through it, you'll see two other tutorials before I posted mine. I believe all three are unique ways to get the conversion done.
If you wanted to give another option, then give another option. But, you didn't provide another option. You pieced together other peoples work and wrote a tutorial on that. That is a VERY different thing. THAT is where the honesty, etc stuff comes in.
Again, if you would have been honest about that, then this conversation wouldn't be happening.
You have to think about this like open-source. Everyone gets credit for what they've done not putting down others work (the "tidbits" comment btw does put down others work). Reference what your sources are, but failing that, mention what is and is not your work. THAT is the honest, reasonable and respectful thing to do.
So, the ball is now in *your* court. Will you fix the problems with your tutorial? Or are you just going to be obstinate and leave it the way it is?