FM3 Firmware Version 12.0 public beta

Status
Not open for further replies.
ok it happened again.
I created first a preset like I always do with 2 send return to have everything visible on the unit on the first screen

then as I didn't needed 3 rows I swapped the output node with the first send

Now the blocks are crashed and they stay crashed even if I change preset remains red when looking at the vu meter

the blocks that remais 'crashes' are the output 1 block, the chorus block and the reverb


EDIT: the crash seems related to the feedback send/return block our the output lock. moving that around in the editor with audio going in causes the crash?? I can make a video if it helps but is happening quite consistently if you start dragging blocks in the editor and connecting/disconnecting them
also strange behaviour I had the feedback loop crash but the output was still going then I switched to an empty patch and returning to the a patch without feedback send now output1 is red

is kinda difficult to film it as you can see the crashed blocks only on the actual device if you switch to the layout level meter page

EDIT2: of course I tried to do a video and nw everything workd perfectly :-) seems an intermittent thing
 

Attachments

  • 1000067150.jpg
    1000067150.jpg
    2.8 MB · Views: 53
  • N ODS.syx
    N ODS.syx
    24.1 KB · Views: 2
Last edited:
What's in the FIRST block on the 2nd row?
is feedback return 1 I'm doing presets like this to have all the blocks on the device in the first screen without zooming I prefer to see all the blocks in one screen without zooming in

the chain is
input 1 -> drive1 -> send 1 -> ret 1 -> amp -> cab-> Rev//multitap dly -> chorus -> out1

the crashed blocks where rev dly chorus and out
 
When both input and output of the block are clipping, the cause may be something before it.

In this case the Return block. What are its settings?
And what drive type are you using in DRIVE 1?

And if AMP follows the Return block, what block is placed in parallel?
(I can't load the attached preset to check atm)
 
the settings of the return block are just return volume set to Max 1?
the parallel block to the reverb is a multitap delay
 
the settings of the return block are just return volume set to Max 1?
the parallel block to the reverb is a multitap delay

1) You are using the Return block wrong, it seems. Mix should be at 100%, and Return should be at 0dB. Your settings make the block oscillate / clip.

2) Multitap Delay parallel to Reverb doesn't correspond with your description in post 164 above, where AMP follows RETURN.
 
I've had the red block crash bug happen on presets multiple times without send/return blocks or out2/in2 effects loops.
 
1) You are using the Return block wrong, it seems. Mix should be at 100%, and Return should be at 0dB. Your settings make the block oscillate / clip.
this is what i have. also i have done this in most of my presets no oscillation. also after restart works correctly

2) Multitap Delay parallel to Reverb doesn't correspond with your description in post 164 above, where AMP follows RETURN.
Rev//multitap dly -> this means reverb in parallel with multitap delay
 
Your information is not consistent. It must be, to help solve the issue.

In post 166 you write that Return Level in the Return block is maxed out.
In post 171 you write that Return Level is at 0dB.
That's not the same.

In post 164 you write that the block after RETURN is AMP.
But that doesn't correspond with the picture of the layout grid where the blocks after RETURN are parallel blocks, which you say are MTD and Reverb.
 
Now it sounds way worse tan with 11.0
Please be more constructive in your comments. This thread is for beta testers. So you’ll need to describe what you are hearing that is worse, help narrow it down to specific blocks or settings that you think changed ? Maybe provide a sound example and a preset if it’s specific to a preset.
 
Austin Powers Love GIF
 
Status
Not open for further replies.
Back
Top Bottom