jBridge problem in cantabile

[humphrey]

Hi,

first of all apologies as I'm new to this forum and maybe there have already been solutions for my problem.

Till now I'm on brainspawn forte but heard about cantabile in a very positive report in german computer magazine c't - so I downloaded the performer demo versions (32 and 64Bit) and can say: very impressive! Not that forte is a bad peace of software to my mind, but cantabile has some really good issues I'm missing in forte. So I do some intensive tests at the moment on my equippment.

My problem: it is a really nice feature to implement jBridge into cantabile (I use it a lot for my Omnisphere to have more than one instance isolated - concerning RAM use). In Forte I use to have jBridge as converter 32-32Bit for this reason and this works. In cantabile I cannot find the .32.dll as it is suppressed by cantabile. I found this thread in the forum where reasons behind are described:
http://www.kvraudio.com/forum/viewtopic ... ht=jbridge
Bradr gives a link to a blog file where a workaround for exactly this seems to be described but unfortunately doesn't work any more.

You may ask: why not use the 64Bit version of cantabile? The reason for this is a reverb plugin (EOS from Audio Damage) that works great in the 32Bit version but not bridged with jBridge in the 64Bit version. So I'd have to stick to the 32Bit version and now have the need to bridge my Omnispheres by a 32-32 jBridge.

Sorry, this was a very long and very special topic for a newbie.

Hopefully there is someone out there with some good hints.

Thanks and regards, humphrey

[TiUser]

Welcome!

Thanks for quoting the article: c't magazine 12/2010, page 154-155, german Title:
Report: Guter Gastgeber
Software-Instrumente und -Effekte komfortabel live spielen mit VST-Hosts
http://www.heise.de/ct/inhalt/2010/12/154/
Pity that the article is payware... I'd liked to read it. How does Cantabile compete?

You are right, the link to the blog article does not work any more. I think what you are looking for might be here:
http://www.cantabilesoftware.com/blog/p ... ed-plugins
I'm not sure if "run isolated" reloads the plugin, but that's all I could find in an instant...

Basically it helps in case of broken links to Cantabile blog articles to look up the blog index and match the date.

Probably it's a good idea to ask jBridge developer why your reverb plugin does not work with jBridge - maybe this can be fixed too.

[humphrey]

Wow,

this was what I would call a quick response - many thanks!

Concerning the article: well I'm really astonished that you got no access. If I were you I would contact Heise or probably the author of the article (his name is Kai Schwirzke). I could imagine that they will send you a copy. But nevertheless I give you a short impression of the content:

For the fact that musical software is not a core theme in c't the article was really long as it had 2 complete pages. The headtheme of the article was (not translated word by word): "playing vsts and vstis comfortably live using vst-hosts" - means it was an article for all vst live hosts.

The very positiv aspect for cantabile: 80% of the article described functionalities and possibilities of cantabile. There is even a detailed comparison between the 3 versions you have available incl. prices & a screenshot of the mainwindow.

The author describes several scenarios in detail. All in all one can say that cantabile competes absolutely fabulous (to show up I can tell you that there is a small summary that takes less than a third of a page in which all competitors are handeld). Hope this gives you a first impression.

Concerning the link and your hints: thanks a lot, I will have a look on that.

To contact the developer of jBridge concerning the incompatibility of EOS and jBridge is surely a good idea I will follow. Meanwhile I contacted Audio Damage (EOS) and also got a quick response. Unfortunately they see the resonsibility at jBridge (probably o.k. from their point of view if EOS runs in many other hosts without problems).

The good news is, that there will be a 64Bit version of the plug in the future - so I think I will get my problem solved...

best regards and thanks again, humphrey

[TiUser]

No problem, I appreciate to help if I can and if I'm just online this might happen fast.

I'm featuring Cantabile with forum activity since beta 2.x development has been started because I think Cantabile is one of the most advanced live hosts available. It can do a lot, some stuff is well buried under the hood, others a bit technical yet most logical in a way. Despite some very special advanced things my point is mostly about better usability - which is hopefully a matter of time.

Concerning the c't article: C't is really one of the good computer magazines and I was surprised that they deal with such software too... But where to read the article online? The link I posted just shows a thumbnail... and the usual way is buying the magazine to read their articles... so thanks for the overview. BTW: you might have sent me a PM with s summary in german which might make it easier for both of us...

