Hi,
I found some issue when recording a sound from the ADAT of Korg Trinity keyboard to the ADAT of my Pulsar2 card using Nuendo2....I think it was a jitter.
My Scope software is 4.5 and it was set to 96KHz, My Nuendo2 was in 32bit float point.
I had never heard jitter sound before but I think I heard it now, it was like a continuing click sounds.
My question is if it was Jitter, why it happened when I was not dealing with AD/DA conversion?..or any idea?
Thanks.
hc.
Is it Jitter?
Re: Is it Jitter?
no, that's not jitter.
which device was digital master and which was slave? afaik, sp/dif out of the Korg can ONLY be master, in which case Scope MUST slave to it, if you are going to make a digital transfer. is the Korg even capable of 96k? if not, the you likely have two devices. both master and atr different samplerates. naturally it won't work and will be full of clicks and pops.
which device was digital master and which was slave? afaik, sp/dif out of the Korg can ONLY be master, in which case Scope MUST slave to it, if you are going to make a digital transfer. is the Korg even capable of 96k? if not, the you likely have two devices. both master and atr different samplerates. naturally it won't work and will be full of clicks and pops.
Re: Is it Jitter?
Hi Garyb,
Thanks for the reply. A quote below is from Wiki.
"DI-TRI: added a 48 kHz word clock input and ADAT optical output. The main problem with the Trinity and digital linking at the time, was that Korg chose to design the synth using a 48 kHz, which is very common for post production and television work, but not the 44.1 kHz CD standard that most studios pro and consumer alike utilized. Therefore, it was difficult to clock unless an outboard box calculated a real-time conversion. Only the first four channels of the ADAT spec were used, and they were assigned to the classic Korg Output layout: 1/L, 2/R, out 3, out 4. These were fixed and non-assignable."
Does it mean the only solution, is to change Scope setting to 48K? Should the word clock connection be utilized also or not necessary?
hc.
Thanks for the reply. A quote below is from Wiki.
"DI-TRI: added a 48 kHz word clock input and ADAT optical output. The main problem with the Trinity and digital linking at the time, was that Korg chose to design the synth using a 48 kHz, which is very common for post production and television work, but not the 44.1 kHz CD standard that most studios pro and consumer alike utilized. Therefore, it was difficult to clock unless an outboard box calculated a real-time conversion. Only the first four channels of the ADAT spec were used, and they were assigned to the classic Korg Output layout: 1/L, 2/R, out 3, out 4. These were fixed and non-assignable."
Does it mean the only solution, is to change Scope setting to 48K? Should the word clock connection be utilized also or not necessary?
hc.
-
the19thbear
- Posts: 1499
- Joined: Thu Feb 20, 2003 4:00 pm
- Location: Denmark
- Contact:
Re: Is it Jitter?
You dont need wordclock. And yes. Switch scope to 48khz and slave it 
Re: Is it Jitter?
since Scope needs to be slave, it doesn't matter what setting you enter. the only thing that matters is the checkbox for "slave" and the source(the checkbox for sp/dif optical or coax).
actaully, i'd just use the analog outs for the Korg. first off, 96k is a waste, but using analog outs will allow you to remain at 96k. otherwise, if you are only doing audio, not video, i'd prefer to be at 44.1k, which will also require analog outs from the Korg. the sound will be more than fine that way. it's best to avoid doing really serious violence to your audio by resampling. ALL of your gains ftom being at a high samplerate will be lost in the resampling process, and the final product might even be worse than if you had been at the lower rate the whole time.
actaully, i'd just use the analog outs for the Korg. first off, 96k is a waste, but using analog outs will allow you to remain at 96k. otherwise, if you are only doing audio, not video, i'd prefer to be at 44.1k, which will also require analog outs from the Korg. the sound will be more than fine that way. it's best to avoid doing really serious violence to your audio by resampling. ALL of your gains ftom being at a high samplerate will be lost in the resampling process, and the final product might even be worse than if you had been at the lower rate the whole time.
Re: Is it Jitter?
HI There,
I am not sure my issue recording ADAT track into VDAT and then imported in Samplitude is the same, but it may be.
I have been bringing 8 tracks from my old ADAT into VDAT recently and have encountered some noise issues.
Some tracks have these great big clicks in them and some have a kind of furry sound.
I suspect the furry sound may be head dirt or damaged tape.
These are quite old recordings.
The big clicks I am less sure about.
The VDAT recording were done with the ADAT slaved to XITE via the ADAT B Source Module (48KHz of course).
I did not slave XITE to the ADAT source - maybe that might have fixed the problem, I don't know at this time.
I was wondering whether its SCOPE trying to cope with 8 recordings at once into VDAT.
Sort of a multiplexing click as it switches between channels.
You can see the clicks on this spectragram below.
This one has only two clicks whereas some have many more than that.
I am not sure my issue recording ADAT track into VDAT and then imported in Samplitude is the same, but it may be.
I have been bringing 8 tracks from my old ADAT into VDAT recently and have encountered some noise issues.
Some tracks have these great big clicks in them and some have a kind of furry sound.
I suspect the furry sound may be head dirt or damaged tape.
These are quite old recordings.
The big clicks I am less sure about.
The VDAT recording were done with the ADAT slaved to XITE via the ADAT B Source Module (48KHz of course).
I did not slave XITE to the ADAT source - maybe that might have fixed the problem, I don't know at this time.
I was wondering whether its SCOPE trying to cope with 8 recordings at once into VDAT.
Sort of a multiplexing click as it switches between channels.
You can see the clicks on this spectragram below.
This one has only two clicks whereas some have many more than that.
- ADAT Noise.jpg (826.7 KiB) Viewed 1485 times
Re: Is it Jitter?
just recording 8 tracks shouldn't make any pops or clicks, period.
a clock issue will always make pops and clicks. there can be only one master. when it is chosen, the other unit must be slave, or vice versa.
data travels between devices in "packets". the timing of each sample in each chunk of information(packet) must have an accurate clock for it to play back in time. two freewheeling clocks, even if they are running at the same speed, will create timing errors that are heard as a click or pop, since they won't necessarily be in sync with each other, leading to errors(the noise). one of the clocks must control the other(or both can be slave with an external clock source like bnc wordclock), so that all data from one machine to the other will have the same timestamp from the same clock. or something like that...
a clock issue will always make pops and clicks. there can be only one master. when it is chosen, the other unit must be slave, or vice versa.
data travels between devices in "packets". the timing of each sample in each chunk of information(packet) must have an accurate clock for it to play back in time. two freewheeling clocks, even if they are running at the same speed, will create timing errors that are heard as a click or pop, since they won't necessarily be in sync with each other, leading to errors(the noise). one of the clocks must control the other(or both can be slave with an external clock source like bnc wordclock), so that all data from one machine to the other will have the same timestamp from the same clock. or something like that...
Re: Is it Jitter?
Pretty obvious really.
Thinking about it I think ADAT has to be the Master.
I am not in the studio, but will check tonight. I dont think I can slave the ADAT anyway.
Thinking about it I think ADAT has to be the Master.
I am not in the studio, but will check tonight. I dont think I can slave the ADAT anyway.