DIVA Bug . . . maybe

[Teksonik]

Let me pose you a question. How do I determine it to be a FL specific/system interaction issue and not related to the VSTs in use? On the one hand I get a DC spike. On the other I get a MIDI problem directly related to U-He stuff. I can attribute the DC spike to DIVA. The MIDI issues cause FL to crash and I can attribute that crash to TyrellN6 & DIVA. Honestly, I'm not seeing how I can blame FL right now. There simply is no reason to suspect FL other than by "gut feeling" rather than any evidence.

The way you can rule out FL as a possible cause is to try another DAW as exmatproton pointed out. If you get the same results then we've narrowed it down to the VSTi or the System. On the other hand if you don't get the same results then it points to being an FL problem since everything else is the same. If you only get the problem when using DIVA or Tyrell then it could point to them as the possible cause. You say you don't get the same results in Reaper so to me that points to FL as a possible cause. You also say it only happens with DIVA or Tyrell so that could point to them as a cause as well. Sometimes a certain plugin just doesn't play well with a certain host but all I can say is DIVA works fine in FL 12 on both this system which is still 32 bit and my 64 bit DAW so at this point I can not confirm the issue you have reported. I have no problem reporting something that may be a bug in either DIVA or FL Studio.... it wouldn't make sense to deny an obvious bug and I have no motivation to do so. If there is a bug I want to help find it.....

I've been a beta tester for dozens and dozens of synths, effects, and DAWs and this is the method we would use to track down a possible bug. Eliminate each part of the chain, DAW, Plugin, or System and whatever you're left with is the possible cause. The other thing required to call something a Bug is for at least two or more people being able to reliably reproduce the issue on multiple systems. So like I said if you can upload an .flp file that shows the issue I and others can test it to see if we can reproduce it on our systems. It's just a process of elimination.

So at this point all I can say is: 1. I can not reproduce the issue reported here. 2. I do not see any posts either here or on the FL forums that would indicate an issue with DIVA and FL Studio.

One thing that would help and is always a good idea is to post your system specs....OS, CPU,Graphics Card, Sound Card, Audio Drivers etc. That information may give us a clue. Perhaps my system is radically different than yours which is why I can't reproduce the issue here.

Anyway I'm willing to help but let's just remain calm and try to work it out........

[APZX]

Look I was only getting heated because you were ignoring my original issue and focusing on something unrelated and superfluous to the issue I'm experiencing. That is all.

As for the system I'm using:
Intel i7 4770K
Asus Z87-A
GTX 780
32GB RAM
Windows 7 Pro
Focusrite Saffire Pro 24

You'll have to give me sometime to export the project into its various MIDI files and controller data and rebuild it all in Reaper. But doing that doesn't eliminate the possibility of plugins interacting strangely with one another. But if it doesn't show in Reaper then it shows that FL is handling the VSTs improperly. Though if it does show in Reaper then that means there is an issue with some plugin somewhere and it isn't related to the host.

Attached is the FLP. I personally don't think the sampler included in FL is causing any problems, but I've seen stranger things While, you guys muck with that I'll work on rebuilding it in Reaper to see if I have the same issue or not.

[Teksonik]

ignoring my original issue

Your original issue was asserting there may be a bug in DIVA.....which is why you posted at the UHE forum. You also claimed FL 12 64 bit needs "to mature". I simply disagreed....that's all.....

Anyway the .flp file you posted is chocked full of plugins and there is very little chance that anybody will have all the plugins and samples installed. For example I don't own OPX Pro. To be honest it could be any of the instruments and effects or combinations causing an issue. That makes it worthless for testing a DIVA bug. So if you have effects on DIVA's channel and turn off DIVA then you can't rule out it wasn't the effects causing the issue.

Like I've said several times before...create a new .flp using only DIVA and see if you can reproduce the DIVA issue in it....if you can then post that .flp and we'll see if we can reproduce it on our systems (assuming anyone else is willing to help). If we can reproduce the issue then we may be able to call it a DIVA bug, and at that point UHE would have to step in and take over......

