Filterscap Step Seq problem in ACID 5...
-
- KVRer
- 9 posts since 2 Sep, 2003
When I choose a preset in Filterscape the plugin works ok when the host is playing, when I hit stop and replay it seems like the step seq preset info of the plugin doesn't start again ... example: BandpassDub - Yeno
-
- u-he
- 30209 posts since 8 Aug, 2002 from Berlin
Hmmm... what exactly is the situation?
Do you stop playback, wait a few moments and continue at the same position? Or do you stop playback, and start again at another position, i.e. song start?
Cheers,
Urs
Do you stop playback, wait a few moments and continue at the same position? Or do you stop playback, and start again at another position, i.e. song start?
Cheers,
Urs-
- u-he
- 30209 posts since 8 Aug, 2002 from Berlin
Okay, I've checked the code and everything *should* work. Maybe ACID does some things different from what the VST specs suggest. I'll try to work out a new concept that is ACID savvy for the next update...
Cheers,
Urs
Cheers,
Urs-
- KVRist
- 67 posts since 26 Sep, 2003 from The Low Lands
I don't know if this is related or not, but I have an issue with Filterscape VA in Orion Platinum 6.1 where the Arp Sync parameter on the arpeggiator changes to 1/64 on all instances of Filterscape VA when I press stop twice (all notes off).
-
- u-he
- 30209 posts since 8 Aug, 2002 from Berlin
There's an easy fix for that:CaseR wrote:I don't know if this is related or not, but I have an issue with Filterscape VA in Orion Platinum 6.1 where the Arp Sync parameter on the arpeggiator changes to 1/64 on all instances of Filterscape VA when I press stop twice (all notes off).
It's probably so that the Sync Parameter is MidiLearned to the ModWheel or some other controler that's reset to zero. Just right-click the Parameter twice to un-learn it and the problem should be gone.
You can also have a look at this file in WordPad:
C:\Program Files\u-he\Support\com.u-he.FilterscapeVA.midimap.txt
Hope this helps!
Cheers,
Urs-
- KVRist
- 67 posts since 26 Sep, 2003 from The Low Lands
In Orion a plugin can be configured to use either Midi CC or VST parameter automation. The default is VST parameter automation and in this mode midi controller data from my keyboard has no effect on any of the parameters of the plugin unless I assign a CC to a VST parameter first. I am pretty sure I didn't do this, certainly not for all instances.
It is possible that Orion itself sends some midi data to the plugin besides 'all notes off', so I will give your suggestion a try when I get home.
Thanks for the quick response
It is possible that Orion itself sends some midi data to the plugin besides 'all notes off', so I will give your suggestion a try when I get home.
Thanks for the quick response
-
- u-he
- 30209 posts since 8 Aug, 2002 from Berlin
Hey,
I'm pretty certain that it's related to Filterscape's internal MidiLearn. When I implemented it, I listened to some people who wanted a quick solution, and so it's only a right-click and boom - for all instances. Unfortunately, this leads to quite some accidental assignments every now and then, so that I'm reconsidering the whole scheme for future releases. So that in future it can't happen in a *hidden* way.
Sheesh... I got so many reports like yours, I just need to read two words and know what's up... I'm sure that two right-clicks on the Sync control will do the trick (or just erase that file I mentioned before launching Orion).
Cheers,
Urs
I'm pretty certain that it's related to Filterscape's internal MidiLearn. When I implemented it, I listened to some people who wanted a quick solution, and so it's only a right-click and boom - for all instances. Unfortunately, this leads to quite some accidental assignments every now and then, so that I'm reconsidering the whole scheme for future releases. So that in future it can't happen in a *hidden* way.
Sheesh... I got so many reports like yours, I just need to read two words and know what's up... I'm sure that two right-clicks on the Sync control will do the trick (or just erase that file I mentioned before launching Orion).
Cheers,
Urs-
- KVRist
- 67 posts since 26 Sep, 2003 from The Low Lands
Works like a charm, thanks very much!Urs wrote:
There's an easy fix for that:
It's probably so that the Sync Parameter is MidiLearned to the ModWheel or some other controler that's reset to zero. Just right-click the Parameter twice to un-learn it and the problem should be gone.
You can also have a look at this file in WordPad:
C:\Program Files\u-he\Support\com.u-he.FilterscapeVA.midimap.txt
Hope this helps!
Cheers,
-
- u-he
- 30209 posts since 8 Aug, 2002 from Berlin
-
- KVRAF
- 2336 posts since 13 Oct, 2002 from Terra Firma
I just wanted to let you know that I've had the same problem of ACID changing the preset of a VST once playback is stopped and then resumed.
I first noticed this problem while using CamelSpace. I contacted CamelAudio who discovered a workaround. This problem does not occur when the preset is chosen in the ACID preset window. The problem only occurs when the preset is chosen in the plugins GUI.
Unfortunately, ACID is unable to see Filterscapes presets so it's impossible to choose a preset via the ACID GUI. I've not been able to use Filterscape in ACID because of this.
CamelAudio believe it is a problem in ACID that needs to be fixed. They claim that their plugins follow the VST spec fully. Because this problem occurs with other plugins I believe it must be caused by ACID. CamelAudio have contacted Sony Support about this issue. I've posted a thread in the ACID support forum as well.
I think it would be worth contacting Sony Support as this would encourage them to fix this problem in the next update.
I first noticed this problem while using CamelSpace. I contacted CamelAudio who discovered a workaround. This problem does not occur when the preset is chosen in the ACID preset window. The problem only occurs when the preset is chosen in the plugins GUI.
Unfortunately, ACID is unable to see Filterscapes presets so it's impossible to choose a preset via the ACID GUI. I've not been able to use Filterscape in ACID because of this.
CamelAudio believe it is a problem in ACID that needs to be fixed. They claim that their plugins follow the VST spec fully. Because this problem occurs with other plugins I believe it must be caused by ACID. CamelAudio have contacted Sony Support about this issue. I've posted a thread in the ACID support forum as well.
I think it would be worth contacting Sony Support as this would encourage them to fix this problem in the next update.
-
- u-he
- 30209 posts since 8 Aug, 2002 from Berlin
Hiya munchkin,munchkin wrote:I just wanted to let you know that I've had the same problem of ACID changing the preset of a VST once playback is stopped and then resumed.
this sounds yet like another weird issue! - There's an official, well documented method for plugins to load presets internally, and in turn inform the host about it. The problem you describe sounds definately like a bug in ACID.
I have no contacts to Sony... could you (or anyone) PM me the support contact for ACID?
Cheers,
Urs-
- KVRAF
- 2336 posts since 13 Oct, 2002 from Terra Firma
I don't have a named contact at Sony but here's the Sony Support page.Urs wrote:Hiya munchkin,munchkin wrote:I just wanted to let you know that I've had the same problem of ACID changing the preset of a VST once playback is stopped and then resumed.
this sounds yet like another weird issue! - There's an official, well documented method for plugins to load presets internally, and in turn inform the host about it. The problem you describe sounds definately like a bug in ACID.
I have no contacts to Sony... could you (or anyone) PM me the support contact for ACID?
Cheers,
Perhaps you could email their tech support? I hope they can sort this out. I've never had problems like this with Sonar 4 or Live 4.
-
- KVRAF
- 2336 posts since 13 Oct, 2002 from Terra Firma
I thought I'd also report that Filterscape VA doesn't show up in the Soft Synth folder in ACID 5. The VST Filterscape plugins show up but not the synth.
I've tried re-registering all my vsti's in ACID but it doesn't seem to help.
I've tried re-registering all my vsti's in ACID but it doesn't seem to help.