ensemble

If anybody can transcribe the Halo 3 ODST Rain in String Orchestra and Alto Saxophone, it'll be very good to play it in orchestral. Thx.

like the title says, also one of these for Farthest Outpost would be helpful.

Thanks,
dR

Can anyone show me (or help me to make a midi file? Because i've noticed that all my work is only in garageband (you might need to down load that in on a mac) but anyways, i just want to know how to make midis.

I WILL HAVE THE SECOND 'MOVEMENT' OUT SOON. MAYBE TOMORROW BEFORE 1 EST.

Finish the fight the first movement - "Duties" (i name things so please don't get confused) this has the first 18 measures of the song. it's a nice slow,tense build up till it gets to movement two which i like t call "This is the hour" Enjoy. Like I Do with all of my works, i include the actual score so you may us this in as a whole set. Thank you Jonathan Churchill for the score and tablature for this piece.

Difficulty : 3

Instrument List :
Woodwinds:
Piccolo
Flute I
Flute II
Oboe I
Oboe II
Bassoon I
Bassoon II
Alto Saxophone I
Alto Saxophone II
Tenor Saxophone
Baritone Saxophone I
Baritone Saxophone II
Clarinet I
Clarinet II
Clarinet III

Brass:
French Horn I
French Horn II
French Horn III
Trumpet I
Trumpet II
Trumpet III
Trombone I
Trombone II
Bass Trombone
Euphonium I
Euphonium II
Tuba

Percussion:
Bass Drum
Cymbals
Timpani
Piano

Here is one of my latest work. I have been arranging Earth city,Movement two for 3 months now and i have finished it. it's a incredibly hard song to learn and i advise people to us it or play it in a high grade concert or symphonic band (or you can just us it to play alone and get the parts for you.) Enjoy. Thank you Poop Scoop for the Orchestral version of this piece. with out it.. this wouldn't happen.. so thank you P.S. I do not have the concert band score so i will provide the orchestra score by Poop Scoop I will have later orchestra and woodwinds but that will be a different arraignment Enjoy
Difficulty: 7
Instrument list:

Woodwinds:
Piccolo
Flute I
Flute II
Oboe I
Oboe II
Clarinet I
Clarinet II
Alto Saxophone I
Alto Saxophone II
Tenor Saxophone
Baritone Saxophone I
Baritone Saxophone II
Bassoon
Bass Clarinet
Horn in F
Trumpet I
Trumpet II
Trombone I
Trombone II
Euphonium I
Euphonium II
Tuba

Percussion:
Piano (Harp)
Crash cymbals and Bass Drum
Timpani

Vocals:
Mezzo Sopranos

Here is Movement I of Follow our Brothers... (To me it is more organized). First 'Movement' is The Wait. the second movement is Brother in arms. But I'm posting the first one for now. It's nice and slow and basically a good song for a beginning Orchestra. Enjoy =) Thank you Mike Poe for the Tablature for this song =)
Difficulty : 2 1/2
Instrument list:
Violin I
Violin II
Violin III (Or Viola)
Cello
Violoncello I
ViolonCello II
Contrabass

Here is my version of"Never Forget". Thank you The-Halo-dragon For the Tabs, and notes for this song. i have added a small Woodwind mix in the track so a small woodwind band may play it as well. Enjoy! P.S. I will also add the Score Transcribed by The-Halo-dragon. on to the file so you may have the full set. Again, Thank you The-Halo-dragon.
Difficulty: 3 (notes that are a whole step from each other)
Instrument list:
Orchestra (Violin I & II , Viola , Cello and Contrabass in one)
Flute
Oboe
Clarinet
Alto Saxophone
Trumpet
Euphonium (In Bass Clef)
and Piano

I noticed in the version of the song, Greatest Journey, that's posted on this site that the first string and chorus intro was missing. That was one of my favorite parts of the song, so I decided to try and figure it out on my own. Here's what I got, I hope its right. It sounded just like it (to me).
In the folder is a MIDI file and Finale PrintMusic file.

Hello, I'm sorta new on this site, so I'll introduce myself real quick