Oh and while trying to load your project I noticed you have several instances of N.I.'s Replika loaded. There were serious graphics issues with Replika especially with earlier versions when using multiple instances. Make sure you're using the latest version of Replika then also try a new project with just a couple of instances loaded to see if you're getting graphics issue with it. There was also a known graphics issue with SynthMaker plugins with gui flickering when a plugin menu is open in FL. I don't use Synthmaker plugins anymore so can't say for sure if this issue still exists but it's something to look out for. I believe Nomad's Magma also had the gui flicker issue so much so that I originally thought they had used SynthMaker to create Magma but of course I learned later that they did not. I'll have to check to see if the Magma gui flicker is still present in FL 12 next time I boot the studio computer.

[APZX]

I've tried all of that before I even came here.

The issue is literally adding one instance of DIVA causes the problem. Removing it? Issue disappears. I'm not saying there is a bug in DIVA, but it is suspect hence the title of the thread. If I load just the instruments I don't have a problem. If I just load the effects I don't have a problem. If I load say all of OP-X Pro and their associated FX, no problem. Etc . . ., which is why I suspect there to be a bug. Where? I dunno, but if removing a single instance of DIVA fixes the issue I'm having. Then the assertion that there is something wrong or more likely (and what I believe to be the case) a strange interaction between plugins is causing the issue is reasonable I feel. The problem is I cannot tell you which plugs are actually causing the problem.

Yes, I used a lot of Replika and it is the latest version. Even then the major bug with it was loading up two instances in the same mixer insert caused FL to crash, but even with the original version I never had a GUI issue at all. Magma is buggy, I'll fully admit that (but it does allow for some very awesome FX chains). It was one of the first ones I threw out to see if that was the problem. It didn't. Another plugin that has some strange issues from time to time is Magnetic, which was also another I started with. Pretty much every other plugin in that project though hasn't really given me much issue before. That includes all the generators.

I understand that not everyone will have the same plugins. But I thought that by having it out there people might see something that I may have overlooked.

[exmatproton]

I've tried all of that before I even came here.

The issue is literally adding one instance of DIVA causes the problem. Removing it? Issue disappears. I'm not saying there is a bug in DIVA, but it is suspect hence the title of the thread. If I load just the instruments I don't have a problem. If I just load the effects I don't have a problem. If I load say all of OP-X Pro and their associated FX, no problem. Etc . . ., which is why I suspect there to be a bug. Where? I dunno, but if removing a single instance of DIVA fixes the issue I'm having. Then the assertion that there is something wrong or more likely (and what I believe to be the case) a strange interaction between plugins is causing the issue is reasonable I feel. The problem is I cannot tell you which plugs are actually causing the problem.

Yes, I used a lot of Replika and it is the latest version. Even then the major bug with it was loading up two instances in the same mixer insert caused FL to crash, but even with the original version I never had a GUI issue at all. Magma is buggy, I'll fully admit that (but it does allow for some very awesome FX chains). It was one of the first ones I threw out to see if that was the problem. It didn't. Another plugin that has some strange issues from time to time is Magnetic, which was also another I started with. Pretty much every other plugin in that project though hasn't really given me much issue before. That includes all the generators.

I understand that not everyone will have the same plugins. But I thought that by having it out there people might see something that I may have overlooked.

The issue can be related to mutithreading. When you add it, do the problems change (worse/less) when you change the mixer track it relates to? And also, when you insert that Diva and the trouble begins, what happens when you delete all other vst's one by one? Is the issue still there in that particular project file?

[Teksonik]

Magma is buggy

Actually it's rock solid here. I just checked and the GUI flicker issue in FL has been fixed either from Magma's side or FL's.......

The issue can be related to mutithreading.

Bingo ! I bet that's it. I didn't even think of MT being a possible cause. A few weeks ago when I asked Urs why there was no ability to make Multi-threading On by default he responded:

We can't recommend it.

The number of instances that should have it on varies from machine to machine. I think that 2-5 might be okay on a fast machine, but beyond that one should either work without, maybe use "fast" with best for offline rendering or freeze.

We know however that many people experience performance issues with multiple instances using the multicore option. Hence we must keep it a conscience decision to switch it on.

I think exmatproton might have solved the problem.........