As promised:michelkeijzers wrote:Actually, this is not so simple.levioter wrote:No one could help about my question ?levioter wrote:First of all I would like to thank you Korg for this update ! Nice job !![]()
In a second step I have a question for you folks:
In OS 3.0 is anybody started to modify his own 2.x combis using 2.x factory programs ?
Is there a script or something to do that automatically already announced ?
I guess I saw Dan talking about that in a previous thread ?
I don't have a lot of them but it could be painful to do this manually and this will imply a very strong file organisation !
Am I missing something ?
Thanks.
Cheers
May be not asked the right way ?
Let me rephrase it:
When you have Combis that are using 2.x programs that now (OS 3.x) have been changed from a bank to another how do you deal with that ? PCGTools ? Any other suggestion ?
Thanks.
Cheers
Until so version 2.3, PCG Tools uses the following strategy when copy/pasting programs/combis/set list slots:
- If a program is found in the pasted PCG file that is BYTE WISE identically, it will not be pasted (depending on the copy/paste settings).
However, I can imagine that people want to use the same/improved programs from the V3 (new) PCG file to be used with their combis.
Therefor, I have made two new options in the copy/paste settings:
- Treat Equally Named Patches As Duplicate: when a program is found that has an equal name, than the program will not be copied, and combis/set list slots will refer to that program. If there are more identically named patches: it prefers the one on the same location, otherwise the first occurence.
- However, this is not enough. Some improved programs have been called V2 as postfix. Therefor I made another setting: Treat Like-Named Patches as Duplicates and the Ignore Characters/Parts. If you fill in V2 (you can use multiple fragments, like V2, V3 etc), than those parts will be stripped of at the end of the name. So e.g. ChurchBell and ChurchBell V2 will be treated as duplicates. This can be handy to automatically refer to improved patches to the new PCG file.
I will write a better story about this soon, but so far this is what I have.
In case you are intending to copy/paste programs/combis/set lists from your own PCG file to the new factory default file or vice versa, please read some extra info about the new cut/copy/paste settings (via the download tab of my website, just under the Manual header): http://pcgtools.mkspace.nl/download.php