SpecMode

Biggest issue I'm running into so far in 2.0.9 is when using filtering within a playlist. Specifically, if I select a playlist, filter it by some criteria (say, file type), then try to play a track, Audirvana will then play the track that currently occupies the playlist index (line) position that the track I'm trying to play used to occupy. By way of example: In an unfiltered playlist, track A is at line 5, and track B is at line 9. After I apply some filter to the list, track A is now at line 2, and track B is now at line 5 (where track A used to be). If I now try to play track A, track B will play instead. Looks like track playlist index position references aren't being updated properly when filters are applied.

What's probably happening is that the update installer is replacing the modified, unsigned driver with an updated, signed version, which has the side effect of disabling TRIM because the modification is no longer present post-update.

I don't think it's unreasonable to remove support for OS X versions older than, say, 10.8; the amount of extra effort required to work around limitations in those older systems while adding and improving features must be weighed against the relatively small number of users still remaining on those older versions. Beyond a certain point, the time spent on old codebase maintenance could be far better spent on making the app better for the vast majority of existing (and potential new) users.

In Audirvana Plus preferences, select 'Audio Filters', and make sure 'Converter' is set to 'Izotope 64-bit SRC'. Expand 'Advanced Parameters' below that, and change the values to match those in your post (or to whatever you want, really). Note that they'll only have any effect if you're actually changing the sample rate of the tracks you're playing (typically upsampling, which is controlled by the next setting down on that page).

Aha, gotcha. Looks like the only way to display it now is to check the track info manually (Command+I, sample size is under the File tab). That's less than ideal. I went ahead and filed an enhancement request with Apple to add sample size to the available column list (as well as making it a filter criteria for smart playlists). Who knows if it'll actually happen, though.

The bit rate, sample rate, or something else? I can still see them in the Song List view in the latest beta.

A couple of things to try, particularly if you enabled the system optimization feature: Delete the following files: /Library/LaunchDaemons/com.audirvana.Audirvana-Plus.plist /Library/PrivilegedHelperTools/com.audirvana.Audirvana-Plus Open System Preferences -> Sound -> Output, and ensure that the desired device is selected. Reboot your computer. If sound still isn't working, reboot again, but before you hear the startup chime (and before the Apple logo appears), press and hold the Command, Option, P, and R keys on your keyboard; continue holding them until you hear the startup chime twice. Let us know if any of this works.

Seems to me that the easiest option would be configuring an AudioUnit effect. Open Audirvana preferences, click the 'AudioUnits' header, and check the box next to 'Use AudioUnits effects'. In one of the dropdown menus, select 'Apple: AUGraphicEQ', 'Apple: AUNBandEQ', or 'Apple: AUParametricEQ', then click 'Configure'. Modify the EQ settings as desired, then click 'Apply'.

Meridian Explorer, on both Mountain Lion and Mavericks.

The control in question should be right next to the volume slider in the iTunes main window, as shown here: If you've already found and fixed that, then it may well be an A+ bug.

Some feedback for Damien: if possible, you might consider allowing non-formatted values for manual field entries, and format them appropriately during validation (ideally using the system's localization settings).

I've seen the same behavior; looks like the program is hardcoded to only accept the formatted number (with commas). On a similar note, the Nyquist value seems hardcoded to use a comma rather than a decimal point for its value (though I haven't tried typing one in myself to test the validation).

Just a quick heads-up for everyone who may developing on (or "testing") Mavericks: today's DP8 update includes a new iTunes 11.1 beta that appears to break iTunes Integrated Mode, at least with today's Audirvana test build (1.5.7.7). So, if you like to stay on the bleeding edge...well​, consider yourself duly advised.