Little update: I managed to save one inter-process call per rendered frame when notes or other MIDI data (i.e. Zxx effects) is being sent to plugins - this should reduce the introduced latency and thus crackling a little bit, at least in theory.

Regarding the KarmaFX issue, I'm in contact with the author to find out what's going wrong.

Logged

» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Probably because you're not bridging it? I don't get any error messages, but the plugin simply hangs here. Probably because it's sending MIDI messages to the host, which is something I haven't really tested so far.

Logged

» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

OK it works now!, Thank you for your great work.And about multitreading... I normally use a lot of VST instruments, and its a bit difficult sometimes to work well(I normally bypass many instances), but If you don't have time it doesn't matter, Thank you Again!!!

but sad to say i get crackling in my tracks if i use 30 notCPUhungry vst's like mda,classic etc. and i dont get that if i use old 32bit version of openmpt. also modifying(or just opening the gui) the plugins makes a crackling effect.actually i have amd phenom quad core 2.10 so i dont think its the best for 64bits.audio driver latency is very big - up to 250ms but nothing. probably there is a mess with my PC, it become shitty..could be the latency beetwen all the pluginbridge instances, like was written few posts back.attached is what i see when comparing 32 and 64.

As explained before, the crackling happens because of the process synchronization and not because of high CPU load. Every bridged plugins adds a lot of latency and thus you will have to increase your latency and probably also update period settings in OpenMPT if you want to use the bridge. Naturally, this doesn't happen with the 32-bit version since it doesn't require a bridge for 32-bit plugins. And to quote the download page:

Quote

The 32-bit version should run on all systems. Apart from a slight performance increase, there are some situations in which you can benefit from using the 64-bit version if you have an operating system that can run 64-bit programs:- If you use no plugins, or most of your plugins are available as 64-bit plugins, use the 64-bit version.- If you need more than 4 GB of RAM for plugins and samples, use the 64-bit version.

Hence: If you use a lot of 32-bit plugins, keep using the 32-bit version.

Logged

» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Probably because you're not bridging it? I don't get any error messages, but the plugin simply hangs here. Probably because it's sending MIDI messages to the host, which is something I haven't really tested so far.

You don't want to know how many hours I have already spent trying to fix that one. It's frustrating.Not sure why this one is a priority for you, though, since there is both a 32-bit and a 64-bit version, meaning that you can use a non-bridged version under all circumstances.

Logged

» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Ok just wanted to see if you had looked at it. But dont worry, I'll have 2 instances of modplug together 32/64 bit.I only asked because I have used this plugins in so many songs and when you save a preset with this plugin in 32 bit version in doesnt load properly in the 64 bits version. But thanks for trying and I wish you a very nice day.