Thanks. Getting those period size alignments (hopefully) right took a while https://github.com/pavhofman/csjsound-wasapi/commit/26bdf4f0054d07dcf7251de7394c35048ab4f4ad...44.1 and 88.2 are now working, but now 192 kHz is failing, whereas it worked before. New log file attached, 48 at startup, then switched to 192.
All rates are now working, thanks very much.Fixed https://drive.google.com/file/d/12IxfO8Z7o1M-KkKwxYbQaZ-oa2m-eGN4/view?usp=sharing , thanks for testing
It's both. With HDMI, the Sink's EDID specifies a Speaker Allocation Data Block (SADB), which specifies all of the speakers that are usable with multichannel LPCM. I would think a generic HDMI driver would allow any channel mask where the number of 1 bits equals the channel count, and where the indicated speakers are all present in the SADB. (I haven't seen a way to obtain the SADB info through a Windows API, though.) A 7.1 sound system might support two variants of 5.1, one using SL/SR and one using BL/BR, and the user could choose which to use. The Windows sound control panel offers both of those options for 5.1, for example.From what I understand the channel masks in the wasapi format are not so much about selecting by user, but more about finding a combination which the driver accepts.
Ah.The javasound API does not allow for setting the channel mask from java/REW, it would have to be hacked in some workaround.
Dear John,One final set of updates have been made for the Windows and Linux versions of the early access builds. The big change is support for WASAPI exclusive when using the Java drivers, courtesy of some heroic work by Pavel Hofman. That means multichannel access and full sample resolution without any need for ASIO wrappers. The corresponding Linux AMD64 ALSA PCM support has also been updated. There are a few minor changes that I slipped in while working with Pavel on the WASAPI support:
- REW now retains the last 7 days of measurements in the temp folder, deleting any older than 7 days on startup. If REW did not shut down normally it will offer to load any measurements that were made since it last started up. If you mistakenly delete a measurement or forget to save it, there will be a copy in the temp folder of the REW log files folder for a week
- Added a soundcard preference to treat 32-bit sample formats as carrying 24-bit data, since formats that claim to be 32-bit almost always carry 24-bit data
- Allow a broader range for the speed of sound setting to accommodate media other than air
- Added check boxes in the FlexASIO control panel to select exclusive mode when using WASAPI
- Expanded the REW bit depth detector to 32 bits
A lot changed to accommodate WASAPI exclusive access, so feedback on how well that works (or doesn't!) is welcome. You may notice a slight delay after initial startup, depending on how many audio interfaces you have - WASAPI enumeration is a bit time-consuming since all possible format combinations have to be tested.
What command do you use for running REW with the system-wide JRE? Are environment variable LD_LIBRARY_PRELOAD or java parameter -Djava.library.path pointing to the REW installation dir with the libcsjsound_amd64.so library?FYI on linux/fedora36 the list of detected devices only shows PCM devices when using the bundled JRE ; otherwise those aren't displayed when using the system-wide jre one (despite being the same version - 18.104.22.1685):
Nothing specific - no LD_...PRELOAD or stuff like that - I started REW as usual (~/REW/roomeqwizard), once with the version with jre bundled, once with the version without.What command do you use for running REW with the system-wide JRE
Noted; as mentioned it was a minor finding, I thought it could be helfpul for you to know.The build without JRE is intended for non-AMD64 systems and does not include the AMD64 library file
The filters created do work as intended. Further improvement could be on the precision of the actual FR like FDW with separate window widths for left & right based on actual reverberation times like RT60?Good to hear. I wasn't trying to provide an FIR generator, just tidying up the divide and inverse operations to include regularisation. Tacking on the frequency limits and notch exclusion were fairly simple additions. I don't think there is enough there to consider it a serious attempt at FIR EQ, but enough to play around with.
Those are defaults for new measurements (or when no measurements have been loaded), they don't have any effect on existing measurements.I am not sure if this is an early access version bug but the room curve metrics entered in Preferences do not show up in the EQ windows:
Correction: They do show up when you restart REW!!!