K Brown Synth Bundle

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

wagtunes wrote:You got a solution where I can use everything I have AND 32 bit plugs? I'll even pay you for it.
It sucks that the bridge(s) has/have been that bad in practice :?

I have to mention one thing that can alleviate the problem somewhat, but sadly it's not a solution for using everything (namely, large sampled instruments) and 32 bit plugs at the same time. Anyway: in situations where the RAM limit of 32 bit processes doesn't get in the way -- namely, when you aren't using those large libraries -- Steinberg officially recommends installing the 32 bit version of Cubase alongside your 64 bit version.

It's 100% supported, and the installations do work in parallel like this, on the same machine. After that, you can launch the 64 bit build for everything else, and when you want to use 32bit-only synths, for example, you launch the 32 bit build. The 32 bit plugins will work there natively, stable, without a bridge. All plugins that have both 32 bit and 64 bit versions available will work natively and interchangeably in both corresponding Cubase versions, as long as you have both versions installed. (Meaning, if you have, say, 64 bit Pro-Q loaded in a project, and you open that project in the 32 bit build of Cubase, it will load the native 32 bit version of the plugin, as long as you have that installed on your machine, too.)

I've done the same with my Live installation, launching the native 32 bit one when ever I need to use 32 bit stuff. I've phased out most of my 32 bit plugs, and it's the only host I have installed for using those things directly without a bridge, these days.

Post

Guenon wrote:
wagtunes wrote:You got a solution where I can use everything I have AND 32 bit plugs? I'll even pay you for it.
It sucks that the bridge(s) has/have been that bad in practice :?

I have to mention one thing that can alleviate the problem somewhat, but sadly it's not a solution for using everything (namely, large sampled instruments) and 32 bit plugs at the same time. Anyway: in situations where the RAM limit of 32 bit processes doesn't get in the way -- namely, when you aren't using those large libraries -- Steinberg officially recommends installing the 32 bit version of Cubase alongside your 64 bit version.

It's 100% supported, and the installations do work in parallel like this, on the same machine. After that, you can launch the 64 bit build for everything else, and when you want to use 32bit-only synths, for example, you launch the 32 bit build. The 32 bit plugins will work there natively, stable, without a bridge. All plugins that have both 32 bit and 64 bit versions available will work natively and interchangeably in both corresponding Cubase versions, as long as you have both versions installed. (Meaning, if you have, say, 64 bit Pro-Q loaded in a project, and you open that project in the 32 bit build of Cubase, it will load the native 32 bit version of the plugin, as long as you have that installed on your machine, too.)

I've done the same with my Live installation, launching the native 32 bit one when ever I need to use 32 bit stuff. I've phased out most of my 32 bit plugs, and it's the only host I have installed for using those things directly without a bridge, these days.
He knows - he's had it explained to him already.
Came up with some lame excuse about having lost the installation disk.
Which - as it was explained - he wouldn't need.

But he's only rolled out this tiresome BS one more time to divert attention from the fact that he claimed to have used these 'great' synths years before they were even released.
And everyone fell for it - yet again.

You deserve him, KVR - you really do.
None of the really dumb people I knew when I was young are young any more.

Post

Syntilla wrote:
Guenon wrote:
wagtunes wrote:You got a solution where I can use everything I have AND 32 bit plugs? I'll even pay you for it.
It sucks that the bridge(s) has/have been that bad in practice :?

I have to mention one thing that can alleviate the problem somewhat, but sadly it's not a solution for using everything (namely, large sampled instruments) and 32 bit plugs at the same time. Anyway: in situations where the RAM limit of 32 bit processes doesn't get in the way -- namely, when you aren't using those large libraries -- Steinberg officially recommends installing the 32 bit version of Cubase alongside your 64 bit version.

It's 100% supported, and the installations do work in parallel like this, on the same machine. After that, you can launch the 64 bit build for everything else, and when you want to use 32bit-only synths, for example, you launch the 32 bit build. The 32 bit plugins will work there natively, stable, without a bridge. All plugins that have both 32 bit and 64 bit versions available will work natively and interchangeably in both corresponding Cubase versions, as long as you have both versions installed. (Meaning, if you have, say, 64 bit Pro-Q loaded in a project, and you open that project in the 32 bit build of Cubase, it will load the native 32 bit version of the plugin, as long as you have that installed on your machine, too.)

I've done the same with my Live installation, launching the native 32 bit one when ever I need to use 32 bit stuff. I've phased out most of my 32 bit plugs, and it's the only host I have installed for using those things directly without a bridge, these days.
He knows - he's had it explained to him already.
Came up with some lame excuse about having lost the installation disk.
Which - as it was explained - he wouldn't need.

