[
    {
        "role": "user",
        "content": "how%20do%20I%20get%20reaper%20to%20read%20and%20accept%20values%20properly%20on%20effects%20when%20using%20it%20with%20Jaws%20and%20Osara%3F%20one%20of%20the%20effects%20I%20added%20reads%20percentage%20values%20but%20even%20when%20you%20do%20the%20arrow%20keys%20it%20is%20still%20saying%200%20per%20cent.%20If%20you%20tab%20once%20it%20changes%20the%20next%20value%20to%20things%20like%20900%20and%20something.%20Also%2C%20things%20like%2015%20per%20cent%20after%20that%20although%20they%20appear%20to%20let%20you%20change%20their%20value%20by%20typing%20one%20in%2C%20if%20you%20type%20it%20and%20press%20enter%2C%20it%20goes%20back%20to%20what%20it%20was%20so%20doesn%27t%20work."
    },
    {
        "role": "assistant",
        "content": "Here are some steps, tips, and explanations that can help you with getting REAPER to read and accept values properly in effects when using JAWS and OSARA. From what you described\u2014percentages staying at zero, enter reverting typed values, the next value jumping to something huge\u2014that lines up with known limitations and behavior of OSARA plus JAWS in REAPER.  \n\n---\n\n## What is OSARA, and what's normal behavior\n\n- OSARA is an extension for REAPER that makes many functions accessible to screen readers. It reports parameter values, FX parameters, peaks, etc. based on the effects\u2019 exposed data. ([reaperaccessibility.com](https://reaperaccessibility.com/index.php/OSARA_readme?utm_source=openai))  \n- The documentation **explicitly says** some effects only expose percentage values, and even when there\u2019s a slider and editable text, the text you type is often an \u201cinternal number\u201d that doesn\u2019t directly match the slider\u2019s displayed, readable value. ([reaperaccessibility.com](https://reaperaccessibility.com/index.php/OSARA_readme?utm_source=openai))  \n\nSo some of what you\u2019re seeing (percentage always at 0, text field changes behaving oddly, etc.) may be expected behavior for certain effects that OSARA only partially supports.\n\n---\n\n## Why the \u201cpercentage value stuck at 0\u201d / weird jumps happen\n\nThese behaviors often happen because:\n\n1. **The FX plugin doesn\u2019t expose its control values in a way OSARA (or the screen reader) can read reliably**.  \n   - For example, the slider might visually show \u201c50%,\u201d but internally, the parameter might be on a scale like 0-1 or 0-1000, which is what's in the editable text. OSARA/JAWS might pick up or allow editing only the internal number. Typing a number that doesn\u2019t map correctly will revert or jump when you press Enter. ([reaperaccessibility.com](https://reaperaccessibility.com/index.php/OSARA_readme?utm_source=openai))\n\n2. **Keyboard interaction limitations in the native control**.  \n   - Some parameter dialogs or sliders are built with UI elements that don\u2019t fully support keyboard control or screen reader accessible value changes. Arrow keys might not adjust what you think they do, or focus might jump to other controls, leading to \u201cnext value\u201d changes you didn\u2019t expect. ([reaperaccessibility.com](https://reaperaccessibility.com/wiki/Using_Reaper_Under_MacOs?utm_source=openai))\n\n3. **JAWS and OSARA communication issues**.  \n   - OSARA uses Microsoft Active Accessibility (MSAA) or UI Automation (UIA) on Windows to communicate parameter changes. If the plugin uses custom GUI or doesn\u2019t expose its controls properly, JAWS may not pick up changes. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n\n---\n\n## What you *can* try to get better results\n\nHere\u2019s a checklist of things to try, that often help:\n\n1. **Use the FX Parameter List dialog from OSARA**  \n   - Select the track or item with the effect.  \n   - Press **p** (or Shift+p for master track) to open the FX parameters list. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n   - Use this dialog\u2014the \u201cParameter\u201d combo box to pick the control you want, then \u201cValue\u201d slider or editable text field. Sometimes this gives better feedback than using the effect\u2019s native GUI. \n\n2. **Watch what the slider value says**  \n   - When you change values with arrows while focused on the slider, pay attention to what OSARA or JAWS reads. Even if the on-screen GUI shows percentage, the accessible slider may show an internal number. That gives a clue about what scale it expects.  \n\n3. **Type the internal number, not the percentage**  \n   - If editable text is present, try typing a number that might correspond to full-scale (e.g. 1.0, 1000, or whatever seems \u201cmax\u201d) rather than a percentage, then press Enter. See if that maps more correctly.  \n\n4. **Use the numeric keypad or key modifiers**  \n   - Sometimes arrow keys plus modifiers (like Shift, Ctrl) change in larger/smaller increments.  \n   - Also check OSARA\u2019s key map to see if there are actions bound that adjust FX parameters more reliably. OSARA has keyboard shortcuts for a lot of parameter control. ([reaperaccessibility.com](https://reaperaccessibility.com/index.php/OSARA_readme?utm_source=openai))\n\n5. **Update REAPER, OSARA, and SWS extension**  \n   - Make sure you're using a recent REAPER version (minimum 6.44 for the latest OSARA) ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n   - Install SWS/S&M extension too\u2014it\u2019s often required or helpful for certain FX parameter actions. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n\n6. **Check whether the effect is one of the accessible ones**  \n   - If it's a built-in REAPER effect, it's more likely to expose values properly. Third-party or plugin effects often use custom interfaces that are not fully accessible. The OSARA docs warn that many effects do *not* expose \u201ceasily readable values.\u201d ([reaperaccessibility.com](https://reaperaccessibility.com/index.php/OSARA_readme?utm_source=openai))  \n\n7. **Use OSARA\u2019s \u201cFilter\u201d field in FX Parameter List**  \n   - Once in the FX Parameter List, there's a Filter you can type into\u2014it can help find the parameter you want by name (if known), reducing confusion and helping ensure focus is on the correct control. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))\n\n8. **Test whether JAWS is the issue vs OSARA vs the plugin**  \n   - If possible, test with NVDA (if you can) or try another effect that is known to work properly. If that one updates correctly, then you know the plugin or GUI for the effect you\u2019re using is the culprit.  \n\n---\n\n## What *can\u2019t* be fixed (yet)\n\nSadly, some of the things you experience might not have a fix until the effect author or REAPER/OSARA devs change something:\n\n- If a plugin doesn\u2019t expose its parameters via standard automation or UIA/MSAA, screen readers can\u2019t \u201csee\u201d them properly.  \n- If the editable text is an internal code rather than a human-friendly percentage, OSARA might still read only that.  \n- Native plugin GUIs often use custom controls not fully keyboard- or screen-reader compatible.  \n\n---\n\nIf you like, I can walk you through a specific example with one of your problematic effects: we could debug the value scale and find what internal number corresponds to, say, 50%. Just tell me the name of the effect that\u2019s giving you trouble. Do you want to try that?"
    },
    {
        "role": "user",
        "content": "shift%20and%20p%20won%27t%20do%20parameters%20for%20me%20but%20alt%20and%20p%20does%2C%20but%20it%20still%20does%20it."
    },
    {
        "role": "assistant",
        "content": "Okay \u2014 good to hear that Alt + P works. That confirms the FX parameters dialog *is* being called correctly. The fact that things still don\u2019t update properly after opening the dialog suggests it\u2019s a limitation either in OSARA, JAWS, or (most likely) the effect/plugin itself. Let\u2019s dig into what might help and what you can try to improve the behavior.\n\n---\n\n## What OSARA says about Alt+P / P / Shift+P\n\nAccording to the OSARA documentation (accessed most recently), here\u2019s how the keybindings for parameter dialogs work:\n\n- **Alt + P**: Open the parameter list for the *selected track/item/FX*, depending on where focus is. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n- **P**: Opens the FX parameter list for the current track or take. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n- **Shift + P**: Same as \u201cP\u201d but for the *master track*. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n\nSo Alt+P is the correct one for viewing specific FX parameters.\n\n---\n\n## Why you might still see \u201c0%\u201d or have typing not stick\n\nEven after opening the parameter list via Alt+P, these problems often happen when:\n\n1. **The plugin effect doesn\u2019t expose its value in a \u201chuman-readable\u201d way**  \n   OSARA states some effects only provide values like percentages (maybe only 0-100%) or internal values (scales like 0-1.0, 0-1000, etc.). The slider may display a percentage, but the editable text field might reflect an internal numeric scale. Typing into the internal field may only accept valid internal values, so if you try to type \u201c15%\u201d where it expects \u201c0.15\u201d or \u201c150,\u201d it may reject it or revert. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))\n\n2. **The text edit field isn't fully supported / committed**  \n   Sometimes typing followed by Enter doesn\u2019t \u201ccommit\u201d the text if the field expects focus or navigation that the screen reader or OSARA can\u2019t guarantee. For example, pressing Tab after typing might move focus and cause the typed value to apply or adjust. Without that, the entry might revert. OSARA notes that typing + Enter might not work reliably in all effects. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))\n\n3. **Sliders or arrows are changing values, but what you hear is the internal number**  \n   When you use arrow keys up/down (with no modifiers), OSARA typically changes values by the smallest step. Use modifiers (Shift, Ctrl, Alt) to adjust in larger steps. ([ear.social](https://ear.social/reaper/help/osara/usermanual/virtual_dialogs?utm_source=openai))  \n   \n   The percentage might *appear* unchanged because the internal value changed only a little, not enough to move the percentage display, or because the percentage display is a rounded version of the internal value, and changes are smaller than the rounding threshold.\n\n---\n\n## What to try to make it work better\n\nHere are more specific things you can try to get values to change and be reported properly:\n\n- After you type into the editable text field, try **Tab** instead of or in addition to Enter. Sometimes pressing Tab moves focus off the field and forces commit.  \n- Use arrow keys while focus is on the **slider**, not necessarily on the text edit field, to make incremental changes. Try with and without modifiers (Shift, Alt, Ctrl) to see if larger steps result in visible percentage change.  \n- Make sure you\u2019re using the **FX parameter list dialog** (Alt+P), because that gives access to slider + editable field + filter, which tends to work more consistently than trying earlier via the native FX chain window.  \n- If possible, use a **REAPER default or stock effect**\u2014those are more likely to expose proper values. Test with something simple (\u201cReaEQ,\u201d \u201cReaComp,\u201d etc.) to see whether behaviour matches or differs. That helps clarify whether the problem is with that particular plugin.  \n- Check whether your version of OSARA and REAPER is up to date (OSARA requires REAPER 6.44 or later). Bug fixes may have improved behavior. ([osara.reaperaccessibility.com](https://osara.reaperaccessibility.com/?utm_source=openai))  \n\n---\n\nIf you tell me *which effect/plugin* is misbehaving (name, manufacturer, whether it\u2019s built in or third party), I can help test approximate \u201cinternal scale \u2192 percentage\u201d conversions or see if there\u2019s a known workaround specific to that plugin. Do you want to try that?"
    }
]