Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/13/2019 in all areas

  1. 6 points
  2. Pffft....I have a keg of abs (
    5 points
  3. The usual reason that enabling effects causes a large increase in latency is that one of the effects uses a "look-ahead" buffer. The effect requires so much processing time that it needs to begin to work before the timeline would normally reach the data. Since the effect cannot actually get data from the future, it needs to slow down the rest of the processing and move all of the tracks into the past relative to the look-ahead time. If all of the tracks continued in real time while the effected track was taking the time it needed, then the effected track would go out of sync and fall behind the rest of the project. Hence a "compensation delay" has to be introduced into the progress of the timeline so that new data is going to be added later--that is the delay that keeps new input lagging behind real time. Generally speaking, the plugins that use substantial buffers for this purpose are marketed as "mastering plugins," which indicates that they are unsuitable for use in real time tracking. Best advice is to use a less calculation intensive effect (or none at all) until you have finished inputting real time data. You can substitute the slower effect when mixing/mastering, in which case the delay is generally tolerable.
    4 points
  4. Hey guys, Lawrence from PluginFox here! The trial was taken "out of stock" as we had one person abusing the deal and ordering lots of them with multiple emails. It's available again now if you want to check it out.
    4 points
  5. I'm just happy we still don't have to perform maintenance or have machines break down in the middle of the night (and that DAWs do not require razor blades for edits)/ 😁
    3 points
  6. Technically not a deal! My power has been out for the past 3 days so I was not able to be online...just so everyone knows why I wasn't here.... Thanx to all who carried on!
    3 points
  7. adding this line EnablePluginCancelButton=1 on the cakewalk.ini file wich is there (C:\Users\user\AppData\Roaming\Cakewalk\Cakewalk Core)(see the picture below) nex time you will open a plugin(there will be a new button on top- right of the plugin like you see in this picture below let's say you open a plug to make some adjustements and you dont want to keep it, you just press this button,it will discard the change made on the plug.. thanks martin
    2 points
  8. So I read yesterday that one of the changes in Windows 10 build 1903 was that there was a change made to the Windows scheduler to better operate with Ryzen CPUs. I wondered if this might help with the latency issues I have always had on my 1st gen Ryzen 1800 (8-core, 16-thread CPU). I have a MOTU 896 Mk 3 and have never been able to use the lowest latency for the last couple of years. I upgraded to Win 10 build 1903 tonight and loaded up a couple of projects that always glitched badly at the lowest couple of latency settings (64 and 96 samples per buffer). Holy cow! I am seeing the best performance I have ever seen - zero glitches on these projects! The difference is night and day. And, CPU usage is super even among the cores and lower than ever. I am absolutely blown away in how much better Sonar runs on the Ryzen with this particular Windows update. All I can say is that you have a Ryzen-based DAW, do yourself a huge favor and upgrade to build 1903! I was thinking seriously about going back to Intel for my next DAW. I am now convinced that my next rig will be Ryzen based.
    2 points
  9. It looks like you guys have cleared out all of our supplier's code stock out! Pretty impressive. I'm sure they'll replenish soon. Anyone with an order outstanding will get their code ASAP
    2 points
  10. I don't want to be within 50 nautical miles, when that thing deflates!
    2 points
  11. Is there a buy one get one deal? Just kidding. I knew better than that.
    2 points
  12. It s becoming hit and miss with PA .... also now philscade only reach six months before smashed in price i bought this when it was 99 , i ain t buying PA in release time no more ...
    2 points
  13. If none of the options above help, or are impractical for you try one of these in between your audio output and monitor speakers: https://www.amazon.co.uk/Ground-isolator-audio-noise-removal/dp/B000KHBU1G/ref=pd_rhf_se_p_img_1?_encoding=UTF8&psc=1&refRID=QK5T3XNVWBG0FVJR5CAJ They're only about £6 (approx €7 or $7.50). I've found they move not only ground loop hum, but also CPU/USB activity induced noise.
    2 points
  14. So you're back to tell us all about the $20 plugin deal at UAD right??? Right???
    2 points
  15. I still remember my dissapointment with the sound change when I moved on from tape casettes to mp3 players. It was much more convenient in use but the sound was clearly thin and much less sweet.
    2 points
  16. Crazy that we couldn't wait to get "all digital" and eliminate "noise"...and spent fortunes to do it! NOW we are spending fortunes to get BACK to where we were trying to get away from!
    2 points
  17. Ô k. after tests it s officially better ....
    2 points
  18. Thank you for saving me a lot of money!
    2 points
  19. Don t do it again , i had to post my first deal thread ...!!! Lol
    2 points
  20. Dear Customer, We are happy to announce the release of Blue Cat's Oscilloscope Multi 2.3. This new version has a refreshed zoomable GUI, a new installer on Mac and many other improvements and fixes (full change list below). This is a free update** that you can download from the same location as the original full version (you may have to refresh the web page) **This is the full version that requires a valid license to run. What's New: Refreshed GUI design, with improved usability and touchscreen support. The GUI can now be zoomed from 70% to 200%. Last loaded preset is now remembered in session and displayed in the presets menu. Plug-in state can now be reverted to the last loaded preset. Now supports retina displays on Mac (text and graphs using high resolution). VST3: added support for MIDI program change messages to change presets via MIDI. VST3: fixed audio muted in some host applications. VST: the user interface is now properly resized in Cubase on Windows. Mac: new installer. Mac: fixed minor compatibility issues with Mac OS High Sierra and Mojave. Dropped support for Windows XP and Mac OS X 10.6 and earlier. Dropped support for legacy RTAS and DirectX plug-ins formats.
    1 point
  21. May want to review Live Input PDC override
    1 point
  22. This would be "depressed" 😛
    1 point
  23. Nice one! Thanks Lawrence. My license has arrived 👍🏻
    1 point
  24. 1 point
  25. blimey! it was ye olde Sounde Blarster, with a EMU daughter board
    1 point
  26. 1 point
  27. Yep lots of low priced and free libraries out there fer sure. I tend to use Kontakt in a more simplistic way. I seldom build multi's in Kontakt. I don't run a lot of tracks. I just load a bunch of separate instances up. Drain on cpu isn't that bad. You can save it as a mix scene and it will be the same next time you open it.
    1 point
  28. Martin, Where were you with this when I needed it two days ago? When I changed the attack time of a compressor on an acoustic guitar track that was perfect and subsequently had to change the output gain too while forgetting to remember the initial values of those parameters? I thought well, Ron, that's what mix scenes are for but I forget to do that too. Martin, I thank you for this. It does work and I will use it. Whether or not I remember to use that button. Addendum: Don't close the effect GUI or you loose the revert values.
    1 point
  29. He was a very decent person in real life . He took the time to console and help me out once ... RIP Dr John Kenny
    1 point
  30. it would be good to get those vouchers !
    1 point
  31. I'm with ya on that Larry. But the way I use the J37 is I keep the noise to the very minimum. It's the response after feeding the signal into the machine that I like. I don't use wow and flutter much either. Same way woith AR Vinyl. Don't add much of the clicks or noise, just like feeding the signal through. (And I love just playing around with that slowdown button!!)
    1 point
  32. Agreed. Same with the cymbal. Some rvb (like Tom suggested) would blend it in and make it more distant, and lower the volume on it. Maybe even alternate the cymbal sample with a few others to help give it a wider spectrum. I did start listening to this on my cell phone and I can tell you, I heard those cymbals above everything else. Listening at work here on regular speakers and the cymbals wasn't as pronounced. But still a little too up front. Forgot to add : Nice song.
    1 point
  33. I dig Kloon's stuff. The groove is like an ecosystem. Lots of interdependent elements that are all mixed extremely well. Sounds like a clean, pro mix. Nice! Vocals hold it all together just great. I will diverge a little on the lyrics / meaning. From my perspective, kind of an older dude who's seen a few things, I found the theme and lyrics kind of preachy!!! But guess what - you are not writing this for me . . . Perhaps for a certain kind of person, this could be an anthem. For someone needing a guiding light, or something. This might be their song. Digression over. Nice tune, as usual. I haven't heard a clunker out of you yet. cheers, -Tom
    1 point
  34. Ah! These drums fit quite nicely. Nice tune. I liked how you strip the arrangement down in the middle, and modulate everything back in. Nice choice. For me the reverb choice (maybe it's chorus, too) on the synths, the arpeggiated stuff, the snare, the sax . . . very nice! But the occassional cymbal crash sounds drier. Maybe a little more rvb on that cymbal? And perhaps lower the cymbal just a bit in volume? I dunno, just a niggle really. Nothing wrong as is. cheers, -Tom
    1 point
  35. And big thanks for that! I haven't bought any plugins for about 3 days now...
    1 point
  36. The GAP Pre73 is indeed nice but yes, unfortunately no EQ/dynamics as pointed out. Love it in a vocal chain.
    1 point
  37. Edith loves a six-pack.
    1 point
  38. Yes, the weather is fine, time to grab some beers... Oh sorry, you were talking about a six pack of Midi!
    1 point
  39. Want to hear and see the new Amps and Cabs in action. Watch Mike's video ! https://www.youtube.com/watch?v=G1YzX9wYQdw Cheers!
    1 point
  40. You should post one of these every 28 days or so. Just as with any good joke, it's all in the timing.
    1 point
  41. There was a known VST2 issue with Izotope Neutron in Sonar when that was released and the workaround until it was fixed was to remove the VST2 version and use VST3 version only, so I figured I'd try the VST3 and see what happened. Thank you for the explanation of the technical. I have no clue about that side of things. CW have responded to say that they are on the case. Having been informed that using the VST3 version does not cause the same issue, Initial Audio seem content to leave it at that and show no apparent interest in investigating the issue further.
    1 point
  42. 1) Sending in the dump was/is helpful to CbB support folks, and even more so if a good recipe for replicating a crash can be determined, and sent in to them as well. 2) As noted by others above, that particular error is a pretty common thing - trying to access memory not owned by the application, in this case the plugin. Things that can cause this are varied, and example would be if a memory pointer had not been valued - and contained all zeros, or wasn't repopulated properly due to falling through some set of If/Else conditions, and thereby executing code that should not have been reached in the normal programming logic. 3) If an error occurs within a plugin, there is pretty much no way for CbB to recover from it, as that plugin had control when the error occurred. If the error had occurred in some location within Cakewalk, you would have almost certainly seen Cakewalk as the failing module, and an offset within the program, rather than the way this crash message was displayed, (with the plugin being named as where the error occurred). 4) AWESOME, that you were, however weird it was, able to workaround the error, by using the VST3 version of the plugin. I have never before seen it go THAT way before - it has been (with some Waves plugins, mostly from what I recall), usually where a VST3 version fails but the VST2 version works. Congrats for even thinking to try using the VST3 version, AND for it allowing you to keep working on your project, and moving it forward. 5) Even when SOME plugins have gone belly up in the past, there have been occasions where the Sonar support folks were able to tweak the Sonar code to have special code to deal with some failures within some failing 3rd-party plugins. No guarantees this will happen here, or ever again - but it was pretty darned nice of those folks to do what they could to keep folks afloat by creating special logic to deal with some deficiency in one or more plugins that weren't their responsibility. Bob Bone
    1 point
  43. The vast majority of folks are running Windows 10 at this point, where maintenance to Windows, or even the version of Windows running, isn't the wild wild West it was, back in the days of Sonar (several flavors of Sonar 8, X1, X2, X3, and Platinum, on top of various Windows versions and maintenance levels of Windows, not to mention drivers, firmware, BIOS, etc...). There were, all kinds of different combinations of environments - and at times, a Sonar update version wouldn't play nicely because someone's Windows updates looked like Swiss cheese. Folks that chose to do rollbacks of Sonar had the freedom to choose how far back to go, or not to worry about it. I found it useful in trying to figure out if a given update version had broken something, versus my just not realizing a particular function hadn't worked in a while, or whatever - I found it QUITE helpful to be able to go back and forth as desired, with Sonar versions. I also frequently rolled back in my attempts to match some other user's version, to help them track down why something wasn't working any more. I hadn't considered retaining multiple versions of CbB and any associated folders, but may do so now or soon. Thanks for this thread - good idea, I think, to have a way of approximating rolling back. Bob Bone
    1 point
  44. When recording direct, the DI input can make a massive difference (positive or negative) in the sound. Many folks think all you need is a "Hi-Z" input. While it's true you need an input with high impedance, there's a world of difference between various Hi-Z DIs. If you're recording passive Fender electric bass thru a cheap Hi-Z DI and it sounds anemic, the issue isn't the bass. That same bass thru a Neve DI will sound amazing. I used to really struggle to get nice DI bass recordings. Tried 1001 different DI solutions (SansAmp - numerous boxes, Reddi, Avalon U5, Solo-610, etc). Finally invested in a Neve Portico-II... and suddenly... good DI electric bass tone was easy to achieve (plug-in and set levels). A nice DI/preamp isn't the most exciting musical purchase, but it's one of the best gear investments you can make.
    1 point
  45. I only use multiple DAWs if I need to. Otherwise I use CbB. Case in point. My goal was to record a movie playing and have a nice audio track....seems simple enough right? None of my DAWS capture video, so I opted to use Vegas Movie Studio. It uses an inner program caller Capture to actually record the video from a webcam which you then move into the movie edit area to work with it. I wanted to import the basic video into a DAW and do some basic editing in it since I didn't intend to edit the video. I'm not a fan of the audio tools in Vegas, even though it will host vst's. The video was an .avi file which didn't agree with CbB when I tried to import it. Next I tried Studio One Pro 4.1. It imported the video but doesn't show a slide by slide timeline of the video. It basically shows the video in a window and it's up to you to align audio to it. That process seemed a bit clunky to me. It did at least allow import and I was able to align the audio to it. Next I will probably try Mixcraft Pro 8 because it's the only DAW I have that seems to have basic video editing capability in it. I likely doesn't import avi ...so I've hopped across three programs to accomplish one simple process. Next time I'll know what to do. This is an example of what can happen if one tool doesn't offer what you need. How you work determines the tools you'll need. If you record group vocals in harmony you might like the vocal alignment tools in Cubase. If you caught the sale awhile back on the basic version of VocAlign by Syncro Arts like I did you bought that, or if you had Sonar Platinum you have a tool in it that does the same thing basically by taking a master track and aligning a slave track to it....or you could simply do some basic audio editing if the problem isn't too bad. There's usually more than one way to do something. In my case I have two different ways to do what the function does in Cubase. Melodyne is the most popular vocal pitch correction tool out there. Most DAWS come with a basic version. Why would I use Cubase's vocal tools? I have Melodyne and the Waves pitch correction plugin, plus the old one made by Roland.....so what I'm saying is, I would need to justify a good reason to buy that DAW or it will sit and gather dust. If you like CbB and there's something it doesn't have there are likely inexpensive 3rd party options to fill those gaps. One thing that really helped me out was buying a few of the 3rd party plugin packages. Now I have all of my bases covered. Everyone does that anyways, no matter which DAW you have.
    1 point
  46. Just saying, listening to Morphine way back when and still is what got me into baritone sax for dark rock. Remember Morphine?
    1 point
×
×
  • Create New...