paulo

After a long and ultimately unsatisfying first day, I mentally filed most of the Reaktor stuff under Can't Be Bothered.

Those who aren't don't have to wait for the sales.?

FWIW using Cakewalk with " run as administrator" option and then running VST scan solved my issue where the scan was only picking up the 32 version dll's and not the 64. I had RAA enabled by default in Platinum but I hadn't done so when I installed the bandlab version, because I remember reading somewhere here or on the old forum that this was not recommended, but it looks like this was the problem for some reason. I have no idea as to the how or why or even if that should make any difference whatsoever to a VST scan, just saying that it worked when I did it.

Thanks. It's even less funny now than when I didn't get it.

Anyone gonna splain it for me?

Nah, there ain't no Freds to preview on there.

It was a smaller pop up window, but the old forum also did this as do the few others that I frequently visit.

Thanks for the info. I'm not near my DAW pc now, but I'll check that next time although I haven't changed any of the default settings. I have some 32 bit plug ins that I still use and they work fine as they did in Platinum so that's not an issue per se. In the case where the scan only recognises the 32 bit version when the 64 is available, removing the 32 bit version from the scan path only resulted in me not having any version at all. If I open Platinum 64 the 64 plug in is the one that loads as it always did. Anyway, don't want to hijack the OP's thread so I'll look at the defaults and scan log next time and see what happens.

I didn't get it when I read it on that internet joke site either.

I've just tried SI drums in Platinum, X3 and 8.5PE 32 bit versions (also win7pc ) and it works ok in all, so installing the bandlab version did not affect SI drums in my case. However, in my experience the VST scanner in the bandlab version does have it's quirks. When I installed it a few weeks ago my initial scan failed to pick up many VST's that had previously been working fine in Platinum X64. Repeated scans consistently completed without picking them up so they were omitted from my custom vst menus. The only way I found to get around this was to move the .dll's in question to another folder and add that to the vst scan list where by and large they were picked up. Two (I don't remember which now) I could not get it to recognise even doing this, but they were minor things that I never really use anyway, so I gave up on them. I still have a couple where it will only recognise the 32 bit version of the plug in even though the 64 bit dll's are where they always were and worked fine beforehand. If I removed the 32 bit .dll's I get nothing at all as it still doesn't pick up the 64 bit version. Even moving these .dll's to an alternate folder had no effect so I can only use those as 32 bit plug-ins now, which is ok as they work, but pretty ironic for software that champions the 64 bit cause and is 64 bit only now. It took a whole afternoon of fighting the bloody thing to get as far as I did and in the end I just gave up as all the important stuff to me was finally present and correct. Not an answer to your problem I know, but sometimes knowing that you're not alone helps with the frustration.

In my case c:\Users\Owner\AppData\Roaming\IgniteVST\Sektor\Expansions

Cakewalk is no good if you are in a punk band then.?

Thank you for explaining. I thought that there may be something in there that would point the way to somebody in the know so figured it was worth a try before going down official channels and giving someone more work to do.

There was a known VST2 issue with Izotope Neutron in Sonar when that was released and the workaround until it was fixed was to remove the VST2 version and use VST3 version only, so I figured I'd try the VST3 and see what happened. Thank you for the explanation of the technical. I have no clue about that side of things. CW have responded to say that they are on the case. Having been informed that using the VST3 version does not cause the same issue, Initial Audio seem content to leave it at that and show no apparent interest in investigating the issue further.

Update for anyone interested..... As suggested I have submitted the .dmp file to CW support and await their response. In the meantime I have discovered that using the VST3 version of the plugin does not cause the issue, so I at least have a workaround. I'm clueless as to why that might be and have also submitted that info to CW. I thought I read somewhere way back that CW will automatically use the VST3 version of a selected plugin anyway if one is available. Or did I dream that? While I was discovering this, the plugin vendor responded to suggest that maybe the problem is being caused by me using the VST3 version and that I should make sure I'm using VST2. I've now updated them that it appears to be quite the opposite and await their response.

Thank you for the explanation. This is the kind of thing that I have no clue about.

Thanks for the info. If I can't solve the issue myself I'll do that tomorrow. I posted the problem here first as I was hoping to be able to solve it without giving the bakers more work to do.

I haven't tried that, but to be clear it's not the unfreezing itself that causes the crash, but whatever I do afterwards - ie change a parameter on the synth UI or playing a note on the keyboard.

To answer both points it happens every time in every project I've tried it in, new or old, so I would say that everywhere is fairly descriptive of where it is happening.

Thanks Larry. As you say there is little doubt what is causing the crash I just wondered if the computer gibberish included in the error message gave any clue as to why. It seems that others who have this plug-in are not experiencing this issue, so I just was hoping that somebody could suggest why before going down official channels and causing possibly unnecessary work for someone.

Cakewalk constantly crashing after unfreezing a frozen synth track instance of Sektor Synth and attempting changes.... Can any of the esteemed computer folk please translate this error message into English for me? Win 7 64 latest Cakewalk version if it matters, but also happens in Platinum. TIA

Wish I could say the same.

Bought it not because I really needed it but figured it was cheap enough to not worry about if I didn't use it much. Really wish I hadn't now - crashes both Cakewalk and Platinum every time without fail after unfreezing a frozen track and then attempting to alter anything. Not Good.?

My doctor has just told me that I have only 90 minutes to live so I've decided to spend them watching a game in the Womens Football World Cup. That will make it seem much longer.

Thanks for the info.