Jump to content

edocura

Member
  • Posts

    38
  • Joined

  • Last visited

edocura's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Got it. Thanks fuzzfilth, I was getting turned around and looking in the wrong place to fix it. Got everything going now.
  2. I have a LPX project that I use to run backing tracks for a live set. Live, I use an USB interface (Behringer X32 rack) and everything works well - I select what LPX channels I want to output to whatever X32 ins, and it works as expected. I have a few channels - click, backing track, etc. At home, I use a couple UAD interfaces - an Apollo 8P and a x8P (which I just recently got). If I opened the project at home, any tracks that were sent to the X32 are automatically sent to my interface stereo out without me changing any routing at all. This is super useful so I can practice the set at home without mucking with the outputs every time. However, I actually have no idea how this is set up - basically how does LPX handle channel outputs assigned to a specific interface if the interface is changed? The channels still show as being outputting to the same channel numbers (e.g. Output 20, the same x32 ch i had assigned to it) and I'm seeing behavior where some tracks automatically are outputted but a couple aren't. I'd like to fix it, but since I have no idea how to set it up, I don't even know what settings it would be. The thing is that I just recently got an x8P and then started having the issue. I'm not sure what the settings were before hand to compare it to a working state - it could also be some weird routing in the UAD control panel I suppose (I see input in the virtual 2 channel in the UAD Control 2.0 app, albeit no outputs from LPX send to virtual 2...). Any ideas of what to try looking into? I've been hunting around for a bit but came up with nothing so far.
  3. Atlas, sorry, I was trying to be a little more generic in my explanation. What I’m doing is technically not triggering a patch chance on the AxeFx3, I’m triggering “scene” changes within a single patch, which requires CC. A “scene” is basically a specific configuration of the preset itself - so I could have a preset with a specific chain of effects or amps, and turn those on/off. If you’re not familiar with - and I didn’t want to assume people would be - the closest approximation is something like a patch change I suppose. I’m not super familiar with the Chase settings. I’ll take a look. Still, not sure why the output channel would change that behavior either way though.
  4. I'm seeing some behavior in MIDI out messages that I just don't really seem to get and want to understand. The context is that I'm using Logic to run some backing tracks for live gigs and I'm, on top of the backing tracks, I'm also automating some both some patch and parameter changes for my guitar amp (AxeFX3) through an external midi track. I have CC messages assigned that do different things on the AxeFX3 (ex: CC 102 controls Input volume, so I can use it like I would use a volume pedal, CC 34 controls patch changes, etc.) In my MIDI track, I have a region that has all these control messages. At the beginning of a song, I start by going to a "Mute All" type patch as a default state then I do whatever patch changes are necessary. Explicitly, this means that the first thing in the region is a CC34 message to switch to the mute patch. Then throughout the entire length of the track, I throw whatever CC34 messages I need to change to whatever patch I need. If I start from the beginning of the region and play through each patch change, everything works properly. So far so good. Here's the weird part. If I click somewhere on the timeline mid region (in the middle of a song for instance), I'm getting different behavior based on what the "MIDI Out Channel" option is set to in the track properties. If I have that set to "All", it throws whatever is the closest CC34 messages that comes before the current position. This is awesome, so if I have to practice a section of a song, it loads the right patch automatically. If I have the "MIDI Out Channel" set to anything else (ex: Channel 1), it seems to output the very first CC34 message (or, at least, it gives me CC34 with the "mute all" patch) Further, if from that state, I let it play until there's another CC34 message to patch change, that now doesn't actually work. Not sure if this is a bug or I'm just missing something. My AxeFX3 is actually using channel 1. All CC messages are being sent on channel 1. Why would the behavior change if I set MIDI Out Channel to "All" instead of just being more explicit and set it to channel 1? I'd like to err on the side of being explicit in case, later on, my other guitar player also wants to do a similar automation but use Channel 2 for example. Yes, I could set both mine and the other guitar to all and manage the channels in the CC messages themselves I suppose, but if I explicitly set my automation to channel 1 and his to channel 2, less things could theoretically go wrong - or at least it feels more compartmentalized.
  5. Looks like the axefx may be the culprit. I’ve been reading other forums where it can send some weird midi messages and has the same ta horng ID and such. I’m still really confused about how it can record midi messages over and audio track that’s not even armed. How does that work?
  6. Yep, restarted computer. I did have it unplugged before and still had the issue I believe. I'll try it again later this evening to see if I can repro with it off. It's random though unfortunately.
  7. I don't remember exactly, I think a few of the projects. I've been working the last couple of days on this one again and it's been doing it nearly every time. Then it stops for whatever reason, and then starts up again randomly.
  8. This has been happening for a while but I figured I’d ask now. I have 2 tracks that I’m recording - 1 for my j48 DI and one for my amp. I’ve been tracking section by section through a song. Each section is 2 tracks (I duplicate them for each new section). Everything seems to be ok, but I get random midi events recorded at the same time on earlier tracks. Check out the screenshot to see what I mean (I may be using incorrect terminology). The bottom two tracks are armed, but the previous 2 aren’t. I did a take on the 2 tracks and recorded the audio. Once I stopped, I noticed that the green region was added to the previous di track. Looks like it’s full of sysex messages and the info in the event viewer has “ta horng musical inst.” something is sending this but no idea why, or why it’s always the previous sections di track, or why the midi region different lengths every time, etc. I didn’t even know you could record midi over an audio track. Any ideas?
  9. Hello, I'm playing around with some drum mixes today. The general issue I'm having is that it seems that sometimes muting/soloing tracks doesn't seem to be doing anything. For instance: I'm using Superior Drummer3, with multiple outs. I have separate outs for kick, snare, toms, hats, spots, and oh. I'm playing around with 2 reverb busses, one for the kit and one for the snare. I mute all the reverb busses. I still hear reverb on the track. Weird. I disable the bus send - still hear reverb. I disable the bus send, mute the aux track, and lower the fader completely. Still hearing reverb. Earlier in the session, I had to completely reload the plug in for this to stop. I rebuilt everything and now it's doing it again. I'm still not 100% used to LPX soloing behavior (for me, Reaper is much more intuitive here - but it's just bias I suppose). Certainly possible that maybe I'm misunderstanding something. But I've muted every track, I see the channel doesn't have audio going through it, but I'm still hearing the reverb. I'm guessing it's a bug (or I'm going insane! ) Are there situations where the UI lags somehow and doesn't update the audio engine perhaps? Reaching in the dark here, but it seems so strange.
  10. That's an odd way to phrase it? I would say that to save channel presets, you save them as a patch. The way you phrase it makes me think you wish it were working in another way? You could also click the Settings button at the top of the channel strip and save a channel strip setting however that's an antiquated way of doing it and not as elegant IMO. You're right, I think I just have a different working model in my head - combination of being new to Logic and not knowing enough about the differences between patches, channel settings, and how those correlate in how other daws do similar things. The documentation doesn't seem to provide any specifics to how it actually works in the backend (maybe it's just a style thing I'm not used to though) so I'm just adjusting all the terminology in my head as I learn more Logic specifics. I played with it yesterday, and it looks like I'll have to do the import method and then just copy over the regions for now. A common use case for me is a multi-out from a drum VSTi, so I have multiple channels, aux, and so on that would have to be in a patch. From the testing and reading I did, I need to use summing tracks to get it to work and it's a little bit of refactoring from how I'm working now. It's good to know, and sounds like a clean way to go about it, in the future when I'm not in the midst of an album. Just being verbose here in case it's helpful for someone. Thanks for the help David!
  11. Thanks David! Gotcha, so you can't really save channel presets other than making them a patch or so. Looks like the patch process is probably what I want. I'll dig into it more and test it out. Thanks again!
  12. Another thought - if there's no easy automatic way, is there a way to load plugins without loading all the sample libraries? Kind of loading them in a "safe" mode or something. That way I could potentially just open up both projects at once, and port things over manually. Right now, that's really really hard to do since I have a lot of large sample libraries in each project and things like the Play engine are rickety already.. I've ended up with weird behavior/crashing in the past when I've tried it.
  13. Hi everyone, I know that this has been discussed a lot in various forms (across many DAWs, and space, and time...). I'm specifically looking for some helpers to my workflow and not necessarily debating the workflow itself. I haven't found anything specific that would work in the research I've done, so thought I'd ask here. To set some context, I'm working on a symphonic metal album with ~10 tracks. Said tracks include VSTs for the orchestra pieces, drum samples, and the like. Because I'm programming them, I don't have to worry about differences in the recording process - they are consistent across tracks. I have some templates for the audio tracks that I've done to make things easier when starting each track. Easy enough. What happens is, after all the work (tracking, programming, etc.) is done I (obviously) start mixing it. After the first track, I have a general idea of how I want the production to sound and want to use that as the basis for the album mix. At this point, what's the best way to "share" that mix between all the other projects? Again, the idea is to shape the production mix to how I want it in the first track or two, and then use that as the common starting point across the tracks to keep them consistent. Since all the projects are already created, updating the template wouldn't do any good. I don't want to recreate the project because they each have their markers, tempo maps, time signature maps, etc. Is there some way to share settings for channels / groups of channels across projects? If I update the project template, can I then import parts of it into each track and basically copy/paste the work into the newly imported channels? Generally, what's the best workflow here?
×
×
  • Create New...