Jump to content

Crazy MIDIFX menu behavior


Danny Wyatt
 Share

Recommended Posts

Midi Feeze is the only plugin that does this (multiple options with the same name) and I was wondering if anyone has ever experienced this with it or any other plugin and how to fix it?

I tried contacting the developer, but this seems to be one of those plugins that are not constantly being developed/improved, so I doubt I will ever heard from him/her. It's been weeks since I sent an email and no reply yet.

1737995480_ScreenShot2022-06-12at4_22_51PM.png.b2e0e8a1cb96371726b6557b4e4a00b9.png

Edited by Danny Wyatt

Danny Wyatt - Musician, Music Producer, Songwriter, DJ
http://www.iamdannywyatt.com  - Join my Discord: https://dwyatt.me/discord
Logic Pro 10.6.3 • MacBook Pro 13" Mid 2012 • macOS Catalina 10.15.7

Link to comment
Share on other sites

I was getting that behavior also with another plugin...but an update to LogicPro somewhere along the line cured them both.  It was something related to AU3 plugins or some such thing I can't remember now.  Which version of LogicPro are you using?

OSX 12.x (Monterey) on OpenCore - Logic Pro 10.7.4, VePro7, Mainstage3 - 5,1 MacPro 3.46ghz x 12 96gb ram

Link to comment
Share on other sites

4 minutes ago, Dewdman42 said:

I was getting that behavior also with another plugin...but an update to LogicPro somewhere along the line cured them both.  It was something related to AU3 plugins or some such thing I can't remember now.  Which version of LogicPro are you using?

Logic 10.6.3 (can't go higher than that with my current laptop).

Yes I saw the AU3 checkbox next to the plugin and decided to check it today, but no change:

622901075_ScreenShot2022-06-12at4_44_51PM.png.2f87948af0655f5009231ffda5bcfd5c.png

Danny Wyatt - Musician, Music Producer, Songwriter, DJ
http://www.iamdannywyatt.com  - Join my Discord: https://dwyatt.me/discord
Logic Pro 10.6.3 • MacBook Pro 13" Mid 2012 • macOS Catalina 10.15.7

Link to comment
Share on other sites

you generally want that unchecked.  Unintuitive I know, but that was the case for VePro.AU3.

anyway, I can't remember when they fixed the AU3 problem related to MidiFXFreeze.  I think it might have been 10.7 sorry to say for you in this case.

 

OSX 12.x (Monterey) on OpenCore - Logic Pro 10.7.4, VePro7, Mainstage3 - 5,1 MacPro 3.46ghz x 12 96gb ram

Link to comment
Share on other sites

As a work around you have two other options that I know of.  One is to use the IAC trick.  That will work generally fine, its not absolutely timing-accurate, but close enough.

If you want an absolutely accurate midi file, then you can try a Scripter script I wrote, which is kind of complicated to setup, but not really that bad once you set it up and use it a few times.  Find here:

https://gitlab.com/dewdman42/MainstageMidiPlayer/-/wikis/home#logicgencsvjs

(from the above link, see the section about LogicGenCsv.js)

You will need to also install something called midicsv to your Mac, which is a command line tool you will have to use as part of the process.  The easiest way to install midicsv is via homebrew.  So first install homebrew.   

https://brew.sh

then in the command line you install midicsv like this:

brew install midicsv

Like I said....a bit complicated, but once its installed you're basically ready.  This approach is not as convenient as MidiFxFreeze...I'd say its more convenient then the IAC trick, once you have it setup and do it a few times to learn how to do it.  But...its a bit nerdy way to do it.  

one nice upside is that it exports the midi file at true 960 ppqn, LobicPro normally exports midi files at 480ppqn.  And anyway this approach works similar as MidiFXFreeze where it can capture the output from your other midi plugins during playback and turn that into timing-accurate midi file.

 

Edited by Dewdman42

OSX 12.x (Monterey) on OpenCore - Logic Pro 10.7.4, VePro7, Mainstage3 - 5,1 MacPro 3.46ghz x 12 96gb ram

Link to comment
Share on other sites

30 minutes ago, Dewdman42 said:

As a work around you have two other options that I know of.  One is to use the IAC trick.  That will work generally fine, its not absolutely timing-accurate, but close enough.

If you want an absolutely accurate midi file, then you can try a Scripter script I wrote, which is kind of complicated to setup, but not really that bad once you set it up and use it a few times.  Find here:

https://gitlab.com/dewdman42/MainstageMidiPlayer/-/wikis/home#logicgencsvjs

(from the above link, see the section about LogicGenCsv.js)

You will need to also install something called midicsv to your Mac, which is a command line tool you will have to use as part of the process.  The easiest way to install midicsv is via homebrew.  So first install homebrew.   

https://brew.sh

then in the command line you install midicsv like this:

brew install midicsv

Like I said....a bit complicated, but once its installed you're basically ready.  This approach is not as convenient as MidiFxFreeze...I'd say its more convenient then the IAC trick, once you have it setup and do it a few times to learn how to do it.  But...its a bit nerdy way to do it.  

one nice upside is that it exports the midi file at true 960 ppqn, LobicPro normally exports midi files at 480ppqn.  And anyway this approach works similar as MidiFXFreeze where it can capture the output from your other midi plugins during playback and turn that into timing-accurate midi file.

I was using the IAC method, but the MIDIFreeze is just easier and faster. I believe I had some issues with timing at one point with IAC, but can't confirm 100%

Your other method seems super complex and unless you really want something specific when you export, it seems that those are too many steps to just have an arp, for example, converted to individual notes... Thanks for sharing though :)

