forked from ahlstromcj/sequencer64
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.windows
142 lines (103 loc) · 5.54 KB
/
README.windows
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
README.windows for Sequencer64 0.96.2
Chris Ahlstrom
2018-05-13 to 2018-11-08
This README provides what you need to know to run the new native Windows
implmentation of Sequencer64 (qpseq64.exe). It provides notes on Sequencer64
and Windows. We mostly use Windows 10; some features might differ in Windows
7 or Windows 2012+ Server.
There is a portable ZIP package for qpseq64 and an NSIS-based installer.
See https://github.com/ahlstromcj/sequencer64-packages. For documentation,
see https://github.com/ahlstromcj/sequencer64-doc. Some minor features are
still missing from the Windows version, such as keyboard configuration.
Sample files are provided for such cases.
Inaccessible Devices:
When first starting qpseq64 on Windows, one might experience some issues.
One issue is that the Microsoft MIDI Mapper, rumored to be removed in
Windows 8 and beyond, is still detected by the PortMidi library used in
qpseq64. Another issue is that the built-in Microsoft wave-table
synthesizer is not accessible.
When an error occurs, the files "erroneous.rc" and "erroneous.usr"
are created. They can be inspected, fixed, and renamed to
"qpseq64.rc" and "qpseq64.usr", and with luck the startup will work.
We installed the CoolSoft MIDIMapper and VirtualMIDISYnth to try to get
around these issues, and tried to turn off the system setup of "Allow
applications to restrict access to this device." But we still had
inaccessible devices, and the resulting errors would cause qpseq64 to
abort. So we had to spend a lot of time supporting the disabling of
inaccessible ports, and saving and restoring the "rc" setup properly.
Here is the latest output on our Windows, generated using the option
"-o log=virtualmidi.log":
qpseq64
C:/Users/chris/AppData/Local/sequencer64/virtualmidi.log
2018-05-13 09:06:58
[MIDIMAPPER] 'mapper in : midiInGetDevCaps() error for device
'MIDIMAPPER': 'The specified device identifier is out of range' '
pm_winmm_general_inputs(): no input devices
PortMidi MMSystem 0: Microsoft MIDI Mapper output opened
PortMidi MMSystem 1: CoolSoft MIDIMapper output closed
PortMidi MMSystem 2: Microsoft GS Wavetable Synth output opened
PortMidi MMSystem 3: VirtualMIDISynth #1 output closed
[Opened MIDI file,
'C:\Users\chris\Documents\Home\sequencer64\data\b4uacuse-gm-patchless.midi']
[Writing rc configuration
C:\Users\chris\AppData\Local\sequencer64\qpseq64.rc]
PortMidi call failed: [-1] 'Bad pointer'
PortMidi call failed: [-1] 'Bad pointer'
Begin closing open devices...
Warning: devices were left open. They have been closed.
We still have some minor issues at start up and at exit, but are now able
to play a tune on the wavetable synthesizer using the "-b 2" option.
When you first run qpseq64 on Windows, it will create two new configuration
files:
C:\Users\username\AppData\Local\sequencer64\qpseq64.rc
C:\Users\username\AppData\Local\sequencer64\qpseq64.usr
Inaccessible devices are noted in the "[midi-clock]" section of
"C:\Users\username\AppData\Local\sequencer64\qpseq64.rc" by a "-1" value.
Configuration Files:
On Linux, the normal directory location of the Sequencer64 configuration
files is "/home/username/.config/sequencer64". Various confignames:
sequencer64.rc, .usr The RtMidi Native ALSA/JACK version.
seq64portmidi.rc, .usr The PortMidi Gtkmm 2.4 version.
qpseq64.rc, .usr The PortMidi Qt 5 version.
On Windows, the conventional location is different, and the location used
is "C:\Users\username\AppData\Local\sequencer64". The file is:
qpseq64.rc The PortMidi Qt 5 version for Windows.
qpseq64.usr Ditto.
To access AppData, highlight the username directory, then append
"AppData" to the end of "C:\username". It is a Windows thang.
After a build, one can change to the shadow-build directory
and run
Seq64qt5\release\qpseq64.exe
If it does not come up after a few seconds (Windows is *slow*), then
run:
windeployqt Seq64qt5\release
and try again. Immedidately quit the application, go to your
"AppData" directory and verify the presence of:
qpseq64.rc
qpseq64.usr
Now plug in a MIDI device, and do the same exercise. Open
qpseq64.rc and see what is in it:
[midi-clock]
2 # number of MIDI clocks/busses
# Output buss name: [0] 0:0 PortMidi:Microsoft MIDI Mapper
0 0 # buss number, clock status
# Output buss name: [2] 1:1 PortMidi:Microsoft GS Wavetable Synth (virtual)
1 0 # buss number, clock status
# Output buss name: [3] 1:1 PortMidi:nanoKEY2
2 0 # buss number, clock status
[midi-input]
1 # number of input MIDI busses
# The first number is the port number, and the second number
# indicates whether it is disabled (0), or enabled (1).
# [1] 0:1 PortMidi:nanoKEY2
0 0
As of this time (2018-05-27) these settings can now be accessed via
Edit / Preferences / MIDI Clock and MIDI Input to
alter the ports accessible, in the Windows version of Sequencer64.
The operator system may have some devices locked out, though.
qpseq64 --buss 1 --option log=filename.out
Keystroke Support:
Some keystrokes are hardwired, but a number of them can be configured by
editing the "rc" file directly. Eventually, a Qt 5 keystroke editor will
be provided.
# vim: sw=4 ts=4 wm=4 et ft=sh