But he's only rolled out this tiresome BS one more time to divert attention from the fact that he claimed to have used these 'great' synths years before they were even released.
And everyone fell for it - yet again.

You deserve him, KVR - you really do.
Know what? I made an mistake. I could have sworn his was among the hundreds of free plugs I downloaded 3 years ago. So f**king sue me.

it's no wonder I f**king hate this place sometimes.

Post

wagtunes wrote:
el-bo (formerly ebow) wrote:
wagtunes wrote:
el-bo (formerly ebow) wrote:
wagtunes wrote:
thecontrolcentre wrote:You don't use 32 bit synths. Neither do I. Why are you in this thread complaining about it? :nutter: ;) Move along FFS.
Because it's frustrating that there are all these new synths that I could try out and can't because they're 32 bit. I've had to get rid of a gold mine of stuff because it was so unstable. Losing X11 was probably one of the hardest synths to part with. That thing was amazing if anybody remembers it.
I think there might have been a couple of plugins that I would like to have made the transition to 64-bit, that didn't, but none were THAT dear to me. Were I as 'invested' in these old vsti as you seem to be, I'd probably just keep a partition on a computer for compatibility's sake :shrug:
Well, hindsight is 20-20 and I can't undo the decisions that I made when I first started doing this stuff. I thought JBridge would be the "answer" to these "problems." It's not. Lesson learned.
Your computer cannot run 32-bit stuff?
My stupid @$@#$ Cubase won't run 32 bit plugs. If I use MuLab (oh which I only have the demo version, so maxed at like 6 tracks) I can run anything. It has a 32 bit and 64 bit version. If I want to run 32 bit plugs, I just pull up MuLab 32 bit. No problem. Some really old ones, like X11, don't work even there. In fact, MuLab doesn't even recognize it as a valid VST, which Cubase, oddly, does. It just freezes up when I run it.

If I had to do this all over again, I don't even know what I'd have to do in order to avoid this problem and not create other problems.

For example, part of what I do requires me to use massive orchestral libraries which are all 64 bit. That's the reason I went with a 64 bit OS to begin with. That was my main priority. And I still use them for many things. I just did a whole Broadway like Soundtrack that I simply could not have done to this quality without them.

Also when I first started doing this, I didn't know that a 32 bit plug would malfunction on a 64 bit machine in a 64 bit DAW. Cubase says right in their specs that it will run 32 bit plugs with its built in bridge. Well, guess what? That bridge is so crappy that they've removed it from 8.0 or are in the process of removing it. They will no longer support 32 bit plugs, period. It's right on their site and in the newsletter I got a while ago.

And I can't give up Cubase because I also use Vocaloid, which has a Cubase editor so that I can use it directly in my DAW like any other VST. Otherwise, I'd have to use the standalone and jump through all these hoops to get it to sync up with my DAW, if even possible.

So that's where I am. I'm stuck between a rock and a hard place. And no, I'm not looking for sympathy. I would just like the products that I buy to actually do what they say they will do. Cubase 7, which I am still running because I don't dare upgrade to 8, was supposed to support 32 bit plugs. It doesn't. At least not well. JBridge was supposed to fix this. It doesn't. At least not well. On average, I can use a 32 bit plug for about 30 to 60 minutes before it locks up my DAW. Makes it a pain in the ass to work with them.

There you go. That's the whole story. You got a solution where I can use everything I have AND 32 bit plugs? I'll even pay you for it.
No! What I meant was that you could run an ol'skool partition. Install XP, run an old, free DAW, and fill yer boots :tu:

Post

el-bo (formerly ebow) wrote:No! What I meant was that you could run an ol'skool partition. Install XP, run an old, free DAW, and fill yer boots :tu:
:lol: heh... But seriously, the Steinberg supported procedure I posted above, that's the most painless way to run those legacy plugins without a bridge. Install the 32 bit build of Cubase, specifically for these tasks, and use that when ever you have the need. Great for taking part in the OSC and using a 32 bit synth with no bridging, for example :)

Post

Guenon wrote:
el-bo (formerly ebow) wrote:No! What I meant was that you could run an ol'skool partition. Install XP, run an old, free DAW, and fill yer boots :tu:
:lol: heh... But seriously, the Steinberg supported procedure I posted above, that's the most painless way to run those legacy plugins without a bridge. Install the 32 bit build of Cubase, specifically for these tasks, and use that when ever you have the need. Great for taking part in the OSC and using a 32 bit synth with no bridging, for example :)
Okay, where can I get a 32 bit download from? Like I said, I have no idea where my Cubase disks are. And if I install this, it's not going to screw up my 64 bit version, will it? Sorry, but when it comes to this technical PC stuff I am close to clueless.

Also, won't I need my serial number when I install the 32 bit version?

Post

wagtunes wrote:Okay, where can I get a 32 bit download from? Like I said, I have no idea where my Cubase disks are. And if I install this, it's not going to screw up my 64 bit version, will it? Sorry, but when it comes to this technical PC stuff I am close to clueless.
I'd recommend contacting customer support. They will walk you through it, and then you will also have an official word to lean on, if something does go wrong. Having a separate parallel install shouldn't break anything, but better safe than sorry :tu:

Post

thecontrolcentre wrote:
1wob2many wrote:1. Please don't turn this into a Waggles-baiting thread.
He'd already hijacked the whole thread. :x
Fair point. Request withdrawn.

Post

Ahem, well anyway - forging on :

Spogg over at DSPR asked a while back about have I done a 'dream synth' - the closest I've come I suppose is this one I just finished tidying up. It's based on a daydream of a Yamaha that combined most of the features of several CS-series synths. The mighty CS-80 was mighty because of it's truly polyphonic touch response and plethora of performance controls; it's basic synthesis abilities were surpassed by most of the other CS synths, especially the monophonic ones like CS-15 and CS-30.
So, the idea was to do a plugin that combined many features of CS-30, CS-15 and CS-80 in a CS-80-style panel layout (no, it doesn't sound like a CS-80).

Therefore CS-358 :
CS-358_copy.jpg
You do not have the required permissions to view the files attached to this post.
Last edited by kevin brown on Thu Nov 24, 2016 4:51 am, edited 1 time in total.

Post

To all: in general, if something appears to be not be working right your first step should be to re-download it from the master folder because I often go through these and find errors or make improvements, but don't litter the forums about every single 'fix' - your issue may have already been addressed!

Post

Here's a simplified FM instrument - based on the basic idea of the pretty obscure Korg DS-8, which was built around the voice of the Yamaha FB-01 4-op FM module. In place of the then-bewildering Ratio Tuning and Modulation Index way of producing waveforms, it had a set of pre-formed FM waves that one could shape 'up' from sine - a bit like the way the Casio CZ instruments worked but with FM instead of Phase Distortion. It also had only two algorithms - a pair of Modulator /Carriers (like DX100 algo 5) and a 4-op stack.

With this vst, I've pushed it to a more conventional Ratio-tuned FM instrument and expanded it to six operators; also two algos - three 2-op pairs or a 4-op stack (X-Mod) plus one 2-op pair. I've retained much of DS-8's more conventional analog synth nomenclature and the Coarse/Fine tuning of the operator pairs (Oscillators). Also given it a second LFO.

A much friendlier way to FM, but less limited than DS-8.

Chorg DS-600 :
Chorg DS-600_copy.jpg
You do not have the required permissions to view the files attached to this post.

Post

Kevin, has been done any update/retouch to various vst here and there in this past week?
I mean, you feel the whole synth pack needs to be downloaded again,if many plugins may have been optimized/updated, or the situation is, more or less, the same since a couple of weeks?
Asking this before, in case, starting the whole stuff download...
And, I noticed that there's a pdf manual of one synth that, only that one, takes about 100 mb (!!)...
May be possible to make it in a more compressed/lighter file? :D ...
Thanks for your time and all your nice synths once again. :tu: Greetings

Post

Diego_C wrote:Kevin, has been done any update/retouch to various vst here and there in this past week?
I mean, you feel the whole synth pack needs to be downloaded again,if many plugins may have been optimized/updated, or the situation is, more or less, the same since a couple of weeks?
Asking this before, in case, starting the whole stuff download...
And, I noticed that there's a pdf manual of one synth that, only that one, takes about 100 mb (!!)...
May be possible to make it in a more compressed/lighter file? :D ...
Thanks for your time and all your nice synths once again. :tu: Greetings
This might help: http://music-society.de/index.php/topic ... n.html#new
None of the really dumb people I knew when I was young are young any more.

Post

amazing package. And although i usually don't install 32 bit (only) plugins, this package is worth it being the exception! Just awesome!

Post

Syntilla wrote:
Diego_C wrote:Kevin, has been done any update/retouch to various vst here and there in this past week?
I mean, you feel the whole synth pack needs to be downloaded again,if many plugins may have been optimized/updated, or the situation is, more or less, the same since a couple of weeks?
Asking this before, in case, starting the whole stuff download...
And, I noticed that there's a pdf manual of one synth that, only that one, takes about 100 mb (!!)...
May be possible to make it in a more compressed/lighter file? :D ...
Thanks for your time and all your nice synths once again. :tu: Greetings
This might help: http://music-society.de/index.php/topic ... n.html#new
It did indeed. :-) Thanks a lot Syntilla :tu:

Post Reply

Return to “Instruments”