Age | Commit message (Collapse) | Author |
|
This fixes an issue with dsp_configure not being when there are
only MIDI signals at the given insertion point.
|
|
The issue is that when ExportDialog is destroyed
ExportFileNotebook::FilePage::on_hide is called which in turn calls
ExportProfileManager::save_format_to_disk() in order to save changes to the
analysis and soundcloud upload checkboxes. This then causes the
ExportProfileManager::FormatListChanged signal to be emitted, which in all
other cases is emitted when the format list is modified so that the GUI can
rebuild the format selector menu in ExportFormatSelector::update_format_list
when a format is added or removed.
The problem when doing this in the destructor is that some of the widgets have
already been destroyed, specifically the issue was in
ExportFileNotebook::update_soundcloud_upload trying to access the
soundcloud_selector member that had already had its destructor called.
As it is not necessary to call this signal in the first place and it just
causes unnecessary GUI updates remove the signal emission.
|
|
|
|
This is a potential fix for unreliable preset load/restore.
(http://mixbus.harrisonconsoles.com/forum/thread-1970-post-21486.html#pid21486)
Since a Glib Mutex can't be copy-constructed an explicit copy c'tor
is needed.
|
|
|
|
* do not include _by_name() API. Port names are locale dependent
* proper whitespace (after comma, before bracket) and styleguide
|
|
This reverts commit faf44386460b6cdda0aa249eb138e8fd82700194.
|
|
|
|
* remove unused functions
* don't globally export C functions that are only used locally
|
|
(libardour)
|
|
|
|
let the user/developer know if this does occur rather than just silently
skipping the file.
Fix some whitespace issues while we are changing indentation.
|
|
The error is generated by a glib function so use the glib version of this
function(it also consistent with usage in the rest the file).
|
|
The paths are in UTF-8 encoding and ::rename expects paths in the system
codepage encoding so ::rename will fail for any paths that contain characters
that aren't in the system codepage.
This fixes Flush Wastebasket on Windows where paths contain characters that
aren't in the system codepage(usually most non-ascii characters).
|
|
For consistency when calling glib functions and to get UTF-8 strings for
display.
|
|
The path is in UTF-8 encoding so use Glib functions to properly support paths
containing characters that aren't in the system codepage.
This fixes Clean-up Unused Sources on Windows where paths contain characters
that aren't in the system codepage(usually most non-ascii characters).
|
|
xml state
|
|
Some Mixbus users (on Windows) have reported seeing ludicrously high figures for the amount of disk space that'll be recovered if they choose to clean up unused sources. I can't see anything obviously wrong in Ardour's code - except for one situation where we don't check a return value after calling 'g_stat()'.
On Windows, the relevant path should be (hopefully!) in UTF8 format and the first thing that g_stat() does is to convert it to UTF16. If that conversion fails for some reason, g_stat() will return an error status and statbuf will be uninitialized - but at the moment, we're not checking this. As an experiment, let's check the returned value and find out if these user reports go away.
Unfortunately, if it does fix the problem then we've got an even bigger problem - because somehow, a Windows user can create source files with invalid names which can't be later deleted!!
|
|
AudioEngine::stop() if running() is not true and _backend->stop() is true, mutex was being unlocked without being locked.
|
|
seamless looping (if using)
|
|
|
|
playback buffer, and do not use port offset to shift data in time either (it should be correct)
|
|
events read from the MidiBuffer
|
|
really use it)
|
|
|
|
|
|
|
|
|
|
offset
if the output is then re-used, MIDI data is readjusted to not use the global port offset
|
|
Port::port_offset()
|
|
|
|
methods from framecnt_t to frameoffset_t
|
|
framecnt_t to frameoffset_t
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Clearing location markers is a frequent task and should be automizable. For
example it is handy to clear all the markers when restarting the recording
from scratch after a failed recording.
|
|
|
|
If a Session is saved and then the start or end session markers are moved,
closing the Session will not result in "Unsaved Session" dialog being presented
even though the Session has been modified. This change sets the Session as
modified when either the Session start or end markers are modified.
|
|
when looking for the file at session load
|
|
|
|
|
|
|
|
5.3-41
|
|
|
|
|