reginaldStjohn

Have you taken any time to look at the Reference Guide or online manual? They offer some good getting started tutorials. Your problem most likely has to do with using your onboard audio and the driver mode that you have selected. ASIO only allows one application to have the driver open.

Make sure you are not in "Offset" mode. This mode applies an offset to what is already set on the fader's or automation. That's my only idea.

Are you talking about rendering the mix to an audio file? Sounds like something is being a bottle neck. Maybe try disabling a synth at a time to see if one of them is what is making it take so long. Another option, create a new project and move the midi and audio tracks over and try rendering in the new project.

It means one of your busses or tracks is routed to a hardware output that doesn't exist. Check the path Nigel Mackay specified and make sure all your tracks and busses are routed to a valid output

How about this as a start? https://help.cakewalk.com/hc/en-us/articles/360034169474-Connect-a-MIDI-Control-Surface

There may be a setting to adjust that, however, that is what takes lanes where meant for mostly, selecting a single take from a selection of takes to composite together a single track. In the future you may be better off recording to different tracks if you want all of them to play. With that being said, there may be a way to have all the takes active. Maybe look through the Reference Manual in the Comping section.

Have a look at this thread. Might be related.

Good question. I would say "no" but will defer to someone with more knowledge

If you disable audio snap does the waveform come back? I have never had it do this.

I think that you have figured out how it works. On your first snapshot it will set the whole automation envelope to that first value since it is the only data that the track knows about. Then you need to take snapshots or add automation nodes in other places if you want the value to be different. As for the documentation, it seems correct but was not clear enough for what you were expecting.

Seems like a pretty minimal update unless the "Recorder" window is of interest.

Does the audio engine report a dropout code? Have you run the program latencymon.exe to see if your system has any issues?

Sometimes even user error reporting is useful for those who make the same error.

Here is a past post that had a similar issue. You may find it useful.

I don't think that is possible right now. But you could look in the Reference manual to be certain. If it doesn't exist you can add a feature request here.