I made some 24/192 files using dbpoweramp, but Foobar outputs no sound when playing them.  The same files but at 24/96 play fine.

I am sure my Lynx 2 card supports 24/192, and when I play such a file in Foobar, the Lynx mixer's clock does report 192...just no sound.

Are there any settings that could be affecting the output, like the asio buffer, etc?

What happens if you remove the crossover plugin?

Quote from: tgoose on 2006-10-07 01:52:14

What happens if you remove the crossover plugin?

Well, I tried this today, and nothing would play, it kept giveing me an error.

I think that it has to do with how I have it mapped in ASIO when using the crossover.

I just tried re doing the asio map, and it works, but I get an error on 24/96 and 24/192:

<Unrecoverable playback error: invalid audio stream specifications.>

16/44.1 files play fine with or without the crossover plugin.

What is weird is that WITH the crossover plugin 24/96 PLAYS, but without it, it doesn't work.

Put the crossover and asio mapping back in, and 24/96 works.

Strange. It must be some setting some place.

Could you try uploading a small sample (less than thirty seconds) of one of the files that won't play? I've never had any 24/192 files to need to play so I've no idea if it works for me!

The plugin I have is foo_out_asio 1.2.4 but I have no crossover and only a stereo interface - perhaps if you upgrade to 0.9.4 and try removing some mappings so you're only using two channels (I don't know how or if this will work since I've never used a surround system on PC, but it's worth a try).

I didn't work for me either when I tried to play the wav.  I'm new to 24bit audio, so I don't know why you need the plugins for anything.  All I have set is my output to 24bit.

I did get it to work when I converted it to WavPack.  Try that for the whole song maybe?

Quote from: DrazardX on 2006-10-08 19:22:37

I didn't work for me either when I tried to play the wav.  I'm new to 24bit audio, so I don't know why you need the plugins for anything.  All I have set is my output to 24bit.

I did get it to work when I converted it to WavPack.  Try that for the whole song maybe?

Was it 24/192 when converted to wavepack?  Or did it convert them to some lower format.

I am know nothing about wavepack, and attempts to convert have been unsucessful.

I am sure I set foobar up for only waves and nixed all the other formats if it was possible.

I downloaded some stuff from wavepacks site, but have no clue about what goes where and what I really need.

Where should I look for this info?

My parameters in the foobar convert tool for WavPack are  ( -hm -i -%d ).
To encode using 24/192 nothing needs to be different.  WavPack will by default keep the same bits and samplerate.

(-h) Compresses more but slowers decompression speed.  It's kinda useful for such big files, if you're computer is fast enough to decode it without gaps though.

(-m) Keeps the original MD5 to verifiy that the data is the same as the original.

(-i)  Something with piping that is needed when you use foobar to convert.

I combine -h and -m to look like -hm for some reason.  It doesn't hurt or help.
Check out the WavPack forums here.  The newest version in progress has a new high setting that looks pretty good, as well as an improved extra setting.  I might be using different settings with the new WavPack.

The only setting you need to use is -i, and that's only because you're using foobar.

EDIT: Make sure the "Keep lossless sources at original bit depth" box is checked on the converter page.

Sorry, I forgot.  I am using a custom encoder setting, not the wavpack one foobar uses by default.  You can simply use that without changing anything.  Moving the bar to high would be the same as -h.  If you want you could create one using the command line by pressing add new.  Then choose custom and point to the exe and add whatever settings you want.  The WavPack user manual on the site is very helpful for explanation for the settings.  This is only necessary if you feel like adding other options like -m.

I know i'm not the best at explaining things, but I try.

DrazardX, I am pretty sure that foobar2000 adds MD5 sums to its converted WavPack files by default - and it probably takes care of any supposed piping issue by itself.

Quote from: dv1989 on 2006-10-09 08:22:19

DrazardX, I am pretty sure that foobar2000 adds MD5 sums to its converted WavPack files by default - and it probably takes care of any supposed piping issue by itself.

I never actually tried so i'm suprised it does.  Still, I can't get foobar2000 to encode 24/192 WavPacks.

I seriously doubt anything will ever be better than Multi frontend for encoding audio files.  It keeps the simplicity of the command lines but allows you to select several files at once.  What more do you need?  Well maybe a shell extension would be nice too (don't point me at dbPoweramp).  I foobar2000 for the tagging and playback.

I put a 2 second file in the up loads section (30 seconds would have been about 30 Mb!):

...

Quote from: Dawnrazor-age on 2006-10-08 19:08:10

I put a 2 second file in the up loads section (30 seconds would have been about 30 Mb!):

...

It seems that Foobar does not like WAVE_FORMAT_EXTENSIBLE (0xFFFE) as format tag.
If you change it to PCM (0x0001) it plays OK.
The same issue is with conversion, so this should not be a output plugin bug.