Printable Version of Topic

Click here to view this topic in its original format

Plugivery Forums _ TS - Feature Requests _ Feature Request - Load/bounce As Separate Directories?

Posted by: Loopy C Jun 4 2014, 07:15 PM

Not sure how OSX 'Navigation Services' are coded, but it would be more convenient if the file 'source' directory ('Open' or 'drag/drop' into TS window' location) and 'Bounce' destination directories were remembered separately by TS.

If I open a file now, it then defaults to same directory to 'bounce' to initially. If I then change that destination to another folder (for example my work file bounces for that session) and then proceed to load (drag/drop) another sound from my original sources folder for a new bounce, I have to keep changing the destination directory each time back to my desired and DIFFERENT work folder of bounces.

I am pretty sure I have other app's that track the source and destination folders separately (though can't specify one off the top of my head) so if possible, this would be nice for a future version ;-)

Thanks in advance.

Posted by: eric Jun 6 2014, 10:50 AM

QUOTE (Loopy C @ Jun 4 2014, 08:15 PM) *
Not sure how OSX 'Navigation Services' are coded, but it would be more convenient if the file 'source' directory ('Open' or 'drag/drop' into TS window' location) and 'Bounce' destination directories were remembered separately by TS.

If I open a file now, it then defaults to same directory to 'bounce' to initially. If I then change that destination to another folder (for example my work file bounces for that session) and then proceed to load (drag/drop) another sound from my original sources folder for a new bounce, I have to keep changing the destination directory each time back to my desired and DIFFERENT work folder of bounces.

I am pretty sure I have other app's that track the source and destination folders separately (though can't specify one off the top of my head) so if possible, this would be nice for a future version ;-)

Thanks in advance.


Hello again Loopy C ;-)

Yes that is very pertinent and will make sure the folks at IRCAM look into that... Shouldn't be something to hard to setup in the source code.

Thanks - Eric

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)