You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to incorporate the render_factor from the original code into the gui? That would allow for more flexibility when the default has a poor colorization outcome.
The text was updated successfully, but these errors were encountered:
Is there a way to incorporate the render_factor from the original code into the gui? That would allow for more flexibility when the default has a poor colorization outcome.
It is likely that it will not be possible to implement such a wide range of render_factor as in the original DeOldify. The limit will be on the maximum render_factor and it is caused by the inability to allocate a large continuous block of memory (more than 4 GB) by standard cross-platform means of .NET Framework/Mono. This limitation is likely to manifest itself in the Stable model, since it itself requires a lot of memory to store intermediate data. In the Artistic version, it can also be, but perhaps less strict.
It's great to have a Windows program for this! But the render-factor is important, because the results are often worse than with the original scripts. Is there a way to change something in the code to have a certain render-factor? (I use the factor 40 in the py scripts with good results.)
Is there a way to incorporate the render_factor from the original code into the gui? That would allow for more flexibility when the default has a poor colorization outcome.
The text was updated successfully, but these errors were encountered: