|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
Dandruff
on Aug 9, 2011, 7:12am:
1. Problem:
-> load GlissEQ
-> doubleclick EQ area to insert new EQ point
-> Undo (REAPER's Undo)
Result: GlissEQ unloaded
Expected: Undo of EQ point insertion
2. Problem:
-> set first EQ in first group to Dyn=0
-> save as default preset
-> reload GlissEQ
-> doubleclick EQ area to insert new EQ point
Result: Dyn=100
Expected: Dyn=0
-> load GlissEQ
-> doubleclick EQ area to insert new EQ point
-> Undo (REAPER's Undo)
Result: GlissEQ unloaded
Expected: Undo of EQ point insertion
2. Problem:
-> set first EQ in first group to Dyn=0
-> save as default preset
-> reload GlissEQ
-> doubleclick EQ area to insert new EQ point
Result: Dyn=100
Expected: Dyn=0
Aleksey Vaneev
on Aug 9, 2011, 2:18pm:
Reaper's undo won't work. Reaper's undo will work only if you change automatable parameters. VST specification has no means to provide action automation.
Problem 2 will be probably fixed in the next update - this problem does not exist in our development build of GlissEQ.
Problem 2 will be probably fixed in the next update - this problem does not exist in our development build of GlissEQ.
Aleksey Vaneev
on Aug 9, 2011, 2:19pm:
Moreover, I think there can be problem with Reaper's undo even when you change automatable parameters only.
Dandruff
on Aug 9, 2011, 3:10pm:
Aleksey Vaneev: Moreover, I think there can be problem with Reaper's undo even when you change automatable parameters only.
What problem?
Dandruff
on Aug 9, 2011, 3:10pm:
Aleksey Vaneev: Problem 2 will be probably fixed in the next update - this problem does not exist in our development build of GlissEQ.
Thanks!
Aleksey Vaneev
on Aug 9, 2011, 5:24pm:
Aleksey Vaneev: Moreover, I think there can be problem with Reaper's undo even when you change automatable parameters only.
Dandruff: What problem?
When I move control points 1, 2, etc that are automated, the Reaper's undo does not always follow these changes.
Dandruff
on Aug 9, 2011, 5:46pm, edited 1 time(s), last modified on Aug 9, 2011, 5:48pm:
You're right. Very strange behaviour. Their own plugins don't show this. Any idea?
I just now that they implemented some timing limit so that too many changes in short time don't flood the undo history ...
I just now that they implemented some timing limit so that too many changes in short time don't flood the undo history ...
Aleksey Vaneev
on Aug 9, 2011, 6:27pm:
The idea is simple - it's a bug of some kind.
Dandruff
on Aug 10, 2011, 6:07am:
Ok, I've entered it into the REAPER bug tracker: http://forum.cockos.com/project.php?issueid=3485
Maybe you can vote or chime in there ...
Maybe you can vote or chime in there ...
Aleksey Vaneev
on Aug 10, 2011, 11:03am:
Thanks for posing the bug report. I have nothing to add.
|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
Copyright © 2002-2012 Aleksey Vaneev - Terms of Use - Privacy Policy - About Voxengo - Questions & Answers