Starts feeling a little laggy at around 60-65%. Not many of my presets get up that high, but a few do....Version 1.00.01.
With CPU between 80-81%, changing values in FC Edit > FC Config is very slow.
I second thatVersion 1.00.01.
With CPU between 80-81%, changing values in FC Edit > FC Config is very slow.
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....I second that
We are currently looking into this.Version 1.00.01.
With CPU between 80-81%, changing values in FC Edit > FC Config is very slow.
I'm heading out to a gig with FW 2.0 beta. I'm interested in your findings by rolling back. Think I'll try it tomorrow too unless you report it didn't helpGave up just now at 107.
Rolling back to previous Editor to see if it is any better....
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....@m_brown is looking at this again.
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.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....![]()
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....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 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....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
When it happened to me it was the same situation, that it seemed twice as long each time.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....
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....When it happened to me it was the same situation, that it seemed twice as long each time.
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.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.
It took 3 days?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.