David Baay

Here's one with some interesting info about where things are stored, but the OP ended up reinstalling everything to get icons back:

I don't have Analog Lab V, but have seen other analog-modeling Arturia synths make quiescent noise at a low level - not audible, but visible in meters and analyzers as your screenshot shows.

I'm going to suggest running the VC Redist repair tool linked in the post below. If the problem persists, it may be due some plugin-related race condition that has a different outcome on the two machines.

Cool. Glad to help.

Izotope/NI stuff is mostly scalable which will help with the overall size of controls and displays but may still leave text too small. I always try scaling the plugin first if possible and only disable DPI Awareness if that's not sufficient.

True, but giving step-by-step instructions for anything always comes off as more complicated than it is. ;^) I always advocate finding a used/open box deal for those on a budget. That's a good example. I think an M5 is in my future when ye olde MOTU 424 PCIe system becomes unusable due to hardware or O/S evolution.

I was just going to add that the UID of plugin should not have changed with the update to v2.5. My guess is that your old projects were using the VST2 and you only installed the VST3 version of the plugin when you updated. If that's the case, Installing the VST2 will save you time having to correct the drum maps in multiple projects.

Hold Ctrl+Shift while changing one port assignment, and they'll all change.

Dis-Arm the track. When armed for recording, the meter shows the Input level.

Like other clip-level FX and edits, Region FX can also be rendered by Bounce to Clip(s). Not sure why the OP is reporting it doesn't work.

Just to be clear, since the microphone has an analog connection to the Neo 'interface', it is not going to show up directly as an input device in CbB. What you should see is the driver for the port on the Neo to which the Mic is connected. It looks to me like the Neo is strictly a class-compliant Windows device so you should see its inputs and outputs in WASAPI mode. Ideally you should connect headphones or motniros to the Neo's analog outputs. If you want to use the USB speakers, you;ll want to set that as the Playback Timing Master while the Neo is the Record Timing Master, but using two different devices for input ant ouput is not ideal. Here's how you would normally go about using a class-compliant device like the Neo: - In Preferences > Audio > Playback and Recording, set the Driver Mode to WASAPI - In Audio > Devices, Check all input/output ports associated with that device. - In Audio > Driver Settings, ensure that the Playback and Record Timing Masters are set to Output/Input ports associated with that device. - Connect headphones (preferable when recording from a mic) or powered monitors or an amp with passive speaker/monitors to the L/R Outputs of the interface. - Add an audio track to a project, assign the relevant Input via the "I" control (a.k.a "widget") in the track. The Ouput should already have defaulted to the Master bus (or direct the interface outputs if you started from a completely empty template with no buses). - If using headphones, enable the Input Echo button (icon looks like headphones) on the track. Do not enable this if using monitors or you will get feedback between the mic and monitors. - Click the record (arming) button on the track to arm it for recording. - Make some noise into the mic and verify you see the track meter responding; if it's peaking in the red (above -6dB), turn down the input level on the interface. - Hit R on the PC keyboard to start recording, and make some more noise into the mic. - Hit Spacebar to stop recording. - Hit W to reWind, and hit Spacebar again to play back the recording.

Yes, rendering clip FX is done by Bounce to Clip(s). If you don;t want to use Workspaces, set Worksapce to None, and your Toolbar will be the same for all projects. IF you want to use whatever Workspace is enable, you need to re-Save the WOrkspace after making any changes ot the layout, including the Toolbar.\ Sonar is unchanged from CbB. If 'Always Echo Current MIDI Track' is enabled in Preferences > MIDI > Playback and Recording the Input of new MIDI tracks will default to 'Omni' which is effectively All, including virtual ports of VSTs. If 'Always Echo' is disabled, the Input will default to 'None', and you can manually select a specific port, but if you manually enable Input Echo before doing that, the Input will default to All External. It has never been possible to set a single default Input port that is automatically set when you insert a new track and/or enable Input Echo whether manually or by 'Always Echo...'

Was this resolved? I'm just curious how things are going with this version The current release is very solid. Eden was encountering an issue precipitated by a Windows update that broke the VC Redist on which Sonar depends. I also encountered this issue which was causing Sonar to crash immediately on launch.

Yeah, I was thinking more in terms of an option that would affect all strips in a pane, but I just discovered you can quick group by holding Ctrl while making the change on all selected tracks/buses so that's pretty quick and easy.

Dollars to donuts its due to an FX with a lookahead buffer. Common offenders are convolution reverbs, linear phase EQ/Compression and transient shapers. If the FX isn't in the path of the track you're input monitoring, you can click the PDC button in the Mix Module to override Plugin Delay Compensation on input-monitored tracks while tracking. But if it's on the Master bus or otherwise in the path from that track to the ouput, you'll need to disable/remove it.

