qsynth: new port, version 0.5.6

[mojca]

I took the port from https://github.com/RJVB/macstrop/tree/master/audio/qsynth after getting user's request for the port and made some modifications.

There is one Qt build dependency missing to translate files. (fixed)

When I open the app, it fails with

Qsynth1: Failed to create the audio driver (jack).

Cannot continue without it.

I might need @RJVB's help for that.

(Also, for a strange reason I cannot use makeicns in trace mode. But I leave that mystery for another time.)

Description

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 10.13.6 17G6030
Xcode 10.1 10B61

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL?

• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?

[RJVB]

On Sunday April 14 2019 11:33:31 Mojca Miklavec wrote: There is one Qt build dependency missing to translate files (I'm not yet sure which one; it works outside of trace mode) and when I open the app, it fails with

I pushed an update a bit earlier that should fix that (but note that I never use trace mode myself because it tends to give me too many false negatives). I also pushed a fix for the missing icon resource.

``` Qsynth1: Failed to create the audio driver (jack). Cannot continue without it. ``` I might need @RJVB's help for that.

Well, I do have (an older) jack installed but the options to de/activate jack support in qsynth are disabled for me. The app is configured to use coreaudio devices directly. Note however that I'm not getting any sound but instead plenty of log messages ``` Apr 14 22:59:32 Portia.local MIDIServer[98698]: 22:59:32.909 ERROR: [0x7fff72695310] Apr 14 22:59:33 Portia.local qsynth[98697]: kAudioUnitErr_TooManyFramesToProcess : inFramesToProcess=512, mMaxFramesPerSlice=128 Apr 14 23:00:03 --- last message repeated 29 times --- Apr 14 23:00:03 Portia.local qsynth[98697]: kAudioUnitErr_TooManyFramesToProcess : inFramesToProcess=512, mMaxFramesPerSlice=128 Apr 14 23:00:33 --- last message repeated 29 times --- Apr 14 23:00:33 Portia.local qsynth[98697]: kAudioUnitErr_TooManyFramesToProcess : inFramesToProcess=512, mMaxFramesPerSlice=128 Apr 14 23:01:03 --- last message repeated 29 times --- Apr 14 23:01:03 Portia.local qsynth[98697]: kAudioUnitErr_TooManyFramesToProcess : inFramesToProcess=512, mMaxFramesPerSlice=128 Apr 14 23:01:33 --- last message repeated 29 times --- Apr 14 23:01:33 Portia.local qsynth[98697]: kAudioUnitErr_TooManyFramesToProcess : inFramesToProcess=512, mMaxFramesPerSlice=128 Apr 14 23:02:04 --- last message repeated 11 times --- ``` This rings a bell, vaguely, but I'm not in the mood now to go figure out what's wrong here. VLC will play midi files, and if you want something that doesn't have a play/pause button (like qsynth) you can also call fluidsynth directly... R.

[mojca]

One can change the driver in Setup and then it stops complaining.

Midi -> Midi driver -> coremidi
Audio -> Audio driver -> coreaudi

I need to check if the default could be changed during the build (and check if this actually produces any sound).

[StanSanderson]

Apologies for not responding earlier. I lost the thread and just found it this morning.

I am further embarrassed to say that I have not used github and really don't know what to do. 60 years ago, this would have been a piece of cake (but, then, the idea of personal computing was a pipe dream). My first experience at computing was on an IBM 1620 using machine language. I have tried following the MacPorts instructions for creating a local port file repository, but so far portindex gives me zeros. I will keep trying!

[RJVB]

This is a new port, so you can simply copy the qsynth directory with all files in it into your default port tree and then run portindex there. Or, you can copy it anywhere you like and then do `sudo port install` from inside that qsynth directory. That is probably the easiest solution.

[StanSanderson]

I am feeling more stupid by the moment. I would like to copy the qsynth directory as you suggested, but where is it, and how do I copy it?

[RJVB]

I am sorry, I thought there was a way to download the changes of a PR as a .zip file or something of the sort but apparently not. So you could do this, in a location of your chosing (and in a Terminal.app window (shell)): ```

mkdir qsynth cd qsynth wget https://raw.githubusercontent.com/macports/macports-ports/f304da4c4842e50410fee56d23ed0f21a8dabb74/audio/qsynth/Portfile wget https://raw.githubusercontent.com/macports/macports-ports/f304da4c4842e50410fee56d23ed0f21a8dabb74/audio/qsynth/files/patch-src-CMakeLists.txt.diff sudo port install

``` (if you don't have wget: `sudo port install wget`)

[mojca]

Let's make this easier. I'll merge it. If it works for you at least ... It builds fine, I just don't know how to use it ... If it turns out to be useless, I'll remove it later.

[StanSanderson]

If I understand correctly, qsynth is now in the port list and it will take some time to propagate through the mirrors. I did try the two-step wget, but the install failed with "Failed to connect to mirrors.shu.edu.cn port 443: Connection refused"

[StanSanderson]

Many thanks! Qsynth built easily and functions as expected with the Frescobaldi app. The interface is the same as the previous version, no settings were lost in the transition. While the purpose of lilypond (and Frescobaldi) is not to produce "finished" midi music, the output can be useful when proofing and editing music. I also find it useful for providing accompaniment for vocal rehearsals. The controls (especial the reverb) offer the opportunity to make the standard sound font instrument sound more realistic.

By the way, earlier in the conversation VLC was mentioned as an alternative for playing MIDI. Unfortunately, the latest versions for Mac do not allow the use of FluidSynth. They claimed there was a high hacking risk with fluid synth enabled in VLC. I did, however, find a beta version which accepts FluidSynth.

Thank you again!

[StanSanderson]

Ahh, I stand corrected. The latest VLC does accept FluidSynth, so it will play Midi. I'm not sure if Frescobaldi will easily interface with it.

[mojca]

@RJVB: I assume we need another keyword somewhere to support high resolution display?

[mojca]

@StanSanderson: I use Timidity to play midi files. But I use it from command line. At some point I would be grateful for some screencast about how to use this piece of software, not via jack but using coremidi :) Playing a midi file from command line didn't work for me.

[RJVB]

@RJVB: I assume we need another keyword somewhere to support high resolution display?

Ah, yes, the famous NSPrincipalClass key that was discussed in the discussion about cmake that I started recently (should be set to NSApplication). Do you know how to get that in via cmake or do you prefer to handle it in the post-destroot?

[StanSanderson]

I only have used qsynth as a helper app for Frescobaldi. The current interface is pretty minimal- non of the Qsynth>Setup>Settings can be modified. I asked (who?) about that earlier, since the Gain always comes up at 0 at startup. Minor annoyance. Oh, and I was wrong again about the current Mac VLC- the midi audio codec is shown as "AUMIDI."