Good to see another Jordan Peterson fan here!Thanks Again FAS!
Last night I saw Jordan Peterson live, and today Q10.1 for our beloved II XL+s! Great times! . .
Good to see another Jordan Peterson fan here!Thanks Again FAS!
Last night I saw Jordan Peterson live, and today Q10.1 for our beloved II XL+s! Great times! . .
94-96% CPU Usage? That would be your problem. Perhaps the new firmware is using slightly more CPU?
I remember watching a documentary about IBM back in the early days. Programmers were paid by KLOCs - thousand (K) Lines Of Code.I am an ASIC designer by trade. I used to work for a rather large company, which shall remain nameless, that does microprocessors. At on point we were graded by the number of gates we created everyday. Not the best indicator of efficiency let me tell you. I could instance a 32 bit register in a for generate loop and create over a million gates in about 3 minutes. But it would be useless logic.
^ He said Foo Bar...
I remember watching a documentary about IBM back in the early days. Programmers were paid by KLOCs - thousand (K) Lines Of Code.
Awe Yeah! Love me some JP, and firmware update on top of that! Sweet!Thanks Again FAS!
Last night I saw Jordan Peterson live, and today Q10.1 for our beloved II XL+s! Great times! . .
Yep, and then 10 years later we were paid by how many lines we could remove in projects to make systems more effecient.
Yeah totally! I was thinking the same!Is it just me, or AXEII has now more air and different (better) dynamic now? I feel like it reacts differently, with more dynamic, when guitar pot is turned down.
Big thanks for 10.01! I love you Fractal!
One of the tricks-of-the-trade when doing embedded programming is to make local copies of member variables. I.e., if you have an object foo with a member bar you would do this:
float bar;
...
bar = foo.bar;
for(i = 0; i < FRAME_SIZE; i++)
{
...
bar = bar * x; // for example
...
}
foo.bar = bar;
The operation on bar is a "Read-Modify-Write (RMW)" and most embedded processors are optimized for this if the memory is L1 cache (or some other tightly-coupled on-chip memory). By making a local copy you force the compiler to use fast, local memory. When you are done with the loop you then save the local variable to the object.
Some compilers will do this automatically if you give them some information about the variable via a pragma. I think it's just easier to manually do it rather than dealing with pragmas which aren't portable.
The danger with doing this is if you forget to initialize bar or save it at the end, which is what I did.