KVR Audio

Architeuthis · Post by **Architeuthis** » Tue Jun 13, 2006 1:47 pm

Yeah, GSnap, you know: http://www.gvst.co.uk/gsnap.htm Gsnap?

jupiter8 · Post by **jupiter8** » Tue Jun 13, 2006 1:49 pm

'Cause touching the volume fader is such a bitchass project.

BobYordan · Post by **BobYordan** » Tue Jun 13, 2006 1:52 pm

Architeuthis wrote:

Yeah, GSnap, you know: http://www.gvst.co.uk/gsnap.htm Gsnap?

That looks hot.

Architeuthis · Post by **Architeuthis** » Tue Jun 13, 2006 2:06 pm

oh lol. just imagine that EXACT same picture except with the fader at 0. Sorry, I thought I took a pic of that. Musta... i dunno. Whatever. Just use your imagination. I don't care to go through the process of recreating it just to take a corrected pic.

If you didn't understand what I just said, the pic was taken when there was no sound being produced. Moving the fader up or down does nothing. Stopping the audio does nothing. It's an error in the VST's audio.

jupiter8 · Post by **jupiter8** » Tue Jun 13, 2006 2:07 pm

So what is the problem ? The output of GSnap is really high ? Or what ?

Architeuthis · Post by **Architeuthis** » Tue Jun 13, 2006 2:08 pm

jupiter8 wrote:So what is the problem ? The output of GSnap is really high ? Or what ?

No, it essentially "becomes broked" and doesn't work anymore, leaving me with a never-ending clipping signal. Let me reiterate there's no sound being produced when this happenes.

bleebsen · Post by **bleebsen** » Tue Jun 13, 2006 2:44 pm

I've had that too, with unstable freeware plugins.. but Gsnap itself wouldn't do this over here. Sometimes it's only happening when certain other plugins are loaded, or multiple instances of one. Can you really reduce this effect to one instance of Gsnap only?

Architeuthis · Post by **Architeuthis** » Tue Jun 13, 2006 2:48 pm

uhh, is it because the audio isn't technically mono? it's recorded by a single mic though.

Lunch Money · Post by **Lunch Money** » Tue Jun 13, 2006 4:02 pm

bleebsen wrote:I've had that too, with unstable freeware

I've had it happen, too-- with commercial products. A price tag doesn't eliminate stability issues.

Greg

gy · Post by gy » Tue Jun 13, 2006 8:15 pm

Hi Architeuthis. If you can give me some steps to recreate this, then I'll be happy to investigate. I use SX myself and haven't encountered anything like you describe.

Moseph · Post by **Moseph** » Tue Jun 13, 2006 8:35 pm

I had a similar issue when I tried it out using Plogue Bidule, because it looked like a stereo in and was in fact Mono. The other input was a digital word clock or something.

Make sure you're only connecting it with a mono input and if you're using a modular host (sorry, don't recognize the host from the pic) make sure you're using the correct input only. That's what fixed it for me.

gy · Post by gy » Tue Jun 13, 2006 9:07 pm

I think that's an old issue that has since been fixed, but I'll double-check.

Have you got the latest version, Architeuthis?

<edit> Incidentally, GSnap works on mono or stereo tracks now. For stereo tracks the signal is collapsed to mono internally before processing. (GSnap used to be mono only - the bug Moseph described was caused by GSnap reporting itself as stereo incorrectly).

Manc Chris · Post by **Manc Chris** » Tue Jun 13, 2006 9:37 pm

Architeuthis wrote:"becomes broked"

Name of my new album. For sure.

Peel · Post by **Peel** » Wed Jun 14, 2006 9:19 am

I see you're using SX. Go into Devices > Plug in Information, find GSnap and check the "old host behaviour" box. That usually fixes the problem for me (although I haven't had it with GSnap specifically, just with a handful of other plugs)

Architeuthis · Post by **Architeuthis** » Wed Jun 14, 2006 9:45 am

ill try that. i would have done some further testing, but im rigorously testing eXT2 right now.

Anything like GSnap (pitch quantizer) but doesn't do.. this?