Old 08-15-2015, 05:57 PM   #1
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 8,852
Default Allow .AAC import (DONE)

Recently I tried to import some .AAC files into Reaper, didn't work.

However changing extension to .MP4 (the container for .AAC afaik), importing and playing them in Reaper was no problem.

So why not allow importing .AAC directly (would save the change extension step), or is there a potential problem I don't see ?

Last edited by nofish; 05-19-2017 at 04:03 PM.
nofish is offline   Reply With Quote
Old 08-15-2015, 07:55 PM   #2
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 8,852
Default

Thanks, but I'm not sure I can follow your reply.

I mean they files play fine already now in Reaper just by renaming from .AAC to .MP4 without me having downloaded an additional codec or anything.

Are you saying it's a licensing issue if Reaper would allow import of .AAC files directly but it's not if the user first changes the extension to .MP4 and then imports ?

If so, why ?

From my understanding it's still the same files playing back, just 'put in a container format' or so, by changing the extension.

Last edited by nofish; 08-15-2015 at 08:00 PM.
nofish is offline   Reply With Quote
Old 08-16-2015, 07:51 AM   #3
ELP
Human being with feelings
 
Join Date: Apr 2014
Posts: 943
Default

the reason is that REAPER only identified files by the extension and not by
the raw header.
So if REAPER not intern registered the extension(example AAC) the file dont load and or play.
Although REAPER actually could because
REAPER registered intern mp4 container and your aac and the header for the aac stream of your file appears to be the same as needed to load/play aac streams inside an mp4 container extension.

REAPER really need the capacity to identified files by file header and not only by the file extension.
Which REAPER actual not has.
__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.

Last edited by ELP; 08-16-2015 at 08:19 AM.
ELP is offline   Reply With Quote
Old 08-16-2015, 08:27 AM   #4
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 8,852
Default

Thanks ELP, this seems to make sense to me (I haven't much knowledge about the formats and containers).

A similar thing just came up here recently btw.

http://forum.cockos.com/showthread.php?t=158478

I think it would be nice if Reaper recognizes all playable files automatically without the user having to rename first, either by identifying file header as you say or, which would probably easier to implement, make Reaper also recognize these extensions, I don't care really.

But luckily I've found an utility to batch-change file extensions, so it's not that of a big issue.
nofish is offline   Reply With Quote
Old 08-16-2015, 08:54 AM   #5
ELP
Human being with feelings
 
Join Date: Apr 2014
Posts: 943
Default

yes of course(register) but a safer and more flexible way is the capacity to identified files also by the file header.
(maybe as an switch-option to save resources)

A Header is always a Header... file extensions can lie.

And not all aac that you simply rename in an mp4 extension play after that.

Another bad example is mts m2ts container
If i want to load these inside REAPER, i first have to repack the streams inside these containers in an mkv container.
(Ok i have to admit that i always do that because the Overhead is much lower etc.pp)
But the raw streams inside these containers remains the same as before.
Only after that(no matter which way i load vdeos) i can load this with REAPER. That´s a little bit..st...
So better also the possibility to identified by header.

Alot- hmmm better other Apps can do identified by header.
Only as an little example because i must/have to call that
is the simple but brilliant XMPlay...
Option -Verify file content
-------

Simply rename an mts/m2ts to mkv like in that posting you reference, nofish, is a very very bad idea!!!
Both are two complete different container formats!
Better extract the streams and move the same streams of course without re-encoding in an mkv container.
With the right App, this need only a few seconds.
As i said before the overheat(block size of the mkv container)is much lower.
So on top of that you save additional space- with the same content.
__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.

Last edited by ELP; 08-18-2015 at 01:47 PM.
ELP is offline   Reply With Quote
Old 10-05-2015, 11:34 AM   #6
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,276
Default

Same with *.divx. Rename to *.avi works.
Dstruct is offline   Reply With Quote
Old 10-05-2015, 12:23 PM   #7
cfillion
Human being with feelings
 
cfillion's Avatar
 
Join Date: May 2015
Location: Québec, Canada
Posts: 2,682
Default

...and *.midi -> *.mid. And so on...

+1 for detecting the file type from the actual data instead of simply guessing it from the file name.

http://www.darwinsys.com/file/ (libmagic)
http://mark0.net/soft-trid-e.html
cfillion is offline   Reply With Quote
Old 12-16-2015, 11:03 AM   #8
Airal
Banned
 
Join Date: Nov 2015
Posts: 406
Default

Quote:
Originally Posted by ELP View Post
the reason is that REAPER only identified files by the extension and not by
the raw header.
So if REAPER not intern registered the extension(example AAC) the file dont load and or play.
Although REAPER actually could because
REAPER registered intern mp4 container and your aac and the header for the aac stream of your file appears to be the same as needed to load/play aac streams inside an mp4 container extension.

REAPER really need the capacity to identified files by file header and not only by the file extension.
Which REAPER actual not has.
Header is not necessary. All reaper needs is a way for the user to specify types(expose a user interface for the internal file opening routines).

e.g., all files with extensions a, b, c are opened by program or codec A. extensions r, s, u are opened by program or codec B.

Then it would take a matter of seconds for someone to add a file that reaper hasn't coded for yet can open up because the codec library supports it.

This gets reaper off the tit of hard coding current and future file format extensions.
Airal is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 05:50 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.