brundlefly

I'm afraid you might be out of luck. A Project Template could save this configuration but you would lose MIDI tempo and other content when importing to a project started from the template rather than opening MIDI files as new projects. And I checked to see if Workspaces save this setting but it appears not.

I've not used this plugin before now to know how it behaved before the most recent Windows update. It doesn't appear to have any effect on my mouse pointer or UI reponsiveness in general, but it is a major CPU hog with an 8ms lookahead buffer that requires quadrupling my normal ASIO buffer to get smooth playback in even the simplest project that normally shows virtually no activity in the Perf Meter. The audio engine drops out immediately with a nasty glitch otherwise. Enabling Plugin Load Balancing also helps somewhat.

Your understanding of the issue is faulty. The issue is not with audio output; it's with MIDI input. Sock Monkey's understanding of the FP-30 and the need for a driver to be installed was also faulty, but he was not wrong in pointing out that your suggestion was irrelevant to getting MIDI input to work.

I tested every major version back to Sonar 7, and it appears the lowered magnetic strength/intensity has only ever applied to slip-editing clip boundaries and not to moving clips in the track view. This would be clearer if the documentation specifically mentioned slip-editing since moving a clip does move its boundary. In any case, like you, I find the behavior unexpected. IMHO, moving clips with reduced intensity should behave the same as moving notes and other events in the PRV. But at this point it's a feature request, as it was apparently never intended to work that way for clips.

Okay, I was able to repro issues attempting to snap the clip at bar 86 in track 12 to some of the clips in track 11. I haven't completely figured out what's going on, but deleting tracks 3-5 got it working. Seems to be some linkage/interaction there, but I'm not immediately seeing it.

Go to Device Manager and confirm you see the MIDI ports appearing disappearing from the Software Devices section when you connect/disconnect the FP-30 with the power on or when you power it on/off. If windows doesn't see them, the DAW won't, either. I don't think the FP-30 needs drivers for the USB-MIDI ports to work. It just needs to be powered up. Try a different USB port if available, and try booting your PC with the FP-30 already powered up or vice versa - powering up after booting.

Well this is interesting... I can't replicate either problem in this project. Clips are moving smoothly between other clip landmarks, and snapping to every candidate as expected everywhere I tried. EDIT: I take that back. Movement is still behaving like snap intensity is maxed, but I am able to hit every landmark so far. Keep in mind that it matters where you grab a clip. If you grab in the left haf, you're snapping the clip's start to landmarks, and if you grab in the right half, you're snapping the end. And if you grab a group, it's the start and end of the group that snaps.

I can't repro that problem; will need to see a project that does it.

Snapping clips to other clips isn't a common workflow for me but I just checked it out and am not seeing any problems. Can you link a simple project with steps to reproduce the issue? EDIT: That said, I do see what you mean about the intensity always being maxed. Lower intensity is working as expected for notes in the PRV, but not for clips in the track view. I usually have snap at or near maximum and just disable it completely when I want to make a fine adjustement, so hadn't really noticed.

To resize multiple/all track heights, select them and hold Shift while changing the height of one.

OK, I should have understood that. Unfortunately there's no indication it's adjustable; it's fixed at 0 (no slope) as you noted: https://legacy.cakewalk.com/Documentation?product=SONAR&language=3&help=ProChannel.06.html

I presume we're talking about recording audio from a mic or line input to one or both of the Tascam's analog inputs...? If you set the Input of an audio track to the appropriate channel(s) of the Tascam and arm the track to record, do you see signal in the track meter as you rehearse?

Not sure where you're getting "Currently is 0"; that doesn't even make sense. HP and LP shelves have Slope controls in dB/Octave; default is 12db, and min is 6dB. Regular bands have Q Factor in place of Slope.

Internal (a.k.a. PC Clock) can only work for pure MIDI projects that have no audio, plugins or even the audio metronome. If any of those are present in the project, Sonar is automatically going to switch the clock to Audio and use the sample clock of the Scarlett as it should. This is highly preferred. This is also a non-standard configuration when using a DAW. You should only connect the controller to the PC via USB MIDI and use tracks in the project to echo MIDI from the keyboard to the Integra via its USB-MIDI. Or you can connect one or the other to the PC via MIDI DIN ports on the Scarlett, but not both DIN and USB.

You need to dial in your record latency compensation. But even an entry-level ASIO interface will generally be off by no more than 30-50 samples right out of the box; half a beat points to a suboptimal interface and drivers, and probably not using ASIO.

Looks like you have Snap to Zero Crossings enabled.

Cakewalk Core subdirectory is for CbB. Sonar's default path is Cakewalk Content/Sonar/Project Templates. For years I have kept my own set of content subfolders directly under Cakewalk Content and pointed all versions to the same directories in preferences. This also allows me to modify factory presets/templates without changing their names and not have them overwritten by updates/re-installs. And new versions can access legacy content that no longer ships with the current release.

Used to be Edit > Interpolate, and I'm pretty sure it's been around since Cakewalk for DOS. EDIT: Just checked, and it had moved to the Process menu but was still 'Interpolate' in S7 which is the oldest installed version I have.

I've encountered that situaiton with velocity-switched samples. I generally use Process > Find/Change in that case.

Not sure how that would get into the MIDI clip; maybe you had a Melodyned clip inadvertently included in the selection when bouncing MIDI to clips at some point...? In any case, you should be able to just manually delete the Text event from the Event List.

Yes, I understand. I'm suggesting to use an actual CWP project file as a sort of enhanced track template to bring tracks into an existing project with MIDI/Audio content included as desired. It obviously has shortcomings, the main one being that the track output and send assignments in the 'template project' need to be compatible with the busing in the target project. Also dropping a project file into an existing project still has the slightly buggy behavior if creating a superfluous "Matrix" track and one additional audio track. Like most workarounds, it's an imperfect solution.

See the videos linked at the bottom of this post by John Vere for an analysis of the alternatives to the no-longer-included TTS-1 and no-longer supported GS Wavetable:

If you have 'Use ASIO Reported Latency' enabled under Preferences > Audio > Sync and Caching, that should largely be compensating for the input latency. There's always some additional unreported hardware/firmware latency that needs to be compensated by entering a value for Manual Offset, bbut this is usualoy on the order of only 30-50 samples - approximately a millisecond. Normally, I would recommend using the Centrance Latency Checker to find the actual RTL, but since your output and input devices are using different drivers, that's not going to work. First, make sure that your Record and Playback Timing Masters are referencing the correct drivers and note the ASIO Reported Latency in samples (sames as Total Roundtrip reported on the Driver Setting page). Then disable latency compensation temporarily and re-record playback of a clip with a single sharp transient - like a single Metronome click - with the mic right up against a monitor. Change the Now Time readout to samples and use the Now Cursor positioin to count the number of samples from the source transient to the uncompensated recorded transient; this is the Actual Round Trip Latency. Subtract the Reported RTL from that Actual RTL figure, and that's what you need to enter for Manual Offset in samples. Enter the offset, re-enable compensation, and try re-recording again.

It's not necessary to set Input channels or controller transmit channels, only the forced output channel ("C" widget in the track/inspector).

That's my go-to for a GM hardware synth.