Notifications
Clear all

Strange Problem with Patch Names.

5 Posts
3 Users
0 Reactions
635 Views
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
Topic starter  

I was adding some new patches to one of my user libraries. Basically, create a patch, save as ... etc.

 

I wanted to go back to a patch I had created called "On The Rhodes". But I did not see it in the list for the library. When I looked at my hard drive, I saw the patch named "On The Rhodes" listed. I then did a rebuild on the library, but no show.

 

The list in Unify had 22 patches. The list on the hard drive had 22 patches.  So what I discovered is on the Hard Drive I had the "On The Rhodes" listed, but not a patch called "Bell Trails". In Unify, I see "Bell Trails", but not "On The Rhodes". My feeling is I must have used "Save" instead of "Save As" and wiped out what was my original "On The Rhodes" with "Bell Trails". I am prepared to accept my stupidity here and accept the loss of the better patch, but I was wondering if I could do anything about having the name on the hard drive match the name in Unify's list. I guess with a save, you can change the name Unify displays, but not the original name on the patch file.

 

I am willing to leave it as it is if trying to change the name of the physical file will screw something up with Unify. I was thinking I could change the name on the hard drive and then do a database rebuild to get all in sync again. Would this be the simple solution?


   
Quote
(@notebynote)
Eminent Member
Joined: 4 years ago
Posts: 24
 

The problem is more or less mentioned before and so far I know @getdunne is aware of this. I had a similar problem weeks ago and think there is a mess up with patch title showed up inside Unify and the file names you give when you "save as..." me myself I have a file in my finder which will not load to Unify and is not shown there although I rescanned everything. Instead I have 2 patches with the same name in Unify - which shouldn´t be possible to prevent chaos.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

Patch names need not be the same as the corresponding file names. Library names need not be the same as the corresponding library folder name. We thought these were good design decisions at the time, but in practice they've turned out to be horribly confusing. We're looking into how we might clean this up. Stay tuned.


   
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
Topic starter  

@getdunne I did see John's explanation of how you could call your patch anything you want even using special characters ... it did seem like a nice idea to me also. Ah well, there is always a gotcha out there.

I would actually be more interested in protection when I am using "Save" accidently instead of what I wanted which was "Save As". I am not usually in favor of too many warning messages, but in this case, I would have liked to see "Are you sure you want to replace this patch?".


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

@larry-ludwick

Yes, the Save/Save As distinction is confusing to many people. I suggest simply using Save As every time. This will present a warning about overwriting existing files.


   
ReplyQuote
Share: