did something in the disk field change?

[shoskey]

i have been ripping with the "padded" data fields ex. 01/01 for disk one of one. now the leading (padded) 0 does not appear (1/1) I have checked and unchecked the boxes and nothing changes...

shawn

[mville]

Re: did something in the disk field change?

i have been ripping with the "padded" data fields ex. 01/01 for disk one of one. now the leading (padded) 0 does not appear (1/1) I have checked and unchecked the boxes and nothing changes...

Are you using any DSPs, when ripping?

[shoskey]

Re: did something in the disk field change?

no

[mville]

Re: did something in the disk field change?

What platform/OS and dBpoweramp Music Converter version are you using?

... FYI, my PC is running Windows 10 Pro 64-bit and dBpoweramp R16.3 Beta 4 [64-bit].

I have just ripped a CD with both the Pad track number to 2 digits (ie 02) and Pad disc number to 2 digits (ie 01) options ticked.

The Disc and Track tags both contain padded values e.g. Disc = 01/01, Track = 01/09.

What is odd though, is my Naming string contains [disc].[track] at start of the filename and I get 1.01 in the filename.

[shoskey]

Re: did something in the disk field change?

What platform/OS and dBpoweramp Music Converter version are you using?

... FYI, my PC is running Windows 10 Pro 64-bit and dBpoweramp R16.3 Beta 4 [64-bit].

I have just ripped a CD with both the Pad track number to 2 digits (ie 02) and Pad disc number to 2 digits (ie 01) options ticked.

The Disc and Track tags both contain padded values e.g. Disc = 01/01, Track = 01/09.

What is odd though, is my Naming string contains [disc].[track] at start of the filename and I get 1.01 in the filename.

That is the same with mine the filename is 101 windows 10 64 bit also.

[Spoon]

Re: did something in the disk field change?

To pad disc number:

[SETLEN]2,48,,[disc][]

The value [disc] is independent to the option to pad it in the tags.