Jump to content

mettelus

Members
  • Content Count

    627
  • Joined

  • Last visited

Community Reputation

461 Excellent

1 Follower

Recent Profile Visitors

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

  1. Reminded me that I need to revisit this one.
  2. LOL, what a hidden gem this thread is!! I have only been logging in every few days and only opened it because the title was weird. Did they put a restriction on advertizing this as "50% off most Spitfire titles for 28 hours with Code - [ ]"??? Just in case they did... for those late to the party, the code is at the 5:07 mark in the video in the OP.
  3. mettelus

    Melda updated to v15

    Now Vojtech just need to steal the "smoky cloud" graphical artist from iZotope for marketing materials The support manuals could also use an overhaul. Part of that is the boilerplate format used for them and the fact that they have to be geared for folks who only own that plugin, but it still takes users a bit of effort to delve into the Edit screen and feel comfortable in the guts of many applications.
  4. Promo email came in with an interesting 2D model that looks 3D Not sure if that link embed anything, but worth a try. I guess the promo is for email subscribers. I was going to post that link but is to me, if you subscribe to their newsletter it should show up for you (is Moho Debut 13.5 + 100 Brushes Content Pack + Characters Content Pack for $79 (versus $119)).
  5. Quick feedback on the above. The 500GB EVO Plus I ordered didn't arrive till yesterday, and I just cloned/installed it (the PN from the above article only works on the 1TB model, so I blew it off and not sure if the article above also applies to the 500GB model anyway). The old drive was a WD Black 256 GB, but was throwing security errors (if rebooting, but not from a cold boot) and the Recovery partition was 453MB/500MB which was flagging it red in Macrium Reflect. I have two M.2 slots so pulled the F drive and used that as the clone slot. Cloned with Macrium Reflect and bumped up the Recovery partition to 1GB, and the Main partition to fill the rest of the drive. This video shows how to clone/reset partition size (I time stamped it at the partition size part if anyone is interested). Be sure to power down/unplug the machine when swapping any hardware! Swapped drives, put the F back in and booted to the UEFI. Fast Boot was enabled, so disabled that (to ensure nothing was remembered from last boot), and the boot was already set to the new EVO Plus. Restarted and the machine ran identical as with the old drive (so far nothing has asked to re-register, etc.). Now to the benchmarks. Samsung's Magician won't benchmark competitor drives anymore (used to), so could only test those two drives. C Drive: 970 EVO Plus - Sequential Read: 3494 MB/s, Write: 3065 MB/s, Random Read: 125,732 IOPS, Write: 105,468 IOPS F: 970 EVO (NOT Plus) was in x2 Mode - Sequential Read: 1764 MB/s, Write: 1707 MB/s, Random Read: 132,080 IOPS, Write: 111,572 IOPS Didn't realize that drive was in x2 till the benchmark, so went back into UEFI and set to x4 mode (disables SATA 5/6 connections) F: 970 EVO (NOT Plus) in x4 Mode - Sequential Read: 3502 MB/s, Write: 2536 MB/s, Random Read: 134,033 IOPS, Write: 115,478 IOPS Bottom line: even in X4 mode, the EVO is not noticeably faster than the EVO Plus in the main drive slot and was actually slower for sequential writes. That WD Black 256GB was actually a bonus item when I built the machine, and not exceptional to begin with. I may consider that one the "first SSD I toasted," since running SFC/DISM checks the past few months was throwing repairable errors.
  6. Ironically, the 970 EVO Plus (500GB) is 40% off at Amazon and I bought one before this was posted to replace my C drive. It should arrive tomorrow, so I will check the part number on it and benchmark it when I put it in the machine (probably this weekend). The specs on Amazon are pretty straightforward, so this should be an easy return if it isn't the real one.
  7. This has been their model for years though. Unfortunately, those who jumped in at some point with MPB/MPS were suddenly seeing what was offered with the next upgrade as lackluster... one or two products upgraded each year, then paying again for something they have already. Throwing in things that not everyone may want is only going to entice so many. So many digital products have matured to the level that grabbing the last version before they went subscription will suffice for most people. If someone is using for business and pulling in enough revenue that the percentage of upkeep is tolerable, then it may have merit.
  8. Didn't get to deep into that one since it immediately reminded me of the old joke of "How do you you get an Italian to shut up?" (Either tie his hands behind his back or make him sit on his hands). Word choice took it right off the plate as objective early on, so I only made it about 30 seconds in
  9. LOL... On my phone here so clicked that wondering why the link didn't work! No more underlines allowed 🤨
  10. Another consideration is weight and how much you need to baby the amp. Tube amps are significantly heavier and susceptible to sudden shock. If sitting in a studio this is not a big deal, but carting it around is another matter. MOSFET technology has been in use for well over 30+ years now, but as Craig mentioned, the final 1% can be a big deal (more for studio than live in my opinion)... and the circuit designer also plays a massive role in the quality of the end product. That said, the plethora of both pre/post FX is another consideration... I have seen folks running chains through a laptop, and the amp was simply another PA system for them. Bottom line, as also mentioned above, people attending a gig are not going to be as uptight regarding hardware as they are for appreciating LIVE music that is performed well.
  11. TDR Kotelnikov, MCompressor, ReaComp (all free and work in CbB). TDR Kotelnikov also has a Gentleman's Edition (not free) with a few more features.
  12. That is the kicker in most cases. A real instrument requires proper environment, mics, yada, yada to even record properly (step 1), and that is only part of the effort to get a good song. VSTis are light-years from where they started and folks have gone to excruciating lengths to get them accurate. From a user's perspective, the value of VSTis over the real instrument is often overwhelmingly one-sided (cost, quality, maintenance, time, etc.).
  13. True, but Drum Empire is one file and is just high-resolution content that is fairly generic (5 kits basically that can be found elsewhere). That particular file is #1 on my axe-list if I ever need more HDD space. MDrummer will also import and sort (to the best of its ability) samples you already own (which can take a while). People with limited bandwidth are going to get frustrated by Drum Empire as well. Drum Empire could easily be down-sampled and lose nothing, but is in a proprietary format. The Studio 2018 kit in particular has the most diverse content of all of them, but is still 14.3GB IIRC on its own. Now that it is bundled with 2008-2018, it is even bigger.
  14. Another issue may be that the timeline is not set properly to the song. If reginaldStjohn's answer isn't the solution (it should be), does the timeline match the project? It is unclear if you imported audio or not from the OP.
  15. I had to read back through the thread to catch this. Are you putting project data on the external HDD? Having buffer set TOO high can sometimes be as damaging as too low, and HDDs need to seek to pull data. The 2048 buffer size on 32 audio tracks from an external drive could be a choke point in your throughput. A quick way to test this: Open the project, and do a "Save As..." create a new folder on the HDD and save it there (be sure to check the copy audio file option in that dialog). What that does is "bunch" all of those audio tracks together, so the HDD does not need to seek so much. If you have enough space on the OS drive, do the same there so you have a new copy on both drives. Try lowering the buffer size to 1024 (or play with the variations below 2048) to see if that helps. Start with the HDD project, then shift to the one on the OS drive. Setting to 2048 actually forces the audio engine to fill those buffers, and with 32 tracks that may be more than your HDD can handle. Bottom line, when playing back audio (and the global FX bypass (e hotkey) is engaged), the audio engine is doing nothing more than streaming tracks from the source (as simple as it gets). If that is glitching, then the throughput isn't happening. I suspect moving that project to your OS drive is going to help, since external HDD (magnetic) drives are not known for speed, but reliability. You may find that working ITB (in the box) is faster, so may need to do project work there, then archive to the external when need more space (the same "save as..." routine, which also strips off anything not actually used by the project when saving it, so this also is a way to regain disk drive space).
×
×
  • Create New...