GSi VB3 question

[MikeCL]

Wow, what lousy interface (using terms like "rapid" instead of showing meaningful values).

First thing I find odd is that there's a 32 bit mode. Try changing it to 24 and see if it makes a difference. Audio is always 24 bit, there's no such thing as 32 bit digitizers. (It's probably referring to padding the data with an extra byte of nothing, which can help in some cases. But let's try it turned to 24 and see if that makes a difference.)

The other thing I see there is an Application Priority dropdown with "normal" selected. You might try turning that up to whatever the higher settings are.

Also I'm surprised you can make these changes on the fly. Usually you'd expect to need to restart the host after changing things like driver latency.

Does the popping still happen even when no instrument is loaded?

Oh wait, is this Absynth in standalone mode? Don't use it that way, use it plugged in to a proper host like Reaper. A lot of standalones don't work very well.

Yeah this is not the best looking interface I've seen :-/

32 bit is the only one that's clickable, the rest are greyed out.

I did have it set to high but I guess the settings did not stick, also it happens regardless if a instrument is loaded or not.

I can try it in reaper but I don't have much high hopes that it's going to work any better.

[AdmiralQuality]

Wow, what lousy interface (using terms like "rapid" instead of showing meaningful values).

First thing I find odd is that there's a 32 bit mode. Try changing it to 24 and see if it makes a difference. Audio is always 24 bit, there's no such thing as 32 bit digitizers. (It's probably referring to padding the data with an extra byte of nothing, which can help in some cases. But let's try it turned to 24 and see if that makes a difference.)

The other thing I see there is an Application Priority dropdown with "normal" selected. You might try turning that up to whatever the higher settings are.

Also I'm surprised you can make these changes on the fly. Usually you'd expect to need to restart the host after changing things like driver latency.

Does the popping still happen even when no instrument is loaded?

Oh wait, is this Absynth in standalone mode? Don't use it that way, use it plugged in to a proper host like Reaper. A lot of standalones don't work very well.

Yeah this is not the best looking interface I've seen :-/

32 bit is the only one that's clickable, the rest are greyed out.

That's really weird.

I did have it set to high but I guess the settings did not stick, also it happens regardless if a instrument is loaded or not.

I can try it in reaper but I don't have much high hopes that it's going to work any better.

I do. Those standalone shells aren't very good. And then we can isolate the problem from the instrument.

[MikeCL]

Jesus I moved it up to rapid and closed reaper to restart it and I can already hear the sound again before restarting it again..

I just loaded it again and no dice same as the stand-alone

But testing right now I noticed if I set the behringer control bad to fast but change the setting in reaper to the WDM streaming and set my samples to 80 then I get 6 ms, I assume that's total?

*edit moved it down to 64 samples it's ok so far but I need to hook the keyboard up some sounds can cause buzzing if they are layered.

[AdmiralQuality]

Jesus I moved it up to rapid and closed reaper to restart it and I can already hear the sound again before restarting it again..

So it has nothing to do with the host app or standalone instrument!

What's really strange is that setting your ASIO driver to low latency is causing clicking even when nothing is USING ASIO! Weird!

I just loaded it again and no dice same as the stand-alone

But testing right now I noticed if I set the behringer control bad to fast but change the setting in reaper to the WDM streaming and set my samples to 80 then I get 6 ms, I assume that's total?

This is why I recommended trying WDM in Reaper. It works quite well, and many devices that aren't "semi-pro" audio devices probably have better Windows drivers than ASIO, which typically only used by us music types and therefore gets less testing, bug reports, etc.

80 is a bit of a weird number but if it works. How many buffers? (My Edirol UA-1000 works in Reaper in WDM at 1 buffer x 64 samples!)

[MikeCL]

I think you saw before the edit but I was able to go down to 64 samples so far with 4 buffers so that gives me 5 ms.

So the issues I'm having with the ASIO is due to the device and not anything else? I had the same issues on a fresh formatted computer.

