Will there ever....
-
vitocorleone123 vitocorleone123 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333504
- KVRAF
- 2489 posts since 30 Jun, 2014 from Pacific NW
I'd bet that it's a 99.9% chance that there will not be a bridge for 32bit plugins (built in), especially since the developers are looking hard at dropping 32 bit support entirely in future versions of Waveform.
-
- KVRist
- 51 posts since 25 Oct, 2015 from Tyrol
-
- KVRAF
- 3735 posts since 17 Sep, 2016
Agree that is a budget friendly solution!
Windows 10 and too many plugins
-
- KVRist
- 320 posts since 9 Sep, 2017
I understand that software-wise there is a lot of fiddling when a maker wants to seriously cover that area.
it might be too much a drag for a smaller company.
still, some official statements about what works and what doesn't would be very helpful.
or, even a little bit of inofficial support/advice about some 3rd party component.
users of the free versions will naturally tend also to a bunch of free plugins, some great classics that are available only in 32bit.
it's a can of worms, but better than nothing.
just for the record,
e.g. the 32-plugins that crash in cubase 7.5, and those that crash T6/32, are different ones, almost no intersection.
one crash type is the GUI display mechanism, the other type is the data in/out mechanism about stereo, mono, number of in/out pins etc. so at that point we get an actual bridge crash in cubase, instead of reasonable error messages (like "wrong number of in-out pins" or "can't use this stereo plugin in mono channel").
T6 in native 32bit seems quite forgiving about in/out issues, after the plugin was basically scanned and accepted by the internal routine-test.
so, the problem is probably in the error handling system, that becomes very complex when it has to work across the bridge.
it might be too much a drag for a smaller company.
still, some official statements about what works and what doesn't would be very helpful.
or, even a little bit of inofficial support/advice about some 3rd party component.
users of the free versions will naturally tend also to a bunch of free plugins, some great classics that are available only in 32bit.
it's a can of worms, but better than nothing.
just for the record,
e.g. the 32-plugins that crash in cubase 7.5, and those that crash T6/32, are different ones, almost no intersection.
one crash type is the GUI display mechanism, the other type is the data in/out mechanism about stereo, mono, number of in/out pins etc. so at that point we get an actual bridge crash in cubase, instead of reasonable error messages (like "wrong number of in-out pins" or "can't use this stereo plugin in mono channel").
T6 in native 32bit seems quite forgiving about in/out issues, after the plugin was basically scanned and accepted by the internal routine-test.
so, the problem is probably in the error handling system, that becomes very complex when it has to work across the bridge.
-
- KVRAF
- 3735 posts since 17 Sep, 2016
I anticipate Tracktion will stop releasing 32-bit DAW versions in the near future. Of course you will still be able to run old versions of Tracktion with that capability.
Windows 10 and too many plugins
- KVRAF
- 37374 posts since 14 Sep, 2002 from In teh net
Not on Mac it doesn't (not well)
-
- KVRist
- 320 posts since 9 Sep, 2017
I'm not critical about that, but I'm begging that as they are interested in offering useful features, it would be very useful when developers investigate about the bridging, and then can recommend a fairly stable 3rd party solution, preferably with establishing some contact framework with the makers, to sort out fatal and frequent bugs if there are any.zzz00m wrote:I anticipate Tracktion will stop releasing 32-bit DAW versions in the near future. Of course you will still be able to run old versions of Tracktion with that capability.
a major vendor might open up when they see that the market segments are different enough, and also that a number of users will buy both software, for different projects and purposes. but some crucial plugins by virtue of the shared bridge, will work in both hosts equally well. just an example.
-
- KVRAF
- 3382 posts since 21 May, 2004 from Deep in the Heartlessness of Texas
I don't know about the rest of you guys, but I do have some 32-bit plug-ins that would be nice to have available, though not necessary. Not a big deal to me.
One thing maybe worth mentioning is that Synthmaker plugs seem to be best abandoned by everyone. IMHO. You can generally tell that it's an SM plug by opening its folder and looking for .sep and .sem files.
I don't know whether this might be one of the problem issues with JBridge on Mac, since I'm not a Mac guy.
One thing maybe worth mentioning is that Synthmaker plugs seem to be best abandoned by everyone. IMHO. You can generally tell that it's an SM plug by opening its folder and looking for .sep and .sem files.
I don't know whether this might be one of the problem issues with JBridge on Mac, since I'm not a Mac guy.
-
- KVRist
- 238 posts since 24 Sep, 2005
I've just built a W10 64 bit laptop for experimenting with Waveform 64 bit, in anticipation of 32 bit being dropped in W9 forward. I was doing the tedious wading through my loads of plugs to see what I could migrate to 64 bit and came across one set of 32 bit only plugs that I've always liked, being those from Variety of Sound. I've got a lot of projects using these plugs, which could likely be replaced by something else, yet why put that effort in if I can still use them in a 64 bit host that supports 32 bit bridging, or use jBridge.
I installed the jBridge demo on this box and gave the VOS plugs a go after converting them to 64 bit enabled. In the short time I had to demo them (20 minutes) in W8, they worked great. This was impressive and offers hope going forward with 32 bit plugs. After the demo expired, opening plugs would strip off the full GUI, then crash W when closing the tiny GUI (X, camera icon & pin icon only)that was displayed. My guess / hope is that this was purely a demo produced behavior, and not something going wrong with the bridged plugs.
Perhaps another thread should be started for this question, yet I'll start here and see what comes.
That question is - how many of you are using jBridge in 64 bit T & W versions? Please also share your basic level of success / failure in using it for 32 bit plugs in a 64 bit host. It seems Windows is a better platform candidate than Mac?
Gratefully!
P
I installed the jBridge demo on this box and gave the VOS plugs a go after converting them to 64 bit enabled. In the short time I had to demo them (20 minutes) in W8, they worked great. This was impressive and offers hope going forward with 32 bit plugs. After the demo expired, opening plugs would strip off the full GUI, then crash W when closing the tiny GUI (X, camera icon & pin icon only)that was displayed. My guess / hope is that this was purely a demo produced behavior, and not something going wrong with the bridged plugs.
Perhaps another thread should be started for this question, yet I'll start here and see what comes.
That question is - how many of you are using jBridge in 64 bit T & W versions? Please also share your basic level of success / failure in using it for 32 bit plugs in a 64 bit host. It seems Windows is a better platform candidate than Mac?
Gratefully!
P
-
- KVRian
- 526 posts since 7 May, 2007 from Angus,Scotland
That question is - how many of you are using jBridge in 64 bit T & W versions? Please also share your basic level of success / failure in using it for 32 bit plugs in a 64 bit host. It seems Windows is a better platform candidate than Mac?
Gratefully
I'm using jbridge, I bought it. And have had no problems at all with it. In day to day use, I just don't notice it's there.
I'm using
Waveform 64bit
Win 8.1 (rolled back from 10,after it decided it didn't like my emu 1212m card)
Intel i3
Gratefully
I'm using jbridge, I bought it. And have had no problems at all with it. In day to day use, I just don't notice it's there.
I'm using
Waveform 64bit
Win 8.1 (rolled back from 10,after it decided it didn't like my emu 1212m card)
Intel i3
Windows 10 / Intel core i7 2700k @ 3.50GHz / 16GB Ram / Emu 1212m Sound Card / Ati Radeon HD5400 Series G/Card
