BE CAREFUL IF YOU OPEN THE LATEST DEV VERSION (330)

Jae.Thomas · 03-31-2021, 07:10 AM

you might just blow your damned speakers.

The latest version does something to reeq to break the GUI, and cause a massive, constant, white noise burst.

Jae.Thomas · 03-31-2021, 07:23 AM

only broken in 330. plugin is embedded in GUI

switched back and forth from 330 to 323, consistently fucking up bad

karbomusic · 03-31-2021, 07:39 AM

Did you disable your auto-mute settings?

schwa · 03-31-2021, 07:41 AM

Can you please be more specific or ideally provide some way to reproduce?

Justin · 03-31-2021, 08:08 AM

Yes, what OS and arch? thanks!

Jae.Thomas · 03-31-2021, 08:09 AM

Quote:

Originally Posted by schwa

Can you please be more specific or ideally provide some way to reproduce?

I will upload the file it first happened on, and then my default template, which it also happened on:

https://www.dropbox.com/s/jrupzb6f84...0.mp3.RPP?dl=1

Jae.Thomas · 03-31-2021, 08:10 AM

Quote:

Originally Posted by Justin

Yes, what OS and arch? thanks!

sorry, yes. Win10, latest, x64

sorry, the shock of the situation kinda blunted my abilities to post specifically haha

better than coffee tho hahahaahh

Jae.Thomas · 03-31-2021, 08:13 AM

my default template:

https://www.dropbox.com/t/wCiAY0phodTluvVH

and yes folks, this is always on the user. It's a fucking dev build. It's the risk I take for almost ALWAYS using dev builds for everything hahah (if it's even a dev build issue. But im running 323 atm running just fine)

JamesPeters · 03-31-2021, 08:24 AM

What version of ReEQ are you using? I can't seem to replicate this in Reaper for Linux dev 330 with the latest ReEQ.

Jae.Thomas · 03-31-2021, 08:34 AM

Quote:

Originally Posted by JamesPeters

What version of ReEQ are you using? I can't seem to replicate this in Reaper for Linux dev 330 with the latest ReEQ.

where could I find the latest?

still weird its only happening in 330 tho

operator · 03-31-2021, 08:41 AM

I feel with you... I had such "noise bombs" in my early days when i was using some cracked plugins... (I assume that in your situation there are no cracked plugins involved, right?)

The moment when your speaker is so loud it is pushing/moving so much air, that you feel a hefty breeze coming towards you... :-) nothing compares to this adrenaline rush while trying to remember in a blind panic where the f**king volume knob of the interface is.

Since then I have "Ice9" on my master (in combination with the Reaper auto-mute turned on [since I use Reaper]). Maybe it would be a good idea to use Ice9 when working with Pre-Release builds in case the Reaper auto mute might be involved in the bug too. idk

Ice 9 Auto Mute VST (it is free) --> https://www.kvraudio.com/product/ice...cerberus-audio

-

karbomusic · 03-31-2021, 08:46 AM

Quote:

Originally Posted by operator

I feel with you... I had such "noise bombs" when I started making music and used some cracked plugins...

Happened here last night doing some loop back testing and made a mistake! But since I have auto-mute configured, it never made it to the speakers.

The salient point is that it is impossible to cover every possible scenario where something like this could happen, and eventually it will, be prepared.

operator · 03-31-2021, 09:00 AM

Quote:

Originally Posted by karbomusic

The salient point is that it is impossible to cover every possible scenario where something like this could happen, and eventually it will, be prepared.

Ohh yeah, loopback/feedback can be a very nasty thing. Yes, luckily Reaper has a Auto-Mute Feature bult in... So great!

And yes, I learned that the hard way.. Guys, listen to Karbo --> be prepared and switch on Auto-Mute. (wise words)

Icchan · 03-31-2021, 09:13 AM

Quote:

Originally Posted by Jae.Thomas

you might just blow your damned speakers.

The latest version does something to reeq to break the GUI, and cause a massive, constant, white noise burst.

Sure, it might be broken, but if it blows your speakers or makes you deaf, it's your fault for connecting them directly to your main outs without attenuator in between and turning them up to 11...

I'm sure they'll fix this.

Jae.Thomas · 03-31-2021, 09:18 AM

Quote:

