1

[Mark Grace]

Thank you for the inquiry.

I tried DTX9, but it was worse than Pro.

DTX9 had not only the claps for closing (foot) hi-hat, but also had alternate sounds and tones for the Snare and Tom rims.

For the naming convention, if 9 now represents the 900 brain, I would suggest returning to DTX900, as that leaves no doubt for the end user. DTX9 looks like another release from Yamaha and leads to confusion for the end user as there is nothing there implying that 900 is now 9.

I’ve no idea when this all changed, but I have not played SDX “live” with the 950 kit since May, and did not notice any of these issues back then.

I can re-assign the MIDI notes from the 900 brain, or perform the “learn” function within SD3 and save it – but it’s just more time required, compared to previous SDX preset mappings.

+++

Reply To: DTX 900 (950) Preset Now Gone from SDX3??? version: 3.3.6
Operating system: Windows 10

[Mark Grace]

I just found this thread and wanted to thank you too Canauos!

Even though you state SOP4, it dropped in fine to SOP5!

I love SD3 and hope to do the same with some of the other libraries.

So two questions –

1. I do not see an export function, once a map is completed. How did you do that?
2. If one does a parallel installation of a new version of SOP, (recommended instead of simply updating) how does one point the newer version to the maps from the older version?

Your drag-n-drop method worked fine, so I guess I just need to figure out how you did an export of that map!

I could find no information on exporting maps in the manual, and the Search function in Exchange does not work for me.

Thanks again Canauos,
MG

[Mark Grace]

edrazor wrote:

having the same issue.. very frustrating!

Ed,
As much as I hate saying this, as I’m sure you have – be sure you’re running the latest version.

Toontrack fixed the “/+” filename issue in the latest update.

Other than trying to rename your files, you may need to contact Toontrack support…

Good luck!
MG

Reply To: SD3 Bounce – "Could Not Create All Files" – actually produced NO files version: 3.1.5
Operating system: Windows 10

[Mark Grace]

I just tried uploading files, but received an error window from support stating dmp files are not allowed…

I’m assuming sd3p files are also not allowed?

One would think that Tech Support could use those dump and project files.

So – I will need someone from Toontrack to email me an upload link.

Thanks,
Mark Grace

—

[Mark Grace]

John and Olle –
Thank you both for your recent replies.

I have no trouble sending the file directly to Toontrack. I just need someone to email me a link.
As mentioned, the client is not good with posting it on a public forum.

Olle –
You may be on to something –
During the bounce, it states first that Track1 is being bounced, then that each mic is being bounced out – but –
with MS Windows Explorer opened, I could watch the files being created, then SD3 CRASHED.

[see attached screen shot.]

Since SD3 crashed, the interim files are still there – but are those the ones I want? – Or are those the mic channels I already have?

Also – I ran the Microphone Channels Bounce again – and once again – it was successful.

This project is using Metal Machinery, and only one Kick Drum – the Right one.

Is it possible there are issues with this library, since it was created for SD2?

The client is very happy with the sound so far, and as mentioned – there is NO processing in SD3, other than summing, so
we really want to get this working.

Thanks again to you all for your help and time,
MG

—

[Mark Grace]

OK – Someone at Toontrack HAS to know what this error window signifies:

It is not a Microsoft pop-up error window, it is a TOONTRACK error window, so a programmer at Toontrack put it there for a reason… WHAT IS IT???

I only see it when attempting to bounce OUTPUT CHANNELS to audio from SD3.

When I bounced Microphone Channels, I ended up with 28 files – all good. But not sounding anything like what I heard on the SD3 2-bus in the DAW.

So, I decided to try my hand at bouncing output channels, and SD3 goes through all the motions, but ends up with the error window above.

To report further experiments:

1. I verified available disk space on three hard drives in this DAW PC and all of them have 300GB or more available.
2. I attempted another “Output” bounce after renaming the folder from “SD3_AudioBounce-2” to “SD3 AudioBounce 2” – no change, same error.
3. I created a new folder on the root of the audio drive, as opposed to StudioOnePro>Songs>ClientTrack>Bounce Folder – no change, same error.
4. I then created a folder on a different drive, in the root folder – no change, same error.
5. I then saved the project, and opened it in the stand-alone version of SD3 – no change, same error.

Someone at Toontrack has to know what that error window signifies, or at least has an educated guess of where to look!!

Thanks for any and all help,
MG

—

[Mark Grace]

Hmmm… that’s exactly what I thought.

Thank you Henrik.

I hope to save that session and open it in the stand-alone SD3, and see what happens.

Unfortunately, the client does not want his tracks posted on a public forum.

I have clients here this evening, but hope to try a few things tomorrow evening.

I will report my findings.

Thanks for your help and time Henrik.

 

 

1

Thanked by: Henrik Ekblom

[Mark Grace]

Thank you for the response Henrik.

The kicker here is that I had a perfect bounce with the pre-fader selection, but unfortunately, that did not sound anything like what I was hearing from SD3 in the DAW project.

Again – no processing – no compressors, no EQ, no effects… so SD3’s mix must have something going on with the summing, and I was hoping to get that sound with a bounce to stems.

So in an attempt to get the bounced tracks to sound more like what I was hearing from the SD3 2-bus, I tried going the separate outputs method.

Since there is plenty of room on the drive, and the previous mic channel/pre-fader bounce was successful, it leads me to wonder what the issue is with SD3’s outputs. The outputs are not assigned to the DAW, but because of the fast/silent bounce…they do not need to be, correct?

Yes – the latest version of SD3 is in use – that is the first thing I verified.

