Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/09/2020 in all areas

  1. https://www.musicradar.com/news/the-best-daws-2020-the-best-music-production-software-for-pc-and-mac Definitely #1 in best free DAW of the century. This is always the poll where some DAW users get butthurt and suffer insecurity issues. I think we are just happy the Sonar lives and its still developed. Meanwhile FL is still the king and I agree. Odd that I got introduced to FL from my Sonar Home Studio 2002 disk.
    3 points
  2. He confirmed it's 32-bit Windows only: https://www.kvraudio.com/forum/viewtopic.php?p=7659944#p7659944
    3 points
  3. 3 points
  4. Finally I can own every plugin known to man.
    3 points
  5. BJZ is: Ken "Zargg" Nilsen - vocals, guitars James "Jyemz" Griffiths - Guitars Ed "Bapu" Kocol - Bass, Piano & Strings Hugo Ribeiro - Drums Scroll down for the lyrics if you want organize "sing along" groups amongst yourselves. Nattmara (c) 2020 BJZ Verse 1: As a child I never really knew any fear The days were long and the night was a welcome My dreams were filled with laughter and cheer I grew older and the night was dark and frightsome Frightsome and then some Pre-Chorus 1: The pressure of growing up too fast My childhood fantasies couldn't last Chorus: Nattmara wears a tiara On top of her ebony hair She prances around in my nightly terrors In the morning I can feel she’s still there Verse 2: My life as man, I kept my love pure I did what I could to keep our life full My dreams are now filled with a dooming fear But something was hidden, making its pull Making it's pull Pre-Chorus 2: Tossing and turning all night long No longer in control, no longer strong Repeat Chorus Bridge Nattmara, why me? Nattmara, why them? Nattmara, why us? Nattmara, please never again. Solo Repeat Chorus Final Solo
    2 points
  6. I was thinking about how so much of my stuff is about the struggle, so wanted to write something more positive. On a mixing note . . . I'm struggling to find the right level for the Hi Hat on this one. If I bury it in the mix too much, the overall feel doesn't work as well, If I have it too prominent, it takes over everything, doesn't sound natural . . . maybe it should be shaker or tambourine, something softer ? Anyways, give a listen, the comments here are always helpful.
    2 points
  7. Storewide https://mercuriall.com/cms/
    2 points
  8. The player is still quite a bit of a mess. If you basically freeze your PC, yeah, the Spitfire player does its job. But it breaks in all sorts of weird ways otherwise. For example, I needed to install a database tool at one point (unrelated to Spitfire, my day job is not music related) and Spitfire Player stopped working. After uninstalling the database tool, Spitfire's player STILL failed to run properly. Ultimately I HAD to uninstall the player, scrub the registry clean (yes, just uninstalling didn't work - wrote myself a small script), restart the PC and reinstall the player all over again to get it to recognize its own libraries. Also, it no longer had an issue with my database tool this time around... I feel a bit sorry for anyone who spent $499 on a Spitfire Player library (i.e. Hans Zimmer).
    2 points
  9. Alternative answer: they're the one who ordered the pizza no other programmer is eating ?
    2 points
  10. People treat them like religions. Once offended over their choice of DAW they start jihad. It's as bad as a Linux distro forum.
    2 points
  11. Night Meets Light - a Dixie Dregs Cover - recorded by Robert Bone and Mike Reidy This is a remake/cover of the Dixie Dregs song, Night Meets Light, that I finished in 2018, and posted in the old forums, and just plain forgot about sharing it with all the folks here in the new world of CbB. Both my friend, Mike, and I, would love to get some feedback on the production aspects of the song - which we mostly were fairly faithful to the general sound of the original song, though I did "modern it up" a bit here and there. Feedback from you folks would mean a lot to both of us, because while we chose this song because of a profound love and appreciation for the beautiful playing in it, we also wanted to use the process of engineering an existing song, as a way to gauge where we stood in terms of crafting a finished product, and by replicating the original song, we could compare our version with the original, we could figure out how well we were "getting it". There is a considerable pool of diverse talent from the Cakewalk community, as musicians and as engineers, and I consider folks here to be my giant disfunctional musical family, and there truly are some experts inmusic production here - certainly way better than me (I am pretty much a keyboard player who tries to additionally wade through the music production process). So, be gentle - and also, please be honest, because I will be taking any feedback to heart, to help me get better at all of this. As far as the playing of the parts, we tried to nail those as best we could, to put our best into honoring the Dixie Dregs, and in particular, Steve Morse, who authored the original song way back in 1978 (their What If album). My friend, Mike Reidy, plays the guitar parts, and the remaining instruments were played/sequenced up by me on my keyboards (violin, keys, bass, and drums). Transcribing the drums took me almost 3 weeks, because they are different pretty much all through the song. Then, near the end, the drums get pretty active, and that was a challenge to faithfully decipher. Oh - lastly, the video was just made to give folks watching in YouTube something to look at while listening to the song, and is simply a series of pics of the Dixie Dregs, pulled from the web. It is the music itself that I hope to get feedback on. THANKS to anyone who read all of the above, and even MORE thanks to anyone who invests around 8 minutes into helping me and my friend, Mike, get better at music production. I hope you guys like it - I edited this post, to now include a link to the real Dregs studio cut of the song, down below mine, for comparison. Link to real studio cut by Dregs:
    2 points
  12. For Kontakt, the process is a little more involved. The easiest way to do this is to create a default output profile for the VST Plugin instance of Kontakt: You may also want to enable multi-core support for Kontakt. This ensures that Kontakt's CPU usage is spread across all your CPU cores: To assign an instrument to an output:
    2 points
  13. Recovering VSPG User here too. That was my second sequencer. Which I first synced to my Tascam 80-8 (lost a track I did). Then later on synced to my ADAT controller and 3 blackface ADATs. Then I moved on to Cakewalk ITB. To this day I cannot remember the name of the first sequencer which was some one off company that went belly up two years later. Had a dongle.
    2 points
  14. Using @chuckebaby's shoe analogy. I have more than one pair of shoes. I have legit licenses for 7 of the 12 DAWs listed and 2 that are not (Digital Performer 10 and Mixbus 32C). I don't own #1, 3, 7, 9, or 12. And likely never will. Like shoes, some sit in the closet for long stretches while others are for used for certain tasks (collabs) and one or two are for daily use. But one is for sure the most comfortable for my current workflow.
    2 points
  15. Hey Noel - Maybe the new logic is getting a partial name match because both of our folders have VST3 in their naming (full folder names are VST32)? That might make sense, as I had tried to explain earlier, when I had my 32-bit plugins in a sub-folder to VST32, the plugins were not removed, or added, or ever mentioned in the scan logs, like they were never even considered for evaluation. And, it would be consistent with the fact that when I moved those exact plugins to a sub-folder within my 64-bit plugin folder, named VST64, that there would be no partial match on the folder name, and then it would all work as expected, showing the plugins added. Bob Bone
    2 points
  16. 2 points
  17. Thanks for jumping into the thread, Noel. Couple of points: 1) I will happily use Preferences VST scanning, for the rest of time. For the record, I had never seen any recommendation to stay clear of Cakewalk Plugin Manager, except for Steve's (scook) indication that you had posted about it before - which was yesterday. Wherever and whenever it had been suggested in the past, to run scans from Preferences, I had not seen that advice. I don't doubt that advice had been given - I just had not seen it. 2) When I created this thread, I did not know that the scanning at launch wasn't being done by Cakewalk Plugin Manager, so my original reporting of scan failures should have named VST Scanning for being at fault, because my issues were caused by VST Scanner's failure to evaluate and process 3rd-party 32-bit plugins for inventory. I did understand that the scanning was kicked off as a separate process, so that CbB would continue to open while the scanning of VST plugins ran, I just did not know that wasn't the actual Cakewalk Plugin Manager doing the scanning during launch. Apologies for my not having named the correct cause of the issues I was having. When the issue first arose, it was during the launch of CbB opening a specified existing project, and in that launch, whatever had gone wrong with the VST scanning resulted in several of the previously working 32-bit plugins, that were part of the project, to be no longer 'found'. I had not run any scan from Cakewalk Plugin Manager at that point. Bob Bone
    2 points
  18. Should locate the folder in Edit-Preferences-File-Folder Locations.
    2 points
  19. I still do this TODAY with my Ensoniq Mirage, which I love and use a lot - it has a pretty unique sound Nigel
    2 points
  20. Is your Sonar content in a custom location perhaps? Maybe search your entire system for a folder with the string "SONAR Themes" in the name.
    2 points
  21. Noel has been recommending this for years It may be time to disable the scanner in the PIM when running CbB.
    2 points
  22. Now they need to work on physical hard drive speed. I saw at CES that one of the companies, Seagate I think. is working on a multi-actuator drive that they claim will work the same speeds as an SSD but I'm not holding my breath on the reality of that happening. Plus, it's Seagate so it will last a week before failing.
    2 points
  23. When I started computing, we had to load our data into leaky baskets made of mastodon leather tanned with urine and haul it up the side of a glacier in the middle of snowstorms in July.
    2 points
  24. When I composed music in the 80s with Voyetra's Sequencer Plus, I plugged in my 5.25" floppy (360K) and loaded up the software into RAM. Then I took it out and put in another 360K floppy to save my data. Of course Sequencer Plus was MIDI only. All sound came from my synths and modules and effects came from hardware. But apparently, it still works today! I remember when I got my first computer with a 20 Mb hard drive. Wow! As my programs were kilobytes in size, and could be loaded in RAM, I didn't know what I could possibly do with all that data!
    2 points
  25. The first computer I ever bought used floppies that held 144 megs. You bought them in packs of 10 and I remember thinking I would never fill them all. And now 80TB? The crazy part is I KNOW I'd fill it up.
    2 points
  26. 2 points
  27. Just how much porn do you need to store?
    2 points
  28. many thanks for the listens . . . and much obliged for any comments.
    1 point
  29. Read about it here https://www.pcmag.com/news/next-gen-hamr-platters-promise-80tb-hard-drives?utm_source=email&utm_campaign=whatsnewnow&utm_medium=image
    1 point
  30. Never had an issue before, but certainly I will be using Preferences from now on, for the sandbox, and for the option for logs. And, I am not sure how you determined that it actually did scan the plugins, because other than the initial listing of the path in the VST Scan Paths, there is ZERO additional reference to any of the plugins in the logs, when those plugins are in a 32-bit folder. Bob Bone
    1 point
  31. C:\Cakewalk Content\SONAR Themes
    1 point
  32. Well, that seems to got it working. encoders, functions, sliders and transport behaving as usual. I need to do more reading on CbBs inner workings, havent read enough to give that page a second look. I know from history that Cakewalk always had a deep implementation of midi, controllers, the ACT protocol, and lots more. I am new to CbB , been to many years on Mac, so time to dig into it. Thanks a lot for your tip. Best Regards. PS Usually I mark post [SOLVED], don't know how to edit title here.
    1 point
  33. What's wrong with the "Official" term??? ?
    1 point
  34. Love the tune! Absolutely “killer” drum track. I realize the guitars are not “carrying” the tune, but I would bring the solo up. Deal breaker? No. Other than that little niggle, great mix Ed. Thumbs up for sure! t almost forget, cool vid
    1 point
  35. Seems everyone at GC is working there solely for the employee discount. I'm always friendly toward them and treat them as equals. Even when they assume I am ignorant because I'm an old fart, perhaps there to get a clarinet for my grandkid. However, I cannot stand being BS'd. That's comes down from corporate, which commands them to sell, sell, sell the high-margin items. So they lie. Monster cables are always "the best". Amplifiers have 1000W outputs even though their UL nameplate says power consumption is 200W Brand names are the most important factor when buying guitar strings. Rokits are the best studio monitors money can buy and all the big studios use them. $100 is a bargain for a 10' mic cable because it's oxygen-free. And of course, everybody there is a guitar player. Ask about keyboards and they can only point to the keyboard room. But I never intentionally bait them with questions I know they can't answer. I save that for the computer department at the big-box appliance stores. Even though I have no animosity toward GC staff, I've not shopped there in 5 years and never will again. GC bought my stolen gear and refused to assist me in any way. Wouldn't let me see the security footage so I could identify the thieves ("it's a privacy issue"). Corporate told me to get lost. Fortunately, we still have a viable local chain as an alternative. Sales staff is just as clueless, but they're OK with "I don't know, I'll try to find out". That earns my respect.
    1 point
  36. Sure - I know with certainty that I had done nothing that would have caused this situation to appear - meaning that I had made ZERO changes to my small number of 32-bit plugins I still must hang on to,. I discovered the issue when I loaded a recent project that used a couple of the 32-bit plugins, and during the load, a popup message box was displayed, saying that those plugins were referenced by the project, but could not be located. Sure enough, ALL of my 3rd-party 32-bit plugins (I had 10 of them), had completely vanished from the inventory CbB builds when it does a VST plugin scan. Worse than that - they were not excluded. It was, rather, that they were not even processed by the Cakewalk Plugin Manager, DESPITE the path to those 10 plugins being unchanged, and present in the VST Scan Paths that Preferences and the Plugin Manager use for scanning to build the inventory of viable plugins. So - they were NOT found to be problematic and excluded. Nope. They were not even processed by the VST scan. I know this because I checked the box to force it to generate a scan log, and in the logs, the only thing present that dealt with those ten 32-bit plugins, was a single reference to the VST scan path I had added, as the scan log lists out all of the VST scan paths it will be evaluating. The PROBLEM is that nothing whatsoever appears in the scan log after the simple listing of that path - so the Cakewalk Plugin Manager has suddenly stopped even looking at 3rd-party 32-bit plugin paths, so those plugins never then show up in the post-scan VST inventory of plugins available for use in CbB, and again, they are not present as Excluded either - it just simply never looked at any of them. SOOOOOOOOOOOOO - I have gone into "Kill it Dead Mode", where I uninstalled CbB, and jBridge, and additionally went into AppData, Program Data, and the Registry, to completely eradicate any traces of both CbB and jBridge, (other than leaving the parameter in every single Inventory Registry entry for every valid plugin in the inventory, that tells CbB whether or not each plugin is to use the jBridge Wrapper to load that plugin (it is built in to CbB so I did not disturb that, but every single occurrence of that parameter - which is part of each plugin's data in the CbB plugin inventory, each data value for that jBridger Wrapper parameter was set to binary zeroes - meaning no plugin is set to be loaded through jBridge). I have just reinstalled CbB, and have NOT yet installed jBridge again, so as to leave this as a completely CbB ONLY scenario, so that jBridge is not part of this current set of testing I will be performing shortly. I want to first make sure I can get the Cakewalk Plugin Manager to even process a single 3rd-party 32-bit plugin that I KNOW was working prior to this glorious nightmare. Mike (CbB support staff @msmcleod) had earlier suggest that there might be an issue with one or more of those 32-bit plugins, and that I try adding those back into the VST search path's folder for the 32-bit plugins to be scanned by the Plugin Manager, so that IF that was the issue, that doing them one at a time would expose which one(s) was/were problematic. This is what I am about to try doing, to see if ANY of my ten 32-bit 3rd-party VST plugins can be successfully scanned. I do already have CbB reinstalled, and am just now about to try adding those in, one at a time, to what IS a completely default CbB install, with NO jBridge present in the system, and the only change to defaults being the addition of the empty 32-bit sub-folder that will eventually have the plugins added - one at a time. The first launch of CbB will not yet have the folder added, and when I do add that folder added - there will be nothing added, with just a restart of CbB. Then, I will close CbB, add a single 32-bit plugin that is KNOWN to work in a 64-bit CbB, and then when I launch CbB again, with loggin enabled, it should process and evaluate that plugin for successful inclusion in the VST Inventory for general use in CbB. I will update this thread as soon as I conduct those additional tests, which should not take long at all. Bob Bone
    1 point
  37. This post was from back in early Feb last year. Right now it is on sale at Audio Plugin Deals. Either as part of "the deal" or you can buy it separately. It's also in The Shop with an even lower price if you have reward credits. Deal $99.99 for just it or $174.99 for it and Spotlight Strings 4D https://audioplugin.deals/deal-1/ The Shop: $69.99 if you have Audio Plugin Deal Reward money: https://audioplugin.deals/virtuoso-ensemble-kirk-hunter-studios/
    1 point
  38. The IBM XT. If I remember correctly it had 256 Mb of Ram and a 20 Mb Hard drive, and a 5 and a quarter Floppy...and THAT was "State of the Art" at the time! Getting a 3.5 Floppy was a HUGE upgrade LOL!!!
    1 point
  39. Ditto...first work PC was 8088...running DOS. The upgrade to windows was a GODSEND, because there was a lot of work I needed to copy across programs, and Windows made it a BREEZE !!!
    1 point
  40. Allan - liked it, sounded good with very nice vocals Nigel
    1 point
  41. Latency Ardour has had plugin latency compensation dating back to almost the first release of the program. But that compensation was limited to tracks (not busses), and didn't cover other cases where latency is introduced into signal flow. Robin (Dr. Gareus to the rest of us) redesigned almost every aspect of the core of Ardour's processing code to now provide latency compensation everywhere. This isn't like some DAWs in which "more things now work". Latency is now compensated for no matter where it happens, completely and always. That reads to me as Aux Buses will now have Latency compensation. If true, YAY!
    1 point
  42. Because Mixbus is in fact customized Ardour one can find a little 'sneak peaks' what was planned in pages of Ardour devs, They are not new but published after release 5.12 which is the latest one. https://discourse.ardour.org/t/ardour-development-update/78588 https://discourse.ardour.org/t/development-update-november-2019/101945
    1 point
  43. This has to do with the very poor transient detection of Melodyne. You must know I like Melodyne and I often use it, but I have learned that I have to revise about 60 to 70% of the detected transients in the note assignment mode. Afterwards everything runs fine. But it is an illusion that the program itself detects the notes automatically (it's Celemony's fairy tale). Even when I've used a very simple and constantly played bass track I noticed that Melodyne sets the transients not at the same place for each note, it is very annoying!
    1 point
  44. I really enjoyed your vocal - really cool voice. I think this is a really good song - nicely done. The BGVs were well done as well. The mix sounded great - nice job. Excellent hook with the lyrics - "A Soft Place To Fall" - I liked it.
    1 point
  45. I too will echo the comments above. Nicely done. The second voice, that's you as well? t
    1 point
  46. Great to hear "Grass Roots# recording. Its easy to loose the magic in our quest for perfection.
    1 point
  47. What Paul said. Well done! Dan
    1 point
  48. Hi a really well crafted song loved the chorus melody and whole feel ,...nice one ..nice to hear an voice without added gimmicks
    1 point
×
×
  • Create New...