Jump to content

brentmagstadt

Member
  • Posts

    28
  • Joined

  • Last visited

brentmagstadt's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I did poke at that as well. I'll see what Apogee comes back with and update this thread. Thanks!
  2. David, thanks for the prompt reply - much appreciated. If it were the specific to the Quartet, wouldn't it happen with other audio apps? Like iTunes etc? I haven't had a chance to even krack open logic since I installed this Quartet a week ago; yesterday was the first time, and immediately I'm seeing these issues, which leads me to believe it might be the interaction between the two that is causing the problem. Is it possible that midi instruments in a previously saved project could cause this conflict/kickoff? Is there a possible setting in Logic itself with the I/O that I can set and save? I did log a ticket with Apogee, fyi... though it doesn't necessarily seem specific to the quartet, but rather the interaction between Logic/Quartet. Any other ideas I might poke at??
  3. - Upgraded from OS X 10.8.5 to 10.11.14 - Successful - Upgraded Logic X from 10.0.0.2 to 10.2.2 - successful - Purchased Apogee Quartet,and downloaded/installed Maestro2 software (v2.10.6) - Selected Quartet in System Preferences - Sound for in/output - Looked in Audio Midi Setup, Quartet is found and looks normal - Open up Logic and everything seems normal in Preferences (Quartet found) - Same for the Env - Quartet found - Open a project and Quartet gets kicked off, previous interface selected, logic message: 'changed number of midi inputs/outputs to 1' (since it bumps onto default core audio). OSX preferences no linger show the Quartet, and same for the Audio Midi Setup. I can then open the project, using core audio, and reboot the Quartet (physical unplug/restart), and is it again found in Logic Preferences and shows up in the system dialogs as well. Then it's possible to play the project, using the Quartet. Save/close the project, close Logic. Fire up logic again, select project in most recent, and Quartet again gets kicked off! What am I doing wrong? It feels like an I/O conflict of some kind, but I haven't been able to directly locate it. Any ideas why this would happen?? Please share! Getting slightly frustrated. Thanks in advance. -- b
  4. Here's notes and a workaround for dealing with non-interleaved stereo files (per the bug located here:http://www.logicprohelp.com/viewtopic.php?t=4488 )... for those of you still on v8.02. Note that all of the below should be performed in ONE SESSION. - slice and dice the track regions and move them into the master track for that instrument (drum overhead sliced up and all regions moved into master drum overhead track, for example). Be sure to make cuts on known timeline entities, such as bar or beat (I used bar). - For each stereo track that may potentially cause a problem, use No Overlap, and move the cut to exactly where it needs to be. - Crossfade the cuts as needed. - File > Export > Bounce the stereo track (or tracks) This results in one file that you can bring into a separate stereo track. Note that when you save close and re-open you will see the Unequal error - it refers to the cuts and crossfades made on the original master track. Specifically it seems the error happens to the stereo non-interleaved files/regions when the moved region length is changed (which is consistent with the bug report entry above). I actually bounces all my drum track takes into single comprehensive files. Since I am at the beginning of this project, it's simple to do now. I then created an entirely new project i a separate folder structure, brought in the bounced tracks, and ended up with a very nice drum comp and no misc garbage hanging out in the audio bin (and no unknown errors flying across the screen when I open my project). I hope this helps... -- b
  5. Hey all, I've brought in drum takes of song I'm working on - 11 total tracks, 3 of them are stereo (1 set overheads, 2 sets rooms). I made cuts on bar lines where needed and carefully comped out a master drum track, snapping all to barlines. It sounds great, just what I wanted. I saved the file and went home. Came in this morning, opened the track, and began assessing each cut, cross fading, cleaning up (using snap = samples) individual tracks. I got halfway through (7:40 track length, fyi), and got interrupted. I saved, and before I closed the file, I listened to all the edits from the beginning to well past where I had just stopped (and of course I check each cross fade minutely when I do them, also). I did not shut down my box, even left all speakers etc on, as I was planning on resuming shortly. When I closed the file, I also closed Logic (v8.02). Upon return, I opened logic, and opened the file again and received the message: "49 unequal stereo regions corrected" (OK). I've never seen this before. I reluctantly selected OK (no other options) and opened the file. I listened from the beginning and it seemed fine, until, at one point, it started sounding... weird. Like, sort of out of phase-ish. I dug in to the stereo tracks and started solo'ing them and sure enough they somehow changed. They no longer match the rest of the tracks. Note that this occurred before the end of my last crossfading session. I closed (without saving) and re-opened and received the same. What did Logic do? How can I fix this? Any thoughts very much appreciated. -- brent
  6. I'm sure this is very basic but I've just bumped into it for the first time, working over the wire. - defined project and sent file (click track) at 44.1kHz - percussionist played to it, sent back his files at 48kHz - brought his files back into project, but now all are faster than defined tempo. (I've noticed that pitched instruments sound higher, as well, in this scenario.) My obvious question (backed by an extensive lack of extreme audio technophile experience) is... why do sampling rates change tempos and pitches when down sampled (in this case)? Like I said, I'm sure this is basic, and I've looked around a bit here in the forums. If anyone can lay out the basic laymans answer, I'd be grateful. Thanks in advance! -- b
  7. Hey everyone! I'm looking for some good bassoon samples for the ESX24. The standard ones just aren't cutting it for me at the moment. Any help appreciated! -- brent
  8. I'm not able to see or load this in logic 8.02. I've placed the sdir file into /Library/Audio/Impulse Responses/Apple, per the manual on page 172. I've looked around and the only impulse response folders I have are either the above, or on a project by project basis. I'd love to check this one out - any advice? Thanks! -- brent
  9. Same - slight give, barely noticeable. Has not affected performance in any way, for 2.5 yrs.
  10. Hey all, I am running a Boss GT-10 pedal board for my guitar, set up to send USB/MIDI. My laptop (a macbook) recognizes (in system preferences) the input source and there is strong input signal. I have my output set to my Apogee Duet. I can successfully communicate from my laptop to the GT-10 through Logic, but am generating no sound on the Logic side. My intent/goal is to record direct from my GT-10, using its on-board sounds. (I know I can do this via the 1/4" outs, but I'm trying to learn about this aspect, as well.) The problem somehow lies in Logic not recognizing the GT-10, in terms of track input level, and out to the duet. Here's a list of params: GT-10 midi setup: - Receive Channel: 1 - Omni Mode: On (msg's received on ALL channels) - Transmit Channel: RX (meaning this value is the same as the receive channel, it can be set to a diff #, which I have also tried) - Device ID: 7 (Transmit/Receive SysEx msg's) Logic Setup - Project Settings > Midi: SysEx with Midi (unchecked, but have tried both); Inst w/out Midi thru (no output) - Create new external Midi track - Arrange displays as GM Device 1. GM Device 1 exists in the Env as well (as does the GT-10 Multi-Inst) - In Arrange, Reassign Track Object > Midi Instr > Boss GT-10 > Channel 1 (prg 0-11) - Inspector now shows Port = BOSS GT-10, Channel = 1 - Selection of the program checkbox effectively sends a msg to the GT-10 and changes the patch. So this direction of communication is happening. - Set the track to Record enable and play: No Sound input to logic, no track levels. I have played with the Port, Channel, and Program settings in every way I could think of. I suspect the answer lies within the Env window, but seriously, any/all thoughts or suggestions are appreciated. I'm definitely a Midi newbie, and this learning curve is a little steeper than I expected. In advance, thanks! -- brent
  11. I'm curious about the process other people are using for drum edits, once they've completed them and are moving forward. Here's the situation: - 10 tracks of drums, performed edits on them where needed - Each track now has cuts & crossfades I notice Logic takes a performance hit when there are a lot of edits on tracks. I'm wondering about the best route from here with the drum tracks: - Should I bounce each drum track to a single file, before I move forward? - Additionally, do I want to bounce them with processing (gates, compression, EQ)? We're ready to begin our overdubbing process, with many tracks to go. Hoping for streamlining. Thanks for sharing and any thoughts appreciated! -- brent
  12. Searched for this with no luck - posting.... - Tracked drums to a click, with scratch guitar and vocals, exported OMF - Imported OMF, and using SMPTE lock set the tempo - it matched perfectly with the imported click track. - However, the drummer is slightly behind in a few sections. I know I can go in and cut this up and align everything and be all happy, but... that's a bit of work. Is there a way I can essentially quantize, for example, the bass drum audio track to the current tempo ticks based upon where the drum hit is, and a resolution I select for quantization (qtr note, eighth note, sixteenth note etc...)? Thanks in advance for any advice... -- brent
  13. Thanks Steve - SMPTE lock works like a charm! -- brent
  14. Searched, did not find, posting.... I'm bringing in an OMF file from an outside studio, into LP8 here in our studio. The recorded tempo at the outside studio is 140bpm (4/4). The default in Logic is 120 BPM. In this take there are a couple of punch-ins midway through the tune. After importation, I set the tempo in LP to 140 BPM. The problem is that the punch in tracks (which do not start at time point 0:00) have now moved in time with the tempo adjustment in logic to my new setting (140 BPM). The tracks that start at 0:00 have not moved (obviously). I suspect that I can set the tempo prior to the import and it may work - it's my next thing to try. (I will post if successful.) But I have already imported many files, and am hoping for a short fix, rather than a long one... So, does anyone know if there is maybe a snap setting or some other config switch that I can tweak to prevent these non-zero entrances from moving in time, based upon the logic tempo adjustment? Thanks in advance -- b
  15. Couldn't find it, so posting this question: - Just finished tracking drums recently at friends studio for a dozen+ songs. All are recorded consistently. - Exported files into OMF. - Dumped first OMF into our studio (LP8). - Got a solid mix going of drums only. Each ch-strip tweaked to our liking, using various signal chain permutations for specific drums. Not currently assigned as a Group, but certainly they will be shortly as we move ahead. - Saved project - Imported second OMF file into next song project file. The Question: Is there a way to export my Drum Mix from the first project, then re-import it into the second one? Notes: - I know I can do this via individual Channel Strips, but I'm hoping for a single or double step process, not a channel by channel process. - Not concerned with exporting busses along with the drum mix (though if they go, all the better) Any thoughts on streamlining this? Thanks in advance! -- brent
×
×
  • Create New...