IPB

Welcome Guest ( Log In | Register )

103 Pages V  « < 100 101 102 103 >  
Reply to this topicStart new topic
CUETools versions 1.9.5 through 2.1.5 (current), AccurateRip support & more
Pidgeon
post Aug 13 2014, 14:09
Post #2526





Group: Members
Posts: 29
Joined: 27-April 10
Member No.: 80211



I've a question about the "Gaps Appended + HTOA" setting in CUETools gaps handling window. Would it be ok to always leave that setting on for every CD, or should I switch to "Gaps Appended" only, instead?
Go to the top of the page
+Quote Post
rankxerox
post Aug 13 2014, 22:55
Post #2527





Group: Members
Posts: 3
Joined: 12-August 14
Member No.: 116949



Wiki says so:

Gaps handling

Used when encoding in Tracks mode.

Gaps Appended + HTOA {radio button}
Recommended setting. Gaps appended to (added to end of) the previous track. Any HTOA (Hidden Track One Audio) located in the INDEX 00 (pregap) area of Track 01 will be preserved as an audio file with the track number 00 and title (HTOA).
Gaps Appended {radio button}
Gaps appended to (added to end of) the previous track. HTOA is discarded and replaced with a PREGAP (silence) command in the CUE file.
Gaps Prepended {radio button}
Gaps are prepended to (added to beginning of) the next track.
Gaps Left Out {radio button}
Gaps are left out (discarded and each replaced with a PREGAP (silence) command in the CUE file).
Go to the top of the page
+Quote Post
Pidgeon
post Aug 14 2014, 14:12
Post #2528





Group: Members
Posts: 29
Joined: 27-April 10
Member No.: 80211



QUOTE (rankxerox @ Aug 13 2014, 22:55) *
Wiki says so:

Gaps handling

Used when encoding in Tracks mode.

Gaps Appended + HTOA {radio button}
Recommended setting. Gaps appended to (added to end of) the previous track. Any HTOA (Hidden Track One Audio) located in the INDEX 00 (pregap) area of Track 01 will be preserved as an audio file with the track number 00 and title (HTOA).
Gaps Appended {radio button}
Gaps appended to (added to end of) the previous track. HTOA is discarded and replaced with a PREGAP (silence) command in the CUE file.
Gaps Prepended {radio button}
Gaps are prepended to (added to beginning of) the next track.
Gaps Left Out {radio button}
Gaps are left out (discarded and each replaced with a PREGAP (silence) command in the CUE file).


You are perfectly right. I thought that I should select for each cue file:
- Gaps Appended + HTOA: when there is a hidden track.
- Gaps Appended: when there isn't a hidden track.

I thought that if I selected the first option even if there is not a hidden track, then the effect would have been the same that selecting the second option. I wanted to ask confirmation of that. So I don't have to check the cue file every time looking for a hidden track.

Anyway, I would like to report a bug. Sometimes, when I select a folder with only flac tracks (no cue file or log) and I start the verification process, CUETools checks each of them correctly, and it produces the AccurateRip report.

On the other hand, with some albums, if I still select the folder containing only the flac tracks, CUETools only checks few of them randomly. Here is a CUETools report in this case:

CODE
.\01. [Gerald Fried] Prelude.flac: AR: disk not present in database, CTDB: disk not present in database.
.\13. [Gerald Fried] Main Title.flac: AR: disk not present in database, CTDB: disk not present in database.


But, if I create a m3u file and I select it with CUETools and start the verification, everything works:

CODE
[CUETools log; Date: 14/08/2014 15:46:17; Version: 2.1.5]
[CTDB TOCID: y7hPOlW.WEUd1D_Hi6zCGNGH7w4-] found.
Track | CTDB Status
  1   | (1/1) Accurately ripped
  2   | (1/1) Accurately ripped
  3   | (1/1) Accurately ripped
  4   | (1/1) Accurately ripped
  5   | (1/1) Accurately ripped
  6   | (1/1) Accurately ripped
  7   | (1/1) Accurately ripped
  8   | (1/1) Accurately ripped
  9   | (1/1) Accurately ripped
