timbertune

Amazing - thanks so very much. Single quote characters - WHO F'IN KNEW? I tried out the revised object you posted and sure enough it worked HOORAY. The only prob now is that for some reason I could only get the XV to produce audio in 'patch mode' (ie. one sound) vs 'performance mode' (individual sounds on each MIDI channel). But I'm pretty sure that has something to do with the XV itself and some button I must have randomly pressed while attempting to trouble shoot this nonsense last week... . Even if it's only working in patch mode, it proves that MIDI is getting thru, AND changing banks no longer causes freezes or crashes. Phew! The Apple folks owe you big coz like I say, I'd been sending them crash reports on this one for months now and not even a glimmer of a response. I guess now I can finally go back to cursing the fan on my Kurzweil, the way the All-Powerful MIDI overlords intended. cheers!

Just looking at this again and wondering if perhaps this problem started when I changed the SRX cards in my XV2020 -- maybe I didn't adjust the corresponding unique strings in my Logic XV multi-instrument, and that disagreement between SRX bank names may be what causes the crash? It's odd because the actual PATCH names are fine - I cut and pasted those. But maybe the hidden bank-name parameters didn't get switched appropriately when moved some SRX cards around (I used to have 4 SRX cards in a 1080 and 2 in the XV, then I sold most of them off and kept my faves in the XV)

Not urgent - take all the time you need. Much appreciated.

Wow - I have to say that I am very impressed indeed by your persistence in getting to the bottom of this annoying bug. And I agree, it really feels like a "Logic bug" to me because of the way it has survived thru various multi-instrument objects, various Logic versions and MacOS's, not to mention happening on both Intel and Mac Silicon machines. To answer your question above - Most definitely YES PLEASE do a fix on my XV2020 multi if you don't mind. As to the oscwilde's question about which specific SRX expansion card is, I THINK it's the "World" expansion card. I'm basing that on the patch names from my multi, but since I haven't been able to use those banks in almost a year, I'm not 100% sure. I used to have different cards in those slots but sold them off as Roland released the equivalents in software... But I'm pretty sure it's the 'World' card still in there. Weird that Apple has been silent about this bug after I've sent them crash reports since it started. But thanks so much to Des99 for drilling down on this. I've had a somewhat painful process moving from my old intel 'Hackintosh' to the new M2 Studio. First the audio interface drivers wouldn't work - got that sorted. Then the MOTU MIDI interface refused to work - finally got that sorted. And now this dumb bank-change bug was biting me almost daily... It will be glorious to once again click patch-change browsers without fear! 🙂

Dang - had my hopes up and everything. I cut and pasted your XV5080 object into my project and started playing some of the tracks (after assigning it to the same MIDI port as my XV2020). All was fine and promising until I selected bank 7 (where the XV's expansion boards are - the ones I'm trying to get to). INSTANT crash... just like before. SIGH.

Thanks des99 - that sounds promising. I've just done some more testing and I'm pretty sure the Custom Bank Messages are the culprit. Which, when you think about it, is kinda messed up - that a little chunk of SysEx is enough to bring Logic to its knees so decisively... But when I created a fresh Multi-Instrument in the Environment and assigned it to the right MIDI out port, I was able to play the XV without trouble, and change patches on the basic GM internal banks. But no luck accessing any other banks, and none of the existing Logic preset BankChange commands work either. Surprising that the JV1080 or 2080 don't work, since they're pretty similar boxes and the XV2020 was just a smaller JV2080 really... Anyway, maybe the 5080's code is the missing piece of this puzzle. I just can't figure out why the XV bank command worked fine for years and now causes such immediate mayhem... But I'm no programmer. Thanks again.

Thanks for the reply. The "?" in the icon field doesn't mean anything bad though, and is no indication of any kind of corruption. It simply indicates that I used a custom icon for this instrument. As for cutting and pasting from an earlier version, that is also not possible. THis is the exact same instrument that's been in my template for over 10 years, and all versions of this instrument cause the same freeze or crash in the current version of Logic. BUT I think you're correct that the next thing for me to try is to create a fresh new environment object for this instrument and see if it behaves any better. The trick will be finding the 'custom bank change messages' which are required to navigate the patches on a Roland synth. But maybe by now those are readily available somewhere... Thanks again for looking into it.

