Lex Nahumury

>>I think megafont did release their sourse code, I remember seeing it somewhere.

Yep, I remember a kX (forum) user once treid to re-write it.


>>if it was written in a different language to what lemury knows…
>>it my be a little hard to work with

Hmm,..Delphi is "easier" then C++, but C++ produces faster and more compact code,
has more "features" and is kind of 'standard da facto'.
Anyway; It wasn't my intention to 'make MegaFont work' with kX
(I never liked the program from a user point of view)


>>So the best solution at present is to compile your own banks....???

IMHO it's always better to have only 10 Really Usefull 'hand picked'/compiled sounds
then 10 banks x 128 presets loaded in sf memory (or elswhere) of wich 90% is useless.
So yes. But compiling/editing ones own sf banks is not a 'kX only' thing.
I would do the same If I would use CL drivers.

Ok, things may become different if one has to stay compatible with
a certain (GM) MIDI exchange standard, but all this is common SoundFont knowledge
and therefore a bit off topic

/LeMury

captain_rusty

Oops.. Sorry

__________________
Can I record my solo album with a Soundblaster Live!Value???

P4 2.4GHz, 256Mb, XP Home, SBLive!Value, Yamaha MG10/2, Toneworks Pandora

Lex Nahumury

>>Oops.. Sorry

np,..I meant; I got off topic myself..
/LeMury

Lex Nahumury

If time is on our side, an updated version of kXSFi will be included in the
next (3538) kX-driver release.

Changes/fixes;
- sfman32.dll independant (no more 'juggling' with diff. dll versions)
- No need to "free" kXSynth2 anymore
- possibly solved midi timing errors reported by < 1ghz PC users.

Thanks to everyone who contributed helpfull feedback to this thread.

/LeMury

TravelRec.

Wow!

Great news here - will test it all out if drivers are coming!

Thanks!

TravelRec.

__________________
Always take a look behind.

BiCho

since kXSFi only loads soundfonts on the first device, i swapped physically both cards. now kXSFi tells me Ok opening the device (SB0060) but it still loads the SFs on the other device...definitely something wrong

__________________
descubre nueva música www.sonidolocal.com
WinXPSP2 authentic running SB0240
MIDIOX-Plogue-Bidule-Traktor-Reaktor-Tracktion-Smartelectronix-ndcplugs-Tobybear
Native Instruments rep.
iCommons Affiliate

Lex Nahumury

>>...definitely something wrong

This is a known limitation I already mentioned in this thread.
So again;
"The current version of kXSFi does *not* support a muli-card config properly (yet)".

For your (and others) information;
Whenever I write a "kX add-on", I always release it on this forum in (very experimental) alpha stage first.
Only If enough users report the initial idea to be usefull, I'm willing to develop it further thereby avoiding needles draining of 'kX programming resources'.
In simple terms; 'To save both mine as well as Eugene's time'.

/LeMury

TravelRec.

Sounds logical! Here for testing if necessary .

Greetings!

TravelRec.

__________________
Always take a look behind.

Mikol

Hi,

I heard about Megafont ... I was the developer (the one !? :-) which try to make megafont compatible with kx Drivers.

At home, megafont works and I can continue to load my "old" Cubase songs with patch names reorganized. My Cubase version is VST 5.