Originally Posted by Icchan

Sure, it might be broken, but if it blows your speakers or makes you deaf, it's your fault for connecting them directly to your main outs without attenuator in between and turning them up to 11...

I'm sure they'll fix this.

haha i did think automute would cover it.

No cracked plugins here, but I was able to narrow it down to reeq, but i mean, I have had demo versions have big white noise bursts before... but not like this

operator · 03-31-2021, 09:24 AM

Quote:

Originally Posted by Jae.Thomas

haha i did think automute would cover it.

No cracked plugins here, but I was able to narrow it down to reeq, but i mean, I have had demo versions have big white noise bursts before... but not like this

Demo noises are nothing compared to "real" noise bombs, i know. :-) So you had the Reaper Auto-Mute enabled and it still got through? Then maybe also use Ice9 on the master like I do, for safety... This is my most recommended plugin to my colleagues, because it can safe (car)ears.

karbomusic · 03-31-2021, 09:33 AM

Quote:

Originally Posted by Jae.Thomas

haha i did think automute would cover it.

You might check the auto mute settings to be sure. Mine's never missed a noise bomb.

Jae.Thomas · 03-31-2021, 09:40 AM

I am wondering if it was somehow on the monitoring fx?!??!

but I don't have reeq there

JamesPeters · 03-31-2021, 09:42 AM

Quote:

Originally Posted by Jae.Thomas

where could I find the latest?

In the first post of the ReEQ thread, where he always posts the latest version. Check your version. Is it Version: v1.0.11? If you don't know how to check, open the file either in a notepad or hitting "edit" on the FX toolbar for the plugin.

Quote:

Originally Posted by Jae.Thomas

still weird its only happening in 330 tho

That's not necessarily relevant if the bug in the plugin is specific enough.

And yes, automute is a good thing. It has helped me many times. I set it for a more paranoid value too, +10 dB on any track (plus I usually mix with the master track's volume turned down).

operator · 03-31-2021, 09:46 AM

Quote:

Originally Posted by karbomusic

You might check the auto mute settings to be sure. Mine's never missed a noise bomb.

I remember in a Bitwig Beta we had a problem: There was some issue with the Peak-Limiter when the signal went +135db above 0dBFS it suddenly let the audio through unprocessed at full volume. This was a range issue...

Maybe Reaper´s Auto-Mute range isn´t defined up to +inf dBFS. (or maybe Jae.Thomas just had it switched off...) :-)

Justin · 03-31-2021, 09:48 AM

In this build I changed the stillwell autoexpander JS to change its behavior significantly (upward expansion rather than downward) , that might be related? reverting that change

Jae.Thomas · 03-31-2021, 09:59 AM

Quote:

Originally Posted by Justin

In this build I changed the stillwell autoexpander JS to change its behavior significantly (upward expansion rather than downward) , that might be related? reverting that change

that would be weird, how would that even relate haha BUT THIS IS WHY IM NOT A SOFTWARE DEVELOPER

I guess it's a possibility, thanks. If you need me to test directly so you don't inconvenience anyone else lmk

JamesPeters · 03-31-2021, 10:01 AM

Quote:

Originally Posted by Justin

In this build I changed the stillwell autoexpander JS to change its behavior significantly (upward expansion rather than downward) , that might be related? reverting that change

Could that somehow be responsible? Code from a JS plugin causing an issue in a project that doesn't contain that plugin?

On a probably unrelated note, I'm still curious about that ReaEQ/ReEQ bug, in which having both on a track would cause weird settings of ReaEQ. (It was resolved a while ago but it always left me wondering how that could've been possible, and cast doubt on the nature of JS plugins in my mind.)

Jae.Thomas · 03-31-2021, 10:02 AM

Quote:

Originally Posted by JamesPeters

Could that somehow be responsible? Code from a JS plugin causing an issue in a project that doesn't contain that plugin?

I mean, maybe reeq calls something in JS that is similar?

It's weird but who knows.

Again, could just be me, too. I am cursed

karbomusic · 03-31-2021, 10:04 AM

Quote:

Originally Posted by operator

I remember in a Bitwig Beta we had a problem: There was some issue with the Peak-Limiter when the signal went +135db above 0dBFS it suddenly let the audio through unprocessed at full volume. This was a range issue...

