Jump to content

pinoguy321

Member
  • Posts

    13
  • Joined

  • Last visited

pinoguy321's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Putting a compressor on a vocal will allow you to make the verses seem almost as loud as the choruses. By having a vocal effectively turned down about 8-10 dB at its loudest points (keep an eye on the "GAIN REDUCTION" meter to let you know) yet pretty normal volume when it's quieter during the verse, it will seem like the chorus vocals aren't as BLATANTLY louder than the verses. Use the threshold to make the compressor work MORE (lower threshold) or less (higher threshold)
  2. If you use Delay > Sample delay on just one plugin it will do this for you. No need for a second
  3. This has happened a few rare times in LPX but when it does it completely destroys my ability to work in a session. What happens is for some odd reason... logic randomly goes into Step Input Keyboard mode... where any key I press acts like a MIDI input. I'll be working on an audio track, hit space bar for logic to play, but instead a Midi region will appear. trying to use any other key commands at this point (C - cycle, a automation, etc) just don't work, they act like I'm using my keyboard as a Midi controller. If I open the piano roll, click Midi out on and off it suddenly works again normally... until I pause the song, where I then have to turn it on and off again. I've looked everywhere for some way to disable the step input keyboard, but I can't seem to find it. No midi controller plugged in, CMD-K keyboard isn't on my screen or being utilized. Please assist
  4. Very self explanatory. As I duplicate vocal tracks to lay down harmonies my ram increases almost exponentially. Less than 10 tracks in the season with maybe 6 using flex pitch led to 10.6 GB of RAM being used. This has happened before and can hold everything up as I have to restart and just hope I have enough time to finish the session without it bugging out. Anyone else have this kind of huge RAM gouging?
  5. Just finished a session tonight and I have to say once again my system is put on the brink due to Flex Pitch. I can't say for certain, but this has happened before... I had maybe 7 vocal tracks, 2 guitar, 1 piano. 10 tracks equated to 10.6 GB of RAM being used. WAY too much for such a small project. For comparison my latest dance track ran 82 tracks no problem.
  6. In logic 9 whenever I would use the CMD+R (Repeat Event) command it would do it in a smart way. I'll give two screen screen shots of how 9 would do it better than LPX Here's the original MIDI I'd like to duplicate to Bar 64 This is how LP9 would make the CMD+R Edit, very useful Here's how LPX Handles CMD+R, not very useful when I don't want to extend the last midi event Here's what setting CMD+R to BAR mode does Ableton's CMD+D is much more efficient to use and I'd rather not have to keep using option+drag to make this happen. Any thoughts or fixes?
  7. Happy to help. A lot of what I do is editing vocals (often somewhat harsher ones than not) so these two are important tools for me. Here's where each beats the other. Flex Pitch > Melodyne: -Transfer: Logic allows you to quickly analyze your vocal track and better yet copy & move that edited region around with ease. Melodyne is forced to *hear each vocal take in order for you to manipulate it. -Dual Pitch Drift: W/ Flex pitch you can drift both the left and right half of the vocal. What this means is that if you want to keep the vocal authentic and avoid getting artifacts and having it sound like it's been tuned you use the drift tool to do a lot of edits. Drift keeps the relative curves the same as you nudge parts of the vocal higher or lower. In Melodyne each "Blob" as they're called can be edited with a single drift tool. In flex pitch when you move your mouse over each vocal slice you can edit both the left half and the right half. This is somewhat tedious and slow at first because you have to use the scissors tool more often to get a good edit. In melodyne you have the ability to quickly drift ALL of your vocals and you will get a better result than in logic... however I consider this a win for flex pitch because editing vocals should be done where needed and with the most accuracy, rather than quickly applying it to the entire take. *If you just want fast and decent, Melodyne's single drift tool wins. If you put in the time Flex Pitch is better here -Tool Accessibility: to do flex pitch edits you can quickly pull up the scissors tool w/ T-5 as opposed to Melodyne where you have to right click... aim... etc to select and change tools. This is a subtle difference but it definitely speeds up the process Here's where I see them tied: -Sound - They both sound great. -Formant Tool - You can change the formant for each, nothing exciting here. Can't say I personally use this tool often -CPU - It seems like Melodyne would lose here due to the fact that you'll have to have an instance of Melodyne open on each vocal, however from just using flex pitch all the time I know that when I start to have 6-10 flex pitch tracks going my computer will behave in the same manner as though it were Melodyne. Mind you this is a fully loaded brand new iMac. Flex pitch has the potential to win here but as it is I don't see my sessions running smoother using flex pitch on the CPU front -Gain - Increasing gain sounds great on both. Here's where melodyne beats flex pitch- -Tying notes together: I can't remember exactly what the parameter is called, but in Melodyne you can edit the transition between two notes. Flex pitch allows you to make these kinds of edits, but you're far more likely to get ridiculous artifacts in logic. Melodyne seems to be very smooth here. -Reliability - Overall you will find far fewer bugs and glitches in melodyne than in flex pitch. Period. Double clicking on a section in flex pitch will bring you to the FILE section and often just send the pitch straight into the ground when you go back to the flex window. Easy undo, but still annoying. I posted here about this recently, but when I have flex pitch going my screen will often jump to a separate section of the song, interrupting my flow and costing 5-10 minutes to fix on occasion. If melodyne doesn't detect a note properly the first time you can quickly just hit transfer and re load it until it works properly. In logic this process is much more trying and difficult. I will say I use flex pitch almost exclusively, so this hasn't deterred me enough to switch, though the combination of all of these occasional glitches is frustrating. -Harmonizing - Very easy to try out a harmony of your vocal by copying and pasting over the same area... then dragging up or down. I love using melodyne for this. Logic theoretically could do the same, however you'd have to duplicate the entire track, a hefty cost for one small harmony. -Editing distance - I find that flex pitch does quite well, however melodyne still wins this battle. I can drop a vocal much farther in melodyne and get away with it than flex pitch. Hopefully you won't be doing too many of those, but when the occasion arises that your vocal is shot to hell and you need to resolve it melodyne handles better. -Polyphonic edits- it's worth mentioning that you can edit polyphonic material in melodyne, but this function won't be utilized more than 3% of the time. Why bother getting a par sounding edit with melodyne than just re-record a guitar or separate vocal takes? Good for cleanup if you have no other option, waste of time otherwise. Overall here's the TLDR -Melodyne will give you great quick results... once it hears the material. It's been around way longer so is less buggier. -Flex Pitch will be faster start to finish 90% of the time. Occasional glitch but the lesser of two evils. I use flex pitch everyday. Used melodyne for years, either will handle the job. Here's a flex pitch edited vocal: [soundcloud] [/soundcloud] Here's a melodyne edited vocal: [soundcloud] [/soundcloud] Hope that helps.
  8. I've been having this issue for a while and have been using a quick workaround but I'm wondering if it's possible to avoid this all together. The issue I'm having is when automation fails to reset during playback. If I were to pause my session in the middle of an automated low pass fade in... then move the playhead to another section where the automation is all the way up... leaving it completely unfiltered I'll still hear the low pass activated, as though the entire track has a low pass filter on it. Same goes for high pass filters. My bass will suddenly disappear when I go back to the beginning of the song. The quick fix is simply nudging the automation while it plays and it "remembers" where it's supposed to be. This gets particularly frustrating when I have several High Pass/Low Pass filters that constantly need to be manually reset by grabbing the automation line and moving it up and back. Is there a button to press anywhere that will make sure that the moment I hit play the track will reflect exactly what the automation is set to, regardless of where I paused at? I already have sample accurate automation enabled.
  9. The issue was within flex pitch, not so much in the arrange area. I could even use scissors normally *upstairs
  10. This has to be hands down the most frustrating thing about LPX. I record a lot of vocals and somehow when I'm using both flex pitch and cycle to edit vocals a solid 30% of the time at some point the screen will jump away from my editing area. I'll try to move back to the area I'm editing yet when I try to scroll back it will jump back to the exact same spot. I'll be actively fighting an invisible force that sends my screen backward or forward 30+ bars. Somehow between mash cycle enabling/disabling, record enabling/disabling, solo/unsoloing, etc it eventually allows me to edit normally... after 10+ minutes of closing logic, opening back up, etc When I zoom out enough so the snapping point is included I'm allowed to edit normally... but the moment I zoom in to where I need to be working. Any thoughts? Also at this very moment my scissor tool is no longer working on flex pitch. Unrelated and have never seen this one before, but not working all the same.
  11. http://www.youtube.com/watch?v=lSg1XkmgomE
  12. For the past few days it's worked fine, but today for some reason when i turned on my mac and opened up Logic, under preferance/devices it only has "built in microphone" and "built in input" as options, Instead of what should be there> Alesis Firewire. I set my system preferences to alesis firewire input, What is going on?
×
×
  • Create New...