Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Joe Bloggs]

Hi, first time user here.  I was attracted to MC by its native VST support.  Unfortunately, the core VST plugin I use, Electri-Q, doesn't appear to support 64bit processing.  My question is, is it possible to step down the internal processing to 32bits for plugin compatibility in any version of MC?  ?

[mojave]

You won't have any problem using Electri-Q, although you can use JRiver's own PEQ and accomplish the same thing.

From Matt in an old thread:

VST plugins use 64bit when available and fall back to 32bit if the VST does not support 64bit.

[Joe Bloggs]

I wish that were true?
Right now I'm playing songs, in the DSP panel it shows Internal processing at 44.1kHz 64bit 2ch and it says "output format not supported" under Electri-Q when stuff is playing?

[mojave]

I just tried it and am seeing the same thing as you. I couldn't get it to work with Version 17 either.  ? I wonder if something has changed. I do have another 32bit VST plugin that do work fine so I'm not certain it is a 64bit issue.

[Matt]

It's returning 1 from effSetSampleRate, which we interpret to mean it doesn't support the sample rate.

I tested 44.1 and 96 kHz.

I think we're handling this correctly:
http://www.asseca.com/vst-24-specs/efSetSampleRate.html

[Joe Bloggs]

I think it's safe to say that Electri-Q does support at least one out of those two samplerates 

I've never had this problem with any other VST host...

Is there some kind of developer setting switch to override this?

[Matt]

Is there some kind of developer setting switch to override this?

Not currently.

Would you be willing to ask the Aixcoustic guys?  Maybe they have a good reason to return 1, but my understanding is that it's an error code.  This isn't common with other effects.

Feel free to give them my contact details (matt at jriver) if they want to talk technicals.

[Joe Bloggs]

I'm using their freeware edition which hasn't been updated in years.  If they do fix the bug it'll probably be only in the payware version.  For all I know it's long since been fixed (unless you happen to have been testing the paid version).  For all I know this bug happened because this plugin was written for an older VST standard?

Maybe it's time for me to look elsewhere for a VST EQ--but I've worked with this program for a long time and have lots of presets calibrated to my audio hardware I'd want to use.

If you guys add an option switch to "ignore VST error codes" that could potentially have much wider applications than making this one plugin work?

[Matt]

If you guys add an option switch to "ignore VST error codes" that could potentially have much wider applications than making this one plugin work?

This is the first plugin I've seen with this issue.  And if we ignore the error, it could lead to the reverse problem (crashes, etc. because we ignore a problem).

Have you tried the 'Parametric Equalizer' built into Media Center?

[Joe Bloggs]

Not really.  My "workflow" highly depends on having a VST parametric equalizer I can use chain two of together in another VST host, and that displays the final EQ curve graphically (that I can then flip upside down to produce a FR curve of sorts)
http://www.head-fi.org/t/633102/budget-iems-review-not-so-budget-review-hifiman-re0-posted

I suppose there are plenty of VST parametric EQs with graphic display but this is the only free one I know of.

I'm willing to run that crash risk  It could be a hidden developer option with warnings

In the meantime I guess MC is not for me yet--if I uninstall it now will the 30-day evaluation counter continue to run?

[Joe Bloggs]

In the meantime I guess MC is not for me yet--if I uninstall it now will the 30-day evaluation counter continue to run?

[JimH]

The trial will end 30 days from the day it was installed.