I am about to acquire Finale 2014; I read that it is software compatible with 64-bit systems: what does that mean? That by itself it is always 32-bit but also works on 64-bit systems?
Personally, I am doing well with Finale 2011, the only problem I always have to deal with is RAM, because with the heavy libraries I use, Kontakt has crashed on me.
I know that 64-bit software can make use of more RAM; I have 8 GB of RAM, but since Finale 2011 is a 32-bit program, I can only use a maximum of 4, if I understand correctly.
Is that so? How much RAM can a 32-bit software use at most? And a 64-bit one?
Furthermore, does anyone know what the new features of this new version of Finale are? I took a quick look at the website, but I didn't understand much....
Regarding the 32 and 64-bit discussion, both architectures are compatible. The substantial difference in terms of RAM between 32 and 64-bit is the fact that with 32-bit there are structural limits according to which software cannot address more than a certain amount of memory (RAM), resulting in not only limits but also few system "compromises."
In a 64-bit architecture, the concept is actually that of infinite memory, so the software can allocate much more than was possible with previous versions written only for 32-bit; if one has ample resources it is an advantage, because the power of the software increases... if resources are scarce, one must be careful that Finale does not consume more than what the system has available.
I am providing the translation offered by a Blog of a part of an article taken from a French site ( http://jipiblog.jipiz.fr/ )
These are the features of Finale 2014 mentioned in the Music Store Professional catalog:
Redesigned toolbar
Rewrite in Cocoa environment for the Mac version
Atonality management (scores without key signatures)
Automatic combination of rests when using different layers
Improved management of accidentals when using different layers
Automatic horizontal alignment of dynamic markings, braces, and lines, now made independent in parts compared to the score
Addition of new settings for percussion instrument notation
Independent modification of events via Special Tools in parts
New sounds for Garritan libraries
New file output format.
Furthermore, the next version of Finale will not be able to run on Mac OS X 10.6.8 (Snow Leopard) and obviously on all previous versions
Until the actual release of Finale 2014, we will not know for certain if these are the true (and only) features included in the official version of the product, but the list includes functionalities that had been requested by many users, so it seems plausible that such developments may indeed be present in the update.
Very useful, thanks everyone. I wanted to point out that reading a bit online about the 32-64 bit problem, there is talk of software created specifically for VSTs that allows you to use 32-bit VSTs as if they were 64-bit, overcoming the usable RAM limits typical of 32-bit systems: it's called Jbridge, I have obtained it but haven't tested it yet; first I want to see how Finale 2014 behaves in relation to this 32 or 64 bit thing.
jBridge is just as Geppino says, a "bridge" that allows iteration between 32/64 bit plug-ins and sequencers in both directions.
Since we are talking about sequencers, it is also very useful for those using Cubase, particularly the 32-bit version, by using 64-bit plug-ins via a bridge. I have found that it works very well; the opposite is not so much... cubase64 and 32-bit plug-ins.
In practice, it bypasses the intrinsic limits of the 32-bit architecture and jBridge opens separate processes (at 64-bit) for each of the plug-ins opened with it; this also lightens Cubase's resource consumption.
Given the usual problems of high resource consumption, since I still have Cubase in 32-bit, I have improved performance without running into compatibility issues with older plug-ins.
Furthermore, which is no small thing, VST Performance seems significantly improved to me when I use VSTs with jBridge.
jBridge works, I loaded up to 6 GB of sounds into Finale 2014; at first it was a bit unstable, now it seems like the system is "getting used to it." The funny thing is that it creates new processes, called auxhost64, which do not weigh down Finale, whereas before both Finale and the VSTs constituted a single heavy lump. Today I have effectively doubled my available resources, going from 4 to 8 GB available (i.e., all my RAM), I can consider myself satisfied....
I inform those interested that I will shortly publish the complete Italian translation of the introductory article for Finale 2014 written by Jari Williamsson, one of the world's Finale gurus, on his site www.finaletips.nu
I also point out the existence of a Facebook group, also named Movimento Finale, which can be reached at http://www.facebook.com/groups/256899574393401/. In the group, which is quite active, we are gradually forming a small community of users and experts of Makemusic's legendary program. If you wish, we look forward to seeing you.
Hi Giorgio, could you suggest the forum as a support tool... practically many people don't have Facebook, and this is a space where one can discuss common "problems" without difficulty.
Of course, I will certainly do so. In fact, I would like to take this opportunity to ask the administrators of this beautiful site if they would be interested in starting a link exchange with my blog. Good evening to everyone.
