CorOS Version: 2.1.1
Describe your issue:
When I assign a neural capture titled “King of Tone Yellow” to a footswitch in a preset and switch to gig view, the top of the text is cut off by an icon. I’m not sure if it’s because of the length of the title of the neural capture and more from the word count. “King of Tone Yellow” is 4 words and 19 characters, but you can see from the attached photo that I also have a capture on this preset called “Greer Lightspeed 18v” which is only 3 words, but is longer at 20 characters.
Steps to reproduce your issue:
- Create a neural capture with a 4-word, 19 character title
- Assign that neural capture to a footswitch in a preset
- Open gig view
I expected this to happen:
When I name a neural capture, I expected the text of the title to scale for this capture as it has with other captures.
I have tried the following things:
- I have tried renaming the neural capture
I would email firstname.lastname@example.org so they are aware and can address in the next update.
If I may ask - no offense intended - for what reason do we have the “bug report” category if it’s not being monitored by or forwarded to the support team of neural? This just increases the work for you as a moderator (replying everytime “please write a mail to the support”) and may lead to bugs not mailed to the support because one might think that a post in this category is sufficient.
If it’s anything like the other forums, Neural probably does keep a loose eye on the bugs here but there is no guarantee they’ll see it. Contacting support is a more likely method to ensure a bug gets addressed in a firmware update.
Bugs are still valuable to report here though as it informs other forum members of a potential problem which can result in vetting the “bug” and offering assistance (it may not be a bug), or workarounds if it is. It can also give the person reporting the bug a better idea of how widespread it is and whether or not it is afflicting other users or just them.
I think the idea of this forum is to interact with other users while determining how to provide resolution for specific scenarios. Since there are multiple scenarios possible, one solution does not fit everyone. Eventually if no suggestion that fits the unique issue, we usually forward the user to support so that the issues get logged and hopefully resolved. Also, we have the ability to escalate directly with support as required. Hopefully that answers your question, if not feel free to DM me and no offense taken