OT: JUCE!

[operationwhat]

Sorry to intrude the thread but can anyone tell me why do plugin alteration,
like knob movement effect the sound when SAC engine is supposed to force
audio to one core only and the rest should be on the other?

WHY???

Just did a show and put Nomad BlueTubes in SAC a low CPU plugin compressor
and SAC started to drop out like hell!!!!!!

And I mixed with 7.4 protools 15years ago with 2x32 without any dropouts + triggers + 1176 + 15ch live monitorng?!
How come?
------------------------
Anyway there's a not so new (2016) software mixer out there for Mac that does some similar thing like SAC Loudlab / SoundDesk
that reminds me of waves rack but much better!
Anyone ever worked with it? Any experience????

[Bob L]

Make sure that the SAC startup icon is set to "Run As Administrator" and that the SAC option to force realtime priority is checked... see if that makes a difference.

Bob L

[mr_es335]

Good day,

A very important update!!

At the recommendation of one of the developers, I spent a few hours learning my way around "Reaper" and to my surprise, I discovered that Reaper was experiencing very similar anomalies as that of SAC!
* I cannot state that these anomalies are identical, but GUI stalls occurs with both hosts! Interesting!

Within a Reaper project, you have the ability to save a plug-in "preset". Again, this ability is within the project...thus, within the application.
* Thus, I saved two presets. Then toggling between the two, the UI stalls..thought the "effect" of that changes is observed...and heard! Thus, the UI itself, stalls.

Again, "When you have eliminated the impossible, what is left, no matter how unlikely, is the truth."

[mr_es335]

Good day,

As an update, JUCE v8 has just been released!

More specifically, JUCE was previously acquired by PACE back in 2020 - which, having been rather dormant since that acquisition, in this latest release, it would appear that some form of "licensing" will become more pervasive.

What this new licensing scheme will actually be comprised of - is yet to be seen!

More importantly, for us Vst2 folk - v8 has apparently revised their Vst2 implementation. Whatever this new implementation is, of the three v8, Vst2 plug-ins that were sent to me for testing, none of these plug-ins worked in either SAC or SAW. Thus, we may be witnessing the end of Vst2 implementation in JUCE - and which honestly, is to be expected!

Am I at all concerned? In short, "Nope!" My reasoning, "More often than not...more is just that, more!"

I hope this information will be of some practicable use?

[mr_es335]

Good day,

Just-for-interest, have a peep at this: [Click_Me]

"Learning how to create audio plugins (VST3, AU, AAX, for digital audio workstations (Ableton Live, Steinberg Cubase, is difficult.
Not anymore.
Join the free audio plugin development course with JUCE to create your first plugin easily, even if you aren't a programmer or a DSP engineer."

Personally, I find the above offensive! Talking with one developer, he literally told me that though he knows the "math" behind his software, he knows absolutely nothing about actual programming!!

So, I asked the question, "What if I have a problem with the actual program then?" I was told, "Go to he JUCE forum!"

However, if the developer has moved much, if not most, of his developmental platform over to JUCE, then that code is protected by them, and we then have to wait for them to troubleshoot and fix the issue.

Not a great place to be in!!

[Peter O]

Good day,

Just-for-interest, have a peep at this: [Click_Me]

"Learning how to create audio plugins (VST3, AU, AAX, ***823;) for digital audio workstations (Ableton Live, Steinberg Cubase, ***823;) is difficult.
Not anymore.
Join the free audio plugin development course with JUCE to create your first plugin easily, even if you aren***8217;t a programmer or a DSP engineer."

Personally, I find the above offensive! Talking with one developer, he literally told me that though he knows the "math" behind his software, he knows absolutely nothing about actual programming!!

So, I asked the question, "What if I have a problem with the actual program then?" I was told, "Go to he JUCE forum!"

However, if the developer has moved much, if not most, of his developmental platform over to JUCE, then that code is protected by them, and we then have to wait for them to troubleshoot and fix the issue.

Not a great place to be in!!

I'm currently following the course and believe me you have to be a pretty proficient C++ programmer to write a plugin that uses Juce. My own C++ skills are a bit rusty and I'm struggling :-)
There are ways to build plugins without writing (much) code (VISE, Max MSP) but if you just use the Juce framework you need to know C++

[mr_es335]

Peter,

You noted, "......but if you just use the Juce framework you need to know C++"
My response: This I noted when I first began dialoging with JUCE.
* I did work in C+ many years ago, but one of my sons [Joshua] is a very proficient C++ programmer. He looked into JUCE and made the very same observations.
* So, what is up with the "hype" about not even having to be a programmer?
* Regardless, JUCE is a "framework" and if the framework has issues - then, at least to me, all other issues are downstream.

At the end of the day, I find it simply not worth the hassle of troubleshooting others issues. Thus, I tend to prefer to purchase products from those that develop such products "in house".

PS: During my "programming days", one author in particular I found very, very helpful was Greg M. Perry! Link

[Ruben VS]

Peter,

You noted, "......but if you just use the Juce framework you need to know C++"
My response: This I noted when I first began dialoging with JUCE.
* I did work in C+ many years ago, but one of my sons [Joshua] is a very proficient C++ programmer. He looked into JUCE and made the very same observations.
* So, when the "hype" about not even being a programmer.
* Regardless, JUCE is a "framework" and if the framework has issues - then, at least to me, all other issues are downstream.

At the end of the day, I find it simply not worth the hassle of troubleshooting others issues. Thus, I tend to prefer to purchase products from those that develop such products "in house".

PS: During my "programming days", one author in particular I found very, very helpful was Greg M. Perry! Link

I find it very strange that those plugins work fine everywhere except in SAC. There's some incompatibility between them (although we don't know what it is).

A novice might create a bad plugin using Juce, but a company that has been in this business for 30 years will use Juce and create a good plugin that works well, and in fact, works well everywhere.

On the other hand, if it were a Juce error, it would have been fixed during the updates, but no one else is reporting the error, only SAC users.

The conclusion is that there is an incompatibility between the two, SAC and JUCE. Although we don't know what it is.

[mr_es335]

Rueben,

Did you not read post #10 and #23? I suggest that you do so...so I can avoid having to repeat myself here?

You stated #1: A novice might create a bad plugin using Juce, but a company that has been in this business for 30 years will use Juce and create a good plugin that works well, and in fact, works well everywhere.
* See Post #23 and Reaper!

You stated #2: On the other hand, if it were a Juce error, it would have been fixed during the updates, but no one else is reporting the error, only SAC users.
* See Post #10
* As SAC appears to be the ONLY application that is exhibiting such issues, most developers employing JUCE will not be looking into this matter further.

At present I am having my son Joshua, write a simple wave player plug-in for me entirely in C++!
* There are number of C++ forums that provide "routines" for a number of the functions that will be implemented in this plug-in.
* At present, he will only be implementing the VST2 SDK's.

PS: Do NOT hold your breath on this one! This is a "pipe dream" for the present!

Update!
I got the idea to perform a search entitled, "JUCE and GUI plug-in stalls", and I came up with the following 6...[there are many others as well]:

[Click_Me 1]
[Click_Me 2]
[Click_Me 3]
[Click_Me 4]
[Click_Me_5] ProTools
[Click_Me_6] Reaper

Check the posting dates as well! Interesting!

PS: After doing some more "digging"...there are indeed quite a number of issue with JUCE-based plugins!