Maybe Reaper´s Auto-Mute range isn´t defined up to +inf dBFS. (or maybe Jae.Thomas just had it switched off...) :-)

Looks like mine is set to auto-mute any track @ +18 dbFS.

Jae.Thomas · 03-31-2021, 10:05 AM

could be I had my speakers set louder so it didn't go above automute but I find that odd. Shoulda caught it. It was insanely loud. haha

Coachz · 03-31-2021, 10:09 AM

Quote:

Originally Posted by Jae.Thomas

my default template:

https://www.dropbox.com/t/wCiAY0phodTluvVH

and yes folks, this is always on the user. It's a fucking dev build. It's the risk I take for almost ALWAYS using dev builds for everything hahah (if it's even a dev build issue. But im running 323 atm running just fine)

Potty mouth

Jae.Thomas · 03-31-2021, 10:09 AM

Jae.Thomas · 03-31-2021, 10:10 AM

Quote:

Originally Posted by Coachz

Potty mouth

just making sure folks know im not blaming the devs for my recklessness in no uncertain fuckin terms

Jae.Thomas · 03-31-2021, 10:10 AM

who knows, maybe I would have been helpful to the testing process for once in a long fuckin time.

that would be nice.

JamesPeters · 03-31-2021, 10:12 AM

You have it set to auto mute the master track. I set mine to auto mute *any* track (plus also when the output exceeds +10 dB). I mean I realize muting the master should be enough, but still...all it took was one loud burst of noise a few years ago, and that setting got changed forever.

That way, if a single track exceeds +10 dB, even if the overall mix isn't above +10 dB, it still mutes that track.

Jae.Thomas · 03-31-2021, 10:15 AM

Quote:

Originally Posted by JamesPeters

You have it set to auto mute the master track. I set mine to auto mute *any* track (plus also when the output exceeds +10 dB). I mean I realize muting the master should be enough, but still...all it took was one loud burst of noise a few years ago, and that setting got changed forever.

That way, if a single track exceeds +10 dB, even if the overall mix isn't above +10 dB, it still mutes that track.

good thinking there bud

karbomusic · 03-31-2021, 10:16 AM

Quote:

Originally Posted by JamesPeters

You have it set to auto mute the master track. I set mine to auto mute *any* track (plus also when the output exceeds +10 dB). I mean I realize muting the master should be enough, but still...all it took was one loud burst of noise a few years ago, and that setting got changed forever.

Yea, back in the day, we'd blow a horn on our practice Altec VOTT PA speakers about twice a month due to accidental feedback, sometimes I could repair it (I used to do that for a living) but other times I couldn't. Eventually, I placed a fast-blow fuse of just the right value which was the caveman's auto mute.

Nothing sucks more than that sinking feeling when all the high-end suddenly goes away in your speakers.

Jae.Thomas · 03-31-2021, 10:20 AM

our when you literally melt a speaker....

happened during a gig where I wasn't in charge of sound.

And was on shrooms and saw a speaker burning and wasn't sure if it was real.

JamesPeters · 03-31-2021, 10:20 AM

Quote:

Originally Posted by karbomusic

Eventually, I placed a fast-blow fuse of just the right value which was the caveman's auto mute.

Lol we think alike. I do things like that too.

I find a lot of fast-blow fuse values are too high for my liking, and I choose "paranoid" values.

Quote:

Originally Posted by karbomusic

Nothing sucks more than that sinking feeling when all the high-end suddenly goes away in your speakers.

When all the high-end goes away in your ears, it sucks more than that.

karbomusic · 03-31-2021, 10:20 AM

Quote:

Originally Posted by Jae.Thomas

Maybe the monitors are just too loud like you said. Mine are SPL calibrated so with the volume full up it's loud but not generally damaging loud. A steady sine at 5k might eat a tweeter if it goes for long enough but I'm mostly protected - I also have an external analog volume knob/dim/mute buttons 6 inches from my left hand (Presonus Monitor Station) because I never trust having to grab a mouse and start clicking around in such scenarios.

I'm pretty good at this though due to the sheer number of speakers I've blown in my lifetime - I should get a plaque or something.

operator · 03-31-2021, 10:22 AM

Quote:

Originally Posted by karbomusic

Looks like mine is set to auto-mute any track @ +18 dbFS.

This +18dBFS is a threshold value, from where it starts to mute. The range would then be from +18 dBFS to +inf dBFS. And I am talking about this range and its upper-range value --> +inf dBFS... Is it maybe set to a fixed value e.g. +135 dBFS. Then when the audio signal exeeds this range the process can´t work anymore and the audio is let through unmuted or worse. -->like the problem we had in Bitwig´s Peak-Limiter.

But i don´t thik this is the case... I just wanted to throw in my 5 cents to collect ideas and eventual sorces of problems to get a quick fix for this.

Jae.Thomas · 03-31-2021, 10:27 AM

Quote:

Originally Posted by karbomusic

Maybe the monitors are just too loud like you said. Mine are SPL calibrated so with the volume full up it's loud but not generally damaging loud. A steady sine at 5k might eat a tweeter if it goes for long enough but I'm mostly protected - I also have an external analog volume knob/dim/mute buttons 6 inches from my left hand (Presonus Monitor Station) because I never trust having to grab a mouse and start clicking around in such scenarios.

I'm pretty good at this though due to the sheer number of speakers I've blown in my lifetime - I should get a plaque or something.

well, I've been lucky. What's weird is the limiter on the Beri's I have didn't even trigger. So maybe it just FELT loud cause I just woke up.

But most DEFINITELY disconcerting. And when I went to replicate it on a different rpp, it DID trigger automute so who tf knows. weirdness.

karbomusic · 03-31-2021, 10:31 AM

Quote:

Originally Posted by Jae.Thomas

our when you literally melt a speaker....

happened during a gig where I wasn't in charge of sound.

And was on shrooms and saw a speaker burning and wasn't sure if it was real.

Well.....

I ran sound for a lot of bands in the 90s, it was a great gig, I didn't have to own a PA. Either the bands rented one or they brought their own and all I had to do was mic up, mix, tear the mics down, go home.

I had been mixing this particular band for a couple years and I knew their PA like the back of my hand. I'd usually have line-of-site of the clip indicators for the QSC sub amps and whatever their wattage was, I could just bump the clip indicator every so often and know I was in the sweet spot where I had maximum thump without damaging anything.

One night I'm 40 minutes into the show, all low end disappears on both sides (huge 18" EV subs). They failed to tell me they essentially tripled the power output with new amps for those subs. So my usual "kiss the clip indicator" practice literally melted/seized the voice coils in both subs. Luckily EV replaced them under warranty but they really shouldn't have. The band laughed it off and didn't blame me, but still a bit stressful.

Jae.Thomas · 03-31-2021, 10:35 AM

Quote:

Originally Posted by karbomusic

Well.....

I ran sound for a lot of bands in the 90s, it was a great gig, I didn't have to own a PA. Either the bands rented one or they brought their own and all I had to do was mic up, mix, tear the mics down, go home.

I had been mixing this particular band for a couple years and I knew their PA like the back of my hand. I'd usually have line-of-site of the clip indicators for the QSC sub amps and whatever their wattage was, I could just bump the clip indicator every so often and know I was in the sweet spot where I had maximum thump without damaging anything.

One night I'm 40 minutes into the show, all low end disappears on both sides (huge 18" EV subs). They failed to tell me they essentially tripled the power output with new amps for those subs. So my usual "kiss the clip indicator" practice literally melted/seized the voice coils in both subs. Luckily EV replaced them under warranty but they really shouldn't have. The band laughed it off and didn't blame me, but still a bit stressful.

that's pretty insane. who tripled the power output? The company? New amps? Or the band?

high on shrooms, I was on stage in a 7 piece band, was playing a solo while I saw the speaker smoking and distorting (physically, melting ((thought it was a result of tripping))), and after the solo, put my guitar on the stand and walked off.

people were cheering like it was some kind of like... thing I was doing. haha

I had to go to the FOH while the audience watched me, they said they couldn't leave and I needed to get a ladder for the stage manager, so I went ALL THE WAY AROUND THE THEATER AS EVERYONE WAS WATCHING ME, THE BAND IN DISBELIEF but still passing around solos, they see me get a fucking LADDER from the back, walk ALL THE WAY AROUND THE THEATER, and then the stage manager went and inspected the speaker and disconnected it as we were playing.