Vienna Symphonic Library Forum
Forum Statistics

184,749 users have contributed to 42,369 threads and 255,368 posts.

In the past 24 hours, we have 3 new thread(s), 11 new post(s) and 73 new user(s).

  • Stretch folder maintenance

    I have opend various new matrices in VI Pro 2 to try them out (including those, that require time stretching) over the last couple of days without actually saving any new matrices of my own. When I checked the "stretch" folder of the VI Pro 2, it turned out that its size was over 4 Gigabytes. What I'd like to know is:

    1. Are those stretched files the result of my opening the matrices that require time stretch? If so, is it safe to delete them? Am I right to assume that the next time I open any of the stretch matrices those files will be automatically created again?

    2. If I create my own stretched material, will VI Pro 2 ask/remind me to save it?

    3. Can these stretched files be manually categorized by being put in separate folders within the Stretch folder?

    4. Probably the most important question: is it possible to have VI Pro perform automatic cleaning of the Stretch folder, deleting those files that aren't used in any of my own custom stretched matrices and patches?

    Forgive me my being impatient and asking this before I finished reading the manual.


  • Hi,

    1. The stretch cache files are - cache files. They can safely be deleted when VIPro is not running. Whenever a stretch is required to be cached again, it will be re-created by the caching subsystem.

    2. No need to save it. Stretching in VIPro2 is done with the graph exclusively. Whenever a new cache needs to be created, the 'Render' button will light up, indicating that a new render of the stretch is required. The graph is then saved along with the matrix or preset.

    3. No. They are strictly cache files.

    4.  Since VIPro v2.0, the directory manager now contains a setting where you can define how much disk space should be used by the caching subsystem. You can read more about this in the manual. Whenever you create new stretch graphs and the cache files run over this limit - there is an intelligent scheme that decides which cache files should be cleared.

    All in all, I have tried to make the caching subsystem work as intelligently as possible. It should really not require any user actions beyond perhaps defining the cache limit.

    Thanks


  • Thank you very much for the promt reply, Mr. Saleteg.

    Indeed, the system you've created is  very elegant, intelligent and extremely well designed. Congratulations on this great piece of software. It's a pleasure to work with.


  • last edited
    last edited

    @MS said:

    It should really not require any user actions beyond perhaps defining the cache limit.

    el-russo,

    I created a folder on a separate drive and gave it a big chunk of space. After using 17GB of space in a very short time, I realized this may be neccessary as I'm using time stretching MUCH more than I ever have before. If you plan to use a good deal of these in some kind of template where you'll frequently use many of them, I'd suggest that.

    -Sean


  • last edited
    last edited

    @Another User said:

    1. The stretch cache files are - cache files. They can safely be deleted when VIPro is not running. ...    Whenever a stretch is required to be cached again, it will be re-created by the caching subsystem.

    Martin, could you plz provide a little more specific info on how the caching subsystem works when the disk limit has been reached?  Specifically, how does it decide which files to delete when new cache files are made?

    I have utilized time stretching a lot with all of my VSL string libraries in VI Pro2 and created a large template.  Some of the timestretch files take a l-o-n-g time to render out, so if ones I created first (but are still 'live' in my template) get deleted when I go over the disk limit set, it would be great to know ahead of that time, so I can put them on a larger disk and increase the limit.

    Thanks for all of the great, great new features!!  

    - Greg


  • When the disk limit has been reached, the cache subsystem will delete:

    1. unused files created within a 5 minutes timeframe, as long as they are not used in the current project.

    2. the oldest cache files, not used in the current project.

    If the current project (process) uses so many time stretched files, that it exceeeds the cache limit - the limit WILL be exceeded to allow for the current project to be loaded/played back.

    I hope this answers your question.


  • Thanks, Martin.  That's exactly the information I was looking for!

    Best,

    Greg



  • Another question about the stretch folder: is it worth keeping before a clean install?

    Given that each cached chunk of data has a denomination like "scch_04_VI-P2_RE_perf-porta_Vib_xxx.bin", will VIP find it on a fresh system, or will the long series of number stand in its way?

    Thanks

  • You can safely delete all stretch files if you wish, they will be regenerated when loading your projects.

    However, if you point directory manager time stretch cache folder to your previous folder, they will be picked up properly again on a fresh install, avoiding the processing time for re-stretching.


  • Thanks Martin, good to know the whole stretching process can be done only once.