Tweet
Re: Metadata diference between normal and batch version
Now I see 39.93
Now I see 39.93
-
-
Re: Metadata diference between normal and batch version
firstly I wish you and your family a blessed Christmas and a pleasant end of year
Just planed to upgrade to the family pack for use on my own computer end the one of my wife. I don't know what to do with the remake "commercial use excluded"Comment
-
Re: Metadata diference between normal and batch version
It means businesses cannot use the family pack, only domestic users.Comment
-
Re: Metadata diference between normal and batch version
What is the alternate ?Comment
-
Re: Metadata diference between normal and batch version
Sorry for being a pain but it is really no more fun to use dBpoweramp.
After a few CDs the program crashes, both the single version and in the batch version
Closing with “Task Manager” in Windows fails to close it also. So each time it happens (and this is allot) I have to restart my computer, I even had to reset my computer two times to a recovery point.
I do not understand, I use dBpoweramp ripping for quite a while, I get the feeling that the problems started since installing the batch version. I don’t know.
I'm desperateComment
-
Re: Metadata diference between normal and batch version
Should I run this:
Comment
-
Re: Metadata diference between normal and batch version
Yes run that, reinstall and try ripping with default settings.Comment
-
Re: Metadata diference between normal and batch version
Okay, will do that, when running the tool should I leave the tird option blank or not ? Why default settings, may I change the genre text file ?
Comment
-
Re: Metadata diference between normal and batch version
No need to clear the programs, just settings.Comment
-
Re: Metadata diference between normal and batch version
Okay, I will try it later today.
-
In batch ripping, is it possible to see the detailed screen like the single riptool does (see attach) (I have seen that the GD3 encode center ripping have this)
-
Could it be that there is a limitation on searching metadata in the batch version and in the single version ?Comment
-
Re: Metadata diference between normal and batch version
In batch ripper you do not get individual file reporting, just general for each disc. You can set to write the log file though.Comment
-
Re: Metadata diference between normal and batch version
Okay I understand, it might sound strange, but what if I simply open the single ripping version twice to work with. I also think of using GD3 for finding the metadata, might be faster.Comment
-
Re: Metadata diference between normal and batch version
I performed the new installation, to the extent that all is well.
Remarkable observation:
I did an institution which I suspect if an error occurs during ripping because of a damaged CD the ripper stops and the cd would be ejected.
This would be handy when rip in batch so I don’t waste time with because of a bad cd.
separately.
So I did the test with a CD that I knew it contains errors, and what turns out, the CD was now finished without error.
Strange, what would be the reason why it did not work before the new install of dbpowerampComment
-
Re: Metadata diference between normal and batch version
Chance? if accuraterip verified then it contains no errors. Unless you submitted the error result.Comment
-
Re: Metadata diference between normal and batch version
Just wanted to know if it is possible to do a setting that if the batch ripper detects an error or problem on a track he ignores the track, instead of doing the ‘frame counting’ thing that takes a lot of time, simply stops immediately and go to the next track
Btw, sorry for my english, part of it is google transletedComment
Comment