2d Joystick Bug Across All Plugins |
2d Joystick Bug Across All Plugins |
Mar 5 2017, 03:08 AM
Post
#1
|
|
Newbie Group: Members Posts: 5 Joined: 30-March 13 Member No.: 12,535 |
Hi,
I've been having a persistent issue for years now with all GRM plugins that use the 2D joystick as part of their interface. The problem is that the joystick often simply doesn't remember the last setting and jumps to a random position once I hit play. This happens when there isn't any automation on the track and the track is set to read (in Pro Tools). If, for example, I set the upper and lower frequency bound in Reson with the joystick and then hit play, about 70% of the time the joystick will jump to another, random position. This also often happens right when I open a session -- the parameters are already different from what they were when I saved the session. Very frustrating to say the least -- I have to resort to writing down all settings in the comment field of the track and printing the track once I feel I dialed in the right settings. I'm on PT HD 12.5.1 on OS X Mavericks, but I've experienced this behavior on multiple workstations with different OS and PT versions. Anybody else experiencing this? Thanks, Alex |
|
|
Mar 5 2017, 04:14 AM
Post
#2
|
|
Newbie Group: Members Posts: 5 Joined: 30-March 13 Member No.: 12,535 |
To follow up on this: I just wrote some automation with the joystick and when I played it back, it still jumped to another position about half of the time! I was hoping as a workaround I could at least write some automation to lock the parameters in.
I also inspected the written automation, and it appears that instead of writing the two parameters that the joystick controls (e.g. first/range in Delays, low/high in Reson) it writes two controls called "Center" and "Width". I wonder if the issue is related to that. |
|
|
Mar 5 2017, 08:55 PM
Post
#3
|
|
Advanced Member Group: Members Posts: 32 Joined: 13-October 13 Member No.: 13,612 |
Hi awelex, i perhaps can not precisely understand all described due to my english, but i tried just now write automation in 2d joysticks (in realtime via computer mouse) in: bandpass, delays, reson, (tested both versions, stereo and mono), and it works propely for me. Well, i mean, automation written, and then i save project and reload it, and during play 2d joystick moves exactly along the path that I moved via mouse, without any random or unexpected movements.
Next I also inspected the written automation, and it appears that instead of writing the two parameters that the joystick controls (e.g. first/range in Delays, low/high in Reson) it writes two controls called "Center" and "Width". Hm, yes, really there is it. Well, I think the existence of an extra pair of parameters should not be a problem in this case. But the combination of these two pairs in recorded state can interact with each other, that obviously (since it impact to the same, but may be with different measures, i not sure). In any case, as i said, it works(automate) properly for me anyway, because my mouse movements affect to record of just one pair (ie "center" and "width"). Maybe really in your case somehow occur unexpected touches to the extra parameters? I think it is not difficult to detect through automation line. (Added: the more parameters - the better ) Tested on: Win7 64bit, Stidio One v3, plugins v370 vst 64it. This post has been edited by Anatolyj: Mar 5 2017, 09:02 PM |
|
|
Mar 5 2017, 09:15 PM
Post
#4
|
|
Newbie Group: Members Posts: 5 Joined: 30-March 13 Member No.: 12,535 |
Hi awelex, i perhaps can not precisely understand all described due to my english, but i tried just now write automation in 2d joysticks (in realtime via computer mouse) in: bandpass, delays, reson, (tested both versions, stereo and mono), and it works propely for me. Well, i mean, automation written, and then i save project and reload it, and during play 2d joystick moves exactly along the path that I moved via mouse, without any random or unexpected movements. Next Hm, yes, really there is it. Well, I think the existence of an extra pair of parameters should not be a problem in this case. But the combination of these two pairs in recorded state can interact with each other, that obviously (since it impact to the same, but may be with different measures, i not sure). In any case, as i said, it works(automate) properly for me anyway, because my mouse movements affect to record of just one pair (ie "center" and "width"). Maybe really in your case somehow occur unexpected touches to the extra parameters? I think it is not difficult to detect through automation line. (Added: the more parameters - the better ) Tested on: Win7 64bit, Stidio One v3, plugins v370 vst 64it. Anatoly, That's the weird thing: the weird jumps don't register on any automation lane. Moreover, they also often occur when there isn't any automation on the track and the track is set to read. Strange... I've recorded a screencap and sent it to the GRM guys. If there is a way to upload it here, I can do that as well. This post has been edited by awelex: Mar 5 2017, 09:15 PM |
|
|
Lo-Fi Version | Time is now: 1st June 2024 - 05:40 AM |