Noel Borthwick

Download the latest installer from this link. We'll be officially releasing it soon.

I've specifically tweaked wasapi to work well with realtek. the main advantage of onboard audio codecs in wasapi is that unlike usb they support the windows 10 low latency wasapi support via IAudioClient3. This means that they will support latencies in shared mode that go down to less than 10 msec. I've had acceptable performance at 3msec buffers. Many consumer grade usb devices won't even go that's low. Of course if you already own a pro audio interface and it's convenient to use you wouldn't choose onboard audio. If you want to use a guitar or mic input portably guitar rig is a nice inexpensive solution and it does work even in wasapi shared mode, allowing you to record guitar while outputting from your onboard audio device in a laptop scenario. It's all about having choices.

Yes the issue has been fixed in the latest release candidate

Many thanks everyone for the stellar feedback to this EA release and helping us make it as stable as possible. We have fixed all the reported issues related to the new features. We also included a couple of small additions. Special callout to @Promidi @Maestro @Steve Harder for all the great feedback on articulation maps. Also @Toy who spent many hours helping us troubleshoot a complex intermittent problem with the arranger and articulation UI. Barring any further issues we should release the final version very soon.

@Frank De Baere and @Toy please check your PM's

Yes I already fixed that last night (after the build you got). In the next release you will not be able to choose a stereo or right channel - that was the problem.

@Frank De BaereWe have a potential fix for the menus not closing themselves. Ive never seen the menus stay after the app has closed. Are you sure that the application actually shut down? Check in task manager. Is this something you can reproduce reliably? If so we'd like you to test a build with the fix if possible.

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 ?