Double precision is no silver-bullet. Double precision Pd needs more memory and can run slower on certain platforms (for several reasons).I'd very much prefer for backwards compatibility, but double precision is the way to go for better sound.
Pd patches are not affected, they are just text files. It's really only about existing externals. Once you have your externals compiled for double precision, existing projects will work.I suppose there'll be a way to import old patches? Export new patches to 32bit pd?
Christof
Thank you Martin, so it does behave similar to OS9 versus OSX. Well then, PDX or PD64. I'd very much prefer for backwards compatibility, but double precision is the way to go for better sound. I suppose there'll be a way to import old patches? Export new patches to 32bit pd? Both would really help to work on with present hardware (libpd-based) for instance. I hope i didn't miss this info in digests sent before. Get's a bit hard to follow all of this sometimes. Thank you again On 11/24/20 16:07, Martin Peach wrote:On Tue, Nov 24, 2020 at 5:07 AM jayrope <jayrope@gmail.com> wrote:Why do we need _any_ name change? Any obvious version jump would do it already, 0.6, no?A 64-bit Pd would not be compatible with any previous version because all the memory structures would be differently sized, so any externals built for previous versions would crash. While any patches using vanilla objects would still work, unless a 64-bit version had some way of running 32-bit externals in parallel, it would be effectively a different program, not just a new version. Martin
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list