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: Another newbie question regarding wavpack (Read 1940 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Another newbie question regarding wavpack

Hello all. I have a simple question, (or at least what I assume is a simple question). I am looking to use the command line through dbpoweramp to convert to wavpack using this compression:

-f -j0 -x0

but I cant seem to find the correct input to preserve all the metadata. Not to mention the original file name is changed to something completely different.

For example, the original file went from this:

Exemia - GUNVEIN (OST) - 01 Press Start -TITLE SCREEN-

..to this:

EX01BD~1

..with no metadata preserved.

How can I stop this from happening and get them to come out normal?
Thank you

Re: Another newbie question regarding wavpack

Reply #2 –
I dont think so? Im doing it on my internal ssd

Re: Another newbie question regarding wavpack

Reply #3 –
Weird. Anything about permissions - or some other application monitoring the folder?
You don't say what you are converting from. WavPack itself cannot convert from anything but uncompressed, and can only import ID3.
There is this --import-id3 --allow-huge-tags, but I thought dBpoweramp's music converter had its own tags transfer. Anyway, ... try https://forum.dbpoweramp.com/forum/dbpoweramp/music-converter ?

Re: Another newbie question regarding wavpack

Reply #4 –
Also, the filename truncation may have led one of the tools involved into not recognising it, so here's one possible reason metadata hasn't got carried over.
• Listen to the music, not the media it's on
• The older, the 'lossier'

Re: Another newbie question regarding wavpack

Reply #5 –
I cant say if it is or not. Im really not that savvy with computers. I know only basic things (maybe even less than basic).
I am converting from uncompressed flac.

Re: Another newbie question regarding wavpack

Reply #6 –
I still suspect write permissions ... Things to try out:

* Make a new target folder with a short name. Try to convert to that.
* And for good measure: Try to copy the source file to a different folder which also has a short name, and rename the source file to say ExemiaTestfile01.flac

Also:
* Try to convert to something else than WavPack. For example FLAC. Yes it is FLAC already, but this is not because you want a new file, this is to check out what is going on.

Could you try each of the above and report back?

Re: Another newbie question regarding wavpack

Reply #7 –
I gave it a shot and no success. I tried it with both the 32bit and 64 bit Flac encoders. As well as the Wavpack encoder. I had checked both the 'pass wave header' and 'db write ID tags' boxes. As well as having them both unchecked and either or checked. I only get the 8.3 filename (audio file) when 'pass wave header' is checked. Doesn't seem to matter whether or not 'db write ID tags' is checked, it will not produce an 8.3 filename (audio file) without 'pass wave header' checked. One thing I forgot to mention is that when the 8.3 filename is created, there is another file created that is not associated with any programs and is of 0 size. THAT file will have the original name of the source file with "[codec]" added to the end of it. (without metadata of course).

Example:

OG file: Exemia - GUNVEIN (OST) - 01 Press Start -TITLE SCREEN-

8.3 filename: EXEMIA~2

Blank file: Exemia - GUNVEIN (OST) - 01 Press Start -TITLE SCREEN-    [codec]

The 8.3 filename can be played normally and is associated with my default player.

The blank file is literally just that.

For reference these are the inputs im using for wavpack:

-f -j0 -x0 [infile] [outfile]

-f -j0 -x0 --import-id3 --allow-huge-tags  [infile] [outfile]

-f -j0 -x0 [infile] --import-id3 --allow-huge-tags [outfile]

--import-id3 --allow-huge-tags -f -j0 -x0 [infile] [outfile]

Anyone one of these combinations will produce an 8.3 filename and the blank file as long as 'pass wave header' is checked.
If it isnt, it will only produce the blank file.

This is the input I used for the Flac encoders:

--disable-constant-subframes --disable-fixed-subframes --max-lpc-order=0 [infile] [outfile]

Same story with Flac as with Wavpack. Just to clarify I did create new folders with shorter names as well as renaming source files with shorter names. Doesn't seem to make a difference

Re: Another newbie question regarding wavpack

Reply #9 –
Try to disable antivirus. Or at least add destination folder to AV exceptions.

Re: Another newbie question regarding wavpack

Reply #10 –
Your naming string should be:

[origpath]\[origfilename]

Re: Another newbie question regarding wavpack

Reply #11 –
Does that mean I have to do each track individually? Forgive my ignorance. I just have no clue on how to translate that to the actual input

Re: Another newbie question regarding wavpack

Reply #12 –
Output To sets the folder and file naming converted files are saved:

    Existing Source Folder: converted tracks are written to same folder as the source file,
    Single Folder: all files written to a single folder of your choosing,
    Preserve Source Path: allows the selection of a base drive or folder, into which the full source path is added and source filename,
    Edit Dynamic Naming substitutes programmable elements, such as [artist] and replaces with real values from the ID Tags. dynamic is very flexible. In the above example all tracks are written to Artist then Album folders, whilst preserving the source filename. Further Naming Details  [dBpoweramp Reference required]

Choose the option 'Existing Source Folder' and the wavpack files will be created in the same location as the flac files automtically

Re: Another newbie question regarding wavpack

Reply #13 –
Quote from: Imakarum Mirabilis on
Does that mean I have to do each track individually? Forgive my ignorance. I just have no clue on how to translate that to the actual input
It's not the solution per se, but since the issue seems to be rather hard to find, in your place, I'd try to emulate it/isolate it in a fresh Windows installation, via Sandbox (assuming you're using Windows 10 or 11 on any flavour, but the Home Edition, that is):

If so, you'd have to enable it via:

Windows prompt:
Code: [Select]
dism /online /enable-feature /featurename:Containers-DisposableClientVM /all /norestart

...or Power Shell:
Code: [Select]
Enable-WindowsOptionalFeature -Online -FeatureName "Containers-DisposableClientVM" -All
I think it can also be activated in the Control Panel, but I've never tried it.

PS: If persistence is needed (i.e, you're willing to save the OS's state and get back to it later) Windows's own Hyper-V can create a virtual machine.
Apart from Celerons, Athlons & co., pretty much all x86 processors produced since 2006-07 support that.

• Listen to the music, not the media it's on
• The older, the 'lossier'

Re: Another newbie question regarding wavpack

Reply #15 –
Quote from: Porcus on
Sure you replied to the right post here?

Yep.
Quote
It's not the solution per se, but since the issue seems to be rather hard to find, in your place, I'd try to emulate it/isolate it in a fresh Windows installation

"When you have eliminated the impossible, whatever remains, however improbable, must be the truth." - Sherlock Holmes (A. Conan Doyle) - The Sign of the Four, 1890.
• Listen to the music, not the media it's on
• The older, the 'lossier'

Re: Another newbie question regarding wavpack

Reply #16 –
But wouldn't it be an idea to first try to follow the developer's guidance on how to set up the filenaming scheme ... ?

Re: Another newbie question regarding wavpack

Reply #17 –
Doh! In my half-arsed read of the topic, I didn't notice spoon was the developer and thought that to be a dead end of sorts.
Sorry! 
I should've known better - specially with you mentioning him midway through.
• Listen to the music, not the media it's on
• The older, the 'lossier'

Re: Another newbie question regarding wavpack

Reply #18 –
Ive tried to implement your recommendations but no success. I have the reference version. Ive been rendering to source location and it hasnt worked. I tried using dynamic naming, that didnt work either. Ive been successful with 3 other programs but for some reason dbpoweramp wont do it. Tbh its probably beyond my ability to figure out in a timely manner.

Re: Another newbie question regarding wavpack

Reply #19 –
First ensure is working using the normal encoders, you state ' I had checked both the 'pass wave header' and 'db write ID tags''   that is using the CLI encoder, there is no need, dBpoweramp has FLAC and wavpack native encoders and decoders, so take a flac file >> right click >> convert to >> choose Wavpack then click convert, If that works you can look at running from a command line, choose the options on the GUI then work out what is needed on the command line:

https://forum.dbpoweramp.com/forum/other-topics/developers-corner/18466-reading-compression-dsp-settings-for-scripting

Re: Another newbie question regarding wavpack

Reply #20 –
Normal encoders/decoders work normally. I located cli settings for wavpack using the registry like the link suggested.

The setting is:

-f -verify

Whatever the setting is at any time it must be accompanied with '[infile] [outfile]' at the end. Otherwise the 8.3 file wont be created, only the blank file will. Not sure if thats the same for anyone else but thats how it is with my set up.
Furthermore if is the setting:

-f -verify [infile] [outfile]

...only the blank files are created. But if I change '-verify' to '-v' then it creates the 8.3 files as well.

-f -v [infile] [outfile]

So my original intent to use '-f -j0 -x0' runs into the same problem even if I write it like so:

-f -j0 -x0 -v [infile] [outfile]


Re: Another newbie question regarding wavpack

Reply #21 –
Note that "-verify" is not a WavPack option. Not "--verify" with double dash either. But single hyphen means to apply all the letters; it would be shortform for -v -e -r -i -f -y and "-e" does not exist.

If you seriously want those WavPack settings, then ... you can use a standard setting, and then later run a re-encoding from command-line:

for /r %f IN (*.wv) do <path-to-wavpack-or-you-have-it-in-path> wavpack.exe --threads -vmyfj0 "%f"

The "--threads" assumes that you have a new wavpack. The letters mean as follows
v for verify
m for MD5 sum
y for "yes" to overwrite the file
f for fast mode
j0 for dual mono

Re: Another newbie question regarding wavpack

Reply #22 –
We do not use the wavpack cli encoder, so command line options for that would not apply.

"c:\program files\illustrate\dBpoweramp\coreconverter.exe" -infile="c:\afile.wav" -outfile="c:\outfile.wv" -convert_to="Wavpack" -f

There is no need for verify,checking the disk drive would never work as windows caches files, it is there to ensure there are no codec bugs, and in 15 years there have never been any, so not needed.

Re: Another newbie question regarding wavpack

Reply #23 –
I have a hunch that the user should use a GUI as far as possible. So use the Music Converter GUI to convert from a tagged format (like FLAC) to WavPack.
That should get all tags transferred, right?

And if that does not offer the desired options, then re-encode - all of them! - with wavpack.exe

Re: Another newbie question regarding wavpack

Reply #24 –
Yep all tags are automatically transferred using the GUI in dbpoweramp