Jump to content

Colin OOOD

Members
  • Posts

    4008
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by Colin OOOD

  1. Colin ask Arno Polaris about Nina , ull get some evidence

    Is that someone on this forum?

     

    A few people have apparently cybered with her on MSN but no-one who has ever written anything about it has ever said they've actually met her, apart from Thomas. No photos in the studio, DJing, or even partying.

  2. she is real

    What evidence do you have for this?

     

    On 2008-01-23 10:50, chuha wrote:

    i live near munich and i know thomas and some label djs are friends of mine ... but never ever some of them mentioned anything about nina. and i never saw her on any party here. she was once supposed to play in munich but thomas said that her mother is in hospital and seriously sick ... if this isnt true it is for sure a very bad joke.

     

    once i asked thomas about nina and he said that the album will sell very well because of all this publicity ... i guess he tinks that even bad publicity is just publicity and publicity (doesnt matter wether its good or not) will increase the sales ^^

     

    i dont care of any success of it or not ... its just a hype created out of some bored and weird business mind.

     

    i mean, if nina would exist in real life, why wouldnt she give a statement here? because thomas forbid it?

     

    we are all slaves :D

  3. Really?

    Really. The two are a pair and interact in a complex manner to produce a quite unique sound, and driving a MIDId-up TB303 from a computer sequencer produces very different results to driving it from its internal seq. The '303 sound' is a product of both elements; this is a major reason why 303 emulations also attempt to model the sequencer, rather than just the synth part. Also, because programming a TB303 is so fkn difficult, you quite often get very unexpected results, and I'm utterly positive that more than one classic 303 tune is based on the happy accidents this causes.

  4. Hey Jon, thanks so much for voicing your thoughts, I'm really glad you like it as a whole.

     

    I agree that Eye of the Beholder is a standout on the album, and this is why we decided to use it as the last track. However I think you are indeed asking a lot of us to produce an album full of material with the same vibe, as - let's not forget - that track was written with and arranged and produced and engineered by someone who has no part on this next album! Basically, you can ask for whatever you want from us (as of course you can with any artist), but in the end we can only write what we write. You will be disappointed if you're expecting an album full of Eye of the Beholder. All I can promise is that we are taking as much care and time and putting as much love into this next album as we did with the last, and that the end result will be something that we as a band are all individually proud to put our names against. Free Range was what I call a 'fuck it' album - "fuck what everyone else thinks, fuck trying to sell shitloads of copies, fuck getting lots of gigs off the back of it, let's just make the record WE want to make and make it the best fucking record we possibly can". FourThought has a similar attitude in its creation at the moment and I'm sure it will surprise some people, for good or ill... whether this will translate to a similarly good set of reviews is another matter; I have hopes but no expectations. It would be great if it did... if not though, well fuck it. :P

  5. Do you people know how to use the automation in Cubase for a synth in Reason?

    It's probably very easy, but I'm really a noob with cubase and the manual is so loooooong.

    You need to find the MIDI CC# for the parameter you want to automate, and use the MIDI automation for that controller on a MIDI track in SX that is sending to the Reason device you're automating.
  6. I understand. However, my issue is this. On my car stereo I have a volume meter. Almost all the music I listen to is about as loud as I like it at about 4.5. It's predictable, and I don't have to fuss with the volume, just like with a good recording I don't have to fuss with the bass or treble. But with, again, Eat Static's new one, I have to lower the volume to under 4 or it will break my speakers. That's what I mean. It makes me think, whether it's true or not, that thickness of sound is being traded in for loudness, which makes me enjoy that wonderful album less than I would otherwise.

    I fully understand there can be a tradeoff between perceived level and dynamics, and that there is a degree of subjectivity over what sounds good and what doesn't, but your car stereo is not an audiophile playback system and the bolded phrase above implies that you're letting your eyes trick your ears to some extent. The only real question is "does the album ACTUALLY sound badly mastered?" Don't let yourself be tricked into hearing something you're not actually hearing. When listening at home, at regular levels, do the tracks sound overcompressed? ie., do they seem to get a little quieter when they kick in after a break, or sound grainy and bass-light? The better the basic mix, the more level it's possible to get out of it without negatively impacting the sound for a mastering engineer inclined that way, and Mr. Pepler is getting quite good at this by now.

     

    Having said that, I'm looking at the waveforms for Tarantaloid and Sucker Unit now, and with a peak RMS hovering around -4dB they do seem (when considering just the numbers) to be mastered a little past the extreme of what accepted good practise considers 'too loud'. But then again, for all that it's louder than most other albums, it sounds ok...

  7. I'm getting pretty annoyed with this loudness war thing myself. I don't understand it. I mean, we all have volume knobs, no? How does louder equal better? The latest Eat Static, for instance, although a lot of fun, is annoyingly loud.

    You have a volume knob, no? Turn it down.

     

    ;)

     

    Bob Katz has a good take on it in his Mastering Audio book; the aim of the mastering engineer is to make the music sound as good as possible on as wide a range of replay equipment as possible. We can see that the optimum playback experience on a 50K Opus rig has different requirements from that for an MP3 player with shitty earbuds being listened to on a crowded train. The first scenario needs very little compression, as the available dynamic range is simply immense, and the rig has more than enough headroom to accurately reproduce the loudest peaks when the volume is such that the quietest passages are nice and loud; unless you have hot-swap eardrums, the second scenario requires relatively heavy compression to ensure that either quieter sections don't get lost in the background noise, or the louder sections don't make your ears bleed when you've got it turned up loud enough to hear the quiet bits.

     

    It's the mastering engineer's job, then, to hit the top of the bell-curve of listenability; to provide as good a sound as possible on as many replay systems as possible. This will inevitably involve compromises - there will always be some replay systems unable to make the most of any particular master, and there will always be some replay systems for which the music has been over-squashed - but this is unavoidable when there is only the budget for one distribution format and therefore one mastering per track. The mastering engineer has to be aware that the track will be played on big festival systems and iPods alike... and since tracks are played more often on personal music systems than on 50K Opus rigs, the mastering is inevitably skewed in the direction of more squash.

     

    Plus no-one wants their track to be quieter than others when they're being played out. Sometimes when DJing it's not possible to raise the volume of a track past a certain point (for instance if you've been warned twice already by the soundman for clipping the mixer :P ) so if your peak level is fixed, each track needs a similar RMS to sound the same level, which also skews mastering in the direction of matching the louder tracks out there.

     

    $0.02

  8. Started with Steinberg Pro 24 on the Atari ST, then used a Chase Bit master keyboard with built-in hardware sequencer for a while. Then Voyetra Sequencer Plus Gold on a 286 PC, then Cubase on the Atari, then Cubase v1.0 for Windows 3; at various points in-between I also used the step sequencers on the SH-101 and Sequential Six-Trak synths, and a Yamaha RX17 drum machine, if they count! :D I got Cubase for my PC in 1992; I've been using it as my main writing platform ever since. Since 1999 or so I've also used Acid and Audiomulch for the occasional project, and regularly use Reason and Ableton Live.

×
×
  • Create New...