Plogue OPS7 (bit-accurate DX7 emulation!)
-
gentleclockdivider gentleclockdivider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=203660
- Banned
- 6787 posts since 22 Mar, 2009 from gent
Time to update then , ( sorry should have done that before reporting it )
Eyeball exchanging
Soul calibrating ..frequencies
Soul calibrating ..frequencies
-
gentleclockdivider gentleclockdivider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=203660
- Banned
- 6787 posts since 22 Mar, 2009 from gent
JUst downloadd the laterst version and encountered another bug
WHen the step sequencer has no steps at all ( and assigned to gain of operator ) there is always a short burt of sound at the beginning , just the same as if there is only 1 step activated .





Vst 2 plugin , 64 bit , win 10
WHen the step sequencer has no steps at all ( and assigned to gain of operator ) there is always a short burt of sound at the beginning , just the same as if there is only 1 step activated .





Vst 2 plugin , 64 bit , win 10
Last edited by gentleclockdivider on Fri Jan 05, 2024 11:08 pm, edited 1 time in total.
Eyeball exchanging
Soul calibrating ..frequencies
Soul calibrating ..frequencies
-
- KVRian
- 928 posts since 3 Aug, 2001 from Montreal
There is a similar bug that we fixed in csC64 already, and needs to be backported to OPS7. Really sounds like the same issue
was:
v1.004 December 15th 2023
Fixed Step Modulators of size 1 not re-saved properly
was:
v1.004 December 15th 2023
Fixed Step Modulators of size 1 not re-saved properly
David Viens, Plogue Art et Technologie Inc. Montreal.
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
I'm getting some z-layer bugs on mouse hover. Example:
1. Pick algorithm 19
2. Notice the line going around operator 6
3. Open Settings
4. Hover around the line mentioned in step 2
Same thing in algorithm 17 with line going around operator 2.
Same thing in algorithm 4 with line starting from operator 6 all the way down to operator 4.
Same thing in algorithm 6 with line around operators 6 and 5.
Same thing in algorithms 20 and 21 with line around opeator 3.
Same thing in algorithms 22-25 with line around operator 6.
Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.
1. Pick algorithm 19
2. Notice the line going around operator 6
3. Open Settings
4. Hover around the line mentioned in step 2
Same thing in algorithm 17 with line going around operator 2.
Same thing in algorithm 4 with line starting from operator 6 all the way down to operator 4.
Same thing in algorithm 6 with line around operators 6 and 5.
Same thing in algorithms 20 and 21 with line around opeator 3.
Same thing in algorithms 22-25 with line around operator 6.
Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.
-
- KVRAF
- 2064 posts since 13 Dec, 2016
Have you tried Bitwig?EvilDragon wrote: Fri Jan 05, 2024 10:47 pm
Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.
Its over for Bitwig--CUBASE WON !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
- KVRian
- 1025 posts since 1 Mar, 2003 from Exmoor
I'm seeing the same here too. Both vst2 and vst3 - in bidule/windows10.EvilDragon wrote: Fri Jan 05, 2024 10:47 pm Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.
γνῶθι σαὐτόν
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
Seems to work fine in FL and Bitwig. Doesn't work in Live, Reaper, Maschine.enCiphered wrote: Fri Jan 05, 2024 10:52 pmHave you tried Bitwig?EvilDragon wrote: Fri Jan 05, 2024 10:47 pm
Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.
-
Korg Supporter Korg Supporter https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=386399
- KVRAF
- 1879 posts since 4 Oct, 2016
https://www.offthematrix.net/product-pa ... 02-patchesdavidka wrote: Sat Jan 06, 2024 8:39 pm Can you reccommend some soundsets which are particularly shining with OPS7?
I am aware of that huge DX7 sysex pack, but that's too much to absolve.
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
@davidv@plogue Just making sure you saw this!EvilDragon wrote: Fri Jan 05, 2024 10:47 pm I'm getting some z-layer bugs on mouse hover. Example:
1. Pick algorithm 19
2. Notice the line going around operator 6
3. Open Settings
4. Hover around the line mentioned in step 2
Same thing in algorithm 17 with line going around operator 2.
Same thing in algorithm 4 with line starting from operator 6 all the way down to operator 4.
Same thing in algorithm 6 with line around operators 6 and 5.
Same thing in algorithms 20 and 21 with line around opeator 3.
Same thing in algorithms 22-25 with line around operator 6.
Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.
-
- KVRian
- 928 posts since 3 Aug, 2001 from Montreal
Did. did you try v1.120 released today? Not saying it fixes all that, but we added a few refreshes.EvilDragon wrote: Wed Jan 10, 2024 3:23 pm@davidv@plogue Just making sure you saw this!EvilDragon wrote: Fri Jan 05, 2024 10:47 pm I'm getting some z-layer bugs on mouse hover. Example:
1. Pick algorithm 19
2. Notice the line going around operator 6
3. Open Settings
4. Hover around the line mentioned in step 2
Same thing in algorithm 17 with line going around operator 2.
Same thing in algorithm 4 with line starting from operator 6 all the way down to operator 4.
Same thing in algorithm 6 with line around operators 6 and 5.
Same thing in algorithms 20 and 21 with line around opeator 3.
Same thing in algorithms 22-25 with line around operator 6.
Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.![]()
David Viens, Plogue Art et Technologie Inc. Montreal.
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
The refreshes when keyboard is toggled on-off is fixed, but the wires bleeding through to Settings dialog on mouse hover still happens 
-
- KVRian
- 1025 posts since 1 Mar, 2003 from Exmoor
The virtual keyboard issue is fixed by the latest update. Thanksdavidv@plogue wrote: Wed Jan 10, 2024 3:30 pmDid. did you try v1.120 released today? Not saying it fixes all that, but we added a few refreshes.EvilDragon wrote: Fri Jan 05, 2024 10:47 pm Oh and there's a complete GUI borkedness when toggling virtual keyboard on/off. Over here in Reaper, the whole GUI goes black. Have to close then reopen GUI to fix.
γνῶθι σαὐτόν
-
- KVRian
- 928 posts since 3 Aug, 2001 from Montreal
Yeah that is a day one known issue which would require a hell of a lot of code to fix.EvilDragon wrote: Wed Jan 10, 2024 4:09 pm The refreshes when keyboard is toggled on-off is fixed, but the wires bleeding through to Settings dialog on mouse hover still happens![]()
Cheers
David Viens, Plogue Art et Technologie Inc. Montreal.
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
https://bsky.app/profile/plgdavid.bsky.social
https://plogue.com
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
Damn!
I'd have figured it's just a component z-layer ordering sort of thing. Why is the hover even bleeding through below the settings dialog, that should not happen... Maybe onMouseHover could be overriden for the settings dialog (I'm assuming it's a separate JUCE component) so that it eats the event then returns false?
I'd have figured it's just a component z-layer ordering sort of thing. Why is the hover even bleeding through below the settings dialog, that should not happen... Maybe onMouseHover could be overriden for the settings dialog (I'm assuming it's a separate JUCE component) so that it eats the event then returns false?
