Jump to content

Keni

Members
  • Posts

    3,266
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Keni

  1. 12 hours ago, David Baay said:

    As mentioned in your other thread, CbB uses the ASIO buffer as the default "chunk" size for offline rendering and some plugins can be sensitive to it - more often when it's too small than too large. But in general, offline rendering will work just fine even when the buffer is too small to get pop-free plyback in real time. The reason is that there's time pressure to keep the interface driver supplied with a steady stream of buffers when rendering offline. If a particular buffer takes a little longer to process for whatever reason or a some other system demand interrupts it, the CPU can take a l long as it needs to process it and write it to file.

    Thanks David...

     

    That's what I have been believing... and experiencing. But wanted a firmer grasp on what's involved and going on. I had the understanding that without the immediacy of live playback, the pc was afforded the necessary resources to accomplish more than the live play...

    Yesterday I played safe so that I didn't feel I needed to scrutinize for such errors (though of course I did anyway) I simply opened the latency all the way to 2048 to be safe! ?

     

    • Like 1
  2. 20 minutes ago, John Vere said:

    You mean buffer settings. Lower buffer settings reduce Round trip latency. But that’s nothing to do with also increasing them to stop drop outs and static. 
    Latency is only noticeable when you turn on input echo when recording audio or midi. Not during playback. 
    This why interfaces have direct monitoring so latency is not a factor in tracking audio. 
    Round trip latency is more or less invisible to anyone who records, edits and mixes with a DAW. 

    But buffer setting are important and performance is based on the quality of the system. 

    A powerful computer with lots of cores and RAM will run at a lower buffer than a not so powerful one. 

    Then some ASIO drivers are better than others like RME, and that also helps prevent dropping out at lower buffer settings. 
    But as projects grow and certain plug ins are added that starts to stress the system and that might require increasing the buffers during mixing to stop glitching. 
    But increasing buffer settings and then trying to record midi you might hear the latency so we then just globally bypass the effects and 99% of the time this fixes it. 

    Then exporting a mix is all in the box and has nothing to do with buffer setting or your interfaces drivers. It just goes faster on a more powerful machine. 
    I always set mine at 256 and forget about them.  But that said my now retired Motu M4  was on the edge at 256 so I had to bump it up. I now have a Zoom L8 and it is on the edge at 128 so I’m back to smooth sailing at 256 again .  
     

     

    Thanks John

     

    I think you addressed my question towards the end of that.

     

    When rendering an output mix, the latency settings do not affect the outcome...

  3. I'm just looking to find out for certain about this issue.

    When I'm freezing a track or Bouncing down, or exporting a mix etc.

    The latency should not be a factor? I mean I know that I've recently encountered a plugin that crashes when freezing with latency set longer than 512. So I know that they do relate...

     

    What I'm wondering is...

     

    If I hear artifacts while listening and they go away at longer latencies, must I set my system to such latency when I export? ...or as the processing is happening without playback, should I expect clean results? So far it sounds as though this is true, hence my confusion...

     

    Many thanks...

    Keni

     

  4. Worked for me here using my own domain mail address/server

    Took some jumping around to get it and then more to figure out which of the T-Racks plugins it actually gave me. I did get it on first try, but the names were written are written very differently EQP-1A would have sufficed...

    Now to see how it sounds?

    I also got the Warmy EQP2 last week...

  5. 1 hour ago, augustenz said:

    Yep, but as I have mentioned, sometimes certain plugins may behave differently compared to others, so even though it may seem that everything is ok, as everything else is working fine and this is the only plugin that is misbehaving, does not rule out that it may be a latency or driver compatibility issue with that specific plugin.

    Also sorry for suggesting Cubase's ASIO driver, didn't realize that CbB stands for Cakewalk by Bandlab (thought it was some version of Cubase)!

    But Asio4all would be worth a try: https://asio4all.org/2-15/

    or KoordASIO: https://apps.microsoft.com/detail/koordasio-universal-driver/XP9CSS6NZBDV21

    I just read the thread @chris.r posted and it seems that it is happening to others too, so it may be a common issue with CbB and this plugin. One user stated that unchecking the VST3 Migration boxes solved it, another that downgrading to the version 5.4 solved it.

    Another thing to try, even though it is not really a solution, is to try the plugin with a different DAW (on the same system) - if the problem goes away, then it is most probably some incompatibility between CbB and this plugin.

    OK...

    I understand as I've run into these issues before with other things...

    Further investigation has yielded some results though... Latency...

    I ran at 64/128/256/512/1024/2048 with all other tracks archived.

    Apparently...

    No difference between 64/128 with very few chirps each

    256 gave fewer chirps as did 512 and 1024. I didn't bother trying 2048

    I also ran tests with my other tracks unarchived thereby loading down the system with more demands to see the results and as expected, it progressively increases the chirping, but at 1024 I am able to run the whole project live with what seems no chirping.

    So it's gonna be a git difficult to use but I have workarounds when needed. I will likely keep both this and the Arturia 140 loaded. Use the Arturia while working and switch to longer latency and the Little Plate when ready to export a mix..... At least for this song. They are both quite good, but different so which I will use in the future will depend.........

     

    Thanks for sticking with me on this, I can't say I feel good about it, but I feel better having uncovered the issue for now...

     

    Oh, and I can't really switch drivers. In order to have the 18 i/o system I must be running the Presonus driver....

    I use an old Presonus Audiobox 1818VSL

     

    • Like 1
  6. 1 hour ago, augustenz said:

    Hmm, weird indeed.

    How about the audio interface? Is the driver up to date?

    What ASIO driver are you using?

    Maybe Asio4All, KoordASIO or the Cubase Generic Low Latency ASIO driver solves the issue?

    Another thing that has happened to me, Arturia instruments and plugins would not work at all in Cubase with my interface's ASIO driver (which is outdated and there are no updates available as it is old), but would work with Asio4All and the others.

    What I found, through trial and error, was that anything below 100ms latency would work ok with my interface's ASIO driver, but equal to or above 100ms - no sound/processing. The crazy thing is that it only affected the Arturia products. Everything else had no such problem with the latency, which made it even weirder and harder to troubleshoot.

    So maybe trying a different driver or a different latency may solve the problem.

    All other plugins are working fine including Little Radiator so I don’t think it's "driver related"

    As to latency? I’ve only tried two settings. My fastest 128 and 256. I rarely operate outside of this.

    64 is mostly useless but I’ll try that as well as longer latency of 512/1024. I did find such solved crashing of Amplitube 5 which crashes longer than 512....

  7. 52 minutes ago, chris.r said:

    You could try installing these betas from the thread I posted.

    I must have missed this. I only saw the soundtoys downloads list which I used and still get the chirping... I also just deactivated it on this machine, re-installled and activated, but I still get the chirping...

    I don't have this issue with Little Radiator...

  8. 57 minutes ago, chris.r said:

    I wonder if you just experienced same issues from this thread:

     

    I guess it could be as the chirps do create a bit of a bump.

    I'll check fir the download. I don’t know which I have.

     

    ...

     

    Ahh... I just installed the current download and voila! Chirp gone!

    Thanks. That solved it. My previous version was from 2017!

     

     

    Oops! Spoke too soon... Still chirping!

     

     

     

  9. 1 hour ago, augustenz said:

    So it was not the latency after all?

     

    I just opened a project and put it on a channel, left it playing for the whole length and there were no artifacts etc., it worked normally.

    I am on Windows 10, using Cubase Pro 12.

    Did you activate the license on the computer using iLok?

    Yup. It claims activated.

    win10 CbB here

  10. No one else is experiencing the chirps?

    They are like what is heard in a demo version that beeps periodically so that it's essentially unusable but allowing a demo.... But this isn't supposed to be a demo?

    I like the sound of it, but...

     

    I keep going back to the Arturia EMT 140 (which isn't bad either but I prefer the Little Plate in this particular situation) to get away from the annoyance. I'm wondering if it will persist when a mixdown is executed? <sigh>...

  11. 8 minutes ago, dumbquestions said:

    Tried in firefox, brave, chrome, safari, and got the “come back on the 24th” message each time.

    Yes... That's the point. There's nothing to get now. If you've registered, come back on the 24th.

    That's when it will be available.

    They also mention that they will send an email notice at that time too!

    We'll see...

  12. Though it doesn't appear to be in freezes/exports, while listening/working on a project with Little Plate in it, I get periodic (not equally times) "chirps"

    Does anyone else get this?

    ...just now thinking. Maybe increase latency? Maybe it's a result of that? I'll see...

     

  13. 12 hours ago, cclarry said:

    Boy...that site is crazy!  It doesn't let you know that you've signed up...it just sits there 
    and says nothing after pressing "sign up"

    I got a confirmation in Firefox... It tells me to expect an email when it becomes available...

     

  14. Yeah, I ran into all of the above....

     

    It seems Play is replacing Lite and being renamed ans Analog Lab V while Analog Lab V is now Analog Lab Pro

    I too found it strange that the new "Play" which is only called Analog Lab inside, not Play or Lite, is not included in Software Center. I'm guessing it will move into there if upgraded to Pro?

    Very odd. It doesn't show anywhere in the Arturia online account (my account). It shows Analog Lab 4 here, but that loads as Lite... Confusing all the way but some great sounds, yes?

     

  15. 26 minutes ago, Erwin593 said:

    I'm having the exact same issue, got the free UAD LA-2A and it crashes every time I try to use it.

    This is the error log that I get:

    CakewalkCrash_Log.PNG

    just to note...

     

    It works fine here.

    Curious...

    Did you try using different latency settings?

    I had a similar problem with Amplitube 5 and solved it changing latency. At 512 it crashed! Disappeared in a puff! At 128/256 it freezes fine...

     

    I just say this because the free UA LA2a is freezing fine here, but I've only been running at latency of 128 .

    That theory just failed here. I can freeze the LA2a at 128/256/512/1024

     

    So that's not a factor here... Sorry.

     

     

  16. 5 hours ago, Red Four said:

    Hi folks,

    I recently installed the UAD LA-2A which they've been offering for free. I have not been able to use it, because every time I attempt to open the plugin interface within CbB, it crashes the program, closing it immediately.

    The plugin seems to install fine, and shows as connected to my iLok account. Scans fine in the CbB plugin scan. I can pick it from the plugin list and add it to a track. But when I open it after applying it, it briefly opens the plugin interface window (with the window filled with a gray blur) and then Cakewalk crashes.

    I've not had this happen with any other plugin, so wondering if it's just me or if anyone else has seen this. Waves, Soundtoys, NI, Analog Obsession, SSD, TDR, I have all kinds of other plugins that work fine and have never had this issue. This is my first time using any UAD plugin.

    If anyone has any tips or relevant experience with UAD, I'd be glad to hear it! Thank you.

    Kevin

    Not with UAD. It’s working here, but I had same problem with Amplitube 5.

    Investigation turned up that if I was set at latency 512 is crashed. If I changed latency to 128 or 256 it worked fine. Maybe try it with your situation?

    • Like 1
  17. 6 hours ago, User 905133 said:

    I just gave the Cherry Audio Space Delay a quick (15 min.) test since I haven't used it in a while.  Due to tinnitus, I don't hear much external hiss. (I hear hiss all the time.)  So I used SPAN, and didn't see excessive emulated tape hiss visually.  

    Some of the presets allow the build up of wide width-noise; so, playing around with the various modes and built-in FX, and then going really crazy with the levels and settings, I was able to build up layers not unlike I used to do with reel-to-reels, but with much more intentional control.

    I heard this above the level of my tinnitus and SPAN showed me what I was hearing visually.

    When I backed down on the massive amounts of tape and other built-in FX, the sound was much less noisy to my ears and as displayed using SPAN. 

    Not doubting there is noise in the tape hiss range or that the emulation might have a wider appeal if it had a noise off (or maybe a dbx/noise reduction) mode.

    I've seen other 201-inspired emulations, though I don't have any.  Maybe one of those might work better for you.

    On the other end there are some other echo plug-ins that justifiably are called lo-fi (or something similar). Some developers put their money into making animations that simulate a tape loop going around the heads at the expense of audio efficiency.

    I haven't listened to McDSP's EC-300 in a while, but I seem to remember that had a lot of options (3 different kinds of device emulations) including some that had nice clean echoes.  

    https://mcdsp.com/plugin-index/ec300-echo-collection/ .

    Ever since the days of reel-to-reel tape echo and long hallways, stairwells, etc. I have been a fan of echoes.  Sometimes I want tape noise build up; sometimes I want sound bouncing off surfaces in all sorts of directions. And sometimes I want pristine, unadulterated echoes that just seem to bounce with immaculate precision.  Sometimes the Tape Echo in IK's Mix Box (as basic as it is) fits perfectly for what I want.  Of course, then there are MeldaProduction's Echo/Delay Plugins--one day I will understand them so well, I will be able to built my own "perfect" delay/echo device.  ?

    I always liked them too.... they were fun as were echoplex which I also had lots of fun with...

    But they are/were noisy and emulations tend to leave it in for authenticity... But many offer the option to simply switch it off creating a more modern "quality".

    These days with how much lower our noise floor is, I fid it hard to justify at times...

    ...as a matter of fact, I just tangled with this issue today on a piece I'm working on where I'm using two EMT 140 simulations and I keep noticing the noise... as low as it is. In this case I'm living with it as it's so subtle, but often that noise floor is too hard to handle these days (for me)

     

    Oh, and I do like the 201 emulation. I'm not dissing it. I'd feel the same if I was sonfronted with using the actual hardware... ?

     

     

  18. On 10/19/2023 at 6:25 AM, cclarry said:

    DarkSkyAudio has seen some big changes in the last two months.

    We’ve restructured so now it’s just me running the show. To give this change a bit of a wink and a nod, I have released the next evolution of my FREE Kontakt engine. 

    Socora LITE features next-gen systems and sonic wizardry that nudge it even closer to the authentic sound and feel of a high-end, hardware analog synth. 


     …and it’s still FREE to download! 

    I don't know if the Password is generic or not

    https://www.darkskyaudio.com/subscribers/

    Will it run in the free version of Kontakt?

     

  19. 8 minutes ago, mettelus said:

    +1, I am firmly entrenched in using an old copy of Adobe Audition in the Utilities menu so I can do that in less than 30 seconds and not require any track bounce afterwards, but I am also always on the lookout for options to new folks that function and don't require massive money investment. Spending CPU power every time the transport runs to remove something that you want to obliterate anyway is a waste of computer resources. I was hoping this might have tracking potential, but the overhead is a bit much to be feasible.

    I have always avoided using that kind of stuff while recording outside of Dolby/DBX noise reduction back in the day.

    The chances of losing some stuff while recording has always out weighed the noise issue. Safer to remove it later.

    Luckily, these days, tech has evolved to a relatively decent level. Far fewer noise problems than in the past.

    ...but when it perks up it's scratchy little head we have bluenoise to help!

×
×
  • Create New...