10   | (1/1) Accurately ripped
11   | (1/1) Accurately ripped
12   | (1/1) Accurately ripped
13   | (1/1) Accurately ripped
14   | (1/1) Accurately ripped
15   | (1/1) Accurately ripped
16   | (1/1) Accurately ripped
17   | (1/1) Accurately ripped
18   | (1/1) Accurately ripped
19   | (1/1) Accurately ripped
20   | (1/1) Accurately ripped
21   | (1/1) Accurately ripped
22   | (1/1) Accurately ripped
23   | (1/1) Accurately ripped
24   | (1/1) Accurately ripped
[AccurateRip ID: 00437922-047d3144-6110fc18] found.
Track   [  CRC   |   V2   ] Status
01     [dcaeb7af|2af75dc7] (0+0/1) No match
02     [0ef1368c|cd065368] (0+0/1) No match
03     [d13f7329|425e7e65] (0+0/1) No match
04     [484c9672|d9075fec] (0+0/1) No match
05     [a7972793|319bd802] (0+0/1) No match
06     [14f2e1ca|aa275d59] (0+0/1) No match
07     [4a49051b|bcfc00a7] (0+0/1) No match
08     [7a92986c|7def9945] (0+0/1) No match
09     [f4171e81|27a2be04] (0+0/1) No match
10     [6263b810|f1890282] (0+0/1) No match
11     [91c3c922|3664ad83] (0+0/1) No match
12     [71dbf64b|cbd29285] (0+0/1) No match
13     [914e0ff4|43833b27] (0+0/1) No match
14     [756bb849|89e7b250] (0+0/1) No match
15     [2642bfed|684891fc] (0+0/1) No match
16     [3f2cef29|b7662427] (0+0/1) No match
17     [948032cc|a87047ee] (0+0/1) No match
18     [ce633150|0428ecc7] (0+0/1) No match
19     [363082ab|156b7ea4] (0+0/1) No match
20     [5bed5692|d8096990] (0+0/1) No match
21     [f1a43c69|c4bc6af9] (0+0/1) No match
22     [00e20fd1|2172a6b5] (0+0/1) No match
23     [65945161|604be3f2] (0+0/1) No match
24     [f2cc5562|e690720d] (0+0/1) No match
Offsetted by -453:
01     [772c32a3] (0/1) No match (V2 was not tested)
02     [1994b52d] (0/1) No match (V2 was not tested)
03     [e38dc188] (0/1) No match (V2 was not tested)
04     [4d97608a] (0/1) No match (V2 was not tested)
05     [b314c0bf] (0/1) No match (V2 was not tested)
06     [6d3938c6] (0/1) No match (V2 was not tested)
07     [c4b41935] (0/1) No match (V2 was not tested)
08     [4fb59586] (0/1) No match (V2 was not tested)
09     [f3fa10a3] (0/1) No match (V2 was not tested)
10     [bb3638e6] (0/1) No match (V2 was not tested)
11     [c02195d7] (0/1) No match (V2 was not tested)
12     [97c58e6b] (0/1) No match (V2 was not tested)
13     [c76a22ee] (0/1) No match (V2 was not tested)
14     [a589a21d] (0/1) No match (V2 was not tested)
15     [34fad3ef] (0/1) No match (V2 was not tested)
16     [693dfe6b] (0/1) No match (V2 was not tested)
17     [e2f38bf0] (0/1) No match (V2 was not tested)
18     [5e097194] (0/1) No match (V2 was not tested)
19     [655d3f9b] (0/1) No match (V2 was not tested)
20     [af75300d] (0/1) No match (V2 was not tested)
21     [38970804] (0/1) No match (V2 was not tested)
22     [1491d810] (0/1) No match (V2 was not tested)
23     [254c254c] (0/1) No match (V2 was not tested)
24     [bc0b2200] (0/1) No match (V2 was not tested)

