FAQ on 64 bit Audacity

I think we're being asked often enough now about 64 bit (mainly Vista)
to justify a FAQ. I thought something like this: 

"Current versions of Audacity should run on 64-bit systems, and have been
tested on 64-bit Windows Vista and Linux. On Windows and Linux, working
sound card drivers specific to the 64-bit operating system will be required,
so these must be updated if upgrading from a 32-bit to 64-bit operating
system.  Generally speaking, 64-bit systems will use more physical memory 
than 32-bit systems. Users upgrading from 32-bit Windows XP to 64-bit
Windows Vista should take this and the increased system demands of Vista
into account when considering Audacity's <a
href="http://audacity.sourceforge.net/download/windows#sysreq">system
requirements</a>. 

Another suggestion for the last sentence (maybe better):

"Users upgrading from 32-bit Windows XP to 64-bit Windows Vista should 
make especially sure their computer is well above Audacity's minimum
<a href="http://audacity.sourceforge.net/download/windows#sysreq">
system requirements</a>.

I figured I might link to this FAQ from the Windows download pages. 
Any suggestions for improvement welcome.   

Gale 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes

mpg/mpeg and m4r import

I've made a few changes (bottom of e-mail) to Audacity locally which
work fine for me, as per recent discussions on this subject. So I'd like
to commit these if no objections (or unless I missed something). These
mean:

* Mpeg/Mpg Videos containing PCM audio will now import via FFmpeg 
   using the  "all files" and "all supported files" filters, instead of
   just hanging. Importing mpg/mpeg in builds where USE_FFMPEG 
   is undefined will now produce an error suggesting the audio should
   be extracted from the video. The only "loss" in these builds is that
   you can't now import mpg/mpeg video with mpeg type audio, but 
   that's of little use IMO as the audio is extremely noisy with frequent
   heavy clicks.

* M4r ringtones can now be imported in FFmpeg builds without having 
   to use the "all files filter" to find them and acknowledge an importing 
   error.  From what research I've done, most m4r will be unencrypted,
   as the ones from iTunes store will still be called m4p, and I guess
   iPhones will make m4r more ubiquitous. In non FFmpeg builds, users
   will now get the more helpful "AAC" importing error instead of the
   (useless) suggestion they import raw.  

Tested in both FFmpeg and non-FFmpeg builds. I guess I could actually 
add AVI so that throws a more relevant error as well? 

Gale 

Import.cpp: 

New Developer

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
audacity-devel mailing list
audacity-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Clips in projects with many tracks jump upwards when snapping

Reported on Windows XP, and confirmed by me on same OS. 

To reproduce:

* Generate 32 tones of 30 seconds each (generating and duplicating
   will save time)
* Edit > Select > None
* View > Fit Vertically to see what you're doing
* Navigate to the bottom track and drag its clip rightwards past the end
   of the clip above
* Very likely, when the snap to the other clips above occurs, the clip
   will seem to "disappear". It hasn't, but it's jumped many tracks
   above.
* If it does not reproduce at once, dragging a few more clips should 
   do so.   

Seemingly, the more tracks there are, the sooner it will reproduce (I 
cannot reproduce with less than twelve tracks). Direction of drag is
irrelevant. If you start dragging at the top, those clips don't seem to
have any problem. The clip can be restored with Undo, but will now
always jump if dragged.

Any confirmations on Mac and Linux please? 

Gale 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Tools Toolbar hover text

I'm often struck how few users are aware of the shortcuts for the 
six tools on Tools Toolbar (let alone "D" to move between them).

So given F1 to F6 are not otherwise discoverable in the main interface,
and are common to all OS'es (any problems with Linux?), how about 
adding them to the hover text? Good/bad idea?

Gale 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: EXPERIMENTAL_MODULES

Further our discussion about possible wordings on the Transport Menu, 
I'm figuring there's no consensus to change "Software Playthrough" 
to "Software Monitoring" or something else containing "monitor(ing)",
so that leaves us to match up the wording on the "Playthrough" section
of Audio I/O Preferences. 

For the first item I'd suggest instead of "Play other tracks while
recording new one", just stick "Overdub" in front viz:

*Overdub: Play other tracks while recording new one"

For the second "Software Playthrough" item, I feel "Play new track
while recording it" means people miss they don't need to record
to listen to the input, and this generates a fair few questions from
users of USB playback devices.

So a couple of suggestions:

*"Software Playthrough: Listen to input (needs monitoring enabled if 
  not recording)"

*"Software Playthrough: Listen to input while recording or monitoring"

I think the second idea gives us room to retain the current "(uncheck
when recording stereo mix)", at the end, which is important. 

Any better ideas (or leave as is and accept the limitation of the current
wording)?   

Also I don't think we discussed before, but would it be worth longer
term adding "Monitor (on/off)" to the Transport menu? 

For :

* makes this command VI-accessible
* convenience
* helps establish monitor as something independent 
   of software playthrough, and proximity to that item
   lets people play and learn?

Against:

* maybe not strictly a "Transport" item?

Gale 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Audacity for a flash/java style run in site idea

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
audacity-devel mailing list
audacity-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Memory Leaks on Effect Preview in src/effects/Effects.cpp

This may already be a known issue, but I noticed that 
Effect::ReplaceProcessedWaveTracks properly removes and deletes 
mWaveTracks entries on performing any of the actual effects, but not on 
the preview-generated effects when pressing the dialog's Preview button.

Each time a preview is executed, (pTrack == pInWaveTrack) always 
evaluate to false inside the do while loop, and never deletes each 
pInWaveTrack (mWaveTracks entries) before it deletes mWaveTracks itself, 
therefore leaking the memory.

It appears performing actual effect has mWaveTracks entries in mTracks 
so when pTrack does equal pInWaveTrack, mWaveTracks entries are deleted, 
but for previews there are none in mTracks.

I don't know how to fix this (modify the code to delete them in that 
part of the code or add mWaveTracks entries into mTracks for 
preview-generated effects, etc.), either way it looks way too 
complicated for me now.  I'll leave it up to your more capable hands.

Just thought I'd let you know.

Thanks,
  Dawson

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: pluggo

It's never been clear to me from the project pages for LV2, so forgive
any stupidity, but will the work we've done here allow VST and Audio
Units (Mac) plug-ins to be categorised, if so how? (I know that a
;categories line allows Nyquist plug-ins to be sorted). This would help
the Mac users who get "Pluggo" plug-ins loaded to at least categorise
them, even if we don't have a Preference to stop Audacity loading
plug-ins from system paths.   

Thanks 

Gale 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Export MIDI refined, NoteTrack selection behavior changed

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
audacity-devel mailing list
audacity-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/audacity-devel

code submission

I'm looking at adding a loop and BPM toolbar to Audacity for internal
use at our company (think a simple version of Recycle).   I'm happy to
contribute what I create back to the official app.   I have a couple
of questions:

1) Though an archive search didn't turn up much of anything, I'm sure
this type of functionality has been discussed before.  Is someone
already working on loop editing functionality?

2) If it has been discussed before, does anyone remember any
minefields (either in the code or with the philosophy)?

3) How "complete" does my code need to be before I can submit a first
diff for comment?

4) Other than the Audacity sourcecode itself, are there any code style
guidelines or templates?

Thanks,
Patrick Roberts

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/