Jump to content

snattack

Member
  • Posts

    24
  • Joined

  • Last visited

snattack's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Thanks, I'll check ut Expert Sleepers plugin, didn't know about that one.
  2. It does the job, I've got two and they both work without issues. The autobank-issues are minor compared to what you get. Unfortunately I have to sell mine now since I'm moving to Nuendo, which doesn't support autobanking. EDIT: To consider if you're mobile is that the motor function requires PSU, it does not work with power over USB.
  3. It does work the way I mention above. I've used it on a couple of project in my experiment template using a multi timbral VEP instrument. It is not possible to assign a delay to the AUX tracks. But the instrument track that the AUX tracks belong to will forward it's delay to the AUX tracks. So all the AUX will have the same delay. Individually won't work as you say, there's no option for it. Or rather, it does work 70%. In practice it sometimes stop forwarding this, until record enabling the AUX track. And the behaviour is erratic. The workaround is to use beat based delay on the regions rather than the tracks. But that's a very blunt workaround that requires a lot of manual work, and merge:ing regions containing delay will move the midi data when merging with other regions, even if they have the same delay. Which is even more annoying. The reason for mentioning it here – even if it's not directly related to AU3 – is just for people who stumble on this post to take it into consideration before putting their time into creating a AU3 based template. If they need the track delay. I think you mentioned it in another thread, so I figured I mention it here.
  4. Hello, I want to add that Logic has unreliable behaviour with track delay on multi-timbral setups. I don’t know when the bug showed up: An aux track connected as a midi channel belonging to a multi timbral instrument channel should use the delay of the instrument channel it points to. Since it can’t have it’s own delay for some reason. This does not always work. Sometimes during playback the track delay (negative or positive) is simply ignored – until the aux track is record enabled. That will make it use the track delay of the multi timbral instrument. For a while. Then it can stop for a while. Etc. I reported the bug to Apple half a year ago.
  5. It would be useful to have multiple marker at the same positions if both were visible, but if not: I agree. Easiest would be to just not create one. Maybe someone else has a use for it, idk.
  6. There is no usefulness (or at least I don’t see one), I placed two by misstake. But still a bug since the behaviour is different when jumping forward. Since it’s not visible in Logic when two markers are placed on top of each other than the event list, it took me a while to figure out why the jump marker malfunction. When jumping forward it skips one of the markers on the same position, which makes sense.
  7. Steps to reproduce: 1. Create a 1:st marker. 2. Somewhere after the 1:st marker, create 2:nd and 3:d markers placed on the exact same position in the timeline. 3. Create a 4:th marker after the 2:nd and 3:d marker. 4. Place cursor after the 4:th marker. 5. Try reaching the 1:st marker using the "Go to previous marker" key command. 6. Observe how it will get stuck on the 3:d marker. Expected behaviour: Even if two markers are placed on top of each other, the "go to previous marker" command should still work.
  8. My hands are tied here. So I'm using Vienna Ensemble Pro the way I should: as a multi timbral instrument. This is to save resources since Kontakt takes up a lot. But Logic contains so much problems in this regard that I will open a separate thread about this. Anyhow: Having two midi regions with equal delay compensation joined together should not move the midi data, it should instead transfer the same value to the field in the inspector. Now, when I have two separate delay compensated regions on a track, joining them together moves the notes screwing with the quantize settings. Currently, the only way is to first remove the delay, then join, then re-add the delay again. We're forced to use the region delay because of a bug where delay on aux channels are randomly ignored. So – we can't use multi timbral instruments the way they should because of a bug. And the only workaround creates so much work that it's almost not worth it. System: Macbook Pro 16", 64GB RAM, macOS Catalina 10.15.7. Software Version: Logic Pro 10.6.2
  9. Steps to reproduce: 1. Set the value in the Top/Left Delay field if the inspector to a NEGATIVE value that will convert into a note value (example: -180 ticks -> -3/64). 2. Press enter to confim value. 3. Double click the field again. 4. Observe that the value has now changed to -1 ticks and that the value has been confirmed. 5. Expected behaviour: Not to change the value when double clicking. System: Macbook Pro 16", 64GB RAM, macOS Catalina 10.15.7 Software Version: Logic Pro 10.6.2
  10. This is a quite easy bug to workaround, but reporting it anyway. It doesn't show up very often. I use a motorized single fader to control volume of tracks/channel strips. Several times, I've found myself trying to adjust volume without anything happening. Workaround: Select a track with the mouse. This resets the MCU and everything should be fine (until it happens again). System: Macbook Pro 16", 64GB RAM, macOS Catalina 10.15.7. MCU: Presonus Faderport Classic Solo Software Version: Logic Pro 10.6.2
  11. This happens quite often for me who uses Logic for sound design of SFX. I need to bounce and re-bounce effects that I'm iterrating into a game. Steps to reproduce: 1. Work with a project, and bounce things several times over a longer period of time to the same folder. 2. Observe how suddenly Logic randomly looses track of the last "Save As" folder. Expected behaviour: Logic should not loose track of the last used directory. System: Macbook Pro 16", 64GB RAM, macOS Catalina 10.15.7. Software Version: Logic Pro 10.6.2
  12. These steps needs to be done in a fast sequence using keyboard commands. I'm not sure which of these commands trigger the bug. Steps to reproduce: 1. Assign a key to "Go to last locate position" key command. 2. Record something on a track (let's call it Track 1). 3. Select a new track (2). 4. Record midi. 5. Stop. 6. Undo. 7. Go to last locate position 8. Record again. 9. Stop. 10. Undo. 11. Go to last locate position. 12. Keep repeating until Track 1 is selected. EXPECTED BEHAVIOUR: Undoing a recording should never select another track. ACTUAL BEHAVIOUR: Randomly Undo selects a previously selected track. This totally breaks the workflow. System: Macbook Pro 16", 64GB RAM, macOS Catalina 10.15.7. Software Version: Logic Pro 10.6.2
  13. Steps to reproduce: 1. Create an instrument track with a multi timbral instrument. 2. Create aux channels and add as tracks and set tracks to different midi channels. 3. Set a negative delay on the main instrument channel. This should affect the aux tracks as well (greyed out and listed as "Inst" in the inspector). 3. Record midi to the AUX tracks. 4. Work with other tracks, recording, playing back, etc. 5. Observe how randomly the recorded contents on the AUX tracks ignores the negative delay. 6. Record arm the main instrument track and playback again. 7. Observe how the recorded content now applies the delay. EXPECTED BEHAVIOUR: Aux tracks connected to multi timbral instruments should always use the delay value in the main instrument track they are connected to. EDIT: This also happens when sending midi from a summing stack containing the AUX track. Randomly, it's necessary to record arm the target track, otherwise the midi will not be delay compensated. This bug has been reproduced by several users, I recently had a discussion in a Facebook group for film composers about this. System: Macbook Pro 16", 64GB RAM, macOS Catalina 10.15.7. Software Version: Logic Pro 10.6.2
  14. It makes absolutely no sense that this is not currently working. An AUX track can send midi and can handle Articulations. I use the scripter plugin for various routings and manipulations of CC in a large orchestral template. Currently, instead of creating multi timbral instruments in VEP, routing via AUX tracks, I have to create 800 separate Kontakt instances just because Logic isn't able to add the scripter plugin.
×
×
  • Create New...