Track Peak [ CRC32  ] [W/O NULL]
--  100,0 [FFDB895D] [A6AD92A1]          
01   94,6 [8A534AA1] [0760DF2C]          
02   67,8 [40CA3A1A] [84489CD5]          
03   84,1 [E88B2DA8] [E38E7D78]          
04   94,6 [8908DAAC] [C51BB221]          
05   94,9 [72CBF60F] [F03DCA74]          
06   95,4 [01C68573] [3579D1FB]          
07   62,0 [55EE4CC4] [115F2AC2]          
08   94,6 [CA605B00] [BE2E3D9F]          
09   68,1 [42CDB836] [C6DAAF75]          
10   79,2 [5886FAE7] [F1B3CB4D]          
11   84,3 [0A77DEF4] [84FC31F0]          
12   84,3 [57173E55] [47AEB22E]          
13   94,6 [90698436] [4EFEF1C3]          
14   94,6 [9CB7FD0F] [9D3E8095]          
15   94,6 [8EA122FD] [5203BD08]          
16   94,6 [E9C9491B] [6EC7D08D]          
17   94,6 [F3E8DA13] [368E97FB]          
18   93,1 [19D72492] [12844A4F]          
19   59,1 [A4756A91] [A5863815]          
20   94,6 [65A23E61] [43D5A898]          
21   69,3 [D0332306] [039C8F82]          
22  100,0 [1B0CB01C] [2115933B]          
23   61,3 [69BB7539] [08994292]          
24   61,3 [983C36AA] [CE11818E]


If there is a solution for this, so that it would be sufficient to select the folder containing the tracks for a simple verification, it would be greatly appreciated.

This post has been edited by Pidgeon: Aug 14 2014, 14:50
Go to the top of the page
+Quote Post
ChronoSphere
post Aug 14 2014, 15:14
Post #2529





Group: Members
Posts: 491
Joined: 11-March 07
Member No.: 41384



That usually happens when the album tag is not the same for all files in the folder. Check for trailing/double spaces etc.
Go to the top of the page
+Quote Post
Pidgeon
post Aug 14 2014, 22:26
Post #2530





Group: Members
Posts: 29
Joined: 27-April 10
Member No.: 80211



QUOTE (ChronoSphere @ Aug 14 2014, 15:14) *
That usually happens when the album tag is not the same for all files in the folder. Check for trailing/double spaces etc.


Like you said, in my case I wrongly tagged some albums, which had to be:

CODE
CD 1:

01 - batman - title 1
02 - batman - title 2
03 - batman returns - title 1
04 - batman returns - title 2


But it erroneously was:

CODE
CD 1:

01 - batman - title 1
02 - batman - title 2
01 - batman returns - title 1
02 - batman returns - title 2


So it was like the single CD were 2 CDs, instead. Correctly tagging the traks solved the problem.

I'm still curious to know if a default choice of appended gaps + htoa for each album would work, though. Has someone been doing that?

This post has been edited by Pidgeon: Aug 14 2014, 22:30
Go to the top of the page
+Quote Post
korth
post Aug 14 2014, 22:46
Post #2531





Group: Members
Posts: 436
Joined: 13-March 11
Member No.: 88969



QUOTE (Pidgeon @ Aug 14 2014, 13:12) *
I thought that if I selected the first option even if there is not a hidden track, then the effect would have been the same that selecting the second option. I wanted to ask confirmation of that. So I don't have to check the cue file every time looking for a hidden track.

With the first option, if there is any gap located in the INDEX 00 (pregap) area of Track 01 it will be preserved as an audio file with the track number 00 and title (HTOA). Even if it is just 32 frames of silence. So HTOA is NEVER discarded and replaced with a PREGAP (silence) command in the CUE file.
An actual hidden track is longer than a few seconds. I still wish there was a way to only save as an audio file if the duration was longer than a few seconds.

This post has been edited by korth: Aug 14 2014, 23:03


--------------------
korth
Go to the top of the page
+Quote Post
Pidgeon
post Aug 15 2014, 02:41
Post #2532





Group: Members
Posts: 29
Joined: 27-April 10
Member No.: 80211



QUOTE (korth @ Aug 14 2014, 22:46) *
QUOTE (Pidgeon @ Aug 14 2014, 13:12) *
I thought that if I selected the first option even if there is not a hidden track, then the effect would have been the same that selecting the second option. I wanted to ask confirmation of that. So I don't have to check the cue file every time looking for a hidden track.

