<Sound object>.duration always returns 0

[Ayuto]

Reference:
http://forums.sourcepython.com/showthread.php?940-Plugins-converts-from-Eventscripts-to-Source-Python&p=6441&viewfull=1#post6441

A possible solution is to add a sound library like mutagen. This would allow us to add more attributes to the Sound class.

Question:
What do we do with sound files packed in VPK files? Actually, this is not just about sound files, but any file within a VPK file. What if we want to call a function that requires a file path? Should we create a temporary file?

[KirillMysnik]

Real-time VPK unpacking?

How about manually hash all stock game VPKs and just create corresponding tables to them which contain information like
<sound path> - duration
?

And if the server uses a custom VPK - well, then unpack VPK either in real time on request (slow?) or unpack and create such tables on server startup.

This only answers the sound issue. If a function requires a file path, then let it be with file system as we see this file system. If the function wants more, we can provide it with VPK unpacking API. E.g. just include that VPK module so that everybody can use it if they want to.

Since we can't get any native support for accessing files within VPK smoothly, since we don't want to unpack them in real time AND if there's a plugin that for some reason heavily relies on files packed in VPK - implement a sp extract-vpk console command that just unpacks all VPK content and deletes these *.vpk-s. Let the owner take an action if they install such plugins. I guess in given conditions it'd be the best option to work with packed content - again, if there's a plugin that for some reason depends on stock game files.

[Ayuto]

Actually, reading a file from a VPK file seems to be fast and it's probably much faster if we create the file-like object with the functionality provided by the SDK (because it's implemented in C++). If someone needs a name on the file system, we could provide a named temporary file (there is a Python library for that).

I don't want a hash table, because that only fixes the duration issue and not accessing packed files.

[dsezen]

No need for special libraries. IEngineTool contains exactly what you need ;). I opened a PR for it above.

[satoon101]

This should all be fixed as of this commit:
bc4b1de

[Ayuto]

The reason for reopening this issue is that the interface is not available on Linux.

[Sh4d0w0561]

If this interface for Linux ever be available? This topic is now long open without a solution, unfortunately.

[satoon101]

@Killer0561 - That interface will never be available for Linux (or at least very highly unlikely). We are working on a solution. The most recent commit should allow access to the duration for all wav, mp3, and ogg files that are directly on the server. We still have to figure out how we want to get the duration for sounds in vpk files.

[satoon101]

The newest solution seems to work fine, but I would like more people to do more testing on it to verify. It now allows for getting the sound duration from sounds within vpk files. My test script on CS:S was:

from engines.sound import Sound
from stringtables import string_tables

sounds = [
    'hostage/hpain/hpain1.wav',
    'player/headshot1.wav',
    'source-python/gungame/default/gg_handicap.mp3',
    'source-python/gungame/default/smb_star.mp3',
]

from time import time
start = time()
for path in sounds:
    sound = Sound(path)
    sound.precache()
    print(path, sound.duration, string_tables.soundprecache[sound.sample])
minutes, seconds = divmod(time() - start, 60)
print(
    'Total time: {minutes} minute(s), {seconds:.2f} seconds'.format(
        minutes=int(minutes),
        seconds=seconds,
    )
)