[MikeCL]

wow

I have 1 buffer X 64 samples and it's playable at 1ms

[AdmiralQuality]

I think you saw before the edit but I was able to go down to 64 samples so far with 4 buffers so that gives me 5 ms.

Try 2 or even 1 buffer. Won't hurt, put it back if it doesn't perform well or crashes the host or something.

So the issues I'm having with the ASIO is due to the device and not anything else? I had the same issues on a fresh formatted computer.

I can't be sure from here. But I think your issue is Beheringer living up to their well earned reputation. Focusrite is a MUCH better brand. That Beheringer doesn't even have 1/4" jacks! It's more for joe-consumers rather than cool musicians like us.

[AdmiralQuality]

wow

I have 1 buffer X 64 samples and it's playable at 1ms

Sweet! Reaper FTW!

Enjoy!

[MikeCL]

I think you saw before the edit but I was able to go down to 64 samples so far with 4 buffers so that gives me 5 ms.

Try 2 or even 1 buffer. Won't hurt, put it back if it doesn't perform well or crashes the host or something.

So the issues I'm having with the ASIO is due to the device and not anything else? I had the same issues on a fresh formatted computer.

I can't be sure from here. But I think your issue is Beheringer living up to their well earned reputation. Focusrite is a MUCH better brand. That Beheringer doesn't even have 1/4" jacks! It's more for joe-consumers rather than cool musicians like us.

I might have to go back to 2 buffers, I can run 1 but doing something like moving something around in reaper will cause a bunch of sounds I don't want.

At least I found a way to get down under 18 ms!

I really wanted the focusrite from the beginning but I was pressed for cash and I had just finished completing this build, I wont make that mistake again

[MikeCL]

wow

I have 1 buffer X 64 samples and it's playable at 1ms

Sweet! Reaper FTW!

Enjoy!

hey one question I'm thinking about building a midi switch to control the Leslie speed but if I remember right anything under 50 is slow and anything above that is fast and 50 is off?

If the velocity is just 1 & 127 then I would just have slow and fast right?

[AdmiralQuality]

wow

I have 1 buffer X 64 samples and it's playable at 1ms

Sweet! Reaper FTW!

Enjoy!

hey one question I'm thinking about building a midi switch to control the Leslie speed but if I remember right anything under 50 is slow and anything above that is fast and 50 is off?

If the velocity is just 1 & 127 then I would just have slow and fast right?

You're confusing your terms.

MIDI "control change" (CC) messages always range between 0 and 127.

Velocity is the speed you hit a key (with a range of 1 to 127) and is per-note, not used to control the Leslie speed.

VB3 has a 3 different modes for the Leslie speed control.

1. You can set it to toggle between fast and slow any time the value goes above 0 (as would work with an instantaneous button like the mod switch on Rolands, or a switch pedal like a damper pedal),

2. Or you can set it to follow the setting of the controller (as you would for a mod wheel that stays where you leave it). In this case any value below the 1/3 position (42?) would be slow, between 42 and 84 would be stop, and above 84 would be fast.

