On 12/9/05, Leland Lucius wrote:
> It worked for me on WinXP too, but the problem showed up on
> Linux. As far as I could gather, GTK does not like to
> popup a menu on a button down event. Seems it needs the
> button up one. (Or Audacity may have been Skip()ing the
> event it needed.)
>
> In any case, I was able to "fix" it and the pressed state
> of the title bar by making it work like all of the rest
> of the label "controls".
Does trackpanel menu open on a single click now again?
Alexandre

Hi
I updated all the Audacity files from CVS HEAD tonight and tried to build it
from scratch (on the way to committing a new version of the Equalizer). I
came across the following 3 (fairly minor) problems which stop the
Unicode-Release version from compiling. Should I send a patch or commit the changes?
The discussion between Markus and Vaughan (and others) back in June/July
2005 at
_http://sourceforge.net/mailarchive/forum.php?thread_id=7552958&forum_id=1949_
(http://sourceforge.net/mailarchive/forum.php?thread_id=7552958&forum_id=1949)
gave me the solution to the first two of these problems.
Problem:
Compiling...
ImportFLAC.cpp
..\src\import\ImportFLAC.cpp(193) : warning C4355: 'this' : used in base
member initializer list
..\src\import\ImportFLAC.cpp(205) : error C2664:
'FLAC::Decoder::File::set_filename' : cannot convert parameter 1 from 'const wxChar *' to 'const char *'
Types pointed to are unrelated; conversion requires reinterpret_cast,
C-style cast or function-style cast
Fix:
change
bool success = mFile->set_filename(mName.fn_str());
to
bool success = mFile->set_filename(mName.mb_str());
Note: warning not fixed, or understood, by me.
Problem:
Compiling...
Export.cpp
..\src\export\Export.cpp(157) : error C2308: concatenating mismatched strings
Concatenating wide "Each of your tracks will be " with narrow "saved as
separate channels in the exported file."
Fix:
change
ShowWarningDialog(project, wxT("MixMulti"), _("Each of your tracks
will be "
"saved as separate channels in the exported file."));
to
ShowWarningDialog(project, wxT("MixMulti"), _("Each of your tracks
will be saved as separate channels in the exported file."));
Note: no great solution appears to have been found back in June/July. My
editor wraps to the next line so I'm happy!
Problem:
Linking...
libresampleud.lib(resample.obj) : warning LNK4075: ignoring
'/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification
LIBCMT.lib(calloc.obj) : error LNK2005: _calloc already defined in
LIBCMTD.lib(dbgheap.obj)
LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other
libs; use /NODEFAULTLIB:library
.\Unicode_Debug/audacity.exe : fatal error LNK1169: one or more multiply
defined symbols found
Fix:
Project -> Audacity Properties... -> Configuration Properties -> Linker ->
Input -> Ignore Specific Libraries -> LIBCMT
Note: Well, it did tell me what to do really...
So, shall I fix it for me or will it muck it up for others?
TTFN
Martyn

Passing through arbitrary headers from NIST WAV files actually sounds
more complicated to me than the specific case of transcriptions. I'm
tempted to say I'd rather implement a feature to aid in working with
files with transcriptions, by importing the transcriptions into a label
track, then exporting the label track into the WAV.
Among the problems with arbitrary NIST headers we don't understand:
* What if the user imports two WAV files and exports the mix? Does it
grab the headers from one, the other, or both?
* What if the headers are really large? We'd need to provide the
ability for the user to get rid of them.
Could you tell me more about the specific headers you're using for
transcription? Is there a format specification?
- Dominic
Markus Meyer wrote:
> David,
>
> Audacity uses libsndfile to read and write WAV files, and I doubt that
> libsndfile supports those extra chunks. Anyway, Audacity does not
> actively "discard" chunks in the WAV file. Actually, the logic used is
> the other way around: Since WAV is not Audacity's native format, it
> (i.e. libsndfile) only reads the pieces of information from the WAV file
> it understands, ignoring all possible other chunks present in the WAV
> file. When writing a WAV file, it creates a completely new file, which
> may very well have a totally different structure.
>
> OTOH, I think it could be possible to add this functionality fairly easy
> by writing a very simple WAV file parser which is able to find the
> Nist-specific chunks inside the WAV file. It is not necessary that this
> parser actually understands the information present in those chunks, it
> only has to locate it, and store it in some place. When writing a WAV
> file, the information could then be inserted into the stream again. If
> someone would implement this functionality, I'd be happy to commit it to
> CVS HEAD.
>
>
> Markus
>
> David R. Sky schrieb:
>
>> Hi Craig,
>>
>> This doesn't sound like a "bug" to me per se, since Audacity
>> doesn't have a "export as Nist .wav", only "export as .wav".
>>
>> But it does sound like an interesting addition, "save header
>> information: yes/no".
>>
>> I'll cc this post to the audacity development list.
>>
>> David
>>
>> From: "Craig Vanderborgh" craigvanderborgh at mail.com
>> Subject: NIST Header Troubles
>>
>> Hello Audacity Users:
>>
>> We are newcomers to Audacity, and we intend to use it for
>> viewing/editing/l= istening to speech samples. Our speech databases
>> are in the NIST ".wav" fo= rmat. To our delight, Audacity is able
>> to correctly open and play our NIST= -headered speech data files.
>> This is a great start.
>>
>> Unfortunately, Audacity has the "audacity" to discard any header
>> fields tha= t it thinks are uninteresting. So, for example, if we
>> edit one of our file= s w/Audacity, the transcription we have
>> stored in our header is lost when t= he file is re-saved.
>>
>> This is a bummer, and actually it seems to us like a bug. We are
>> reporting= it as such. If noone here has any interest in fixing
>> this, can we submit = a patch when we get around to fixing it
>> ourselves?
>>
>> Please advise.
>>
>> Thanks in advance, craig vanderborgh voxware incorporated
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> language
>> that extends applications into web and mobile media. Attend the live
>> webcast
>> and join the prime developer group breaking into this new coding
>> territory!
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> _______________________________________________
>> Audacity-devel mailing list
>> Audacity-devel@...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Audacity-devel mailing list
> Audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel