Jump to content

Matthew Sorrels

Members
  • Posts

    1,503
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Matthew Sorrels

  1. While APD Shop pricing can vary a bit, as a rule when deals end they only sometimes move to the shop and when they do the lowest price (using shop credit) is equal to or higher than the deal. Nothing I've seen that has moved over has offered a better deal. You can't game the system with the shop. And most deals don't move over at all. I also suspect Sugar Bytes won't move over to the shop at all, they don't have anything in the shop already. Considering they sell through multiple retailers having an on-going deal at the APD shop would seem very unlikely. Retailers don't like selling products one of their competitors has a on-going better deal on. Developers try hard to not burn their retail channel.
  2. I'm only missing Masala 2. I wonder if you wait to redeem if you could hold onto this until new releases show up?
  3. Cubase's 30th Anniversary sale (which included updates) was Mid-May last year and ran for 2 weeks. So I'd suspect the next sale will be sometime around then.
  4. Plugins hosting plugins are always going to be big piles of problems. Might have better luck sending Obscurium's MIDI output to the instrument in your DAW rather than trying to host another plugin inside it.
  5. Cubase 10.5.10 Available February 3, 2020 The Cubase 10.5.10 maintenance update resolves a macOS performance issue that many users encountered, plus also including more than 35 enhancements that will make life easier. We recommend especially our customers on Mac computers to install this update for Cubase 10.5. https://www.steinberg.net/en/support/downloads/cubase_105.html Note the Windows download link for the 10.5.0 to 10.5.10 update on this page appears to download a 1.3 gig file (very slowly). If you use the Steinberg Download manager you can get the much smaller 10.5.0 to 10.5.10 update. I think they have some links wrong on that page. Use the Download Manager to avoid these problems. Has a large list of fixes: http://download.steinberg.net/downloads_software/Cubase_10.5/10.5.10/Cubase_10.5.10_Version_History.pdf
  6. Most of it's sales are around $69 Black Friday)/59 Euro. A few times it goes on sale for $79. This was low enough I decided to grab it. Though I really should just buy the bundle upgrade in my account and be done with it. Not really sure how useful it is though. That FM synth sound is a bit limiting. And it's UI is so strange I'm not really sure how to use it at all. Which on the Sugar Bytes scale means it's pretty awesome. 🙂
  7. I don't think I've ever seen anything to fix NI install issues on the Mac. And I'm pretty sure there are issues. 😞
  8. https://support.native-instruments.com/hc/en-us/articles/360001024029-License-Transfer-Why-Is-My-Product-Not-Transferable- Your product has been registered during the last 60 days For technical reasons, serial numbers are automatically excluded from license transfer for 60 days after registration. In case you wish to resell the product before the 60 days transfer block, please contact our support team. If you wish to do so, you can include the NI username and email address of the new owner, so that we can transfer the serial numbers directly to the new account.
  9. Usually this is because the file path is too long. It looks like you are installing it into D:\Synth Samples\Komplete 9\Session Horns\ Which seems like a really bad directory to install the Mosaic Voices library (inside another library). Native Access also does this crazy thing where it downloads an ISO file and then mounts it as a drive and runs the installer from there. That causes all sorts of crazy things to happen since Windows "loves" to autoplay CD/DVD drives which is what this looks like. I had to turn off some options in some ISO mounting and backup software I run so that it wouldn't try and fight with Native Access when it did the drive mount. I can't remember all the hoops I ended up going through to sort that out. One thing that you might also have to deal with is Kontakt 6.2.1 has some problem with doing a batch resave. Can crash and/or corrupt a library. They claim they are fixing it in a 6.2.2 release that hasn't happened yet. It's messed up at least one or two libraries on me now. As a result I only batch resave things I have the zip/install files for (or I make a backup) just in case the batch resave goes bad. Though in this case I think you just need to configure the install directory for Mosaic Voices to be a much, much shorter path. Once it's downloaded you can move it then use Native Access to point to the new location. I think it's just the install/download part that cares about the path length.
  10. Yes, load balancing on or off didn't make any difference. My Kontakt is configured to use threads through, which may be a factor. With only one instrument loaded though I'm not sure how much actual threading Kontakt is doing. And of course this box has a crazy number of cores and threads (it's an Intel i9-9960X). I'm not sure it's worth spending time on at this point. Could easily just be my problem entirely, I'd wait for a lot more feedback before wasting any time on it. I was just surprised because the Early Access version seemed to work just fine, but I'll admit I didn't actually do exactly this. May have been there all along and really just be a Kontakt only thing.
  11. Did a few tests and the click/pop is definitely ThreadSchedulingModel=3 I had turned it on during Early Access and it seemed better (lower CPU) which is why I was using it. I can't really verify this problem with Kontakt wasn't happening with the early access build though. Good news is ThreadSchedulingModel=2 or ThreadSchedulingModel=1 both seem fine.
  12. I updated this morning from the Early Access version, which was working fine. But with this new final release I was hearing a single click/pop when playing a single Kontakt instrument (the horns in Spitfire's Bernard Herrmann Toolkit) once in awhile. I hadn't noticed this before. I assumed it was something to do with my ASIO buffer/sound card/etc. But everything checked out just fine. I run synth projects at 2048 samples just because it solves lots of problems and that was still set. This basic Cakewalk Kontakt template does have a few plugins but the clicking wouldn't stop even when bypassing FX. It wasn't continuous. You had to play a few chords and usually it would click on a chord release/chord change. Not something I could just reproduce 100% but could get it to happen in a few seconds of playing. The new popup CPU status showed no late buffers and the load was always very, very low (under 10%). So I tried the same things in Cubase Pro 10.5 and it played just fine, I couldn't get the click there at all. So back in Cakewalk I deleted my AUD.INI file and and had it make a new one. This new one I couldn't reproduce the click. The only difference between the two is ThreadSchedulingModel=3 (the clean start version has this as 1) EnablePluginLoadBalancing=1 (vs 0) ProfiledWASAPI=1 (vs 0) I had turned on the ThreadSchedulingModel 3 during the early access, and it seemed fine. (I don't think the plugin load balancing and profiled WASAPI have anything to do with this.) I don't have much more time today to try testing a bunch of combinations, but I do think there is something wrong with TSM 3 in this final release 2020.01 build 24
  13. It may have to do with how many audio effects you have. I seem to remember they changed this, but it was a long, long (years) ago. Because the popup menu didn't work very well with 1000+ plugins. I haven't seen pull off arrows for audio effects for a long time.
  14. Lately I've been using the brass in Metropolis Ark 1-4 (mix and match for "epic") and Cinesamples 90's Retro Trumpets. But to be honest neither are making me happy. I've also been using NI's Symphony Brass (the full version, both solo and ensemble). Truth is when I want a generic all purpose brass I'm usually ending up there and later I swap it out. Forzo is definitely in the mix too. It does some things really well (the designer is very cool). The new Junkie XL Brass looks very interesting (you can listen to individual parts in the SINE player) but the pricing is way off for me. I listened and gave a punt on the new 8DIO Century Brass. It's price isn't bad though, but it doesn't seem like they fixed all the issues the first release had. I may regret this call at some point though, but 8DIO will have another sale sooner or later. I've tried very hard to work with Spitfire's BBCSO and it's brass. I had hoped it would become my standard orchestra. But the player and it's headaches have pretty much driven it out. If it were a Kontakt library I might say it's a good brass answer. It does have the sound/instrumentation/articulations I want. I don't regret getting Forzo (or Novo) I just wish Forzo had a bit more. Lack of solo instruments is also another factor. While I have all the Albions I don't think I used the brass in any of them. I suspect with brass you may just have to settle for a lot of mix-and-match.
  15. You might need to be specific on what doesn't work properly. Guitar Pro 7.5 has decent MIDI export (in earlier versions the MIDI export were pretty bad for guitar parts), but you will always have to deal with conversion issues (as well as filtering out any of the crazy MIDI control messages as @scook points out). What it thinks is a kick drum or a snare (the note number) and what the software (or hardware) synth you are trying to use that file on can be vastly different. I don't think Guitar Pro uses "perfect" GM MIDI drum mappings. And even if it did, your synth might not.
  16. Forzo's lack of legato kind of kills it for me. When I first got it I don't think I cared so much. But over time it has pushed it further down my goto brass list.
  17. Yes. A rompler is a sampler with a fixed set of sounds (used to be stored in ROM, read-only-memory) hence the name. Early versions of Sampletank actually allowed a user to make their own instruments, but that was dropped a while back. Which changed it more into a classic sound module/rompler. It's not exactly a term of endearment. By and large early sound modules for keyboard workstations had pretty weak sound libraries. They would take one sample and stretch it across the whole keyboard by pitch shifting it and that would be the flute or sax instrument for example. They did this because the storage space on the ROMs was very limited. Sampletank's very early libraries were often of that class. It's not so true for Sampletank 4 though, the sample library included with it is a bit more complicated (which is why the download is now so large). Even still, many Sampletank instruments still only have a small number of samples for an instrument, instead of many samples at every pitch and velocity. And the playback engine is fairly limited, unlike things like Kontakt and UVI which can have scripts that determine when and how to play back a sample. How a software instrument is made -- the samples, how they were recorded, how they are played back are really important for how well any specific instrument works. One problem with rompler class instruments is they tend to focus more on breath and quantity of instruments, rather than quality.
  18. OP is using Sampletank 3, not 4. it's VST3 version was never very stable.
  19. The modules I think are just Synthedit things. The "engine" was more a hand/manual conversion of Synthedit into a full C++ plugin. Maybe. Not sure it really matters, with Synthedit I prefer a total quarantine. It's the only way to be sure.
  20. I found a demo version of some of their stuff on vst4free.com Looking at the binary it claims to be using something called the CK Engine Which I'm guessing is this: https://www.kvraudio.com/forum/viewtopic.php?t=460229&start=45 So not Synthedit anymore. I'd still avoid though.
  21. This old review of Blue Grand by the same guys on KvR says it's Synthedit https://www.kvraudio.com/product/blue-grand-by-sound-magic Not sure what this is, but it sure looks like Synth Edit.
  22. Nothing to go on in the crash dump. The thread that crashes is all Cakewalk (so only someone at Cakewalk could tell what it was doing). It does look like your using behringer_xuf_1394_asio_x64.dll for an Audio driver. I'm guessing this is the Firewire version of Behringer's XUF?. Not sure how well a driver last updated in 2013 using a Firewire is going to work in modern Win 10. Your Win 10 is behind, crash dump says you are running 10.0.18362 which is the May 2019 build of Windows. There is a newer version 1909, November 2019 release. But honestly there really isn't anything in the crash dump to help narrow it down. A Cakewalk developer with the PDB symbols for Cakewalk might be able to tell more. About the only thing I'd recommend is updating everything you can.
  23. What were the settings on the problem project? I tried the Brian May presets at 48khz/16 (my defaults) and didn't have any problems, but would like to know what to avoid.
  24. Falcon too. But no updated release notes yet for either.
×
×
  • Create New...