Valhalladsp Plugins on 32 bit

[Jamie A]

I want to run Valhalladsp plug-ins on my Windows XP machine if possible.

Is there a way to do this that is easy and stable?

Huge thanks to anyone who has done this and can give me a step by step. Huge thanks to anyone who has tried this and will tell me not to mess with it because it is a pain in the a

[cgrafx]

I want to run Valhalladsp plug-ins on my Windows XP machine if possible.

Is there a way to do this that is easy and stable?

Huge thanks to anyone who has done this and can give me a step by step. Huge thanks to anyone who has tried this and will tell me not to mess with it because it is a pain in the a

You would have to get 32-bit versions of the plug-ins which are no longer available so your options are

1. upgrade to Saw Studio 64 which will work with the currently available 64-bit versions of Valhalladsp plugins
2. try chainer or other VST plugin host tool and see if the plugins will work using that.

[Jamie A]

Thank you for chiming in. I downloaded the 64demo with the plug-ins I wanted and they popped right up and worked.

Upgrading to SAWStudio 64 is a no brainer and keeps me playing with mixing instead of screwing with computers!

thank you!

[mr_es335]

Jamie,

Firstly "Welcome to the Forum!"

Please search the forums for topics pertaining to "JUCE" and JUCE development [Click_Me]

JUCE plug-ins DO NOT WORK very well in SAW or SAC!!

In the end, save your money and invest in non-JUCE development software...such as FabFilter.
* These plug-ins are absolutely excellent!!

Any-and-all questions that you WILL HAVE, are dealt with in those texts.

PS: Please understand that the reason that JUCE-based plug-ins do work in SAW or SAC - have nothing at all to do with SAW or SAC - but with the development platform itself.
* From MY perspective - with many, many, MANY hours of testing and re-testing, this anomaly has shown to be true!!

My earnest suggesting is, that BEFORE obtaining any third-party software for employment in RML Labs software, that such third-party software be VERIFIED beforehand.

Anything else, please let me know.

[jmh]

Dell, what issues have you observed - are they with SAC or live mode or 64 bit? I have 2 of their plugins, one free and the other paid, in use in several edls, and I haven't noticed any particular problems.

I pretty much use 32 bit saw for everything, as my type of projects don't benefit from 64, and there are a couple of native plugins which I like to use.

...that said, the valhalla plugin is not so superior that I would reach for it all the time, then again I use the FabFilter reverb and I find that while it is pretty decent, it looks even better than it sounds - and I would prefer the other way around. Also, I bought it a year or so ago, and not that long afterward, they came out with a new version with a upgrade price that was significant, which rubs me the wrong way.

[cgrafx]

I believe the juice problems are really a scenes related issue. The plug-ins seem to work fine otherwise.

[Jamie A]

Thanks for the continued info.

My biggest hurdle at this point in time is the rml store doesn***8217;t let me purchase stuff. I***8217;ve tried several different browsers hoping that was the issue but it wasn***8217;t.

[mr_es335]

Jamie,

For the purchasing issues, I would suggest contacting Bob directly.

Regarding FabFilter, what version of R-2 are you employing?
* I am currently employing v2.0 - with v2.04 being the most current iteration.

I have developed some more-than-acceptable presets with R-2 - easily on par with Valhalla.

Lastly, I sincerely believe that anyone employing any RML Labs software, cannot afford to have what I would refer to as "quirky" software!
* Also, Valhalla was NOT AT ALL interested in my findings...and as noted, after spending hundreds of dollars their various plug-ins, they showed absolutely NO INTEREST AT ALL in even the smallest attempt at a possible resolve. Very,m very disappointing indeed!

On the other-hand, Ralph at FabFilter has always been more that helpful with any issues that I have had...involving mostly personal "ID-10-T" issues!

PS: I just tested-out the store, and all was working on my end!!

[Macay]

I had to make my purchase as guest, since the store didn

[Macay]

I had to make my purchase as guest, since the store did not work for me when using my account.

[Todd R]

Jamie,
JUCE plug-ins DO NOT WORK very well in SAW or SAC!!

In the end, save your money and invest in non-JUCE development software...such as FabFilter.
* These plug-ins are absolutely excellent!!

Any-and-all questions that you WILL HAVE, are dealt with in those texts.

PS: Please understand that the reason that JUCE-based plug-ins do work in SAW or SAC - have nothing at all to do with SAW or SAC - but with the development platform itself.
* From MY perspective - with any, many, MANY hours of testing and re-testing, this anomaly has shown to be true!!

My earnest suggesting is, that BEFORE obtaining any third-party software for employment in RML Labs software, that such third-party software be VERIFIED beforehand.