With the first option, if there is any gap located in the INDEX 00 (pregap) area of Track 01 it will be preserved as an audio file with the track number 00 and title (HTOA). Even if it is just 32 frames of silence. So HTOA is NEVER discarded and replaced with a PREGAP (silence) command in the CUE file.
An actual hidden track is longer than a few seconds. I still wish there was a way to only save as an audio file if the duration was longer than a few seconds.


Finally I've understood the point, thank you. Well, your suggestion about the hidden track duration detection is valuable, tough.

This post has been edited by Pidgeon: Aug 15 2014, 02:42
Go to the top of the page
+Quote Post
Pidgeon
post Aug 16 2014, 04:45
Post #2533





Group: Members
Posts: 29
Joined: 27-April 10
Member No.: 80211



I've another question regarding CUETools verification. Do you think that my rip is problematic on track 13, even if test & copy crc are the same?:

CODE
[CUETools log; Date: 16/08/2014 05:38:02; Version: 2.1.5]
Offset applied: 667
[CTDB TOCID: zlIUqg46NkG9s4NNAGoXo6O8R8c-] found.
Track | CTDB Status
  1   | (10/11) Accurately ripped
  2   | (10/11) Accurately ripped
  3   | (11/11) Accurately ripped
  4   | (10/11) Accurately ripped
  5   | (11/11) Accurately ripped
  6   | (11/11) Accurately ripped
  7   | (11/11) Accurately ripped
  8   | (11/11) Accurately ripped
  9   | (11/11) Accurately ripped