MIDIBUG_TESTlxp.logicx So - here's the Logic project which I created. Just an empty project with a few Audio tracks and a few GM Midi tracks, plus the Roland XV2020 Multi-Instrument from the the MIDI Environment in my larger template. For me, when I attempt to change patches on this instrument - which has worked FOR DECADES - now Logic freezes graphically. Every time. I made a video of this happening a couple times, but the movie file is too big to be uploaded here... maybe I'll try YouTube if I can figure that out? Thanks to anyone who takes some time to explore this weirdness.

Thanks for the reply. Oddly, I can't share the exact template but your suggestion makes me think of a possible test or workaround. I'll copy the objects from the MIDI environment into a blank template and see if the problem still persists, which I think it will. I've used this template for years without trouble, but it's only the last few versions of Logic where this new crash/freeze has appeared. I wonder if it's possible there's something in the 'custom bank change messages' that could somehow bring Logic Pro to its knees? Anyway, soon as I can I'll see if I can make a 'generic' form of my template that still exhibits the bug on my system, then share that here for others to test. I'm also thinking of making a screen-grab video of the crash, just to show it in action... Thanks.

Wonder if anyone’s seen this odd crash? It’s 100% repeatable both on my previous Intel iMac and now on my new M2 Mac Studio. I have an old Roland XV2020 connected to the Mac over a MOTU Micro Express interface. It’s all configured in my template's Logic Environment and the XV has been there for years without issue…. But for the last 6 months or so, if I select the patch browser for the XV (by double clicking the icon on the track in Logic’s arrange page), I can scroll thru the patches - BUT then one of two things will always happen. A) Logic quits immediately if I click on a patch, or B) Logic freezes graphically when I click, ie. menus won’t open, the Logic display is ‘frozen’, but other apps are fine and the mouse is still fine and task manager does NOT show Logic as ‘not responding’. My only option then is ‘Force Quit’ (coz you can’t even select ‘quit’ in Logic coz the menus are frozen). Very strange and, as I say, totally reproduceable. Any thoughts? Anyone else ever seen anything like it?

Question for the LogicPro minds out there - can I change the Project Tempo logic WITHOUT having an effect on either the Audio AND the MIDI? I played a song in 'free time' (not to click) but now I want to add a click track after the fact. But I don't want any of the audio or midi-performances to change in any way. Is there a way to make MIDI ignore a new tempo? (I'll be experimenting with this today and if I figure it out before anyone else replies, I'll report back).

Monterey on a Hackintosh? Have you researched people being problem-free with a music setup? Monterey is giving certain people headaches on Apple hardware. So do your research before you'll regret it. My 2 cents. I've been watching a few threads on the topic, yes. Basically it seems Monterey's been out long enough, and most of my plugins claim to support it. And since I'm having all these glitches now, I need to try something to shake the system up. BUT I've got all my drives fully backed up and if it looks like more trouble than it's worth, then back to Catalina I go... I just made a new Template that uses fewer 3rd party plugins, so hopefully I can try this Alternate User account experiment and see if things run any differently.

That's a good idea, thanks. I wonder how much drama that will create with plugin authorizations? I suppose there's one way to find out... I guess I should count myself lucky that my system has been so solid for the last couple years, given that it IS a Hackintosh... But it's weird to see this glitch pop up so consistently all of a sudden when no other significant part of my system has changed. (Other than the usual occasional plugin updates, of course.) The other thing I'm going to try is upgrading the OS - I've been 'frozen' on Catalina for a while. Maybe this problem will disappear in Monterey. That's tomorrow's adventure.

Yes, I've seen that too - a CPU spike causing Logic to lose sync. But in this case, I even tried it with a completely blank 'New' song -- not even starting with my basic template. Just a new song with 3 Logic 'Retro Synth' tracks, and it still lost sync after a few minutes. Very weird because just a couple weeks ago I was working on a giant mix with 50+ tracks and tons of plugins - all without seeing this error once. Now it's daily, unavoidable, and no amount of changing buffer sizes or disconnecting peripherals has any effect. Bizarre.

I used to get this error once every few months, but now it's happening every ten minutes and making Logic almost unusable. Always the same error, with the line "Sample rate 32,333 recognized". Nothing has really changed in my system over the last little while, but now this error will not go away. I'm a veteran user and I've checked all the most obvious stuff - USB and Thunderbolt connections, clock rates, word-clock sync etc. My main interface is an Antelope Orion32+ connected via USB3, and I also get inputs from a UAD Apollo x8p connected via Thunderbolt. But my testing shows that I still get this error even if the Apollo hardware isn't turned on or connected. I can 'clear' the error by switching sample rates to something/anything else, then switching back. But 5 minutes later the error returns. Anyone know of any other trouble shooting tips or suggestions for this work-killing error?