Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Converting via command vs foobar2000 (Read 1485 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Converting via command vs foobar2000

 I came across a post on another message board that says, supposedly, command line is better. More reliable. I don't get it. Isn't it all the same?

Re: Converting via command vs foobar2000

Reply #1 –
The command line would only be better if some options weren't implemented in the front end application that you needed to use.  The reality is that you're simply making things more complicated to use as those might be options few people would ever use.

Re: Converting via command vs foobar2000

Reply #2 –
CLI implies that between User and Program there is only the hands (with the head) of the User and bugs of the Program. GUI add bugs of GUI. in theory.
 

Re: Converting via command vs foobar2000

Reply #3 –
And CLI adds the complexity of operating a CLI. For instance, unlike foobar2000, and many modern conversion utilities, even CLI based... raw CLI encoders don't usually take advantage of multi-threaded encoding of any sort, and will only encode a single file at a time, unless you manually invoke the tool multiple times from multiple terminals, or use special scripts that run multiple instances in a forked background process.