PBR for Audio Software Interfaces (2016)
auburnsounds.com
PBR for Audio Software Interfaces (2016)
1–10 of 35 posts
Re: PBR for Audio Software Interfaces (2016)
#2Does anyone have any experience with the DPlug framework? I've used IPlug for a few plugins and have been impressed (considering the lofty goals of the project) but D looks a lot more mature and well-thought-out. I found a comparison on their Github page (https://github.com/AuburnSounds/dplug#comparison-vs-iplug) but does anyone here have an opinion?
Re: PBR for Audio Software Interfaces (2016)
#3Obligatory OT comment complaining about the site:
I think this is one of the worst performing sites I have ever visited. When the gears in the top right are visible, my whole phone (oneplus one) stutters and when I scroll down, it takes up to a second for the page to follow and render in.
I understand the need to make your site special, but if it's at the the cost of this much performance you should really overthink it.
Re: PBR for Audio Software Interfaces (2016)
#4The article itself is very interesting but the skeuomorphic UI looks horrible to use - especially the knobs, because there is no intuitive AND practical way to emulate twisting stuff with a mouse pointer.
Can anyone with practical experience with this tool share their opinion?
Re: PBR for Audio Software Interfaces (2016)
#5The article itself is very interesting but the skeuomorphic UI looks horrible to use - especially the knobs, because there is no intuitive AND practical way to emulate twisting stuff with a mouse pointer. Can anyone with practical experience with this tool share their opinion?
Yeah... audio software, especially VST plugins, have a tendency to 1) all invent their own UI styling and 2) use skeuomorphic designs. I wish this trend would stop, but it doesn't look at all likely.
Re: PBR for Audio Software Interfaces (2016)
#6The article itself is very interesting but the skeuomorphic UI looks horrible to use - especially the knobs, because there is no intuitive AND practical way to emulate twisting stuff with a mouse pointer. Can anyone with practical experience with this tool share their opinion?
Yeah... audio software, especially VST plugins, have a tendency to 1) all invent their own UI styling and 2) use skeuomorphic designs. I wish this trend would stop, but it doesn't look at all likely.
It has its upsides, I guess - such as it would be instant to learn (if a bit cumbersome to use) for someone who already has experience with physical interfaces.
Re: PBR for Audio Software Interfaces (2016)
#7The article itself is very interesting but the skeuomorphic UI looks horrible to use - especially the knobs, because there is no intuitive AND practical way to emulate twisting stuff with a mouse pointer. Can anyone with practical experience with this tool share their opinion?
It's been a while since I used these UIs, but usually what happens is you click on the knob and it turns into a vertical slider. Not so bad really.
The skeumorphic UI lets you move between the physical panel and the GUI pretty seamlessly. Not saying there isn't a better option, but this at least is pretty nice for beginners.
Re: PBR for Audio Software Interfaces (2016)
#8The article itself is very interesting but the skeuomorphic UI looks horrible to use - especially the knobs, because there is no intuitive AND practical way to emulate twisting stuff with a mouse pointer. Can anyone with practical experience with this tool share their opinion?
It's been a while since I used these UIs, but usually what happens is you click on the knob and it turns into a vertical slider. Not so bad really. The skeumorphic UI lets you move between the physical panel and the GUI pretty seamlessly. Not saying there isn't a better option, but this at least is pretty nice for beginners.
Except for a few emulations of hardware, most of these UI's don't correlate to a physical panel and the lack of consistency between the various virtual-only ones, IMHO, negates any benefit from a consistency point of view. Having something look like a physical knob is one thing, but when each plugin you have has its own different style of "physical knob" design, I find it gets messy personally.
Re: PBR for Audio Software Interfaces (2016)
#9The article itself is very interesting but the skeuomorphic UI looks horrible to use - especially the knobs, because there is no intuitive AND practical way to emulate twisting stuff with a mouse pointer. Can anyone with practical experience with this tool share their opinion?
Music plugins have to have skeumorphic UIs, nobody wants to twist generic looking knobs. C'mon man, these are artists, they are not the average muggle.
If designers from this world got ahold of the music scene from that world plugins would get considerably worse, as UI's would be the focus of intense simplification, leaving complex features and their power users by the wayside.
Re: PBR for Audio Software Interfaces (2016)
#10The article itself is very interesting but the skeuomorphic UI looks horrible to use - especially the knobs, because there is no intuitive AND practical way to emulate twisting stuff with a mouse pointer. Can anyone with practical experience with this tool share their opinion?
Music plugins have to have skeumorphic UIs, nobody wants to twist generic looking knobs. C'mon man, these are artists, they are not the average muggle. If designers from this world got ahold of the music scene from that world plugins would get considerably worse, as UI's would be the focus of intense simplification, leaving complex features and their power users by the wayside.
Is there any actual evidence that "nobody wants to twist generic looking knobs"? It seems like a widespread assumption, but I don't know to what extent it's been measured or tested.
I, for example, am a nobody (a hobbyist musician) who dislikes most custom VST UIs. Back in the day, FL Studio (nee Fruityloops) shipped with a bunch of plugins that looked like they had an autogenerated UI, with every parameter getting its own controls (a knob, numeric readout, and visual bar)... and I liked them. No cruft, and it was easy to systematically manipulate each control to determine its effect on the sound.