MUCHO Wrote: > I can't figure out exactly how to use the command prompt. > > Assuming my dts file is named "kiss the frog.dts" and is in my g: drive > in the folder named dts and the spdif file is in the spdif folder in the > prgrams folder exactly what would I have to type in to the command > prompt to get out a wav file? > > If I know this I can then probably figure out how to do the rest. > > Thanks! I'll do my best to help. I'll put commands to type in *bold text*, so please read these instructions through the 'forum' (http://forums.slimdevices.com/showthread.php?p=109889#post109889) rather than through the mailing list. Some of the commands are quite long and we don't want to introduce typos, so you might want to copy and paste into your command prompt. On my Win2000 system, I can click the icon at the top-right of the command prompt window to get a menu, then choose "Edit" and then "Paste" to paste in some copied text.
Open a command prompt (you may already know how to do this, but if not, click "Start", then "Run", then type *cmd* and press RETURN). Type *g:* and press RETURN to change to that drive. Type *cd \dts* then RETURN to change to the 'dts' folder. (All commands at the command prompt should be followed by RETURN, so I'll leave that off of my subsequent instructions.) We need to work out how you'll be able to invoke the conversion utility on your system, so we'll try a couple of things. Is the utility in 'prgrams' on the G drive? Then type *\prgrams\spdif\spdifconvert.py --help* to see if you can invoke the utility that way. If 'prgrams' is on a different drive, say the C drive, type *c:\prgrams\spdif\spdifconvert.py --help* instead. (The drive-letter-plus-colon is optional if the path you're referring to is on the same drive as your current directory.) If you've made a typo in your post, and the utility is within the main Windows 'Program Files' directory, you'll need to include double-quote marks: *"c:\Program Files\spdif\spdifconvert.py" --help* to run it. If one of the above lines spits out a bunch of help text, we've identified the way to run the utility. (The '--help' bit was just there to show us the help text. You won't include that argument when running the utility for real.) If you get a message like "... is not recognized as an internal or external command, operable program or batch file." then the path to the utility is not correct. If you can identify the correct path, you can probably work out how to adjust the above tests to get it working. If you didn't get any help text, and you didn't get an error suggesting that the file couldn't be found, perhaps your system doesn't know how to run Python files. Have you installed Python 2.3? If not, please do so, and be sure to allow the installer to associate .PY files with Python. After that's installed, open a new command prompt and try the above steps again. Still no help text after installing Python? Then we need to step back a little. At your command prompt, type *python -V* (that's a capital 'V'). It should print the current Python version. If it doesn't, the Python executable isn't in your path, and you'll need to refer to it directly. Do you know where Python installed itself? It was probably 'c:\Python23', so try typing *c:\Python23\python -V* -- you should see the Python version. If that worked, now combine the commands we've found to make *PYTHON SPDIFPY --help*, where 'PYTHON' is whatever you typed to get Python to show its version (WITHOUT the '-V'), and 'SPDIFPY' is correct path to the conversion utility (including the 'spdifconvert.py' part). How are you doing so far? You should have been able to type a command which ended with '--help' which showed lots of options for the conversion utility. That command, without the '--help', is the thing to run any time we invoke the conversion utility. I'll refer to it as 'SPDIFCONVERT' below, and you should substitute the real command on your system. The next bit should be easy! You should be in your 'dts' folder (if not, type *g:* and *cd \dts* to get there). If you type *dir* then you ought to see your DTS files listed. Now type *SPDIFCONVERT "kiss the frog.dts"* to begin conversion. You should see messages indicating which files are being read from and written to, and that a stream type of 'dts' was detected. Now you have your converted WAV file. You should convert it to FLAC so that metadata can be applied; if you don't know how to do that already, you could try typing *"c:\Program Files\SlimServer\server\Bin\MSWin32-x86-multi-thread\flac.exe" "kiss the frog.dts.wav"* -- it'll probably work if FLAC is installed where I think it is. You can now file your FLAC files away in your usual music folder structure, and you can delete the WAV files. Keep the DTS files for now, until you've tested the FLAC output (this'll save you re-ripping them in case anything went wrong). Apply metadata (tags) to your FLAC files (I use foobar2000 for that, but there are loads of ways to do it -- beyond the scope of this response however), and perform a new-and-changed rescan with SlimServer. Be sure to check your volume, bitrate-limiting and file conversion settings in SlimServer before playback (see the guide at the start of this thread). And start your receiver at a fairly low volume, so if there's anything wrong it won't hurt your speakers or ears. Please post back here to let us know how you've got on with it. -- smst ------------------------------------------------------------------------ smst's Profile: http://forums.slimdevices.com/member.php?userid=752 View this thread: http://forums.slimdevices.com/showthread.php?t=19260 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