But my megafont version has many bugs (sometimes it crashes and can't load soundfonts after load of cubase song) because it's based on a temporary solution to bypass some kx Drivers known limitations.

Link to megafont beta-compatible is : http://perso.wanadoo.fr/mickael.lacoste/mf.html

Good luck with it.

P.S : I wiil try KxSFi as soon as I could, link was not valid today.

dj_stick

perhaps there should be a beta testing team for such plugins?

i would join that

__________________

NightBreed

Anytime something that's benifical to the quality of a project, I'm always willing to test it out.

BiCho

i will be willing to do so, too

__________________
descubre nueva música www.sonidolocal.com
WinXPSP2 authentic running SB0240
MIDIOX-Plogue-Bidule-Traktor-Reaktor-Tracktion-Smartelectronix-ndcplugs-Tobybear
Native Instruments rep.
iCommons Affiliate

captain_rusty

I'd also be a volunteer for beta testing - I'm sooooo ignorant about the technical side that if it works OK for me, it'll work OK for anyone

__________________
Can I record my solo album with a Soundblaster Live!Value???

P4 2.4GHz, 256Mb, XP Home, SBLive!Value, Yamaha MG10/2, Toneworks Pandora

Lex Nahumury

Attn: TravelRec,

I traced down the "volume" variation you mentioned on that drumtrack you once send me (remember?).
It seems that on very short Note_On durations (like in your drum track) these note volume changes appear.
Making the Note_On durations longer (let's say twice as long), note volume is correct.

Strangly enough this doesn't happen when playing back directly to the 'kX Synth' ports
as you already mentioned.

I thought I'd let you know. Still investigating the problem though.

/LeMury

dj_stick

could this be an issue similiar to the attack issues many people have bene having with soundfonts?

__________________

HarmLammers

No, the attack issue has nothing to do with midi note length.

TravelRec.

Yeah, some strange things happen sometimes, will test it out.
Thanks again for your investment of power to make it all complete !

TravelRec.

__________________
Always take a look behind.

TravelRec.

Yeah, you´re right, there were some very short note_on durations, doubled their lenght and all problems fade away! Thank you for your input!

Greetings!

TravelRec.

__________________
Always take a look behind.

Lex Nahumury

dj_stick;
>>could this be an issue similiar to the attack issues many people have bene having with soundfonts?
No. The 'attack issue' is a quite serious "bug" in kX.
It renders kX's Soundfont usage useless if the first 6,5 ms of your SF samples holds sonicly important content.
Kicks, snares, e-pianos, guitar presets etc. sound dull in kX.
Adding 6,5 ms of silence to the sample start solves this, but who wants an extra latency of 6,5 ms on a hardware sampler?!

TravelRec;
It seems I've found and solved the 'drop outs' on very short midi notes.
It was not kX, nor PC speed related.
Thanks for the feedback/reporting.

/LeMury

dj_stick

that is pretty serious

__________________

TravelRec.

Hey, that´s very cool - you´ve got an extra place in my "hall of fame" !
When the new version comes out?

Greetings!

TravelRec.

__________________
Always take a look behind.

dungle

hi LeMury and others,
I'm finding real use for kXSFi, I think its wonderful.
I verified the problem to satisfy myself and yes, there sure is a soft attack of 6.5mS on SF output.
I dont know whether this driver bug will ever be fixed.
A possible workaround (in KXSFi) occurs to me suitable for Cubase/VSThost use:
KXSFi reports a 6.5mS latency to the host for automatic compensation.
SF's that require a crisp attack are modified to include 6.5mS of silence. This could be efficently
done by batch conversion, perhaps using SFcomp or something.
Maybe KXSFi could do the conversion at SF load time.
cheers

Lex Nahumury

Dungle,

>>I dont know whether this driver bug will ever be fixed.

Neither do I.
Unfortunatly, proper overall SoundFont support has never been kX's strongest point
and apparently most users dont' care, (Vsti samplers are a populair alternative).
So I can imagine that improving kX's SF implementation has become a very low priority issue.

>>A possible workaround (in KXSFi) occurs to me suitable for Cubase/VSThost use:
>>KXSFi reports a 6.5mS latency to the host for automatic compensation.
>>SF's that require a crisp attack are modified to include 6.5mS of silence. This could be efficently
>>done by batch conversion, perhaps using SFcomp or something.
>>Maybe KXSFi could do the conversion at SF load time.

Realy clever thinking,.... but what a hazzle..don't you agree?!!
It's better to fix this "at the root".

/LeMury

dj_stick

afaik, this is true - after speaking with eugene about this, and his reply was

__________________

Lex Nahumury

>>>afaik, this is true ...

Implementing "full" 2.1 features (extended modulator routings etc) into kX is
not the same as fixing 'basic' 2.x Attack generator behaviour.

/LeMury

dungle

Implementing the full 2.1 speification is one thing, but (hopefully) removing
the attack bug requires much less code to write.
It would be a shame (if its not seen to) because soft samplers will never give the ultra low
latency and CPU performance of the hardware implementation. Better to use the host
CPU power for really non-standard effects and synthesis!
cheers

edit: LeMury I didnt see your last post!

Lex Nahumury

>>It would be a shame (if its not seen to) ....
Yep, kX Synths are pretty useless this way, so let's hope for the best.

In the mean time;
You can install both kX and LiveWare.
Currently I use kX on an ADG2 and LiveWare for SF2.1 on ADG1 hooked up via SPDIF.
Kinda best of both worlds, and admiditly a far from elegant solution, but it works.

/LeMury

dungle

I've installed the latest sblive drivers (feb 03) and retested for any
attack problem (which there isnt).
I will now connect a second live I have so that I can have DSP, Asio etc.
In the past I have had all sorts of problems installing CL drivers when 2 cards are present.
Having installed it ok with one card, I can install the other card and install kx only to the other card.
I dont like this because if I boot into my other partition and want to set it up the same, I will need to remove a card to install the CL driver.
Is there a better way of managing separate driver installation for kX/CL multicard?
cheers

BiCho

Actually most users prefer VSTi's for their ease of use (in particular at the exporting to .WAV stage) and not for their polyphony/stability features. These are the features where E-mu soundfont devices beats VSTi's. There are tons of users who still don't switch to kX because they need the SF2.1 compatibility. There are LOTS of users who read these posts and do never say what they think. I'm pretty sure I'm speaking in the name of many users.

With this device you could easily hook various people playing instruments via MIDI controllers leaving plenty of voices yet to be used. The CPU consumption can be assigned to other tasks (such as processing EACH of the different sounds being played and using several chains of effects). Even with the latest processor you will eventually consume too much CPU to do this many tasks.

In my opinion, the only way kX can turn into a complete production beast, is by having SoundFont 2.1 capability. It is true VSTi's give you more flexibility in synthesis terms, but a true hardware sampler can still be used for traditional keyboard playing of polyphonic instruments with zero latency (ideal for playing along with a drummer with MIDI pads, for example, which uses a LOT of polyphony sometimes)

The "no clicks or drops ever", along with the "no latency" features of Tiger M's amplifier models will be a hit for keyboardists, (you could have a DJ playing with Traktor at the same time, on the same computer, along with a guitarist and a keyboardist, with no clicks). There is no other way of really pushing this project up than making the SF 2.1 work.

These drivers are really good. I really trust them live, in studio and for educational purposes. They ROCK, i really wish version 3539 will have this support, thanks!

__________________
descubre nueva música www.sonidolocal.com
WinXPSP2 authentic running SB0240
MIDIOX-Plogue-Bidule-Traktor-Reaktor-Tracktion-Smartelectronix-ndcplugs-Tobybear
Native Instruments rep.
iCommons Affiliate

Lex Nahumury

>>Is there a better way of managing separate driver installation for kX/CL multicard?
Well, it's always a bit of a hazzle (trial and error) mainly because of the CL installer
and identical card types. So no, ..not that I know of.
Maybe other users do..!

(I dont have to juggle cards since my LiveWare version doesn't reconizes the ADG2)

/LeMury