Jump to content

yks

Member
  • Posts

    48
  • Joined

  • Last visited

yks's Achievements

Apprentice

Apprentice (3/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

1

Reputation

  1. Thanks for the suggestions everyone, I made a couple of IAC busses and things are working for my immediate needs! I will update Logic sooner or later.
  2. I will try the IAC suggestion since I don't need to record the MIDI, it's just for a live performance application.
  3. Good suggestion. I should have said, I already tried that, and it does not maintain the MIDI flow when the tracks get unselected. That surprised me greatly!
  4. I am using MaxMSP to send continuous controllers to a couple of instruments in Logic, on two different tracks. The instruments have XY graphic controllers so I made my own wandering LFOs to move the X and Y values. The problem is, the MIDI is only received by the tracks when they are selected, and I can't figure out how to maintain that focus when I want to go to record on another track, for instance. I want the LFOs to keep the plugins moving, but they stop when the instrument tracks are deselected. Can I use the MIDI environment to set up a permanent routing to the two tracks perhaps? Thanks for any suggestions.
  5. Thanks, for this week's episode I went to this method and it worked just as well as manual automation. I tried out the gate in the 'Neutron' series from Izotope, which worked very well.
  6. Hi folks, this week's update: I'm working on the next episode and I did spot bounces for each scene. There is one scene in this episode which runs for quite awhile, like 10 minutes. The automation is out of time by the end of the 10 minutes.
  7. Hi again folks, I tried the deleting all audio regions (without deleting automation) and restoring. For some reason I didn't think that would help me, and it didn't, but it was worth trying. I did another bounce of the piece in order to test this, so I excerpted clips from the two parts of the piece I already shared, so you can hear how the character who is not on the phone is being cut off early. The person on the phone is not being cut off, so their automation has not been affected, which is interesting. The two clips together are about 35MB as a WeTransfer - https://we.tl/t-9NWeMIl4Au
  8. Good things to try... do you mean removing the audio files entirely, from the Project Audio altogether, then restoring? I will certainly try the easier approach of deleting audio regions in the arrange window, and then doing an undelete. Looking at the track automation folder data for the obvious problem areas shows nothing unusual.
  9. That is what I expected, having done the same bounce of the reduced session, and also I heard no issues. Thanks for trying! I would share the whole session but it's not really mine to share (this episode is "airing" as a podcast on Thursday).
  10. Thanks RobertAnthony for offering your experience which sounds very much the same as mine. It did also occur to me to try erasing and re-doing all the automation for the areas where there were audible problems, and to see if Logic then picked it up correctly. I haven't done that, since it's painstaking work and I don't have time but your experience suggests the key to the problem might be found here. It is interesting to know that you found a re-do of the automation fixed the problem in your case! cheers, MR
  11. Let us call it "shifting" then. But it's happening -- sometimes -- and it seems to me it's when Logic does long duration bounces, and it seems to increase over time so I actually think "drifting" is also an appropriate word. I already described to you how everything else remains locked in place but the automation moves. I am not sure of the precise circumstances that need to exist but my experience suggests that the more complex a project, and the longer and more complex the bounce region, the more likely I am to have this happen. Personally I managed to finish my current large project by addressing each of the scenes of the radio play individually as track stacks and exporting each scene separately. I assembled a master track crossfading these scenes. As I say I have worked on many large projects and I have favoured Logic to do this. The fact that Logic is behaving badly now is dismaying to me because I have relied upon it and enjoyed using it. I may continue to use Logic for the next episode of this radio drama, but I will assume that I have to follow this workflow that slows me down, which also has to include checking every track manually to make sure it is correctly bus-assigned when dropped into a track stack - I have found I cannot depend on that either. As the host of this forum says, that is a second issue which I don't want to derail discussion of the other problem. cheers, MR
  12. I believe I already said, this is the entire session with only audio files removed. Everything else is in place.
  13. Caveat: I did a NRT test bounce of the full length of the reduced session linked below and despite that there were major problems in the bounce of the full session, there were NO VOLUME AUTOMATION PROBLEMS FOR THESE SCENES. I can only guess that having removed the other files from the project, it changed the complexity of the bouncing situation. I am interested to see if you can duplicate the volume automation timing problems but am guessing this test session is not going to help you hear that, and I can't share the full session because it's not my IP. I am supplying a link here to a WeTransfer of the session which includes all the tracks and automation but only the audio for dialogue which was affected in two scenes, both of which involve one person heard on a telephone. The scenes begin at 22:09 and 29:28. I am using plenty of third-party commercial plugins and also my own impulse responses with Space Designer, but you should be able to open this demo session and see dialogue for the two scenes way down at tracks 97-98 and 128-129 (screen shots attached). These tracks are part of scenes defined as track stacks. WeTransfer link (69MB): https://we.tl/t-NPGYf7wsE5 Thanks for any comments!
  14. The automation is volume + FX parameters -- reverb dry/wet mix balance changes for instance. Nothing unusual or particularly complex. In some of the radio play scenes I am working on, there is dialogue between two characters which was recorded without good isolation, so I am manually "noise gating" with volume automation (one of the characters is on the phone so there is a radical tonal difference, thus any bleed is to be avoided). The automation is cutting very close to the dialogue so any drift is very audible. I am hearing LOTS OF DRIFT when doing a full-length bounce of the master mix, and also when trying to bounce all the short scenes individually, by selecting them all and trying to do a BIP for all. In the latter case Logic started at the beginning of the session and gave me back a single long WAV (not what I expected since I had rendered many individual scenes, which were their own unique regions, and unique regions should I think result in separate bounces). The timing of the automation was off starting around minute 12. My latest strategy, which seems to be working, is to manually bounce each scene (they are each defined as a track stack, so I put an empty MIDI region on that lane to BIP it). Logic seems to be OK with short duration bounces and all the automation stays in place. Or maybe it is already starting to drift, but the amount is negligible.
  15. Dear Polanoid, I am looking for this other reason, but none seems to exist. The software option which should solve this problem (checking the box in Audio Options for sample accurate bouncing) does nothing for me, unfortunately. In my session, the audio regions remain in place, just as you are suggesting to do with a MIDI event (I am not needing any MIDI elements in this session). But the volume automation is very definitely off, in relation to those audio regions.
×
×
  • Create New...