FM3 Firmware Release 1.04 Public Beta 5

[Mindfunk27]

Downloaded the 1.04 v5 today and I am getting the squealing artifact as well

 

[Mindfunk27]

Downloaded the 1.04 v5 today and I am getting the squealing artifact as well

Is there a way to roll back until the update is fixed?

 

[chris]

Is there a way to roll back until the update is fixed?

install the 1.03 file the same as you did the 1.04 beta.

https://www.fractalaudio.com/fm3-downloads/

 

[mikah912]

install the 1.03 file the same as you did the 1.04 beta.

https://www.fractalaudio.com/fm3-downloads/

Don't forget to uninstall FM3 Edit 1.04 and reinstall FM3 Edit 1.03 too. Otherwise, the blocks on the editor won't lineup with the ones on your unit.

 

[Mindfunk27]

Woof.... maybe I will just wait for a fix.
I am so afraid of messing anything up

 

[Randalljax]

Woof.... maybe I will just wait for a fix.
I am so afraid of messing anything up

i dont think it will be too long Cliff is on it

 

[Jumpback]

1.04 did me right, wrote tunes all weekend

 

[FractalAudio]

i dont think it will be too long Cliff is on it

I've narrowed it down. I fixed some minor mistakes in the amp block but the squealing thing I think is a feedback loop somewhere. I suspect it's something to do with the USB changes.

 

[FractalAudio]

I found it. Engineer was trying to save CPU by combining two operations into a double-length vector. So the instruction is indexing off the end of the vector.

 

[chris]

I found it. Engineer was trying to save CPU by combining two operations into a double-length vector. So the instruction is indexing off the end of the vector.

i totally understand this

 

[notalemming]

I found it. Engineer was trying to save CPU by combining two operations into a double-length vector. So the instruction is indexing off the end of the vector.

 

[Jeggz]

I found it. Engineer was trying to save CPU by combining two operations into a double-length vector. So the instruction is indexing off the end of the vector.

Thats exactly what I was thinking last night while I was playing, “indexing vectors”.

 

[FractalAudio]

The problem is the Input 1 Right data is corrupted. I found a workaround:
Put a Volume block immediately after the Input 1 block. Set the Input Select to Left Only.

 

[USMC_Trev]

I found it. Engineer was trying to save CPU by combining two operations into a double-length vector. So the instruction is indexing off the end of the vector.

Reticulating splines again? I hate when that happens.

 

[arniez]

The problem is the Input 1 Right data is corrupted. I found a workaround:
Put a Volume block immediately after the Input 1 block. Set the Input Select to Left Only.

So are you suggesting the end user do this or will this be coded into the next FW version?
arniez

 

[badmagick]

So are you suggesting the end user do this or will this be coded into the next FW version?
arniez

I read it as: do this if you want to continue using the beta til the next rev comes out.

 

[Randalljax]

So are you suggesting the end user do this or will this be coded into the next FW version?
arniez

No they will fix it , just will likely take a bit more time
if you want to carry on and check out the new amps this is a way to do that
and stop the feedback in the meantime

 

[Mark L.]

I found it. Engineer was trying to save CPU by combining two operations into a double-length vector. So the instruction is indexing off the end of the vector.

I KNEW it!!!

 

[yek]

https://forum.fractalaudio.com/threads/fm3-firmware-release-1-04-public-beta-6.161324/#post-1931445