Paz75
Im about to buy now as my demo is running out and there's no doubt that its a good purchase.
However, one burning desire for a feature is to have the waveform analysis put into a file like wavelab or soundforge does. Im using large digitized vinyl and queuing a track which has been played before is slow to show the waveform.
There should probably a config entry to specify where these files reside as Im not terribly interested to see them next to the file itself. However if thats too complicated, next to the source is better than nothing.
I think it would be a huge performance gain as well because that means you dont have to do read-aheads while using the tool for tracks that already had a waveform generated.
Cheers
However, one burning desire for a feature is to have the waveform analysis put into a file like wavelab or soundforge does. Im using large digitized vinyl and queuing a track which has been played before is slow to show the waveform.
There should probably a config entry to specify where these files reside as Im not terribly interested to see them next to the file itself. However if thats too complicated, next to the source is better than nothing.
I think it would be a huge performance gain as well because that means you dont have to do read-aheads while using the tool for tracks that already had a waveform generated.
Cheers
Posté Fri 05 Jan 07 @ 9:13 am
sbangs
that is a good idea but im not sure if it would be possible to add that info as a tag.
Posté Fri 05 Jan 07 @ 12:42 pm
Paz75
could record of the track's waveform file not be stored in the xml catalog? xpath is such a good way to quickly extract info from a tonne of it. just create a waveform file and then store its path and name as a string.
Posté Fri 05 Jan 07 @ 3:49 pm
sbangs
possibly it is stored in the vdj database
so maybe it could be exportable ,
so maybe it could be exportable ,
Posté Fri 05 Jan 07 @ 3:54 pm