Jump to content

Scott Wheeler

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

11 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We don't have any plans to make a melodic sampler at the moment. That doesn't mean that it won't ever happen, but there's almost no chance it'll happen in the next couple years.
  2. I thought I'd go ahead and drop in slightly more technical details in case @Noel Borthwick or others are interested. The API for this is very small -- basically the 4 functions that have to be implemented. I just posted the current version (which we're using for Reaper at the moment) in a Github Gist: https://gist.github.com/scotchi/4066f56b71b7b3b112b05df26d52034c There are a couple core ideas here: We want create several very small interfaces, so that DAWs can pick and choose which extensions to implement We want to keep the interfaces very generic so they can be implemented frictionlessly by other plugins
  3. There are various ways that a poorly written service could take resources even when doing nothing, but a well-written service won't. It will however take a little bit of CPU time when the system is started up. What's confusing in the Windows system monitor is that it shows which resources have been allocated; that's only part of the picture though: system memory can be swapped out to disk when it's not in use, and that will usually happen for a service that's not doing anything.
  4. I don't quite understand what you're suggesting here, so to be clear: in our first couple of alphas, there was a background service that ran and didn't actively do anything. (Being pedantic, a background service that isn't doing anything doesn't actually consume system resources: its memory will be swapped out, and it doesn't take CPU time.) When you start up Sitala, then and now, it checks for updates. You can't upgrade an app from inside the app itself, so you have to start a second process to perform the upgrade. In our first couple of alphas, we did that with a background service. Now it just temporarily starts a second upgrader process that automatically exits when the upgrade is finished (and upgrading automatically removed that service). There was never anything nefarious or advertising related, just some inexperience with Windows programming (the two of us that work on Sitala primarily come from macOS and Linux backgrounds).
  5. That went away ... I think after the second alpha? Anyway, hasn't been the case for more than a year at least.
  6. Great, thanks! Reaper has a pretty extensive (though a bit craptastic) API, so it makes deeper integration possible in a lot of ways. The things we have in the upcoming release are automatic multi-out routing, and synchronized track names (so the pad name is automatically reflected in the pad name). We already had note names working in Reaper in our last release. sitala-reaper-automatic-multi-out.mp4 The planned API doesn't do that at the moment, but interestingly, you don't need to have an extension to the VST API to do that. Reaper has a modifier that you can hold when dragging things like that that simply creates a temp file for a few seconds with that content. I even think it should be possible to simply correctly set the encoding of the dragged content to PCM and it should be possible to get it working without any real magic (just using normal desktop drag and drop protocols), but when I went spelunking a year or two back to see if any DAWs actually did that, I didn't find any. But that's something I'm open to exploring for future releases if we get more DAWs on board.
  7. While that's something that we're definitely open to (and say so explicitly on our website), there's also a middle path: in a release that's coming out in a couple of days we've got tighter integration specifically with Reaper, and that's something that we're very open to expanding out to other DAWs. If there are any Cakewalk developers that happen to be reading this and find it interesting, please get in touch with us at info@decomposer.de. We've got an API that we're planning on opening soon that will make it possible for other hosts to integrate more deeply to Sitala (or any other plugin -- we're planning on open sourcing the code) that papers over a lot of the shortcomings of the VST format.
  8. Yeah, I'd noticed that that was the default when we don't set a value (in the screenshot above I'm actually setting the names to a single space), and found that a bit ugly (note names would have been less so), but it's probably worth doing what the others do just for consistency. I assume that they (at least BFD3) have the same issue of things not updating in the step sequencer?
  9. We did get this implemented in Sitala, and it'll be part of the release we have coming up in a few weeks. A couple of quick questions: Right now we're blanking out the notes that aren't support by Sitala. Anyone have a strong preference to that vs. showing simply note names for the unassigned notes? Anyone happen to know of any other hosts that support effGetMidiKeyName? It'd be nice to test to see if it's working in other hosts. Unfortunately there's a little bit of a lag for Cakewalk pulling in the updated note names into the piano roll, and in the step sequencer, it seems to never update the note names once the step sequencer has been activated.
  10. It's on our tentative to-do list for the next release, but we haven't actually messed around with it yet. Basically, if it ends up being straightforward, it'll almost certainly be included in the next release.
  11. I'm one of the Sitala devs, so I thought it might be useful to chime in here. We are right now working with tighter integration with one other DAW at the moment (mainly syncing things up so that note names show our pad names in the sequencer, and that in multi-track mode the tracks are created automatically) and we're willing to do that with more DAWs in the future. Even before I saw this thread I'd been thinking of doing some contact spelunking to see who I might know that I could get in touch with at BandLab since we've seen a real uptick in Cakewalk usage in the past couple of months. The current stuff we're doing is basically just a proof of concept, but effectively what we're shooting for is to create a very small API (i.e. something DAWs can implement) that extends the VST interface in a way that makes these things possible. So, yes, this is something we're interested in. You can go a long way with the VST interface, but there are just some things that aren't possible without adding some extensions, and that's what we're looking at for a few of the hosts that Sitala is more popular with.
×
×
  • Create New...