OK, I will just chime in and agree with Dell here and say I have had to completely abandon any JUCE based VSTs in SAW.
I have several years worth (over a decade, actually) of Acon Digital Restoration Suite work across all my SAW jobs. Acon's move to JUCE has forced me to stop using Acon VSTs altogether. My issue has been real time rendering of the VST UIs and parameter freezes. It is possible to render jobs with JUCE plugins (I performed several large renders of that type last week), but editing work with Acon VSTs in SAW is a no go for me nowadays.

Further, I have tried using MetaPlugin to see if another wrapper might solve my Acon issues, but the Acon plugs still fail in SAW.

I have moved to SpectraLayers for all my NR requirements and getting a much better end result, altho quite a bit more time consuming with manual, bounce-based workflow.

Fab Filter VSTs are a mainstay for me, as well.

I will also say I've been using 64 bit SAW since around 2020 and haven't done and 32 bit SAW editing since before then.

[mr_es335]

Todd,

Todd..."Well spoken!"

In particular...

1) "My issue has been real time rendering of the VST UIs and parameter freezes. It is possible to render jobs with JUCE plug-ins (I performed several large renders of that type last week), but editing work with Acon VSTs in SAW is a no go for me nowadays."
* Regarding the " ...real time rendering of the VST UIs and parameter freezes..." Have you eve asked yourself as to "Why?" this is the case? To begin with, though my initial issues were indeed, as Philip as noted, with the UI "locking up" when employing scenes, there are much more nefarious "things' going on in the background. One "other" developer, whom I have also spent literally hundreds of dollars - and the equal number of hours in writing documentation on their product, when I made them aware of my issues, all that I received back in return was 1) "silence", and 2) the all-too-common response, "Well no one else has had any similar issues, so the problem must be with the host!"

This reply took me down a path I was hoping NOT to have to tread on...and of which I feel I am not able to speak of for fear of being misunderstood (...and this position is based on experience). All that I am ABLE to state at the moment is, is that what I did see is great DSP...over-top of an absolutely horrible GUI. That, is as they say, "It!"

2) You them stated, "Further, I have tried using MetaPlugin to see if another wrapper might solve my Acon issues, but the Acon plugs still fail in SAW."
* If JUCE is your heart, then you need to have a heart transplant! Join the JUCE Forum, as I did, have a look at some of the same "efforts" provided by others and you will soon discover what I did. This is precisely why I equate JUCE with "Synthedit". "Remember "GIGO?"

3) "Fab Filter VSTs are a mainstay for me, as well."
* As I have noted, Ralph the owner of JUCE, told me specifically that JUCE is a path he is not willing to go down! Thus, he will stay with what "works" - and this is "...all in house development".

Thanks again Todd for your very insightful response. Appreciated!

[Todd R]

" Have you eve asked yourself as to "Why?" this is the case? To begin with, though my initial issues were indeed, as Philip as noted, with the UI "locking up" when employing scenes, there are much more nefarious "things' going on in the background.

I didn't...I was too embroiled with continuing the audio work...I did have numerous multiple instances of the same plugs in my big film job I'm still working on...turning them off and getting them out of my SAW job was indeed helpful. I did ask Stian at Acon, and, yeah, we a a minority in the DAW world.

If JUCE is your heart, then you need to have a heart transplant! Join the JUCE Forum, as I did, have a look at some of the same "efforts" provided by others and you will soon discover what I did. This is precisely why I equate JUCE with "Synthedit". "Remember "GIGO?"

I don't know about "Synthedit" or "GIGO" :-) I will look them up

**EDIT**
oh, ok, lincoln logs and the old acronym...yes I know of GIGO

[mr_es335]

Todd,

Yes...GIGO..."Garbage In...Garbage Out!"

SynthEdit is a "development platform"...akin to JUCE, Ruby On Rails, MAX/MSP and FlowStone!

You basically build the GUI, add your own DSP code, or obtain either the GUI code DSP code from others.

I reworked an offering for a 4-channel wave file player plug-in [free-ware], that I had stripped down to a single channel plug-in called "SAC Wave File Player".
* At the time SynthEdit was still in the developmental stages for 64-bit...and thus, I never updated that plug-in.
* However, as I am NOT a DSP developer, the original plug-in was "buggy"...thus, my plug-in would, as a result, inherit those very same "bugs".
* Thus, my second reason for not moving forward with the 64-bit version of SynthEdit!
* This very same "anomaly" I witness over-and-over-again in the JUCE forum - wherein, one would adopt someone else's code - reworking the GUI for themselves, and then offering that "update" to others...often without any mention of where they obtained the original code!