VP: Bug Reports
From Sonikmatter
If you are making a bug report, please read though the list of Currently Reported Bugs first, to make sure that the bug hasn't already been reported. Ensure that you are running the latest release of VAST Programmer, as your bug may already be fixed in a later version. Please indicate how to reproduce the bug, the Kurzweil model you are using, the OS you are running, and any workarounds that you can find.
BUG: Enter your descriptive title here like this.
Indicate: (OS:Win/Mac) (Kurz:K2661/K600/K2500/K2000/etc.)
Put description of the bug including how to reproduce here.
BUG: This is an example bug report.
OS:Mac Kurz:K2500
VP hangs when I push Setup and Program buttons alternately very quickly
Currently Reported Bugs
V 0.2.4 Beta
Order of Buttons in Edit Mode
on my k2600xs, they are:
- Mute1 Previous Pg
- Mute2 Mark
- Mute3 Jump
- FX Bypass Compare
Not sure if it's a design decision by you, but I'm surprised no one ever brought this up before.
chuck
V 0.2.3 Beta
NOT A BUG - Doing a LOPTS on a predefined parameter
(eg Program Editor - Pad) loses the drop down box and instead gives a slider.
Is there any way to get the original setting back?
Lopts Inc seems to work OK.
This is not a bug although you did not get what you expected (I doc issue). As you observed LOPTS INC did what you wanted. Although it is easy for human beings, there is no "good way" to determine when a numeric parameter is best represented by a range (LOPTS assumes this) or an enumerated set of values (LOPTS INC does this). If you can think of a "good way" to distinguish these cases I will put this logic into LOPTS (and thus call LOPTS INC implicitly).
NOT A BUG - Doing a LOPTS on the programs searches through all programs by number
Doing a LOPTS on the programs searches through all programs by number rather than scrolling up. This means that it searches empty banks.
Wouldn't it be more efficient to send a datainc command and then read the parameter value. That way empty programs won't be interrogated.
---
I'm glad this came up. For paramters that contain the names (references) of objects there is a much better feature that should be employed.
If you LOPTS PROGRAM on a paramater field that contains a Program name (for example), VP will use the "logical" collection of names collected using [VP:Parameter_Options | UPOBS]. LOPTS PROGRAM only needs to be done once, UPOBS should be done anytime you want to update the list of object names.
PS. I thought I had set all of the "logical" fields, perhaps you stumbled on to one I missed. If you do a regular LOPTS it will "erase" the previous logical setting. To restore the logical simply re-LOPTS using the form LOPTS <type> (e.g., LOPTS PROGRAM, LOPTS SETUP, etc.)
BUG FIXED - Fetch doesn't return to original page
When the F* button is pressed when you on a page, it doesn't return to that page after it has finished interrogating the program.
---
Fixed in 0.2.4 Beta
NOT A BUG - Pad parameter on None doesn't have predefined dropdown.
Example - Algorithm 1 F1 Pad. Also Algorithm 1 AMP page Pad is a slider.
---
As you observed above, use LOPTS INC on these fields. Please let me know if I misunderstood this bug report.
Bug - Going from F1 to F2 lost Cursor Sync
Example HiFrq Stim F1 to F2 didn't sync cursor. VP thought cursor was on Adjust when it was on MinDpt.
---
I cannot reproduce. Can you give me more info? Thanks.
NOT A BUG - LOPTS on KStart Parameter gets stuck at C9 unipolar.
Example - F2 of HiFrq Stim. The ranges for this parameter are 0 - 127 - Unipolar -120 to -1.
It doesn't scan the -ve's by default.
Workaround LOPTS -120 seemed to work OK.
---
Use LOPTS INC on this field.
Bug - SNAG still doesn't work
Creates 0 byte files that can't be opened. Do we need to install a Java Library by any chance?
---
Are you on a Mac? If on a PC make sure you are using J2SE v 1.4.2_xx JRE or later. Please give me a follow-up on this. Thanks.
BUG FIXED- LOPTS for Drawbars need 2 settings
In KB3 programs, the Drawbar settings can range from 0-8 or 0-127 depending on the setting of Steps. VP doesn't account for this.
---
Fixed in 0.2.4 Beta
Bug FIXED- LOPTS for KB3 Mode Tune doesn't work
LOPTS on any of the tune parameters doesn't work, even using manual methods. The reason is that the range is -127 to +127, but there are only 3 characters allowed, so -127 reads as -12, but the value is -127. Similarly -126 reads as -12, etc.
---
So -120 and -12 look the same, lovely!
I'll put in a LOPTS hack to get around this. Sigh :-(
---
Fixed in 0.2.4 Beta - Added LOPTS RANGE <high> <low> which allows LOPTS range for numeric valued fields to be entered directly. For this case the command would be LOPTS RANGE 127 -127
NOT A BUG- In KB3 mode LOPTS on UpperToneWheels parameter doesn't return to pre LOPTS value.
---
There are 2 issues here.
1. LOPTS will only (can only) return to the original value if it succeeds.
2. In (1) above, use LOPTS KEYMAP
NOT A BUG - LOPTS on KB3 Mode LowestPitch doesn't work
LOPTS Inc does it's thing, but the drop down list isn't complete and doesn't change the value when a selection is made.
---
Use LOPTS INC.
NOT A BUG- KB3 Mode - Misc ASR lower page has 3 blank pages at top
---
These are unused screen areas. Perhaps I can disable them or use some sort of other visual cue to indicate this but very low priority.
NOT A BUG - LOPTS doesn't work for FUNS inputs.
Workaround - Lopts Inc does work.
---
This is what LOPTS INC is for. :-)
NOT A BUG - (and you are gonna hate this one) - LOPTS on KDFX parameters don't work.
On the KDFX page (I did it in a KB3 program), the Param fields are dependent upon the studio. If you do a LOPTS on it, then it is fixed to the Bus, even if you change the studio.
For example. If I have Bus set to Aux while the studio is set to the default KB3 studio, and I do a LOPTS on Param, then I get a list. If I change the studio to #1, then the Param list is not updated.
This will be impossible to get a fully defined LOPTS set because studio's are fully variable. The only way to do it would be to list all the parameters from each algorithm, look inside the studio to find out what algorithms are used and where, and then to formulate a set of parameters from there, though this is always going to be slow to get this list.
---
Thanks for calling attention to this one... you'll appreciate my hard work! :-) Here goes...
Adjust and Depth fields are additionally keyed off of the value of the Param field. As for the Param field itself you are correct, there is no reasonable way to determine the options. Too bad, that would be a nice one to have.
V 0.2.2 Beta
BUG FIXED: Pan ctrl (Pan keyword) is misrecognized
OS:Win Kurz:K2600
The Pan keyword is misrecognized in some places and erroneously listed as the Pan ctrl.
Fixed in 0.2.3 Beta: "Pan" is no longer erroneously identified
BUG FIXED: Page list selection does not honor Layer/Zone selection
OS:Win Kurz:K2600
Page list selection does not use the currently selected Layer/Zone (right side buttons) that is being viewed.
Fixed in 0.2.3 Beta: Works now.
BUG: When deleting L/Z VP should invalidate cached sceens
OS:Win Kurz:K2600
When deleting L/Z VP should invalidate cached sceens or correct them otherwise this can get confusing. Should consider some technique to indicate possibly "stale" pages.
BUG FIXED: Object rename should also update the name cached in VP during an edit
OS:Win Kurz:K2600
Object rename should also update the name cached in VP during an edit.
Fixed in 0.2.3 Beta: Name now updates properly.
CANNOT REPRODUCE: Last object name in ProgramMode (probably Setup mode also) does not update properly
OS:Win Kurz:K2600
Last object name in ProgramMode (probably Setup mode also) does not update properly. Don't know when this happens, possibly all of the time, possibly when a new object is created.
Cannot reproduce: This might be a version (or confused with) the BUG reported above.
BUG FIXED: Ctrl List did not clear between L/Z changes
OS:Win Kurz:K2600
Caused some ctrl to be erroneously reported.
Fixed in 0.2.3 Beta: Now clears properly.
BUG FIXED: Misc Ctrl list special cases
OS:Win Kurz:K2600
Caused some ctrls to be erroneously reported.
Fixed in 0.2.3 Beta: These cases have been corrected.
BUG: Back & Forward buttons in EditStudio
OS:Win Kurz:K2600
Back & Forward buttons in EditStudio do not honor INPUT letter (A,B,C,D) or FXBUS number (1,2,3,4).
| Main Page : | Kurzweil : | VAST Programmer : | Bug Reports : | Feature Requests |
