Extreme huge "hwoutfx" file (182Mb)

[Moy]

Hi I found that my reaper-hwoutfx.ini file became so huge, and I'm wondering does something goes wrong?

I opened the file and found VST3: Youlean Loudness Meter 2 (6ch) created 1,450,000 lines : (

[Dstruct]

Try with disabled "Save state as VST bank" for this plugin (rightclick in FX browser) ...

[MEMFIS_AKA]

Originally Posted by Dstruct

Try with disabled "Save state as VST bank" for this plugin (rightclick in FX browser) ...

No this is not helping. I got same thing with any monitoring plugins.

[Justin]

strange! have you seen this with any other plug-ins?

[MEMFIS_AKA]

Originally Posted by Justin

strange! have you seen this with any other plug-ins?

ANY plugins.

Plugins which do not open quickly, greatly slow down the launch of the Reaper if they are installed on the monitoring FX chain.

[Justin]

hmm no, I think that loudness meter is unique in that its state size grows with the history, it saves it to the .rpp. which is a separate issue from slowness you're describing

[MEMFIS_AKA]

Originally Posted by Justin

hmm no, I think that loudness meter is unique in that its state size grows with the history, it saves it to the .rpp. which is a separate issue from slowness you're describing

I don't use Youlean. There's a tone of better options out there.
I talk about my setup (Dsoniq Realphones + Izotope TB2 on the *Monitoring FX chain)

But any plugin added to MFXC* make hwoutfx.ini bloated with miles of code.

[Justin]

hmm any freely-downloadable FX I should test with?

[MEMFIS_AKA]

Originally Posted by Justin

hmm any freely-downloadable FX I should test with?

I try REA plugins, AIR (any easy to load plugins) it's fine (fast startup no white eye piecing windows while Reaper opens)

I describe all here:
https://forum.cockos.com/showthread.php?t=278535

https://forum.cockos.com/showthread.php?t=278542

[Justin]

Originally Posted by MEMFIS_AKA

I try REA plugins, AIR (any easy to load plugins) it's fine (fast startup no white eye piecing windows while Reaper opens)

I describe all here:
https://forum.cockos.com/showthread.php?t=278535

https://forum.cockos.com/showthread.php?t=278542

any freely available plug-ins that make it slow, I mean? post here.

[MEMFIS_AKA]

Originally Posted by Justin

any freely available plug-ins that make it slow, I mean? post here.

Really?
You want me to check all plugins out there?
I already said how to fix this long start-up.



This is why reaper so windows-ish and gypsy.
This type of approaches and workarounds.


BTW - "locked" tracks are not lock volume fader if you change level with the
"Xenakios/SWS: Nudge active take volume up\down" script.
This is ridiculous.

[Justin]

You're not being terribly helpful so I shall give you the same respect.

[MEMFIS_AKA]

Originally Posted by Justin

You're not being terribly helpful so I shall give you the same respect.

[Meo-Ada Mespotine]

Originally Posted by MEMFIS_AKA

[

BTW - "locked" tracks are not lock volume fader if you change level with the
"Xenakios/SWS: Nudge active take volume up\down" script.
This is ridiculous.

This is an issue with SWS so you should report it on their issues page.
It also has nothing to do with the issue in your opening post.

[MEMFIS_AKA]

Originally Posted by Meo-Ada Mespotine

This is an issue with SWS so you should report it on their issues page.
It also has nothing to do with the issue in your opening post.

[MEMFIS_AKA]

Originally Posted by TonE

Memfis seems to be an idiot. Sorry.

Your mom thinks different

[MEMFIS_AKA]

Originally Posted by Meo-Ada Mespotine

This is an issue with SWS so you should report it on their issues page.
It also has nothing to do with the issue in your opening post.

[MEMFIS_AKA]

"It's not the Reaper's problem, it's the SWS.
It's not us, you made it all up."

This is the reason for my attitude. Developers do anything but work on what users REALLY need.
Reaper users themselves are forced to look for the causes of bugs, and in the next update we get another useless "razor edits" and meaningless updates to video editing functions in Reaper. (thanks - we got Premiere, Resolve and a lot more programs to work with video)

Track "locking" it just another fail.


"lock track CONTROLS"(c)

Very visual file.
The option is useless, and performs purely decorative functions.
The degree of decorativeness is highly questionable.

Heaping up an already whole heap of previous problems and errors in the program. That no one will ever fix.
A typical Microsoft approach.



This is crazy frustrating.

[schwa]

Originally Posted by MEMFIS_AKA

But any plugin added to MFXC* make hwoutfx.dll bloated with miles of code.

What does this mean? I see you provided examples of plugins that do not have a problem, but can you provide an example of a plugin that causes reaper-hwoutfx.ini (not hwoutfx.dll) to become "bloated"? As far as I can tell the only example in this thread is the Youlean loudness meter which apparently stores its entire measurement history as plugin state.

If you can help us debug this specific issue, we can move forward, but otherwise I'll close the thread because it is not otherwise helpful.

[MEMFIS_AKA]

Originally Posted by schwa

What does this mean? I see you provided examples of plugins that do not have a problem, but can you provide an example of a plugin that causes reaper-hwoutfx.ini (not hwoutfx.dll) to become "bloated"? As far as I can tell the only example in this thread is the Youlean loudness meter which apparently stores its entire measurement history as plugin state.

If you can help us debug this specific issue, we can move forward, but otherwise I'll close the thread because it is not otherwise helpful.

hwoutfx.ini there's a mistyped (i write at late night) no hwoutfx.dll


I have troubles with Dsoniq Realphones, Izotope Tonal Balance and ANY plugin that loads up longer that Reaplugins does.

[schwa]

I downloaded the trial version of Realphones. With default settings, the plugin save/load size is only 2kB, and the state size is the same whether the plugin is inserted as track FX (in which case the state is stored in the .RPP file) or inserted as monitoring or FX (in which case the state is stored in reaper-hwoutfx.ini).

It's possible the state size is larger with different plugin settings, but in any case there is no reason to think that there is anything incorrect in reaper-hwoutfx.ini. If the plugin is inserted as monitoring FX, the plugin data (which is solely for the plugin's use, not REAPER's use) is stored in reaper-hwoutfx.ini. Some plugins store a lot of data. It's all fine.

With default settings, the Realphones plugin takes about 250ms to load its state and another 250ms to display its UI, for a total lag of a half second when initially loading and showing the plugin. The lag is the same whether inserted as monitoring FX or as track FX. A half second is a long time, but 100% of that time is spent in the plugin's own code, not in REAPER's code.

So the bottom line is, I am not able to observe any REAPER bug with respect to the reaper-hwoutfx.ini file, or with respect to loading monitoring FX.

[MEMFIS_AKA]

Originally Posted by schwa

So the bottom line is, I am not able to observe any REAPER bug with respect to the reaper-hwoutfx.ini file, or with respect to loading monitoring FX.

My main concern is about long startup.
It's not 250 ms it's seconds. Seconds with eye piercing empty white widows at startup.
Reaper on the SSD (Samsung EVO fast one) Windows on another SSD.
This is not my machine, i try on few other computers.

I post it here - but nobody even feedback there.
https://forum.cockos.com/showthread.php?t=278535



I don't have same problems with Realphones with other DAW if i for example open a project with Realphones inserted and saved.


This is REAPER thing. Same as odd screensets and windows behavior on startups. And not only me complaining this.