3. You can set it to use two controllers, one for stop and one for slow/fast. (Which is how I'm using it with my CX-3).

Read the addendum pdf for version 1.4 for more details on that third mode. You need to edit the .ini file if you want to change the CC#s of the two controllers.

[rockstar_not]

First of all, VB3 is one of the plugins in my list of 10 must have's - Guido is a coding master.

Second, I read most of the posts in the first several and last several thread and this one made me snort:

"I wouldn't take this rig into church though for fear of offending God with the tangle of snakelike patch cables. Also, it's got no backboard like a C3 so the congregation can see up my skirt. Wink"

Third, 18 mS latency for live playing simply is awful. Also try Savihost or other Hermann Seib wonders, but Savihost likely is all that you would need. Don't have to use reaper's donationware mode or anything like that.

Give it a run with VB3, I think you'll like it. http://www.hermannseib.com/english/savihost.htm

Lastly - I just bought a Casio XW-P1 a few months ago partially for the drawbar organ emulator and because I can't afford even a used Nord Electro II, but VB3 runs circles around it for overdrive and leslie simulation.

Carry on...

[MikeCL]

Well I found out thanks to AdmiralQuality that I could get 1ms when switching to WDM in reaper, so 18 ms would no longer be an issue.

[MikeCL]

wow

I have 1 buffer X 64 samples and it's playable at 1ms

Sweet! Reaper FTW!

Enjoy!

hey one question I'm thinking about building a midi switch to control the Leslie speed but if I remember right anything under 50 is slow and anything above that is fast and 50 is off?

If the velocity is just 1 & 127 then I would just have slow and fast right?

You're confusing your terms.

MIDI "control change" (CC) messages always range between 0 and 127.

Velocity is the speed you hit a key (with a range of 1 to 127) and is per-note, not used to control the Leslie speed.

VB3 has a 3 different modes for the Leslie speed control.

1. You can set it to toggle between fast and slow any time the value goes above 0 (as would work with an instantaneous button like the mod switch on Rolands, or a switch pedal like a damper pedal),

2. Or you can set it to follow the setting of the controller (as you would for a mod wheel that stays where you leave it). In this case any value below the 1/3 position (42?) would be slow, between 42 and 84 would be stop, and above 84 would be fast.

3. You can set it to use two controllers, one for stop and one for slow/fast. (Which is how I'm using it with my CX-3).

Read the addendum pdf for version 1.4 for more details on that third mode. You need to edit the .ini file if you want to change the CC#s of the two controllers.

Ahh got it, looks like that stuff I would have to program in a sysex message, it's crazy how expensive a used or new switch is.. Upwards of like $80..

A SWITCH!!! I have at least 4 months to work on stuff (plus buying more gear) so at least it's not like the last time where I only had a few weeks.

[AdmiralQuality]

wow

I have 1 buffer X 64 samples and it's playable at 1ms

Sweet! Reaper FTW!

Enjoy!

hey one question I'm thinking about building a midi switch to control the Leslie speed but if I remember right anything under 50 is slow and anything above that is fast and 50 is off?

If the velocity is just 1 & 127 then I would just have slow and fast right?

You're confusing your terms.

MIDI "control change" (CC) messages always range between 0 and 127.

Velocity is the speed you hit a key (with a range of 1 to 127) and is per-note, not used to control the Leslie speed.

VB3 has a 3 different modes for the Leslie speed control.

1. You can set it to toggle between fast and slow any time the value goes above 0 (as would work with an instantaneous button like the mod switch on Rolands, or a switch pedal like a damper pedal),

2. Or you can set it to follow the setting of the controller (as you would for a mod wheel that stays where you leave it). In this case any value below the 1/3 position (42?) would be slow, between 42 and 84 would be stop, and above 84 would be fast.

3. You can set it to use two controllers, one for stop and one for slow/fast. (Which is how I'm using it with my CX-3).

Read the addendum pdf for version 1.4 for more details on that third mode. You need to edit the .ini file if you want to change the CC#s of the two controllers.

Ahh got it, looks like that stuff I would have to program in a sysex message, it's crazy how expensive a used or new switch is.. Upwards of like $80..

A SWITCH!!! I have at least 4 months to work on stuff (plus buying more gear) so at least it's not like the last time where I only had a few weeks.

Not "sysex". (That means arbitrary vendor specific messages sent through MIDI. Devices from different manufacturers don't typically understand the same sysex messages, though you can often record them and play them back with a sequencer to dump/restore settings from many devices.)

So your controller probably has a sustain pedal input on the back. You can map that to the Leslie speed in VB3. But yes, you still need a pedal. (Which, yes, is just a switch inside. Though in a robust package that can take lots of pounding with a foot.)

Damper pedals aren't THAT much... http://www.musiciansfriend.com/accessor ... mper-pedal