I’m curious about the beta and itching to try it. Before I do, may I ask a couple of questions please:
I’m assuming that Audirvana Studio 2.11.5 and the beta version can be installed concurrently and be used alternatively. Will they be accessing the same Audirvana library or does the beta create a new library? If the latter, can the current library be imported into the beta?
Assuming that I won’t be using the three tentpole features (EQ, cross-fade, balance), what are the main areas for testing and feedback I should be looking at?
@waves, I know you are asking @Agoldnear … I hope you don’t mind my opinion…
Gain staging… Input as well as output gain management is the most important part of the process… Also, the order of the small signal processing chain/path is important… Color and/or Tone EQ would come before using EQ or Convolution for Room Correction DSP…
For me on a Mac it overwrites the existing file. Going back is a case of opening the old file .dmg and overwriting the beta file. However there is one gotcha, the My Music tab in the sidebar moves to the bottom of the sidebar and in settings/appearance it goes missing from the ordering list so cant move it back to my preferred position. I think if you kept an old copy of the V2 database this would be easily solvable.
I installed the BETA version, renamed it “Audirvana Studio BETA” in Finder, then installed the “normal” version, and now I switch between the two with the same database without any problems.
(except for BETA bugs)
But every computer has its own issues, so I always make a backup before doing anything like this…
The device selected is the MacBook local speakers… I tried to configure the HL Convolver, like I have done many times with success, and Audirvana just goes crazy… I was lucky I could get a System monitor snapshot as these processes hogging the system to the point that you may not gain control long enough to get a chance to monitor or even quit Audirvana…
BTY these two plugins used to work just fine with the previous version of Audirvana and still work using the Hang Loose Host & HLC with Apple Music… My guess is that the new plugin management is not quite right… Even you can not run your plugins any longer… And I understand that your old signal chain may not work any longer and you have moved to the new signal chain with success…
I, however, prefer my convolution for Digital Room Correction last in my signal chain and I do not see how that is possible with the new DSP… The plugins solution allows sequencing up to 4 plugins… So I can even have two instances of master quality EQs pushing and pulling like a Pultec and then do Digital Room Correction…
In the remote app on iPad we get the details of both the Total No of Tracks in Play Queue and how many remain to be played… however;
In the Studio App on Big Screen we only get the the number of remaining tracks. In that space above the number, would you be able to include the remaining playing time.
It may seem very minor and a petty request, and it probably is , however I find that it’s just one of those little things that I really notice and use a lot when setting up play queues or adding to them.
Obviously, something is not handling the plug-ins as expected, I see this partial display of the first insert slot (see screenshot) when I enable Plug-ins before inserting a plug-in… (It displays correctly after a plug-in has been inserted) I cannot open the plug-in to configure… However, I can open this one and others in Logic Pro and MainStage, but now here in v3, it is ‘hit and miss’ some plug-ins work and some don’t… (This is just using the System DAC of the Mac Studio with ‘Power of Two’ up-sampling…) Some plug-ins let me configure and use, while others won’t open or open a blank configure window. I was able to use 112 dB’s Redline Equalizer, but not Redline Monitor for instance.
It seems any HRTF virtualization DSP like Waves NX or Waves Abbey Road Studio 3 and Redline Monitor are rejected and cannot be opened…
Another weird thing, was that my output volume was muted automatically, when stopping playback after disabling real-time processing… I don’t know if this has been the normal operational function or not, because I am usually modulating all PCM to DSD, so no real-time control…
Even though I don’t apply plug-ins in v3 Beta, this unexpected behavior of the plug-in module and the behavior you are experiencing is disturbing, to be nice about it.
Also, the DSP signal-path display(s) are confusing… My feeling is the screenshot below of the ‘Processing’ module hierarchy, is correctly showing the signal-flow and makes the most sense to me, as compared to the main settings window hierachy display.
Thanks a lot for the work, I would never even hoped for a convolution in audirvana, so cool !
I dropped my response file in Audirvana that I currently use in Ableton Live for producing music and it actually works; so thank you However, when listening through the Convolution there are clicks/pops that occur.
I want the DSP done on the file prior to up-sampling in all cases… I don’t use Volume control in any form… Most plug-ins don’t support sample-rates beyond 192kHz, and for me, 192kHz is inadequate… The Redline Monitor supports up-to 384kHz, and the Waves HRTF virtual surround plug-ins are limited to 96kHz. Up-sampling/modulation to DSD makes an audible difference in all cases of PCM playback. (In my playback scenario). Even if I didn’t modulate to DSD256, I would want to up-sample to 705.6kHz or 768kHz after any processing, just to offload processing overhead in the DAC architecture.
I have a DAC that does 768kHz PCM so have no reason to upsample anything… Plus internally it upsamples with the Watts Transient Aligned (WTA) Filter… This DAC is purpose built for this task… And I usually listen to albums so the volume leveling is suppose to keep the same dynamic level across all songs in an album… I also believe that Digital Room Correction, EQ or Convolution, should be the last thing in the signal chain… Usually on the Monitor Bus…
, however I find that it’s just one of those little things that I really notice and use a lot when setting up play queues or adding to them.
However, when listening through the Convolution there are clicks/pops that occur.