It’s odd that I easily got a great stem sound with SD2 and comments on the forums here state that SD3’s process is essentially the same…

I will try another folder, and worst case just use the pre-fader mic files, since that bounce was sucessfull.

Thanks again,

MG

[Mark Grace]

Thank you Sir Muso!

I just found your link, and I am certain that I will not be the last one looking for an off-line way to review the manual…

Highest Regards,
MG

[Mark Grace]

Great question Jacob, thank you.

I believe the issue stems from my initial misunderstanding of Tracker.

Since I wanted to hear the drum replacement in context (in real time with the music), I had Follow Host engaged and would start and stop SOP’s transport… hence the lag.

If I disengage Follow Host, and just work within Tracker, then everything [within Tracker] is in sync.

I’m used to the drum replacer in Sonar, which is the equivalent of Drumagog or Steven Slate’s Trigger, in that, you can audition the drum samples in real time with the music.

SD3 Tracker is superior (pun intended) but has a different work flow.

As I get used to converting to MIDI first, then dropping that MIDI back into the DAW, it will get easier.
This is a very similar workflow to Sonar Platinum’s integration of Melodyne Studio 4 to convert audio to MIDI, which I also use for drum replacement.

Thanks again Jacob.

[Mark Grace]

So you HAVE to have a tempo map for Tracker to work?

I saw a video on Groove3 where the instructor just drug the audio file in to SD3 Tracker, and it sync’d up with his audio in Studio One.

I have all audio tracks recorded live, without a click track, no midi files in the project, and the drummer and bass player are solid.

But when I drop the snare track file (the same file I dragged into Studio One Pro), after Tracker analyzes it, it will not sync up…

I was under the impression it would um…track…the audio file – like Drumagog or Steven Slate’s Trigger.

…or am I missing something?
Which is highly likely.

[EDIT]
Found it – “Tracker is an offline Audio to MIDI conversion tool.”
More time spent experimenting is in order…

Thanks!

[Mark Grace]

Greetings Joey – long time user of Cakewalk/Sonar here…
‘sure going to miss that program…

I’m also just getting started with Studio One Pro, and the browser allows you to simply drag SD3 out onto an instrument track and SOP will launch it.

The issue I’m having is with SD3’s Tracker –
I have had SD3 analyze a snare track from the file I dropped into the project, but it’s not lining up – there’s a delay in when the recorded snare hits vs the SD3 snare.

The buffers are set low, but I cannot get Tracker to play in sync.

There is no metronome/click track – the band was free-wheeling, but the drummer is solid.

I have “Follow Host” engaged, and the transport starts and stops with SOP, but I cannot figure out the sync issue.

Anyone have some suggestions?

Thanks!

[Mark Grace]

@Mat Anderson said:
Hi, I’d like to echo what Mark is saying. I’m a Yamaha DTX950 owner and have spent 3 days (count ’em) trying to get my RHH135 hi hat to trigger a smooth hi hat transition from fully closed to fully open by using the Yamaha preset in SD3 and tweaking the various parameters available in both the DTX Module and the SD3 software. It’s driving me nuts. Would any of the Toontrack team be able to rig up a RHH135 controller on a hi hat stand to see if they can solve this issue please? Merry Christmas to all BTW.  

Thank you for chiming in Mat!
I was starting to think I’m the last human with a DTX900/950!

By chance, did you have SD2 with the DTX900?
And did the hi-hat/edrum presets seem to work better out-of-the-box with SD2?

I’m just curious if you experienced the same difference.
Thanks!

Happy New Year Year All!!

[Mark Grace]

@rrosin said:

@Mark Grace said:
Alll well and good, but it does not help those of us with the Yamaha DTX900…

Why not? Is the DTX900 using a totally different approach for dealing with the hi hat? If you are not able to configure the settings yourself you could start by posting the raw MIDI data your module is sending. This can help you much more than just complaining.

Regards Reiner  

Mr. Reiner,
I DID post a lengthy report in a similar thread in this very forum, detailing the alterations and changes made to both the DTX900 module’s programming, as well as SD3’s mapping settings.

In searching for that thread, it appears to have been removed.
I searched on my drummaman moniker, as well as SD3 hi-hat variables, and my detailed post is nowhere to be found.

This is a similar thread, and providing feedback to Toontrack in the form of “something’s just not quite right” should be noted.

I would very much like someone at Toontrack to hook up a DTX900 module with the RHH135 hi-hat.
The default for the Yamaha eDrum preset setting in SD2 either got lucky, or there is something different in SD3’s Yamaha hi-hat/mapping preset.

As mentioned in my other post –
In charting the Yamaha’s CC4 data, via Sonar’s midi controller screen, I see a full range of motion from 0-127.

I have adjusted any and all DTX trigger/velocity response curves, SD3’s mapping curves, as well as went as far as turning off the internal polyphonic mode of the DTX900 module…yet I am still getting an out-of-place open, when I should still be getting a semi-open hat splash.

There is honestly something different in SD3 from SD2, with regard to the hi-hat functionality – when used with the Yamaha DTX900 and RHH135.

The preset for the Yamaha hi-hat in SD3 wasn’t even close out of the box compared to SD2.
With a substantial amount of tweaking in SD3, I have it very close.

The Roland adjustments shown in this thread do not help with the Yamaha system, and I was hoping to see another Yamaha DTX900 user chime in.

I truly love everything else about SD3.

Highest and kindest regards,
MG

[Mark Grace]

Alll well and good, but it does not help those of us with the Yamaha DTX900…

SDX2 worked much better!!

[Author]

Replies