notahat / midi_patchbay Goto Github PK

Way back in 2015 I updated Midi Patchbay to be 64 bit clean, and I even put it up on the App Store. I seem to recall reaching out to NotAHat, but I don't think I got a response. In any case, I put this web page up:
http://efroymson.blogspot.com/2015/11/midi-patchbay-64-bit-version.html

And I still get the occasional inquiry, or Kudo, or what have you. I stumbled across this repository more recently, and I wonder if there is someone here who would like to take responsibility for maintaining the app, answering questions, etc. Or is this the place? Github is not exactly user friendly for someone who just wants to use the software.

Hi
First of all, I love your software, it's a true tool. I can't imagine any, even DAW-less session without it.

One issue I've found after connecting my new NTS-1. I have 3 pieces of this device connected together via USB.
MIDI patchbay displays only once.
I've checked in DAW (Logic) - there are three the same MIDI in(s) and MIDI out(s), for every NTS-1 device.

Do you delete duplicates from MIDI input and MIDI output lists?

best regards
Piotr

Hi, I have been happily using Midi Patchbay in Mojave (thanks for making it available!) and am looking to upgrade to Catalina, but the upgrader said Midi Patchbay would not be compatible. From the homepage I found this GitHub project and noticed in the readme there are two more recent releases, 1.0.4 and 1.1.0, but I cannot find where they are published. Would you mind updating the readme with a link to where to download 1.1.0, or perhaps publish it to the Releases page?

Had a really issue with this. I had the app open (on 10.10) and I think my Mac must have crashed.

Then on every reboot the previous setup that I had (which was mostly midi through) was the same as before the crash without Midi Patchbay running. I couldn’t see an anything in Activity Monitor. Which was obviously really annoying as almost all my devices sounded at the same time...

Re-downloading and re-running the freshly downloaded program cleared this.

@danomatika I've been thinking it over, and what I'd like to do is this:

• Merge #6
• Fix the display issues when editing virtual endpoints on Catalina
• Disable dark mode for now, coz it only half works It was easier just to get it working: #8
• Disable the tab bar: #9
• Fix window resizing issues
• Cherry pick your docs changes onto master
• Add you and others to the credits and the README
• Get everything in place for Apple to validate the app
• Update the website and support links in the menus
• Make text in the patch table invert when highlighted?
• Make the Delete menu item behave?
• Fix the build number
• Release as 1.1.0

Ideally I'll see if I can get it on the App Store, but I'm not sure how much work that'll be.

From there, I can do a 1.1.1 release with:

• SecureCoding support
• View-based tables for virtual endpoint editing
• ARC changes
• Any UI tweaks from your branch that seem like an obvious improvement
• Maybe dark mode support (coz I don't think it'll be too hard)

That should give us a pretty solid, long-lasting release, with no deprecation warnings.

Sound sensible? Any details I've missed from your PRs that you think are important?

The Midi Patchbay file icon in a document window titlebar has a black background instead of being transparent. I don't think this happened in Mojave using version 1.0.3

Version: 1.0.4 (2)
OS: Catalina 10.15.2

I can't find a download link for a compiled app, and there isn't instructions on how to compile the application from the source code. Can you point me in the direction on how to compile it? Or am I missing something?

Hi,

this project currently is under no license.
Could you please add a software license in order to
a) waive your own liability
b) provide context for the OSS community how we can re-use / extend this software

Thanks!

Hello,

first of all: I'm a Windows guy, so maybe I just missed some simple Mac stuff.

Is there a possibility to
a) start MIDI Patchbay with the last active configuration instead of empty or define a default config to be loaded on start?
or b) start MIDI Patchbay minimized when I doubleclick a config file?

Background: I try to establish the always same config on Mac startup.
Only chance I see is to put the config file in "autostart", but this way the MIDI Patchbay window opens on desktop.

Rick

I cant find it in the releases section