Bear-Faced Cow
Participant
Topics Started: 30
Replies Created: 2930
Has Thanked: 252
Been Thanked: 1038
Bear-Faced CowWhat 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
Bear-Faced CowJust 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
Bear-Faced CowAnd 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
Bear-Faced CowDifference 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
Bear-Faced CowYou 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
Bear-Faced CowMacBook 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
1
Thanked by: tgfoyl1472_1Bear-Faced CowAlthough, 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
Bear-Faced CowBeen 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
Bear-Faced CowHardly 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
Bear-Faced CowAll 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
Bear-Faced CowFun song to listen to. The opening reminded me of some old Men Without Hats tunes.
Cute song. Missing the ultraviolet light bath with Clorox injections though. 😀
jord
Bear-Faced CowVery nice song. Only things I found was that the vocals seem to get buried withn the music. I also felt the music was a little sibilant. Otherwise, I liked listening to it.
jord
Bear-Faced CowTT have already said there’s a bug in the Product Manager. You should be fine… I have NY Vol. 2 as well.
jord
No products in the cart.
