Working fine for me on W10 x64.
Possibly the compile you are using requires an unsupported CPU feature.
Quote from: A_Man_Eating_Duck on 11 October, 2015, 09:39:25 PMWorking fine for me on W10 x64.Weried. I've reproduced the same problem on other windows 10 pc.
Quote from: samidare1234 on 11 October, 2015, 09:56:34 PMQuote from: A_Man_Eating_Duck on 11 October, 2015, 09:39:25 PMWorking fine for me on W10 x64.Weried. I've reproduced the same problem on other windows 10 pc.Unfortunately I don't have a Windows 10 system yet, but maybe you can answer a couple questions.First, does “wavpack --help” work, or does it only crash if you try to compress audio?Also, can you check if the previous version crashes too (it's been out for almost 5 months)? It's located here.In the meantime, of course, you can use the 32-bit version. It's actually almost as fast as the 64-bit version, and sometimes even faster.Thanks for the help, and sorry for the trouble!--David
What's the full path (incl. filename) of the encoder?
Try to put the files in a different directory/folder and run Command Prompt as Administrator before running wavpack.exe. It might be some kind of Permission issue
There's only one tricky thing that wavpack.exe does before displaying the help message, and I've eliminated that for a test (it has to do with the debug mode).Could you please try the attached executable with either just "wavpack" or "wavpack --help"?Thanks!
Corrupted download or broken windows install?
Notice that in the CP932.TXT mapping table linked below, code 0x5C is mapped to U+005C REVERSE SOLIDUS (\). This is often a source of confusion because in many Japanese fonts, this code is displayed as a Yen symbol, which would normally be represented as U+00A5 YEN SIGN (¥) in Unicode. However, on Windows systems, code 0x5C in code page 932 behaves as a reverse solidus (backslash) in all respects other than how it is displayed by some fonts.
There is one thing that bugs me on that screenshot, that "Y"-like symbol.Is that a chinese/japanese Windows? If so, maybe the problem is related to unicode support. (in the multibyte sense of the term).Btw, to further help on the diagnosis, it would be nice that you report the real error.To do so, open the Event viewer (you can do that easily writing eventvwr on the search box).there, open the "Windows Logs" folder, Applications, and locate the error for wavpack
I built Wavpack 4.75.2 with 3 different compilers. Maybe one of them will work?
Fault offset: 0x00007ffde3aced90
Quote from: samidare1234 on 14 October, 2015, 06:35:08 PMFault offset: 0x00007ffde3aced90One thing that comes to mind: download VMMap, then:1) run wavpack2) start VMMap, choose wavpack.exe process, then File -> Save As... and save wavpack.mmp file.3) Open Event viewer, and find the event for this crash.4) post the contents of the event and wavpack.mmp.