Waveform seeker issues with mapped network drive

[thisisbbc]

Howdy,

While looking at some of the threads here I came across one mentioning the waveform seeker. I've never really used it before but it's a neat little feature so I played a bit with it and found some issues.

When I'm reading a FLAC or MP3 from my NAS, the waveform won't load and looks like this:


However if I copy the file locally, looks good!


Seems like Wacup doesn't play too well with libraries on a NAS.

This also prompted me to do some testing regarding the other issue I mentioned about ATF/metadata, so I'm going to update the other thread with this information as well.

[Glamrlama]

Waveform seeker is one of the many features/functions of WACUP that keeps me using it forever. 

I find it sometimes will struggle with some files in determining the waveform or scrolling through the waveform. You can solve some issues by clearing it's cache if you right click in the waveform when a song is playing. If you have .wma files it will not read those waveforms. 

[dro]

If you have .wma files it will not read those waveforms.

It can only render the waveform for formats that have an appropriate local decoder installed which supports the file conversion api. WMA doesn't fall under that as support for those files is via the re-used in_dshow plug-in from 5.666 which doesn't provide what's needed.

Other files not working could either be the same issue or that there's an issue obtaining either access to the file (sharing conflict) or that the metadata which is looked at isn't available which causes the checks to fail making it then show the generic waveform.

As for the NAS issue, I've still to look at the other threads but am wondering if it's all due to an optimisation change made to reduce the overhead of checking for files existing before doing additional processing against them & that might not be working well for NAS based paths (something I've still to get a test setup re-created for checking such things).

-dro