Symphony No. 1 (Carter)

The Symphony No. 1 is a symphony for orchestra by the American composer Elliott Carter. The work was originally completed in Santa Fe, New Mexico on December 18, 1942, though Carter later revised the work in 1954. It was first performed on April 27, 1944 by the Eastman-Rochester Symphony under the direction of Howard Hanson at the fourteenth annual Festival of American Music. The piece is dedicated to Carter's wife.[1]

Composition

The Symphony has a duration of roughly 25 minutes and is composed in three movements:

  1. Moderately, wistfully
  2. Slowly, gravely
  3. Vivaciously

Instrumentation

The work is scored for an orchestra comprising two flutes (second doubling piccolo), two oboes, two clarinets (first doubling E-flat clarinet), two bassoons, two horns, two trumpets, trombone, timpani, and strings.[1]

Reception

The Symphony No. 1 has been praised by music critics. Reviewing a 2003 recording of the work (among other Carter pieces), Arnold Whittall of Gramophone wrote:

The wartime muscularity of the Symphony No 1 (completed in 1942 but heard here in its 1954 revision) is clearest in passages which echo, or anticipate, Copland's more extrovert orchestral scores of the same period. But that triumphalist spirit is most productively on show in Carter's splendidly brash Holiday Overture (1944). The Symphony as a whole is less straightforward, more varied in style and character, and the slow movement in particular moves from hymnic meditation into more ambiguous regions of expression in a manner that might not be completely convincing. It is certainly distinctive, however, and fits well with the balance between restraint and exuberance that typifies the work as a whole.[2]

gollark: This person apparently reverse-engineered it statically, not at runtime, but it *can* probably detect if you're trying to reverse-engineer it a bit while running.
gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.
gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.
gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.
gollark: That doesn't mean it's actually always what happens.

References
  1. Carter, Elliott (1942). "Symphony No. 1". G. Schirmer Inc. Retrieved February 11, 2016.
  2. Whittall, Arnold (March 2004). "Carter Symphony No 1; Piano Concerto: Elliott Carter makes his Naxos début with an ear-catching programme". Gramophone. Retrieved February 11, 2016.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.