Roland TR-1000 Rhythm Composer

The Lounge Other Gear
6548

I want to second this opinion : TR-1000 is a bad master clock.

My modular looses steps, Midi followers are hard to properly sync and also the analog clock out is meandering like the Amazonas.

If you come from an Elektron based setup/experience: the clock issues of the TR-1000 are not acceptable for this premium price

Otherwise: greatest drum machine in existence; sounds massive, faders are fun and loads of sound options (machines, fx, filter, outputs…)

Encoder acceleration could be finetuned and build quality is not on Elektron level

7 Likes
6549

So tonight I switched the TR-1000 to master clock adjusted 2 settings and it’s all good.

Project settings

General Tab

Sync Delay +5 (in my case) adjust to suit your gear
Track Delay - Select Layered Gens

My midi out 1 > Analog 4
My midi out 2 > TB-03

Settings might be different for others however it works for me. I just came across a video that made me try it.

2 Likes
6551

TR-1000 on firmware 1.22: Layered Gens mode vs All Tracks mode, at 100 BPM on its own internal clock.

In Layered Gens mode, the Rim Shot trigger output kept a steadier interval between hits than in All Tracks mode. The largest interval error between any two hits fell from 2.7 ms to 2.0 ms. The share of intervals that came out exactly right rose from 16.7 % to 39.2 %.

The MIDI clock generation went the other way. Its largest clock interval error grew from 0.6 ms to 1.0 ms.

The offset between the Rim Shot trigger output and the MIDI clock it sends out also grew, from up to 4.9 ms to up to 6.7 ms. Slaves would be further out of step with the TR-1000’s own trigger output.

In both modes, every timing error on the trigger output comes in whole multiples of about 0.67 ms. In All Tracks mode about 5 in 6 intervals were off by 0.67 ms or more; in Layered Gens mode about 3 in 5.

The details:-

Roland TR-1000 — FW 1.22 — MIDI Clock Out
Layered Gens Mode, Internal Sync, 100 BPM, 24 PPQ
2 x 5-pin MIDI Out, 318.9 s continuous capture, 12,710 clock intervals per port

Jitter Max: 1001 µs
Push-Pull Max: 1999 µs
Tempo Dev Max: 4.1555 BPM
Port Skew Max: 449 µs (Out 1 vs Out 2)

A perfect 24 PPQ clock at 100 BPM sends one pulse every 25,000 µs. The TR-1000 ranged from 24,001 to 26,001 µs.

1 in 8 clock intervals was off by 250 µs or more. 18 intervals were off by a full 1 ms.

The two MIDI Outs normally sit 8 µs apart. 29 times in the capture they split by about 450 µs.

Not all good - yet.

People hit a problem, search online and find a YouTube clip reporting a fix. The clip spreads and adds to the confusion, even though it’s one person’s workaround, checked on one output, on one firmware.

If Roland published timing data specs for each output, mode and firmware, this would all go away.

6 Likes
6552

Ordered one last night :drum::drum::drum::drum::melting_face:

13 Likes
6553

Those of you who have octatrack an t1k, how do you find them complement eachother? Just looking for some inspiration I guess

6554

I’m so happy the TR-1000 offers the same flexible approach to tempo than my actual drummer. And without using any drugs. I hope Roland will never fix it!

13 Likes
6555

Nothing to fix in regards to the TR-1000 and my setup. Love it!

6 Likes
6556

I’m having some problems with play back of Slices.
I’m on FW 1.22
I’m slicing a sample chain of loops, I’ve set the bpm for the sample, bpm sync and classic time stretch is on.

The sample starts on time, plays the slice through but then pause for 1 bar before re trigger. The slice length is an even number, as in 4 or 8 bars.

I tried to shorten the end and the start point of the sample(suggested tip on the web) but it doesn’t help.

I’m very used to dealing with samples on the OT so I guess still learning the Roland way but has anyone an idea of why I’m getting the 1 bar gap before re triggering?

6557

This is a known bug that has been reported by me and some other users. I hope they fix it soon. Better report it again by your own, because when I submitted it, the support sadly reacted like it was completely new to them.

2 Likes
6558

Thanks for letting me know.
That makes the TR a bit difficult to use with the sample chains, so hopefully they will address this matter in the long anticipated FW update

6559

Yeah this is the fix for latency when master but not jitter - see the many posts above re jitter - you may not notice/care

glad you’re enjoying it - it’s a beast, isn’t it?! :blush:

1 Like
6560

Definitely a beast mate. I’m spending all my free time mastering it. Finding new stuff out every day love love love hehe

2 Likes
6561

I’ve reported it to Roland now.

I´m very new to the sample side of the TR1000 and as a long time OT user, I need to get my head around the Roland workflow.
I was thinking if it would be possible to manually set the end point of the sample and use Play through instead of Slice On.
But I find it hard to get the exact end point of the sample when there’s no indication of bars on the screen, or am I missing something.
Also very time consuming trail and error process when using long sample loops.

6562

Sadly, there is no indication for that. Even sampling with the internal sampler to exactly four bars leads to this bug. Cutting the sample end won’t bring any satisfying results. So best to just report it so they fix it asap.

1 Like
6563

There is an audio gap bug when using that too, at the end of the loop there is silence

6564

There is or isn’t

1 Like
6565

Corrected

1 Like
6566

Thanks buddy.
Glad to know it wasn’t me being stupid but what a shame.
I’m doing a live set with the A4, TR and a microphone, and I was hoping to get some sample chains going on the TR.
Maybe I should just incl the OT in the setup instead of waiting for a new TR FW and move on….

2 Likes
6567

Great track! How much of this is built in sounds vs samples that you’ve added to the machine yourself? How did you make your galloping rumble or your drone background noise? Love it

6568

Thank you I thought I was doing something wrong. Glad I didn’t spend more time trying to problem solve