Marcus Diess / StudioGuard
2017-05-29 19:31:14 UTC
Dear friends,
first I wanted to congratulate you for the release of V.2.1.3 and thank
all of you for their great contributions!!! - all I could contribute
were some Euros a minute ago...
Great, that some of you put effort in developing MIDIbility, but may I
remind you, that my attempt in 2016 was rather related to MIDI-control
of faders, knobs and buttons via an external MIDI controller unit, than
composing music with MIDI. (which would be great also, but secondary)
because MIDI Control would specially improve visually impaired user´s
accessability and workflow in Audacity, as they can not use a mouse to
slide faders, push buttons or turn knobs!
Meanwhile my announced shortcut emulator "Studioguard Key" has reached
some point of usability indeed! Please have a look at this short video
of the prototype:
(the announced website studioguard.eu is not finished yet, sry)
The blind pro radio producer and musician Robbie Sandberg from Hamburg,
(who also contributed his voice for speach of the "Key") has one in use
since months for recording and editing his works! Robbie even configured
the buttons functions and is my top consultant!
My target is a combined MIDI and shortcut controller, because MIDI would
allow continous volume & pan changes and not step by step ;-)
MIDI mix-automatation could be a desired further step in Audacity...
I´m very aware, that it is a hell of a lot of work for you developers,
no doubt! I´m confident that one day it will happen though :)
I can´t program, but I have all necessary MIDI facilities set up in my
studio so all I can offer is testing functions if needed.
Thanks again and kind regards to all of you! I´ll follow the thread :)
Marcus
P.S.: my Mails to blind devel member David Engebretson continousely
bounce! Maybe he can contact me via this platform or by using another
mailaddress. His provider seems to have blocked my address?
Marcus C. Diess / StudioGuard / WAVESOUND Art, Sound & Broadcast
A-5020 Salzburg / AUSTRIA - EUROPE
mobile: +43 (0)660 4416480
mail: ***@wavesound.at
http://studioguard.eu (coming soon)
http://ohrenblicke.eu
http://facebook.com/pages/studioguard/109469439140008
http://servus.at/tongaonair/travelogue_de.html
http://freiesradio.at
http://radiofabrik.at
http://commit.at Workshops für Tontechnik und Sounddesign
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Partner von RTVtec Sendetechnik http://www.rtvtec.at
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Stay tuned on Free Community FM-Radios Worldwide for Real Content!
Marconi invented it, we´ve perfected it! ;-)
first I wanted to congratulate you for the release of V.2.1.3 and thank
all of you for their great contributions!!! - all I could contribute
were some Euros a minute ago...
Great, that some of you put effort in developing MIDIbility, but may I
remind you, that my attempt in 2016 was rather related to MIDI-control
of faders, knobs and buttons via an external MIDI controller unit, than
composing music with MIDI. (which would be great also, but secondary)
because MIDI Control would specially improve visually impaired user´s
accessability and workflow in Audacity, as they can not use a mouse to
slide faders, push buttons or turn knobs!
Meanwhile my announced shortcut emulator "Studioguard Key" has reached
some point of usability indeed! Please have a look at this short video
of the prototype:
(the announced website studioguard.eu is not finished yet, sry)
The blind pro radio producer and musician Robbie Sandberg from Hamburg,
(who also contributed his voice for speach of the "Key") has one in use
since months for recording and editing his works! Robbie even configured
the buttons functions and is my top consultant!
My target is a combined MIDI and shortcut controller, because MIDI would
allow continous volume & pan changes and not step by step ;-)
MIDI mix-automatation could be a desired further step in Audacity...
I´m very aware, that it is a hell of a lot of work for you developers,
no doubt! I´m confident that one day it will happen though :)
I can´t program, but I have all necessary MIDI facilities set up in my
studio so all I can offer is testing functions if needed.
Thanks again and kind regards to all of you! I´ll follow the thread :)
Marcus
P.S.: my Mails to blind devel member David Engebretson continousely
bounce! Maybe he can contact me via this platform or by using another
mailaddress. His provider seems to have blocked my address?
Send audacity-devel mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/audacity-devel
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of audacity-devel digest..."
1. Re: [Audacity-quality] Merging more changes in MIDI track
behavior; how else to improve MIDI tracks? (Paul Licameli)
2. When scrolling left of zero enabled, negative times in ruler
are no longer blue (Paul Licameli)
----------------------------------------------------------------------
Message: 1
Date: Tue, 2 May 2017 10:22:52 -0400
Subject: Re: [Audacity-devel] [Audacity-quality] Merging more changes
in MIDI track behavior; how else to improve MIDI tracks?
Content-Type: text/plain; charset="utf-8"
I got my own travis build and I see it is link failure.
There is no Makefile.am at all in portmidi, so that library is not complied
on Linux.
PRL
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Wed, 3 May 2017 10:13:15 -0400
Subject: [Audacity-devel] When scrolling left of zero enabled,
negative times in ruler are no longer blue
Content-Type: text/plain; charset="utf-8"
Is this intended? This is a consequence of the commit that brought in Dark
028ed19d908d80fe70bf030089ca8210e75f8af4
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel
End of audacity-devel Digest, Vol 133, Issue 3
**********************************************
--To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/audacity-devel
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of audacity-devel digest..."
1. Re: [Audacity-quality] Merging more changes in MIDI track
behavior; how else to improve MIDI tracks? (Paul Licameli)
2. When scrolling left of zero enabled, negative times in ruler
are no longer blue (Paul Licameli)
----------------------------------------------------------------------
Message: 1
Date: Tue, 2 May 2017 10:22:52 -0400
Subject: Re: [Audacity-devel] [Audacity-quality] Merging more changes
in MIDI track behavior; how else to improve MIDI tracks?
Content-Type: text/plain; charset="utf-8"
I got my own travis build and I see it is link failure.
There is no Makefile.am at all in portmidi, so that library is not complied
on Linux.
PRL
Moved to devel.
Configure and build logs attached.
Steve
it
1
PRL
Ignore that, I misread my logs.
PRL
of
+
features
correspondingly
channel,
with
and
occur
buttons
in
it
and
it,
would
we
the
the
channels
than
------------------
------------------
------------------------------------------------------------
------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel
-------------- next part --------------Configure and build logs attached.
Steve
On Tue, May 2, 2017 at 3:44 AM, Steve the Fiddle
Steve
Sorry, I missed that. Well, how difficult is the fix that would make
I reviewed Pokechu22's work and I have merged the parts considered
ready,
after rebasing the commits and permuting their sequence a bit. Also
the new
call to MakeParentModifyState which I don't doubt is correct. Just
two
commits still left out.
For convenience I have also enabled EXPERIMENTAL_MID_OUT on all
platforms.
What is "convenient" about pushing code that does not build?ready,
after rebasing the commits and permuting their sequence a bit. Also
the new
call to MakeParentModifyState which I don't doubt is correct. Just
two
commits still left out.
For convenience I have also enabled EXPERIMENTAL_MID_OUT on all
platforms.
Steve
build on Linux?
cs.po:4752: format specifications in 'msgid' and 'msgstr' for argument
cs.po:4752: format specifications in 'msgid' and 'msgstr' for argument
are not the same
So is that the same build error you see?PRL
PRL
This is not final, but may be reverted before release.
Note tracks are already a feature of released Audacity. Described
below are
new enhancements to editing and visualizing them. These changes are
independent of playback, and so WILL BE IN 2.2.0, even if the rest
Note tracks are already a feature of released Audacity. Described
below are
new enhancements to editing and visualizing them. These changes are
independent of playback, and so WILL BE IN 2.2.0, even if the rest
the
project is unready. There are bugs yet, but I expect them to be
easily
fixed in the time frame.
A selection in a Note track should now be silenceable (as with Ctrl
project is unready. There are bugs yet, but I expect them to be
easily
fixed in the time frame.
A selection in a Note track should now be silenceable (as with Ctrl
L and
Ctrl + T) and sync-lock adjustments of Note tracks should be
implemented (as
when deleting or inserting in a wave track above it) . These
Ctrl + T) and sync-lock adjustments of Note tracks should be
implemented (as
when deleting or inserting in a wave track above it) . These
need
testing.
Ctrl + Shift + F affects both MIDI and Wave track heights.
The old code is now enabled, to draw sixteen toggle buttons that you
can
click to hide (and, when playback is enabled, to mute)
testing.
Ctrl + Shift + F affects both MIDI and Wave track heights.
The old code is now enabled, to draw sixteen toggle buttons that you
can
click to hide (and, when playback is enabled, to mute)
colored notes on the piano roll display. Left to toggle one
right
to solo or un-solo that channel.
Undo/Redo restores the state of MIDI channel muting, analogously
to solo or un-solo that channel.
Undo/Redo restores the state of MIDI channel muting, analogously
wave
track muting state.
The display of the top and bottom edges of the buttons is not right
yet,
perhaps because James independently changed the height of the Mute
track muting state.
The display of the top and bottom edges of the buttons is not right
yet,
perhaps because James independently changed the height of the Mute
Solo
buttons and the sliders. So don't make screen shots yet.
Probably, some constants in TrackPanel.cpp simply need changing and
that's
all. But I would rather see this fixed with enum names that are
reused,
than still see "magic numbers" (like 19 or 34 or 38 or 48) that
buttons and the sliders. So don't make screen shots yet.
Probably, some constants in TrackPanel.cpp simply need changing and
that's
all. But I would rather see this fixed with enum names that are
reused,
than still see "magic numbers" (like 19 or 34 or 38 or 48) that
in
multiple places and look only "coincidentally" the same.
If I drag the bottom edge of the note track up, then controls should
disappear as the height becomes too small. But I don't see this
happening
cleanly. The borders of Mute and Solo remain even after those
multiple places and look only "coincidentally" the same.
If I drag the bottom edge of the note track up, then controls should
disappear as the height becomes too small. But I don't see this
happening
cleanly. The borders of Mute and Solo remain even after those
disappear. This does not happen with Wave tracks. Also when the
colored
buttons disappear, a short vertical stroke appears over part of the
menu
button.
Pokechu: I may misunderstand?
should #define CHANNEL_BIT(c) (1 << (c & ALL_CHANNELS))
instead read #define CHANNEL_BIT(c) ((1 << c) & ALL_CHANNELS)
The MIDI playback project will invite users to make more use of MIDI
tracks,
and therefore to try editing them. Such existing but little used
editing
features as we already have, need reexamining and improvement.
Time-shifting (Repeat, Reverse, Change Speed, Change Tempo) and
pitch-shifting effects (Change Speed again, and Change Pitch) need
some
renewed testing. (These lists may not be exhaustive.)
A change in the status bar message, for mouse-over of the colored
buttons,
is still lacking. (See TrackPanel::SetCursorAndTipWhenInLabel)
It seems that editing operations like copy, cut, paste, delete, etc.
affect
MIDI notes according to whether the onset of the notes is in the
selected
time range. The sustain or release of the notes doesn't matter.
This is unlike the behavior of wave tracks. This is not to say it's
wrong,
MIDI being a different thing after all.
Whether we agree that it is right or wrong, the editing behavior we
see
should be consistently the right behavior.
There is a "stretching" feature of note tracks. You can even do it
colored
buttons disappear, a short vertical stroke appears over part of the
menu
button.
Pokechu: I may misunderstand?
should #define CHANNEL_BIT(c) (1 << (c & ALL_CHANNELS))
instead read #define CHANNEL_BIT(c) ((1 << c) & ALL_CHANNELS)
The MIDI playback project will invite users to make more use of MIDI
tracks,
and therefore to try editing them. Such existing but little used
editing
features as we already have, need reexamining and improvement.
Time-shifting (Repeat, Reverse, Change Speed, Change Tempo) and
pitch-shifting effects (Change Speed again, and Change Pitch) need
some
renewed testing. (These lists may not be exhaustive.)
A change in the status bar message, for mouse-over of the colored
buttons,
is still lacking. (See TrackPanel::SetCursorAndTipWhenInLabel)
It seems that editing operations like copy, cut, paste, delete, etc.
affect
MIDI notes according to whether the onset of the notes is in the
selected
time range. The sustain or release of the notes doesn't matter.
This is unlike the behavior of wave tracks. This is not to say it's
wrong,
MIDI being a different thing after all.
Whether we agree that it is right or wrong, the editing behavior we
see
should be consistently the right behavior.
There is a "stretching" feature of note tracks. You can even do it
2.1.3. But I think its behavior is weird and buggy. How do we fix
for
2.2.0? If nobody finds the time to fix this feature, then I am
inclined to
disable it.
Select a region of a note track. Put the cursor in the selection
2.2.0? If nobody finds the time to fix this feature, then I am
inclined to
disable it.
Select a region of a note track. Put the cursor in the selection
near
the middle of the track height. Cursor changes to a box with a
cross-hair.
Click and drag left and right, and see changes in the timing of the
notes,
but not the pitch.
Notes both within the selection, and right of it, but not left of
the middle of the track height. Cursor changes to a box with a
cross-hair.
Click and drag left and right, and see changes in the timing of the
notes,
but not the pitch.
Notes both within the selection, and right of it, but not left of
can be
changed.
I don't understand the intended behavior. Actual behavior is very
weird.
It is not the case that the results you see are simply a function of
mouse x
coordinate. Rather, results are path dependent.
Incremental changes are not consolidated in Undo history, as we
changed.
I don't understand the intended behavior. Actual behavior is very
weird.
It is not the case that the results you see are simply a function of
mouse x
coordinate. Rather, results are path dependent.
Incremental changes are not consolidated in Undo history, as we
do for
changes like time-shift of clips.
In my opinion, all editing operations should affect channels
independently
of whether they are mute, just as it is done with wave tracks. The
analogy
makes sense. If you argue for the opposite, still again, whatever
changes like time-shift of clips.
In my opinion, all editing operations should affect channels
independently
of whether they are mute, just as it is done with wave tracks. The
analogy
makes sense. If you argue for the opposite, still again, whatever
implement should be consistent across all operations.
Consider the following speculative implications to be much lower
priority
than the rest of the playback project; defer to future versions if
time does
not permit. Let's think about them some but not get diverted.
Would it make better sense to change display of muted channels in
Consider the following speculative implications to be much lower
priority
than the rest of the playback project; defer to future versions if
time does
not permit. Let's think about them some but not get diverted.
Would it make better sense to change display of muted channels in
piano
roll, so they are not completely invisible?
Would we also want some means to edit channels separately too? At
roll, so they are not completely invisible?
Would we also want some means to edit channels separately too? At
least, perhaps, a drop-down menu item that moves the unmuted
to a
new note track?
Splitting of a note track into channels suggests merging is needed
too.
Or is my opinion wrong: should the state of colored buttons be a
"selection" state, finer than track selection, and affecting more
new note track?
Splitting of a note track into channels suggests merging is needed
too.
Or is my opinion wrong: should the state of colored buttons be a
"selection" state, finer than track selection, and affecting more
playback, but rather affecting all editing?
PRL
------------------------------------------------------------
PRL
------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-quality
------------------------------------------------------------engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-quality
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-quality
------------------------------------------------------------engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-quality
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Wed, 3 May 2017 10:13:15 -0400
Subject: [Audacity-devel] When scrolling left of zero enabled,
negative times in ruler are no longer blue
Content-Type: text/plain; charset="utf-8"
Is this intended? This is a consequence of the commit that brought in Dark
028ed19d908d80fe70bf030089ca8210e75f8af4
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel
End of audacity-devel Digest, Vol 133, Issue 3
**********************************************
Marcus C. Diess / StudioGuard / WAVESOUND Art, Sound & Broadcast
A-5020 Salzburg / AUSTRIA - EUROPE
mobile: +43 (0)660 4416480
mail: ***@wavesound.at
http://studioguard.eu (coming soon)
http://ohrenblicke.eu
http://facebook.com/pages/studioguard/109469439140008
http://servus.at/tongaonair/travelogue_de.html
http://freiesradio.at
http://radiofabrik.at
http://commit.at Workshops für Tontechnik und Sounddesign
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Partner von RTVtec Sendetechnik http://www.rtvtec.at
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Stay tuned on Free Community FM-Radios Worldwide for Real Content!
Marconi invented it, we´ve perfected it! ;-)