msmcleod

Only with heavy compression, as an "after the fact" parallel compression technique - worked pretty well to be honest.

FYI - the new Sonar has a new Track Manager button on both the Track View and Console View, which: 1. Allows quick access to your per-project Track Manager presets - i.e. they're listed in a drop-down menu 2. Can toggle the hidden state of all tracks 3. Gives a clear indicator as to whether any tracks are hidden 4. Allows you to quickly toggle the TV/CV sync state without having to open the track manager We can take a look at the PRV anomalies - it sounds like there's some weird conflict going on between PRV filters and the track hidden state. A more enhanced version of the Track Manager is likely on the cards at some point in the future - we started initial discussions, but has not been fully designed or scheduled yet.

It's not clear exactly what you want to use the nanopad for? I've got one, and I've used it for a couple of uses: as a drum trigger (which to be honest, wasn't that good compared to my old Alesis SR-16 - the pads just weren't as responsive), and also for triggering cells in the matrix view. Perhaps if you elaborate on what you intend to use it for, we can point you in the right direction?

Variants of the AI code can be found on git-hub (i.e. it's free), and I'm pretty sure a bunch of commercial implementations are based on this, only differing in the training data they've used. I've not seen the BandLab code however, so I can't speak for that. There are some extremely useful applications of this technology, depending on how you've trained it. For example: - Being able to split up drums when you've only recorded with 2 or 3 mics - Removing/reducing bleed from other drums... in fact removing/reducing bleed from any recording. - Being able to tweak the balance of instruments - Splitting chords into separate notes I've not personally seen any examples that are specifically trained in drums so far, but it's certainly do-able using the technology. I'd be surprised if it doesn't already exist though. The only downside is the artefacts that are pretty much always present in the results to some extent. For remixing, this is normally not an issue as when the stems are re-combined, they blend almost seamlessly. Tracks in isolation however might need some treatment. When I've played around with this, I've found the best results are when you combine the separated stems with the original, using a separated stem to boost/reinforce the original part. Keeping the separated stem at a fairly low level is enough to give that part a volume boost over the original without any artefacts becoming obvious.

This is how I normally do it.

Everything you've asked for can be done already in the screenset control bar module.

BandLab does indeed have the Splitter tool, which will split a stereo mix into separate bass, drums, vocals etc. I believe Cakewalk Next will have this feature too. I'm not sure if the new Sonar will have this feature on day one of release, but I AFAIK it's in the pipeline.

As far as I can tell, the PRV will hide the track if it's hidden the Track View - at least that's what I'm seeing.

Bounce to Clip, Bounce to Track and Audio Export all use the same code behind the scenes. They're all creating clean audio files. Of course with the bounce commands, you still have the old clip objects in memory and the old clips' audio on disk to support Undo, so until you either clear the undo history (or reload the project), they'll still be taking up resources.

It depends. If it's an audio clip, and it's doing real-time stretching, then yes. It'll also likely not sound as good, as the real-time stretching algorithms prefer speed over quality. For MIDI clips or audio clips that aren't being stretched, the difference will be negligible. It also depends what you mean by resources... if you mean CPU, then the above is true. If you mean disk-space / memory, then bouncing it will actually increase disk-space or memory usage.

Simply put, this shouldn't happen. The rules are: - The envelope shapes are stored in start time order - The time base for each shape can be either in musical time or in sample time, but the time base must be the same for a single envelope stream. - The end of one shape cannot be after the beginning of the next one. Somehow one or more of these rules is being broken... finding out why / where is the tricky part. It would be useful to know if there are tempo changes in your project, and you have a sample-time based envelope. There is logic to update all sample-times within a project when the tempo map is altered (which is why editing the tempo track envelope is slower than other envelopes). I don't think there is anything fundamentally wrong with the logic here, but it's a possibility. It's more likely a bug in the envelope editor code itself.

It's worth mentioning that the new Sonar will have a completely new set of icons, and will be in a completely different format (i.e. they're vector based) So if you're planning on moving to Sonar once it's out, I wouldn't spend too much time getting the icons from CbB. It may be easier to just do a screen capture and cut out the icons you need.

@pulsewalk - yes, this looks like an envelope bug. We've seen this from time to time, but unfortunately it's almost impossible to reproduce. If you can get an envelope in a project in the state before this happens, with a reliable recipe for editing it to get it into that state afterwards, then please let us know. The only thing you can do is edit the envelope to put it back to a sensible state.

The most common reason for this is that the encoder can't write to the file, either because it's on a read-only drive, or something else has got it open.

