Noel Borthwick

So I tried this out with VEPro and I can see that you cant start the Cakewalk transport from within VEP. However it also does not work in the 26.04.0.151 release. So this is NOT a regression. I'm not sure why it seems to work for you. I'm using an older build of VEPro 7.0 demo server so maybe we aren't running the same version. In fact even pressing the transport in the server doesn't start playback in CbB so this is not related to the spacebar. I'll see if I can find out what the plugin is relying on to start the transport in the host. In any case this doesnt seem to be a bug but some missing communication.

Type 1 MIDI files are multi track files. Type 0 are single track. To convert you will have to split channels to tracks. This can be done using a CAL script. See C:\Cakewalk Content\Cakewalk Core\CAL Scripts\Split Channel to Tracks.cal I've attached the file below if you cant find it. Split Channel to Tracks.cal

@Vyacheslav Thanks for the video. So let me verify whether I understand what you are doing: You open a plugin window from within the VEPro window When that plugin window has the focus you press space bar and the spacebar does not start the transport in CbB Is this correct? In your video you have not enabled the "give all keystrokes to plugin" button in the main VEP plugin window. Does it make a difference if that button is enabled? Also to clarify - the video you posted is with it working properly correct? BTW we had a case for this already logged. Unfortunately it did not get investigated in this release. I will escalate it and we'll address it since it appears to be a regression.

I’m having trouble understanding the exact problem since there seem to be conflicting reports. Are you trying to start playback from within the VEP window and is this the plugin version or the standalone version runnng on a different PC? i.e when it says “start and stop your playback from within Vienna Ensemble PRO” are you referring to an instance running within Cakewalk or external to Cakewalk. It may be helpful if you post a video so we can see what you are doing. We normally intercept the spacebar and it should start the transport. PS: binary thinking like it works in x/y/z but not cakewalk is not useful for diagnosing problems so lets focus on trying to find out what is happening. The problem could be in Cakewalk or could be in the plugin until we find out what the issue actually is.

You are conflating different issues. The BandLab assistant issue is not the same as the one where error 12175 is reported from within Cakewalk. That is a Win 7 specific problem. The BL assistant issue is different. As mentioned we're planning on deprecating that tool and provided a link to an alternate installer for new users.

Please report this to the PC vendor you got your computer from. Until they fix these buggy drivers from Realtek users will continue to have problems.

Yes in WASAPI shared we disallow multiple interfaces because recording from multiple devices would be very complex to synchronize. In WASAPI shared mode the device returns variable size buffers so handling them and synchronizing them across multiple devices would be difficult to do. Its more deterministic and fixed size in WASAPI exclusive so we allow it there. WASAPI shared mode is quite complex because you are really reading and writing data that has is processed by the Windows audio engine additionally, unlike exclusive mode where the app is directly communicating with the driver (similar to ASIO). This is how audio output from Cakewalk output can be mixed with other application streams in Windows (via the Windows audio engine)

Most users did not want that because the port field is too small so I suppressed it. If you want numbers there use friendly names where you can enter whatever you want.

It depends on the manufacturer. Some allow running two interfaces of the same kind and aggregate the I/Os via the ASIO driver. Presonus allows it with some of their devices. MOTU, RME, LYNX all do.

Until Microsoft drops support and it stops working yes Similar to Win 7.

No that looks like a bug in the program you are working with not properly understanding the Wavformat extensible format. I don't think this has anything to do with our export. Choosing Wav(microsoft) is simply choosing the libsndfile wave file writer rather than Cakewalk's built in one. There is probably some difference in the format that is confusing your encoder. I would log an issue with their support to find out why it fails.

post some screenshots of how you have set up the track inputs and your audio preferences settings. Also what driver mode are you using and what audio interface.

This is a win 7 issue. See this thread. Note that win7 isn't supported

Well I think a better adjective is workflow rather than old school Those programs are built for different primary use cases rather than production. Cakewalk has deep midi editing tools and now articulation support that those programs don't have. And our console view is one of the better implementations depending on your perspectives of course. Look and feel aesthetics vary a lot and we will continue to update our UI. Cakewalk is a program that has roots 30 years ago so there are bound to be some elements that are legacy but that isn't always a bad thing for reasons that you state. PS: try going to Europe and telling people that their architecture is old school lol.

That is very strange. Can you please attach the reduced project that crashes so we can double check this?

Curious what aspect feels old school to you and what you are comparing it to.

2021.06 Update 1 has been released

Realtek ASIO has bugs that are known to cause symptoms like what you saw. I would uninstall that driver.

Thanks for your feedback. In friendly names mode you can now also name the left, right and stereo components independently for completely control over the names.

Its an old bug. The same thing happens in SONAR. We'll look into improving it.

@Heinz HupferWhen you say it crashes without error does the program exit? If so that is likely heap corruption from a plugin. Have you tried setting the ExceptionHandlingSeverity to 5 or 7 to see if you get an error dialog?

Bus waveform preview is completely different from the clip waveforms so it doesn't show clip outlines there. Its not a bug but we can consider doing it for consistency in the future.

@paul terry, please attach the dump file created by the crash reporting (its listed in the crash dialog). That is the only way for us to analyze crashes.

@Brian Lawler I verified that it is related to a fix I made in 06. There were cases where some windows messages were being skipped by certain UI controls that could cause unexpected UI behavior in some plugins. The spin control used for changing tempos was one of them that had the bug. >>Also- the data does not send on mouse up for me- I have to click somewhere outside the tempo window (Win Pro 21H1) That part is expected, only when you press enter or click away from the control is the new value committed. It's normal behavior for a spin control.

Which version were you using before you updated? The slider always send data at the end (on mouse up) but there was a a bug fix for something else in the UI that may have caused an unwanted plugin interaction.