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: Rip-to-Directory Problem / RubyRipper 0.6.0 on Kubuntu 10.10 (Read 957 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Rip-to-Directory Problem / RubyRipper 0.6.0 on Kubuntu 10.10

I've just installed 0.6.0 on my Kubuntu 10.10 system. I'm using the command-line version, and so far I'm ripping to ogg. But I seem not to understand how the "base directory" and file-naming settings work. I'll try to explain:

1. I have my base directory set to ~/Music.

2. I have my standard naming scheme set to %a (%g) %t (my various artists scheme is similar).

3. When I select "Rip cd now," I get the following message:

[blockquote]The directory ~/Music already exist. What do you want rubyripper to do?[/blockquote]

I can cancel the rip, overwrite the directory, or auto-rename the directory, none of which sounds like what I want. "Overwrite" sounds scary. When I try "auto-rename," RR creates a new directory called "Music#1" off my home directory. I assume it would continue doing that (sermons#2, etc.) on future runs.

4. I use Amarok to organize my music, so I'd just as soon dump all my music files into ~/Music and let Amarok scan and refresh its database. I also prefer to use internal tags for metadata and I don't feel I need a file structure (ex.: /genre/artist/album/) to keep my stuff in order. That's Amarok's job.

So, what am I getting wrong, and how do you think I can solve this issue. I'm holding off ripping because I don't want to make a big mess.

Many thanks!

Todd