Noel Borthwick

Im quite impressed I can put the latency down to 16 samples and it works fine here.

I've fixed it for the next release. It was a regression caused by some new code affecting tracks assigned to the same shared input channel only.

@Kai Olav FredriksenThanks for reporting this. I've fixed the issue for the upcoming release. Let me know if you would like to test a build with the fix.

Found the source of the record issue, thanks. It only showed up if you had multiple tracks assigned to the same input. Fix will be in the final release. If anyone wants to test the fix PM me.

@MarkNisbet please check your PM. We will need to do some more detailed troubleshooting since we can't repro this case here.

Yes I don't think they have released a fix for this issue yet since I havent heard back from Steinberg. That update you downloaded may be a different release.

I just tested the rocksmith cable in WASAPI shared and Wasapi exclusive mode and it works fine here. I output through a different headset device. In fact in WASAPI exclusive I could go down to about 5 msec buffer sizes and it worked ok. It also works with my focusrite as an output but the focusrite has poor WASAPI latency. What problem are you running into - do you get any error messages?

This is a bug in the plugin and has been already reported to Akai by us.

When reporting dropouts please mention the dropout code. Did you already look up the help for the dropout from the link in the message? There is no way to diagnose this without the code.

Can you please share your template file so I can look at it? Is this problem new to the early access release and does rolling back solve it?

This thread is to discuss early access specific issues. For feature requests please use the Feedback Loop

@Ervin Pegues can you PM me your project file? Is this a simple audio project or are you recording synth inputs? How many record inputs do you have enabled in preferences - post a screenshot of your audio devices page. Please also try unchecking Exclude Synth inputs and see if it changes the behavior. Also try disabling Allow Arm changes and check again.

Hi @babylonwaves, Thanks for stopping by. I'll PM you and we can discuss further.

Yes its really hard to reproduce. We'll try and fix it.

I worked with Steinberg to help them troubleshoot this. I'm glad they released the fix. It was an issue with their licenser managing process states as far as I know.

I don't see any reason to be snobby about Realtek. Its quite amazing what they do at the cost and its a viable solution for playback when all you have is a laptop. For input you will need a line level signal. Here is an example of their specs: https://www.realtek.com/en/products/computer-peripheral-ics/item/alc898 For recording the bigger problem is that the converters are housed in a PC which typically isn't the best location to avoid interference which is where most of the issues arise from with hum and noise. The OP was not looking for high quality so if the user can get it working without spending a hundred or more its a good thing.

Glad that the dropout diagnostics were of use. Once you followed the instructions ? Based on your project description you have close to 173 tracks. Assuming that they are all audio tracks that is a fair amount of load on the disk. If you have a slow disk a buffer size of 256 may be too slow to keep up esp if its fragmented. Is it an SSD? PS: A dropout is not quite a crash <g>

Glad that the dropout diagnostics were of use. Once you followed the instructions ?

Did the same thing happen with EA2 or do you believe this to be new behavior?

There may be a misunderstanding. We investigated all Waves issues reported to us and they were are all crashes within the Waves plugins. I have passed on this information directly to Waves and they are actively investigating it. Please read this article on plugin compatibility. Just because a plugin doesn't crash in one DAW doesn't mean very much.

Please PM @msmcleod or @Jonathan Sasor with the project file that has this issue to allow us to investigate it.

This isn't an install related issue. It may be project specific. Since you are in touch with the company you can tell them that they can contact me if they need clarifications or assistance with anything.

Check your PM messages.

@Winstonhulley88 This is a plug-in crash so it would be something to report to the plugin vendor to fix. It looks like they are missing a pointer check in their code somewhere. The panic code sends a reset controllers sequence to the VST instruments. Perhaps this plugin is crashing on one of the CC resets. Unhandled exception at 0x000007FEB546B478 (Blade2.dll) in blade 2 test_10282020_183756.DMP: 0xC0000005: Access violation reading location 0x0000000000000008. This is the plugin info. If its a beta plugin you should obtain an updated version or contact the vendor about the crash and give them the same dump file. Blade2.dll *c:\beta test vst 64\Rob Papen\Blade2\Blade2.dll 1.00.0.0 10/26/2020 6:30 AM blade 2 test_10282020_183756.DMP EDIT: I just installed the trial version of Blade 2 and I don't get any crash when I press the panic button. So it may be specific to your project or the way you are using it. I suggest contacting the vendor.

@Winstonhulley88 please upload it to any file share like google drive or One drive etc and PM me the link. Also often zipping the file will make it much smaller.