Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
Thanks for the response. I'm glad that you will be addressing the overwrite issue in R16. Instead of adding this with a DSP effect, it would be really nice to have a setting instead. This setting, if set, would completely disable overwrite. I'm wondering in the meantime if marking all of the converted files as Read-Only in the filesystem would prevent the overwrite, but still allow the conversion to continue?
Also, any plans to address the "suspend machine when conversion is complete" issue that I also mention above? Thanks. FYI, I am a registered user. Sent my payment a couple of days ago.
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
R16 should fix the suspend issue also.
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
I am really sorry.
I tried this Naming String proposed by Spoon;
[IFVALUE]album artist,[album artist],[IFCOMP]Various Artists[][IF!COMP][artist][IFEQUALS]artist,Unknown Artist, [cddb_id][][][]\[album]\[track] [artist] - [title]
to prevent overwriting when you have several "unknown album".
It doesn't work. It's not creating different folders.
Can somebody help?
Thanks!
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
Do you have unknown album and unknown artist? Provide a specific example of a cd that causes this problem along with the metadata.
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
Yes unknown album + unknown artist, so no metadata at all.
This is what I found, hope it make sense to you.
dBpoweramp Batch Ripper
Batch Name:
Batch ID: 50006
Using Profile: (default)
Batch Rip Started: 30/11/2019 15:14:26
Disc 1: <no meta data>
Track 1 Result: AccurateRip: Not in database Secure: Yes [05604F7A]
Track 2 Result: AccurateRip: Not in database Secure: Yes [332C2F9E]
Track 3 Result: AccurateRip: Not in database Secure: Yes [AB901B16]
Track 4 Result: AccurateRip: Not in database Secure: Yes [74315259]
Track 5 Result: AccurateRip: Not in database Secure: Yes [54E6C746]
Track 6 Result: AccurateRip: Not in database Secure: Yes [C8008608]
Track 7 Result: AccurateRip: Not in database Secure: Yes [368E3BBB]
Track 8 Result: AccurateRip: Not in database Secure: Yes [EC9B29C8]
Track 9 Result: AccurateRip: Not in database Secure: Yes [A5732AA7]
Track 10 Result: AccurateRip: Not in database Secure: Yes [C1FBFCD7]
Track 11 Result: AccurateRip: Not in database Secure: Yes [8872DD07]
Track 12 Result: AccurateRip: Not in database Secure: Yes [18CB79B3]
Combined Result: All (12) Secure
Disc 2: <no meta data>
Track 1 Result: AccurateRip: Not in database Secure: Yes [D3403115]
Track 2 Result: AccurateRip: Not in database Secure: Yes [CAFD5312]
Track 3 Result: AccurateRip: Not in database Secure: Yes [7D347934]
Track 4 Result: AccurateRip: Not in database Secure: Yes [4FA33A15]
Track 5 Result: AccurateRip: Not in database Secure: Yes [64F9D7BE]
Track 6 Result: AccurateRip: Not in database Secure: Yes [BA590983]
Track 7 Result: AccurateRip: Not in database Secure: Yes [6C9CA525]
Track 8 Result: AccurateRip: Not in database Secure: Yes [3F77D178]
Track 9 Result: AccurateRip: Not in database Secure: Yes [66F51A68]
Track 10 Result: AccurateRip: Not in database Secure: Yes [16375C9A]
Track 11 Result: AccurateRip: Not in database Secure: Yes [1A811077]
Track 12 Result: AccurateRip: Not in database Secure: Yes [6DA5F32B]
Track 13 Result: AccurateRip: Not in database Secure: Yes [AA27FB30]
Track 14 Result: AccurateRip: Not in database Secure: Yes [BCFDF44E]
Track 15 Result: AccurateRip: Not in database Secure: Yes [1C2AA58C]
Track 16 Result: AccurateRip: Not in database Secure: Yes [E4DBE9D1]
Combined Result: All (16) Secure
Unable to locate Nimbie, is connected?
Batch Ended: 30/11/2019 15:32:24
Ripped: 2 Discs
Rejected: 0 Discs
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
If both those items are unknown, it is not clear to me how dbpa would know to keep them separate. Looks like you are using a batch ripper. For these unknown CDs, I would do them manually and enter some sort of album and artist name. I use following string, but may not help with everything unknown.
[QUOTE][MAXLENGTH]240,[IFCOMP]Compilations\[album][IFMULTI]\Disc [disc][]\[track] - [title] - [artist][][IF!COMP][IFVALUE]album artist,[album artist],[artist][]\[album][IFMULTI]\Disc [disc][]\[track] - [title][][][/QUOTE]
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
[QUOTE=garym;195033]If both those items are unknown, it is not clear to me how dbpa would know to keep them separate. Looks like you are using a batch ripper. For these unknown CDs, I would do them manually and enter some sort of album and artist name. I use following string, but may not help with everything unknown.[/QUOTE]
Yep. It's a Nimbie Batch ripper.
I'll try your solution and let you know.
Thanks!
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
Hi Garym,
I'm sorry but your formula is not creating separate folders for "unknown albums or artists".
So the second "Unknown" one will overwrite the first one.
I guess this is a typical problem for a batch ripper.
I can't imagine I'm the only one.
Thanks a lot for responding!
Re: Need Naming String to Prevent "Unknown Artist"/No Metadata Rips from Overwriting
If both artist and album are unknown, I cant imagine any automatic solution. At least one of those items needs to have some info entered. You likely have to deal with those one at a time in some manual way. I do not use the batch ripper, but I recall discussion of using a DSP to reject ripping under specified conditions. I assume all unknown could be such a condition.