Hello, after installing the plugin, when starting the software, Cubase puts the Captain Chords plugin in the blacklist, if I reactivate the plugin, Cubase closes unexpectedly and then it does not reopen. I have to remove the plugin from the VST folder where it has been installed so Cubase will work again.
My computer is Mac Pro 2x6 @ 3,33 and 64 GB Ram, Mac Os High Sierra and the version of cubase s the 9.5.1.
As I have seen it seems that there are problems with all the versions, I do not know how to get something like that for sale.
Greetings.

Greetings.

On Sunday, December 17, 2017 4:37 PM Salfuman wrote:

Hello, after installing the plugin, when starting the software, Cubase puts the Captain Chords plugin in the blacklist, if I reactivate the plugin, Cubase closes unexpectedly and then it does not reopen. I have to remove the plugin from the VST folder where it has been installed so Cubase will work again.
My computer is Mac Pro 2x6 @ 3,33 and 64 GB Ram, Mac Os High Sierra and the version of cubase s the 9.5.1.
As I have seen it seems that there are problems with all the versions, I do not know how to get something like that for sale.
Greetings.

Greetings.

Hey there,

I am really sorry about that. We've been trying to get Steinberg to send us a Not-for-resale license for 3 weeks now, because we've heard about this crash before. It's super hard to figure out what the problem is without having Cubase ourselves. We want them to hurry up the process, because I really want to fix this problem :)

On Tuesday, December 19, 2017 8:47 PM James Araujo - MIK Team wrote:

Hey there,

I am really sorry about that. We've been trying to get Steinberg to send us a Not-for-resale license for 3 weeks now, because we've heard about this crash before. It's super hard to figure out what the problem is without having Cubase ourselves. We want them to hurry up the process, because I really want to fix this problem :)

Hi James.

I guess you're contacting Steinberg through their ticket system. They are very slow (overburdened) right now. I had a question recently and had to wait something like 3 weeks for a totally unrelated answer, which showed that someone was in a rush when replying and didn't read properly. I then posted a new question and saw that my ticket ID was like tens of thousands higher than last time. They're really overburdened.

I am sure they're going to connect you to the right people when they finally see the ticket, and get you a NFR to get the plugins working with Cubase.

Really hopeful that you're going to officially add Cubase to the list of supported DAWs someday. It's the only professional DAW out there these days. Ableton is for EDM and is ultra-basic, and Logic is getting kiddified by Apple, and Pro Tools is mainly for audio. That leaves Cubase as the only serious DAW aimed at producers that need power-tools.

Currently, Cubase doesn't have 3rd party "Midi FX", but you should talk to them about that. Your plugins would be a perfect fit.

Right now, you're going to have to use this workaround (this is how I use Cthulhu in Cubase, you can check YouTube for videos about Cthulhu to see it visually): Insert the Captain plugin as a VST Instrument track, and create a separate synth track as another VST Instrument track. Then click the synth track and look in the left-side panel. There's a "Midi input: All MIDI inputs" dropdown menu. You just have to click that and select "Captain - MIDI Out" as the input source. Next, click the speaker "Monitor" icon on the synth track to make it monitor/play the incoming midi. Now just play from the Captain plugin and the MIDI will drive the synth.

Cubase themselves have a "MIDI Inserts" feature, which is awesome as hell, but sadly not open to 3rd party developers yet. But like I said, please push them to open that up. It would make Captain plugins as easy to use in Cubase as in Logic. Speaking of which... Cubase would be even better, since Cubase allows up to 4 MIDI inserts, so someone could for example insert Captain Chords first, then insert Xfer's Cthulhu as the 2nd plugin (which is the world's best arpeggiator plugin, no doubt about it).

I can already achieve that by routing 3 tracks: One Captain generator (when Captain finally works in Cubase), going to a Cthulhu track, which goes to the synth. But with a little pushing, Steinberg may open up MIDI Inserts to 3rd parties and make it into a slick, single-track solution instead. So be sure to push for that. ;-)

Good luck and take care! :-) And happy new year!

• "Right now, you're going to have to use this workaround (this is how I use Cthulhu in Cubase, you can check YouTube for videos about Cthulhu to see it visually): Insert the Captain plugin as a VST Instrument track, and create a separate synth track as another VST Instrument track. Then click the synth track and look in the left-side panel. There's a "Midi input: All MIDI inputs" dropdown menu. You just have to click that and select "Captain - MIDI Out" as the input source. Next, click the speaker "Monitor" icon on the synth track to make it monitor/play the incoming midi. Now just play from the Captain plugin and the MIDI will drive the synth."