It's not that it hyper-annoys me having those 8 instances. It would just be better if it wasn't there. For what I do, the MIDIFreeze seems enough for now.

Thanks for letting me know this is not an issue with my Logic or even the plugin itself, since you had it with another one.

 

Danny Wyatt - Musician, Music Producer, Songwriter, DJ
http://www.iamdannywyatt.com  - Join my Discord: https://dwyatt.me/discord
Logic Pro 10.6.3 • MacBook Pro 13" Mid 2012 • macOS Catalina 10.15.7

Link to comment
Share on other sites

 

its complex to setup, its not bad once its setup.  The provided AppleScript makes it pretty easy, once its setup, the steps are basically

  1. play the sequence with the Scripter script there; instead of MidiFXFreeze
  2. copy the outputted text from the scripter window
  3. launch the AppleScript from your dock.

That's it, a midi file will appear on your desktop.  then drag it into LogicPro.

I personally find that a lot easier then setting up an IAC loop, but that's just me.  Admittedly my script scenario is kind of scary to setup, but I made it as simple as I could considering the limitations of Scripter.  It is what it is.  Hopefully you can get MidiFXFreeze working better as that is the easiest solution for sure.  And IAC will work fine, generally it will be accurate within about 1ms which is really close enough, if you get a bigger timing problem then that then there is something amiss.

 

Edited by Dewdman42

OSX 12.x (Monterey) on OpenCore - Logic Pro 10.7.4, VePro7, Mainstage3 - 5,1 MacPro 3.46ghz x 12 96gb ram

Link to comment
Share on other sites

this is the other plugin which used to make 8 menu entries also:

https://appadvice.com/app/mfxmonitor/1451193551

Well that link seems to be iPhone version, there is/was a Mac version that was free, which I still have installed...so I am not sure how to get that now, but anyway that was also AU3 midi fx and had the same problem as MidiFXFreeze.

You can check the LogicPro release notes to find out where there are mentions about a fix for AU3 and probably that is the minimum version you need to avoid seeing 8 menu items.

Edited by Dewdman42

OSX 12.x (Monterey) on OpenCore - Logic Pro 10.7.4, VePro7, Mainstage3 - 5,1 MacPro 3.46ghz x 12 96gb ram

Link to comment
Share on other sites

On 6/12/2022 at 5:59 PM, Dewdman42 said:

I personally find that a lot easier then setting up an IAC loop

Once you get used to the workflow, I think it's quite easy and fast actually. I have my External Instrument to default to the IAC, so that's another step I bypass.

I also have a keyboard shortcut to duplicate the track so all I do is:
1 - Shortcut to duplicate the track. Now visually I see it flow from top to bottom as a logical path. The top track is the source and the bottom track is the destination.
2 - Since the top is still selected, I just change the Instrument to External Instrument. This one is done.
3 - Select the bottom track, disable the MIDIFX, record enable and start recording.

That way I never leave Logic, I don't have to drag files from the desktop, which forces me to open finder, go to the desktop, click the file, drag it to Logic, align it in the project, etc. I also need to have another "object" on my Dock, etc.

But of course, each workflow is different and if that one works for how you work, then it makes more sense that you use that one :) It took me a while to really understand the flow of the IAC in this situation and how things needed to be set up, what needed to be disabled and changed, but once I understood, it became easier and faster. Of course MIDI Freeze is even faster ;)

Danny Wyatt - Musician, Music Producer, Songwriter, DJ
http://www.iamdannywyatt.com  - Join my Discord: https://dwyatt.me/discord
Logic Pro 10.6.3 • MacBook Pro 13" Mid 2012 • macOS Catalina 10.15.7

Link to comment
Share on other sites

fair enough.  One more thing...  MidiFXFreeze...and my script...are sample accurate.  IAC is not.  This may not matter.  Whatever works for you and gives you a smile.

 

  • Like 1

OSX 12.x (Monterey) on OpenCore - Logic Pro 10.7.4, VePro7, Mainstage3 - 5,1 MacPro 3.46ghz x 12 96gb ram

Link to comment
Share on other sites

5 hours ago, Dewdman42 said:

fair enough.  One more thing...  MidiFXFreeze...and my script...are sample accurate.  IAC is not.  This may not matter.  Whatever works for you and gives you a smile.

Unless there's a huge shift, I don't mind it being a bit off. Actually, I've been embracing that imperfection so it's ok.

Today I finished a Keyboard Maestro that automates the whole process with IAC so now all I need is to hit a shortcut and it will do it for me. I'm good to go :)

  • Like 1

Danny Wyatt - Musician, Music Producer, Songwriter, DJ
http://www.iamdannywyatt.com  - Join my Discord: https://dwyatt.me/discord
Logic Pro 10.6.3 • MacBook Pro 13" Mid 2012 • macOS Catalina 10.15.7

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...