Comment by btown
2 days ago
As someone who's loved Logic Pro since the days before Apple bought Emagic, this is amazing that it will be accessible to a broader audience.
There are many discussions e.g. https://gearspace.com/board/music-computers/1433515-why-does... about the reasons for its popularity, but one stands out to me - its event data model.
There are far too many tools out there (from FL Studio on one end, to MuseScore on the other) that present piano-roll-based rapid prototyping and traditional western score notation as diametric opposites. From day 1, Logic challenged itself "what if we can use the same event-based data model to render both."
None of this complexity is hidden - you can edit the raw event stream directly. If you're a developer familiar with, say, React, it makes music creation quite intuitive - everything from visual to audio output is a function of a transparently formatted data store.
And while that has its challenges, and some of the UX innovations of e.g. MuseScore have been slower to arrive in Logic, because of this "dual life" it's unmatched as a pedogogical tool, and a professional creative tool as well.
There's a lot of information in a traditional western score that cannot be easily represented in a pianoroll, at least not losslessly.
Considering them as alternate views of the same data model gets problematic when the composer uses the full bag of tricks that score notation allows (notably repeats, but also the problem of representing tuplets correctly when a pianoroll can offer no clues about how to structure them). So for example, the user can create a set of notes in the pianoroll that will never be played correctly by anyone reading the score; the user can create dynamics in the score that cannot be correctly presented in the pianoroll version.
I'm not saying it isn't possible to do an MVC-style system with two different views of the same data model - it clearly is. It's just moving between the two views is not lossless, and moving between the two controllers (i.e. editing) is not equivalent.
How else could you represent piano roll data than as a stream of events? I thought that was ubiquitous since the invention of MIDI.
Are you saying other sequencers are unable to render the same data as piano roll and score?
Among professional-ready DAWs, as far as I know, it's unique in its approach. Pro Tools and FL Studio still don't have score rendering or even MusicXML export! Reaper has limited score rendering/engraving support, but minimal customizability.
And on the notation-oriented side, you have things like MuseScore, Finale, etc. where there is an event model, but the UI itself doesn't have mature (or any) support for tracking mixer/knob automation (outside of what can be derived automatically from dynamic symbols).
Years ago, I used Logic in a musical theater context where I could build a constantly-updated demo for pitching/rehearsals/live-iteration and edit the final orchestration to be printed for the pit orchestra, both from the same living document. Could I have duplicated my changes in a DAW and notation software separately, and kept them in sync manually? Absolutely, and many creators do. But there's something special about having that holy grail at your fingertips.
Among professional-ready DAWs, as far as I know, it's unique in its approach.
Cubase, surely? I'm pretty sure it has done this for decades unless I am misunderstanding what you're saying.