Cubase PRO 9.0
macOS Sierra

It does not work!!! Cubase unexpectedly closes! Log in back to Cubase is not possible until you delete the VST. Dear developers, how much can you expect to correct this error ???

Right now, you're going to have to use this workaround (this is how I use Cthulhu in Cubase, you can check YouTube for videos about Cthulhu to see it visually): Insert the Captain plugin as a VST Instrument track, and create a separate synth track as another VST Instrument track. Then click the synth track and look in the left-side panel. There's a "Midi input: All MIDI inputs" dropdown menu. You just have to click that and select "Captain - MIDI Out" as the input source. Next, click the speaker "Monitor" icon on the synth track to make it monitor/play the incoming midi. Now just play from the Captain plugin and the MIDI will drive the synth.

Sorry for the delayed reply on this. I was away on a small break, and I missed this message when I came back. But, thanks for the suggestion :) I've just shared it with our developers. I am sure it will help them as they try to make Captain Plugins work on Cubase ASAP :)

It does not work!!! Cubase unexpectedly closes! Log in back to Cubase is not possible until you delete the VST. Dear developers, how much can you expect to correct this error ???

I am really sorry ;/ We are still working on a fix to this. It's a high priority for our developers to get it fixed. We will let you know as soon as it's working 100% on Cubase :)

On Friday, January 19, 2018 2:21 PM James Araujo - MIK Team wrote:

It does not work!!! Cubase unexpectedly closes! Log in back to Cubase is not possible until you delete the VST. Dear developers, how much can you expect to correct this error ???

I am really sorry ;/ We are still working on a fix to this. It's a high priority for our developers to get it fixed. We will let you know as soon as it's working 100% on Cubase :)

Thank you for your response and diligence. I look forward to it.

