DIVA Bug . . . maybe

[APZX]

So, I've encountered the most baffling issue I've had in a very long time. I'm making a track and save it for the night; come back the next morning to discover that I have a full scale DC spike (it is really similar to an impulse honestly) that I can remove only by muting the Master or reseting the entire track. After some lengthy troubleshooting I find that removing just one instance of the three for DIVA in the track I alleviate the DC spike. Removing pretty much any other combination of plugins does not.

Now, I'm using FL 12.1.3 32-bit. I know it has issues with VSTs, but this is the only time I've had an issue with DIVA other than having no CPU power left over. I'm running the latest version of DIVA. If it is of any help I did open the project in FL 64-bit just to see if the issue carried over. It does not. Now, in FL 64-bit the only change is the DAW and the like 4 or 5 FL plugs I have in the track. Other than each VST is still the 32-bit version and they're running bridged.

I can provide more information if requested, but I honestly don't know what else you'd like to know.

[Teksonik]

Could it be an issue with iLBridge ?

[APZX]

Teksonik,
I'm not running the 64-bit versions of the plugins. This is mainly due to the fact that I feel FL 64-bit is still a bit too buggy to really use all the time. So, I'm running the 32-bit versions of everything. What I did was open the project with FL 64-bit just to see if that would still have the problem. These are the very same plugins (32-bit) just not running in FL 32-bit. With some searching it appears that strange things like this can sometimes be remedied by using the ILbridge.

[Teksonik]

I feel FL 64-bit is still a bit too buggy to really use all the time.

I use only 64 bit plugins on my studio computer. I have well over 200 plugins installed on that system including DIVA. They are not the least bit buggy even in FL 12.

I'm using FL 12.1.3 32-bit. I know it has issues with VSTs.

So you use the 32 bit version even though you know it has issues ?

[APZX]

Yes because FL 64-bit has issues on my setup and there should be no reason that the 32-bit version causes an issue that the 64-bit version doesn't. FL 64-bit still has to mature because it just isn't as stable as the 32-bit version, and has more issues than 32-bit version. Just because you're not having issues on your particular setup with your configuration of plugins doesn't mean others do not experience issues. I use Reaper 64-bit for actually mixing tracks down and I've got 200+ plugins with a handful of 32-bit ones because there aren't good replacements in 64-bit. That gives me no headaches at all, but FL? There are tons of issues that need to be sorted out. When the 64-bit version of FL matures in about 1.5 versions I'll move to it, but as of right now? It causes more complications and headaches than it is worth for me.

Look I'm not saying this is a bug with DIVA, but it really is peculiar because this is the only time I've had an issue like this that I cannot figure it out. Removing a single instance of DIVA removes the problem. That doesn't sound or strike you as odd? I'm trying to figure out what exactly is causing the issue so that I can work it out and continue the project.

[Teksonik]

FL 64-bit still has to mature because it just isn't as stable as the 32-bit version, and has more issues than 32-bit version.

No, the 64 bit version doesn't need to "mature" or have more issues and is just as stable as the 32 bit version....on three different systems here.

Have you brought this issue up at the FL Forums ? I see no evidence on those forums indicating there is any difference in performance or stability between the 32 bit and 64 bit versions.

If you follow the FL forums you know I'm one of the most vocal critics of FL Studio but in this case I see no evidence to back up your assertion that the 64 bit version is in any way inferior to the 32 bit version.

[APZX]

No, the 64 bit version doesn't need to "mature" or have more issues and is just as stable as the 32 bit version....on three different systems here.

Have you brought this issue up at the FL Forums ? I see no evidence on those forums indicating there is any difference in performance or stability between the 32 bit and 64 bit versions.

If you follow the FL forums you know I'm one of the most vocal critics of FL Studio but in this case I see no evidence to back up your assertion that the 64 bit version is in any way inferior to the 32 bit version.

It does need to mature. I'm not running anything crazy here. But if it is "mature" then why do I get visual glitches and issues with memory allocation? I'm not running a crazy system or strange 3rd party VSTs here. I know a few of the ones I use have issues and I don't include those in my judgement on the quality or stability of FL because I don't believe it to be fair. These are issues that I don't get with Reaper. If it were mature I'd not get visual glitches or have stability problems with large projects. FL 64-bit has all of those issues. So, no it isn't mature. Additionally, I never said inferior nor was I implying such. That is putting words into my mouth. I stated that FL 64-bit for me has to mature before I'll use it because it has too many issues for me. Some people may never encounter the issues I get. I may never encounter issues that other folks may get. That doesn't change the fact that I've encountered issues that make me want to wait to switch over to FL 64-bit. It is that simple.

