What about Ardour?
Linux DAW: Help Linux musicians to quickly and easily find the tools they need
81–90 of 125 posts
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#82For some reason "Linux musicians" made me think of someone making art out of 'cat /dev/random > /dev/dsp', and made me wonder what Windows musicians are like (lots of anger and frustration to express I'd imagine)
Back in the pre-alsa days when linux used OSS you could pipe /dev/random into /dev/dsp and get noise, you could pipe anything into /dev/dsp and generally get some sort of noise. Possibly can still do this on the BSDs since they still use OSS.
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#83Earlier quoted context omitted.
The alternative is the mouse wheel and keybinds. Flight Simulators got this right. Roll up on the wheel to increase the value, roll back on the wheel to decrease the value. Left click to push, right click to pop (or context menu, left click to push it again to turn off). In fact, if it was all MIDI controlled, it's just a matter of mapping the mouse scroll wheel to a midi channel.
I don't really see how that would be precise enough, the mouse wheel has a DPI of like 10 vs 400-800 for a mouse. A mouse wheel has like 25 notches in a full rotation and even MIDI CC values go from 0-127, that's 5 full rotations, that doesn't sound practical as it would be far too slow. And many parameters require much more precise control than 127 steps. I don't play flight sims but I imagine most flight surfaces r…
I would assume the better programs implement some velocity control, turning it quickly will cause it to increment in larger steps, turning it slowly will increment single steps. This is how I have done it in the past when I have used the scroll ring on my trackball in PureData.
I would also assume there are detent free mousewheels with a far greater number of steps, there used to be. The scroll ring on my trackball is detent free and quite fine but it is also ~2" in diameter, considerably larger than the wheel on any mouse.
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#84Just an fyi to anyone making or thinking of making one of these: Turning a knob with a mouse is the worst interface I can think of. I don't know why audio apps/DAWs fall so hard on skeuomorphism here when the interface just doesn't make sense in the context.
You map them to controllers
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#85Just an fyi to anyone making or thinking of making one of these: Turning a knob with a mouse is the worst interface I can think of. I don't know why audio apps/DAWs fall so hard on skeuomorphism here when the interface just doesn't make sense in the context.
It makes a lot of sense when you're holding a chord on a MIDI keyboard with one hand and dragging various knobs with a mouse in the other. Once you know the params you want to tune, you can obviously automate or map them to a MIDI controller, but doing that upfront slows things down considerably.
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#86The real-time low latency multi channel audio streaming needed for musicians is awfully similar to the real time low latency multi channel audio streaming required for telephony. Yet somehow the two industries have pretty much entirely different tech stacks and don't seem to talk to one another.
Not really! AES67 is essentially RTP with a PTP derived media clock. Connection description uses SDP and unicast signaling uses SIP. Just like VoIP.
Also I imagine TDM was first used in telephony.
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#87Earlier quoted context omitted.
Good morning. An expanding plethora of buttons, tabs, menus requires geometrical memory that may have nothing directly to do with the function in question. The first GUIs were designed that functions be "discoverable," however the size of haystacks in which these discoverable functions hide has grown exponentially, adding cognitive overhead, and increasing the length of apprenticeship needed to master the application…
Mind sharing your DAW app?
Looks like it's nama: https://github.com/bolangi/nama
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#88Earlier quoted context omitted.
Is it fair to assume most mouses have a scroll wheel? Hover and use that? Do they do that?
I think it's even more fair to assume the user has a MIDI device with a bunch of knobs on it?
If that's what they're using, why would there need to be a way to move it via the mouse at all then?
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#89What about Ardour?
Ardour is listed. You need to search for it in the search bar.
If your question was about using Ardour, I used it a bit and I managed to make a tune. I recommend this tutorial: https://www.youtube.com/watch?v=ACJ1suTVouw
Re: Linux DAW: Help Linux musicians to quickly and easily find the tools they need
#90Just an fyi to anyone making or thinking of making one of these: Turning a knob with a mouse is the worst interface I can think of. I don't know why audio apps/DAWs fall so hard on skeuomorphism here when the interface just doesn't make sense in the context.
A 20 pixel knob has considerably greater resolution than a 20 pixel slider with its max resolution of 20. I don't think I have come across a digital knob that you have to turn with the mouse since the previous century, just drag up or down or left or right.
A slider is just a UI element as is a knob, the underlying resolution does not have to correlate 1:1 with the exact number of pixels something takes up on a screen. The resolution could be effectively infinite depending on the implementation of the controls.