Not sure if it makes a difference, but I've never had problems on a Mac. I have both installed, but never have both open simultaneously. I will typically use the standalone version for all update/backup needs, but have used the Edit version once or twice just to try it out.
People who have experience with the systems, especially previous generations of the hardware, and used the standalone version prior to it being embedded in Edit are in a different user-space than people new to the Fractal eco-system. We've seen many reports recently of users crossing the beams and having their screens fill with the alerts.
I'm still on 6.02. Gun shy based on reports of increased CPU requirements and all the apparent snags people seem to be hitting while upgrading. Can you share a sense of CPU usage changes going from 6.02 to 7.00? My most used patches all sit close to 80% in 6.02 and I'm loath to cut blocks from them. TIA
So you're saying to avoid having both open at once or else some chaos results?People who have experience with the systems, especially previous generations of the hardware, and used the standalone version prior to it being embedded in Edit are in a different user-space than people new to the Fractal eco-system. We've seen many reports recently of users crossing the beams and having their screens fill with the alerts.
I've run into it a couple times when I'm moving fast during testing, and it's amazing how fast Fractal-Bot can fill the screen, and it can lead to someone totally freaking out if they're not aware of the ways to kill a running app, because, at that point Fractal-Bot has lost its mind and won't listen to the keyboard and there's a screenful of alert boxes hoping someone will click them. I have a strong computer background, especially on Macs and doing development on them, and I sat there stunned thinking "WHAT THE F*!?" the first time, and "NO, I DIDN'T DO THAT AGAIN!?" the second and third times. (Like I said, I was moving fast.) And the easy way for people to avoid that is to only use Edit's embedded version until there's an absolute need. YMMV, and that's cool, because the more experienced people who understand the issue and can talk the others off the ledge, the better.
Yes. Dogs and cats will be living together.
And doing godawful things to the furniture and each other, laughing at anything that “can’t connect.”
sure! on firmware 6.02 my main JMP-1 Preset that has an Amp, Cab, Comp, Wah, Pitch, Reverb, Looper, Chorus, Formant, Phaser Block, and uses all 4 channels on every block (4 amps, 4 cabs, 4 pitches etc..) would top at 68-70%.
That has no affect on CPU. Only the active channels use CPU...
Granted the Reverb block isn’t super high quality but I don’t notice and no one else does either in a live setting. So good news for me I guess lol
So, in this example, the move cost you something in the range of 3% My primary patches are not unlike this one, so I'll go through my important ones and assess the impact of upgrading on this basis. I like to keep current and have access to the latest features.
I have several presets that suddenly show overload and cut out. Very embarrassing during rehearsal. Multidelay is very jummy, but also very heavy. It's also a bit of a hassle to rectify this from the front panel.Anyone else notice CPU usage, dropped a little? I noticed when I loaded 7 beta 4. Confirmed now with FW 7.0. I’d say between 1-1.5% less than 6.02. In my experience anyway. I’ll take it. Lol. Later this evening I will post my setups. Lots of effects, dyna cabs, controllers, etc.
80% is the recommended max CPU level. Audio processing and varying models in the blocks can make the CPU usage change on the fly so a preset that’s already on the edge can suddenly trigger the system’s warnings and block sound processing can be stopped until you do something about it.
You can’t really compare memory usage from older firmware with the current firmware. It’s different code.
There are some in the forum, but firmware updates to the models change the values.
It can wobble back and forth. New features can increase CPU then Cliff will have a chance to optimize and it’ll drop again. It’s an interesting thing about watching Fractal’s development of the system, it shows that they really care.
It is interesting. I’m definitely not complaining. For my presets the drop in CPU is welcomed. I usually run around 78-80%. These are now comfortably around 76-78 now. If I remove the looper I can free up more space.
Been using the standalone version for years, since when has bot been embedded in Edit and where I find the button +
Since many years. You can find it in the Tools menu.