Question about Chinese Winds VSTi

Official support for: chineekong.com & kongaudio.com
RELATED
PRODUCTS

Post

dvonae wrote: Seems some people will live with (and pay for flawed products) rather than demand such things be fixed before spending their money. Offer a big discount and promiss a fix, then wait years to actually fix it, if at all.

Oh, wait...

Didn't Bill Gates get rich doing just that??? :dog: :hihi:
<joke mode on>Thanks to the new wonderful wild west of Internet, now lots of synth/sound devs here at kvr own their personal islands and get surrounded by beautiful women....who needs to give heed to Bill Gates? :)</joke mode off>

Joke aside:

1. About the sample-path issue. Since we use SynthEdit as our engine, there is nothing we can do unless the author of SynthEdit has it fixed. When the fix arrives from Jeff, we will update the engine accordingly for sure.

2. We knew it's a big flaw. We acknowledged that. We didn't hide it. That's the reason why we have put the info on the purchase page upfront since day one, knowing that will cost us sales. Yet we know it's the right thing to do. Anyone who goes through to push the purchase button should see it(admittedly, ppl with an impulse might still overlook that :wink:).

To be honest, one of the main reasons why users can get this excellent sample-based instrument at such a low price is due to this very flaw. Otherwise you might end up seeing it on the shelves with a shiny 200 USD prictag on the box plus a kompakt engine, whilst the core samples - which really make the difference - are still the same excellent samples as they are.

We sincerely hope musicians around the world can enjoy making music with the refreshingly inspiring sound from our products, once they go through the possible initial trouble. The good outdoes the bad so much that we believe it worths the efforts.
Last edited by sosayweall on Sat Jul 02, 2005 7:44 am, edited 1 time in total.

Post

Hi Hans,

Strictly speaking, we do not have the source code of SynthEdit. No one but Jeff does.

BTW, if you think you bought ChineeWinds by mistake, we are willing to refund. Please contact us via email.

Post

sosayweall wrote:BTW, if you think you bought ChineeWinds by mistake, we are willing to refund. Please contact us via email.
I bought it by impulse :), and since it's working now, and create unique sounds, I have no reason to get rid of it :)

Post

sosayweall wrote:Strictly speaking, we do not have the source code of SynthEdit. No one but Jeff does.
Yes. I can imagine Jeff hardcoding the samples path D:\audio\Chineewinds into the SE modules... please don't treat me like an idiot.!

Post

SORRY -- let me ask again, if I may...

Can someone spell out a little more explicitly for me how one might do a "work around" for this VSTi -- OTHER than re-naming drives on my system?

I understand from earlier posts that I can "set up a virtual drive" in XP or something like this, and someone mentioned using the "subst" command in XP...?

(Again -- so sorry if this is supposed to be "basic" stuff -- but this is news to me, and I'm still holding off purchase until I feel I can make this work agreeably.)

BUT I SAY AGAIN, the demo's for this sound so great, I am TERRIBLY anxious to try it out!! :)

Post

M'Snah wrote:
sosayweall wrote:Strictly speaking, we do not have the source code of SynthEdit. No one but Jeff does.
Yes. I can imagine Jeff hardcoding the samples path D:\audio\Chineewinds into the SE modules... please don't treat me like an idiot.!
It's not easy to earn people's trust these days, it seems. I suppose time will tell. :wink:

Hans, we do not see our users or anyone here as fools. The only fool here is me, not capable of giving a clear explanation. For a clear explanation about the specific SE bug, you will have to wait till Shan comes up online later. AFAIK, Jeff is aware of the issue in the sampler module, but we don't know when he'll be fixing that.

Post

EDIT: ahh. Didn't read tokyotain's original post carefully. my bad. :)

Yet still, Tokyotain, it's not hard to set up the virtual drive, but it's tiresome and annoying indeed.

You may want to check this link, just in case you haven't done so.
http://www.microsoft.com/resources/docu ... subst.mspx
Last edited by sosayweall on Sat Jul 02, 2005 1:17 pm, edited 2 times in total.

Post

TokyoTain wrote:Can someone spell out a little more explicitly for me how one might do a "work around" for this VSTi -- OTHER than re-naming drives on my system?
You might potentially use a hex editor or a resource hacker to patch the binary, but only at your own risk: it's in violation of most license agreements, but sometimes there's little other choice.

- m
Markleford's band, The James Rocket: http://www.TheJamesRocket.com/
Markleford's tracks: http://www.markleford.com/music/
Markleford's free MFX, DXi2, DR-008 modules: http://www.TenCrazy.com/

Post

OK...I've talked to Shan. I have to eat my own words and hereby declare myself as a genuine fool of the month. :)

THIS DRIVE ISSUE HAS NOTHING TO DO WITH SYNTHEDIT being buggy. My apoligies to all.

I misunderstood Shan's meaning when we talked about this in the past. So...making the long story short:

We have two options, either

1. Users can put the dll anywhere they want, but have to put the soundbanks to a fixed drive position.

2. Users can put the soundbank anywhere they want, but the dll has to be in the same folder as the soundbank.

We picked the first route in the past, but it appears that some users are not happy with it. What do you guys think, should we stick to the old way, or should we allow the soundbank to be anywhere, but the dll has to go with the soundbank as well?

If more ppl are in favor of the latter, we will switch to that from here on and release a new build right away.

Post

sosayweall wrote:2. Users can put the soundbank anywhere they want, but the dll has to be in the same folder as the soundbank.
So... this means that it MIGHT be more difficult to find the dll in my host, since it won't be in the vst-plugins folder, right?

Ahhhh... NOW I can see why you chose the route you did. I'll be honest, it wasn't making sense before (and in fact, not being a developer myself, I STILL can't quite get why the limitations--seems other SE's with samples don't have this restriction?)... BUT, at least now I see that for whatever reason you are faced with only these two options, and you chose the "fixed location for soundbank" option.

Thanks for explaining! :)

For ME, I would rather have the soundbank anywhere I want it. I'm not positive (I'd have to check it), but I am PRETTY sure that Cubase will let me find VSTi dll's anywhere I want... and/or, I could probably put a shortcut in the plugins folder to wherever the dll actually is located... ?

And THAT would be a LOT easier for me to deal with than trying to rename drives and all that...


I know I started this thread, and I know I keep saying it -- but the FACT is, I hope this can be worked out -- because based on your demo's I think this is one amazing set, and -- having lived in Hong Kong and now Tokyo -- it would be something I would use all the time!! :love:

Post

Hi TokyoTain,

We can see you are really interested in ChineeWinds. :)

Shan has just decided to switch to option 2 hereafter - soundbanks will be able to be placed anywhere you want, but the dll has to go with the banks. (It's not ready yet though)

I have read about the shortcut trick before, but I'm not familiar with Cubase, so you may have to consult other fellow Cubase users to make sure of that.

Post

TokyoTain wrote:So... this means that it MIGHT be more difficult to find the dll in my host, since it won't be in the vst-plugins folder, right?
Anywhere you want means that it could also be the vst-plugins folder... but you'd have to put the samples there as well. Which means that some hosts take a bit longer to scan for VST's...

It would be my preferred solution though.

Post

M'Snah wrote:Anywhere you want means that it could also be the vst-plugins folder...
Of COURSE!!!! That's RIGHT... (insert image of me doing this: :dog: )

Beautiful!

I will purchase as soon as you tell me it's "settled" and ready to go -- I can't wait!

:D

Post

I guess it's an important issue, but it hasn't bathered me. Also, I have never met a dev that is as honest and as helpful as Kongaudio.

I think these guys are great because of the instant support of course, but also for the absolutely pure sounds they achieve. I LOVE ChineeWinds and I want to get Chineekong as soon as it's released -- that VSTi is totally amazing!! (I have already written a song using ChineeKong and haven't even used it yet -- just waiting for it's release!) 8)

Cheers,
Alex

Post

WOW, xander -- that's a great endorsement... Now my mouth is watering!

I just popped onto their site again, to listen to those demos of ChineeWinds -- if I can make this thing sound anywhere near as authentic as those demos, I mean if it's possible without jumping through crazy programming hoops to get a good sound, then I will become these guys' biggest fan.

('cause those demos sound AWESOME... especially the newest one, "demo 4", which I hadn't heard before about 10 minutes ago)

Post Reply

Return to “Kong Audio”