


It would also appear to me to be an indication that the random clicks are either clock problems, or some process in the computer stepping on the recording at just the right moment and energy to create a spike. Depending on the editing tool you're using, the good thing is that you should be able to smooth random clicks with the drawing tool at the sample level and get rid of that annoyance. You may have to zero in on the click sound a little at a time before you can find the visual affect of the click on the waveform, but if it has been captured in the recording, it will show up. Search around in the general area of the click, vertically zooming in on the waveform if necessary and look for even the slightest spike going against the contour of the wave display. wherever you hear a click during playback. One way to discover if the random clicks are actually affecting your tracks, is to zoom way in on the waveform. I have made digital audio interconnects in this fashion before and they always worked - however, I am wondering if RG6 really is the problem - not sure!!! Now before you tell me that is the cause of my woes, I used RG6 coaxial cable and on each end I used a 360 degree double bubble crimp system (American) which ensures a very good quality connection as it does not crimp hexagonal, rather circular, and strong. One other thing I feel i should mention, the cable conceting the two machines, I made myself.
Capturesync Pc#
Please bear in mind that this is a newly built PC (three months old and rock solid), running Win 7 X64, and a very decent spec of processor, RAM etc and also an 800W PSU.Īgain, I know that there are prbably no readers her who use the 2480/QUAD combination, but I thought it would be worth asking. I have since read that the QUAD does not have a jitter correction capacity, and as the VS is "slaving to it" this may be the problem, but really - given that it worked fine (VS - to PC) using an optical two-way link for years, how could this be? It sounds like the two machines are not truly synchronized. I have paid careful attention to ensure that the input levels are not digitally clipping. Just to clarify - this happens when I have 1 coaxial connection - linking my PC (with USB 2.0 connected Roland Quad Capture), to my VS-2480 via coaxial cable, the only digital connection presently connected in the system) What I am finding, is now (Day 2 of having the Quad) that there are random clicks, and what is even more random is that they come sometimes from the left channel and others from the right, but never simultaneously from both! I have tried using the internal clock of the 2480 to lock in the coaxial - this really is not an option as there is constant digital pop/click, telling me that it absolutely needs to lock in to the source. The 2480, using its coaxial input needs to sync to the PC (Quad) or else I get noise. I am not sure what the reason for this is, but ideally I would like to be able to have both scenarios hardwired in and simply use it as and when I need, avoiding a feedback loop by disabling monitoring on the input of Coaxial Input of the Quad when not needed.Īny thoughts and suggestions would be welcome. If I disconnect either one, then the remaining cable does what it is supposed to.

The problem is that if both of those cable are connected at the same time, the SYNC cannot "Lock in" and I have awful popping and clicking etc. I also wanted to use the Coaxial Output on the 2480 to send the master L/R (or anything else I needed to ) out to the Quad's Coaxial Input, to enable me to do editing or capture a mix digitally etc. To achieve this I also have to match the 48 kHz 24-bit settings on both machines - and select Coaxial I/O on the 2480 to "Lock " the two devices together. I have a Roland VS-2480 and have just bought a Roland Quad-Capture to enable me to interface with my Win 7 64-bit PC.Īs the Quad doesn't have Optical (Toslink) connectors, I opted to use the coaxial connectors on the back of the unit to send the main L/R from my PC to my VS-2480's Coaxial IN and sdet up a pair of channels hard panned to monitor the signal. I just wanted to run a scenario by you all in the hopes that someone here may have encountered the same situation (or similar) and may have a workaround.
