• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Send setlist / Select role / Colour by parameter / Group inside setlist
#11
The concept behind versioning is that you will be able to have multiple versions of a song that you can switch between. For each setlist, you will be able to choose which version of the song is used. On the songs tab, you will be able to choose the default version used (what is used by default for setlists and what is used if the song is loaded by itself). There will not be multiple entries in the songs list - just one single song entry with a toggle for the version. This will get you most of what you want. The problem is that you want to easily be able to share the library with others, and not require them to update their setlists to pick each version of the song they want. I think what you really want is both song versioning, but also a role selection. You want to be able to assign each version of a song to a role, so that a user can just pick their current role, and the correct song version will be loaded for each setlist. Not every user would need the role feature though (that's really more for bands). In that case, I'm going to need to support the concept of role just being set to "None" or "Default", so that most users don't even have to think about it. When choosing what version of a song to use for a setlist, you would be given a choice - either pick a specific version, or pick a role. That way it works in both cases. If this all sounds good to you, I'm going to update my write-up for the versioning feature to include this role concept.  There will be a new dropdown on the song editor screen so that, for each song version, you can pick what role it's associated with. If multiple versions are associated with the same role, the first version in the list will be used when figuring out what version of the song to load in a given setlist.

Thanks,
Mike
Reply
#12
I really like your description, Mike. I like combination of versioning and roles, both seems useful in different cases. Also I agree best would be to set role to "none" by default and if anyone needs different roles (keyboard, guitar, etc), they can add them for specific version of song. 

Just an idea (maybe it was said before) - would it be possible to give each version custom name? Like version 1 would be called "chords only" and version 2 "keyboard solo"?

Tablets: Surface Pro 4, ThinkPad 8; Mobile: Lumia 930
Other: USB foot-pedal or Strich BT-FP2, USB-MIDI connection to Kurzweil Forte 7 and Alesis Vortex Wireless
Reply
#13
Yes, I plan on allowing each version to be named (I'll provide a default name that can be changed).

Thanks,
Mike
Reply
#14
Hello,

thank you for the very prompt response. What you are proposing sounds great! Looking forward to testing it out.
Reply
#15
Mike, in regards of the planned versioning feature (this post is as good as any one you mentioned it):

If you haven't already considered it

Can you provide a column in CSV import to assign a version of the song for the import?

Will it be possible to convert a big database with lots of different versions of a song (all with the same title) somehow automatically to versioning  so there's only
one song as the main version and the rest are sub-versions?
Reply
#16
That's an interesting idea. Each version will require a unique name, so if a name is provided in the CSV for the version, that could be used to figure out whether to update an existing song version or create a new one. 

When it comes to collapsing existing songs into one song with multiple versions, I'm not sure if there will be a way to automatically do that. I could certainly provide an option on the library screen where a new option is available if you select multiple songs ("Combine Songs" or something like that).  I'm sure a utility could be created/added to find songs sharing the same file and prompt if they should be combined... I'll have to think on this some more, but I'm open to suggestions.

Mike
Reply
#17
That'd be good, I think. Maybe some simple name building from title (title without spaces, commas and so on) + version number (There'll be some changes made -> therellbesomechangesmade_001) so one can manually create a unique name without conflicts? Or what do you think?

[quote pid='20256' dateline='1511762591']
When it comes to collapsing existing songs into one song with multiple versions, I'm not sure if there will be a way to automatically do that. I could certainly provide an option on the library screen where a new option is available if you select multiple songs ("Combine Songs" or something like that).  I'm sure a utility could be created/added to find songs sharing the same file and prompt if they should be combined... I'll have to think on this some more, but I'm open to suggestions.
[/quote]
I think a way to collapse (and if needed to expand back) marked songs into versions from the GUI is needed. An automatical conversion of all (though I certainly would need it) is probably not necessary to code into the GUI. I doubt many people have intentionally so many "duplicates" in their database they want to convert to versions as I. If not they should speak up.
Maybe there can be some utility for external SQL-editing or such though. Maybe you could put some functions like that into the companion for "advanced editing" outside of the MSP GUI? Just a thought.
Reply


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2018 MyBB Group.