Hi. COVID sucks, I have a half hour to kill. Here's a small novel.
----

Yes. Both. Yes. Sure, skip down / skim, or just read it.

Assuming you extracted the hugin source thusly?

D:\code\hugin\hugin-2019.2.0> grep -RHEn "(_blended_fused|_fused)" * 

StitchingExecutor.cpp:697:                const wxString 
fusedExposureLayersFilename(prefix + wxT("_blended_fused.") + 
opts.outputImageType);
StitchingExecutor.cpp:738:                    const wxString 
fusedStacksFilename(prefix + wxT("_fused.") + opts.outputImageType);

Just change the text in the quotes to "_bf" and "_fd" and compile. Doing it 
this way will change it so any reference by any of the multiple programs 
that make up hugin will use your truncated names, and nothing will break or 
require hand-editing to fix. (Note this is not what you should be doing, 
but that is what you asked for.) You'll need to install a LOT of tools, 
first of all even grep is not part of Windows by default. There's no unix 
dev environment by default. You can enable the Windows Subsystem for Linux 
(WSL) if you want to get that going, but you'll still need a full GNU dev 
environment and all the prerequisites installed and properly configured.

Don't take this the wrong way, you were trying to hexedit the precompiled 
binary of an open-source project to change it, so this is might be a long 
road for you for something simple.

I'd suggest 2 alternatives. 1) Just write a batch file to rename the files 
after-the-fact, or 2) customize an executor so you can make your own output 
filenames, that's what most of us do.

Let me outline an example:

Go into Program Files\Hugin\share\hugin\data, pick the one you have the 
problem with _blended_fused, which is fused_layers.executor. Copy that to 
something else, abri_fused_layers.executor then edit it. (use something 
that understands unix line endings like notepad++ / bluefish / brackets / 
even wordpad) Change the Description= and Help= lines, to make it something 
unique, now go down to the Result line and change it to read something like 
Result=%prefix%_bf.tif

That's it. Save and exit. Now load up an already-optimized and 
ready-to-stitch .pto file in hugin gui, click Output / User defined output 
sequences / and the Description you chose. Boom, there it goes. And there 
goes your intermediate files being named what you wanted. You can make as 
many of these as you need, every scenario every file type, there's enough 
examples in that directory for you to customize anything you want, and 
again, no recompiling required. You could make your own assistant if you 
chose to.

I'm not sure if there's a default one that you can change the executor of 
that will change the hugin GUI so that when clicking the Stitch! button 
with fused and blend settings, it'll use your modified version, or if 
you'll need to recompile for that. But this here will get you going.

Have a great day.

On Tuesday, September 15, 2020 at 9:36:25 AM UTC-4 Abrimaal wrote:

> Are the suffixes generated by hugin.exe or one of the co-apps?
> I could try to recomplile from source, just tell me in which file are the 
> suffixes defined.
>
> On Thursday, September 10, 2020 at 12:46:40 AM UTC+2 Abrimaal wrote:
>
>> What files should I modify to shorten the _blended_fused and _fused 
>> suffixes to *_bf *and *_fd* ? 
>> Multiple stitching of panoramas and making collages creates extremely 
>> long filenames. 
>>
>> Then automatic renaming that obviously doesn't rename contents of .pto 
>> files, if a file with _blended_fused suffix is added to a new .pto project 
>> file
>>
>> I already tried, but there are too many blended_fused strings only in the 
>> main .exe file.
>> So I don't know which of them are responsible for filename suffixes, 
>> which of them may be labels, variables or commands.
>>
>>
>>
>>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/744dc743-4252-4140-8507-1dc09e68674fn%40googlegroups.com.

Reply via email to