David Baay

Kontakt: hey quad core, hot enuf 4 u? Quad Core: funny, how about I crash u?

I think it has always been the case that giving focus to a track in the Notes pane causes drum-mapped notes to disappear rather than be ghosted because the PRV depends on track focus to 'know' that a drum map should be applied (and which one if there's more than one in the project). Pretty sure I've reported this in the distant past. The mystery to me is how the OP got the first screenshot as the PRV track selector shows only the Strings track selected.

I have to say I find the synth-instance-per-kit-piece setup to be really pointlessly complex and time-consuming to manage with pretty much no benefit except that they can be frozen independently which has pretty minimal utility itself. But, if nothing else, the one thing you really should do is create a single custom drum map that routes the relevant note numbers for each track to its respective synth instance, including the SI Drum instances. Aside from being able to see drum names in the PRV Drum Pane, this is one of the key purposes of using a drum map. With a separate map for each track, you can only see one track's notes in the Drum Pane at a time. If you use a single map, you can see and edit the hits for all the kit pieces together.

Let's start with basic machine specs, O/S version and the symptoms of failure. And has any other version of SONAR/CbB ever been installed on this machine or is currently installed and working?

Hmmm... that's not what I'm seeing. and as i said, you can't create an Instrument track from a MIDI track pointing to a drum map so I think you must have added the maps via the Inspector after creating the Instrument track... no? In any case, as it stands now, if you want to use drum maps and have freezing work seamlessly, you pretty much need to keep the MIDI and Synth audio tracks separate. There are a various ways to use folders to help manage that.

Oops, missed that. Yes, and it's immediately apparent that the issue is due to adding a drum map to the Instrument track. By definition, a Simple Instrument track consists of MIDI and Synth Audio tracks with I/O ports referencing the same synth. The drum map breaks that association and the freeze button in the MIDI track is grayed out as Sonar no longer sees the connection between the two. You can add a drum map to a simple instrument track using the Output widget on the MIDI tab of the Inspectr, but you can't re-make it once you split it except by Undo. I'm thinking this might be easily resolved by having Simple Instrument tracks link the Freeze button to the audio side instead of the MIDI side.

Interesting, but should not be necessary. I'd still be interested in seeing the stripped project.

I can't get Sonar to show more than one instance of a synth in the Recent list. It may well be a bug in CbB that's been fixed.

Freezing freezes the entire synth; it's not possible to freeze individual outputs. If you split the Instrument track you can 'bounce in place' by executing Bounce to Track(s), specifying the synth audio output track as the target for the bounce, and then mute the MIDI, but that gets awkward and doesn't really accomplish anything vs. just leaving the track playing "live". The synth is still live for the rest of the tracks so you're not conserving resources. I would just leave it all live until you're ready to freeze the whole thing.

Since it's just MIDI with a soft synth, the .CWP project file is enough and should be small enough to post here on the forum. Or you can PM me a copy.

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.