• We would like to remind our members that this is a privately owned, run and supported forum. You are here at the invitation and discretion of the owners. As such, rules and standards of conduct will be applied that help keep this forum functioning as the owners desire. These include, but are not limited to, removing content and even access to the forum.

    Please give yourself a refresher on the forum rules you agreed to follow when you signed up.

Slow operation

JasonE

Inspired
I have noticed this as well. The preset I have been working with has ranged from the mid 70s to lower 80s as I have been building it. It seems to just be a visual issue for me. The FM9 changes but the display on my PC takes a few seconds to update. I also believe that if I disconnect the USB cable, the FM9 switches with zero issues. It seems to just be a communication issue between the FM9 and FM Edit.
 

Joe Bfstplk

Axe-Master
I second that
Adding modifiers is sometimes painfully slow on high cpu presets (above 65%). Per Preset Overrides sometimes don't load at all when going to that tab. Have changed USB cables a couple times, including getting a shorter one, so the cable doesn't seem to be to blame....
 

Joe Bfstplk

Axe-Master
Still experiencing slowness here on 2.0.0b firmware and 1.00.02 FM9Edit. Software start-up read of cabinet names started at a second or two per, but slowed gradually to the point of taking 26 seconds to read the 100th cab name.

In the time it took to one-finger this in and find/correct typos, it only got to 106....
 

Joe Bfstplk

Axe-Master
@m_brown is looking at this again.
Hopefully you archived those deleted posts to give an idea of the timing. it acts like each cab name it tries to load adds more time to the cab loading process until it eventually just sits there and does nothing for minutes at a time before loading the next cab name.... :)
 

Greg Ferguson

Axe-Master
Hopefully you archived those deleted posts to give an idea of the timing. it acts like each cab name it tries to load adds more time to the cab loading process until it eventually just sits there and does nothing for minutes at a time before loading the next cab name.... :)
I've seen the FM9+FM9-Edit combo do this several times prior to the beta. I haven't seen it do it yet after installing the beta. When it'd do it to me previously I'd lose patience much sooner and reboot the FM9 and once it restarted *Edit was perfectly happy and things proceeded at a normal speed. I'm thinking the smoking gun points at the FM9.

I should also mention I've seen the FM9 drop the USB connection when left on and the iMac Pro sleeps during the night. This has happened many times. The FX3 and FM3, on the same computer's built-in hub, remained connected. Leaving *Edit running and restarting the FM9 allowed *Edit to reconnect and work normally. I haven't seen that occur with this beta, but I haven't left the FM9 on for extended periods because of this. I'll see if I can aggravate it into misbehaving again. These are my Energy Saver settings:
Screen Shot 2021-12-18 at 4.56.11 PM.png

Update 211219_1147: I left the FM9 and FM9-Edit running overnight, and they were still connected this morning. That's a positive sign. I'll let the combination run for a couple more days and see what happens.
 
Last edited:

Joe Bfstplk

Axe-Master
I've seen the FM9+FM9-Edit combo do this several times prior to the beta. I haven't seen it do it yet after installing the beta. When it'd do it to me previously I'd lose patience much sooner and reboot the FM9 and once it restarted *Edit was perfectly happy and things proceeded at a normal speed. I'm thinking the smoking gun points at the FM9.
Me too. Tried restarting the unit to no avail, however. Something in a loop is taking longer with each iteration, kinda like a temporal version of the old rice grain doubling for each successive square on the chessboard parable....
 

Joe Bfstplk

Axe-Master
I should also mention I've seen the FM9 drop the USB connection when left on and the iMac Pro sleeps during the night. This has happened many times. The FX3 and FM3, on the same computer's built-in hub, remained connected. Leaving *Edit running and restarting the FM9 allowed *Edit to reconnect and work normally. I haven't seen that occur with this beta, but I haven't left the FM9 on for extended periods because of this. I'll see if I can aggravate it into misbehaving again. These are my Energy Saver settings:
View attachment 93049
I shut down the music rig when not using it, generally, so I doubt it has the chance to get to sleep mode. It is going better on the previous Editor. Hope this gets sorted soon. Too much utter crap going on around here to have my two bits of enjoyment (MINI and music gear) offline at the same time....
 

Greg Ferguson

Axe-Master
Me too. Tried restarting the unit to no avail, however. Something in a loop is taking longer with each iteration, kinda like a temporal version of the old rice grain doubling for each successive square on the chessboard parable....
When it happened to me it was the same situation, that it seemed twice as long each time.
 

Joe Bfstplk

Axe-Master
When it happened to me it was the same situation, that it seemed twice as long each time.
Same here. First time it got from 107? (don't remember for sure, and the posts recording my test got deleted) to 127 in the time it took to fix and eat lunch. Next time, after power cycling the unit and closing/reopening FM9Edit, it was even slower. The first dozen or so went fast, but then you could see them coming slower and slower - the very model of an exponential growth curve....
 

Greg Ferguson

Axe-Master
I've seen the FM9+FM9-Edit combo do this several times prior to the beta. I haven't seen it do it yet after installing the beta. When it'd do it to me previously I'd lose patience much sooner and reboot the FM9 and once it restarted *Edit was perfectly happy and things proceeded at a normal speed. I'm thinking the smoking gun points at the FM9.

I should also mention I've seen the FM9 drop the USB connection when left on and the iMac Pro sleeps during the night. This has happened many times. The FX3 and FM3, on the same computer's built-in hub, remained connected. Leaving *Edit running and restarting the FM9 allowed *Edit to reconnect and work normally. I haven't seen that occur with this beta, but I haven't left the FM9 on for extended periods because of this. I'll see if I can aggravate it into misbehaving again. These are my Energy Saver settings:
View attachment 93049

Update 211219_1147: I left the FM9 and FM9-Edit running overnight, and they were still connected this morning. That's a positive sign. I'll let the combination run for a couple more days and see what happens.
I'm on the third day of letting the FM9 and FM9-Edit run overnight and I've been greeted with Edit connected to the FM9, and cheerily showing me the current CPU % and I've been able to switch presets without restarting either.
 

bleujazz3

Fractal Fanatic
Joe,

There must be something happening with your devices that isn't with mine. I've only about 7 presets loaded and perhaps 2 or 3 extra user cabs.

Ny max CPU (after shunting some unneeded blocks I'd not likely use from LT's and Ian's presets, and consolidating signal paths, shortening them if possible)...runs about 63% give or take a couple points...What I discovered may shock you, and I'm not proud of this, but you can use this to your advantage...

Any preset that I've tried working with over 71% will absolutely display some lag when switching presets, scenes, or just normal operation...if you've got kitchen sink presets, definitely consider shunting unnecessary blocks OR create separate presets that contain what you might need for a song that contains what blocks you might need for intro, verse, choruses, etc.

It may be that v. 2.0.0 needs work, or that your normal FM9's operation with varied circumstances doesn't produce your desired results.

Although I've not done enough research into this matter to provide you with a more complete report, it may be possible that once I've dug deep enough, I'll know.
 
Last edited:
Top Bottom