ASIO buffer size (please report back)

[themixtape]

Hi guys, Chris here (the RC video tutorial guy).

I was wondering if all of you could report back in this thread regarding ASIO latency/buffer size.

I was building a new computer for recording as mine's kind of on the slow side, so after I got my audio interface installed, I put a fresh copy of RC in (version 2.3, like in my videos). With an ASIO buffer size of 256, I experienced audio glitchiness in RC Standalone. Had to increase to 512 to remedy the problem. On my current studio computer, I can go as low as 64, with no issues whatsoever (even with a lot of RC tracks).

I remember this being a weird behavior back in 2012 when RC was very unstable. I don't remember how I fixed it, then.

Now here's a weird thing--

With RC as a VST... I can go as low as 64 in the new computer, with no issues whatsoever. It's a standalone issue.

So I would like you guys to report here, with what your ASIO latency/buffer settings are when you use RC in standalone mode, and what they are when you are inside your DAW.

Thanks!!!

[dsan@mail.com]

Chris,
I only use RC in stand alone so I hope my reply helps you.

Machine Specs:
Core 2 Quad Q9300@ 2.5 GHz 6Gb Ram x64

Sound Card:
Edirol FA-101 Firewire
ASIO Settings:
Buffer Size - Middle (between Min - High; does not indicate numeric size so I assume 512 - although if using default setting in RC it reports 660)
WDM: Normal
ASIO: Larger
Driver Version: 1.0.6

RC Settings:
Audio API: ASIO
Audio Device: Edirol FA-101
ASIO Channels: LineOut 1-2 (L&R)
SampleRate: Default (44100 Hz)
BufferSize: 2 msec

I am having no problems at this time; however, I do not use audio functions of RC. I mostly send midi over LAN to my host on a second computer and run VST's in my DAW.

For purpose of assisting you I opened a composition and changed the sounds to the default sf2's and played back. Did not have issues.

HTH and let me know if anything else I can do to assist you.

Happy Musiking!
dsan

[themixtape]

Thanks man! Yeah, would like to hear from everyone... For some reason, 256, 128, 64... all problematic. Problems instantly disappear at 512, on this new computer.

And-- it's tweaked/optimized for audio/music (I'm good at this stuff). Makes no sense...

-Chris

[dsan@mail.com]

I understand the theories behind buffer settings but I typically just go with the flow and accept whatever settings that work (within reason of course). I'm not doing live performance though so latency is not a big issue for me. A setting of 512 is within reason and widley accepted.

I realize why you would like it lower but is it causing you other problems at this setting?

Happy Musiking!
dsan

[themixtape]

Well like I said, it's not an issue with RC as a VST. I can go very, very low.

I like a low latency when creating custom phrases so I don't have to quantize so much.

512's definitely accepted, but I usually go 128 or 64, especially when I'm playing my digital drum kit, triggering Superior 2.0 (the drum sampling software). So 512's just too high for me. So I get used to immediate response from MIDI controllers... but again, it's great to have lower latency when inputting custom phrases.

[dsan@mail.com]

Yes, I kinda thought the live playing would be the issue. Have you run Latency Checker to see if something else could be the cause?

Good luck with this!

Happy Musiking!
dsan

[como baila]

Hi Chris ...

Love your videos ... they got me reconnected when I saw the Melody Generator one.

I'm sure you're pretty sophisticated with respect to the DAW-PC world, so I'll come at this from that level.

First the VSTi vs. standalone comparison doesn't really mean anything as in the first case it's your DAW interacting with the computer and brokering the demand. In the second case it's RC doing this.

I'm assuming you are talking about hosting the exact same VSTis in RC in your new setup as in your old one, right?

What it sounds like ... not to be too obvious, as from the example with your DAW you're able to go down to 64 samples, is that some how RC is not using the same interface.

Have you double checked to see whether it's using your ASIO drivers instead of some of the generic windows duplex? You probably have, but I thought that would be worth looking at ... as it most simply explains the difference between working standalone and working VSTi.

Assuming the CPU and RAM demands are unchanged between your old PC and new one with respect to the VSTis you are hosting in RC, this is a head scratcher.

Since I'm only using direct midi out with standalone to hardware, my results wouldn't be very meaningful.

I will say that when ever I was composing in RC standalone without access to a hardware module I simply used SoundFonts. I could then keep very low latency and not worry about the VSTi demands. When I had something I liked, I just exported the midi to my DAW.

I am biased, but I think using programs for their strong points makes the most sense. For me that means that RC is period, end of story a glorified and wonderful midi program. That's how I use it.

Como

[themixtape]

Standalone and RC as VST are both using the same exact audio interface and the same driver settings. Computer 1: no problems. Computer 2: can't go below 512.

It doesn't make any sense.

And yes, I agree about using the program as intended and to use Soundfonts, that's usually how I compose stuff, anyway (with soundfonts). But still...

That's why I was hoping everyone would report back with their ASIO driver settings, to see if anyone else experienced some weirdness.

Thanks!

[dsan@mail.com]

Chris, just my opinion, but I think you may have something else going on and RC is just responding with what it has availble.

There is a thread in computer set up that talks about SSD's and some issues relating. There is not alot of information but something there may be helpful.

Have you tried loading another DAW for comparison? So to be able to conclude it actually is RC?

Happy Musiking!
dsan

EDIT: I went looking for that thread but am unable to find it now. Sorry!

[themixtape]

Yes, as stated... when RC is a VST inside Reaper, there are no issues whatsoever, at 64 buffer (1ms latency, pretty much). So it's not the computer. That is the main post of this thread, to see what everyone else is doing/having/experiencing.

[como baila]

Standalone and RC as VST are both using the same exact audio interface and the same driver settings. Computer 1: no problems. Computer 2: can't go below 512.

It doesn't make any sense.

Thanks!

I don't mean to be anal ... but specifically, you are saying reaper hosts RC's VSTi perfectly on both Comp #1 and Comp #2, yes?

And, to put a fine point on it, I'd say it's not standalone and RC as VST using the same interface, it's standalone and reaper ... or whatever other host of the RC VSTi ... using the same interface. There is no connection between a VST or VSTi and an interface ... only between an audio program and an interface. They are just along for a ride on the host. Unless the VSTi or VST is run standalone and you are using virtual midi cables, that is.

Anyway, if on Comp #2 you have both RC standalone and Reaper with the same driver selected,the setups the same as before on Comp #1, both Comps have the identical Windows optimizations, and you are running the same version of RC standalone on both computers, I can't think of any explanation for your finding.

Lot of help that is, hunh?

Good luck.

[VariKusBrainZ]

Have you had a fiddle with any graphics settings/drivers to see if this has an effect?

Disabled wi/fi, internet, Virus checker and firewall?

[themixtape]

Did all that. Has to be something with the computer. I built another identical system and I can get down to 64 with RC standalone.

Definitely a computer thing. There's no wireless, not connected to internet, no anti-virus (not needed when you keep it offline).

No big deal. Problem solved, I guess.... damn computers

[como baila]

Plagarizing from the no longer politically correct: 'Computers ... can't live with 'em and can't live without 'em!'

[petearch]

Hi Chris, how did you solve this please? I was having some problems yesterday and even setting to 2048 didn't stop it, only deleting a track did it.