Wow, this seems like a nice VST to add to Cubase I thought and bought it right off the bat. Installed and when I start Cubase9 all files were moved to the blacklist :( Very sad. I hope you fix that ASAP or I have to get a refund.

after installed captain plugins 2.0,still did not work on cubase 9.5.

I've just started to use Captain Plugins on Cubase 9.5.21 (windows) They were added to the black list straight away, but did show up in the plugin folder once I opened Cubase. No crashes or problems as yet, I feel like I'm paying to beta test , but will report any bugs or glitches I find when I've used it more.

"Right now, you're going to have to use this workaround (this is how I use Cthulhu in Cubase, you can check YouTube for videos >about Cthulhu to see it visually): Insert the Captain plugin as a VST Instrument track, and create a separate synth track as >another VST Instrument track. Then click the synth track and look in the left-side panel. There's a "Midi input: All MIDI inputs" >dropdown menu. You just have to click that and select "Captain - MIDI Out" as the input source. Next, click the speaker >"Monitor" icon on the synth track to make it monitor/play the incoming midi. Now just play from the Captain plugin and the >MIDI will drive the synth."

Yes this is the standard way to use a midi plugin in Cubase, and how I would expect Captain Chords to work.

just installed Captain Plugins on Cubase 9.5.21 (win 10 64 bit ultimate )

Some things for users to note: Cubase' VST sentinel auto blacklists ALL 32 bit plugs ( which Captain Chords installs even if you UN checkboxed the 32 bit version install ) Im guessing these are reliant Child Dlls inherent to the program.

Cubase blacklists automatically any NON VST/FX Dlls in the VST Plugins Folder - nothing you can do to prevent that & is NORMAL expected behavior for any files that are not VST Instruments or effects. Cubase NO longer accepts any 32bit DLLS - Its strictly a 64 bit only environment. So to get some Dlls Blacklisted is normal.

Do NOT reactivate any plugs Cubase has added to the Blacklist after Captain Chords installation - Its smart - It knows simply not to use these DLLS that dont process audio or midi to the VST Spec - Captain Chords runs fine albeit until the Devs move these Child DLLS - Its just a waiting game until MIK team addresses this issue - Ive ran Captain Chords / Deep & Play all successfully for the last 4 hrs ( some audio dropouts were encountered but no biggie) .

So to round it off - Cubase 9.5 successfully runs Captain Chords suite of plugs. With the fear that some of the dlls that have been blacklisted - might affect performance & possibly do - but all is working - timing - drag & drop of Midi - Preset handling - Save features - proceeded to work ok at this time -

EDIT: After installing - After closing the first project I used captain chords/deep in.

I reopened the project & now receive continually crashes from the program.

Hope this helps someone.

Captain still crashes Cubase 9.5 on a Mac on Open.
Confirmed this by removing the Captain VST's and Cubase opens fine. Putting them back in the folder and crashes as it scans plug-ins on Open.

This is not a small bug, this is a major problem. Any idea when this will be resolved?

Thanks.

It still crashes and always has for Mac. I can't open Captain and Cubase at the same time. I have to physically remove the Captain VST's if I want to open Cubase.

Shame.

Developers please fix this, or is there a way to get a refund?

Thanks.

I am having that problem right now!

Since your message was Dec 2017, I'm hoping they have figured out how to resolve this.

I'm also on a Mac and it's acting exactly the same way. Did you find a solution?

On Wednesday, July 18, 2018 8:37 PM KOVAL wrote:

I am having that problem right now!

Since your message was Dec 2017, I'm hoping they have figured out how to resolve this.

I'm also on a Mac and it's acting exactly the same way. Did you find a solution?

Unfortunately, not yet ;/

Any updates on this?

Despite the blacklisting i can load the instruments fine into a new empty project but it always crashes pre existing ones at the checking in or select a key stage. In regards to the blacklisting, shouldn't all the child dll's and other app files be installed into program files/data rather than everything in the vst path (so cubase can't even scan anything except the chord/play/deep dlls themselves)? If every plugin was like that we would have 100's of files blacklisted.

I really don't want a refund but if it won't work with my project templates it becomes redundant. I'm going to try a complete fresh install of Cubase, see if that makes any difference.

https://prnt.sc/klpafm

Cubase 9.5.3
Windows 7

I'm also having this issue on Cubase 9 and 9.5, macOS 10.12.6. I did notice that the plugin loads correctly in Cubase 8.5. Looking forward to a resolution like everyone else in this post!

Confirming that it works with Cubase 8 on Mac (see the attached images):

macOS High Sierra 10.13.6
Cubase Pro 8.0.40 Build 623 (64 Bit) - Built on Mar 24 2016
Captain Chords 2.0.3.2863

Captain plugins in Cubase 8: https://drive.google.com/open?id=1eYBOVp3F7QLSEw04dblYGyvyi5yqeHRT
Cubase version: https://drive.google.com/open?id=1kNGQ5BmyHY0qdEviDrIZ3-UqtgV0AKMH

I've bought this plagin today
I'm also having this issue on Cubase 9 .5.10, macOS 10.13.6

Same problem here, Mac OS 10.13.6 with Cubase 9.5.
I bought the plugs a few weeks ago and in the moment I cannot use anything.
Maybe you should warn possible interests upfront.

Please solve the problem asap.

Best
Thoka

Hi,

Cubase 10 was released today: https://new.steinberg.net/cubase/new-in-10/?_sp=1d3cb74b-75a0-4757-9800-3cb1c32695bf.1542237887125.

Did someone try Captain Chords with Cubase 10?

I'm wondering about combinations with:

• macOS High Sierra
• macOS Mojave

Crashes with Cubase 10 :/ can't use it... It blacklisted all the plugins, I tried to reactivate it and it didn't work :( am I screwed then ? is there any fix coming ?

EDIT: Restarting Cubase and now everything seems to work, crossing my fingers...

Same here. Cubase 10 (Mac) backlists the plugin right away because it doesn't play by the rules.

Considering this thread is already a year old and it wasn't ever fixed, it's probably safe to assume that there is no Cubase support planned in the foreseeable future, if ever.

Too bad, I like the user friendly approach to quickly come up with ideas. But doesn't help when it doesn't work at all.

Just upgraded from Odesi and I can't use it in my DAW which is Cubase 10 on Mac OSX Sierra :(

Dear developers you should've put the info that your software is not supported in Cubase.

Hi. I was just about to buy the plugin and then found this post I am just wondering if this has been fixed yet or if this is still an issue since it says on the website that it is not officially supported but appears stable.

Thanks

On Saturday, June 29, 2019 3:14 PM Barnstable wrote:

Hi. I was just about to buy the plugin and then found this post I am just wondering if this has been fixed yet or if this is still an issue since it says on the website that it is not officially supported but appears stable.

Thanks

We have a fix for this coming for Mac very soon. I would say in the next couple of weeks an update will be available with the fix. It works fine on Windows :)