167

[Bear-Faced Cow]

Are you using any different mapping in your preset/project?

What is being played back into SD3 from SO4? You can find this out in SD3’s MIDI monitor.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

Thanks for the very self-entitled remarks. I hate to break the bad news to you but you’re going to be finding yourself working around all software, regardless of what you think. And yes, it is cosmetic in the PM, and not functional. It does not affect your library installation or the playability of SD3, nor does it really hamper the over users experience in any damaging way. You’re just bugged by it because you have to look at it. Nothing more.

Just because they aren’t outputting software to your timeline, that is no indication that they are either uncaring, or incompetent. The fact that they took care of some major install bugs in the last round shows quite the opposite. And considering that they have had numerous releases since launch, is more of an indication that they are paying attention.

Perhaps, go make some music rather than complain in your first three posts.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

1

Thanked by: Alan Scott

[Bear-Faced Cow]

So far I see two potential issues:

1. Your drum MIDI technically starts at Bar 8 (your controller information in the region might be ignored on export) and your tempo marker is at Bar 1. Hence no beginning tempo marker in your export.
2. Your change in tempo is a ramp. Logic handles ramped changes in tempo internally. As a MIDI export the only way it can interpret that ramp is with a series of tempo changes, which explains John’s screenshots. Thus, there will be a very rough resolution to your tempo changes, and you will hear it in your drum parts. If you want to smooth it you, you will have to do some work in SD3’s tempo map, by recreating the ramp manually if you want your tempo change in SD3 to be just as smooth. At least your ramp appears to be linear. You would have a harder time if you had used a more logarithmic ramp in Logic.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• This post was modified 5 years, 2 months ago by Bear-Faced Cow.

[Bear-Faced Cow]

What do you mean by “it gets off”? Is it not decelerating?

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

What you are exporting your MIDI with? As well, does your tempo map in SD3 show any changes? You may not have imported your tempo into SD3’s tempo map if not.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

Just for shitz an gigglez, I decided to try to bog down the resources to make things tougher on CoreAudio on my dev MacBook Pro, including a couple of active JVM processes (they have proven in the past to be the worst enemy to CoreAudio). Your MIDI file is running like a clock at 160BPM without issue. I could take it further by clearing the Spotlight cache, triggering a swarm of mdworker daemons if we want.

However, there’s nothing proving to be “math-y” within SD3 with this. It’s holding its own.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• The post has been modified 2 times, last modified 5 years, 2 months ago by Bear-Faced Cow.

[Bear-Faced Cow]

And I code at a more systems and automations level. What’s your point? This could be something as elusive as a race condition competing for resources at just the right time. Hence the 160bpm, considering my “theory” was based on recent observations on an automated testing framework that I was troubleshooting recently.

If by your theory that something is “math-y” with the software alone, then why wouldn’t it be universal considering that this particular part of the code base would be common considering that we’re both Intel processors? Not to mention that it would be easier to exacerbate on the Mac due to how CoreAudio operates. Sorry, but there’s not enough there to scream bug without doing a further deep dive to prove it in this case.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

Difference in class could have little to do with this. It could all depend on what was installed on both machines. There could very well be something under the hood stealing resources. I’ve seen enough of that in my years both as a software developer and as someone who’s set up plenty of audio production systems. Audio is especially taxing on computer resources, and can get knocked off kilter by certain processes. I’ve killed a lot of daemons to keep my audio Mac running smoothly.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• This post was modified 5 years, 2 months ago by Bear-Faced Cow.

[Bear-Faced Cow]

You would create a multi-output instrument in your DAW and route your kit pieces to those outputs. From there, you can apply EZMix to them.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

You would have to apply EZMix within your DAW.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

MacBook Air is good for online surfing and more light computational work. You might find yourself encountering various issues including audio dropout. You’re better off with an adequate MacBook Pro with a competent audio interface, especially if you plan to use it live.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

1

Thanked by: tgfoyl1472_1

[Bear-Faced Cow]

Although, I’m running on a Mac with Mojave 10.14.6 (tested both in standalone and in Logic), I find it difficult to believe it has any relativity. Could be something something stealing your CPU resources at a more “coincidental” moment.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

Been playing the MIDI file in a loop for the last five minutes (it’s now like the Japanese water torture)… unable to recreate the issue here.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

Hardly true… 3.1.7 was released not all that long ago with considerable functional bug fixes. This is a cosmetic bug with a workaround. That’s considered a low priority compared to functional bugs without a workaround.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• This post was modified 5 years, 2 months ago by Bear-Faced Cow.

[Bear-Faced Cow]

All you really need to do is change the drum map in the midi in/e-drum settings to the logic drum designer map. You can then control SD3 with drummer and import a drummer region.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• The post has been modified 2 times, last modified 5 years, 2 months ago by Bear-Faced Cow.

[Author]

Replies