Jump to content

Simon R.

Member
  • Posts

    522
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Simon R.'s Achievements

  1. Right, because I don't use Logic 365 days a year, I only found out recently, when I was starting to prepare for a new project. I assume the developers/testers use it on a fairly daily basis.... 😉
  2. Well, someone else could have reported this, or the developer team could have caught it and fixed it inbetween 10.7.9 and 10.8.1. I really am quite surprised this has been going on since around 10.7.5/6 (I tested with .6, I think it's also there) and nobody complained much. But I guess I am in a minority group using Logic with multitimbral instruments, since I work with big orchestral templates and such, so that's what makes most sense.
  3. Seeems you have all versions of Logic? 😆 Can you hook me up with 10.7.7 which shouldnt have the rename issue, please? Would be great!
  4. Yes I saw that as well yesterday and thought it was me who had made a mistake. But the "Inst 2" IS actual another, discrete instance of the same plugin. It is not just a "ghost copy" of "Inst 1". But seems like it is created by error (bug) maybe under specific circumstances as you mention.
  5. It ACTUALLY seems like to be fixed in 10.7.9 (and apparently in 10.7.1 as well as you tried). I can't reproduce either. I tried in 10.4.8 and there the bug is present, but not in 10.7.9! Great! Unfortunately they then re-introduced the renaming bug instead. So pick your poison 🙂
  6. I didnt report much. I probably reported more stuff waaaaaay back but I don't recall exactly what. I just know that this issue was there for several years (and might still be, haven't checked in 10.7.9 yet) and nothing happened. And I think it's a relatively big thing that you end up with several conflicting CC data sets on different MIDI channels in the same region. If you really want to dive back into this, I will create a new walkthrough to replicate it.
  7. I think the main one that I reported is the "MIDI CC data gets recorded to several different MIDI channels in the same region/same track when in MIDI merge record mode" bug: I don't think that one was ever fixed. I have hardly used 10.7.9 yet so I am not 100% sure but I will find out soon enough.
  8. Do you have 10.7.7 lying about?? I would be very interested in getting hold of it if possible 🙂
  9. I know you can't officially. But e.g. I have 10.4.8 lying about. Maybe someone has a collection of older versions of Logic for download hosted somewhere...
  10. I have never had anything I reported fixed. So I am not sure if their official bug form is just a black hole.... But I will give it a shot.
  11. I am trying to find a way to roll back from 10.7.9 to something a bit further back before the channel strip naming bug was introduced. Is there any resource for this somewhere....?
  12. I just tried the same thing in Logic 10.4.8 (only other version I have), and here it works as it should. You can rename channel strips independently from MIDI tracks! So this bug has been introduced fairly recently. I was working in 10.6.x for a long time and don't think it was there either. I think it happened around 10.7 for sure. Just a question which version it happened to.
  13. Well, as a starting point when you create a new multi, the problem will be MIDI Ch 16. I am not at the computer now to test, but I believe that if you delete track 16, the channel strip will now just take its name after track 15 instead. For a moment I thought maybe I could "fool the system" by creating a copy of the 16th track and then hide the one that gives the channel strips its name. But as soon as I hide that track, the channel strip will then take the name from the non-hidden copy of the track haha - so that didn't work as a workaround either. I really doubt this is intentional. Unfortunately I am not on Sonoma so I can't update to 10.8.1 - do you know if this is the same behaviour in 10.8.1 or if it has been fixed?
×
×
  • Create New...