2CAudio Kaleidoscope | It's A Trip | Latest Update 1.1

[Sampleconstruct]

Simon might have reached ameoba stage. me, I'm still a bacteria.

Yeah, I'm feeling like a right little ameoba tonight

[krankyone]

Simon, Dorian Flair might be my favorite KS piece you've done so far. Very nice!

[Sampleconstruct]

Simon, Dorian Flair might be my favorite KS piece you've done so far. Very nice!

Thank you, John - I returned back to normal world tunings in this one and for my whole life I've always played around a lot with these modes.

[lnikj]

A feature request - assuming I haven't missed it, and also that it is permissible within the VST / AU specs.

Would it be possible to implement a button to refresh the browser?

When creating image files I have to quit the plugin and reload it for new files to show up.

I have a current workaround which is to create several 'holding' image files and then use the interface arrow keys to move off them then back to them which allows me to update them to my latest image editor saves.

[Daags]

A feature request - assuming I haven't missed it, and also that it is permissible within the VST / AU specs.

Would it be possible to implement a button to refresh the browser?

When creating image files I have to quit the plugin and reload it for new files to show up.

I have a current workaround which is to create several 'holding' image files and then use the interface arrow keys to move off them then back to them which allows me to update them to my latest image editor saves.

good luck with that. seems rudimentary features like this (i suggested adding a simple 'launch image editor' button) are consigned to the 'far out cool things that may happen, someday over the rainbow' folder.

[Sampleconstruct]

I have a current workaround which is to create several 'holding' image files and then use the interface arrow keys to move off them then back to them which allows me to update them to my latest image editor saves.

Could you elaborate, I didn't quite get that and I also struggle with the non-updatability of image files and waveform folders.

[Andrew Souter]

good luck with that. seems rudimentary features like this (i suggested adding a simple 'launch image editor' button) are consigned to the 'far out cool things that may happen, someday over the rainbow' folder.

Come on buddy... play nice.

That is not what I said. I said basically: we have a wish-list of many ideas and features requests. We will consider them all. The first priory however, is resolving technical things, like for example the Retina Display issue and making things as absolutely efficient as possible. Once this is done, then we can consider feature requests.

We are on the same team...

[Andrew Souter]

I have a current workaround which is to create several 'holding' image files and then use the interface arrow keys to move off them then back to them which allows me to update them to my latest image editor saves.

Could you elaborate, I didn't quite get that and I also struggle with the non-updatability of image files and waveform folders.

All browsers should refresh when you use the Import command. Does that not work correctly?

[Sampleconstruct]

I have a current workaround which is to create several 'holding' image files and then use the interface arrow keys to move off them then back to them which allows me to update them to my latest image editor saves.

Could you elaborate, I didn't quite get that and I also struggle with the non-updatability of image files and waveform folders.

All browsers should refresh when you use the Import command. Does that not work correctly?

Yeah, I never use that, I just drop a bunch of the new files into the respective folders while editing a preset, importing them one by one would seem tedious, no?

[Andrew Souter]

Yeah, I never use that, I just drop a bunch of the new files into the respective folders while editing a preset, importing them one by one would seem tedious, no?

Well, you could import a folder using "Import SubFolder"....

If you copy things in the finder/explorer there is really no way for KS to know something has changed. You have to somehow tell it to rescan the content library. We could add some kind of "rescan the content library" button, but this already happens when using the Import commands, so it does not seem to make sense as it is not any less work that way. Arguably it is more work b/c it involves switching to the finder/explorer copying/moving, switching back to KS, and then clicking the hypothetical "rescan" button (or more likely, menu item).

The import commands are meant to handle all this stuff.

Regarding the actively editing an image with a third party graphics editor stuff Daggs mentioned, it is a good a idea. We did not say we don't like it. We do. But, first we must fix bugs, then features...

[Sampleconstruct]

Yeah, I never use that, I just drop a bunch of the new files into the respective folders while editing a preset, importing them one by one would seem tedious, no?

Well, you could import a folder using "Import SubFolder"....

If you copy things in the finder/explorer there is really no way for KS to know something has changed. You have to somehow tell it to rescan the content library. We could add some kind of "rescan the content library" button, but this already happens when using the Import commands, so it does not seem to make sense as it is not any less work that way. Arguably it is more work b/c it involves switching to the finder/explorer copying/moving, switching back to KS, and then clicking the hypothetical "rescan" button (or more likely, menu item).

The import commands are meant to handle all this stuff.

Regarding the actively editing an image with a third party graphics editor stuff Daggs mentioned, it is a good a idea. We did not say we don't like it. We do. But, first we must fix bugs, then features...

Well, if you have multiple tabs opened in the Mac Finder it's a very fast procedure to drop files scattered all over your system into the KS user folders, compiling them all into one or two subfolders first (images/waveforms) and then importing them, seems like more work to me than simply hitting a refresh button. But if that's the way to go, so be it for now.

[Sampleconstruct]

EDIT:Damn it, wrong button

[Sampleconstruct]

Yeah, I never use that, I just drop a bunch of the new files into the respective folders while editing a preset, importing them one by one would seem tedious, no?

Well, you could import a folder using "Import SubFolder"....

If you copy things in the finder/explorer there is really no way for KS to know something has changed. You have to somehow tell it to rescan the content library. We could add some kind of "rescan the content library" button, but this already happens when using the Import commands, so it does not seem to make sense as it is not any less work that way. Arguably it is more work b/c it involves switching to the finder/explorer copying/moving, switching back to KS, and then clicking the hypothetical "rescan" button (or more likely, menu item).

The import commands are meant to handle all this stuff.

Regarding the actively editing an image with a third party graphics editor stuff Daggs mentioned, it is a good a idea. We did not say we don't like it. We do. But, first we must fix bugs, then features...

Well, if you have multiple tabs opened in the Mac Finder it's a very fast procedure to drop files scattered all over your system into the KS user folders, compiling them all into one or two subfolders first (images/waveforms) and then importing them, seems like more work to me than simply hitting a refresh button. But if that's the way to go, so be it for now.

To add to this: I have begun to distribute my images and wavforms over various subfolders in the User library now, as dumping them all into one user-folder just becomes chaotic. Using the import function does just that, dumping them all into one folder or creating a new sub folder with just a handful of new files inside them, so that would be yet another argument for a refresh/rescanning function.

[Andrew Souter]

Well, if you have multiple tabs opened in the Mac Finder it's a very fast procedure to drop files scattered all over your system into the KS user folders, compiling them all into one or two subfolders first (images/waveforms) and then importing them, seems like more work to me than simply hitting a refresh button. But if that's the way to go, so be it for now.

Is this really a re-occuring normal use thing to have files all over the place and then merge them into one folder? Seems like it might happen once or twice while setting up a custom library and then not really that common. right?

But in this case you can make a single folder in the finder, move everything you want into it, make as many subfolders in it as you like, do whatever you want etc etc.

Then, simply use "Import Subfolder" and select the parent of this new directory. Everything will be copied including your directory structure.

The resource library can have any level of nested folders. Import subfolder can import entire directories etc. This is different than the Preset file structure which is limited to one sub-folder level. The only thing you should not really do is mix files and folders at the same directory level. A folder should really only contain more folders, or files. Not both.

[Sampleconstruct]

And while we're on the feature-request trip now, an "export with assets"-function would be cool, either a single preset or a folder with presets, all assets (images/waveforms/tuning files) would be saved into their respective subfolders in the newly created save-folder.