Arturia Forums

DRUMS => Spark => Spark Technical Issues => Topic started by: mrfugu on April 22, 2015, 12:19:25 am

Title: Save Project and Library errors, v2.1.1.650
Post by: mrfugu on April 22, 2015, 12:19:25 am
Latest versions here, OSX, Live 9.1.7 and Spark Standalone 2.1.1.650.

I'm unable to save projects via the Save and Save As... buttons, within the app/plugin.

New Projects create a new (blank) Kit that is useless and unable to be deleted.

Project Library in general is easy to navigate, very difficult to edit. User projects and categories and banks and kits and instruments in particular.




Title: Re: Save Project and Library errors, v2.1.1.650
Post by: artao on April 22, 2015, 02:08:56 am
I also recently encountered this problem, under win 7
When I investigated further, I discovered that I FIRST needed to "Create New Project" before the "Save" and "Save As" buttons worked as expected.
I hope this helps. If not, then the problem clearly lies deeper.
Good luck  8)
Title: Re: Save Project and Library errors, v2.1.1.650
Post by: mrfugu on April 22, 2015, 03:23:40 pm
right, but how does one manage existing projects.

for example: rename a project? change project bank or category or author? load and save a new kit to project? delete the blank kit that is created with a new project?

etc.
Title: Re: Save Project and Library errors, v2.1.1.650
Post by: CC4 on April 22, 2015, 07:38:13 pm
The Delete button for projects is in the Library panel in the right-hand column.  So technically to rename a Project you could choose Save As, rename it, change any other details, click Save, and then delete the old project. 

One thing that stinks is you currently cannot directly save an image to a project from the Save As dialog.  (Bug submitted)

I'm having no problem saving an existing project as a new one.  If you have a problem there, then something is probably wrong.
Title: Re: Save Project and Library errors, v2.1.1.650
Post by: mrfugu on April 22, 2015, 11:52:17 pm
If you have a problem there, then something is probably wrong.

turns out I had a permission problem with my external library.

pardon me.