page 2 | 38 posts new topic Store  
1 | 2 | 3
thread starter

I want to share with you guys, two opinions, seemingly dissagreeing.

One hexfix of the outfit Velvet Acid Christ, was interviewed for the Matrixsynth blog, and said: "
and it was the follwing that caught my attention:

link

"i spent years on the pc pulling my hair out, ever since cubase with audio in it, midi has sucked on the pc. cubase 2.8 was the last tight midi i ever got on a pc. i tried everything. and always got jitter of about 13 ms with even steinberg’s midi interface on external midi synths and drum machines.
It was an evil battle. i spent years trying to figure it out. no go. I came from the Atari st with notator and cubase. this was super tight and ultra responsive. nothing on the pc came close for midi. let’s not even get me started on how bad cubase sums and mixes digital signals. sonar 6 and saw studio kick the crap out of cubase for audio summing.

finally got a mac with an amt8 midi. running logic express.
WOW 3ms of jitter, just like cubase on the atari. it records me perfectly, something the pc could never do, especially when i was playing fast..
Logic is not much better at summing, but it records better, and i mix outboard now anyhow so. still saw and sonar 6 are king for digital summing and mixing.
But for midi, its logic all the way. it’s tight. cubase is not.

these are just my opinions. all based on the last 20 years of working on gear. It's all opinions. don't hate if you don't agree. it's like arguing that you like apples better than oranges. I'm not trying to tell anyone how to work or what to buy. I'm just talking about my own personal tastes and likes and dislikes."


Ofcourse, one could argue that in fact, he's comparing apples and oranges, and saying oranges taste sweeter.
I dont want to question his dislike for pc and favour for mac. Ive used the two of them, they both have their faults.

I am however curious about the question of midi timing.
A gentleman called kiwiburger, on the gearslutz site, said: "

"I was a loyal Ensonic sampler user for many years, and owned most models at some time. IMO, the D/A converters and/or analog stages were absolute shyte, and couldn't handle low bass. This was very evident on some samples that always clicked and farted on the low end. So there is plenty of distortion and noise going on to thicken up the sound. Not to mention the reverb that always defaulted to ON when you took a sample.

I use various software samplers, and have zero regrets. I've tried converting the old Ensonic samples, but basically my tastes have changed and I don't like them at all - not even for nostalgia.
There definately are some differences, when playing exactly the same sample - with no effects or filtering or anything.
Here is what is missing:

Noise - don't underestimate the effect that low level white noise has. I hate noise, but then again - sometimes when it's gone, I miss it. Analog dithering perhaps. (…) There is a an acoustic analogy - sound lacking bass can effectively have the low end restored if you have some low end noise to interact with the sound. Don't underestimate noise, whether in hardware samplers or analog summing or mag tape, etc.

Distortion - I have no doubt the cheap analog circuits added harmonics that thickened the low end.

Sample rate - (…)

Erratic Midi timing - the timing slop on midi hardware is shocking. I used to tear my hair out. Now I have perfect, sample-accurate timing - and it's too good. There is something about a little randomisation that our ears love. Whether is subtle wobbly tape, or erratic midi timing - a very, subtle, small amount of randomisation can be a very good thing."



Now I really dont want to get into a mac vs pc thing, and its not about hardware versus software either.

But there are still some myths surrounding digital music making that pop up now and then.
Keeping the channel faders up to 0dB (analog throwback), pci cards that are supposedly more prone to EM interference (soundblaster throwback) and then there's this midi timing thing.

Debunk please?

When have you run into sloppy midi timing; did it give a pleasent looseness to the music, or did you hear a digital mess?
Replies

i hate midi jitter, but not necessarily because i can hear it. mainly just because it drives me fucking crazy to sequence something on a module, go in to try and cut it up or loop it, and see that it's not even lined up on the grid that i used to compose it in the first place. it's damn hard to work like that. and impossible to get a good loop going when notes at the beginning and end of the desired area to be looped are randomly ahead or behind. this is on a Mac btw.

wow daswesen - thats... pretty comprehensive.
the usb thing is quite clear to me now.
the way the midi data is handled is fundamentally different when sent, transferred and received - and the tap only gets opened in bursts.
that sum it up?

korgborglar said: " i like it better that way, it adds to its lofi charm (…) but yeah, id like to see someone do a real experiment with this. "

i think its crazy - with all the overclocker and benchmarking and speedbumping sites, there are no real tests that say something concrete.
or my google skills are failing

