I agree, there are simply to much strange things in Logic's notation-part, this is the main reason I didn't update it for ages now. Updates are simply to expensif to justify the minor improvements in the notationpart (At least for me) as I use Logic mainly for notation. Emagic should seriously take a look at Igor engraver( http://www.noteheads.com). It's FREE and does Notation the way it should. Dispite the fact that it's stil very buggy. Emagis do your job and make serious work from the notationpart or you will lose users to this kind of software. Edward ----- Original Message ----- From: Stewart Mackintosh <lists@...> To: Logic-users <logic-users@egroups.com> Cc: support emagic <support@...> Sent: Friday, June 30, 2000 8:21 PM Subject: [LUG] Score bugs in LAMP 4.2 - will they be gone in 4.5? > Firstly can I apologise to those who ask questions on the list that I know > the answer to: I get the digest and often go for days before catching up in > an orgy of information, by which time the question I could have replied to > has already been answered. > > Now to business. Those of us who have persevered with the notation side of > Logic have seen this element wither compared to the exponential improvements > in other parts of the package since the early days of Notator on the trusty > Atari. > > Notwithstanding the improvements announced with the latest upgrade which are > most welcome, I find I'm still having to use way too many workarounds to > produce a legible result, even in version 4.2. > > A few weeks ago I posted the following bug-report: > > > ...trying out a colleagues version of 4.2 to check out the notation > > improvements (thanks emagic - let's have more!) before I buy the upgrade, I > > came across the following bug, unless I've missed some new adjustable > > parameter.... > > > > In a 4/4 bar, insert a 1/2 note, 1/8th rest, 1/8th note, 1/8th rest, 1/8th > > note Now try to beam the 1/8th notes... Works fine in 3.7.2 I can't seem to > > find anything (even in extended layout parameters) that will fix this > > > OK OK, I hit the send button a little too soon. In my haste to criticise, I > hadn't experimented enough - it was a new feature. I now find that there > appears to be a bug in this new feature which allows individual alteration > of stem length: the default setting seems to have the beams almost on top of > the note heads rather than having the correct stem length to start with. > (I'd be happy to send a song with this problem as an example to anyone at > emagic who cares, showing what I mean...) Sure, I could assign a key command > to nudge these to the correct length every time I hit a rest within beamed > notes, but life's too short. > > I'd love to upgrade to 4.2 and beyond to take advantage of cross-staff > beaming, accidental size in chord symbols etc. etc. as well as the audio and > midi improvements, but simply don't have the time to keep finding > workarounds for basic mistakes that should really have been sorted long > before version 3.0, and I shall sadly probably call time and stick at 3.7.2 > > Yes, I use Logic for midi, yes, I use Logic for audio, but I also am > fortunate enough to be able to use Logic to earn money using the notation > part of the program. I know I'm not alone! > > My dilemma is this: I have a large notation project due to commence this > autumn. Do I believe the promises that the notation side of the program will > be improved when it still can't cope with the most basic musical grammar in > compound time? We've been posting these bugs for maybe four years now! > > Think about it this way, emagic: if kids in school can't use this software > to notate "Stille Nacht" correctly, what are they gonna do? I can't > recommend this software (for notation at least) to any of my friends who do > teach until this sort of basic mistake is fixed. And think about this: get > the notation working correctly, then blitz the education sector. Kids will > buy software they use in school, BUT ONLY IF IT WORKS. There's a huge market > there which must be going your competitors' way... > > And what am I gonna do? Only accept work in 4/4 time? I mean, come on! > I have done complete orchestral scores and parts for West End shows in > London using Logic, but the amount of information I have to retain simply > for workarounds is now reaching saturation point. Do emagic seriously expect > someone to read in the manual (and that's another thing!) "...in order to > display compound time correctly, you must have invisible rests hiding > underneath the notes..." Looks like I either bite the bullet and persevere > with Logic, clutzes and all, or use the cash I would have spent on the > upgrade towards making the move to S*belius. > > I desperately want to stay loyal to Logic. Despite its shortcomings, the > program can still take my breath away when I discover a new feature that > saves me hours of work the old way (and I still find these features on a > regular basis!), but sometimes the best of friends must part..... > > I'm not asking emagic to tell me what notation goodies they have planned for > 4.5 and beyond, I'm asking them to tell me they might consider spending a > little of their development Deutschmarks to address these long-standing and > frustrating notation problems. -- Best regards > > Stewart Mackintosh > > > > > Unsubscribe: mail to logic-users-unsubscribe@egroups.com > >