Jump to content

David Baay

Members
  • Content Count

    1,298
  • Joined

  • Last visited

Community Reputation

528 Excellent

2 Followers

Recent Profile Visitors

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

  1. They are still working on some latency-compensation-related stuff. There was still an outstanding issue with punch-recording from time zero. Leave punch disabled, and it should be good.
  2. Weird. did they say what the fix was related to? I would still like to better understand the symptoms of failure, and which method you're using to insert the synth. Also, if it's the VST3, you might try the VST2. I ran into this issue with the Chromaphone VST3 more than a year ago, but if you're not actually seeing crashes, this probably isn't it:
  3. Just to be clear, when you say "MIDI track", are you really using separate MIDI and Audio tracks for input to and output from MTPower, or is it a Simple Instrument track that combines MIDI and Audio features in one track? If the dipping/ducking is really related to the guitar signal it sure sounds like you have a side-chaining compressor on the drum track taking input from a send on the guitar track, but that wouldn't happen by accident, and would be hard to forget unless this is a project you're coming back to after a long time or was created by someone else....? But it would explain the behavior since a prefader send wouldn't be affected by muting the track unless you deliberately altered the default behavior by setting LinkPFSendmute=1 in the Config file (AUD.INI). If that's not it, you should share a copy of the project somewhere so we can figure out if the issue is in the project or in your DAW setup.
  4. You may need to enter a more negative dB value for Other Beats in metronome properties. I usually go with -1 and -7dB for First Beat and Other Beats, respectively. I think the default is only 3dB lower, and does not provide enough 'contrast' for my taste.
  5. No, but it does rule out that it's independent of the environment in which it's running, and the project content (i.e. Spitfire synths). Hmmm... that's quite different from "The worst thing about this is that even after rolling back, I'm still having issues with drop outs on Spitfire's OPW... now all of a sudden it's killing my projects. and "I'm getting serious choking even after rolling back." If rollback did in fact resolve the issues, and they are all related to Spitfire then you should report that in the 21.04 Feedback thread. I reported an issue with Izotope Iris 2 during EA that turned out to be related to the large number of automatable parameters it exposes interacting badly with the new automation code. But that was fixed, and was only noticable on my system at very low buffer settings of 32 samples. Even then, it wasn't causing 'serious choking', just crackles and pops showing up sooner than expected. In any case, it sounds like something about Spitfire synths, specifically, is also causing an issue with that new code in which case the Bakers will need to look into it. It will help if you report the symptoms and conditions in detail.
  6. I long ago lost count of the number of reports of issues caused by updates that were eventually traced to some other root cause. Rollback pretty much eliminates the updated code as a cause of the issue. I suppose it's possible some other system issue was precipitated by the download or installation process, but you should still check DPC Latency whether you believe anything else has changed or not. Also, have you checked that interface driver mode and buffer size are unchanged...?
  7. Check your system DPC Latency: https://www.resplendence.com/latencymon New hardware/firmware/driver updates can drive DPC latency up. Low is good - preferably no more that 200-300us (microseconds) - but stable without spikes is even more important. Bluetooth and WiFi drivers are common offenders, especially BT. They can be disabled in BIOS if/when not needed.
  8. I don't think he's talking about a performance problem. The way I read it, he's saying new AAS instances simply aren't created. I just tried several instances of Lounge Lizard and Ultra Analogue and could not reproduce a problem.
  9. I will give it a shot. Can you confirm this was working reliably in a previous release? EDIT: Working as expected here. What procedure are you using, and is it just tracks are not being created, or also no new instance in the Synth Rack?
  10. This can happen if you've previously enabled Copy-Pasting tempo changes in the Copy-Paste Special dialogs, and are dropping the clip at a different time. This is not new, just maybe more obvious because it's so easy to leave the tempo track showing all the time. Check your copy-paste settings, and also the state of 'Use Paste Special Options on Paste' under Preferences > Editing. Depending on your workflow, you may want to disable that.
  11. Pan one hard left, one hard right, and bounce to a new track with Channel Format set to stereo in the bounce dialog. Depending on your pan law setting in Preferences, the levels may change slightly.
  12. Switch to the Edit tool. Smart tool wants to move the split point by default, but Edit tool will default to slipping the boundary. I'm out of practice so don't know offhand what modifier keys might allow doing this without changing tools.
  13. You can either disable the Comp Tool or just avoid clicking in the lower half of clips where its active.
  14. Thanks for confirming. I suspected that might be the case. As a 'MIDI guy', my most common use for punch is simply to define an end boundary when recording hardware synth tracks, so punch range is often from zero to end of the project. I generally don't experience any issues starting projects at zero, and do it all the time, but I would like to be able to re-number measures from 0 for the case that a piece starts with a partial measure of 'pick-up' notes, or needs to give time for a synth to respond to initial controllers or patch changes.
×
×
  • Create New...