Export Options WAS: (Export Multiple) Options dialog goes on top of all applications in windows XP

68 Messages Forum Options Options
Embed this topic
Permalink
1 2 3 4
Gale Andrews
Export Options WAS: (Export Multiple) Options dialog goes on top of all applications in windows XP
Reply Threaded MoreMore options
Print post
Permalink

| From Jan Kolar <kolar@...>
| Thu, 19 Jun 2008 02:07:09 +0200
| Subject: [Audacity-devel] (Export Multiple) Options dialog goes on top of all applications in windows XP
> This one remains in recent built from Gale, (June 18th)
> - Format "(external program)" is broken: Options does not show
> anything  (no action)
> (from Export, Export Multiple and Export Selection dialogs)

Hi LRN

Is this one being looked into for us? It only broke recently
and without it, any MP3 export other than CBR 128 kbps  
is impossible, given the MP3 Export bug.

You said the individual format listings for "uncompressed"
types in the export dialogue was temporary, what's the
ultimate plan? How about two groupings:

* WAV or AIFF (uncompressed)
* Other uncompressed types


Thanks

Gale




-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
LRN
Re: Export Options WAS: (Export Multiple) Options dialog goes on top of all applications in windows XP
Reply Threaded MoreMore options
Print post
Permalink
Gale Andrews wrote:
> | From Jan Kolar<kolar@...>
> | Thu, 19 Jun 2008 02:07:09 +0200
> | Subject: [Audacity-devel] (Export Multiple) Options dialog goes on top of all applications in windows XP
>    
>> This one remains in recent built from Gale, (June 18th)
>> - Format "(external program)" is broken: Options does not show
>> anything  (no action)
>> (from Export, Export Multiple and Export Selection dialogs)
>>      
I'll look into it.
How does "external program" works exactly? Audacity feeds WAV to
process' stdin?
> You said the individual format listings for "uncompressed"
> types in the export dialogue was temporary, what's the
> ultimate plan? How about two groupings:
>
> * WAV or AIFF (uncompressed)
> * Other uncompressed types
>    
It's not for me to decide. The list of uncompressed types was just a way
to demonstrate new exporting procedure (FFmpeg exporter didn't existed
at the moment, and it's still not in tree even now).
I think i'll just shrink the list back to one option - there's almost
zero differences between "uncompressed types". Unless someone explicitly
asks me to keep some of the exported types as separate entries and
explains why it is necessary.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Richard Ash (audacity-help)
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
On Sat, 2008-06-21 at 13:51 +0400, LRN wrote:
> I'll look into it.
> How does "external program" works exactly? Audacity feeds WAV to
> process' stdin?

Yes, a WAV file with 16 bit data in it. Mono/Stereo depending on the
project contents, project sample rate (try 'file -' as the command and
show program output to see what a given project produces).

For me, external program exports are working OK - I've just done a 40
minute export to Ogg Vorbis using oggenc OK.

> > You said the individual format listings for "uncompressed"
> > types in the export dialogue was temporary, what's the
> > ultimate plan? How about two groupings:
> >
> > * WAV or AIFF (uncompressed)
> > * Other uncompressed types
> >    
> It's not for me to decide. The list of uncompressed types was just a way
> to demonstrate new exporting procedure (FFmpeg exporter didn't existed
> at the moment, and it's still not in tree even now).
> I think i'll just shrink the list back to one option - there's almost
> zero differences between "uncompressed types". Unless someone explicitly
> asks me to keep some of the exported types as separate entries and
> explains why it is necessary.

I would suggest "Default WAV" pointing to 16-bit PCM WAV and "Default
AIFF" pointing to 16-bit AIFF as convenience entries for people creating
CDs, the rest all go into the uncompressed types entry (if people want
other sorts of WAV / AIFF they would do them by clicking options from
"other", I wouldn't want Default WAV to be changeable to some other bit
depth, because in a lot of software there is only one sort of WAV - 16
bit.

Richard


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Richard Ash (audacity-help)
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
On Sun, 2008-06-22 at 16:37 +0100, Richard Ash wrote:
> > I think i'll just shrink the list back to one option - there's almost
> > zero differences between "uncompressed types". Unless someone explicitly
> > asks me to keep some of the exported types as separate entries and
> > explains why it is necessary.

At the moment there is also a bug - if you export one file, choosing WAV
and selecting 32-bit encoding, it exports 32-bit data. If you then go
back to do another export, then the encoding has been changed back to
16-bit, so you have to remember to keep changing it to the correct
value. You didn't use to have to do this - it used to remember your
format choices between exports.

Richard


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
LRN
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
Richard Ash wrote:

> On Sun, 2008-06-22 at 16:37 +0100, Richard Ash wrote:
>    
>>> I think i'll just shrink the list back to one option - there's almost
>>> zero differences between "uncompressed types". Unless someone explicitly
>>> asks me to keep some of the exported types as separate entries and
>>> explains why it is necessary.
>>>        
>
> At the moment there is also a bug - if you export one file, choosing WAV
> and selecting 32-bit encoding, it exports 32-bit data. If you then go
> back to do another export, then the encoding has been changed back to
> 16-bit, so you have to remember to keep changing it to the correct
> value. You didn't use to have to do this - it used to remember your
> format choices between exports.
>
>    
Fixed.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
LRN
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by Richard Ash (audacity-help)
Richard Ash wrote:
> I would suggest "Default WAV" pointing to 16-bit PCM WAV and "Default
> AIFF" pointing to 16-bit AIFF as convenience entries for people creating
> CDs, the rest all go into the uncompressed types entry (if people want
> other sorts of WAV / AIFF they would do them by clicking options from
> "other", I wouldn't want Default WAV to be changeable to some other bit
> depth, because in a lot of software there is only one sort of WAV - 16
> bit.
>    
Done.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by Richard Ash (audacity-help)

| From Richard Ash <richard@...>
| Sun, 22 Jun 2008 16:37:17 +0100
| Subject: [Audacity-devel] Export Options

> On Sat, 2008-06-21 at 13:51 +0400, LRN wrote:
> > I'll look into it.
> > How does "external program" works exactly? Audacity feeds WAV to
> > process' stdin?
>
> > > You said the individual format listings for "uncompressed"
> > > types in the export dialogue was temporary, what's the
> > > ultimate plan? How about two groupings:
> > >
> > > * WAV or AIFF (uncompressed)
> > > * Other uncompressed types
> > >    
> > It's not for me to decide. The list of uncompressed types was just a way
> > to demonstrate new exporting procedure (FFmpeg exporter didn't existed
> > at the moment, and it's still not in tree even now).
> > I think i'll just shrink the list back to one option - there's almost
> > zero differences between "uncompressed types". Unless someone explicitly
> > asks me to keep some of the exported types as separate entries and
> > explains why it is necessary.
>
>
> I would suggest "Default WAV" pointing to 16-bit PCM WAV and "Default
> AIFF" pointing to 16-bit AIFF as convenience entries for people creating
> CDs, the rest all go into the uncompressed types entry (if people want
> other sorts of WAV / AIFF they would do them by clicking options from
> "other", I wouldn't want Default WAV to be changeable to some other bit
> depth, because in a lot of software there is only one sort of WAV - 16
> bit.

Yes that was my point too, a "convenience" entry for the common use
case, though I don't think "Default" is a terribly good word for the
menu in the case of noobs. I think some programs use terms like "CD
quality" to define this (though they may be setting the sampling rate in
that option too, which we don't).  Or "Standard"?

Do we need separate entries for WAV and AIFF though? I thought that
when we just had the one "WAV, AIFF and other uncompressed types"
entry, that this initialised to WAV on Windows and Linux, and to AIFF
on Mac?


Gale

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by LRN

Hi LRN

I built following Martyn's suggestion of removing NoteTrack.cpp and
ImportMIDI.cpp, then tried exporting some stereo MP4 (AAC) files
against your fix for profile not being correctly exported. Checking the
exported files in iTunes, I got:  

8 kbps LC  > iTunes: 18 kbps LC
16 kbps Main > iTunes: 19 kbps no profile
32 kbps SSR > null file 0 bytes
32 kbps LTP > iTunes: 22 kbps no profile

Should 32 kbps per channel in Audacity end up as 64 kbps given I had
a stereo file?

DBPowerAmp sees the correct profile for the three files that exported,
but has 0 kbps bit rate. Foobar 2000 displays all the exported profiles  
correctly, and displays the same bit rates as iTunes (i.e. not what
Audacity exported).

SSR profile also produces null files when exporting AAC.

Exporting "WAV (Microsoft) 16 bit PCM" now gives 16 bit even if you
choose some other sample format. I think that's correct, but also think you
should grey out the OK button when choosing any of the other options,
or remove them from the list.


Thanks


Gale  
 



-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
LRN
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
Gale Andrews wrote:

> 8 kbps LC>  iTunes: 18 kbps LC
> 16 kbps Main>  iTunes: 19 kbps no profile
> 32 kbps SSR>  null file 0 bytes
> 32 kbps LTP>  iTunes: 22 kbps no profile
>
> Should 32 kbps per channel in Audacity end up as 64 kbps given I had
> a stereo file?
>
> DBPowerAmp sees the correct profile for the three files that exported,
> but has 0 kbps bit rate. Foobar 2000 displays all the exported profiles
> correctly, and displays the same bit rates as iTunes (i.e. not what
> Audacity exported).
>    
Actually, it said "per channel", but in reality it was "per whole file",
because FFmpeg is making the bitrate/channels division internally.
Part of the problem is that max supported bitrate is per channel only,
and it depends on samplerate.
I know how to handle that, but ShuttleGui is resisting my attempts to
change the data.
> SSR profile also produces null files when exporting AAC.
>    
After some digging in libfaac source code i found out that SSR is not
supported. D'oh.
> Exporting "WAV (Microsoft) 16 bit PCM" now gives 16 bit even if you
> choose some other sample format. I think that's correct, but also think you
> should grey out the OK button when choosing any of the other options,
> or remove them from the list.
>    
Fixed.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink

| From LRN <lrn1986@...>
| Sat, 12 Jul 2008 18:02:26 +0400
| Subject: [Audacity-devel] Export Options

> Gale Andrews wrote:
> > 8 kbps LC>  iTunes: 18 kbps LC
> > 16 kbps Main>  iTunes: 19 kbps no profile
> > 32 kbps SSR>  null file 0 bytes
> > 32 kbps LTP>  iTunes: 22 kbps no profile
> >
> > Should 32 kbps per channel in Audacity end up as 64 kbps given I had
> > a stereo file?
> >
> > DBPowerAmp sees the correct profile for the three files that exported,
> > but has 0 kbps bit rate. Foobar 2000 displays all the exported profiles
> > correctly, and displays the same bit rates as iTunes (i.e. not what
> > Audacity exported).
> >    
> Actually, it said "per channel", but in reality it was "per whole file",
> because FFmpeg is making the bitrate/channels division internally.
> Part of the problem is that max supported bitrate is per channel only,
> and it depends on samplerate.
>
> I know how to handle that, but ShuttleGui is resisting my attempts to
> change the data.

I don't know how finnicky iTunes is, but it's more important that we
get the profile appearing correctly in iTunes than in other programs,
because of the number of people using it.

> > SSR profile also produces null files when exporting AAC.
> >    
> After some digging in libfaac source code i found out that SSR is not
> supported. D'oh.

Can we remove it then if it won't work?

> > Exporting "WAV (Microsoft) 16 bit PCM" now gives 16 bit even if you
> > choose some other sample format. I think that's correct, but also think you
> > should grey out the OK button when choosing any of the other options,
> > or remove them from the list.
> >    
> Fixed.

Thanks


Gale




-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
LRN
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
Gale Andrews wrote:

> | From LRN<lrn1986@...>
> | Sat, 12 Jul 2008 18:02:26 +0400
> | Subject: [Audacity-devel] Export Options
>    
>> Gale Andrews wrote:
>>      
>>> 8 kbps LC>   iTunes: 18 kbps LC
>>> 16 kbps Main>   iTunes: 19 kbps no profile
>>> 32 kbps SSR>   null file 0 bytes
>>> 32 kbps LTP>   iTunes: 22 kbps no profile
>>>
>>> Should 32 kbps per channel in Audacity end up as 64 kbps given I had
>>> a stereo file?
>>>
>>> DBPowerAmp sees the correct profile for the three files that exported,
>>> but has 0 kbps bit rate. Foobar 2000 displays all the exported profiles
>>> correctly, and displays the same bit rates as iTunes (i.e. not what
>>> Audacity exported).
>>>
>>>        
>> Actually, it said "per channel", but in reality it was "per whole file",
>> because FFmpeg is making the bitrate/channels division internally.
>> Part of the problem is that max supported bitrate is per channel only,
>> and it depends on samplerate.
>>
>> I know how to handle that, but ShuttleGui is resisting my attempts to
>> change the data.
>>      
>
> I don't know how finnicky iTunes is, but it's more important that we
> get the profile appearing correctly in iTunes than in other programs,
> because of the number of people using it.
>    
>>> SSR profile also produces null files when exporting AAC.
>>>
>>>        
>> After some digging in libfaac source code i found out that SSR is not
>> supported. D'oh.
>>      
>
> Can we remove it then if it won't work?
>    

Just committed the fix.for both. It probably won't fix the iTunes
compatibility, but bitrate setting works more or less correctly now and
is, indeed, bit-rate per channel (damn...i forgot to change the label to
"per channel" again...).
Try testing it on every available bitrate, and maybe with different
sample rates. I think LC is 44100-only.


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
LRN
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by Gale Andrews
Gale Andrews wrote:

> | From LRN<lrn1986@...>
> | Sat, 12 Jul 2008 18:02:26 +0400
> | Subject: [Audacity-devel] Export Options
>    
>> Gale Andrews wrote:
>>      
>>> 8 kbps LC>   iTunes: 18 kbps LC
>>> 16 kbps Main>   iTunes: 19 kbps no profile
>>> 32 kbps SSR>   null file 0 bytes
>>> 32 kbps LTP>   iTunes: 22 kbps no profile
>>>
>>> Should 32 kbps per channel in Audacity end up as 64 kbps given I had
>>> a stereo file?
>>>
>>> DBPowerAmp sees the correct profile for the three files that exported,
>>> but has 0 kbps bit rate. Foobar 2000 displays all the exported profiles
>>> correctly, and displays the same bit rates as iTunes (i.e. not what
>>> Audacity exported).
>>>
>>>        
>> Actually, it said "per channel", but in reality it was "per whole file",
>> because FFmpeg is making the bitrate/channels division internally.
>> Part of the problem is that max supported bitrate is per channel only,
>> and it depends on samplerate.
>>
>> I know how to handle that, but ShuttleGui is resisting my attempts to
>> change the data.
>>      
>
> I don't know how finnicky iTunes is, but it's more important that we
> get the profile appearing correctly in iTunes than in other programs,
> because of the number of people using it.
>    
Installed iTunes. Impressive. This is the slowest software player i ever
encountered.

Research results: iTunes only supports LC-AAC (no HE-AAC, no Main-AAC,
no LTP-AAC). iTunes correctly displays LC-AAC files bitrate.
Looks like i fixed everything, eh?

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink

| From LRN <lrn1986@...>
| Sun, 13 Jul 2008 10:17:01 +0400
| Subject: [Audacity-devel] Export Options

> >> Gale Andrews wrote:
> >>      
> >>> 8 kbps LC>   iTunes: 18 kbps LC
> >>> 16 kbps Main>   iTunes: 19 kbps no profile
> >>> 32 kbps SSR>   null file 0 bytes
> >>> 32 kbps LTP>   iTunes: 22 kbps no profile
> >>>
> >>> Should 32 kbps per channel in Audacity end up as 64 kbps given I had
> >>> a stereo file?
> >>>
> >>> DBPowerAmp sees the correct profile for the three files that exported,
> >>> but has 0 kbps bit rate. Foobar 2000 displays all the exported profiles
> >>> correctly, and displays the same bit rates as iTunes (i.e. not what
> >>> Audacity exported).
> >>>
> >>>        
> >> Actually, it said "per channel", but in reality it was "per whole file",
> >> because FFmpeg is making the bitrate/channels division internally.
> >> Part of the problem is that max supported bitrate is per channel only,
> >> and it depends on samplerate.
> >>
> >> I know how to handle that, but ShuttleGui is resisting my attempts to
> >> change the data.
> >>      
> >
> > I don't know how finnicky iTunes is, but it's more important that we
> > get the profile appearing correctly in iTunes than in other programs,
> > because of the number of people using it.
> >
>    
> Installed iTunes. Impressive. This is the slowest software player i ever
> encountered.

:=) Plays with no gaps between files though, one thing in its favour.

> Research results: iTunes only supports LC-AAC (no HE-AAC, no Main-AAC,
> no LTP-AAC). iTunes correctly displays LC-AAC files bitrate.

Thanks for checking that.

> Looks like i fixed everything, eh?

On the way, certainly. A few things outstanding....

* MP4 (AAC) bit rates don't seem right for higher bit rates yet. At
   44100 Hz sample rate I got a 48 kbps stereo MP4 to show as
   99 kbps in iTunes and Foobar (so near enough?), but stereo
   96, 193 and 258 kbps files all show in Foobar and iTunes as  
   152 kbps

* Can we have the bit rate list for AAC and MP4 (AAC) ordered
   lowest first as per the other formats?

* Were we going to have an M4A filter so that Windows users
   of iTunes don't have to rename AAC to M4A before export,
   and Mac users of iTunes don't have to rename both AAC and
   MP4?

* Real Audio is still a problem. Real Player, JetAudio and MPC don't
   understand Audacity's RA files. On my system, only VLC (which
   does not support Real) will play them. As Richard said, RA (like
   it or not) is one of the key formats.

* GSM: Is the WAV version of these as compliant as can be? WMP11,
   MPC and iTunes won't play them and I think they should? Only
   QuickTime plays them on my machine, but there is a slight problem      
   even there, a 45 seconds file only lasts 9 seconds in QuickTime.

* Both Richard and I would prefer sample rates were taken out of
   of format options for sake of consistency. Do you see any drawbacks
   to this?


Thanks

Gale


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
LRN
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink
Gale Andrews wrote:

> | From LRN<lrn1986@...>
> | Sun, 13 Jul 2008 10:17:01 +0400
> | Subject: [Audacity-devel] Export Options
>    
>>>> Gale Andrews wrote:
>>>>
>>>>          
>>>>> 8 kbps LC>    iTunes: 18 kbps LC
>>>>> 16 kbps Main>    iTunes: 19 kbps no profile
>>>>> 32 kbps SSR>    null file 0 bytes
>>>>> 32 kbps LTP>    iTunes: 22 kbps no profile
>>>>>
>>>>> Should 32 kbps per channel in Audacity end up as 64 kbps given I had
>>>>> a stereo file?
>>>>>
>>>>> DBPowerAmp sees the correct profile for the three files that exported,
>>>>> but has 0 kbps bit rate. Foobar 2000 displays all the exported profiles
>>>>> correctly, and displays the same bit rates as iTunes (i.e. not what
>>>>> Audacity exported).
>>>>>
>>>>>
>>>>>            
>>>> Actually, it said "per channel", but in reality it was "per whole file",
>>>> because FFmpeg is making the bitrate/channels division internally.
>>>> Part of the problem is that max supported bitrate is per channel only,
>>>> and it depends on samplerate.
>>>>
>>>> I know how to handle that, but ShuttleGui is resisting my attempts to
>>>> change the data.
>>>>
>>>>          
>>> I don't know how finnicky iTunes is, but it's more important that we
>>> get the profile appearing correctly in iTunes than in other programs,
>>> because of the number of people using it.
>>>
>>>        
>>
>> Installed iTunes. Impressive. This is the slowest software player i ever
>> encountered.
>>      
>
> :=) Plays with no gaps between files though, one thing in its favour.
>    
So does foobar2000.
> * MP4 (AAC) bit rates don't seem right for higher bit rates yet. At
>     44100 Hz sample rate I got a 48 kbps stereo MP4 to show as
>     99 kbps in iTunes and Foobar (so near enough?), but stereo
>     96, 193 and 258 kbps files all show in Foobar and iTunes as
>     152 kbps
>    
 From faac commandline encoder help:
   -b <bitrate>    Set average bitrate (ABR) to approximately <bitrate>
kbps.
         (max. value 152 kbps/stereo with a 16 kHz cutoff, can be raised
         with a higher -c setting).
   -c <freq>    Set the bandwidth in Hz (default: automatic, i.e. adapts
         maximum value to input sample rate).

Should i add cutoff frequency to dialog? Or just leave things as they are?
> * Can we have the bit rate list for AAC and MP4 (AAC) ordered
>     lowest first as per the other formats?
>    
Yes.
> * Were we going to have an M4A filter so that Windows users
>     of iTunes don't have to rename AAC to M4A before export,
>     and Mac users of iTunes don't have to rename both AAC and
>     MP4?
>    
Elaborate a bit more, which filters for which platform i should make and
what should they do exactly?
While i had iTunes installed, it played mp4 files without problems.
> * Real Audio is still a problem. Real Player, JetAudio and MPC don't
>     understand Audacity's RA files. On my system, only VLC (which
>     does not support Real) will play them. As Richard said, RA (like
>     it or not) is one of the key formats.
>    
Files produced by FFmpeg can't be played either.
> * GSM: Is the WAV version of these as compliant as can be? WMP11,
>     MPC and iTunes won't play them and I think they should? Only
>     QuickTime plays them on my machine, but there is a slight problem
>     even there, a 45 seconds file only lasts 9 seconds in QuickTime.
>
>    
Yes, they should.
On the other hand, in Audacity we have libsndfile which is capable of
encoding GSM-WAV. In theory.
> * Both Richard and I would prefer sample rates were taken out of
>     of format options for sake of consistency. Do you see any drawbacks
>     to this?
>    
Well, now for AAC encoding bitrate range depends on sample rate. Either
i have to make the dialog aware of the AudacityProject contents, or
leave as it is.
For other formats removing sample rate is easier.
What should be Audacity's policy when track's sample rate doesn't
matches any of the sample rates supported by format? Error message?
Upsampling? Downsampling? Up/Downsampling (to closest rate)? Forced
resampling (for formats such as GSM which supports only one sample rate).

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: Export Options
Reply Threaded MoreMore options
Print post
Permalink

| From LRN <lrn1986@...>
| Sun, 13 Jul 2008 23:08:10 +0400
| Subject: [Audacity-devel] Export Options

> Gale Andrews wrote:
>
> > * MP4 (AAC) bit rates don't seem right for higher bit rates yet. At
> >     44100 Hz sample rate I got a 48 kbps stereo MP4 to show as
> >     99 kbps in iTunes and Foobar (so near enough?), but stereo
> >     96, 193 and 258 kbps files all show in Foobar and iTunes as
> >     152 kbps
> >    
>  From faac commandline encoder help:
>    -b <bitrate>    Set average bitrate (ABR) to approximately <bitrate>
> kbps.
>          (max. value 152 kbps/stereo with a 16 kHz cutoff, can be raised
>          with a higher -c setting).
>    -c <freq>    Set the bandwidth in Hz (default: automatic, i.e. adapts
>          maximum value to input sample rate).
>
> Should i add cutoff frequency to dialog? Or just leave things as they are?
 
Well