Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
FamiTracker
An idea for FTM files containing more than one song in the module: The ability to specify that certain pattern IDs are to be shared/duplicated between all songs in the module (instead of being specific to their song). Like how instrument definitions are shared between all songs in the module -- but for pattern data.
One or two FTMs I'm working on contain different mixes of the same song in the file, so while some pattern IDs are specific to one song in the module, other pattern IDs are the same between songs, and it is an editing nightmare trying to keep the latter group in sync as I continue working on it and tweaking parts.
I imagine this could be an option included in the Module Properties dialog -- e.g: a "Global patterns" frame listing which patterns IDs are common to the module (instead of specific to each song); when you add a pattern ID to the list, Famitracker checks all songs to see if there's more than one song using that pattern ID, and warns/prompts you to pick which pattern data to use (the other ones are inevitably overwritten, and there is no Undo for this).
It may also need a means (such as a second display color in the Frame Editor, perhaps blue?) to distinguish that a given pattern ID is shared between all songs.
_______________________
Where to find me:
YouTube: [url=http://youtube.com/user/stratelier]http://youtube.com/user/stratelier
DeviantArt: [url=http://stratadrake.deviantart.com/]http://stratadrake.deviantart.com/
Assuming I'm understanding your request correctly, one potential workaround would be to save the FTM to a different file, and import that file back into the main FTM using the Module Properties dialog. Then just delete everything in the pattern matrix. It's not optimal (since any changes made after the import would not transfer back to the pre-existing song), but it's a viable temporary solution I guess.
_______________________
Follow me on [url=https://twitter.com/jrlepage2a03]Twitter.
I record (some) NSFs on hardware. Feel free to [url=http://www.famitracker.com/forum/posts.php?id=3633]request a hardware render.
That's what I've been doing as a shortcut for a 'duplicate song' command, but that isn't really the issue -- the issue is the editing nightmare that [i]follows[/i] once I start to differentiate the versions from each other.
Say I'm switching between songs every 20 minutes while I work on their various parts, the problem is me losing track of which edits exactly I've made to each one, which results in 'wtf' moments where I'm playing one of the songs and think "wait, didn't I fix that already?" when I hear something like a missing part (wrong note/timing, etc.) because I only fixed it in one song and it's an issue that I need to fix in all.
_______________________
Where to find me:
YouTube: [url=http://youtube.com/user/stratelier]http://youtube.com/user/stratelier
DeviantArt: [url=http://stratadrake.deviantart.com/]http://stratadrake.deviantart.com/
Maybe edit them both together in a single track. Once you're done, duplicate them and delete the other half of each? (Text export can reduce the task of duplicating track to a copy-paste operation.)
