Jump to content

Squidge1

Member
  • Posts

    36
  • Joined

  • Last visited

Squidge1's Achievements

Newbie

Newbie (1/14)

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

Recent Badges

0

Reputation

  1. Did you watch the video before your response? Your entire response goes around the entire purpose of external effects. A simple internal route either to a buss as the channel output or via a send is the way to bounce your external IO or in real time is general practice. External I/O effects save a lot of time folding out to console whether you agree with that or not is up to you - its horses for courses. In addition ping is rather handy when working with a lot. The type of external outboard is totally irrelevant - its a DA AD routing to an analogue or digital device. The video shows it quite clearly. Im not looking for a run down on what you believe to be good nor bad tbh. The issue occurs as shown when a mix of external IO effect plugs along with a standard AD input is recorded. If you remove the standard AD 1-2 or whatever input in, ithe issue doesn't happen,. Thats not a workaround. In addition if you take a real time bounce of the session - a desk jam - again there are no issues. Its a logic issue, no other daw on the rig behaves like this. it goes without saying OF COURSE routing out DA and then back in AD doesn't cause an issue - but then again thats not what I have asked For clarity the following work: 1. In this mixed situation, when using external IO for tracking through channel strips quickly, if you have a general AD input in the mix as well, wrap that within an external IO and there is no issue. 2. As you say a more manual approach is to manual patch in and out Logic should not behave in the way its shown in the video hence my post. Thanks anyway!
  2. HI All Have a major issue here at the moment and its happening in 10.4.8 and the latest 10.5.1 Im using mono external effects I/o to route the two stems to a mixing console. I then have the channels being sent to sends/aux with the aux output off so we can use the aux as an input to record the audio live without hearing duplicated signal. I also have a direct input into the daw from an FX output on the desk going into input 1-2 You will see in the video the audio shows as being recorded in perfectly but when you press stop the Audio gets totally changed!! see video below I have used another method of simply routing the audio out to the desk via the DA (not using an external FX) and then set up Audio channels to record the desk direct out channel and don't have the problem. I really want to use the method of external FX as its so quick to drop out to the console Really stressed and cannot find the issue - it has to be a preference as I've tested it to death in Ableton and we can record perfectly every time.. https://youtu.be/o4dgfdvyr9Y any help much appreciated as going round in circles here.
  3. Hi All Im running two systems of 10.4.8 on a Mac Pro with an LG4k apple monitor and also on a MacBook Pro and I'm getting logic screen display issues which are number parameter boxes which won't disappear until logic closes. Is this a known issue? Thanks
  4. very interesting will look at this
  5. Hi Guys having an issue since upgrading to 10.4.6. We use a hardware device called an ERM Multiclock which we have used for sometime. Basic principle is the ERM has a plug in which sits on a software instrument channel and sends a tone via designated outputs to the hardware device which then sends clock to drum machines etc. We have been using the unit fine until 10.4.6. The issue is the software instrument channel with the ERM plug in on it within logic seems to fall asleep and not send signal. Example if we have a project template with the clock set up on a software instrument channel and go to work on the project it will be in sleep mode, if we simply click on the channel it wakes it up. We also have seen some instance if you drop on certain parts of the arrange screen the clock channel does not keep up It could be an ERM issue however wonder if its logic bug? Thanks
  6. Yes I'm sure its a bug now. I have tried 10.6.7 on a separate system and its the same ....
  7. Hi All Within 10.4.6 whereby logic have implemented a similar midi clock and delay system to Ableton. You are able to now send clock to as many areas as the devices you use and set delays. This saves per project and not as a global preference. I see in the left hand corner there is a save a default option however its greyed out no matter what I do, is this a bug or Screen shot attached,
  8. Yes. you have solved it just tested and that works a treat - thanks David !
  9. Ah ok could this be it? Im just testing with bounce in place and when you do that with the new channel fader set to zero the stem plays the correct volume. this is a time consuming way though
  10. I just want a direct duplication of the project - just audio stems.
  11. Why? What's the goal of that procedure? Have it mixed by someone else or with a different software? yes to be used on another logic system without plug ins Can you describe the exact export procedure and your export settings? High lighting all channels (audio and aux/busses), file/export "x tracks as audio files". normalise not selected nor any other by pass etc
  12. Hi There I have a project im working which I need to export all stems in order to have a project with just audio tracks and not plug ins used in the original project. I tried to export all selected audio files whereby each channels faders were at different levels etc (as per normal). When I imported the stems into a new project the mix is not balanced mix wise (levels) like the original project (no master channel plugs etc)- I effectively just want a project with the audio stems which sounds exactly the same as the main project. As fair as im concerned in the new project I open and drop the stems in, all the faders are at zero and that should play the stems level as it was bounced??? or do I need to drop every fader to what the corresponding channel was that created the stem help!
  13. If Auto Input monitoring is checked, and you press play, you can't hear the signal on a "record-armed" track. You have to be recording to hear it. That's why I always have it unchecked. Ah ok. so our issue happens when the track (external I.O synth in) is selected but not "R" and elsewhere in the project "R" is activated on a few tracks. Sounds like this is the cure then?
  14. Is Auto Input Monitoring unchecked in top menu under Record? What should it be ticked or unticked? Im our situation we could have 10 external synths playing in which we want to monitor
×
×
  • Create New...