Smiff
Emutalk Member
a couple of things.. pj64 is not 1964 or nemu.. KISS. no offense but i can't think of any worse idea than looking at others and going "yeah, we could have that".
the kind of person who replies to this thread may want options for everything, but most people do not. they just want something that works. you wouldn't believe the debates weve had internally about adding or not one control.
the RSP selector is a good example. we have it in beta so we can test easier.. but don't say "how about.. an option.." say "we need this option because..." and then probably can add that capability so the option isn't needed, or automate it, or finally consider adding the control. Jabo would nearly always would rather fix the problem, rather than add a workaround - because everything the user needs to do is a workaround and has to be documented as such. everytime someone fails to RTFM (or posts an FAQ) is a reminder to me that the problem isn't really fixed. this particular point, i'm on the fence, i would probably now make the RSP selection an advanced control at the bottom of the plugin selection tab.
having advanced and basic modes as we do also helps sometimes, so think whether a control should be only visible in advanced or not, or never.
Clements i like the small bug-fix suggestions like fixing the about box
small simple things are much more likely to get done!
things like CPU optimisations are totally up to Jabo, if he doesn't feel he can get a significant gain out of it (like several %) it's not worth the extra pathway you have to add with the extra testing and possibilities of going wrong. i personally have just bought a Sempron with SSE3, but don't expect much out of it, and of course CPUs with the extra instructions tend to be faster anyway so they need it least. so better to optimise in general code.
the kind of person who replies to this thread may want options for everything, but most people do not. they just want something that works. you wouldn't believe the debates weve had internally about adding or not one control.
the RSP selector is a good example. we have it in beta so we can test easier.. but don't say "how about.. an option.." say "we need this option because..." and then probably can add that capability so the option isn't needed, or automate it, or finally consider adding the control. Jabo would nearly always would rather fix the problem, rather than add a workaround - because everything the user needs to do is a workaround and has to be documented as such. everytime someone fails to RTFM (or posts an FAQ) is a reminder to me that the problem isn't really fixed. this particular point, i'm on the fence, i would probably now make the RSP selection an advanced control at the bottom of the plugin selection tab.
having advanced and basic modes as we do also helps sometimes, so think whether a control should be only visible in advanced or not, or never.
Clements i like the small bug-fix suggestions like fixing the about box
small simple things are much more likely to get done!things like CPU optimisations are totally up to Jabo, if he doesn't feel he can get a significant gain out of it (like several %) it's not worth the extra pathway you have to add with the extra testing and possibilities of going wrong. i personally have just bought a Sempron with SSE3, but don't expect much out of it, and of course CPUs with the extra instructions tend to be faster anyway so they need it least. so better to optimise in general code.
Last edited:
