MulletRobZ Posted February 20, 2004 Share Posted February 20, 2004 Oh blast it! I am trying to convert some MP3 and MIDI files to WAV using this, but it won't let me, even when I typed in the instructions correctly (mpg123 -w (filename.mp3) --wav (filename.wav) ! Is there a better audio converter than this around or is there some configuration I have to do? Link to comment Share on other sites More sharing options...
MrStaticVoid Posted February 20, 2004 Share Posted February 20, 2004 You should be able to do something like mpg123 -s filename.mp3 > filename.wav, or just mpg123 --wav filename.wav filename.mp3. -w and --wav are the samething according to mpg123's man page. Link to comment Share on other sites More sharing options...
MulletRobZ Posted February 20, 2004 Author Share Posted February 20, 2004 Just found that out thirty minutes ago as I found a blurd on Google about this, but there is one question I have that remains. How do I convert MIDI files to WAV by using Timidity? There appears to be no visible way of doing this, yet it advertises it can do that? The documentation doesn't seem to be present. Link to comment Share on other sites More sharing options...
kemical Posted February 20, 2004 Share Posted February 20, 2004 GooGOOOOGLGLLGOGLELELEEELELLELELEL IT. Link to comment Share on other sites More sharing options...
Danrarbc Posted February 20, 2004 Share Posted February 20, 2004 -Ow1S outputs to 16 bit stereo wav, the sample rate is determined by the other settings you use. timidity -h will help you out, it's all in there ;) Link to comment Share on other sites More sharing options...
MulletRobZ Posted February 20, 2004 Author Share Posted February 20, 2004 Not much use, so I just e-mailed the developer to see if he can spit it out in plain English instead of the useless documentation method which I read over at least twice in detail. Oh now what! Upgrading the ALSA packages in Slackware caused my soundcard to not function properly! I wonder if there is a way in which I can re-initialize this! Link to comment Share on other sites More sharing options...
MrStaticVoid Posted February 20, 2004 Share Posted February 20, 2004 Webgraph, you need to get a sound pack. I suggest the eaw patchset. I just emerged timidity++ and the eawpatches...and OMG...it sounds so good. Nearly real. The switch Danrarbc641 posted works really nice for outputting to a wav. Link to comment Share on other sites More sharing options...
MulletRobZ Posted February 20, 2004 Author Share Posted February 20, 2004 -Ow1S outputs to 16 bit stereo wav, the sample rate is determined by the other settings you use.timidity -h will help you out, it's all in there ;) Static Void: Check your private messages. Danrarbc641: And would I use timidity -Ow1s (filename.mid)? If so, then where would the output file be generated to? Link to comment Share on other sites More sharing options...
MrStaticVoid Posted February 20, 2004 Share Posted February 20, 2004 The file would be outputted to filename.wav. If you are burning it to a CD, which you probably are, then you must output it in 44100Hz like: timidity input.mid -Ow1S -s 44100 -o output.wav By the way, my /usr/share/timidity/timidity.cfg file looks like: #on my debian: /usr/local/share/timidity/timidity.cfgdir /usr/share/timidity/eawpatches source gravis.cfg source gsdrums.cfg source gssfx.cfg source xgmap2.cfg #dir /home/user/patches/ #mid -> wav: timidity input.mid -Ow1S -s 44100 -o output.wav when the eaw patchset was added by Portage. Link to comment Share on other sites More sharing options...
aldo Posted February 21, 2004 Share Posted February 21, 2004 Webgraph: (no smartassness intended here): why don't you write a newbie guide to converting files if you find out in the end? Then you can get it shipped in the next version and help out the opensource community :). Link to comment Share on other sites More sharing options...
MulletRobZ Posted February 21, 2004 Author Share Posted February 21, 2004 The file would be outputted to filename.wav. If you are burning it to a CD, which you probably are, then you must output it in 44100Hz like:timidity input.mid -Ow1S -s 44100 -o output.wav By the way, my /usr/share/timidity/timidity.cfg file looks like: when the eaw patchset was added by Portage. Tried that in command line and I get an error saying "cannot open display" or something like that. Good lord! I think KDE included the wrong kind of TiMidity if you ask me. Says version 0.2i might I add. Link to comment Share on other sites More sharing options...
MrStaticVoid Posted February 21, 2004 Share Posted February 21, 2004 The reason that you are getting that error is because it is trying to open up the GUI by defalut. Try using a command line switch like -iT to force it into the console. When you use the -Ow option, you won't here anything coming out of the speakers, just a wav will be created where you specified with the -o option. Below is a list of available interfaces. We've already determined that you don't have the ncurses one (imo the best one). Try different ones. If nothing else works, update Timidity. If you can't find it anywhere, I've already compiled a Pentium III binary for you. Just let me know and I'll tell you how to get it. Available interfaces (-i option): -in ncurses interface -iT vt100 interface -is slang interface -im motif interface -ie Emacs interface (invoked from `M-x timidity') -ia XAW interface -ii skin interface -ig gtk+ interface -id dumb interface -ir remote interface -iA ALSA sequencer interface Link to comment Share on other sites More sharing options...
MulletRobZ Posted February 22, 2004 Author Share Posted February 22, 2004 All right. I reinstalled TiMidity++ with the following configure options: --enable-audio=alsa,arts,vorbis --enable-interface=vt100,ncurses,xaw,gtk --enable-network --enable-wrd However, I still can't get the conversion to work since it did not generate a timidity.cfg file by default and when I copied the config and the eawpatch files to the proper directory, it still says the config is still screwed up. So it's still the same file as I sent ya on MSN a day ago. Would you happen to know how to modify the configure file so the damn thing works, please? After that, it should be a go! Link to comment Share on other sites More sharing options...
MrStaticVoid Posted February 22, 2004 Share Posted February 22, 2004 What do you mean "it still says config is still screwed up?" On my installation, I have in /usr/share/timidity: The timidity.cfg file Some file called timidity.el (I don't know what it does.) A dir called eawpatches with the patches inside. The timidity.cfg contains what I posted above and what you have in yours. Since you installed it from source, though, all of the newly compiled timidity stuff is probably in /usr/local/share/timidity and that is confusing the program. Especially since you probably have the older version still installed. Try removing the old stuff. If that doesn't work, remove the new stuff and recompile the new stuff with the configure flag "--prefix=/usr" so that your old stuff would be rewritten. Man this whole thing is turning out to be way more compilcated than it has to be. Something tells me that everything worked fine before you compiled the new version, it's just that you didn't know it was working. I really wish you could post *exact* console outputs to support your problems. Link to comment Share on other sites More sharing options...
MulletRobZ Posted February 25, 2004 Author Share Posted February 25, 2004 OK. I reinstalled the program with the same prefixes, except that it installed to /usr and not /usr/local. However, the directory /usr/share/timidity was not created. Now what might you suggest on this? Link to comment Share on other sites More sharing options...
Recommended Posts