|
|
|
10-21-2021, 08:38 AM
|
#1
|
Human being with feelings
Join Date: Dec 2006
Posts: 462
|
Synth1 crashes v 6.38
Hey all
I've been struggling with crashes on a certain project since I upgraded to v6.38, and have figured out that it has something to do with the Synth1 VSTi (which was working fine before the upgrade). A project will play fine until MIDI starts going through the Synth1 plugin (so if Synth1 is not used until, say, the 1 minute mark, everything is fine).
Anyone else having problems?
|
|
|
10-21-2021, 10:34 AM
|
#2
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
From what I can tell the 64-bit VST version of this plug-in has an issue where it truncates some pointer to 32-bits, and tries to write to it. For now, using the 32-bit VST bridged is a safer bet.
|
|
|
10-21-2021, 10:53 AM
|
#3
|
Human being with feelings
Join Date: May 2009
Location: Polandia
Posts: 3,578
|
I can play through my most recent project no problem, despite having 4 instances of Synth1 in there (1.13 beta3), fiddling with controls and all. Would hate to be forced to use annoying floaty GUIs of bridged plugins I have Synth1 almost everywhere, it's the bee's knees.
|
|
|
10-21-2021, 11:06 AM
|
#4
|
Human being with feelings
Join Date: Dec 2006
Posts: 462
|
Thanks for your replies.
I've done some further investigation, and discovered that it is working fine on at least one other project, and that one instance of it in the project that keeps crashing is also working fine. Also, I was able to copy the working Synth1 into the track that was crashing, loaded the preset, and it ran without crashing. Until I saved, closed, and reloaded the project, when it crashed again...
|
|
|
10-21-2021, 11:08 AM
|
#5
|
Human being with feelings
Join Date: Jun 2012
Location: Spain
Posts: 7,239
|
I agree with Justin, I also had some crashes with the 64 bit version but 32 bit is good.
@zeekat there is an option to force it to be embedded to avoid floating bridged plugins. But I don't know if it is safe or experimental. you can try it for sure.
|
|
|
10-21-2021, 11:19 AM
|
#6
|
Human being with feelings
Join Date: May 2009
Location: Polandia
Posts: 3,578
|
Quote:
Originally Posted by heda
@zeekat there is an option to force it to be embedded to avoid floating bridged plugins. But I don't know if it is safe or experimental. you can try it for sure.
|
Oh wow, I didn't know it's there! Maybe because I tried to find the option _after_ inserting the plugin Thanks!
|
|
|
10-23-2021, 06:16 PM
|
#7
|
Human being with feelings
Join Date: Dec 2006
Posts: 462
|
Possible 64 bit solution
I've been messing around with some things, and I discovered that if I can use v1.12 2010.5 (which is a 64 bit version of the plugin) in this project without issue (at least for the time being). The version that was causing the problem was v1.13 64bit beta3 2014.7.
Not a lot of differences between the 2 versions that I can see; just one more filter type in the newer version, but everything sounds the same.
|
|
|
10-23-2021, 07:07 PM
|
#8
|
Human being with feelings
Join Date: Mar 2009
Posts: 85
|
Quote:
Originally Posted by moribund
I've been messing around with some things, and I discovered that if I can use v1.12 2010.5 (which is a 64 bit version of the plugin) in this project without issue (at least for the time being). The version that was causing the problem was v1.13 64bit beta3 2014.7.
Not a lot of differences between the 2 versions that I can see; just one more filter type in the newer version, but everything sounds the same.
|
Hi moribund,
Can you double-check the version you are referring to?
According to THIS changelog, v1.12 2010.5 is not 64-bit; the 1st 64-bit compatible version is 'Ver1.13 beta1 (2014.6.12)'
https://daichilab.sakura.ne.jp/softs...ng.html#rireki
Or maybe there is another version avail that I am not aware of?
|
|
|
10-24-2021, 07:12 AM
|
#9
|
Human being with feelings
Join Date: Dec 2006
Posts: 462
|
That is the version # - it doesn't say that it's 64 bit, but it doesn't say "(x86)" after the plugin name, so I figured it must be 64 bit.I may be wrong though. I did copy the plugin from another project though, so maybe that has something to do with it?
|
|
|
10-25-2021, 10:05 PM
|
#10
|
Human being with feelings
Join Date: Jan 2019
Posts: 245
|
Quote:
Originally Posted by moribund
That is the version # - it doesn't say that it's 64 bit, but it doesn't say "(x86)" after the plugin name, so I figured it must be 64 bit.I may be wrong though. I did copy the plugin from another project though, so maybe that has something to do with it?
|
x86 means 32 bits
|
|
|
10-26-2021, 12:21 AM
|
#11
|
Human being with feelings
Join Date: Jun 2015
Posts: 8,696
|
Quote:
Originally Posted by DaniloVillanova
x86 means 32 bits
|
Yes, to clarify x86 always implies the 32bit version.
However the vast majority of Intel and AMD 64 bit processors are currently still an x86 CPU, but 64 bit plugins are not known as x86-64 thankfully.
So x86 in this context is always shorthand for the 32 bit version.
|
|
|
10-26-2021, 07:01 AM
|
#12
|
Human being with feelings
Join Date: Dec 2006
Posts: 462
|
Yes - that's my point. Any other 32 bit plugin that I use will have the suffix "(x86)" on the plugin name displayed in the FX list. This one does not, however (like all the 64 bit plugins I use), therefore I assumed that it was not a 32 bit plugin, but 64.
|
|
|
10-26-2021, 11:04 AM
|
#13
|
Human being with feelings
Join Date: Dec 2016
Posts: 373
|
Also had issues: didn't save a few presets, and at the wrong initial id's. Not sure why.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 03:19 PM.
|