Peter Schmidl

Peter Schmidl (born 10 January 1942) is an Austrian clarinetist.

Peter Schmidl

Schmidl was born in Olomouc, Czech Republic, and studied clarinet at the University of Music and Performing Arts, Vienna.[1] He was the principal clarinetist of the Vienna Philharmonic Orchestra. He has played with the MDR Orchestra, the Salzburg Mozarteum Orchestra, and the Tokyo New Philharmonia.[1] He has taught at the University of Music and Performing Arts, Vienna since 1967.[1]

Discography
  • Classical Bliss, with various artists. Naxos, 2009.
  • Mozart: Clarinet Concerto / Symphony No. 25, with the Vienna Philharmonic Orchestra. Naxos, 2006.
  • Chill with Beethoven, with various artists. Naxos, 2006.
  • Beethoven for Meditation, with various artists. Naxos, 2005.
  • The Art of the Clarinet, with Madoka Inui, Teodora Miteva and Pierre Pichler. Naxos, 2003.Peter Schmidl is the son and grandson of Vienna Philharmonic clarinetists he comes by the Viennese tone and style naturally

Decorations and awards
  • Gold Medal of the Province of Salzburg
  • Honorary Ring of the Vienna Philharmonic
  • Grand Decoration of Honour for Services to the Republic of Austria (1999)[2]
  • Large golden belt of the Vienna Ambulance
  • Cross of Honour of Cultural Merit of the Republic of Romania
  • Appointment as Special Advisor for Cultural Exchange by the Japanese Ministry of Culture
  • Mozart Silver Medal at the International Mozarteum Foundation
  • Austrian Cross of Honour for Science and Art, 1st class (2008)[3]
gollark: Git stands for GIT Is Tremendous.
gollark: The stages of git clone are: Receive a "pack" file of all the objects in the repo database Create an index file for the received pack Check out the head revision (for a non-bare repo, obviously)"Resolving deltas" is the message shown for the second stage, indexing the pack file ("git index-pack").Pack files do not have the actual object IDs in them, only the object content. So to determine what the object IDs are, git has to do a decompress+SHA1 of each object in the pack to produce the object ID, which is then written into the index file.An object in a pack file may be stored as a delta i.e. a sequence of changes to make to some other object. In this case, git needs to retrieve the base object, apply the commands and SHA1 the result. The base object itself might have to be derived by applying a sequence of delta commands. (Even though in the case of a clone, the base object will have been encountered already, there is a limit to how many manufactured objects are cached in memory).In summary, the "resolving deltas" stage involves decompressing and checksumming the entire repo database, which not surprisingly takes quite a long time. Presumably decompressing and calculating SHA1s actually takes more time than applying the delta commands.In the case of a subsequent fetch, the received pack file may contain references (as delta object bases) to other objects that the receiving git is expected to already have. In this case, the receiving git actually rewrites the received pack file to include any such referenced objects, so that any stored pack file is self-sufficient. This might be where the message "resolving deltas" originated.
gollark: UPDATE: this is wrong.
gollark: > Git uses delta encoding to store some of the objects in packfiles. However, you don't want to have to play back every single change ever on a given file in order to get the current version, so Git also has occasional snapshots of the file contents stored as well. "Resolving deltas" is the step that deals with making sure all of that stays consistent.
gollark: A lot?

References
  1. "Schmidl, Peter". Naxos. Retrieved 2009-08-06.
  2. "Reply to a parliamentary question" (pdf) (in German). p. 1279. Retrieved 9 March 2013.
  3. "Reply to a parliamentary question" (pdf) (in German). p. 1861. Retrieved 9 March 2013.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.