Jump to content

TTOZ

Member
  • Posts

    102
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TTOZ's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Have you worked out which particular device is giving you issues? for example, if you launch logic with no midi connected, then add one by one to see which it is?
  2. hmmm.. had no issues with high sierra here.. it was the korg driver that broke logic for me on both my imac and macbook. Apple are terrible for bugs, agreed.. I might even say they are the worst of the worst in that regard.. I don't even know anymore why I am not using windows since my main DAW is pro tools these days. I guess that off the shelf and uber quiet appeal of their desktops is too strong and keeps sucking me in. As well as everything thunderbolt just working.
  3. it's called standardised testing. That's why. I am not even going to explain further than that as you simply don't seem to understand nor want to. I said it was divine mode and made an error, I corrected it. Big deal. You obviously don't want to give your results when testing the same way everyone at gearslutz tested, cause you maybe can not even get one, and want to pretend your cheese grater is more powerful than a 2019 mac pro. I CLEARLY updated the instructions in the original post, as well as subsequent posts, but you are fighting with me about my own test. Once again for the LAST TIME: Audio track must be highlighted, no changes made to diva whatsoever. The project must be played as is, with the only changes allowed being to duplicate or delete tracks as necessary till you get a figure you can reliably play for a minute without the overload message. I don't know how much simpler I can make it than that. Any other result is invalid in THIS test as THAT'S how the mac pro users tested. One guy made a mistake of having a diva track selected, and got 30 on his 16 core mac pro., but there were pops and clicks cause logic's low buffer was activated which doesn't give the core audio overload message. This was therefore an invalid result. When he highlighted the audio track, which means logic will overload before there is EVER any audio fidelity loss, he got 6. That's the valid result IN THIS TEST. If you want to turn on multicore, feel free to do so and report the difference. But the multicore result is NOT valid to compare to the results recorded so far since the test started. If you don't want to test like everyone else thus far to get an actual comparative result, stop wasting my time. This is the last time I post about it to you.
  4. For example, someone claimed his mac pro 16 core got 30 of them but he had one of the divas highlighted, which put logic into "no overload but will click and pop" mode. When run correctly, the result was 6. If you want to put it in multicore mode you can, as long as you first include your "DIVA SETTINGS AS IS WHEN PROJECT LOADS" result. I have updated the initial post with the link and made the terms and conditions clear, to accurately match the results against all those who have tested with their iMac pros and mac pros at gearslutz. Cheers.
  5. yes, it's great quality mode with multicore disabled. That's not your result then. I forgot about that, the other test was made with divine mode later, an updated test for more powerful computers. I sent you the exact test that a 16 core mac pro can get 6 on.. and you HAVE to have the audio track highlighted otherwise logic will just add clicks and pops if ANY of the diva tracks are highlighted when you play back, as those tracks go on low buffer mode which prevents logic from stopping with an overload message. Your maximum tracks with the audio track highlighted, logic playing back for at least 30 seconds looping without an overload message, and diva multicore disabled is the result. How can we compare when you are using a different parameter? The highlighted track I am not sure about, only you can confirm you highlight the audio track on playback, as it is when the project loads. Your result is the result with the test loaded AS IS. I do not believe your 5.1 has better performance with Diva than a new mac pro. I do not buy it for a second, I am sorry but I don't. Your computer has a 2700 geekbench 4 single core vs around 5300 in the new one. because you have so many cores, you are able to get away with it by enabling multi processing.. I don't think your machine could even play back two with multi processing disabled. You gave me the result I didn't ask for LOL! If you are telling me yours can play 9, with the audio track highlighted, and multicore disabled, that means your cheese grater is WAY more powerful than the new 16 core 3.2ghz mac pro for certain VI tasks, and that is 20 grand in Australia for a decent config! If so this needs to be put on VIDEO ASAP so we can send it apple, so they can SORT THIS OUT with an EFI update.. Evidence would be much appreciate to show apple how much the NMP is underperforming with some VI's.
  6. Name your instances! LOL! https://drive.google.com/file/d/15rteHzMTxPFPgyvLqtYjn5mmDMyLCJEB/view?usp=sharing Cheers! EDIT.. this has been edited for only one DIVA CPU test project link. If you need more DIVAS, duplicate the last track and copy the midi clip as much as you need, and your final instance count is only valid with the *audio* track highlighted, so logic is putting all the Divas on the playback buffer. Playback must be stable for MINIMUM 30 seconds looping, at the default Diva settings the project loads at, WITH only the single audio track that is present being selected. Your playback buffer must not be LARGE, as all the the others were tested at MEDIUM. To get an accurate comparison score, all testers must follow the same rules.
  7. Different thing in that Legend is specifically a moog emulation in int hat one regard, it's better than Diva. overall Diva is much more a jack of all trades type analog, with higher polyphony and can emulate multiple machines.. so... yeah of course it's better. I'll be right back with the logic test project, the one that allows my 8 core IMAC pro and the 16 core max pro to only get 6 instances of diva. (15 instances on the MacBook pro 16" 8 core) If you can get more, you'll need to duplicate. If you can't play the 6, just delete till you can.
  8. You do realise this diva test where people get 6, is on divine mode and playing back 8 voices all at once (enough notes in the midi file to make the voice steal so we know we are using all 8). Let me see if you can get even ONE on this max quality test.. do you want me to link you the logic project file with the Diva test? You have to compare apples to apples (no pun intended).. a NMP can do 100+ divas if it's on draft mode and not playing 8 voices all at a time per instance.
  9. DP's pre gen is a joke.. I am getting 71 synths in a test I designed, playing in Logic vs 50 in DP 10 of the same midi file and synth, and i waited half hour too in case pre gen wasn't finished rendering. A PROPER pre gen would be good, yes.. where it constantly transforms to audio in the background and updates when you make changes.. disables the VSTi unless you click on the gui to edit it, and so on.. That would mean the DAW is basically playing audio back at all times and you should get 100's of tracks better performance. Reaper's pre anticipative processing also SUCKS. It is good for performance (Logic still pips it) and comes in second amongst all OS X daws for performance, but it adds that 200ms latency every time you move the playhead during playback and so on. It feels sluggish and awful. No thanks.. It also uses WAY more real cpu than the others (you can check on this, it's a known thing) which means heat and noise. Reaper uses 95% real cpu to play back the same amount of VI tracks Logic uses 80% for, as one example. Anyway the infrastructure for pre gen is already there in many DAWs with freeze.. they just need to make it automated so to speak. Whatever MOTU have done, they have not done it well.
  10. Something is seriously wrong there then.. you are duplicating the settings and diva is in the same quality mode, playing the same patch with the same midi file, and your 2010 mac pro gets more? I find that impossible and need to see it on video with my own eyes.. I am not saying you are being untruthful, not at all,. but I think there is something different you may have missed because it doesn't make any kind of sense. The 2019 mac pro does not sustain it's correct max all core turbo under load, but it's single core is at least 40% better than the 2010 3.33 and 3.46 models. In fact it's basically almost double the performance, clock for clock.
  11. BTW, the best way to work with Diva and Massive X right now, it to play and record them and instantly freeze each instance as you go along. Even if you had the 28 core mac pro and spent 50 grand maxing it out LOL. If Logic had something like S1's track transform, there'd be zero issue to ever have to keep all divas running in realtime.. Track transform allows editing when frozen and then if you unfreeze it, places midi where you have copied and edited audio.. S1 has terrible realtime performance on mac, but this one feature is particularly ingenious. Need to tweak the synth itself? Transform to midi, tweak, then right click transform to audio again. You can always see both midi and audio data when transformed as it displays both in the one clip.
  12. Nothing to do with Catalina.. I have replicated all of those issues on my iMac pro in High Sierra and Mojave. Apple is not allowing the Xeons to hit their rated speeds under load (they DO in windows on the very same mac).. it has been proven now on video with the new mac pros.. windows is allowed higher watts draw and better single core performance.. when I said at gearslutz it was a power limit issue everyone basically called me crazy but it turns out I was right. This affects iMac pro and mac pro computers. when you see 32 logical cores in Logic's meter for a 16 core mac (for example), it's not that simple to just think they all have even performance. There is overhead with each new one used. Massive can basically *just* be played on the new mac pro, using whatever patch you are using. One instance is using an entire core, right? Then when you duplicate it, each one adds a bit of processing overhead to the previous "thread" and it tips over. If the mac pro was sitting at 4ghz all the time for the 16 core, which is the all core turbo it should be hitting, this would not happen, as there'd be enough headroom to duplicate. This is why the MacBook pro kills the mac pro in Massive X and Diva, cause it's single core performance is better.. It really is that simple. I am in Catalina on the macbook pro and it is destroying my Mojave iMac pro with these synths. However, in stuff that is well optimised, the iMac pro kills it.. The logic score is 155 iMac pro vs 99 MacBook pro 16" for example. This is why DAW builders, in any case, say single core speed matters. The best mac for DAW overall, if you use heavy algorithmic VIs (as in not samplers first and foremost but VA's and the like) is currently the 9900K iMac. If apple improve the cooling and put in the imminent 10900K, that will be the one to get. All of this said.. it is kind of ridiculous though.. that native instruments and u-he expect everyone to have super computers to play 8 voices of their synth. Just say no, and use alternatives.. Listen to the legend, for example.. 8 voices uses about 1/12th the cpu that 8 voices of diva does, and it sounds wonderful. I can get like 71 of them on my iMac pro vs 6 Divas (same issue as the mac pro). In bootcamp, the core speed fluctuation problems are removed, and I get 12, but the all core turbo speed of my iMac pro is 3.93 ghz and it's still not enough to quite put one instance on every core like the MacBook pro can. The ultimate thing as VI users, that WE want, is something like 16 cores at 4.5ghz.. when that sort of solution (without overclocking) comes out, we'll be laughing, as it will be the jack of all trades. What Apple needs to do is stop this nonsense on the iMac pro and mac pro of dropping from 4ghz to 3.2 out of nowhere (for example) when the cpu is at like 45 degrees and there are no thermal issues. They COULD fix this 100% with an EFI update. PS if you used CPU setter to disable hyper threading, you'd probably get more consistent performance per core, and might even get 15 Massive X (logic always leaves a core free in case you arm a track to record). overall you'd lose a lot of performance but for really hungry VI's it might be better. I am going to try it on my iMac pro myself after lunch.
  13. none of mine show up either. it's not that Diva can't take advantage of xeons, it's just a very CPU demanding plugin... Omnisphere is (fwiw) a rompler with a decent synth engine nowhere near the quality and demand of diva, Dune 3 is a WT synth. The only comparable synth from all you listed is The Legend - but it has one model, Diva has 5 - and while The Legend is GREAT, i think diva still sounds better. I can use Diva just fine on my 2018 Mini or my 2018 13" Bleh.. read the post properly before defining it so simply.. If Diva used AVX 512, it would take advantage of xeons. .That's what that part meant. Maybe i worded that one line wrong, but the mac pro can't sustain clock speeds fast enough to use a lot of Diva, i.e single core performance, which was pretty clear in the rest of my post. Diva sounds great but is not worth the cost, I have tons of alternatives that WILL work properly on the mac pro. The point of my post was to tell that fellow who loos u-he stuff, not to worry that he can't afford a new mac pro, as it runs u-he stuff crap anyway.
  14. Just keep reporting to apple.. this is quite serious and must be addressed. I did, even though i uninstalled korg drivers.. it really sounds like a mojave issue also. If their response is to upgrade to Catalina.. imagine doing that and it doesn't fix it.. but.. at least send a bug report!
  15. don't feel bad! The new 16 core Mac pro is crippled with 6 instances of U-HE Diva playing 8 voices each.. too much for single core load so it can only load 6 and leave all the other cores free.. it's the single core performance that is at fault here.. My iMac pro gets 6 also, yet my MacBook pro gets 15.. yes an 8 core MacBook pro gets 15 x 8 voice divas all playing back without logic overloads, vs 6 in a mac pro configured to about 14 grand.. There's a large topic at gearslutz explaining it all (the last 5 or so pages are the ones to read about this from memory), but basically OS X is not allowing the Xeons to keep a steady all core turbo speed and drops below Intel's actual rated speeds, whereas Windows is letting them perform at their maximum. For example in my iMac pro, i get 12 divas in Pro tools/bootcamp vs 6 in Pro tools/Mojave. It's a power limit issue in OSX and we all hope it gets worked out. The reason the MacBook pro gets one per available thread in Logic is because there is enough headroom left over after each one, to put the next one on.. With the mac pro's, the reason they can only play 5 or 6 is because even though those first few instances can be loaded on one core each, every new instance adds overhead even to previous cores, just slightly, but there is no headroom left in the single core performance so it flakes out much quicker. The 9900K gets like 20 or something. Yet, with omnisphere, there is a demo of the new mac pro playing 80 of them and all 16 cores/32 logical cores getting hammered to the max. So really, it's only U-HE synths that seem to not be able to be fully taken advantage of on the Xeons.. I have other heavy cpu synths and I can use them all.. just not Diva. All the Arturia stuff is fine, Dune 3, the legend which sounds *amazeballs* used about 1/5th the cpu of DIva's moog filter mode. Try the legend, you will love it.. Only 8 voices but he used an AVX trick to get it to perform like other synths with one voice! Just one disclaimer, I only use the demo of Diva, I sold my purchased copy yonks ago and never re bought it, but I doubt he would cripple the demo with higher cpu load.
×
×
  • Create New...