ElMojoWe already have it! Why do I need a damn logo to remind me. Tell your marketing people to F*** O** and fix the crap they have caused. You have once again broken a working product because of madness. Every time I load my stuff the drums don’t work until I go into SD3. Are you actually adults!
We already have it! Why do I need a damn logo to remind me. Tell your marketing people to F*** O** and fix the crap they have caused. You have once again broken a working product because of madness. Every time I load my stuff the drums don’t work until I go into SD3. Are you actually adults!
Mark KingI have a m.2 drive for all my samples. I use huge kits but they load in seconds. Audio is still on spinning disks. I’m not having problems. I was saying mine loads really quick and the splash screen is gone in less than a second. I have a i9 computer with win 11 running Cubase 11 (still waiting for upgrade discount )
SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors
Bear-Faced CowI gather you have no groove packs? I’d almost assume you don’t, or at least do not have as many as many of us do, being an eDrummer (yeah, I know what they say about assuming). That is where I noticed a bulk of the loading is happening during the splash screen. Wouldn’t be surprised if it had something to do with that MIDI display column in the grooves tab.
jord
patrick maguireDamn jord , you really are a disagreeable fellow.
how can anything not be possibly system specific?
No need to reply to that because I don’t care anymore what you think.
Mac Studio
patrick maguireJord believes that some people are just “bad” people and that’s why the splash screen takes longer on some systems.
Dear lord dude. What is your problem? Are you an adult ?
Mac Studio
ElMojoI started this thread when I thought the developers had caused a major transport problem because of aesthetics. I am still not 100% sure that that isn’t true. As it took them so long to fix what would appear to be a very easy fix. They have now fixed the transport problem. It seems that it only affected Steinburg DAW systems, which I use. So the argument about that is now ended. However the question of workflow is still alive. The latest version 3.3.3 on my system is now working perfectly. The splash screen goes away quicker than it did in the previous version for sure. That is with no change to the first source material I used on 3.3.2. It matters not how fast your system is, as the splash screen will use a timer. This timer is programmed by the development team and is independent of the speed of your processor/s. So it is based on real time as we know it. Not the time that a processor executes instructions. In terms of work flow the longer it takes for you to look at settings as the plugin loads is measurable. Looking at a logo instead of the SD3 mixer causes a stall in that work flow. I find myself waiting for the logo to go away before I can make a decision about what to change. This is not good when I am darting about and making small changes to a mix. I know that I am using Toontrack stuff. I am not that dumb that I don’t realise that. Yes it does affect work flow and because of that it becomes a Nag Screen. Which is used to spoil work flow. This is the technique used by hackers to force payment. It is wrong and should be removed.
patrick maguireYes. Exactly !!! The work flow issues is one that many will never understand.
This IS a flaw ! There is no way to get around the fact that as a heavy SD3 user thinks IT SUCKS. Its not the biggest issue in the world. Its not like the software is crashing or playing the wrong files.
The reason it’s become such a big deal is the selfish pushback by some that insist it doesn’t exist. Or it’s a newbie issue. Remember ,that it worked Perfectly!!!!! Moments before the update. Its just plain and simple a crappy design that only effects FAST PROFFESSIONALS.
Ive been down this road many times with various pro tools and other audio “features “ and or bugs.
Some people simply will not understand how bad the design screws up work flow. Its the type of issue that programmers will never understand until they are running a session with 5 instances of SD3 and clients in the room and deadlines. And a mix that is almost done. Its so hard to convince slow deliberate users how important work flow is!!!!
For example. The fact I have to select my operating system and version number for a post in this forum EVERY TIME I log in is a clear lazy bad web forum design. But some will say “it’s fine” doesn’t bother me.
Mac Studio
Yes. Exactly !!! The work flow issues is one that many will never understand.
This IS a flaw ! There is no way to get around the fact that as a heavy SD3 user thinks IT SUCKS. Its not the biggest issue in the world. Its not like the software is crashing or playing the wrong files.
The reason it’s become such a big deal is the selfish pushback by some that insist it doesn’t exist. Or it’s a newbie issue. Remember ,that it worked Perfectly!!!!! Moments before the update. Its just plain and simple a crappy design that only effects FAST PROFFESSIONALS.
Ive been down this road many times with various pro tools and other audio “features “ and or bugs.
Some people simply will not understand how bad the design screws up work flow. Its the type of issue that programmers will never understand until they are running a session with 5 instances of SD3 and clients in the room and deadlines. And a mix that is almost done. Its so hard to convince slow deliberate users how important work flow is!!!!
For example. The fact I have to select my operating system and version number for a post in this forum EVERY TIME I log in is a clear lazy bad web forum design. But some will say “it’s fine” doesn’t bother me.
Mac Studio
Mark KingCorrect I have no groove packs except what comes with sd3 and the expansions. I’ve never used any of them as I always play my own grooves. Slipped off topic a bit now. I probably don’t have anything to add to this conversation as the splash is so short for me I don’t even have time to think about it.
SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors
ElMojoThat highlights the problem exactly. People use SD3 in different ways. I use grove tracks too and modify them. So issues will be more annoying in the way some people use the software. This is called workflow. So the workflow on grove tracks is now screwed. Drummers who are using MIDI kits have a different workflow to me. If Toontrack is abandoning grove tracks and going over to MIDI drummers only tell us. So I can stop wasting money on grove tracks, and find a new way of working with a different drum plugin . It is that simple. There is no point in trying to sell MIDI groves and then screw the workflow………..
Bear-Faced CowDamn jord , you really are a disagreeable fellow.
how can anything not be possibly system specific?
No need to reply to that because I don’t care anymore what you think.
Oh, but I will reply and I promise you that I will have a lot of fun and enjoyment doing so, especially at your expense. The part that will give me a lot of joy will be ripping your responses apart one by one. What I won’t enjoy is involving @EIMojo in my response because I have respect for him. You, not so much. So without further adieu, let the fun begin…
Damn jord , you really are a disagreeable fellow
No, you’re just wrong in your answers and are just way too arrogant to see that. Wake up! It’s okay to be wrong. It’s how you learn.
how can anything not be possibly system specific?
For the simple reason that if it was system specific, then I would have far greater problems than you since my computer is slower. You are so stuck in the fact that you have a blazing fast computer. However, the problem is not with the computer. Have you heard of PEBKAC? Look it up. That is you! It’s not your computer but how you have it set up as a DAW. How your data is distributed among your drives will not only create the type of problems that you are experiencing, but can also result in CoreAudio Overload errors. Do you even have enough drives to handle proper audio production? All in all, this is not the computers problem, especially in your case since you have a computer that is far able to handle your audio processing needs. Once again, wake up and perhaps realize when people are trying to help you, rather than walk around with your head up your arse believing you are always right and anything I am saying is disagreeing with you. Man, it’s a wonder you’ve really made it this far. Seriously!!
Jord believes that some people are just “bad” people and that’s why the splash screen takes longer on some systems.
No, Jord believes that in order to solve a problem, one must get to the heart of the matter. There was obviously a reason that the splash screen takes longer. It is Patrick that is walking around offended and butt-hurt because he can’t handle being wrong from time to time. You know, in Canada, our healthcare system covers problems like that.
Dear lord dude. What is your problem? Are you an adult ?
Perhaps look in the mirror and ask yourself that. But that might require a colonoscopy, which is also covered here, in order to give the doctors an idea of what’s holding your head in there so that they can possibly free it so that you can take a good look in the mirror.
This timer is programmed by the development team and is independent of the speed of your processor/s. So it is based on real time as we know it. Not the time that a processor executes instructions. In terms of work flow the longer it takes for you to look at settings as the plugin loads is measurable.
That is not by definition a timer. Timers are constant. Perhaps you are confusing it with a loop, and if it were the case then would it not stand to reason that my computer would take longer? Mark and I have managed to determine that this is a combination of data loading and hard drive bandwidth bottleneck issue as the controllers are trying to handle the number of files being loaded, which instead of bellyaching like Patrick, we can actually assist Toontrack in solving this issue.
I am not that dumb that I don’t realise that. Yes it does affect work flow and because of that it becomes a Nag Screen. Which is used to spoil work flow. This is the technique used by hackers to force payment. It is wrong and should be removed.
Seriously, almost every piece of software I own has a splash screen while it is setting up (Logic Pro, Final Cut Pro, Reason, Maschine, all Affinity graphic products… ad nauseum). And if you want to talk firmware, my Line 6 Helix has a splash screen while it is booting (and it takes longer than SD3). Even the little screens on my PowerCab units. You’ll have a better argument in helping TT optimize their splash screen than to get it removed. In light of every other software developer, you’ll have a harder time trying to do the latter. Would you not agree?
Its just plain and simple a crappy design that only effects FAST PROFFESSIONALS.
Ironic how you can call yourself a professional and yet act worse than the hobbyists on the forums in the same breath. There’s a reason it was implemented. Perhaps instead of being part of the problem, you should be a professional and be part of the solution. It’s not going to go away and your bitching and complaining won’t make it go away either.
Some people simply will not understand how bad the design screws up work flow. Its the type of issue that programmers will never understand until they are running a session with 5 instances of SD3 and clients in the room and deadlines. And a mix that is almost done. Its so hard to convince slow deliberate users how important work flow is!!!!
Name one person who doesn’t understand! And being a professional programmer as well as a professional audio engineer, do you think I don’t understand? Oh wait, you’re not reading my response since your head is lodged in tight. Sorry, my bad.
For example. The fact I have to select my operating system and version number for a post in this forum EVERY TIME I log in is a clear lazy bad web forum design. But some will say “it’s fine” doesn’t bother me.
I have never seen such a beautiful straw man argument. Good work, scarecrow! The wizard has just what you are asking for.
People use SD3 in different ways. I use grove tracks too and modify them. So issues will be more annoying in the way some people use the software. This is called workflow. So the workflow on grove tracks is now screwed. Drummers who are using MIDI kits have a different workflow to me. If Toontrack is abandoning grove tracks and going over to MIDI drummers only tell us. So I can stop wasting money on grove tracks, and find a new way of working with a different drum plugin . It is that simple. There is no point in trying to sell MIDI groves and then screw the workflow………..
Or perhaps, we could use our skills to help TT. The devs are only human like us (as well they are musicians too) and probably don’t mind when others help point out certain tech issues. Too bad people like you and I are not part of their beta-testers, since it’s times like this, they could use some outside eyes, especially from those of us in both fields. I highly doubt they intended to screw us groove pack users, especially when they have been putting out some really great packs that would save me many days of drum programming. I believe we know where the problem now lies and it is fixable (addressing data traffic issues have been my specialty).
jord
patrick maguireJord. I’m sorry. I understand now.
I went to your website. Its all clear now.
“christian blues rock “.
have a wonderful day.
Mac Studio
Bear-Faced CowWell look at that… you actually did notice I responded. It’s people like you that make our day wonderful.
Perhaps, people like you need to familiarize yourself with such verses as Matthew 21:12, which is not to be confused with Rush 2112, to really understand like you “say”. Otherwise, your veiled and feeble trollish attempt was nothing more than mere entertainment and speaks more of you than it does of me. Perhaps, think before typing next time.
You’re not as professional as you’ve deluded yourself into believing and your posts serve as proof.
jord
ElMojoI still hate the nag screen. Remove it! Why!
drumjack52I still hate the nag screen. Remove it! Why!
Superior Drummer 3 version: 3.3.3
Operating system: Windows 11
Give it up and deal with it. The rest of us have. I don’t like it either but I don’t waste time even thinking about it any more.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
Mark KingI really don’t care. It is so trivial and not worth going on about. It’s not exactly a bug.
SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors
No products in the cart.