I have recently become a Machinima Director and greatly appreciate Halo music. It has great musical quality and I enjoy it alot. I also play the violin, so I'm bound to organize a group to play some of these pieces.

Can some please make sheet music for full orchestra for Bits and Pieces? It's from ODST OST. It's quite a light, carefree, but very musical piece.

Thanks!

P.S. I might make One Final Effort Full Orchestra Scale, but I might have to base it off Jonathan Churchill's Piano Part.

Another mostly positive review for Halo Wars up at Spong:

I still enjoyed Halo Wars. I even enjoyed the cut-scenes that powered the single-player's short, 15 episode (mission) game along. The simple reason for my enjoyment is that Ensemble Studios (rest its soul) has produced an intelligent game that can be slipped into with or without an in-depth knowledge of what preceded it. It can, in fact, be slipped into without much previous knowledge of RTS games.

Check out the complete text.

Soulskill has posted a review of Halo Wars over at Slashdot. Generally his opinion was positive. He sums up the game thusly:

Ensemble succeeded quite well at establishing a control system that is powerful yet doesn't fight for intellectual real estate with the actual playing of the game. It's not a ground-breaking new entry into the real-time strategy genre, but, in a manner similar to the first Halo shooter, it demonstrates how well this genre can work on consoles. And it does well by the Halo franchise in the process.

Check Slashdot for the complete review and discussion.

My opinions and views on Halo Wars have, for the past couple weeks, been changing as often as my pants - once every few days - as new material comes out. As of right now, though, my enthusiasm, while still present, has reached its lowest point yet on its long descent from pre-E3 2007.

Originally, I was thrilled about Halo Wars. I'm an RTS fan, and I was looking forward to commanding armadas of hornets, fleets of scorpions, and long convoys of warthogs and marines. The first blow in that idea, however, came with the otherwise excellent 2007 E3 demo. I've always hated the idea of ONI coverups messing with established Halo canon, and when I saw that the flood would be featured in Halo Wars I lost a great deal of faith in the storyline. I still expected the game to be enjoyable, but any game that encountered the flood pre-Combat Evolved had a major downcheck against it in my mind.

Now we come to the demo and related announcements. I enjoyed the game, but was disappointed by the unit cap. But, I thought, that was just a demo thing - I'd be able to send my horde into battle in the full version, right? Wrong. The unit cap is, according to a recent Ensemble interview, the same in the full version as the demo. So much for the horde.

I'm now at a point where I actually expect the storyline to be great - the unauthorized "transformers" cinematic trailer renewed my faith in the story, and psyched me up for the game. But the news about the unit cap has put a very large damper on my enthusiasm. I end, now, in the opposite position as the beginning - huzzah for the story, but a quiet tear for the gameplay. I hope somehow to be proved wrong on the latter count, but I don't think that likely.

-LPG

I need to make a band arrangement for my band class to play and its worth a lot of band mark so if anybody can transpose the song.Id appreciated very much.

I just need 8 bars of the halo main theme for these instrument

flute, Clarinet,alto sax,b.sax,french horn,tuba,bass guitar,xylophone/guitar,percussion,bar.tc,trumpet.1,trumpet.2

If anyone did it they can send me through this hotmail iviet@hotmail.com

What started as another one of those rumors within the span of a day became a confirmed truth: following the release of the upcoming Halo Wars RTS game for the Xbox 360 console, Ensemble Studios, known for the Age of Empires RTS series of games for Windows, will be shuttered. A new studio, like Ensemble part of Microsoft Games Studios, will be formed to support Halo Wars. Employees releated to Halo Wars will be offered spots in the new studio; those currently working on the project have been offered extra incentives to continue working on it through release. Those not directly related to Halo Wars are being let go.

This is being called a "fiscal move" designed to "grow" the company's game efforts.

This is a strange move on many levels, and deserves examination in a wider context.

