Can't create test document for Braillo 650SF

[ThiloLutz]

Testing Daisy Pipeline 2 for volume braille creating here at blista in Marburg/Germany.
Testing Dotify Studio 1.0 to print PEF files.
Our Braillo 400S works fine with Dotify Studio 1.0.
The 650SF is another matter. When I set the printer settings, the button "Create test document" disappears and the program claims invalid printer settings on my Windows 10 mashinee for some reason. Absurdly, this is only the case when I'm logged into Windows as a Domain user. When I log in using a local account, the settings are accepted.
Any idea what the problem might be? I usually blame Oracle and/or Microsoft and have a sinking feeling the Windows Firewall might be involved, but I'm rather hoping I'm looking in the wrong place here.

[joeha480]

@ThiloLutz Are you using a custom (user defined) paper? The custom papers are stored in the user's home folder. The settings are stored in the Windows registry. There could possibly be a mismatch there.

[ThiloLutz]

Hi Joel, I was using custom paper sizes. I deleted the file in my home folder, but still can‘t create a test document. I need custom paper sizes, we uses. We print on roll paper using our Braillo 650SF and on tractor paper (280mm wide x 12 inch long) using our Braillo 400S. The Impacto 600 is a backup machine which we are scrambling to get to work using the tractor paper since the 400S broke downl yesterday. It works with our tractor paper, but only using RTFC to print, and that program goofs when trying to print 28 symbols per line in duplex mode (we cut of the rest of the paper to get 210 mm wide A4 pages). So I was hoping to solve the problem using Dotify Studio. Alas, I can’t use the Braillo 650SF with Dotify Studio 1.0.0 because I can’t create test documens and I can’t use the Impacto 600 because, if I create a custom paper (tractor paper, 280mm wide, 12 inch long or 11 inch wide and 12 inch long), I can’t select that paper in the Emboss tab with the Impacto 600 selected. Regards Thilo Lutz IT Specialist [blista Logo] Deutsche Blindenstudienanstalt e.V. (blista) Am Schlag 2-12, 35037 Marburg Tel.: +49 6421 606-0, Direktwahl: -459 E-Mail: t.lutz@blista.de<mailto:t.lutz@blista.de> Internet: www.blista.de<http://www.blista.de/> Pflichtangaben: www.blista.de/impressum Von: Joel Håkansson <notifications@github.com> Gesendet: Dienstag, 8. Oktober 2019 10:23 An: brailleapps/dotify-studio <dotify-studio@noreply.github.com> Cc: Thilo Lutz <t.lutz@blista.de>; Mention <mention@noreply.github.com> Betreff: Re: [brailleapps/dotify-studio] Can't create test document for Braillo 650SF (#85) @ThiloLutz<https://github.com/ThiloLutz> Are you using a custom (user defined) paper? The custom papers are stored in the user's home folder. The settings are stored in the Windows registry. There could possibly be a mismatch there. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#85?email_source=notifications&email_token=ALZEO3R3QRVZBVCCCJZQ3A3QNQ7PHA5CNFSM4ICFO6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEATLCIY#issuecomment-539406627>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALZEO3WVD7TBUHECJRXDNCTQNQ7PHANCNFSM4ICFO6HA>.

…

______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com

______________________________________________________________________

[joeha480]

@ThiloLutz If the paper doesn't show up in the Emboss tab, then it's because the embosser implementation says it doesn't support it. I haven't implemented the Impacto embosser myself, but sometimes the official supported paper sizes are more restrictive than necessary.

I don't know if I can help you with the Braillo 650SF issue, but I know that that embosser has been tested by several people. If you send me the paper definition, maybe I could try to reproduce. Is this the case with all custom papers and only custom papers?

[ThiloLutz]

Hi Joel, sorry for the late reply, the printing of PEFs has been put on the bakcburner here since we can also create BRF files with the DAISY Pipeline2 and print those with DBT. Getting the Pipeline2 to work fully has been prioritized. And the Braillo 400S has been repaired. Still, I can’t print or create test pages for the Braillo 650SF. I’m not even using custom paper sizes. I just try to select 28 cm wide paper and let it cut the paper after 30 cm, and I don’t get the option to create a test page. Same issue with other paper widths and lenghts. You mentioned that there could be a conflict between paper sizes in the Dotify config file and the registry. Where in the registry are the paper sizes stored? Maibe if I edited them there, it would help. Merry Christmas and a Happy New Year to you and yours Thilo Lutz IT Specialist [blista Logo] Deutsche Blindenstudienanstalt e.V. (blista) Zentrum für Barrierefreiheit (ZfB) Am Schlag 2-12, 35037 Marburg Tel.: +49 6421 606-0, Direktwahl: -459 E-Mail: t.lutz@blista.de<mailto:t.lutz@blista.de> Internet: www.blista.de<http://www.blista.de/> Pflichtangaben: www.blista.de/impressum Von: Joel Håkansson <notifications@github.com> Gesendet: Donnerstag, 21. November 2019 19:54 An: brailleapps/dotify-studio <dotify-studio@noreply.github.com> Cc: Thilo Lutz <t.lutz@blista.de>; Mention <mention@noreply.github.com> Betreff: Re: [brailleapps/dotify-studio] Can't create test document for Braillo 650SF (#85) @ThiloLutz<https://github.com/ThiloLutz> If the paper doesn't show up in the Emboss tab, then it's because the embosser implementation says it doesn't support it. I haven't implemented the Impacto embosser myself, but sometimes the official supported paper sizes are more restrictive than necessary. I don't know if I can help you with the Braillo 650SF issue, but I know that that embosser has been tested by several people. If you send me the paper definition, maybe I could try to reproduce. Is this the case with all custom papers and only custom papers? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#85?email_source=notifications&email_token=ALZEO3TOY3XPGY5YBM3UA2DQU3KLDA5CNFSM4ICFO6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE3IWXY#issuecomment-557222751>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALZEO3TKWXTIY663EJTJ46LQU3KLDANCNFSM4ICFO6HA>.

…

______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com

______________________________________________________________________