DPI trouble since version 1.1.2 on a mac

39 views
Skip to first unread message

moreligh...@gmail.com

unread,
Jun 12, 2018, 11:03:27 AM6/12/18
to OpenToonz Users Forum
Since the version 1.1.2 there has been a strange introduction of a misconstrued concept of DPI, and it makes it painful to import image sequences for basic coloring because of the DPI hoopla.

DPI should not be resizing the digital images.

Version 1.1.1 is the last stable release before the DPI mishap began almost 2 years ago. Every day I have to face the pain of having to manually lookup a magic number to type into OT so it won't resize my line art on import.

Please remove the DPI stuff from OT that was added after 1.1.1.

Sincerely,
ML

Jane Eyre

unread,
Jun 12, 2018, 9:12:45 PM6/12/18
to OpenToonz Users Forum
I disagree with you. While there are still areas that could use work (like FX which are fairly unstable), overall OpenToonz has become significantly more stable for MacOS in the past few years. Even since this winter there have been helpful improvements. Keep in mind most of the developers are unpaid - they deserve a little more respect even though you are frustrated. If there is a problem area that you really want to see improved, try using Bountysource to add a bounty.

In terms of the issue you are having with DPI, have you checked your preferences? Under “Loading” there is a checkbox for “Use Camera DPI for All Imported Images”. Try leaving that unchecked.

Shun Iwasawa

unread,
Jun 12, 2018, 11:09:23 PM6/12/18
to OpenToonz Users Forum
You can work on pixels (without any regard to DPI) by activating 
Preferences > Interface > "Pixels Only" checkbox.

Considering DPI is one of the advantages of OT (especially for studios familiar with traditional workflow) as it enables users to put scanned images on "virtual" camera stand in real scale. Actually it had been introduced from Toonz Harlequin (or even from older versions of Toonz) and not from the version 1.1.2.

moreligh...@gmail.com

unread,
Jun 14, 2018, 3:52:03 PM6/14/18
to OpenToonz Users Forum
Shun,

The Preferences > Interface > "Pixels Only" checkbox has no effect on the problem at hand.

The problem is not present in 1.1.1 and before, and is present in 1.1.2 and after.

Sincerely,
Jason

moreligh...@gmail.com

unread,
Jun 14, 2018, 4:09:24 PM6/14/18
to OpenToonz Users Forum
Additionally, the use "image dpi" option in the tlv convert dialog uses an incorrect number, so the magic number has to be typed in manually every time.

Sincerely,
Jason

Jane Eyre

unread,
Jun 14, 2018, 4:13:46 PM6/14/18
to OpenToonz Users Forum
Jason, I’m assuming the import preference didn’t help either? Is there a specific image format you’ve been using? Are you using the cleanup settings at all?

moreligh...@gmail.com

unread,
Jun 14, 2018, 5:46:12 PM6/14/18
to OpenToonz Users Forum
The convert dialog sometimes messes up and causes the "image dpi" option to be selected but the custom text field on the right is being used. I've attached a screenshot.

Sincerely,
Jason


Screen Shot 2018-06-14 at 4.40.51 PM.png

Jane Eyre

unread,
Jun 14, 2018, 6:44:52 PM6/14/18
to OpenToonz Users Forum
If the Image DPI is not always read correctly, that sounds like a bug that should be reported on github. When this happens, if you change to Custom DPI or Current Camera DPI & then back to Image DPI, does that ever fix the problem?

moreligh...@gmail.com

unread,
Jun 14, 2018, 6:55:19 PM6/14/18
to OpenToonz Users Forum
Yes, switching back and forth helps.

There is another bug where it sometimes pulls in an old value for custom dpi as well.

Overall, it's just a headache. The whole convert and then import process was silly enough, but the added buggy dpi setting, along with the additional popups for load/import, and the malformed file name popups that all appear after 1.1.1 are just too much. It's a psychologically crushing experience when all I want to do is drag and drop line art and start coloring.

Jane Eyre

unread,
Jun 14, 2018, 7:16:09 PM6/14/18
to OpenToonz Users Forum
I didn’t even know images could be converted this way! It took me some time to find this in the Browser room. This ought to be added to the level menu with the other convert options & apply inside of OpenToonz too. Something like “Convert raster outlines to TLV” or something. It does seem silly that the image doesn’t import upon conversion. I don’t know why anyone would bother to convert & not load or import.

It looks like in the RC that the Image DPI is only calculated upon changing into Image DPI mode - not upon opening the convert window which I think is the expected & desired behavior.

As far as the load/import dialog goes, it is nice to have the choice - there are benefits to both behaviors. Fortunately choosing to always import or always load prevents the dialog from reoccurring.

Shun Iwasawa

unread,
Jun 15, 2018, 6:40:06 AM6/15/18
to OpenToonz Users Forum
Hi Jason,
 
The convert dialog sometimes messes up and causes the "image dpi" option to be selected but the custom text field on the right is being used. I've attached a screenshot.

Thank you for sharing the image. 
It's obviously a bug since the dpi field should be disabled when the "Image DPI" is selected.
Unfortunately I couldn't reproduce the same situation with my OSX environment yet.
Could you find any conditions or steps to reproduce this problem?

Shun Iwasawa

unread,
Jun 15, 2018, 6:52:49 AM6/15/18
to OpenToonz Users Forum
Hi Jane,

It took me some time to find this in the Browser room. This ought to be added to the level menu with the other convert options & apply inside of OpenToonz too. 

FYI, the convert popup can be opened by clicking "Main Menu Bar > File > Convert File..." command as well.

It looks like in the RC that the Image DPI is only calculated upon changing into Image DPI mode - not upon opening the convert window which I think is the expected & desired behavior. 

I could reproduce the problem and will fix it. Thanks! 

moreligh...@gmail.com

unread,
Jun 16, 2018, 2:30:41 AM6/16/18
to OpenToonz Users Forum
Shun, I'm not yet sure what causes it to happen, but it happens a lot for me.

There are other dimension issues as well, like when you create a new toon raster level in the xsheet, it makes it the wrong size.


Reply all
Reply to author
Forward
0 new messages