chris.r

I see in the Installation Notes that MDrummer Electronic Genres should work also in the free player, after the trial period expires. So what's the consensus, does it work in the free player, anyone can confirm?

THIS!!!

so it's basically an advanced distortion for $150?

Thanks. When I connect the Shure usb mic, both hardware outputs are going back to their original buses like I have set them initially - ART on the master bus and Shure on the extra bus I've created for it. When I'm working with only ART connected to my pc, I'm expecting that ART stays on master bus, and the extra Shure bus will be set to none. In fact, for about a week it was probably so because I got the "One of your buses is routed to a silent hardware output..." pop-up window only after about a week of connecting/disconnecting Shure. And then when I checked it was the Master bus going to -none- and 'Shure' bus suddenly was routed to the ART outputs - so basically vice versa.

Thanks

Not sure it's based on the same bug, but: Cricketts there. I only learned that WASABI is a... well, a non-professional driver and I probably shouldn't use it, so far. No word on what's actually going wrong, my routing routine or Cakewalk itself.

excellent value for money

Also they could let us buy any drum piece from any adpak and mix&match, to make us have more fun.

What kind of adpak you guys would like to see next that is not yet covered by AD2? I would say that their approach is to make something once it makes really sense and not doing anything just for keeping the momentum. Maybe that's why we see some new adpaks less often but with higher quality i.e. special drum kit elements, well regarded drums room etc. It takes time to invent a great idea and execute it.

Has that been ever resolved?

I believe it is doable with screensets or workspaces, so far I've tried with screensets but I failed. Didn't try the workspaces yet as they are more deep. And I'm trying to make careful steps because I don't want later to fall in some common traps people encounter with workspaces as I could see here on the forum.

I'm fine with trading having to open an account on Bandlab for the services it's offering later, like a possibility to co-work with bandmates from a distance or space where I can publish songs. Having to call home once in 6 months is a PITA but luckily only once in 6 months.

Just tried to save a template with console view first maximized with Shift+D and then pulled back down with D. Works only until I close the project. On reopen the template (or project), hitting D opens console view half way again. So here we are. Additionally, when I saved the template with console view opened and maximized, on reopening it does open with console view maximized indeed but the Alt+1 shortcut doesn't work at all. Anyway, what I'm, and I believe Mats is too, trying to achieve is to have a single shortcut to open the console view AND already maximized, from the track view after opening or creating a new project.

Sorry didn't get that, what do you mean "screensets already setup", how to set up screensets for an empty project? I thought it's the same as setting them up for a project template. I may be confusing some basics and I'm trying to break this subject down before stepping into it to avoid any future problems with screensets and workspaces for example when updating Cakewalk to a new version.

Ok, I still have virtual room then.

How many virtual pianos one can have...?

No, geometry is also preserved if the multidock or view is floated lol, Steve, that was a metaphor, like "finally I understand now that if I want to open console in it's full glory then I need to touch those 'pesky' screensets at last" and yet, your answer, as per ususal, was so competent, that you also answered to problems I didn't even encounter yet in my life... but I potentially might in some future

One more question, I was wondering how people that use hardware controller like Behringer Xtouch or Qcon Icon for example, open the console view when pressing any "console" button on the hardware. Does it open in Cakewalk half way and then you have to double click with the mouse to maximize it, or press Shift+D? Do they have option to open it full view by single button press? Or screensets/workspaces the only way?

as much as I hate having to step into screensets and workspaces area, your answer suggests it's the only way forward from where I am

Being in the subject... I can use D to close and open the already maximized multidock while working on a session but when I close project and later reopen it, the multidock opens halfway through again. I tried to save the maximized state in the template but it didn't work. Is there a way to make it keep being maximized on re-open after closing project?

Hmm... is it possible that they did some maintenance update, even performance enhancements like they say, but forgot to update the version number? If the bytes are identical then I have doubts... ?

How often are they doing 50% off? I'm constantly saving money for mallets waiting for 50% off and then they do this 30% or 33% off and I then spend on something else and have to save again and again, lol. Almost did buy it on KVR recently but someone beat me this time.

If you click on the plugin GUI on the bottom left, what is the exact version of your updated Hybrid?

All fine, I agree but, like I said, that's not a problem for me for the time. The other person is manually aligning my tracks later. The problem that frightens me is, why did the two outputs exchange all of a sudden? Yesterday they was assigned correctly to the corresponding busses, today they are literally swapped. Where I had ART outs assigned is Shure now, and Shure is routed to where the ART was.

Sorry I confused driver names. I am using WASAPI Exclusive because in shared mode I can't select both devices, selecting one disables the other. Somehow I thought that WASAPI are still WDM with the new name in Windows 10. My takes are late but what's funny every day with different amount. Even though there's driver reported latency in preferences, Cakewalk is not compensating for the latency, or not making it correctly.