1

[Alan Cox]

Hi everyone,

I’m just checking to see if there has been any further development on this please?  I’m using SD3 in Reaper. Even though I haven’t changed any mappings the score is all over the place in Reaper in regards to the MIDI drums. I’d love to be able to easily export my MIDI drums to a standard drum notation score as I’m getting asked for this score. I’m not really looking at the Mixcraft option as I don’t want to buy and install another DAW. I’ve tried exporting the MIDI from Reaper and putting that into Guitar Pro as that has a drum tablature function but it’s not worked.

Thanks in advance!

Reply To: Drum Notation version: 3.1.7
Operating system: Windows 10

[Alan Cox]

@melaniedmika haha it can be at first it’s like anything, practice it enough and soon it becomes easier, blast beats can be kind of like bouncing a basket ball, all about control.

Thank you for checking it out!

[Alan Cox]

Thank you all for taking the time to check out the video, I really appreciate it.

Hey Mcgarnacle, massively appreciate the feedback. Yeah, the video filter was initially used because I was trying to create this cartoon brand which I think may have been ok in concept but not so good in execution. I’ve removed it for my videos going forward (just uploaded a new one to my YouTube channel). Video editing is very new to me so hopefully going to get better at colour grading as time goes on.

Thanks again!

[Alan Cox]

Hey Digitalpimple,

Thank you for checking it out.

I’m using a Yamaha DTX900 module with DTXtremeIII triple zone pads.

It works like a beauty with the Superior Drummer 3 software 🙂

[Alan Cox]

Hi Olof,

Thank you for your help. I’ve tried this and unfortunately the issue remained. It’s so strange and seems like a very unique problem.

 

I do however think I’ve resolved it. I saved the drum kit within SD3, then started a new/empty drum kit. I then loaded my saved drum kit within SD3 and instead of loading the settings as a whole chose the drum set and mixer settings in the load options dialogue box. So far so good.

 

I’ll let you know if the issue does return but I’d like to thank you all for your help, patience and the great community here. SD3 is killer software and I can’t wait to release what I’ve done very soon.

All the best,

Al

Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
Operating system: Windows 10

[Alan Cox]

Hey everyone,

I’m not getting any resolution with anything else and so want to explore the ‘midi-learned CC’ aspect more, but I don’t know anything about it.

Please can you help me with reseting these? I couldn’t find anything in the overhead bleed options to reset them.

Thanks again in advance,

Al

Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
Operating system: Windows 10

[Alan Cox]

Hey Olof,

Unfortunately not, I’ve never used those settings. I’ve also checked them and there’s nothing set. My first thought was that some kind of automation was possibly overriding it but no results.

Cheers,

Al

Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
Operating system: Windows 10

[Alan Cox]

Hi John,

 

Apologies, I’ve got SD3 running in Reaper 64-bit.

8 CPUs, 2.8-3.8GHz Intel Core i7-7700HQ processor

16GB RAM

Nvidia 4GB GeForce GTX 1050

 

Cheers,

Al

Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
Operating system: Windows 10

• This post was modified 5 years, 11 months ago by Alan Cox.

[Alan Cox]

Hi Jord,

 

Yeah it’s really strange. It happens on everything in the overhead bleed. I’ve used the same drums and cymbals for some time (all from the core SD3 library), only now has this issue started. It could be happening on bleed volumes but I’m not changing these so can’t say.

 

Thanks for your help

Al

Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
Operating system: Windows 10

[Alan Cox]

Tried that too. Unfortunately no positive results. The same issue persists 🙁

Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
Operating system: Windows 10

[Alan Cox]

Hi Mick,

 

Thanks your input. I’ve saved it in both ways. When I recall those saves the correct settings are applied, but still whenever I close the SD3 plugin window in my DAW the settings revert back.

Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
Operating system: Windows 10

[Alan Cox]

Thanks for all your feedback guys.

Scott – I’m not sure what to say. You’ve suggested something that I’m already doing.

Bcslaam – the soundcard is USB and the SD3 SSD is USB. Both in their own USB 3.0 ports, I’m not sure what I can do to change that.

Jack 007 – I have NVidia GPU

[Alan Cox]

I removed SD3 and my RAM usage is around 0.8GB

[Alan Cox]

Hi everyone, apologies for the delay in getting back to you on this. I’ve struggled to get back into the studio over Christmas and New Year. Thank you for your responses and patience whilst I get back to you.

I conducted some fault finding following the information that WGN5150 gave and it looks like this user is bang on the money. Toontrack’s suggestion that Line6 is to blame is incorrect. The issue that I’m experiencing goes away when I change SD3 to either 16-bit mode or remove some of the microphones/bleed/surround channels. This is freeing up memory to let the VST work more seamlessly. With most other variables tested and no change in behaviour experienced this is the only conclusion I can come to. So I thought, let’s double check my system specs against the minimum and recommended system requirements for SD3. I have 8GB DDR4 memory on my system which meets the recommended system requirements on Toontrack’s site. So now I wonder why a system that meets the requirements of the software is struggling to run it. I also now have an SSD of the SD3 sound library that is unusable because if I want the samples at 24 bit resolution I can’t use anything but the basic sound library.

[Alan Cox]

Hi Scott, thank you for this suggestion. I’ve just tried that (set to the largest buffer size I can without getting noticable latency – around 256), instead of the audio glitches I’m now getting dropouts instead. This occuring on playback now too.

I don’t know if this is cause or coincidence but the glitches with UX2 ASIO and dropouts with ASIO4ALL drivers seem to occur more when I’m opening and closing the hi-hat.

[Author]

Replies