If the staff working on projects unrelated to Halo Wars formed a significant portion of the studio's payroll, then removing them would indeed make the studio less expensive. However, paying incentives to keep the Halo Wars staff makes them more expensive than they are currently, and also negatively impacts morale. So unless those employees were more numerous or more expensive, those gains are long-term and not short term; and that assumes that they were not working on projects that were going to generate revenue, since that potential revenue is now lost.

The timing of the news is also interesting. There's never a good time for someone to hear that they've been fired or laid off, but the gaming press has covered several studio shutterings that occurred right after a game's release; perhaps Microsoft considered that announcing the closure nearer to Halo Wars' actual release date might negatively impact the game's sales, and so elected to do it earlier. Once people have been given their pink slips they can hardly be expected to keep entirely silent, especially with friends in the industry, so there was no way to keep the closure secret for any length of time; hence the quick confirmation.

I've seen several posters on various message boards wonder aloud why Microsoft didn't just buy Ensemble. That's just it. Microsoft didn't have to buy Ensemble. They already owned them. Microsoft's high profile studio acquisitions now have a decidedly checkered history. FASA stumbled and was shuttered. Rare tried to make a shooter to appeal to the Xbox demographic and missed the mark, even though it had the field at launch nearly to itself. Their other title, Kameo, was more in line with titles from their Nintendo days, but also received a mixed reaction. Viva Pinata looks like their strongest Xbox 360 title, but it also sits in a niche by itself amongst sports games and shooters.

Then there's Bungie; the unexpected blockbuster that spawned a hit trilogy and a staggering array of related merchandise, propelling the studio from its position as a critically acclaimed Macintosh developer with occasional financial problems to a mass market juggernaut.

Then they walked out the door, leaving Microsoft with the franchise and industry watchers scratching their heads. The goose who laid the golden egg left one last present, left the farm to hang out its own shingle, and prompty announced it would keep supporting and enhancing the eggs, but that new and as-yet-unannounced golden items would be coming in the future. This kind of thing doesn't happen every day.

This might have convinced Microsoft that the way to continue to build its Xbox empire isn't to acquire good independent developers, treat them nicely, let them keep their own corporate culture, and let them do their own thing, because ultimately when you do that, if they're successful enough they'll just leave. If they keep making games for your platform that's good, but suddenly you're getting only the publisher's take instead of the whole enchilada; and ultimately that independent studio might decide to develop for other platforms, and you've lost exclusivity with your premier developer. In short it makes the entire experience with Bungie look much like what I thought it was at the start: not the acqusition of a studio but the acquisition of the Halo property. Despite all the hot air about Bungie's talent and innovation, what Microsoft wanted, and what they ultimately got and had to keep-- and ended up acquiring on the cheap compared to developers like Lionhead-- was Halo.

Now Ensemble Studios is feeling the repercussions of Bungie's independence. The independent identity of the studio Microsoft bought, Ensemble, is being destroyed, to be replaced by a Halo Wars-focused division of MGS that will help monetize the property that Microsoft was able to rescue from the Bungie departure. It is largely a symbolic move; those people worked for Microsoft before and they still will. What is being removed is the idea of that group as something separate from Microsoft; the knowledge of their history before Microsoft, and the kernel of the idea that just as there was life before Microsoft, there might be life after Microsoft. When the studio is a group just part of a larger team, with a name assigned to them that bears no relation to the studio Microsoft purchased, the risk of those people going independent is minimized.

UPDATE: The above was written before I saw notes at Kotaku that indicate that while MS retains ownership of Halo and of Age of Empires, the new studio that is replacing Ensemble will, in fact, be independent of Microsoft, as Bungie is. This ends up painting a picture in which rather than trying to prevent further defections from MGS, what it in fact is doing is divesting itself of game development and becoming more of a pure publisher-- letting independent companies bear the costs of financing and developing the games.

In the end, the real casualties seem to be Ensemble's PC developers. With Starcraft 2 looming in the future of RTS games for Windows and Microsoft focused squarely on building and expanding the Halo property and continuing to add genres to the Xbox 360's repertoire, there was no room for Age of Empires. No room for the idea of Ensemble Studios, a group that used to make its own decisions and might again someday.

I wonder what is going through Peter Molyneux's mind right about now?