mirror of
https://github.com/robbert-vdh/yabridge.git
synced 2026-05-07 03:50:11 +02:00
Don't fill long lines in issue template
GitHub seems to treat these newlines as hard line feeds (e.g. just like two spaces at the end of a line in regular Markdown).
This commit is contained in:
@@ -6,15 +6,9 @@ body:
|
|||||||
attributes:
|
attributes:
|
||||||
label: Thanks for giving yabridge a shot!
|
label: Thanks for giving yabridge a shot!
|
||||||
description: |
|
description: |
|
||||||
If you're having issues with plugins not working at all or scans timing
|
If you're having issues with plugins not working at all or scans timing out then make sure to check out the [troubleshooting common issues](https://github.com/robbert-vdh/yabridge#troubleshooting-common-issues) section of the readme.
|
||||||
out then make sure to check out the [troubleshooting common
|
|
||||||
issues](https://github.com/robbert-vdh/yabridge#troubleshooting-common-issues)
|
|
||||||
section of the readme.
|
|
||||||
|
|
||||||
You should also read through the [known issues and
|
You should also read through the [known issues and fixes](https://github.com/robbert-vdh/yabridge#known-issues-and-fixes) section. There may already be a solution or a workaround for the issue you're having.
|
||||||
fixes](https://github.com/robbert-vdh/yabridge#known-issues-and-fixes)
|
|
||||||
section. There may already be a solution or a workaround for the issue
|
|
||||||
you're having.
|
|
||||||
options:
|
options:
|
||||||
- label: >-
|
- label: >-
|
||||||
I read through both the troubleshooting and known issues sections my
|
I read through both the troubleshooting and known issues sections my
|
||||||
@@ -137,22 +131,18 @@ body:
|
|||||||
attributes:
|
attributes:
|
||||||
label: Debug log
|
label: Debug log
|
||||||
description: |
|
description: |
|
||||||
Please also include a debug log if possible. If you are reporting an
|
Please also include a debug log if possible. If you are reporting an issue with yabridgectl, then you can omit this section.
|
||||||
issue with yabridgectl, then you can omit this section.
|
|
||||||
|
|
||||||
1. First make sure that there are no leftover Wine processes left
|
1. First make sure that there are no leftover Wine processes left running in the background using `wineserver -k`.
|
||||||
running in the background using `wineserver -k`.
|
|
||||||
2. Launch your host from a terminal using:
|
2. Launch your host from a terminal using:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
rm -f /tmp/yabridge.log; env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2+editor <host>
|
rm -f /tmp/yabridge.log; env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2+editor <host>
|
||||||
```
|
```
|
||||||
|
|
||||||
Where `<host>` is the name of your host, like `bitwig-studio`,
|
Where `<host>` is the name of your host, like `bitwig-studio`, `reaper`, or `ardour6`.
|
||||||
`reaper`, or `ardour6`.
|
|
||||||
|
|
||||||
3. Try to scan or load the plugin that's causing issues.
|
3. Try to scan or load the plugin that's causing issues.
|
||||||
4. `/tmp/yabridge.log` should now contain a debug log. You can drag this
|
4. `/tmp/yabridge.log` should now contain a debug log. You can drag this file directly onto the text field below to upload it to GitHub.
|
||||||
file directly onto the text field below to upload it to GitHub.
|
|
||||||
validations:
|
validations:
|
||||||
required: false
|
required: false
|
||||||
|
|||||||
Reference in New Issue
Block a user