Just a FYI since you seem so confused as to why I won't run 64-bit despite my issues with it. I'll let you know what VSTs are running in the project. DIVA, TyrellN6, Z3TA+ 2, SynthMaster Player, SQ8L, OP-X Pro II, Poly-Ana, Cypher, Fusor, and Massive are the 3rd party VST generators in use. As for effects it is namely Nomad Factory plugins including: British NEQ-1972, BT Tempo Delay DL3D-3, EQ 9063B AllTech, BT Analog Phaser APH2S-3, Magnetic, Magma (using only the built in effects no external VSTs). For the others it is: Native Instruments Replika, Cytomic The Glue, Bootsie's Thrillseeker VBL, NastyVCS, ValhallaVintageVerb, ValhallaRoom, D16 Syntorus & Toraverb, and finally Classic Delay. I've made much larger projects using these exact same plugins and yet I'm getting a full scale DC spike and removing a single instance of DIVA removes that DC spike.

Rather than try and campaign me into using a version of software that doesn't work well for me, I'd like some help in figuring out what is going on, and I came to the U-He forum because the only plugin I can narrow it down to is an U-He plugin. That is why I came here in the first place. There is something strange going on and I'm trying figure out how to fix it. If you don't want to help that is fine, but if you continue to insist that the problem must stem from the notion that I'm not using the 64-bit version of things then you're not helping. If you can show beyond any reasonable doubt that the issue is caused by the 32-bit nature of things then I'll switch over. So, please lets keep this to the issue at hand rather than talking about something that is not related to what I'm experiencing.

[Teksonik]

But if it is "mature" then why do I get visual glitches and issues with memory allocation? FL 64-bit has all of those issues. So, no it isn't mature.

There is no difference in the performance or stability of FL Studio 32 bit or 64 bit.......here. I'm simply reporting a fact. So the evidence tells me yes it is mature. If you're having problems with your system then report the issue at the FL Studio forums. What you are experiencing is called a "System Specific" issue. Otherwise we'd be seeing a lot more people posting that the 64 bit version of FL has issues that the 32 bit version does not. We'd be seeing more people say "Hey DIVA causes issues in 64 bit FL Studio". So lacking the evidence of those posts we can only surmise it is most likely a system specific issue.

Additionally, I never said inferior nor was I implying such. That is putting words into my mouth. I stated that FL 64-bit for me has to mature before I'll use it because it has too many issues for me.

To say that the 64 bit version needs to "mature" or "has too many issue" implies that it is inferior to the 32 bit version which it is not. I'm not putting words in your mouth I'm simply reading what you wrote.

Anyway I am trying to help but if you say XYZ is broken and XYZ works just fine here all I can do it report that fact. I have used the 64 bit version of DIVA in the 64 bit version of FL Studio 12.1.3 without issue.....it works just fine so all I can do is report that fact. I don't install 32 bit plugins on my 64 bit studio system so can't test 32 bit plugin in 64 bit host. Try starting a new project with only DIVA loaded. If the issue can be reproduced with that DIVA only project you can post it and the people at U-HE can test it.....

Like I said along with this thread post a thread at the ImageLine forums and maybe someone there can help with your issues with the 64 bit version. If it really isn't "mature" I'm sure IL would like to know.........

[exmatproton]

Yes because FL 64-bit has issues on my setup and there should be no reason that the 32-bit version causes an issue that the 64-bit version doesn't. FL 64-bit still has to mature because it just isn't as stable as the 32-bit version, and has more issues than 32-bit version. Just because you're not having issues on your particular setup with your configuration of plugins doesn't mean others do not experience issues. I use Reaper 64-bit for actually mixing tracks down and I've got 200+ plugins with a handful of 32-bit ones because there aren't good replacements in 64-bit. That gives me no headaches at all, but FL? There are tons of issues that need to be sorted out. When the 64-bit version of FL matures in about 1.5 versions I'll move to it, but as of right now? It causes more complications and headaches than it is worth for me.

Look I'm not saying this is a bug with DIVA, but it really is peculiar because this is the only time I've had an issue like this that I cannot figure it out. Removing a single instance of DIVA removes the problem. That doesn't sound or strike you as odd? I'm trying to figure out what exactly is causing the issue so that I can work it out and continue the project.

I have no issues running FLS 64 bit (latest 12.1 version). Not with Diva, or any other vst i own. Your spiking could be related to hardware/software, whatever. But really, your claim x64 FLS 12.1 isn't matured, is just bollocks.

[Teksonik]

Now, I'm using FL 12.1.3 32-bit....... If it is of any help I did open the project in FL 64-bit just to see if the issue carried over. It does not.

Yes because FL 64-bit has issues on my setup and there should be no reason that the 32-bit version causes an issue that the 64-bit version doesn't.

I think you're confused about what needs to mature.......

Anyway good luck I hope you find a solution.........

[exmatproton]

Now, I'm using FL 12.1.3 32-bit....... If it is of any help I did open the project in FL 64-bit just to see if the issue carried over. It does not.

