Replies created

 

Viewing 4 replies - 1 through 4 (of 4 total)
  • Jared Lewis
    Participant

    I’m currently using an RME Fireface UFX+. It’s a beast! Aside from the rest of the instruments, we are running our Roland TD-10 to the RME via midi. RME to Surface Pro 6 (i5) via USB 3, SD3 stand-alone…no DAW, then out stereo from the RME to FOH. Works flawlessly! No lag, no delay. Latency is around 5ms, which is unnoticeable.

    To test the latency, we ran the Roland TD-10 brain and SD3 samples through the same monitor and both samples played together at the same time with no latency. In other words, the SD3 samples and the Roland samples played at the same time with no delay when stacked on top of each other. Two other people were with me and both verified they could not hear any latency, that both samples played at the same time to their ears. Followed up with rehearsal and everything was tight.

    RME states their drivers determine low latency, that all of their audio interface products use the same drivers. Of course, you have to use a computer/laptop that has a decent processor chip, like the Intel i5 we’re using. So in theory, you should be able to use any RME interface with midi capability to achieve low latency. But check with RME first to verify. Hope this helps!

    Jared Lewis
    Participant

    Update: After connecting the refurbished symbol, it appears that was only part of the problem. Traced the problem back to a setting in the VTech module. Apparently, there was a setting in my TD 10 assigned to a cymbal, which played midi background music each time the cymbal was struck on the rim. Couldn’t originally hear the midi music playing in the background because it was turned down to 0 db on the TD 10. Even though I couldn’t hear the music playing, it was still triggering within the system. This midi background signal was being sent to SD3, causing the SD3 drum set to go bonkers. When I turned off the midi background music setting in the TD 10, everything functioned properly in SD3.

    2

    Thanked by: Henrik Ekblom and Erik
    Jared Lewis
    Participant

    The problem occurred when I hit the rim of the cymbal. The location of the cymbal pad did not make a difference. The symbol itself was faulty. This particular model is a CY-8 dual trigger cymbal on a Roland TD-20. I Found some YouTube videos explaining how to pull back on the thick rubber part and clean the debris off of the sensor. When I opened it up, there were tiny rubber fragments on the edge / rim on the inside of the cymbal. Apparently, after years of striking the cymbal, small rubber fragments break off and interfere with the sensor trigger. I used some Goo gone and a rag to clean the rubber debris from the sensor and the rubber grooves. I haven’t had a chance to see if that fixed it. I had a spare cymbal laying around and used that as a temporary replacement. I’ll report back in a few days after I’ve had a chance try out the repaired CY-8.

    1

    Thanked by: Erik
    Jared Lewis
    Participant

    I had the same problem. Turned out it was a faulty cymbal trigger. Once I replaced the cymbal, the problem went away.


    Operating system: Windows 10
    • This post was modified 6 years, 1 month ago by Jared Lewis.
Viewing 4 replies - 1 through 4 (of 4 total)

No products in the cart.

×