Jump to content

Favedave

Member
  • Posts

    25
  • Joined

  • Last visited

Favedave's Achievements

Newbie

Newbie (1/14)

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

Recent Badges

0

Reputation

  1. It's a little hard to tell from your post, but since when you close and open the session, it's fine, you might be having the mute bug. Here's a previous post showing how to deal with this bug: shadowbox wrote: I've searched the forums for a solution to this. I've had this problem in every version of Logic Studio Pro. Every once in a while, sometimes more than others, a software instrument track will just stop playing back. If I hit record, I can play the soft synth, but the recorded track won't playback. The work around is to create new track with same channelstripe/instrument and then move the region to that track and delete the orginal track. It's a pain. is there some reason this is happening and does anyone else have this problem? I just posted this same problem here and on the Apple site. From what we can determine, the problem is a bug with Apple's muting. The track gets muted, but it doesn't SHOW as muted. And hitting the mute switch on and off on the track doesn't help. Try this method of fixing it, it worked for me and others. If it happens to you again: - Close the project file. - Re-open the project file. - You'll notice that the problem region is now muted (grayed out). - Click on the region and hit the "m" key to unmute it. - It should now play fine. This is a faster workaround than creating new tracks and copying everything over. Besides, when I copy everything over, sometimes the new track gets the same bug right away. Please note it is a REGION that gets muted, not a TRACK or CHANNEL. Yes it's a bug, and a random one. No one who had this problem said they had even been muting the tracks before the bug kicked in. It just happens. Please let us know if this works for you. You can read the newer thread on this board here: http://www.logicprohelp.com/viewtopic.php?t=21570&highlight= You can read the Apple thread here: http://discussions.apple.com/thread.jspa?messageID=9226915#9226915
  2. I hope v9 concentrates on bug fixes! Although, *sigh*, I still think Apple should've bought Opcode and used their StudioVision user interface instead of the kludgey Logic one.
  3. How can you do that effect where the whole song sounds like you're stopping a tape player by hand? The pitch drops and it slows down quickly to a stop. I can't figure out how to do that in Logic on the entire mix. Thanks! This forum is awesome -- so many great tips!!!
  4. Good idea, thank you. Uh, "Dragging the division column...?" I do not understand. Columns can be dragged? Wouldn't this affect everything in the column? Are you talking about the event list window or the piano roll window here? And this does not sound musical to me. I do not understand your point here. But anything that would make this monstrosity more musically useful is most welcome! I tried that -- that's awesome! Thanks so much. That made it super clear. The manual (which is very poorly written, hence the huge number of third market tutorials), simply says it's "bar, beat, division, tick." They don't mean division, they mean an increment of a division. To be precise, the eighth note in my case is the third increment of the 16th division of that beat. How they shortened that concept to just "division" is poor design/programming, and manual writing decisions all wrapped into one. (All this with no explanation I can find in a logical place in the manual -- oops, sorry being ironic with the word "Logic" again). Look, I just want to get some work done to meet some deadlines. I don't care about anything else. And when I encounter a company with vast resources like Apple (not the least of which is the user community) which implements poor choices like this -- I vent. They should be chided strongly for not making this program all it can be. At the root of these poor decisions are human beings - programmers who did not think things through. Who likely did not test on musicians who are more musical than mathematical. If you're mathematical, then yay for you - you're covered. But this design philosophy is more exclusionary than doing it the other way. Of course, you might substitute the word "smart" for "mathematical" in this case, an you might not be wrong Thanks again for your helpful suggestions.
  5. Thanks for clarifying! This has to be one of the stupidest design decisions in a long list of stupid design decisions in this program. Changing something in the transport bar will change something in the midi list window? Yeah, real intuitive. Can't the German engineers who thought of this be prosecuted under the Geneva Convention for torture? I am truly stunned every time I find something like this in this program. How the hell did this program survive? I still can't find this in the manual (: Performer and ProTools are starting to look better and better, but I'm sure they have their own idiocies. too. Anyway, thanks for helping me, man.
  6. OK, I cannot figure this out for the life of me reading the manual. I'm sure it's somewhere, but I cannot wrap my mind around it. In the event list, how the hell does Logic number notes in regards to where they fall in the measure? This example is in 4/4 time. If a note fall on the first beat of the first measure, Logic lists it as 1 1 1 1. If it falls on the eighth note after the first beat - otherwise known as "one AND" to musicians - Logic lists it as 2 1 3 1. WTF??? How does the number 3 = 1/8 note? The manual says it's listed as "bar, beat, division, tick." How the f*%@ is "3" a division of an eighth note in 4/4 time? If someone could enlighten me, I'd really appreciate it. I've been using Logic for months and have been avoiding the midi event window because all my pieces were very short music cues, but now I need it. Obviously no musicians were consulted when designing Logic, but I'm sure that's beating a dead horse. Clearly, there are aging german engineers chuckling about how they pulled off the greatest ironic name in the history of software when they got away with calling this "Logic." BTW, for reference, I've been out of music for 10 years, and just got back in 6 months ago. The last program I used was Studio Vision, which was musical, and divided notes in a sensible way. Grrr...I don't want to have to go back to Performer, which was 2d rate and clunky 10 years ago and probably is no better now. Clearly Thanks for listening.
  7. Yeah -- the UAD-1 is NOT supported on Mac Intel 8 Cores. But you'll love it!
  8. I just posted this same problem here and on the Apple site. From what we can determine, the problem is a bug with Apple's muting. The track gets muted, but it doesn't SHOW as muted. And hitting the mute switch on and off on the track doesn't help. Try this method of fixing it, it worked for me and others. If it happens to you again: - Close the project file. - Re-open the project file. - You'll notice that the problem region is now muted (grayed out). - Click on the region and hit the "m" key to unmute it. - It should now play fine. This is a faster workaround than creating new tracks and copying everything over. Besides, when I copy everything over, sometimes the new track gets the same bug right away. Please note it is a REGION that gets muted, not a TRACK or CHANNEL. Yes it's a bug, and a random one. No one who had this problem said they had even been muting the tracks before the bug kicked in. It just happens. Please let us know if this works for you. You can read the newer thread on this board here: http://www.logicprohelp.com/viewtopic.php?t=21570&highlight= You can read the Apple thread here: http://discussions.apple.com/thread.jspa?messageID=9226915#9226915 If you go to the Apple thread, ignore all posts by a user named fermusic -- he's an idiot who only confuses the issue. I'm soooo glad he doesn't hang out here.
  9. Uh thanks. I just wanted to log out to see how my profile appeared to other users. I'm not leaving the forum -- I am too full of ignorance! I need more answers to questions I don't even know I have yet.
  10. Yeah, music is all so subjective. I mean, *somebody* buys U2 albums, and they literally make me ill. Seriously, I get physical twinges of revulsion when I hear their music. The incredibly narcissistic self-idolatry in that guy's voice is like an audio version of a skunk's smell. And I was talking to my friend who had once-in-a-lifetime tickets to see a famous opera singer in an intimate setting and asked if I wanted to go. My reply: "Opera? I love the music, and the stories, and the grandeur, and the ballet interludes, and the sets, etc. I love everything about opera...except the singing." U2 and opera = both physically painful to listen to for me.
  11. I really like that section that bothers you. I found it refreshing and cool. Moves things along and builds tension. Just goes to show ya.
  12. Thanks RichardSX90, I'll check out those threads. EDIT: I checked them out. Interesting. I did a search on "ghost" and I saw those threads but since my bug is only on MIDI tracks, not audio, I didn't think it applied. And the one that's about MIDI tracks used the word "burp" to describe it, so it didn't show up in my search. I searched under "ghost" and "false" and "midi note," but not "burp." "Burp" is actually a really great way to describe it! Thanks for the info -- but I was concerned about playback, not bouncing. But that's good to know! Anyway -- YALB. (YALB = Yet Another Logic Bug).
  13. Well, that's the purpose of religion - to rigidly force you down to size, so you can't think for yourself. Sorry -- couldn't resist. p.s. couldn't watch video -- I'm allergic to being forced.
  14. Once I checked "log me in automatically" I can't seem to find a way to ever log out of this forum again.... Any clues?
  15. I have this bug, too. Happens all the time. The only workaround for me is to close and reopen the project, then un-mute the now-muted track which was not muted before. YALB! (Yet Another Logic Bug).
×
×
  • Create New...