Yes because FL 64-bit has issues on my setup and there should be no reason that the 32-bit version causes an issue that the 64-bit version doesn't.

I think you're confused about what needs to mature.......

Anyway good luck I hope you find a solution.........

So what he is saying is, that the 32 bit version of Diva spikes in the 32 bit version of FLS12.1.....


Use FLS 64bit with the 64 bit version of Diva! No issues here

Edit: i must note that in Reaper, Sonar, Renoise and FLS 12.1, the amount of voices that can be played, in the same quality over the 32 and 64 bit versions, is the same, roughly. On my system, i get the best performance in all those daw's when using 64 bit. Including FLS. The trouble begins when i use some kind of bridging

[APZX]

FL 64-bit does have issues with the project, but slightly different. In FL 64-bit I cannot jog the track, and will at times just crash playing through the track. It causes a MIDI error with DIVA and TyrellN6 and crashes.

Still you're being accusatory to me for not using FL 64-bit. That is not what I came here for. I have visual bugs, MIDI issues, more memory leaks than the 32-bit version, and general stability problems with the 64-bit version. It isn't inferior nor am I implying such, but what I am saying is the 64-bit version has issues "for me". So, yes they're more than likely system specific. I'm not doubting that nor did I ever say otherwise. So, to me and in my experience FL 64-bit isn't mature yet. Just drop the whole thing about the 64-bit version, okay? I'd report the problems on the Image-Line forum, but I suspect I'd get about the same treatment there as I am here from the threads I've read on there. Which is probably why I don't venture there often.

So, please leave the FL 64-bit is inferior or whatever out this and lets strictly talk about the problems that I'm experiencing. I'm willing to talk about them and assist and do what I can to try and resolve this. But if you insist that IT must be that I'm not using the 64-bit version of FL then I'm not going to tolerate it and I'm going to report both of you because this is bollocks and frustrating. I've spent more time in this thread trying to bring the thread back onto topic. I'm trying to be reasonable about this but you're not listening to what I have to say and just focusing on something completely unrelated to the issue at hand. That is I'm experiencing repeatable problems related to U-He products. Both 32-bit AND 64-bit.

Please lets just talk about the issue and see where things go.

[Teksonik]

Yes you're right. You'd better not even try the FL forums if you are going to be that thin skinned. They would eat you alive........

What are you going to "report" me for ? This ?

Anyway good luck I hope you find a solution.........

I've given you what you need to find out if this is a DIVA problem or not....simply create a new project in FL using only DIVA. If your issues can be reproduced in that project then post the .flp file for people to test. If they get them same results then there may be a bug. If they can't reproduce the issue then it's likely something with your system/setup and since you won't seek help for the FL issues.....like I said good luck.......

[APZX]

Yes you're right. You'd better not even try the FL forums if you are going to be that thin skinned. They would eat you alive........

What are you going to "report" me for ? This ?

You're being instigative and ignoring what I'm saying, and trying to push an option that doesn't work for me for reasons that I've already said. Further, you're just not helping or giving any other avenues. If it isn't something that you can help with then just don't post. Why is it so hard to be civil and reasonable? Why side step the original question and focus on something that isn't the issue? Besides that last quip this post is reasonable.

Also, the reason I don't got to the IL forums is because in general I don't like the community there.

I've given you what you need to find out if this is a DIVA problem or not....simply create a new project in FL using only DIVA. If your issues can be reproduced in that project then post the .flp file for people to test. If they get them same results then there may be a bug. If they can't reproduce the issue then it's likely something with your system/setup and since you won't seek help for the FL issues.....like I said good luck.......

I've done that before with a beta version of DIVA and other than a couple of strange memory access violations I didn't have a problem. 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.

[exmatproton]

Yes you're right. You'd better not even try the FL forums if you are going to be that thin skinned. They would eat you alive........

What are you going to "report" me for ? This ?

You're being instigative and ignoring what I'm saying, and trying to push an option that doesn't work for me for reasons that I've already said. Further, you're just not helping or giving any other avenues. If it isn't something that you can help with then just don't post. Why is it so hard to be civil and reasonable? Why side step the original question and focus on something that isn't the issue? Besides that last quip this post is reasonable.

Also, the reason I don't got to the IL forums is because in general I don't like the community there.

I've given you what you need to find out if this is a DIVA problem or not....simply create a new project in FL using only DIVA. If your issues can be reproduced in that project then post the .flp file for people to test. If they get them same results then there may be a bug. If they can't reproduce the issue then it's likely something with your system/setup and since you won't seek help for the FL issues.....like I said good luck.......

I've done that before with a beta version of DIVA and other than a couple of strange memory access violations I didn't have a problem. 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.

"strange memory access violations" are DAW/system related, as far as i know. Try demo versions of other DAW's to check if it is really Diva that's giving the problem. Really, Diva and Teyrell for that matter, running awesome over here. Check your FLS settings, your plugin settings and try other DAW's!