No midi input in Instrument- BBCSO Spitfire player- Logic

Maybe this will help?

OleJoergensen said:

Im trying the BBCSO Template Core 2 - Multiple Instance - Full Routing, but the Spitfire player does not receive input from my keyboard. I can see Logic monitoring input from my keyboard. The Spitfire player does play if I play the keyboard on the Spitfire player with the mouse and it also playback if I click notes into a region in Logic.

Click to expand...

Stewart from Spitfire says this is a bug in the latest release of the plugin, and has linked to an out-of-band update you can download via this thread on their forum (the link is almost invisible: it's the word "here" in bold in the second paragraph of Stewart's post.)

I haven't had this problem myself, and I don't think anyone has explained the nature of the bug. I also don't understand why this hasn't been released through the usual channel (i.e. the app.)

newbreednet said:

Maybe this will help?

BBC Template Updates

Hello everyone, We've received reports recently that BBC no longer works with the most recent update when using the templates.

community.spitfireaudio.com

Click to expand...

Thank you I will try it out.

aldous said:

Stewart from Spitfire says this is a bug in the latest release of the plugin, and has linked to an out-of-band update you can download via this thread on their forum (the link is almost invisible: it's the word "here" in bold in the second paragraph of Stewart's post.)

BBC Template Updates

Hello everyone, We've received reports recently that BBC no longer works with the most recent update when using the templates.

community.spitfireaudio.com

I haven't had this problem myself, and I don't think anyone has explained the nature of the bug. I also don't understand why this hasn't been released through the usual channel (i.e. the app.)

Click to expand...

Thank you for helping out I will try it.
I don't have the great understanding of this (hope it will come by time) anyway it is strange. Im glad I after 20 minutes decided to let it be and ask here.

OleJoergensen said:

Thank you for helping out I will try it.
I don't have the great understanding of this (hope it will come by time) anyway it is strange. Im glad I after 20 minutes decided to let it be and ask here.

Click to expand...

It seems the bug only affects those on the newest version of BBCSO - which I haven't updated to yet - so will be interesting to hear if these new templates sort it out. Good luck!

Thanks for posting, I had this issue and couldn't figure out what was happening. It happens sporadically in AR2 as well, I'll reach out to Spitfire to confirm.

newbreednet said:

It seems the bug only affects those on the newest version of BBCSO - which I haven't updated to yet - so will be interesting to hear if these new templates sort it out. Good luck!

Click to expand...

I celebrated to early, u
It didn’t work…..maybe I did something wrong. Anyway activate R(red button) In Logic makes it work.
Spitfire should make an update from the Spitfire app instead.

OleJoergensen said:

I celebrated to early, u
It didn’t work…..maybe I did something wrong. Anyway activate R(red button) In Logic makes it work.
Spitfire should make an update from the Spitfire app instead.

Click to expand...

I'm not using the absolutely most recent version of Logic, however, did something change with the way Logic deals with record-enabled tracks? Or do things work "normally" with other sample libraries/instruments, and it's just BBCSO that has the problem?

OleJoergensen said:

I celebrated to early, u
It didn’t work…..maybe I did something wrong. Anyway activate R(red button) In Logic makes it work.
Spitfire should make an update from the Spitfire app instead.

Click to expand...

Just saw you asked on the SF forum about the "command" script packaged with the updates. It shouldn't matter where you run it. Or, forget the script and just issue this command at a terminal:
xattr -cr <plugin_file>
for each <plugin_file> you installed, surrounded by quotes if it contains spaces. So, if you only took the AU version, the command would be:
xattr -cr '/Library/Audio/Plug-Ins/Components/BBC Symphony Orchestra.component'

(When you download files from the web, MacOS adds "extended attributes" (xattr) to the file so it knows to do various security checks/block execution. This command removes those attributes.)

OleJoergensen said:

I celebrated to early, u
It didn’t work…..maybe I did something wrong. Anyway activate R(red button) In Logic makes it work.
Spitfire should make an update from the Spitfire app instead.

Click to expand...

That's normal behavior. The track has to be record-enabled, or highlighted for it to play incoming MIDI.

newbreednet said:

I'm not using the absolutely most recent version of Logic, however, did something change with the way Logic deals with record-enabled tracks? Or do things work "normally" with other sample libraries/instruments, and it's just BBCSO that has the problem?

Click to expand...

I have not seen this problem using other libraries in Logic....I will see what Spitfire respond. I wrote a message at the Spitfire forum, maybe I will open a support ticket.

Justin L. Franks said:

That's normal behavior. The track has to be record-enabled, or highlighted for it to play incoming MIDI.

Click to expand...

