scook

I remember the threads very well. There is no amount of hand waving that can dismiss the fact that some benefit from an offset. If one wants clips to line up properly, it is a good idea to test and apply any offset as needed regardless of driver mode or sample rate. My current setup using a RME Babyface Pro running at 44.1K sample rate requires a -20 sample offset in ASIO driver mode to achieve this level of alignment

X-Ray is an old feature designed for dealing with plug-ins in the XP era. This FR appears like a refinement of While waiting for either feature the inline PRV (albeit not nearly as convenient as the full PRV) is a way to view and edit both audio and MIDI data on the same timeline with a common Aim Assist and Now line.

I suppose this may be read several ways but it is not the case that all ASIO drivers accurately report latency. If ASIO drivers were always accurate there would be no manual offset provision when running ASIO driver mode. Some ASIO drivers may not require an offset. In some cases, the offset may be very small.

AFAIK, "Remove DC Offset During Record" is off by default.

Note hot spots are hard coded too. See the documentation linked above. Of course, BandLab owns the source code and may modify it as they see fit. Even in the context of this forum, it is difficult to tell in some posts if one is asking "does a feature exist" or "could a feature be added." Generally when I post in this area, I post about existing features and how they work hence the links to the documentation.

Why Steve? Can't we add a function to Shift+Alt+Mouse Move for instance, if ALt+Mouse Move function is not possible? It seems nothing doing different in PRV with Shift+Alt combination with the Smart Tool. I mean it seems available. My post concerns what is available within the program itself, the scope of this forum. Clip hot spots and smart tool bindings are hard coded. The smart tool is not in the keyboard shortcuts area drop down in preferences.

When documented features appear to be missing, review the Workspace setting. Change the setting to a different workspace, create a custom workspace or set it to None.

Process > Apply Effects > Audio Effects does this

Currently, the functions supplied by the smart tool may be altered the hot spots and key combinations bound to the functions cannot.

The audio buffer setting is one source.. Plug-ins are the other. In order to keep all audio in sync, a delay is added based on the track or bus reporting the largest Plug-in Delay Compensation. To see if plug-ins are the problem, bypass all plug-ins using the FX button in the Mix Module. Of course, this will also bypass ampsims but typically they are designed for real time playback so can be ruled out as the cause of the problem. Bypassing all effects is the first step in isolating the offending plug-in chain. If the delay disappears when plug-ins are bypassed, the delay is plug-in related. If plug-ins are the problem, re-enable all plug-ins and bypass individual FX racks and ProChannels to determine the offending plug-ins. Usually the largest sources of plug-in delay compensation are dynamics processors with look-ahead buffers and impulse response based reverbs. Often these plug-ins document the PDC added by their use. Either temporarily delete or replace the plug-ins. Freezing or bouncing and archiving works too. It is possible to override PDC on the recording track by using the PDC button in the Mix module.

The delay experienced when monitoring through the DAW has two sources the user has control over: The buffers used by the audio driver. The buffers used by the plug-ins. Smaller audio buffers result in smaller delays. While recording avoid plug-ins designed for mixing and mastering.

Don't recall this every being reported. The program folder paths are hard coded in the plug-ins. Are the program folders compressed?

If Remove DC Offset During Record is enabled, try recording with the option turned off

Try reduced CPU mode

Generic drivers can be a problem any time a factory driver is present. Many of these drivers are repacked versions of ASIO4All. None of them are true ASIO drivers. They are all software wrappers for other Windows audio drivers. Cakewalk reads HKEY_LOCAL_MACHINE\SOFTWARE\ASIO from the registry to find out which drivers are installed. There should be at most one ASIO driver for each audio interface.

Yes. In fact, I rely on the ability to start the transport with no data in the tracks and without record being enabled. This is why I keep "Always Stop At Project End" turned off. The spacebar

Yeah, the current solution is use a pitch plug-in (I use zPlane Elastique Pitch) or throw the clips into a sampler. To me this is a special case of the built-in sampler FRs.

There is no "end marker" for audio or MIDI Cakewalk plays until the last bit of data is reached regardless of the "Stop At Project End" setting. If "Stop At Project End" is not set Cakewalk continues past the last bit of data. Sometimes projects appear to play past the end due to an automation node or some sliver of data beyond the "end." Usually, this "play past end" problem is fixed by selecting everything right of the "end" then using ripple edit to the delete the selection. I recall a report about projects created with an old template having this problem too. This was not fixed by deleting unwanted data. In that case, the fix was building a new template.

It depends on the routing and the volume and pan control in question. There are a couple of ways to use a single MIDI track and route the data to multiple synths. In this case, MIDI volume and pan may be shared. However if each instrument has its own instrument or audio+MIDI track pair and plug-in then nothing is shared.

Please do not cross post

Based on the track icons Track 1 is not an aux track (in the way Cakewalk uses aux tracks), it is a synth audio track, Its input is the audio from a synth plug-in. Aux tracks receive their audio from other audio tracks. Track 2 is an instrument track Track 3 is a MIDI track WRT routing image showing Tracks 3 > Track 2 > Track 1 with track 2 muted Track 3 is routed to a synth according to the image Track 2 has no output routing Track 1 has its input set to a synth and its output goes to the Master bus. IOW, it appears track 2 has nothing to do with track 1.

All SI instrument plug-ins have a single stereo output Of course one may have multiple instances of the plug-ins.

While most of the theme changes made in response to CbB updates are optional; when an image size changes an update is required or features may break or become unavailable. The changes made in 2020.04 and 2021.1 fall into the mandatory category. Staying with an old theme is fine as long as one is willing to either make the updates themselves or accept the program may not work as expected.

That must be it, I did get much game coding in college