bpa wrote:
> I opt for spelling out all possibilities.
>
> As I read your posts (albeit very quickly) you can play 44.1/16 but
> possibly you haven't managed to get wavin2cmd to record 96/24 - then
> * point 3 in terms of modes may not be an issue but perhaps the audio
> format part of properties might be an issue.
> * point 1 & 2 - you haven't shown that the modified conf file works -
> typos creep in and you haven't proven recording 96kHz works OK so still
> perhaps parameter issue.
> * I don't know your source device so I have to consider whether
> different audio formats show up as different devices or whether a single
> device handles all formats. It's not clear whether audacity uses the
> same audio API as wavin2cmd. Windows has about 4 types of Audio API.
>
>
> It is not logged in as admin - just runs under a logged user and not a
> service. I don;t use Windows normally so my terminology may be wrong. I
> remember one user had a problem when LMS runs as a service. Just trying
> to point out possible causes of failure.
I finally got it to work -24/96 all the way to my DAC and speakers!!!
Thanks a lot for your help and inputs!
Firstly, to your 3 points:
3. These kind of problems were ruled out by a working solution.
1-2: I attempted several variations of your suggested "wavin2cmd.exe -o
wavin:3 > audiocapture.raw" where I got all combinations of bitrates
44,1-96 to play back in Audacity or convert correctly through flac.exe
at 16 bit depth. However, at 24 bit nothing worked. This led me to
suspect that wavin2cmd just doesn't support 24 or higher bits?(Somebody
care to verify?) Maybe I'm wrong, but I gave up after skimming the
source code and the tests above, as well as the alternate and hacky
solution I stumbled across.
Secondly, the hackety and ugly, but working solution:
-I copied the sox.exe to the WaveInput plugin bin folder and renamed it
to wavin2cmd.exe
-Then I edited the custom-convert.conf file to:
Code:
--------------------
[wavin2cmd] -q -r 96000 -b 24 -t waveaudio 2 -t flac -
--------------------
Pros:
-It works much faster and with shorter latency than the built-in
solution, without the need to pipe the command via flac as step 2
-The hardcoded "2" after "waveauido" can probably be changed to the
variable "$FILE$", so that it will continue to work seamlessly with
numbers instead of "wavin:X" references to the audio device.
Cons:
-The setup will probably not survive any (plugin)updates
-Bad solution to rename an executable
Maybe it could be an idea for someone competent and motivated to update
the WaveInput plugin to work with the sox.exe instead of wavin2cmd.exe
in the (near) future?
I tried to look at the code, but unfortunately couldn't figure our the
references [wavin2cmd] and [flac] to the executables wavin2cmd.exe and
flac.exe, respectively...
Really happy to see the 92kHz diode light up on my DAC, but only the
gods know for certain if I really get the extra bit quality and
information from Tidals master/hi-res/MQA to my speakers!... ;-)
Maybe someone could verify?
Br,
Vegard
------------------------------------------------------------------------
Vegz78's Profile: http://forums.slimdevices.com/member.php?userid=32897
View this thread: http://forums.slimdevices.com/showthread.php?t=102551
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
