Home |
Search |
Today's Posts |
#1
![]() |
|||
|
|||
![]()
When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file
or is it internally converted to a wave and then compressed BACK into an MP3? If it is compressed a second time, that's not good. |
#2
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. |
#3
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. |
#4
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. |
#5
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. |
#6
![]() |
|||
|
|||
![]()
Richard Crowley wrote:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. Thanks, Richard. Yes, I often check Help menus, but so many software developers skimp on their Help files that it is not an automatic habit. Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? |
#7
![]() |
|||
|
|||
![]()
Richard Crowley wrote:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. Thanks, Richard. Yes, I often check Help menus, but so many software developers skimp on their Help files that it is not an automatic habit. Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? |
#8
![]() |
|||
|
|||
![]()
Richard Crowley wrote:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. Thanks, Richard. Yes, I often check Help menus, but so many software developers skimp on their Help files that it is not an automatic habit. Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? |
#9
![]() |
|||
|
|||
![]()
Richard Crowley wrote:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). If it is compressed a second time, that's not good. Which is why CoolEdit posts a warning about saving in MP3. Many of us consider MP3 to be a play-only format. No further editing (at least not high quality editing) is possible. Thanks, Richard. Yes, I often check Help menus, but so many software developers skimp on their Help files that it is not an automatic habit. Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? |
#10
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? I'm not familiar with "Flash audio files" or SWF format. Is this something unique to a particular device? Wouldn't hurt to provide additional context like the make/model of the device. |
#11
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? I'm not familiar with "Flash audio files" or SWF format. Is this something unique to a particular device? Wouldn't hurt to provide additional context like the make/model of the device. |
#12
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? I'm not familiar with "Flash audio files" or SWF format. Is this something unique to a particular device? Wouldn't hurt to provide additional context like the make/model of the device. |
#13
![]() |
|||
|
|||
![]()
"mcp6453" wrote ...
Bonus question, not in the help file. Flash audio files are saved as SWFs. If I open them in CoolEdit, they play fine, and CE says they are really MP3 files. However, if I edit the file and save it, unlike a normal MP3 file, the audio has glitches. Is there an SWF file editor (even though it decompresses and recompresses)? I'm not familiar with "Flash audio files" or SWF format. Is this something unique to a particular device? Wouldn't hurt to provide additional context like the make/model of the device. |
#14
![]() |
|||
|
|||
![]()
"Richard Crowley" writes:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). I could be wrong, but I thought the internal format was floating-point. -- % Randy Yates % "And all that I can do %% Fuquay-Varina, NC % is say I'm sorry, %%% 919-577-9882 % that's the way it goes..." %%%% % Getting To The Point', *Balance of Power*, ELO http://home.earthlink.net/~yatescr |
#15
![]() |
|||
|
|||
![]()
"Richard Crowley" writes:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). I could be wrong, but I thought the internal format was floating-point. -- % Randy Yates % "And all that I can do %% Fuquay-Varina, NC % is say I'm sorry, %%% 919-577-9882 % that's the way it goes..." %%%% % Getting To The Point', *Balance of Power*, ELO http://home.earthlink.net/~yatescr |
#16
![]() |
|||
|
|||
![]()
"Richard Crowley" writes:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). I could be wrong, but I thought the internal format was floating-point. -- % Randy Yates % "And all that I can do %% Fuquay-Varina, NC % is say I'm sorry, %%% 919-577-9882 % that's the way it goes..." %%%% % Getting To The Point', *Balance of Power*, ELO http://home.earthlink.net/~yatescr |
#17
![]() |
|||
|
|||
![]()
"Richard Crowley" writes:
"mcp6453" wrote ... When I edit an MP3 file in Cool Edit 2000, is it edited AS an MP3 file or is it internally converted to a wave and then compressed BACK into an MP3? The answer is as close as the help menu... "As an .mp3 file is opend, it's decompressed into Cool Edit Pro's uncompressed internal format..." This internal format is most likely identical to ".wav", perhaps at 24-bit resolution (speculation). I could be wrong, but I thought the internal format was floating-point. -- % Randy Yates % "And all that I can do %% Fuquay-Varina, NC % is say I'm sorry, %%% 919-577-9882 % that's the way it goes..." %%%% % Getting To The Point', *Balance of Power*, ELO http://home.earthlink.net/~yatescr |
#18
![]() |
|||
|
|||
![]()
Randy Yates wrote:
I could be wrong, but I thought the internal format was floating-point. "François Yves Le Gal" wrote ... Yep, it's 32-bit floating point. According to their help file... "32-bit 16.8 float (type 1 - 32-bit)" "This is Cool Edit Pro's internal format. Floating point values are in the range of +/- 32768.0, but larger and smaller values are valid and not clipped since the floating point exponent is saved as well. The .wav BitsPerSample fileld is set to 32 and BlockAlign is set to 4 bites per channel." Note that +/- 32768 is 16-bit signed integer. Same as standard 16-bit fixed-point wav files. So they appear to accomodate "floating point" input and output protocol while processing only the actual 16-bits of data. |
#19
![]() |
|||
|
|||
![]()
Randy Yates wrote:
I could be wrong, but I thought the internal format was floating-point. "François Yves Le Gal" wrote ... Yep, it's 32-bit floating point. According to their help file... "32-bit 16.8 float (type 1 - 32-bit)" "This is Cool Edit Pro's internal format. Floating point values are in the range of +/- 32768.0, but larger and smaller values are valid and not clipped since the floating point exponent is saved as well. The .wav BitsPerSample fileld is set to 32 and BlockAlign is set to 4 bites per channel." Note that +/- 32768 is 16-bit signed integer. Same as standard 16-bit fixed-point wav files. So they appear to accomodate "floating point" input and output protocol while processing only the actual 16-bits of data. |
#20
![]() |
|||
|
|||
![]()
Randy Yates wrote:
I could be wrong, but I thought the internal format was floating-point. "François Yves Le Gal" wrote ... Yep, it's 32-bit floating point. According to their help file... "32-bit 16.8 float (type 1 - 32-bit)" "This is Cool Edit Pro's internal format. Floating point values are in the range of +/- 32768.0, but larger and smaller values are valid and not clipped since the floating point exponent is saved as well. The .wav BitsPerSample fileld is set to 32 and BlockAlign is set to 4 bites per channel." Note that +/- 32768 is 16-bit signed integer. Same as standard 16-bit fixed-point wav files. So they appear to accomodate "floating point" input and output protocol while processing only the actual 16-bits of data. |
#21
![]() |
|||
|
|||
![]()
Randy Yates wrote:
I could be wrong, but I thought the internal format was floating-point. "François Yves Le Gal" wrote ... Yep, it's 32-bit floating point. According to their help file... "32-bit 16.8 float (type 1 - 32-bit)" "This is Cool Edit Pro's internal format. Floating point values are in the range of +/- 32768.0, but larger and smaller values are valid and not clipped since the floating point exponent is saved as well. The .wav BitsPerSample fileld is set to 32 and BlockAlign is set to 4 bites per channel." Note that +/- 32768 is 16-bit signed integer. Same as standard 16-bit fixed-point wav files. So they appear to accomodate "floating point" input and output protocol while processing only the actual 16-bits of data. |
#22
![]() |
|||
|
|||
![]()
RC [Sat, 15 May 2004 22:40:12 -0700]:
Note that +/- 32768 is 16-bit signed integer. Not quite right. 0x8000 is -32768, but 0x7FFF is 32767, in a 16-bit short integer. It will sound VERY bad if you saturate at -32768 and 32768. Go ahead, try it. Close only counts in hand-grenades, and maybe horseshoes. -- 40th Floor - Software @ http://40th.com/ iPlay : the ultimate audio player for iPAQs mp3, ogg, mp4, m4a, aac, wav, and then some |
#23
![]() |
|||
|
|||
![]()
RC [Sat, 15 May 2004 22:40:12 -0700]:
Note that +/- 32768 is 16-bit signed integer. Not quite right. 0x8000 is -32768, but 0x7FFF is 32767, in a 16-bit short integer. It will sound VERY bad if you saturate at -32768 and 32768. Go ahead, try it. Close only counts in hand-grenades, and maybe horseshoes. -- 40th Floor - Software @ http://40th.com/ iPlay : the ultimate audio player for iPAQs mp3, ogg, mp4, m4a, aac, wav, and then some |
#24
![]() |
|||
|
|||
![]()
RC [Sat, 15 May 2004 22:40:12 -0700]:
Note that +/- 32768 is 16-bit signed integer. Not quite right. 0x8000 is -32768, but 0x7FFF is 32767, in a 16-bit short integer. It will sound VERY bad if you saturate at -32768 and 32768. Go ahead, try it. Close only counts in hand-grenades, and maybe horseshoes. -- 40th Floor - Software @ http://40th.com/ iPlay : the ultimate audio player for iPAQs mp3, ogg, mp4, m4a, aac, wav, and then some |
#25
![]() |
|||
|
|||
![]()
RC [Sat, 15 May 2004 22:40:12 -0700]:
Note that +/- 32768 is 16-bit signed integer. Not quite right. 0x8000 is -32768, but 0x7FFF is 32767, in a 16-bit short integer. It will sound VERY bad if you saturate at -32768 and 32768. Go ahead, try it. Close only counts in hand-grenades, and maybe horseshoes. -- 40th Floor - Software @ http://40th.com/ iPlay : the ultimate audio player for iPAQs mp3, ogg, mp4, m4a, aac, wav, and then some |