Topic: Bug: Dragging groove parts into an existing block replaces block

Viewing 6 replies - 1 through 6 (of 6 total)

Replied December 2, 2021 at 17:50 #2842474
Bear-Faced Cow
Participant
Yup! They totally broke this feature while fixing everything else!

@Petter, @Olof: Is there no testing???!!! You guys have broken basic MIDI features in the past three releases!!! This is unheard of and borderline frustrating!

The only possible workaround that I have found so far is:
1. Drag the groove part to either an empty space or another song track in SD3
2. Cut/Copy the region with the groove part
3. Right-click intended region and select Paste on Selected Block(s) -> Your kit piece from the groove part
Might be the one of the ugliest workarounds, but at least we’re not totally dead in the water.

Jord

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/
- The post has been modified 3 times, last modified 3 years, 6 months ago by Bear-Faced Cow.
1
Thanked by: Mac McCormick
Replied December 3, 2021 at 16:56 #2842794
Brad
Participant
Vern Cantrell wrote:

I’m using the latest version.

Previously, I could drag groove parts (such as cymbals, snare, etc) from the browser into an existing block, and the parts would mix with the existing block.

However, in the most recent version of SD3, when I drag parts from the browser, the existing block is replaced/overwritten with the groove parts.

Is this a known bug or am I missing something?

Superior Drummer 3 version: 3.2.7
Operating system: Windows 10

The post has been modified 3 years, 6 months ago by Vern Cantrell"> 2 times, last modified 3 years, 6 months ago by Vern Cantrell.

A slight modification to Jord’s workaround would be to right click the groove you want to copy the kit part from, in the groove browser and select copy.

Then use step 3 from Jord’s instructions above. That seems to work as well.

Superior Drummer 3 version: 3.2.7
Operating system: macOS Big Sur (11)
Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

This post was modified 3 years, 6 months ago by Brad.
Replied December 4, 2021 at 14:12 #2843134
Bear-Faced Cow
Participant

Thanks Brad! That is indeed the less “ugly” workaround, relatively speaking, if you are going to be using the entire region. However, if you were going to use one bar of a two bar region, you will be forced to edit it on a track prior to using the groove part.

I totally get the fact that bugs happen. But, to break core functionality (and in this case more than once) and release it without proper testing is grossly negligent on any company’s part.

Here’s hoping that it’s not going to be another 7 weeks of misery.

jord

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

This post was modified 3 years, 6 months ago by Bear-Faced Cow.
Replied February 1, 2022 at 21:45 #2871682

Bear-Faced Cow
Participant

Looks like this has been fixed in version 3.2.8

Actually quite happy for this fix.

Thanx TT!

jord

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

1
Thanked by: Brad

Replied February 17, 2022 at 07:30 #2878272

yoontrack
Participant

I can’t even picture the workflow you’re talking about. How do you select groove parts from the browser? What? Where? The “work around” makes sense to me and I use it but the “dragging in” thing makes no sense to me but it sounds super useful. Help please if someone has the time. Thanks.

Replied February 17, 2022 at 07:42 #2878277

yoontrack
Participant

Never mind. Rtfm. Got it.
Author

Replies

Viewing 6 replies - 1 through 6 (of 6 total)

Bug: Dragging groove parts into an existing block replaces block

Superior Drummer 3 Help

Viewing 6 replies - 1 through 6 (of 6 total)