But normally this happens when you move from track to track. Here you have activate the "R" on the track with the mouse....

aldous said:

Just saw you asked on the SF forum about the "command" script packaged with the updates. It shouldn't matter where you run it. Or, forget the script and just issue this command at a terminal:
xattr -cr <plugin_file>
for each <plugin_file> you installed, surrounded by quotes if it contains spaces. So, if you only took the AU version, the command would be:
xattr -cr '/Library/Audio/Plug-Ins/Components/BBC Symphony Orchestra.component'

(When you download files from the web, MacOS adds "extended attributes" (xattr) to the file so it knows to do various security checks/block execution. This command removes those attributes.)

Click to expand...

Thank you for explaining. Then I think I did it right.
I don't have experience using Terminal, so I just used the instruction given with the downloaded files.
I will wait and see if Spitfire responds....

OleJoergensen said:

But normally this happens when you move from track to track. Here you have activate the "R" on the track with the mouse....

Click to expand...

This has changed back-and-forth a couple of times in recent Logic versions. In 10.8+, the selected track is record-enabled (first picture) only if no tracks are manually record-enabled. If any track is manually record-enabled (by clicking the button, second picture), then selected tracks are not record-enabled automatically.

OleJoergensen said:

I will wait and see if Spitfire responds....

Click to expand...

They rarely respond in the forum, so I suggest opening a support ticket if you need help. Though, if the plugin plays when its track is record-enabled then there doesn't seem to be a problem...?

OleJoergensen said:

But normally this happens when you move from track to track. Here you have activate the "R" on the track with the mouse....

Click to expand...

aldous said:

This has changed back-and-forth a couple of times in recent Logic versions. In 10.8+, the selected track is record-enabled (first picture) only if no tracks are manually record-enabled. If any track is manually record-enabled (by clicking the button, second picture), then selected tracks are not record-enabled automatically.

Click to expand...

I'm still on Catalina which can't run 10.8, so I still get the "old" behavior. I guess it makes more sense to have it play incoming MIDI only when manually record-enabled instead of just being highlighted....but then having a highlighted track play if there aren't other manually record-enabled tracks is just weird.

They should either have it so a highlighted track always plays incoming MIDI regardless of being record-enabled (the old behavior), or that all tracks need to be manually record-enabled to play incoming MIDI. None of this inconsistent "halfway" stuff.

Justin L. Franks said:

I'm still on Catalina which can't run 10.8, so I still get the "old" behavior. I guess it makes more sense to have it play incoming MIDI only when manually record-enabled instead of just being highlighted....but then having a highlighted track play if there aren't other manually record-enabled tracks is just weird.

Click to expand...

There are two parallel conversations happening here and we're getting muddled

I was replying to @OleJoergensen about how record-enable follows the highlighted track. Separately, as you say, the selected track also receives MIDI even if it isn't record-enabled. I think that second part has been true almost always (maybe apart from one of the 10.7.* releases?) but I can only test it on 10.8.1.

This all gets confusing because there were several changes during the 10.7.x releases... and either "bugs" or "unpopular features" that got changed again. There's lots of detail in the release notes, but my summary is: it was mostly intuitive before 10.7, mostly intuitive after 10.7.9, and mostly annoying in between.

aldous said:

I was replying to @OleJoergensen about how record-enable follows the highlighted track.

Click to expand...

So was I (and of course, also replying to your response explaining how it changed in recent versions of Logic). I was just pointing out that they went from a "highlighted track always plays incoming MIDI even if not manually record-enabled", to a "highlighted track sometimes plays incoming MIDI if not manually record-enabled". Which is inconsistent.

Justin L. Franks said:

I was just pointing out that they went from a "highlighted track always plays incoming MIDI even if not manually record-enabled", to a "highlighted track sometimes plays incoming MIDI if not manually record-enabled". Which is inconsistent.

Click to expand...

The highlighted track still does play MIDI, though - I don't think that's changed.

aldous said:

This has changed back-and-forth a couple of times in recent Logic versions. In 10.8+, the selected track is record-enabled (first picture) only if no tracks are manually record-enabled. If any track is manually record-enabled (by clicking the button, second picture), then selected tracks are not record-enabled automatically.




They rarely respond in the forum, so I suggest opening a support ticket if you need help. Though, if the plugin plays when its track is record-enabled then there doesn't seem to be a problem...?

Click to expand...

Thank you Aldous.
I thought that was the bug that Spitfire that Spitfire tried to fix with the replacement files.
This “bug” only happens with the 2 large BBCSO templates, the more simple one does not have this “Bug”. Anyway, I can use the bigger templates just activating the R button on the track .
I will contact Spitfire with a support ticket, maybe they need this information.