Jonathan Sasor

@marled Can you send us a copy of your project to look at? A lot of AudioSnap stuff is very material-dependent, so if we had a concrete example where you're seeing your project go wrong, that'd be very helpful. Thanks!

I'm currently not able to reproduce this issue. Can you upload a project where you're seeing this happen?

Can you elaborate on this? Are the track/clip states changing? Is the change only audible in the render?

Hi @GreenLight, I was able to reproduce your issue, so I went ahead and logged it, so it's in our system for when we have a chance to look at it. Thanks!

@Guillermo Diaz Can you get us a dump file for when it's stuck on the splash page? You can find details on how to do that here:

That's simply talking about the images for your audio. What you see in your clips are the "wave pictures" that the app draws, then it caches then so it doesn't have to redraw when it doesn't need to.

Hi Kenny, Based on your dump files, it looks like your crashes are originating within SpectraLayers itself. Unfortunately I can't get a repro with SpectraLayers 7 on my end to troubleshoot this further. Your best option is probably to contact Steinberg directly.

You just need to bear in mind your signal/monitoring chain. Enabling Input Echo on the track allows you to hear your signal as it's running through the track/audio engine in real time. The recorded signal will always be the dry original input from the device, it's just routed through your project in real time. Just make sure you have your direct monitoring through your audio card also disabled otherwise you will hear both the direct monitoring and your signal in Cakewalk. Direct monitoring is set up through your audio card, but is always before the signal gets to the DAW.

The SONAR Mac prototype was discontinued, but was working, albeit in a limited capacity when compared to the standard Windows version. It was working well in and of itself at the time we were experimenting with it, however it lacks the ability to work with external AU/VST plugins. I can't say that I've tried it with more recent MacOS updates though. The Mix Editor in BandLab is an entirely different animal as it's a much broader cross platform app and ties in directly with BandLab's social/collaborative network. Cakewalk by BandLab is the continued development from the SONAR platform and runs on Windows.

They're a convenience thing. Some people prefer mapping parameters to something tactile. They're also useful if you like manually automating stuff, but on the whole they're 100% not essential to a DAW setup. On my VS-700, I'd say probably 90% of what I use on it are the transport/jog wheel and the save/undo functions. But everyone's mileage varies.

Ah come on, the Custom Control Bar module has only been there since SONAR Platinum... you're talking like 5 years max! ?

This is working normally for me, have you tried it with different projects? Try creating a new simple one with just audio and see if there's any difference.

We stopped officially supporting Windows 7 after Microsoft themselves dropped Windows 7 support. That said, we do not block install for Win 7, we notify you that we're not specifically testing against Windows 7. The app should generally be okay, but we just don't make any guarantees.

If you can upload examples where the algorithm isn't working we can pass this along to zplane.

A dedicated audio interface is really the best solution, but if you're having trouble with WASAPI, integrated audio cards should be able to play back with the MME driver mode.

Just to reiterate the points made already, you typically would not record the output of a plugin within the DAW like that. You can in Cakewalk if you have the output from a different track routed to an aux track as scook mentioned, but generally this is just creating additional work for yourself. The standard workflow would be to record with Bias (or any other amp sim/plugin) running on the track that you're recording to, with the audio being processed by the plugin in real time. To listen to the audio being recorded in SONAR/Cakewalk, you enable the Input Echo button on the track. This then means you're recording the dry signal, but hearing the processed one, which means you could always change the sound in the plugin if you need to too. Just watch out if you have monitoring enabled on your interface as well, otherwise you'll hear both the effected sound being routed through your track, and the dry "direct monitoring" coming through the interface.

We generally will do localization a few times a year rather than per update. This will ultimately get translated in the next round.

Yeah, I mean, simply recording multitrack audio is pretty easy on systems these days. The processing becomes more of an issue when you start loading down plugins, but that's also very dependent on what plugins and how many you're using. You could certainly accomplish a lot with the stock plugins included with Cakewalk, which are not super CPU intensive.

The gain knob on the track strip is for the playback gain in Cakewalk. For instance if you recorded something with a low signal from your interface and then want to change how hot that signal goes into your plugins in the rack, the gain knob is before the FX bin in the signal flow. As mentioned, this is distinct from the record level though. Cakewalk (or any host) receives a signal from the selected audio input driver. That level is then set from the hardware device, be it from a software mixer panel or a physical knob on the device.

Essentially this boils down to what you have set for your inputs and where your signal flow is going. Look at what you have for your inputs and how that's receiving signal. if you're using a Steinberg interface, make sure you have Cakewalk set to use the proper ASIO driver for it in the Preferences.

the percentages are based on the clip length. Make the 2 clips identical in length and they should compress size (speed up) at the same rate.

About a year ago we actually did a couple tweaks for loading older .wrk files in CbB, so that should all work just fine on a Win 10 system in x64. So either opening directly, or Mark's way to grab in newer features from the go are valid options.

Also a valid point. I can't reproduce a crash on my end, but based on how Aux tracks are designed, trying to freeze them is a somewhat odd workflow. The whole point of an aux track is to have a live input like a bus, but in the track pane. This allows recording, or you could also do a Bounce to Tracks to get a similar effect. If your CPU is starting to get eaten up, you could put TH3 on the individual tracks then freeze those separately, or you could record the aux track, then disable the input and the FX on it. You'll need to consider how the signal flow is to ultimately get what you need. The app shouldn't crash in any case, so if there's any kind of dump or reproducible scenario that we can look into, we're definitely interested in looking into that. It might be useful if you uploaded a copy of the project to that end if you can't get a dump file.

Is the .exe still visible in Task Manager when it crashes? You can generate a dump file from there if so.

I've done a bunch of testing with Spitfire's BBC Symphony Orchestra without issue, so there shouldn't be any major issues with the plug. If you're seeing a crash, please send us a dump file, and we'll take a look. Do bear in mind it is rather resource intensive plugin since it's loading a rather large library, but it works normally on my end.