B&W Driver
Well-known Member
I downloaded and unzipped FFmpeg for Mac tonight. As I had created a special folder for experimenting with the utility, I placed the unzipped Unix executable -- known simply as "ffmpeg" -- in the new folder and proceeded to place some quad audio files that I previously ripped from an SACD-A and, subsequently, converted from .dsf to .wav (via JRiver Media Center for Mac).
I'm not much of a Terminal user, but, after I got the ffmpeg and the audio files into the new folder, I launched Terminal and used the "CD" command to move over to the object folder. After I arrived at the correct folder, I typed in the following command to attempt my first conversion via FFmpeg: "ffmpeg -i 01.wav -strict -2 01.mlp". No quotation marks, of course, but the point is that FFmpeg seems to be unhappy with the command I used. [NOTE: all of the audio file/track names were changed to simple numbers to save typing time]. In the end, here's what I got back from FFmpeg:
As you can see, after using the "ls" command to ensure that all of the .wav files were present in the new folder, called "audioconversion," I typed in the command string I mentioned before (above the screenshot) and got this back: "-bash: ffmpeg: command not found." As I mentioned, I'm not much of a Terminal user, so I employed a command string that was recommended to me for audio file conversion. The fellow who was kind enough to pass along the command string I used was a Windows user, so is it possible that FFmpeg for Windows and FFmpeg for Mac employ different commands?
Thank you kindly for your time
I'm not much of a Terminal user, but, after I got the ffmpeg and the audio files into the new folder, I launched Terminal and used the "CD" command to move over to the object folder. After I arrived at the correct folder, I typed in the following command to attempt my first conversion via FFmpeg: "ffmpeg -i 01.wav -strict -2 01.mlp". No quotation marks, of course, but the point is that FFmpeg seems to be unhappy with the command I used. [NOTE: all of the audio file/track names were changed to simple numbers to save typing time]. In the end, here's what I got back from FFmpeg:
As you can see, after using the "ls" command to ensure that all of the .wav files were present in the new folder, called "audioconversion," I typed in the command string I mentioned before (above the screenshot) and got this back: "-bash: ffmpeg: command not found." As I mentioned, I'm not much of a Terminal user, so I employed a command string that was recommended to me for audio file conversion. The fellow who was kind enough to pass along the command string I used was a Windows user, so is it possible that FFmpeg for Windows and FFmpeg for Mac employ different commands?
Thank you kindly for your time