Build 5380: Presets not saved (missing line in)

[meRobs]

in x64 5380, I loaded a number of Presets and lnoted that their output folders were incorrect.
So, I changed to the correct folders and File > Save as Preset, to save te changes.
On re-loading the Presets, the folder were incorrect.

I opened the XML file for the presets and the line for "overall.task.destdir" was missing !!!

[stanley]

The output folder will not be saved in 5380 as I consider this part of UI settings instead of transcoding parameters.

[meRobs]

What does that mean?
That you forgot or that you are not going to fix this?
It just requires you to add one line.

[meRobs]

I just fixed up my Presets using 5342, which I have as a portable version. I simply loaded them one at a time and set the appropriate Output Folder then File > Save as Preset.
I also tried 5360 with success.

However, 5370 is faulty as regards presets (see bug: viewtopic.php?f=28&t=12546), so no good.
I also checked 5372, which failed like 5380.

Other users: I suggest you keep an older version of MediaCoder, such as 5342 or 5360 (not more recent) to change and save Presets. I installed one as a Portable version (see Sectioon 1 in viewtopic.php?f=17&t=12453).

[fredbe9300]

What does that mean?
That you forgot or that you are not going to fix this?

You probably prefer a response from Stanley, but perhaps I can help you interpret what he said

above:
> The output folder will not be saved in 5380 as I consider this part of UI settings instead of transcoding parameters.

http://blog.mediacoderhq.com/changelog/
> Excluding UI related parameters in exported preset file

it seems Stanley now considers the destination path part of those settings NOT INTENDED to be saved in a preset. There's pro's and con's to that, I would think. It makes the preset slightly more portable to other pc's, but less all-encompassing for local work that involves multiple directories. I would probably recommend to keep the destination directory in the preset, but that's just me

[stanley]

Hey fredbe9300 thanks for explaining for me and that's just what I wanted to express.
Because once a user complained to me after loading a preset exported on another computer, the transcoding fails, and finally just because the output folder points to a invalid location.
Yes, I admin there are pros and cons for this. Actually, the output folder setting can still be attached to a exported preset XML by adding one line:

Code: Select all

<node key="overall.task.destdir" value="D:\Output"/>

Maybe I should ask before taking this action. If more people prefer the output folder to be saved in preset, I will consider.

[meRobs]

Thanks for the explanation.

I use MediaCoder for routine testing (see Test Report) and for that I send each output to a directory for that type of conversion.
I also use it to create files with paramaters to suit editing in Adobe Premiere, so, they are sent to a directory ready for Premiere. These are just two applications where "output Folder" is important. There are others.

Looks like I will need to keep build 5360 on my PC to be used whenever I need to change a Preset.
Of course, eventually, such a preset will not work in a new build. Then, I will no longer upgrade.
This may result in my regular Test Reports being too much of a nuisance!

For those who don't want different output folders, they can leave that setting at its default.

[stanley]

I will include output folder in next release.

[meRobs]

Thanks.
I have just confirmed that the latest version of 5380 allows us to load and read the Output Folder to and from a Preset.

The original x64 5380 was sized at 31,268 kB in Explorer
The next iteration was 32,081 kB
and the final: 32,079 kB

[flagpole]

can't you just test that output folder exists when you load it from the preset.

i see both sides of this. it seems the only complete solution is to be able to save the UI too.