10   | (11/11) Accurately ripped
11   | (11/11) Accurately ripped
12   | (11/11) Accurately ripped
13   | ( 7/11) Differs in 2 samples @01:11:61
14   | (11/11) Accurately ripped
15   | (10/11) Accurately ripped
16   | (11/11) Accurately ripped
[AccurateRip ID: 00251c2a-01c118ff-db0fe810] found.
Track   [  CRC   |   V2   ] Status
01     [a7c299f8|e127ce0b] (19+06/59) Accurately ripped
02     [079a6a1e|bb2b5ba6] (18+07/60) Accurately ripped
03     [0b3026a2|1ba03a20] (19+07/61) Accurately ripped
04     [444829c9|dd3feb7f] (19+07/61) Accurately ripped
05     [45b191e3|cb11bf06] (19+07/61) Accurately ripped
06     [864d663b|c7dd9192] (19+07/61) Accurately ripped
07     [92ac9917|dc1f8ec3] (19+07/61) Accurately ripped
08     [12e37362|059bff53] (19+07/61) Accurately ripped
09     [0a6c7387|b0cb2267] (19+07/61) Accurately ripped
10     [51aadb93|a1c45796] (19+07/60) Accurately ripped
11     [cbba35e7|962ec6d0] (19+07/61) Accurately ripped
12     [73748212|924344f3] (18+07/60) Accurately ripped
13     [92dabf2a|1f97fe6d] (00+00/61) No match
14     [f1f14090|9d402e83] (19+07/60) Accurately ripped
15     [55509095|584e2df1] (19+07/58) Accurately ripped
16     [c2384c52|ed4f6c4a] (19+07/58) Accurately ripped
Offsetted by 845:
01     [83cafc62] (11/59) Accurately ripped
02     [a292acbb] (11/60) Accurately ripped
03     [3f5a9bc0] (11/61) Accurately ripped
04     [eac83fb6] (11/61) Accurately ripped
05     [51925946] (11/61) Accurately ripped
06     [5dfbdf9b] (11/61) Accurately ripped
07     [8ff9fb72] (11/61) Accurately ripped
08     [4b1ee8c6] (11/61) Accurately ripped
09     [00673080] (11/61) Accurately ripped
10     [e0a125cb] (11/60) Accurately ripped
11     [9dfa7beb] (11/61) Accurately ripped
12     [21bccf5d] (11/60) Accurately ripped
13     [34aeff8b] (00/61) No match (V2 was not tested)
14     [a9afa9a4] (11/60) Accurately ripped
15     [a811c131] (11/58) Accurately ripped
16     [53d6dc03] (10/58) Accurately ripped
Offsetted by 885:
01     [716d7732] (00/59) No match (V2 was not tested)
02     [1a00e363] (05/60) Accurately ripped
03     [cbab6330] (05/61) Accurately ripped
04     [e2004cde] (05/61) Accurately ripped
05     [62cbf29e] (05/61) Accurately ripped
06     [4e71329b] (05/61) Accurately ripped
07     [28d7c68a] (05/61) Accurately ripped
08     [efdd8ee6] (05/61) Accurately ripped
09     [68730f08] (05/61) Accurately ripped
10     [3f41418b] (04/60) Accurately ripped
11     [746d9f0b] (05/61) Accurately ripped
12     [2d0465f5] (05/60) Accurately ripped
13     [5310e753] (00/61) No match (V2 was not tested)
14     [dfd3f144] (05/60) Accurately ripped
15     [38dccb11] (04/58) Accurately ripped
16     [77837a4b] (05/58) Accurately ripped
Offsetted by 947:
01     [2e8fb58e] (12/59) Accurately ripped
02     [86521e81] (12/60) Accurately ripped
03     [985bcb84] (12/61) Accurately ripped
04     [1463fadc] (12/61) Accurately ripped
05     [3d7ed380] (12/61) Accurately ripped
06     [c3270cdb] (12/61) Accurately ripped
07     [55c927bc] (12/61) Accurately ripped
08     [159ea9fe] (12/61) Accurately ripped
09     [e352418e] (12/61) Accurately ripped
10     [eb86395b] (12/60) Accurately ripped
11     [b4067be3] (12/61) Accurately ripped
12     [8b4cf5c7] (12/60) Accurately ripped
13     [dbc241c9] (00/61) No match (V2 was not tested)
14     [e6f2937c] (12/60) Accurately ripped
15     [594ab3f9] (12/58) Accurately ripped
16     [d5356fa1] (12/58) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL] [  LOG   ]
--   94,4 [623D4CCE] [1FD3F42B]          
01   87,4 [5C9B8222] [5EACB604]  W/O NULL
02   82,8 [90DAB5A3] [99A90332]  W/O NULL
03   64,8 [D34AD169] [93810CB1]  W/O NULL
04   84,5 [FF171F84] [ED51E319]  W/O NULL
05   74,0 [F3598071] [5FFD576E]  W/O NULL
06   94,4 [CF5611F1] [95645CB4]  W/O NULL
07   75,6 [A1F68180] [13FB1808]  W/O NULL
08   72,5 [C2F9F3C3] [4C65F902]  W/O NULL
09   79,1 [69227F75] [2A105CDB]  W/O NULL
10   80,9 [7751527E] [01406D82]  W/O NULL
11   55,7 [AC17973B] [806A90FA]  W/O NULL
12   74,6 [B3DA3DFF] [05937ADC]  W/O NULL
13   74,0 [7AAE00EA] [264AA6DB]  W/O NULL
14   85,7 [F3BBE844] [030CF5A4]  W/O NULL
15   67,5 [B854CE02] [95831CEC]  W/O NULL
16   87,1 [5CCC8CC8] [C6773305]  W/O NULL


This post has been edited by Pidgeon: Aug 16 2014, 04:46
Go to the top of the page
+Quote Post
BrassDude
post Aug 16 2014, 08:46
Post #2534





Group: Members
Posts: 44
Joined: 1-February 11
Member No.: 87835



I recently updated to CUETools 2.1.5 since it is now the latest stable version. When I do a verification of a FLAC file I'm writing out a file with the format:

%music%\%albumartist%\%album% - %date% - %sourceformat%\%albumartist% - %album% - %date% - %sourceformat%$ifgreater(%totaldiscs%,1,[ - %discnumber%],).riplog

Under version 2.1.4 the %date% field gets properly taken from the FLAC file but in version 2.1.5 just the string %date% is written out. The other fields seem to work normally.

Did this change in 2.1.5 or is this a bug? If not, what is the correct way to get the %date% (actually I just have the year in that field) in version 2.1.5?
Go to the top of the page
+Quote Post
korth
post Aug 16 2014, 14:14
Post #2535





Group: Members
Posts: 436
Joined: 13-March 11
Member No.: 88969