Since the path from TD-27 to and through the Focusrite's direct monitoring circuit is all analog, monitoring from the Focusrite will be the same as from the TD-27 in terms of latency and will be necessary to hear Sonar's click or existing tracks. I agree tracking is often best done "dry" but there are situations where you really need to hear FX (e.g. syncing the performance tempo to a delay when not playing to a click), and it can help the performance to be hearing some semblance of the reverb space that will be on the final mix as it can affect how you articulate. You just need to stay away from FX that use big lookahead buffers.

As I said, the registry entries belong to Sonar. A plugin installer/uninstaller doesn't know or care what DAWs you have installed or what/where they write to the registry when they scan. Sonar's scan should have detected the file was no longer in place and removed the registry entries.

I just recently started using a Workspace. I created it specifically to stretch the Console and Inspector faders and put the pane splitters of the Console in a reasonable default starting position becasue I had a bunch of projects made from a template that inadvertently had the Tracks pane competely collapsed. I don't have the Workspace set to be a applied automatically on opening a project, but when I select it, all my preferred Console settings are applied as expected, including wide/narrow strips, though I wasn't aware it was possible to have wide buses and narrow tracks...?

That rectangle should be displaying the tempo at the pointer position like "Tempo: 67 bpm". EDIT: Likewise the rectangle in the controller pane should be showing the controller level at the pointer. The one issue I'm seeing is that the controller level, timestamp and event counter do not update continuously as the pointer moves; it continues to show the level, time and count of at which you first clicked which seems like a bug. In the tempo view, the value updates continuously as expected.

I missed this post. Sounds like you are now direct-monitoring the TD27's analog output through the Focusrite which doesn't require Sonar to be using its driver. If you enable Input Echo on the tracks receiving the multitrack input from the TD-27's driver, you'll hear an echo/delay from the latency. Leave Input Echo off, and it's a perfectly valid solution apart from not being able to record anything else from the Focusrite's inputs, not being able to have FX applied to the drums in real time, and having some additional output latency from soft synths if you ever play/record live from a MIDI keyboard.

Hmmm.... strange that scanning did not fix it. I just checked by removing a file from my VST3 folder, and Sonar detected it within 5-10 seconds and removed the entry from the registry. No fuss, no muss.

The registry entries are made by Sonar when is scans. You just need to do re-scan from Plugin Manager and it will remove registry entries for for which files are no longer present. I just leave Automatic Background Scan enabled in preferences and Sonar keeps track of all comings and goings of plugin files and will update within seconds of a change.

Yes, my guess is that you're looking in the wrong place in the CbB UI. Instument plugins can either be dragged in from the Instrument tab of the browser to an empty area of the Tracks Pane or inserted by right-click Insert Instrument in the Tracks Pane or Insert > Soft Synth from the main menu. All of these methods will insert the synth in the Synth Rack and create MIDI/Audio or a combined Simple Instrument track to get MIDI input to and audio ouput from the synth in the rack. Although CbB supports inserting synth plugins in FX bins, that is not the preferred method, has limitations, and may not always work correctly with some synths.

The drastic difference between 2x the buffer latency (2 x 5.8ms = 11.6ms) and the reported round-trip of 28.1ms indicates that the TD-27 has a lot of hardware/firmware latency. Typical USB interfaces like your Focusrite will add only 6-8ms to the buffer latency, and good ones may add only 3-4. Adding 16.5ms is huge, and you're not going to eliminate that or compensate by running a smaller buffer (256 samples is a lot for real-time monitoring) . I can only think the TD-27's audio output is really only meant for recording-pre-existing MIDI and not real-time monitoring. I would suggest your use the Focusrite to record MIDI in real time, monitoring the combined stereo analog output from the TD-27 through Sonar (or direct from the Focusrite with direct-monitoring engaged) and after polishing up the MIDI, switch to the TD-27 and record it's separate outputs. I realize this is awkward and not what you would like, but based on what the Driver Setting page is showing, you are not going to get real-tme playability with the TD-27 driver. You could try recording the multitrack audio from the TD-27 with its driver selected while direct-monitoring from it's headphone out. The recordings will be automatically compensated for Input latency when you stop recording, but you will probably find that the MIDI is late because you're performing to a delayed late click from Sonar due to the Output latency and MIDI is not latency compensated. If you're not planning on editing the MIDI and re-recording maybe that doesn't matter to you.

Only one ASIO driver can be in use at a time. This is an ASIO limitation, not Sonar.