bla - thanks a lot for the input.
384 notes on 14 tracks sounds like a lot indeed , but we're supposed to have Cray like pcs in the consumer marketplace now, right?
I did think that the pipes on modern computers were fatter than old sequencers with the one midi out.

mlbot said: "
13msec of jitter on a metronome is, well, not a big deal."


donald fagan is rolling over in his...bed

daswesen said: "
Also, midi is 31250 bps, which amounts to 3125 bytes per second. A midi note is 3 bytes, so roughly (if there is no running status), you get about 1 ms per note. send a chord (4 notes) and a couple cc for pedal or pressure. Woops, 15 ms for a single chord between first NOTE ON and last NOTE ON."


that was a trick i forgot about the start and stop bit. 10 bits right.
something else though if we want to get oh so geeky... if its a chord usually the notes following eachother will be only 2 bytes per note as the status byte is usually only sent if status changes. so for a 4 note chord: status byte + note#1 + velocity, note #2, velocity, note #3, velocity, note #4, velocity, status + cc + value. so on the best of situations that would be 12ms :D yay for the 3ms savior.

personally i think the not sending status byte behavior is annoying and should be mentioned more often to keep people like me wasting a day trying to figure out why something is a miss with my code.

haha yeah you can get into some deep shit with all the "hacks" midi has. Realtime bytes can interrupt anything. Midi Sysex can be closed with 0xF0 instead of 0xF7, stuff like that. It gets really funky when you start to merge midi streams.

bb01 said: "re: dark matter: you mean you can always go back to the editor to fix it?"


I should have fleshed that out! My thought process went a little off topic. All the different data-entry options - live playing without any quantizing, quantized performances, manually edited performances, directly entered sequencing data, on and on - don't really exist in parallel... there's a lot of overlapping use of each technique in every project. (At least for me.) So I was wondering how someone's preferred method(s) end up affecting the overall feel of their work and their perception of or reaction to (potential) MIDI timing issues.

mlbot said: "Perhaps the best would be to record the sound in a DAW and start counting samples/msec.
You'd have to assume that no jitter was introduced in the recording.

Unless you had an oscilloscope"


Oh smart. And I guess even if there was jitter in the recording - as long as it was consistent and reproduceable - would at least give you a baseline, in the sense that each sequencer could be compared to the other(s) when you compensated for the final recording's jitter?

(And I should qualify my "MIDI jitter doesn't bother me"[/jhoon_rhee] statement by saying that I've never needed to sequence more than three pieces of hardware at the same time. Short cables and a lack of 384th notes helped, too.) ;)
every track i've ever made was sequenced with MIDI-trigged hardware. build up a whole track with 3 drum machines and 3-5 synths with MIDI CC controlling filter cut-offs, MIDI clock going out on almost every port, etc. then press record. i never really noticed a problem with MIDI timing using a variety of USB interfaces in Cubase SX on a Mac. I ran it on a PC for a while and then on a Mac running Windows (effectively a PC) and didn't really notice any problems either.

when i read about people's nightmares with MIDI timing i'm just thankful that i either don't have the same nightmares or don't notice them. phew!

long cables will have no influence on timing, except they may be more prone to picking up noise.

minisystem said: "when i read about people's nightmares with MIDI timing i'm just thankful that i either don't have the same nightmares or don't notice them. phew!"

well - me too, only I always think my "palet is too rough"
I mean, maybe I should notice something

daswesen said: "long cables will have no influence on timing, except they may be more prone to picking up noise."


I know you know that MIDI cables don't trasmit audio... but "noise" to me sounds like you could be referring to white noise.
Which I am sure you aren't.

"errors" would be a better word, imo. And long MIDI cables can degrade all sorts of MIDi signals, like cause stuck notes, or even degrade MIDI beat clock signals which causes crappy timing, especially noteicable when your drum machine on the other side of the room flams with your softsynth drum machine.


bb01 said: "
minisystem said: "when i read about people's nightmares with MIDI timing i'm just thankful that i either don't have the same nightmares or don't notice them. phew!"

well - me too, only I always think my "palet is too rough"
I mean, maybe I should notice something "


lol. exactly. with all this talk about it i thought i would have noticed something by now. i always assumed i didn't notice because of my awful sense of timing.

since when has the quote function been working???

1 | 2 | 3

Register / login
You must be a member to reply or post. signup or login