Try %year% - http://www.cuetools.net/wiki/Cuetools_templates


--------------------
korth
Go to the top of the page
+Quote Post
ChronoSphere
post Aug 16 2014, 15:17
Post #2536





Group: Members
Posts: 491
Joined: 11-March 07
Member No.: 41384



QUOTE (Pidgeon @ Aug 16 2014, 05:45) *
I've another question regarding CUETools verification. Do you think that my rip is problematic on track 13, even if test & copy crc are the same?:

CODE
[CUETools log; Date: 16/08/2014 05:38:02; Version: 2.1.5]
Offset applied: 667
[CTDB TOCID: zlIUqg46NkG9s4NNAGoXo6O8R8c-] found.
Track | CTDB Status
  1   | (10/11) Accurately ripped
  2   | (10/11) Accurately ripped
  3   | (11/11) Accurately ripped
  4   | (10/11) Accurately ripped
  5   | (11/11) Accurately ripped
  6   | (11/11) Accurately ripped
  7   | (11/11) Accurately ripped
  8   | (11/11) Accurately ripped
  9   | (11/11) Accurately ripped
10   | (11/11) Accurately ripped
11   | (11/11) Accurately ripped
12   | (11/11) Accurately ripped
13   | ( 7/11) Differs in 2 samples @01:11:61
14   | (11/11) Accurately ripped
15   | (10/11) Accurately ripped
16   | (11/11) Accurately ripped
...

What I'm getting from this is that if you repair your rip with cuetools, you will get confidence 7/11 on that track. Currently it's seeing your rip as not accurate.
Go to the top of the page
+Quote Post
BrassDude
post Aug 17 2014, 18:03
Post #2537





Group: Members
Posts: 44
Joined: 1-February 11
Member No.: 87835



QUOTE (korth @ Aug 16 2014, 08:14) *


Thanks korth - that worked! smile.gif
Go to the top of the page
+Quote Post
tuxman
post Aug 18 2014, 02:41
Post #2538





Group: Members
Posts: 188
Joined: 24-April 07
From: Northern Germany
Member No.: 42855



Hi,

I just noticed CUEtools have moved to Mercurial. Damn. ;-)

So I just wanted to update German translations but it says I have no permission anymore?

Anyway...
Here's the update. Hope I haven't missed a thing.

https://www.dropbox.com/s/d659cdsct8uv6do/548.patch

Regards.


--------------------
audiophile // FLAC and Vorbis user // Winamp addict
Go to the top of the page
+Quote Post
audiophool
post Aug 18 2014, 16:58
Post #2539





Group: Members
Posts: 33
Joined: 13-June 14
Member No.: 116389



Will the EAC plugin see an update to 2.1.5 as well?
Go to the top of the page
+Quote Post
Gregory S. Chudo...
post Aug 18 2014, 17:18
Post #2540





Group: Developer
Posts: 699
Joined: 2-October 08
From: Ottawa
Member No.: 59035



QUOTE (tuxman @ Aug 17 2014, 21:41) *
Hi,
I just noticed CUEtools have moved to Mercurial. Damn. ;-)

So I just wanted to update German translations but it says I have no permission anymore?

Oops. Apparently sourceforge reset user permissions when upgrading the project to a new platform. This is not fixed, and i will apply your patch when i get a minute. Thank you!

UPD: i meant to say this is *now* fixed wink.gif

This post has been edited by Gregory S. Chudov: Aug 18 2014, 18:07


--------------------
CUETools 2.1.4
Go to the top of the page
+Quote Post
Gregory S. Chudo...
post Aug 18 2014, 17:20
Post #2541





Group: Developer
Posts: 699
Joined: 2-October 08
From: Ottawa
Member No.: 59035



QUOTE (audiophool @ Aug 18 2014, 11:58) *
Will the EAC plugin see an update to 2.1.5 as well?

There weren't any significant changes to the EAC plugin since 2.1.4; Unfortunately, EAC itself hasn't been updated for a long time and it still comes with an even older version bundled.


--------------------
CUETools 2.1.4
Go to the top of the page
+Quote Post
tuxman
post Aug 18 2014, 17:36
Post #2542





