Noel Borthwick

To clarify, I meant that Workspaces save the same DATA that a given screenset saves. However the workspace wont save the set of screensets themselves. Screensets are intended to record per project view configurations. Workspaces are wider and only store settings and view configurations at a global level. In the 2020.05 release we fixed some problems where screensets and workspaces were affecting certain global settings, causing problems. No. Screensets have a different function in that they allow you to store 10 view snapshots at the project level. So you can have different view layouts zoomed in views etc, customized to that specific project. Edit: That said, a workspace with all of the checkboxes turned off apart from "View Layout" can is essentually a screenset. So you could save multiple "screensets" this way as workspaces.

Tempo is already being transferred. In the future we will do automation and MIDI as well obviously. This is the data currently being transferred: Project appId appName projName title author copyright keywords description bpm signature (time signature) metronome Track: id order type name color volume pan isMuted isSolo Regions: file fileHash startPosition endPosition

Thanks for your feedback. We plan on improving this workflow. We'll look into transferring the project info as well. Track comments and markers are not available in BandLab so this isn't something that is planned.

The bug that they apparently fixed in 1.0.3 was due to faulty processing of calls from the host in response to parameter changes sent to the plugin.

Are you running the original 04 release or the latest early access build? What is your thread scheduling model set to?

What version of cbb are you running? Can you share the project?

He's talking about the early access 2 release. It's not officially released yet. I'm not sure I follow. If you get a dropout there is always a toast message displayed telling you that.

Putting melodyne as a clip effect would certainly cause doubling of audio because its playing the clip audio as well as Melodyne. Its not intended to be used that way unless you like doubled audio

Its already in the early access 2 build.

I'm not sure why the GPU spike would affect Cakewalk's engine but one thing you can try is raise the value of DropoutMsec in the settings you listed above to something like 200-300. While that seems high it may get you past the fallout from the spike. You want to try and diagnose what is causing that however, esp if nothing much is happening in Cakewalk at the time.

Thats interesting. Do you see the same dropout even when not using Kontakt? It could be something interfering with Kontakt Cakewalk doesn't directly utilize the GPU so I wouldn't expect it to be affected but if a plugin depends on it its possible that it could trigger a dropout.

You can also add clip effects from the clip inspector on the left.

? Of course MIDI was invented by Apple right?

So by extension if someone decided to arbitrarily name .wav file .wave we should support it right and it's a "bug"that we don't? ? Well verify if this is indeed coming from established Mac apps

The MIDI specification doesn't list .midi as a valid extension. Standard MIDI Files ("SMF" or *.mid files) https://www.midi.org/articles-old/about-midi-part-4-midi-files

Where are you getting .midi files from? the standard extension is .mid not .midi. And CbB sees .mid files fine in the file open dialog if you pick "files of type MIDI"

Ha then I bet they are not using the low latency size at all

Seeking to a different offset is not quite the same thing as actually trimming the vide because that is implemented at the video engine level and is reflected in video exports, looping, etc. Also you can relocate the trimmed video anywhere on the timeline and the thumbnails will show the correct video frames. If all we did was seek to a different frame this wouldn't happen automatically. Media foundation is rather complex - all the video playback is handled internally in the MF engine. The host sets up a video track with the clips and trim points and then all the playback is handled by the engine which we slave to our audio engine clock. The bug with trimming is Media foundation hangs whenever we set trim points. I had a lengthy thread with MS years ago and they were unable to figure it out at the time. I don't think they have many people who even know this stuff there! They seem to spend more time changing sdk's then actually fixing the stuff that has been broken forever. I'll follow up again and see how it goes

Our video support isn't the best, but I don't fully agree that not having an offset makes it unusable for use with film scoring, since there are options to make it work. I do a lot of video work myself and its a simple task to export a video from any video editing application that is aligned with the music in Cakewalk. From that point on there is no need to offset the video in Cakewalk. We've explored many options with video and have yet to find something that works across the board. Sadly video at least for desktop apps is one area that Windows is sorely lacking and Microsoft has yet to address it cohesively. This shouldn't be an area where companies have to reinvent the wheel. Video is enormously complex to implement from scratch and even worse to support with the moving targets of video formats. We have considered using FFMpeg and may try and revisit that - it is also not a panacea for everything since it requires a lot of integration work.

Right because directshow doesn't support mp4 out of box on windows. So catch 22. Video support on windows is problematic unless you roll your own video support. Something we don't have the time or resources to do. Well loop back at some time and try and work with Microsoft on solving the MF issues which is really the only option available at this time.

Quicktime video definitely works in Cakewalk using the Media Foundation engine in Windows 10. See image where I am running a QT video in the latest release. Keep in mind that the MOV extension is just a container for a video format so just looking at the file extension doesn't mean anything. If stock Windows can play the video then Cakewalk, should be able to load it since we rely on Media Foundation for all our video support. For it to be compatible with Windows the video must be encoded in a compatible format such as MPEG4 or you must have the appropriate codec installed. Generally a thumb rule is if the Windows video player can play it then it should be ok to import. I loaded up several MOV files on my computer and they played fine here.

So you just launch Cakewalk and the app shuts down when in this state? Do you get a crash dialog - if so we'd like to look at the minidump file. Are you using a different language setting in Cakewalk by any chance?

@Maxim Vasilyev We have not observed this issue. Can you please provide a project to reproduce it?

Hi @Josh Wolfer incidentally we have already fixed this issue for the next update. Fortunately the problem isn't that the gain is incorrect. Rather its an inaccuracy in drawing the gain ruler in the bus pane. You can verify this by looking at the VU meter - it should still show a 0dB value indicating that no gain was applied by the drawn envelope. You should see the fix in the next update.

@Percy Ferry This is'nt normal and we haven't seen it in any of our tests. Can you share a project that exhibits this?