This repository has been archived by the owner on Jun 10, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
NEWS
173 lines (116 loc) · 5.51 KB
/
NEWS
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
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
* freespace state was using a char array with one char
per location. this was because i forgot to #define
USE_nnBIT_ARRAY when i moved to the cmake build system.
turns out the one-char-per-location array had a bug
which caused placement of an event with the same width
as the boundary it was to be placed within to fail.
Tuesday 28th September 2010
* improvements to box movement and resizing calculations.
* much refactoring of gui code to allow reusability -
see ChangeLog for full details.
Sunday 26th September 2010
* grid boundaries can be re-ordered.
with a boundary selected, press the - or + key
to bring it forward or backward in the boundary list
respectively. it is however not at all clear.
* arrow keys will move the selected boundary 1 grid location
in the specified direction at a time.
Friday 24th September 2010
* grid boundaries now have three states:
play, block, and ignore.
the play state is the normal state. in the block state,
all events are treated as blocks. the ignore state ignores
all events.
* three keyboard shortcuts for controlling the boundary
states:
p or P to play events as normal
b or B to turn all events into blocks
i or I to ignore all events
only effects the boundary the mouse is currently hovering
over.
Friday 24th September 2010 (01:35am)
* Oops, yesterday was Thursday and not Wednesday.
* The display of the grid is now within the main window
(ie, below the time display and transport control buttons).
* Finer zoom step-sizes.
* Wednesday 23rd September 2010
After an extended break from programming during which I changed
web hosts and domain name registrars for jwm-art.net, and then
suffered from some kind of creative i hate everything it's worthless
crisis, I'm back programming again:
* The grid editor now has zoom control
* The grid itself (which does not have any grid lines ;-)
is now centered when it is smaller than the viewport.
* Space in the window which is not the grid is grey
rather than the black of the grid.
Hmmm, well actually, I had started work on an FLTK version of Boxyseq
during August. It stagnated when I discovered it had the potential to
end up with the same problems as the Cairo/GTK version because FLTK
can be compiled with Cairo.
So basically, I've decided development of the BoxySeq GUI will proceed
using Cairo and the (deprecated) GDK and the FLTK versions are abandoned.
* Sunday 15th August 2010
* The boundaries are now resizable via right-mouse click
* Sunday 15th August 2010
* Something which I shall name as a 'fix' 'fixes' the
problem with the l2r placement where the right edge
of a box would often extend past the right edge of
the boundary which it was supposed to fit within.
* The GUI now displays grid boundaries. A simple demo
means you can click-drag the boundary around. release
the click to set the new position.
* Tuesday 10th August 2010
* Pressing the grid button for the first time changes
the key and scale of the grbound placement. So connect
boxyseq up to your fave synth and listen to what it does
*BEFORE* pressing the 'grid' button :-)
* Monday 9th August 2010
* Mainly code changes signalling the start of getting
GUI ready for actual user interaction as opposed to
user passivity.
* Wednesday 4th August 2010
* The display is looking a bit spiffier.
* Event boxes change colour after note-off during the
release phase.
* Events are removed upon stop/reposition transport
* etc, lots of stuff which doesn't sound that much
when i write it like this.
* Saturday 31st July 2010
* note off events are generated for all notes currently playing
upon a transport reposition, transport stop, and application
quit.
* 15:16 Sunday 4th July 2010
i've been attempting to investigate the source of a certain
problem involving events which are placed within the grid but
for what ever reason fail to be removed.
i've been using the 'sprinkle the code with debug statements
showing the value of relevant variables' approach to as yet,
no result.
i am still yet to find any identifiable pattern which the
events which are not removed share. i am yet to find anything
which provides a lead. i need to do a cold hard reboot to
prove to myself that it's not a memory error which is using
old bytes from second hand pre-used (ie free()d memory from
previous program run or whatever).
valgrind bring up uninitialized values in midi_out_port.c
and i was shirly fure i noticed a potential cause of these
but alas no the event boxes still stick in the grid refusing
to be peeled off.
...
i have found though a bug instead elsewhere. this little
blighter was nibbling away at the free space code - causing
events with width > (boundary_width / 2 - 2) to not be
placed. luckily, this was a incredibly simple minded bug and
took no persuasion in moving him in to the neighbours garden
where last seen looked very happy and at home.
------------
further news on this day of Sunday 4th July 2010:
further news, from the past few days:
* timebase is um, erroneous, BoxySeq's 145bpm seems slower
than Ardour2's 145bpm. i began investigating this but
somehow got distracted and went on a mission to investigate
the non-removal of certain choice event boxes.
*THE IS THE NEWS*
01:54 Wednesday 30th June 2010
boxyseq is now sequencing and outputting MIDI to JACK!
Hurrah!