Group: Members
Posts: 188
Joined: 24-April 07
From: Northern Germany
Member No.: 42855



QUOTE (Gregory S. Chudov @ Aug 18 2014, 18:18) *
Apparently sourceforge reset user permissions when upgrading the project to a new platform. This is not fixed, and i will apply your patch when i get a minute. Thank you!


Thank you too. I'll keep an eye on it!


--------------------
audiophile // FLAC and Vorbis user // Winamp addict
Go to the top of the page
+Quote Post
audiophool
post Aug 18 2014, 17:56
Post #2543





Group: Members
Posts: 33
Joined: 13-June 14
Member No.: 116389



QUOTE (Gregory S. Chudov @ Aug 18 2014, 18:20) *
There weren't any significant changes to the EAC plugin since 2.1.4

Thanks for confirming that! (It wasn't quite clear to me from looking at the changelog.)
Go to the top of the page
+Quote Post
NetRanger
post Aug 23 2014, 15:30
Post #2544





Group: Members
Posts: 58
Joined: 2-November 03
Member No.: 9605



Any changes to the changelog now when v2.1.5 is the current stable version?
Go to the top of the page
+Quote Post
korth
post Aug 23 2014, 19:02
Post #2545





Group: Members
Posts: 436
Joined: 13-March 11
Member No.: 88969



No changes that I can think of that made it stable.
The only significant change that isn't listed in the changelog was the removal of references to the CSScriptLibrary.v1.1.dll which removes the ability for the user to add custom scripts.
There were some minor fixes which can be listed as "Various bug fixes".
I'll make adjustments to the wiki. I've already removed other references to the Scripts tab from the wiki.


--------------------
korth
Go to the top of the page
+Quote Post
NetRanger
post Aug 23 2014, 19:12
Post #2546





Group: Members
Posts: 58
Joined: 2-November 03
Member No.: 9605



Thnx for the reply/info korth. smile.gif
Go to the top of the page
+Quote Post
mjb2006
post Sep 1 2014, 14:12
Post #2547





Group: Members
Posts: 811
Joined: 12-May 06
From: Colorado, USA
Member No.: 30694



For metadata lookups, how does CUERipper find a given CD in Discogs? Does it require that the disc have an entry and relationships data in MusicBrainz, or what?

Is CUERipper affected by the recent Discogs API changes? In Mp3tag, to do a Discogs lookup, you now have to have a Discogs account which you authorize access to; Discogs gives you an OAuth token that copy-paste back into Mp3tag. I also saw something about them ditching XML and switching to JSON. It may just be buggy at the moment, though: http://forums.mp3tag.de/index.php?showtopi...amp;#entry79121

This post has been edited by mjb2006: Sep 1 2014, 14:32
Go to the top of the page
+Quote Post
korth
post Sep 1 2014, 15:48
Post #2548





Group: Members
Posts: 436
Joined: 13-March 11
Member No.: 88969



Unless things have changed, CUERipper gets the metadata from the CTDB. CTDB replicates and stores the data from Discogs. Discogs searches can be done using a fuzzy search algorithm or associations via a Musicbrainz discid search. The metadata search setting in CUERipper will determine which searches are used.

I'll leave the rest for Grigory (and any corrections to the above as needed).

Edit: spelling correction

This post has been edited by korth: Sep 1 2014, 16:06


--------------------
korth
Go to the top of the page
+Quote Post
gojirasan
post Sep 8 2014, 20:55
Post #2549





Group: Members
Posts: 2
Joined: 8-September 14
Member No.: 117203



I am writing a script to convert audio books to wavs/mp3s quickly and without using the analog hole and the console version of cueripper seems perfect for the tool chain (and it is also the only console ripper that runs in windows natively) except that there is no documentation at all for using the console version. So I will ask my questions here. I do plan to post my tool here when I am finished btw.

Questions:

1) CTDB searching. Is there a way to stop cuetools.consoleripper.exe from searching databases like CTDB, Brainz, and Accuraterip for data? For audio books this is not helpful and it seems to match up with music CDs and then I end up with filenames based on some random music CD. I noticed that when I run the cueripper.exe or cuetools.exe it makes a folder for itself and writes a settings.txt file in that folder. Settings.txt for cuetools.exe is the most complete and has some interesting sounding settings. I have tried messing with both files and copying settings from the cuetools settings.txt file to the cueripper one just in case cuetools.consoleripper.exe actually just calls cueripper.exe or something like that.