At the moment, Articulations aren't applied to real-time MIDI input. This is something we can look at for the new Sonar, but even if we did, it would only apply to Transforms (i.e. the "Transform Existing MIDI Events" section), and not Triggers (the "Generate New MIDI Events" section). It would apply to any "active" articulations at the Now Time. This shouldn't be a huge issue, as clicking the articulation will fire off any triggers in any case. It's likely this would have to be an "opt-in" for each track via Track Properties.

C:\Program Files\Cakewalk\Cakewalk Core\TungstenTheme.fth is essentially a resource dll. It contains all of the graphics used by CbB.

If you don't want to separate out your tracks, another way of doing this, is to put all of your processing in separate sets of verse/chorus buses. You can then automate the bus sends for each track to send to the appropriate bus for when it's a verse or chorus.

We changed sign-in to launch the browser, as too many people were having issues with the WebView2 component at the time. I can't recall exactly when this was, but I think it was some time mid 2022.

I'm pretty sure this is not the case. WebView2 isn't used for testing the internet connection, nor is it used for activation. It's also not used for authentication - hence why it launches a browser. The only time WebView2 is used is when a web-page is shown inside the application - if it's not there, it'll fall back to IE... the content may not display properly, but at least in CbB it shouldn't cause any major issues. Cakewalk uses sockets to connect to bandlab.com behind the scenes for both testing the connection and activation. If Cakewalk can't connect to bandlab.com or establish a session to the BandLab authentication API, you'll get the "Unable to connect. Check internet connection" message. At this point, it'll not even launch a browser for you to login. The issue is almost certainly one or more of these issues: 1. Something is blocking Cakewalk from connecting to the internet 2. Something is blocking access to bandlab.com 3. Particularly slow access to bandlab.com is causing it to time-out and fail the connection 4. Security updates are missing from Windows 7 (e.g. at the SSL/TLS/Certificate authentication level), which is preventing a BandLab API session from being initiated. It may be the case that having Edge installed will solve issue 4, but I'm pretty sure there were other security updates that were pushed out just before Windows 7's EOL, that updated some of these.

@pulsewalk - if you're using all the default options, it should be as simple as selecting the tracks, opening the Bounce to Track(s) dialog, and clicking OK. There might be some additional checks you need to do if you've got more than one hardware output, but here's an overview:

Velocity is a property of the note events themselves - there is no way to automate them. Expression ( MIDI CC#11 ) is probably the closest thing to it, assuming it's been implemented by the VSTi as it was originally intended. What CC11 should do is scale what the velocity comes out as - so at 127, a note with velocity 127 will sound at full volume. If expression is at 64, then a note with a velocity of 127 should sound as if it was played with velocity 64; notes with a velocity of 64 should sound as if they were played at 32 etc.

My recommendations: 1. Try to identify chapters etc with Arranger Sections. You can have more than one arranger track, so you could have one track for broader sections, then another arranger track with more granular sections. You can use the Arranger Inspector for navigation to jump directly to the section within the timeline. 2. Use the scrub tool to audition at a more granular level. To do this, hold down the "J" key, then click on the waveform. While holding down both the left mouse button and the J key, moving the mouse to the left will play forwards through the clip; moving to the right will play backwards.

@RexRed, @Noel Borthwick may be able to correct me here, but I'm not sure a complete fix is possible with Melodyne's current ARA interface. As I see it there are two things we could do here: Automatically bypass the Region FX for that clip when it's muted - you'll still see the blobs, but they'll be shown as muted within Melodyne (they'll have a gray fill); or Remove the Region FX for that clip when it's muted. The blobs will not be shown, but you'll also lose any edits. My gut feel tells me option 1 is the correct solution, however I can't find any way in Melodyne to get it to hide bypassed regions within the editor. Without that, you'll still get blobs overlaid on top of each other when you add the new take - although at least you'll kind of be able to see which ones are muted. So whilst we could go some way to solving the issue, Celemony would need to implement a "hide bypassed notes/regions" option within Melodyne for it to work how you want.

First of all, BandLab assistant will not work with the new authentication servers. The only thing you can do is try to work out why Cakewalk can't see the internet. Something must be blocking it. Ensure there are no 3rd party firewalls or virus checkers, anti-malware etc blocking Cakewalk. Double check your firewall rules (even if the firewall is switched off).

This is what activation should look like in Windows 7. I've got Firefox set as my default browser. Cakewalk was upgraded to 2023.09 from 2022.11: