David Baay

Is this referring to the Now Marker? Are you seeing this in more than one project? I can't repro anything like that. Set the Now Marker where you want to set Start or End markers (anywhere other than 1:01:000), right-click the Timeline and choose Set Project Start/End... So far as I know this is implemented internally and does not involve MCI. The Tranport controls honor these markers and they define the default range for bounce/export when nothing is selected.

Hi, that is also happening to me (the same issue)! As Promidi suggested, this sounds like either a locked screenset or possibly a Workspace being applied.

From your original post, I got the impression that the tracks were wildly out of sync or drifting apart over time. If there are just some small timing errors of individual notes, what you want to use is Process > Quantize (or Groove Quantize if you want to use one of the tracks as a reference for quantizing the others rather than quantizing everything towards the M:B:T grid).

That would have to be a bug if true. I cannot envision any project routing and/or combination of config settings that would allow a bus to continue receiving input from a disabled Send.

@bmarlowe If you're still having issues with freezing AD2, strip a copy of the project down to a single track and synth instance that won't freeze, and share it so we can investigate. If the problem goes away in the process of stripping it down, that might reveal the cause.

In that case, I would tend to suspect something related to Antivirus or other security features. Or are you maybe using a very large custom project template pre-populated with tracks and plugins...?

Probably, yes. And ideally, the drive where project and audio are stored should also be an SSD. Personally I do both: Global Audio is on an SSD separate from the O/S and I usually save projects early in the creation process before any audio files are imported/recorded/rendered.

The default location for Sonar drum maps is C:\Users\<username>\AppData\Roaming\Cakewalk\Sonar\Drum Maps (a.k.a. %appdata%\Cakewalk\Sonar\Drum Maps Personally I use a common Cakewalk Content folder for all versions, and have Folder Locations in each app's Preferences set to reference that path for all content.

I think you answered your own question. The fist save has to copy all the audio files to the new drive. Subsequent saves only have to save the project file. What you need to do is save the project to H: before importing/recording any audio. This will create a per-project Audio folder into which the audio files will be written as they're created. If you don't do that initial save, they first get placed in the Global Audio Folder (on C by default) from which they have to be copied to H:. Alternatively, you can go to File > Audio Data in preferences, and change the Global Audio Folder to be on H: so that the O/S only has to change the path reference to the per-project folder when you save it, and not physically write a new file to the disk.

Imported MIDI follows the tempo of the project; if the files have the same time signature, they should automaticaly sync unless they weren't recorded to a click. It's possible to roughly sync such tracks by changing the length of MIDI clips, but ideally you should get each of them in sync with the timeline at a common tempo in individual projects before bringing them together.

I think he's using the Instrument Track per Output option that CbB added a few years ago. This gives the best of both worlds. The only thing I can think of offhand that might prevent freezing in that case would be that one or more of the Instrument tracks is Archived.

Are you maybe talking about the Bandlab web app? Or maybe CW Next? In Sonar, the menu path is Insert > Soft Synth. After selecting an Instrument plugin, you get an Insert Soft Synth Options dialog. Or you can right-click in Tracks pane and choose Insert instrument which gets you an Add Track dialog with the Instrument tab selected that has an Instrument pick list at the top and an Input pick list under that.

Two things: - A new MIDI track will only default to an input other than None if you have Always Echo Current MIDI Track enabled in preferences. - If you have that enabled (or you enable it manually without explicitly selecting an Input first), and there are virtual MIDI OUTs in the project being presented by plugins, the input of a new MIDI track should default to All External Inputs, and not echo or record those virtual inputs. So, worst case, you might have a new track getting input from more than one hardware IN by default, but not automatically from virtual INs as well. If you can reproduce a scenario where a track's input gets set to 'All Inputs' by default without limiting it to External inputs, please share the exact steps.

The Notes field of Sonar is not a document; the project as a whole is the document, and it hasn't changed until you commit the edit. That said, I found that uncommitted edits to track/bus names and control values get committed when you click to close the project which sets the dirty flag and prompts to save. So on that basis I have to agree that it's a bit inconsistent that the Notes field doesn't do the same.

I would say this is working as designed, the same as anything else you type and don't commit by hitting Enter or OK. In this case since Enter would create a new line, you either have to click the OK at the bottom of the pane or click away to another part of the app as you discovered. Another method I often use to commit changes and give keystrokes back to the main app without having to touch the mouse is to hit Tab which moves focus to the Name field and then Esc.

In what context? The cursor for the Smart tool changes depending on what it's hovering over in the UI. Some of the Smart tool cursors do look a bit different than in CbB. I'm too used to it to recall which ones or exactly how they changed, but nothing too radical.

You can also set LinkPFSendMute=True in Config File to have Pre-Fader sends muted along with their source tracks. My guess is you had changed the send to Pre-fader and when you deleted/restored it you got a default Post-fader send that is subject to muting.

The resetting of the patch would have set the "dirty" flag on the project, prompting the re-save. Sorry you had to learn the hard way: Never re-save a project that doesn't sound right or is otherwise in a bad state; always Save As or Save Copy As with a new name. Ultimately, I think responsibility for this issue probably lies with T-Force as I do not recall a report of any other synth behaving this way in Sonar. Another possibility occurs to me: If the MIDI is from a third-party - not something you recorded/sequenced yourself- it may contain Controller/Program Change/RPN/NRPN messages that are causing the reset.

The Create page should show .CWT template files from which new projects can be started. By default these are located in C:\Cakewalk Content\Sonar\Project Templates If the default files are present, check Preferences > File > Folder Locations to verify the path set for Project Templates. If the files are missing I can share a copy of the default set for you to paste in, but that would suggest some larger issue with the installation process (maybe folder permissions) that needs troubleshooting. EDIT: What happens if you just hit Ctrl+N?

Removing/Restoring power, by a switch if it has one or by disconnecting power or data cable if it's USB-powered. Sometimes you can also just go into Device Manager and disable/re-enable the driver. It can often save the time/trouble of rebooting, especially when you're having a really chronic problem or deliberately reproducing a crash to troubleshoot.

I know of it, but not details of that model. I have an H1n from a couple years ago that I have used only a handful of times to record acoustic piano via the mics. And I experimented using it as an audio interface for recording directly into Sonar just to see how that worked. It's been a while but I recall that it worked that way as well but not in a way that allowed input monitoring. Long-term you will want to look into getting a basic ASIO audio interface with built-in preamps and a mic or two to get the most our of Sonar and not be messing around with file transfers and syncing the project to audio recorded without a click. P.S. If you want to share the two original files from the H2n for download somewhere (or zip up the project folder with the two left-channel tracks already imported), I could set up the two mono tracks in a project with the stereoizer setup configured for you to experiment with.

Each track has an 'A' button to archive the track that basically tells Sonar not to process it when enabled. If you don't see them, set the Track Control Manager at the top of the track pane to 'All". It can be turned off an on any time the transport is not rolling with no permanent effect. What I'm thinking is that this will cause any initializaitonto be skipped for that track on opening the project which might help determine the cause of T-Force losing its patch settings.

The input to the H4n is probably stereo, but if you're going direct in with a cable from an electric guitar, that's going to be mono, and recorded on the left side of a stereo file. Sonar would import that as a stereo track by default, and the sound would be only in the left channel throughout the production unless you change the Interleave on the track to mono which would put it in the center, but you still woudn't be able to control the Pan position. The better way to handle this is to bounce the stereo track to Split Mono (see Tracks > Bounce to Track(s) options) and delete the flatline track from the right side. All mono tracks will continue to sound mono through a stereo bus unless processed by FX that specifically create a stereo image with differing left and right-channel information. Here is one technique for "stereoizing" a mono track that was recently re-surfaced: The alternative would be to record from the H4n's stereo mics near an amplifier(assuming both electric bass and guitar) in a room that isn't too lively. Or double-track the mono recordings, reproducing the timing and articulation as closely s possible (i.e. playing along with playback of the original tracks) and pan one left and one right. It might also be possilbe to just use the H4n as a pair of mics with a preamp to be recorded directly in a stereo track in Sonar via whatever you're using as an audio interface.

Copy and delete as Chaps suggested is one way. You can easily select all notes of a specific note number(s) to be deleted by clicking/dragging in the keyboard/note names pane at the left of the Piano Roll View. You can also do a partial selection of the MIDI clip by this method, and then Shift-drag from the source clip to a new MIDI/Instrument track in the track view. Shift ensures the timing is constrained.

Sounds like maybe a plugin on the Master bus has gone into demo mode due to the trial period or license expiring. Not sure what you mean by "freeze one card at a time".