FWIW here are some of the settings from the cuetools settings.txt that seem like they could be useful to me:

CUEToolsDBLookup=0
MusicBrainzLookup=0
AccurateRipLookup=0
LocalDBLookup=0
KeepOriginalFilenames=1
AccurateRipMode=0
DontGenerate=1
AutoCorrectFilenames=0

Advanced=<CUEConfigAdvanced>
=<CTDBSubmit>false</CTDBSubmit>
= <CTDBAsk>false</CTDBAsk>
= <metadataSearch>None</metadataSearch>
=</CUEConfigAdvanced>

I don't think cuetools.consoleripper.exe is reading either of those settings.txt files. It does not seem to matter what changes I make to them. Is this in fact the case? Is cuetools.consoleripper.exe intended to read a settings.txt file as well? If so where should I put it? Can I just copy a settings.txt file from the cuetools or cueripper folder to somewhere where cuetools.consoleripper.exe will look for it?

2) Rips to a single wav (cdimage.wav). The program that I just wrote takes multiple files named "Track<nn>.wav" as inputs and there are good reasons for that. I suppose I could try to split the wav up again using the cue file, but since this is supposed to be an automated script that presents all sorts of difficulties. acdir, sox, and shntool are all windows command line tools that can resplit the file or I could even write my own, but it would be a lot better if that were not necessary.

3) Save-To Folder. Is there a way to tell cuetools.consoleripper.exe where to rip the files? Currently it just puts cdimage.exe and a cdimage.cue in the cuetools folder itself. This is not that big of a deal except that I would like others to be able to use my script and they probably don't have a "P:" drive letter or put their programs in the same place I do. I suppose I could put cuetools.consoleripper.exe at "c:\" and search for the files there, but that is obviously less than ideal.

If it is not possible to change the default behavior of cuetools.consoleripper.exe then I'd like to look into how difficult it might be to alter the C# source code. Maybe it is as easy as just commenting out the CTDB checks etc. I am not familiar with C# though. So I would have to read some books on it which I eventually wanted to do anyway I guess. I went to the sourceforge page with the source code and I noticed there are a lot of files there. Aside from the obvious "CUETools.Ripper.Console" folder what other folders should I be downloading to examine the source if I want to change the above behavior in cuetools.consoleripper.exe?

I would certainly be grateful if the program author or anyone else can tell me how to do these things or whether they are just hard coded in the console version. In which case I would appreciate any help in finding which .cs files from the project I should be examining. I do plan to use cuetools.consoleripper.exe in my script no matter what even if I have to live with the current default behavior, but it would certainly be nice if I could change it.
Go to the top of the page
+Quote Post
korth
post Sep 9 2014, 00:20
Post #2550





Group: Members
Posts: 436
Joined: 13-March 11
Member No.: 88969



See the second part of this post.

CUETools.ConsoleRipper.exe appears to be dependent on
plugins\CUETools.Ripper.SCSI.dll
CUETools.Ripper.dll
CUETools.Codecs.dll
CUETools.CDImage.dll
CUETools.AccurateRip.dll
CUETools.CTDB.dll
CUETools.ConsoleRipper.exe.config

You are correct, it does not appear to be dependent on any CUERipper settings and writes CDImage only.

Destination of the files depends on where you call CUETools.ConsoleRipper.exe from. For example:
If I start the app from C:\Users\ME in the command prompt
C:\Users\ME>"C:\AudTools\CUETools_2.1.5\CUETools.ConsoleRipper.exe" -S -D D:
the files are written to C:\Users\ME

Have a look at CUETools.Ripper.Console/Program.cs

Edit: CUETools.ConsoleRipper.exe.config just tells it to also look in the plugins folder

This post has been edited by korth: Sep 9 2014, 00:58


--------------------
korth
Go to the top of the page
+Quote Post

103 Pages V  « < 100 101 102 103 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 20th September 2014 - 12:25