Log in
Register
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
Behringer X32 Firmware v3.0 Feature Requests
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Jay Ashworth" data-source="post: 131245" data-attributes="member: 8260"><p>Re: Behringer X32 Firmware v3.0 Feature Requests</p><p></p><p>Well, John, there are two things I'd like to suggest, and they're both somewhat meta to the topic of actual firmware features on the board, but I think both of them would contribute a lot to reducing the amount of energy I see people expending on the various forums trying to figure things out:</p><p></p><p>1) Get the documentation up to date.</p><p></p><p>I see that you have the manual sources poured into a wiki, which is an excellent starting point, and you even picked my favorite engine, mediawiki. That said, no one seems to be *doing* anything there; when I manually pull up the Recent Changes page (because the link to it's been removed), I find only spammers on talk pages, and no apparent actual updates. There's some new copy about some of the 2.x feature set, but as near as I can tell, it's just the release notes; there's no actual *documentation* about, say, how snippets are created and used. Or how safes work. And these are topics about which I've seen a fair amount of speculation in the wild this week, as I've come up to speed on the board, since my favorite rental house just bought one, and after a new job matures, I might as well.</p><p></p><p>I thought to go look at the Midas manual, and it's Much Newer (about a week old as I type this), and while it's clearly 2.x, at least in parts (it includes the RTA, for example), it still doesn't really seem to explain topics like snippets and safes in as much detail as I would like to see, having grown up on, say, Mackie's manuals.</p><p></p><p>2) A Public Bug Tracker</p><p></p><p>I know that these are often looked at with somewhat of a jaundiced eye by corporate managements, but exactly the sort of thing you're doing here is exactly what -- at least the current generations of -- bug trackers do well: capture bug and RFE reports from the end users, and allow users to vote on which ones are most important to them.</p><p></p><p>They can also capture, of course, bugs against the documentation, making that job easier in two ways. Finally, they allow you to assign target releases to specific changes, so that end users have an idea when what they might need is coming down the pike, and whether (here's another question I've seen several places) a showstopper for them is going away, and they should either hold out, or buy, knowing that their particular showstopper *is acknowledged and scheduled for extinction*... instead of buying something else.</p><p></p><p>Other than that, I'll chime in on the group muting. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":-)" title="Smile :-)" data-smilie="1"data-shortname=":-)" /></p><p></p><p>I've actually got a short list of other suggestions to make about the UI and operations design, but I want to get my hands on the board and confirm they're software issues and not doco issues, first. (As you might suspect by now, I've got fairly deep background in both production and software engineering. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":-)" title="Smile :-)" data-smilie="1"data-shortname=":-)" /></p></blockquote><p></p>
[QUOTE="Jay Ashworth, post: 131245, member: 8260"] Re: Behringer X32 Firmware v3.0 Feature Requests Well, John, there are two things I'd like to suggest, and they're both somewhat meta to the topic of actual firmware features on the board, but I think both of them would contribute a lot to reducing the amount of energy I see people expending on the various forums trying to figure things out: 1) Get the documentation up to date. I see that you have the manual sources poured into a wiki, which is an excellent starting point, and you even picked my favorite engine, mediawiki. That said, no one seems to be *doing* anything there; when I manually pull up the Recent Changes page (because the link to it's been removed), I find only spammers on talk pages, and no apparent actual updates. There's some new copy about some of the 2.x feature set, but as near as I can tell, it's just the release notes; there's no actual *documentation* about, say, how snippets are created and used. Or how safes work. And these are topics about which I've seen a fair amount of speculation in the wild this week, as I've come up to speed on the board, since my favorite rental house just bought one, and after a new job matures, I might as well. I thought to go look at the Midas manual, and it's Much Newer (about a week old as I type this), and while it's clearly 2.x, at least in parts (it includes the RTA, for example), it still doesn't really seem to explain topics like snippets and safes in as much detail as I would like to see, having grown up on, say, Mackie's manuals. 2) A Public Bug Tracker I know that these are often looked at with somewhat of a jaundiced eye by corporate managements, but exactly the sort of thing you're doing here is exactly what -- at least the current generations of -- bug trackers do well: capture bug and RFE reports from the end users, and allow users to vote on which ones are most important to them. They can also capture, of course, bugs against the documentation, making that job easier in two ways. Finally, they allow you to assign target releases to specific changes, so that end users have an idea when what they might need is coming down the pike, and whether (here's another question I've seen several places) a showstopper for them is going away, and they should either hold out, or buy, knowing that their particular showstopper *is acknowledged and scheduled for extinction*... instead of buying something else. Other than that, I'll chime in on the group muting. :-) I've actually got a short list of other suggestions to make about the UI and operations design, but I want to get my hands on the board and confirm they're software issues and not doco issues, first. (As you might suspect by now, I've got fairly deep background in both production and software engineering. :-) [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
Behringer X32 Firmware v3.0 Feature Requests
Top
Bottom
Sign-up
or
log in
to join the discussion today!
