When you are making choices about integrating features that in some what duplicate hardware functionality, where do you draw the line between designer intent, and the exact behaviour of the resulting design? So speaking of what my readers have read, I’ve previously had a bit of a fit about Mixbus’s lack of ‘pure emulation’ of certain Harrison console processes (such as EQ and compression).
I’d like to know more about your VCS (git I assume) setup and how you manage working with two, often diverging, projects across two teams. I have a lot of technical readers, largely programmers, but many IT people and hobbyist nerds.Has there been any collisions or conflicts of interest? How do you determine what’s fed upstream to Ardour? Have you ever blocked any downstream changes? I wanted to ask about the bidirectional development process with Ardour. How do you combat that, or do you? What defines the focus of the project? That brings me to the concept of ‘feature creep’, where over time the DAW starts to be saturated with features that are requested or desired by a big part of the user base.So being experienced in console design, along with your interest in other products (as you and I have discussed before), how much of your time thinking about Mixbus comes from seeing what other products do ‘wrong’ and doing better, compared to your own innovative vision.What does being a ‘large-format console GUI designer’ consist of? What makes this a job that necessitates a person to specialize in it? I think most folks assume consoles are designed by putting some knobs in faders in a cannon and blast it at a metal chassis. How did you personally get in to the DAW world, and what was the spark that lead Harrison to enter the software world in such a grand manner?.Who are you, what do you do, where do you do it, and what do you do when you’re not doing it? Hello! Let’s start with the most generic question ever.
#Editing podcasts in mixbus 32c v5 on pc full#
If you have questions, please leave a comment and I will clarify and/or edit that section.Ĭlick through for the full text interview. I attempted to keep most of the content intact as written, but I made some edits so that the text is more clear for non-native english readers. We covered some of the history of Mixbus, goals, design challenges and team management. I took some time to discuss Mixbus with Ben Loftis.
#Editing podcasts in mixbus 32c v5 on pc pro#
Harrison Mixbus is a relatively new DAW in the music world, yet has easily managed to insert itself in to the pro audio world as a contender. I previous did a review series about Mixbus 32c 4.x.
0 kommentar(er)
