Live data from Hacker News

What Is the Future of the DAW?

djmag.com

201–210 of 223 posts

Re: What Is the Future of the DAW?

#201
post #155

Earlier quoted context omitted.

> I don't know why Audacity remains so popular, it's way clunkier than the above Presumably because it’s free, but I’m with you on the clunkiness. The UI looks very dated. I can recommend OcenAudio, which is free though not open source, and for me offers just the right level of functionality in a clean user interface. It’s very similar to how I remember the old versions of Cool Edit pre-Pro, which I thought were amaz…

Yup, was going to mention it, though it was crashy for me last time I used it.

Ah interesting. Don’t think I’ve had it crash ever but I don’t use it all that often relative to e.g. Ableton

Re: What Is the Future of the DAW?

#202
post #125

Earlier quoted context omitted.

Really??? Uh, it's probably my fault but as a hobbyist composer (day job software engineer) I can personally say that tools I use absolutely and utterly suck. They're immensely buggy. My workflow includes: - LilyPond for writing the final notation - MuseScore 4 for playing around, MuseScore 3 for playing MIDI - REAPER as DAW, SFZ plugin for midi soundfonts - Audacity for processing WAV files - music21 python lib if I…

> Unfortunately my own experience with Linux audio processing has been nothing other than encountering one bug after the other one. You kind of buried the lede there...

"To the man who has only a hammer, everything looks like a nail." Imagine, expecting Linux to provide a productive, frictionless music creation workflow, using programs that aren't exactly torture-tested for usability on the platform. I think you're supposed to be grateful/amazed that they work at all. (Not that the UX would be dramatically better or trouble-free on Windows or a Mac, using the same suite of apps.)

Re: What Is the Future of the DAW?

#203
post #136

Earlier quoted context omitted.

> Linux audio processing Just use Windows and all of these problems go away. When I make music my stack is basically Ableton Live, NI Komplete and Spitfire Audio and I have exactly 0 of these issues.

This doesn't work for me because I do a lot of algorithmic composition and a huge part of my music making involves programming and it's very hard to write code anywhere that's not linux. Also I truly hate using windows or osx.

> it's very hard to write code anywhere that's not linux.

Oh nonsense -- in fact, bullshit. No, it is not. This is a personal problem; seek help.

>Also I truly hate using windows or osx.

And we truly hate hearing about it, and how things don't work well on your platform of non-choice. So suffer it in silence please.

Re: What Is the Future of the DAW?

#204
post #187

Earlier quoted context omitted.

I can't agree more with this post! As a middle eastern producer trying to incorporate maqam, the workflow is custom...and frustrating...and funnily still better on a workstation. And CV control is not viable as a control for acoustic sampled vsts. Your opguide site looks like an incredible resource, thank you for creating it!

I've been going down the rabbit hole of using all physically modeled synths instead of sample based VSTs so that I can fully take advantage of MPE controls instead of trying to get samples to be expressive though arcane incantations of key twidding in Kontakt. I think it's probably the best option for doing things in a DAW right now, unfortunately.

Would love to find out more about what you're doing here. Not all physical modelling options allow dynamic retuning. Also, which software will allow a double reed like the mijwiz. We really need modartt to crack the remaining instrument classes :) if you're open to chat, do you mind dropping an email to the address in my profile?

Re: What Is the Future of the DAW?

#205

The umbrella topic to this is one of my favorite topics in all of software and one where strangely we as an industry don't seem to have internalized its lessons: That the right approach to building a software program (like a DAW, NLE, bitmap/vector editor) emerges early. This is why these applications have lifespans measured in decades, and it's extremely rare for a new player to be able offer anything new, different…

I highly encourage folks to check out a new DAW called Blockhead. It upends a lot of typical ideas of how a DAW should work. There’s no MIDI events and no global tempo. Everything is represented as blocks of samples on rows of timelines which are then effected by transforms placed on the rows above the rows containing samples. Edits and transform adjustments all happen in real time, and everything is continuously ren…

[dead]

Re: What Is the Future of the DAW?

#206

Earlier quoted context omitted.

I can't agree more with this post! As a middle eastern producer trying to incorporate maqam, the workflow is custom...and frustrating...and funnily still better on a workstation. And CV control is not viable as a control for acoustic sampled vsts. Your opguide site looks like an incredible resource, thank you for creating it!

I'm the lead author of Ardour [0], and I'd very much like to hear more about your frustrations, since over the next 1-2 years, paying attention to non-European musical culture is one of the things I hope to focus on during development. You can reach me via the email address in my profile, or maybe use our forums at discourse.ardour.org. Thanks. [0] https://ardour.org/ <= a cross-platform open source DAW that has been…

Hey Paul,

I'd love to chat! I'll make my way onto the forums. Hopefully there's a relevant spot to post about this :)

PS. Not sure if you're aware your email is not currently in your profile.

Re: What Is the Future of the DAW?

#207

Earlier quoted context omitted.

I'm the lead author of Ardour [0], and I'd very much like to hear more about your frustrations, since over the next 1-2 years, paying attention to non-European musical culture is one of the things I hope to focus on during development. You can reach me via the email address in my profile, or maybe use our forums at discourse.ardour.org. Thanks. [0] https://ardour.org/ <= a cross-platform open source DAW that has been…

Hey Paul, I'd love to chat! I'll make my way onto the forums. Hopefully there's a relevant spot to post about this :) PS. Not sure if you're aware your email is not currently in your profile.

There's no existing topic for this, but do feel free to create one.

paul@linuxaudiosystems.com for email

Re: What Is the Future of the DAW?

#208

Earlier quoted context omitted.

This doesn't work for me because I do a lot of algorithmic composition and a huge part of my music making involves programming and it's very hard to write code anywhere that's not linux. Also I truly hate using windows or osx.

> it's very hard to write code anywhere that's not linux. Oh nonsense -- in fact, bullshit. No, it is not. This is a personal problem; seek help. >Also I truly hate using windows or osx. And we truly hate hearing about it, and how things don't work well on your platform of non-choice. So suffer it in silence please.

[deleted]

Re: What Is the Future of the DAW?

#209

Earlier quoted context omitted.

This doesn't work for me because I do a lot of algorithmic composition and a huge part of my music making involves programming and it's very hard to write code anywhere that's not linux. Also I truly hate using windows or osx.

I don't have this problem. Reaper, microphone + sax, occasional other woodwind and occasional keyboard. If I write code for music it'll probably be in puredata or perl (day job). Puredata for (generative)? sequencing and audio effects. Lilypond for notation which I'll consume with reaper or timidity. I tried windows - it confused the crap out of me. I don't mind OSx but do all my real work on a debian workstation. I…

My music involves a lot of time sig changes. When I export REAPER project to midi and consume in Python, there are bugs such as note duration being wrong exactly where there is a time sig change.

Re: What Is the Future of the DAW?

#210

Earlier quoted context omitted.

Really??? Uh, it's probably my fault but as a hobbyist composer (day job software engineer) I can personally say that tools I use absolutely and utterly suck. They're immensely buggy. My workflow includes: - LilyPond for writing the final notation - MuseScore 4 for playing around, MuseScore 3 for playing MIDI - REAPER as DAW, SFZ plugin for midi soundfonts - Audacity for processing WAV files - music21 python lib if I…

What are some Lily bugs you've encountered?

Nothing too major except I'm about 99% sure \after is buggy. I love LilyPond enough that I'll soon file a bug report. It's possible I'm missing something but I have ample evidence that \after in certain contexts mess up stuff.
Post reply on HN