|
|
| MakeMusic Forum > Public Forums > Finale - Macintosh - FORUM HAS MOVED! > Announcing Finale 2014d! | Forum Quick Jump
|
| 
Zuill
"The Troll"
      
Date Joined Oct 2003
Total Posts : 29077
| Posted 12/3/2014 2:35 PM (GMT -6) |   | Much, much, much faster! I was sitting there waiting (for 15 minutes and less than 5% complete) when I read this. I cancelled the "within Finale" update immediately and went to the website. Downloaded the zip file in less than a minute.
Zuill
"When all is said and done, more is said than done."
Finale 2002b, 2003a, 2004b, 2005b, Win XP SP3, 2011b Win 7 64bit, 2012a Bought and Paid For (Hopefully soon 2012b with some of the MAJOR BUGS fixed--well, now with 2012b and some of the bugs are fixed) 2012c, with some bug fixes. 2014c at present.
Favorite Forum quote: "Please, everybody, IGNORE THE TROLL!" | | Back to Top | |
|
David Ward
Registered Member
Date Joined Aug 2009
Total Posts : 2834
| Posted 12/3/2014 4:57 PM (GMT -6) | | I'm still just getting this for Quick Look (see screenshot), and no, I don't have an earlier version of Finale QL etc installed. I rarely want this, but I thought I ought to check it in case …
Saving is quicker (as is opening): at most 9 secs to save a 4.5 MB file that took more than 16 secs in F 2014c. Small files save almost instantly.
The boon for many of us will be the new Smart Shape option not to snap to the beat position: my thanks to MM for that.
I think that what Wiggy calls problems with 'focus' may still exist in this version, but as long as one is aware of them, they hardly matter.
David Ward
www.composers-uk.com/davidward
Finale 2014c with Mac 10.9.5
Finale 2010b with Mac 10.6.8
full TGTools
Since 2001 have used F 2001, 2003, 2007, 2009, 2010, 2014
| | Back to Top | |
|
Gary the T
[Funny comment here.]
Date Joined Aug 2000
Total Posts : 710
| Posted 12/3/2014 8:55 PM (GMT -6) | | I'm not nearly the regular I used to be on the Forum, though I still browse it fairly regularly. I've said in various threads over the past year that I still prefer 2011, but I had recently installed 2014c on my MBP as it was required for a recent part extraction project.
I had no intention of installing 2014 on my Mac, because of the well-documented issues Finale has with Waves and Native Instruments plugins. I've posted on numerous threads the crazy workaround I have to do in Finale 2011 every time I update my Waves.
With the release of 2014d today, however, just for giggles, I decided to try installing 2014d on my Mac, and here's what happened:
First I updated all my NI plugins, and restarted. Then installed Finale and GIFF, restarted again, said a prayer or three, and tried to open Finale.
First attempt, nothing. Force quit. Oh God, is it Waves and NI screwing things up already?
Second attempt, Vienna Ensemble opened, but Finale still didn't. Come ON, dammit.
Third attempt, Finale opened, I set my program options, experimented with Speedy entry, made sure all my print presets are there (they are, and also still in 2011, which is good, because when I first installed 2014 on my MBP, for some reason all my print presets disappeared from 2011 and I had to rebuild them all). Is that a glimmer of hope I see?
Fourth attempt and onward: So far, so good. Playback works, folders are correct, plugins are where they should be. Even after a restart, things appear to be correct.
Cue Hallelujah Chorus.
One very strange thing was that Avid's CoreAudio Manager launched when 2014 did, which never happened on the MBP, even though I have Pro Tools 10 and 11 installed on that machine as well. Turns out that my Avid OMNI was selected by Finale as the default I/O device. It's not, even on my system. I only use it for Pro Tools. Once I switched the I/O to my Metric Halo ULN-2, which IS the default for the system, no problems. Even ARIA Player seems to work on a VERY cursory bit of experimentation. Haven't yet tried Kontakt or any of that stuff, and I may not even try. I have so little hair left as it is…
So, I'm happy to say that things appear to be working correctly, and that's a relief, because on that big project, I had the choice of either using just a 17" MBP, or, if I wanted a second monitor, I had to connect it via HDMI to a Sony Bravia in my studio, because my matching 23" Cinema Displays are of a vintage that there was really no easy way to connect them to the laptop.
Now, does anyone know if there are any plans to revamp the Chord tool? The Chord Suffix Editor is to me the single worst thing in Finale. Back in the late 90s, when I was an engraver/editor for the National Guitar Workshop, I dealt with that nightmare every day. I was known to use the Lyric or even Expression tools rather than the damned Chord tool. 15 years later and it's still the same wretched interface. I'd say it's about time for an update, wouldn't you agree?
Cheers,
GT
Mobile: 17" MBP (2.66 GHz Intel Core i7, 8 GB RAM, 10.8.5), True Systems Precision 8, MH LIO-8
Home: Mac Pro (2x2.4 GHz Quad-Core Intel Xeon "Westmere", 32 GB RAM; 10.8.5; boot drive 960 GB Mercury Accelsior_E2 PCIe card), OMNI, MH ULN-2, MOTU 8pre
PT HDN 10.3.9/11.2.2; REAPER 4.7+ (32 & 64-bit); Logic 9.1.8; PreSonus FaderPort
Lots of Waves, McDSP, MH, Nomad Factory, Blue Cat plugins; VEPro 5; Komplete 9 Ultimate; IK Total Workstation 2; Peak Pro 6 & 7; Sound Forge Pro
Finale 2011c, 2014d | | Back to Top | |
|
BvdPress
Registered Member
Date Joined Nov 2001
Total Posts : 1006
| Posted 12/4/2014 8:58 PM (GMT -6) | | I was going to try to be nice and say something positive, but I can't. The delays, lag time and overall slowness of 2014 makes Finale 2014D unusable.
There is no reason why almost every feature requires a wait time. For example, add a dynamic, wait, wait and then it appears. Using the selection tool click on that dynamic and wait, wait and then you can move it. Forget scrolling. It is virtually impossible. I get not everyone has these issues, but enough of us have from day one and there has not been a single enhancement in speed.
Now I will be stubborn. MacBook Pro with plenty of RAM, etc. so don't go there. I am not reinstalling or deleting preferences again. I highly doubt it is anything from end because every program on my computer works absolutely fine but Finale 2014. All of them. Even the ones that are much older than Finale 2012, 2011, etc. Heck even Finale 2012 works great until it quits unexpectedly.
Something nice: Being able to turn off snap is great!
Something sort of nice: The files I tried today can still be moved back 2012. Again Mr. Conspiracy in me says this feature was added because MakeMusic knew 2014 was going be a disaster. Sorry, but every passing day I can buy into that more and more.
A big ugh from to MakeMusic.
According to the new CEO this is the goal:
"I’m out to build a world-class company that delivers world-class products."
2014d definitely is not a good start at least for me, but maybe there will be hope the company will care more for the product than us users someday. Today may faith is totally gone.
I will now go back to 2012 and continue learning Sibelius which once you play with the settings enough you can get decent results. If nothing else, it is stable and speedy.
That is all I have for this rant. I have work to do, deadlines and giving 2014d test run wasted a good amount of my day.
Maybe I will go watch "Grumpy Old men" now...
Bryan Doughty
BVD Press, Music Express and Cimarron Music
Oystein Baadsvik US tour coordinator - http://www.baadsvik.com/
bvdpress@snet.net or bryan@cimarronmusic.com
http://www.bvdpress.com
http://www.cimarronmusic.com/ | | Back to Top | |
|
Vaughan
Registered Member
Date Joined Jun 1999
Total Posts : 4984
| Posted 12/5/2014 4:02 PM (GMT -6) | | Bruno, your first sentence holds an important key: Finale slows down after 20-30 minutes. I've noticed this as well and remarked on it here several times. When I'm doing layout work, I generally restart Finale approximately every half hour. I even filed a support case with MM and they didn't respond to it at all. Here it is (case number 141105-000018):
In working with Finale 2014, whether on Yosemite or Mavericks, after it has been running for awhile, operations like staff nudging or switching tools slows to a crawl, making the program aggravating to use. In this state, nudging a staff using the arrow keys takes Finale 2 seconds to respond, as does switching tools (accompanied by the spinning ball of death). If I quit and restart Finale, reload the document and then nudge the same staff, it will then move about 4-5 times per second. Changing tools is then almost instantaneous. This behaviour requires me to quit and restart Finale about once every half hour to an hour. Not an impossible situation but very annoying and it shouldn't be necessary for a piece of professional software!
Here is an additional anomaly. When moving staves around (Page View), Finale is supposed to show the music while it's being dragged and it does indeed do this at the beginning of a work session. At about the same time as the aforementioned slowdown starts occurring, Finale stops showing the music as the staves are being dragged, and I can only see the outlines of the staves. This makes it difficult to do editing work, as one needs to be able to see the music in order to know how much to drag the staves! I either have to work using trial and error or by using the arrow keys to nudge the staves, but by this time Finale is functioning so slowly that each pixel nudge takes Finale 2 seconds to process. As I already mentioned, the only solution is to quit Finale, restart it, reload the document and find the spot where I was previously working.
Vaughan
Finale 3.2 - 2014c, Sibelius 4 - 7
Tobias Giesen's plugins, full version, Robert Patterson plugins, Dolet 6 plugin
MacOS 10.9.5/10.10
MacPro 6GB, MacBookPro (2011) 8GB
Amsterdam | | Back to Top | |
|
Vaughan
Registered Member
Date Joined Jun 1999
Total Posts : 4984
| Posted 12/6/2014 3:09 AM (GMT -6) | | Wiggy, it depends greatly on what I'm doing. If I'm entering notes, articulations, expressions or smart shapes, creating PDFs, etc., Finale generally doesn't slow down for me, either. It's working on the layout which seems to trigger it. The 'additional anomaly' I mentioned above is a sign that things are slowing down. Finale should show the contents of a staff while dragging it and this does happen when Finale is still 'fresh'. At a certain point, dragging staves starts just showing the staff outline and that's the signal for impending slowdowns. Several others have remarked on this behaviour, as well.
Vaughan
Finale 3.2 - 2014c, Sibelius 4 - 7
Tobias Giesen's plugins, full version, Robert Patterson plugins, Dolet 6 plugin
MacOS 10.9.5/10.10
MacPro 6GB, MacBookPro (2011) 8GB
Amsterdam | | Back to Top | |
| 58 posts in this thread.
Viewing Page : 1 2 3 |
| Forum Information | Currently it is Tuesday, December 19, 2023 6:07 PM (GMT -6)
There are a total of 403,820 posts in 58,165 threads.
In the last 3 days there were 0 new threads and 0 reply posts. View Active Threads
|
Forum powered by dotNetBB v2.42EC SP3
dotNetBB © 2000-2023 |
|
|