Well, concerning issues with jBridge I guess Joao is very much interested in being informed. I am sure he will address the issue if it's in jBridge and if he can fix it.

[humphrey]

<<<BTW: you might have sent me a PM with s summary in german which might make it easier for both of us...>>>

o.k. I will look for a "german summary machine" and PM you when I'm done. >>>

best regards, humphrey

[TiUser]

...you are welcome, and check your PM...

[humphrey]

Hi TiUser,

some additional information (as you were involved in some of my questions):

during testing I had a look at jBridge and registrated I hadn't updated to the very last release (1.2 instead of 1.19). After update to 1.2 my EOS now works flawless in x64 cantabile. So I'm now able to use cantabile 64Bit without any further problems.

Another aspect: I had a closer look at the performance issue (I mentioned kind of misbehavior compared to forte). In between two things have changed: using x64 gives me some advantage / using "agressive mode" for multiprocessor support brings an extra on performance so I can say now: cantabile is running on a par with forte performance-wise.

With all the extras included it looks like becoming the winner for me. I think some smaller tests towmorrow and I will purchase the performer edition.

This only fyi, best regards, humphrey

[TiUser]

Thanks for the feedback.

[krraqk]

Hello

im having some problems with Jbridge (ATM at 1.19, but has mentioned the latest is 1.20, so I will update to it).

My problem is that if I close the gui of a vsti and later i try to reopen it, then there is a big delay (about 30 secs) and after that delay (which turns cantabile irresponsive) then I get an error message <dispatcher opcode 14 failed (try disabling any option you may have enabled)>, and when i click ok, then the gui appears inmediatelly.

I have no enabled any option, its all default.

Im using Cantabile X64 alt config (what means alt config??) and this happens with all the x32 plugins.


Do you have this problem also?

[TiUser]

"alt config" means "alternate configuration". This allows you to run two instances of Cantabile in parallel - with different configurations.

I still use the x86 version as most plugins I use are still 32bit. So I have no idea - except this sounds like a jBridge issue.

[humphrey]

Hi,

no sorry, I do nor did have this issue even not with jBrindge 1.19. I did test this today with the Alt Config Version but also in this case: no similar issues.

The long load time reminds me of the very early days of Spectrasonics Omnisphere - but even if this is the plug that shows this effect: the bug should be fixed for a long time.

Concerning use of "Alt Config": It's described on Page 94/95 of the manual. It simply means that you can use the Alt Config version of cantabile in parallel with a first instance you started. To clearify the advantage: think of a keyboard setup consisting of two MIDI keyboards connected to on PC.

If you know exactly which songs you want to play you are fine with only one instance of cantabile as it is pretty clear which combination of plugs you want to control from your keyboards and it is very useful to call up the whole setup (f.e. by using a MIDI program change instruction) in one task.

Now think of a session: here the situation is completely different. In most cases it is not useful to have fixed layers and combinations of sounds in one set. It would probably be more useful to have 2 separate instances of cantabile available each connectes to one MIDI - keyboard. In this setup you can have a bunch of standard sounds in each of them and are now able to freely combine them as you need it for your session.

This is one the possibilities to use the "Alt Config" and there are more described in the manual.

Please keep in mind that you need soundcard drives that offer the possibility to share audio ports to use this functionality.


regards, humphrey

[TiUser]

Please keep in mind that you need soundcard drives that offer the possibility to share audio ports to use this functionality.

...or you can run two Cantabile instances each with a different audio interface...

[krraqk]

Hi,

no sorry, I do nor did have this issue even not with jBrindge 1.19. I did test this today with the Alt Config Version but also in this case: no similar issues.

The long load time reminds me of the very early days of Spectrasonics Omnisphere - but even if this is the plug that shows this effect: the bug should be fixed for a long time.

No its not the plugin that takes so long to load, in my case its already opened, then I close the gui (it keeps sounding) and if I reopen the gui later is where I have that long wait, error window, etc., annoying at least.

Oh, I understand now the "alt config" thing, well I think I dont need that, atm at least. Maybe if I want to share the laptop (synths and effects) with other person would be a good solution, although it implies to have 2 audiocards, 2 midi interfaces, etc.

[umd]

@krraqk:

Try enabling the "prevent main host control when the GUI window is closed" option ( in jBridge ).

[krraqk]

@krraqk:

Try enabling the "prevent main host control when the GUI window is closed" option ( in jBridge ).

Thanks for the info. I need to do it to every plugin?