Thanks for the info. I believe I've read elsewhere that JRiver is supposed to have some kind of Lookback driver but in my version (23) I don't see that feature. I'll have to look into why that might be and if I would still need to install ASIO4ALL driver in addition to the ASIO driver that Lynx Studios supplies with the Hilo.ASIO generally only supports a single device, so it looks like the JRiver Media Center device has no inputs. There are applications that create ASIO wrappers around multiple devices to circumvent that limitation, such as ASIO4All and FlexASIO.
Read the rest of this update entry...Changes in V5.20 beta 17:
- Added Alt+C as a shortcut for the graph capture button
- Added a warning that Default input cannot be used for SPL calibration
- Added a message on the Cal Files preferences to select an input device and input if they have not been selected
- Bug fix: Manual SPL calibration was not working properly in beta 16
- Bug fix: RTA distortion panel did not show results if the signal generator had not been displayed
I’m not too savvy with this stuff or your needs but you can route to JRiver with java drivers. Windows driver must enabled in JRiver options. JRiver then appears as an audio device.Hello,
I was attempting to try and route REW sweeps thru JRiver for the purposes of confirming the correction applied from my Convolution FIR files but it appears that the "INPUT" channels are Greyed out within REW when choosing JRiver as the Output.
Is this the expected behavior? If so, I'm not sure how I can tell REW which Input my MIC is connected to if by chance that Input is something other than Channel 1-2.
If I change the ASIO Deice to my Lynx Hilo ASIO the Input Channel becomes active again.
View attachment 23609
Read the rest of this update entry...Changes in V5.20 beta 18:
- Don't show zero volume warnings if Suppress Soundcard Errors is selected
- Bug fix: Scope math traces could be clipped
- Bug fix: Stop windows selected from the menu being pushed behind the main window
- Bug fix: Changing graph while loading measurements could cause the legend to show the wrong trace names
- Bug fix: Devices with no input channels could appear in the mic cal files list
- Bug fix: Cal files were not being restored on next startup if...
Read the rest of this update entry...Changes in V5.20 beta 19:
- Added miniDSP EARS as a recognised USB mic, EARS gain is extracted from the device name - if the gain is changed disconnect and reconnect EARS and restart REW so the new gain is picked up
- Allow tone generator harmonic distortion levels down to -150 dB
- When an input or output device is selected automatically select the first input or output rather than selecting default
- When prompting for USB mic cal data show a mic calibration files dialog rather...
Read the rest of this update entry...V5.20 beta 20 changes:
- Added support for 768 kHz on ASIO. Tested for replay (ADI-2 DAC) but not for capture.
- When calculating target level for a Full range target use the measurement data from 200 Hz to 2000 Hz rather than from the LF cutoff to 2000 Hz
- Added support for a sensitivity figure in analog mic cal files. Format is: Sensitivity -12.3 dBFS where the dBFS value is the input level REW sees when the mic sees 94 dB SPL. Note that it will only be valid for the input gain...
Read the rest of this update entry...Changes in V5.20 beta 22:
- Added an option to show the audio frequency bands above the graph for the SPL & Phase and All SPL graphs
- Allow Soundcard calibration measurement names to be changed
- Bug fix: Measurement trace on RTA window did not update when trace offset was changed
I just imagined that perhaps there could be a scenario where one wants the graph itself copied in monochrome but the audio bands shaded in color like the screenshot in the preceeding message. In that case and in the context of the previous post, maybe the shading of the audio bands can be made an independent feature in the "View" tab of the Preferences option.Thanks John for the update.
I noticed when capturing the the graph with audio frequency bands enabled, they get mangled up in the captured image. It would be nice if the shading can be controlled by whether one has chosen to capture in monochrome or not. In monochrome case, perhaps the shading could be just white.
View attachment 24431
I can confirm that the audio bands get copied properly when using default resolution of 1538; the image is obviusly big and it somewhat looks different when compared to an image copied with a resolution of 600; I use this resolution almost aways, which kind of adjusts the vertical scale to make for a more visually appealing image in terms of scale, size and composition.I just imagined that perhaps there could be a scenario where one wants the graph itself copied in monochrome but the audio bands shaded in color like the screenshot in the preceeding message. In that case and in the context of the previous post, maybe the shading of the audio bands can be made an independent feature in the "View" tab of the Preferences option.
Thank you so much for a wonderful application.