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: Wavpack.exe and two-core CPU (Read 10672 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Wavpack.exe and two-core CPU

Well, basically, i love wavpack and i want to see it supporting two-core CPUs...
will it be possible?..

thanks in advance...

Wavpack.exe and two-core CPU

Reply #1 –
Tell your app to run two instances at once.

Wavpack.exe and two-core CPU

Reply #2 –
I think it's better to ask the developers of CD-Rippers for supporting encoding tracks in parallel so you don't need multithreaded version of various encoders (which are often complicated to develop).

*wink wink* :-D

my 2 cents,
Sebastian


Quote from: Mike Giacomelli on
Tell your app to run two instances at once.

Oh, is this already supported by any cd ripping tool?

Wavpack.exe and two-core CPU

Reply #3 –
i know foobar2000 does

Wavpack.exe and two-core CPU

Reply #5 –
Also, you can run multiple instances of EAC, each with its own compressor (if you rip from multiple drives in parallel).

-brendan

Wavpack.exe and two-core CPU

Reply #7 –
just execute wavpack.exe twice in your program. there shouldn't be anything complicated about that.

Wavpack.exe and two-core CPU

Reply #8 –
Nope, does not work...
if i execute wavpack twice, the computer just stalls...

p.s. OggVorbis is great - it uses 2 core at the time...

Wavpack.exe and two-core CPU

Reply #9 –


that's weird. right now, i'm doing -x6 conversions of a few of my albums from FLAC to WavPack and i'm not experiencing any problems. i'm also using foobar2000 which launches 2 processes anyways.

Wavpack.exe and two-core CPU

Reply #10 –
Quote from: satorippoi on
Nope, does not work...
if i execute wavpack twice, the computer just stalls...

p.s. OggVorbis is great - it uses 2 core at the time...



You're doing something wrong.

Wavpack.exe and two-core CPU

Reply #11 –
Should i activate some special settings in Windows or inside Fb2k?..

Wavpack.exe and two-core CPU

Reply #12 –
Quote from: satorippoi on
Should i activate some special settings in Windows or inside Fb2k?..


I can't find that setting in Foobar either, can someone give a clue on this?
In my office's PC, a P4 2.4 GHz with Hyperthreading is what I have, and Wavpack doesn't scale as well as I'd like. It only has affinity with one "virtual" processor.

Thanks in advance! 

Wavpack.exe and two-core CPU

Reply #13 –
foobar2000 detects the number of cpu cores by itself and then uses one instance per core automatically. You don't have to do anything...

But if you only encode one file at a time, there will only be one wavpack process...

So the idea of starting an encoder process for each core isn't practical at all when you're only encoding one file at a time (for example an image rip in EAC). Multi-threading support within the encoder itself would be needed nevertheless in this (IMHO not so rare) case.

Btw, I'm affected by this myself since I have a hyperthreading P4.

EDIT: You can use the full power of your hyperthreading CPUs under XP (for applications that can't handle multiple threads), but it's a bit complicated. You need to exchange the multicore HAL (hardware abstraction layer) with a single core HAL, or more conveniently, create an alternative boot.ini entry... Simply disabling HT in the BIOS is not enough, because XP's thread managing system circumvents this BIOS setting (or to be more precise the multi-core kernel does). Changing the HAL involves using a different set of two essential system files of which I can't remember the names right now, one if part of the kernel of course. When creating the boot.ini entry you have to use a boot option and point to the single-core occurences of those two system files which you can find on the XP install CD or even from some place in your %WINDIR%.

Anyway, this would only be of use when you want to process big WAV files one after another and you can't process them for some reason in parallel (for example you have to rip them CDs first... and want EAC to encode the WAVs during the rip instead of letting this job do fb2k when you're done ripping to WAVs). IMHO it's not worth the trouble... just harmonise your encoding methods to your multi-core hardware setup.

Wavpack.exe and two-core CPU

Reply #14 –
Well, I have Core2Duo, so there is no need for hyperthreading procedures for me...
all i need is a support for dual-core CPUs...just like it is done in OggVorbis...

Wavpack.exe and two-core CPU

Reply #15 –
Quote from: Fandango on
foobar2000 detects the number of cpu cores by itself and then uses one instance per core automatically. You don't have to do anything...

But if you only encode one file at a time, there will only be one wavpack process...

So the idea of starting an encoder process for each core isn't practical at all when you're only encoding one file at a time (for example an image rip in EAC). Multi-threading support within the encoder itself would be needed nevertheless in this (IMHO not so rare) case.

Btw, I'm affected by this myself since I have a hyperthreading P4.

EDIT: You can use the full power of your hyperthreading CPUs under XP (for applications that can't handle multiple threads), but it's a bit complicated. You need to exchange the multicore HAL (hardware abstraction layer) with a single core HAL, or more conveniently, create an alternative boot.ini entry... Simply disabling HT in the BIOS is not enough, because XP's thread managing system circumvents this BIOS setting (or to be more precise the multi-core kernel does). Changing the HAL involves using a different set of two essential system files of which I can't remember the names right now, one if part of the kernel of course. When creating the boot.ini entry you have to use a boot option and point to the single-core occurences of those two system files which you can find on the XP install CD or even from some place in your %WINDIR%.

Anyway, this would only be of use when you want to process big WAV files one after another and you can't process them for some reason in parallel (for example you have to rip them CDs first... and want EAC to encode the WAVs during the rip instead of letting this job do fb2k when you're done ripping to WAVs). IMHO it's not worth the trouble... just harmonise your encoding methods to your multi-core hardware setup.



Nice solution, changing the HAL, this never occurred to me. Thanks for the tip!
But in this situation where I want to convert a single album image one at a time, it's really boring, using only one HT's processor. I hope there's a new patch/version when I buy my Core2Duo!
BTW, other lossless encoders scale well with HT and C2Duo?

Regards. 

Wavpack.exe and two-core CPU

Reply #16 –
Well, i got my problem solved - just instead of 7 i set priority thread for transcoding at 5 in fb2k and it works like magic!!!