Jump to content

joegold

Member
  • Posts

    53
  • Joined

  • Last visited

joegold's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. That sure looks right! Does it play back properly? And how the hell did you do that?
  2. Hi My preferred way of working with and writing for drums has always involved entering things by hand in the Score Editor. I've always used a combination of a Mapped Instrument Track/Region triggering (via an Environment cable) a software synth (or external midi synth) Track with drum sounds. This way of working allows for a Mapped Score Style (usually the stock #Drums Style works fine) where everytime I select a note in the Score Editor and/or within an Event Editor it will show the actual name of the drum kit element rather than the MIDI note name/number. E.g. If I enter in the note C2 it won't show as "C2" but rather as "Kick 1" and it will show up on the 5-line staff on the first line. Entering in D2 will show the name "SD1" (Snare 1). Etc. And the individual drum names (Kick 1, SD 1, etc.) will be visible also in any Event Editors. This is all fine except that I have to use 2 tracks (one for the Mapped Instrument and 1 for the software instrument), which is sub optimal and easily becomes unwieldy. So... I notice that if I just use a Software Instrument Track with a Mapped Style assigned to it in the Score Editor, w/o also using the Mapped Instrument track, that when I enter in a note via the mouse from the Part Box, as I'm in the process of dragging in the Score area the various instrument names (Kick 1, SD 1, etc.) are visible in the little info bubble, but as soon as the note is entered it is shown only by its MIDI note name in the Score single Event sub-window as well as in any other Event Lists. I don't suppose there's a way to make this simpler by having a Mapped Score Style also force and Event Editors to list the instrument names rather than the MIDI note names the way the Mapped Instrument map seems to work, is there? Hope I explained that in a way that's somewhat intelligible. lol
  3. Hi I updated to LX 10.0.7 when it first came out via the App store application and it appears to be working fine. But for some reason App Store doesn't list the 10.0.7 update in its list of already installed updates. But App store is not prodding me to update my version of LX either. Does anybody have any idea why this might be so and if i should be concerned?
  4. I stand corrected yet again. It wasn't mentioned in the little blurb of a release note shown by the Software Update app but it is mentioned in the detailed release notes here: http://support.apple.com/kb/TS4498?viewlocale=en_US&locale=en_US I guess I really haven't been putting LX through the paces very much since I bought it a few months back because I never encountered any of the other zillions of bugs (in the Score Editor and elsewhere) that this update appears to have addressed. Of course as far as the Score Editor is concerned, there doesn't seem to be much in the way of significant new features in this update, just lots of bugs that were fixed and a few minor work-flow enhancements.
  5. Yep. It appears to be fixed in LX 10.0.7. Yay.
  6. OK. I see now that you're talking about a new udpate, 10.0.7, for Logic X. I thought you were referring to OS 10.0.7. My bad. I'm dl'ing the LX update now. Hopefully you're right but I see no mention of the PDF printing fix in the release notes.
  7. Either you're mistaken, or you don't understand the problem or there's something even weirder going on than what we've all been concerned about.
  8. I said it "made sense", not that it was a way that any trained musician would ever write it. Writing it that way would be a recipe for disaster IMO. By "'making sense" I simply mean that the beats line up. Obviously, the only way to write it that really makes sense is with the dotted 1/8 figure you supplied. Still, writers like Bartok have been know to do strange notational things like that from time to time to make a point about how they want things phrased even if it will cause the very best musicians to scratch their heads for a while.
  9. OK. Here's an over-the-barline tuplet that does make sense. And here's the only way to notate the original 1/4 triplet starting on beat 4 idea that makes sense, even though it's "wrong" as far as I know. There's probably a way for Logic to do this sort of thing, graphically, using the Layout Tool to move an Independent Note so it sits in the middle of the barline along with a few other tweaks. But it won't sound right over MIDI.
  10. Beaming over barlines is a fairly common way to indicate phrasing that crosses the barline. But your example had none of that. Tuplet figures over barlines are another matter though. There may be exotic cases where even this makes sense but I can't think of any.
  11. That's written as a 1/4 + 1/8 triplet starting on beat 4 tied to an 1/8 + 1/4 triplet on beat 1 of the next bar. There is no such thing as a triplet of three 1/4 notes that starts on beat 4 of a 4/4 bar. That is a logical impossibility if you think about it. The first half of the second 1/4 would be on one side of the barline and the other half would be on the other side of the barline. You can use non-standard notation like that if you want but musicians who know how to read music won't understand what you want.
  12. How To Fix LX PDFs With Acrobat Pro 9 1. Open PDF in Acrobat Pro 9. 2. Advanced Menu: > Pre Production > select Pre Flight 3. Pre Flight window: Select “Create separate layers for vector objects, text and images.” 4. Click Analyze and Fix. 5. When prompted Save File. 6. Close Pre Flight window. 7. Close file and reopen in Acrobat Pro. 8. View Menu: Navigation Panels > select Layers 9. Layers Pane: Control Click on text layer and de-select Show Layer. 10. Layers Pane: Control Click on vector objects layer and de-select Show Layer. 11. Tools Menu: Advanced Editing > select Touch Up Object Tool. 12. Click on PDF image and select all (Command A). 13. Hit Delete. 14. Layers Pane: Control Click on text layer and select Show Layer. 15. Layers Pane: Control Click on vector objects layer and select Show Layer. 16. File Menu: Save your fixed file to disk. 17. Open file in Adobe Reader and check that it worked. [Many thanks again to bluegrassLogic.]
  13. If all you need to do is to view your PDF files on screen and/or print them on a printer then Preview is fine for that and will give you full quality results. The problems are all with how these LX generated PDF files appear and print from Adobe applications. Since I've got a book out that I'm always editing and making additions to that was written with Adobe InDesign and uses many PDF files as graphic inserts, this is a big problem for me. If you need to fix an LX generated PDF file I think you WILL need a sophisticated PDF editing app like Acrobat. Several folks have already submitted bug reports to Apple about this. Let's hope they get the message and fix this in the next update soon.
  14. Cool. Based on what you've said I figured out how to do same in Acrobat Pro 9. Thanks so much. Why it is that LX is printing that layer and why only Adobe apps happen to show it is just to weird.
×
×
  • Create New...