Opening interlaced screens with AMOS

Cv365 · 25 January 2017, 18:29

Hi! Try as I might, I just can't seem to make AMOS open a Hires interlaced screen (or a LowRes interlaced screen for that matter)

I open a screen like this:

Code:

Screen Open 1,640,512,16,Hires+Laced

Whenever I print text on this screen or load an IFF into it, the aspect ratio looks right, but it seems only one of the two fields is shown, i.e. no interlacing is taking place. Here's an example. I print the text "THIS SHOULD BE INTERLACED TEXT" right after opening the screen and it looks like this.

This is done with AMOS Professional 2.00. Anybody know if it's possible at all to open interlaced screens with AMOS? Thanks a lot in advance! The manual says it should be possible, but I don't seem to be able to get an interlaced screen open.

Samurai_Crow · 25 January 2017, 18:32

Is this emulated or on real hardware?

Cv365 · 25 January 2017, 18:53

Hi, Samurai_Crow. This screengrab is from emulation, but I've run the code in AMOS on real Amiga's as well and it shows up looking exactly the same. It looks like the screen is non-interlaced and every other line is simply skipped as a result.

Here's the actual code I am using :

Samurai_Crow · 25 January 2017, 19:06

I have posted a link to this thread on the AmosPro bug reports and feature requests forum on UltimateAmiga.co.uk to bring it to the attention of the maintainers.

Cv365 · 25 January 2017, 19:14

Cool, thank you! Hope I'm not doing anything wrong.

After opening the screen I double checked the screen mode with:

Code:

A=Screen Mode
Print A

And I see 32772 printed, which is $8004 and is exactly the value Hires ($8000) + Laced (4) should be.

Samurai_Crow · 25 January 2017, 19:20

I don't think it is your fault. Maybe the second Copper list is getting corrupted.

Lonewolf10 · 27 January 2017, 00:36

Can I just jump in here and ask if the IFF image being loaded in is an interlaced image?

Cv365 · 27 January 2017, 09:21

Yes, the IFF image is an interlaced image. I created it with PPaint. It also opens correctly in an interlaced screen with some picture viewers that I tried (outside of AMOS).

Lonewolf10 · 27 January 2017, 22:45

Hmmm, ok.

Well then, I agree with Samurai Crow, it is a bug you have stumbled onto

Cylon · 29 January 2017, 21:27

Can you be sure this isn't a setup-issue inside the AMOSPro editor to avoid flickering while the editor itself is set to non-flicker?

Samurai_Crow · 29 January 2017, 22:02

I know of no such antiflicker setting.

Lonewolf10 · 29 January 2017, 23:18

Quote:

Originally Posted by Cv365

Cool, thank you! Hope I'm not doing anything wrong.

Can you please upload your "test.IFF" file and current AMOS configuration to The Zone please? (it is called "AMOSPro_Interpreter_Config" and is found in the "S" drawer where AMOSPro is located)

I ask because I just tried to recreate the bug using the code you posted above and was unable to do so. I used a hires+laced image created in Personal Paint as the test image. I tried with and without loading the image and no bug occurred.

Cv365 · 30 January 2017, 09:24

I'll try and upload it tonight when I get home. It's actually reassuring that you weren't able to reproduce it. I couldn't imagine I was the first person ever to stumble upon this.

Cv365 · 30 January 2017, 19:31

Erm, I'm feeling a bit foolish now....

After your hint about the config file I went to the editor config setup and set the "Editor Screen in Interlaced" setting to Yes and voila! I can open interlaced screens now, like it ain't no thang!

Sorry for wasting everyone's time, but you nudged me in the right direction as I would probably never have found the solution on my own. So thanks everyone for your time and your help!!!! And who knows, this thread might help someone else in the future.

Lonewolf10 · 30 January 2017, 20:03

Don't worry, it's one of those cludges that is probably related to AMOS flipping between Editor and Direct mode (and for the reason Cylon stated earlier). Also, if a game screen is large enough you can see the edges of it poking out from behind the Editor window!

Anyway, problem is now fixed

06 March 2017, 12:47

Not sure if I should start a new thread here on this one but i'm also getting this issue in Amos Pro on WB3.1 and setting Editor Screen to Interlaced does nothing to fix this problem. Interestingly running Amos Pro under WB1.3 the issue goes away and the screen is displayed perfectly.

idrougge · 06 March 2017, 13:30

Makes sense, since Cv365's "success" screen looks like it also uses the old 1.3 Topaz font.

However, I've been able to use hires+laced in AMOS Pro under 3.1 in a genlocking application. Note that genlock applications tend to use interlacing regardless of what you tell the Amiga – I seem to remember that the screen turned pixelated whenever the video source was turned off.

Does the same error occur in the old AMOS Pro 1.x version?

Lonewolf10 · 06 March 2017, 21:59

Quote:

Originally Posted by AronGooch

Not sure if I should start a new thread here on this one but i'm also getting this issue in Amos Pro on WB3.1 and setting Editor Screen to Interlaced does nothing to fix this problem. Interestingly running Amos Pro under WB1.3 the issue goes away and the screen is displayed perfectly.

I assume after changing the option, you did exit and re-open AMOS Pro?

Have you tried using Close Workbench instruction just to see if Workbench was somehow interfering with AMOS?

FWIW, I tested under WB 2.04 and I don't have WB 3+

14 March 2017, 07:37

Changing the option Editor to interlaced makes the editor showup in the top half of the screen only with the bottom half of the screen showing part of the output screen, interlace not working ie the editor has every second line missing and squished to the top half of the screen if that makes sense. Saving this config as default, exiting and restarting Amos produces the exact same result.

Running the program with this option in either mode still produces an Amos output screen as shown at the top of this thread. Workbench 1.3 however shows a working interlaced screen with both frames working correctly.

Close workbench instruction doesn't seem to have any effect what so ever either running this from direct mode or before or after the screen open command.

Might give this a go in Amos 1.3 and check results this way.

14 March 2017, 07:52

I just ran the same test with Amos 1.3 but this time in WinUAE as apposed to my real machine test I did earlier with Amos Pro.

The results are exactly the same as Amos Pro on my real A600 machine.

In WB3.1 the interlaced screen issue is present and running Amos 1.3 in WB1.3 the issue goes away and a proper interlaced screen is displayed.

25 January 2017, 18:29	#1
Cv365 Registered User Join Date: Sep 2015 Location: Amigaville Posts: 21	Opening interlaced screens with AMOS Hi! Try as I might, I just can't seem to make AMOS open a Hires interlaced screen (or a LowRes interlaced screen for that matter) I open a screen like this: Code: Screen Open 1,640,512,16,Hires+Laced Whenever I print text on this screen or load an IFF into it, the aspect ratio looks right, but it seems only one of the two fields is shown, i.e. no interlacing is taking place. Here's an example. I print the text "THIS SHOULD BE INTERLACED TEXT" right after opening the screen and it looks like this. This is done with AMOS Professional 2.00. Anybody know if it's possible at all to open interlaced screens with AMOS? Thanks a lot in advance! The manual says it should be possible, but I don't seem to be able to get an interlaced screen open.

25 January 2017, 19:14	#5
Cv365 Registered User Join Date: Sep 2015 Location: Amigaville Posts: 21	Cool, thank you! Hope I'm not doing anything wrong. After opening the screen I double checked the screen mode with: Code: A=Screen Mode Print A And I see 32772 printed, which is $8004 and is exactly the value Hires ($8000) + Laced (4) should be.

27 January 2017, 09:21	#8
Cv365 Registered User Join Date: Sep 2015 Location: Amigaville Posts: 21	Yes, the IFF image is an interlaced image. I created it with PPaint. It also opens correctly in an interlaced screen with some picture viewers that I tried (outside of AMOS). Last edited by Cv365; 27 January 2017 at 09:22. Reason: for clarity

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Interlaced vs Non-Interlaced display	whitebird	support.Hardware	9	12 January 2015 10:20
Scanline flicker when moving between interlaced and non-interlaced WB screens	mr_a500	support.FS-UAE	0	19 December 2014 17:10
Automatically disable Direct3D scanlines/mask during interlaced screens (WinUAE)	Maren	request.UAE Wishlist	6	26 September 2010 09:14
Flickering when interlaced and non-interlaced highres screens "meet"	Maren	support.WinUAE	12	27 November 2009 22:59
Where's the amos.library on the 3-disk AMOS set?	andreas	support.Apps	0	15 November 2001 16:04

25 January 2017, 18:32	#2
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,186	Is this emulated or on real hardware?

25 January 2017, 18:53	#3
Cv365 Registered User Join Date: Sep 2015 Location: Amigaville Posts: 21	Hi, Samurai_Crow. This screengrab is from emulation, but I've run the code in AMOS on real Amiga's as well and it shows up looking exactly the same. It looks like the screen is non-interlaced and every other line is simply skipped as a result. Here's the actual code I am using :

25 January 2017, 19:06	#4
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,186	I have posted a link to this thread on the AmosPro bug reports and feature requests forum on UltimateAmiga.co.uk to bring it to the attention of the maintainers.

25 January 2017, 19:20	#6
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,186	I don't think it is your fault. Maybe the second Copper list is getting corrupted.

27 January 2017, 00:36	#7
Lonewolf10 AMOS Extensions Developer Join Date: Jun 2007 Location: near Cambridge, UK Age: 44 Posts: 1,924	Can I just jump in here and ask if the IFF image being loaded in is an interlaced image?

27 January 2017, 22:45	#9
Lonewolf10 AMOS Extensions Developer Join Date: Jun 2007 Location: near Cambridge, UK Age: 44 Posts: 1,924	Hmmm, ok. Well then, I agree with Samurai Crow, it is a bug you have stumbled onto

29 January 2017, 21:27	#10
Cylon Registered User Join Date: Oct 2014 Location: Europe Posts: 470	Can you be sure this isn't a setup-issue inside the AMOSPro editor to avoid flickering while the editor itself is set to non-flicker?

29 January 2017, 22:02	#11
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,186	I know of no such antiflicker setting.

30 January 2017, 09:24	#13
Cv365 Registered User Join Date: Sep 2015 Location: Amigaville Posts: 21	I'll try and upload it tonight when I get home. It's actually reassuring that you weren't able to reproduce it. I couldn't imagine I was the first person ever to stumble upon this.

30 January 2017, 19:31	#14
Cv365 Registered User Join Date: Sep 2015 Location: Amigaville Posts: 21	Erm, I'm feeling a bit foolish now.... After your hint about the config file I went to the editor config setup and set the "Editor Screen in Interlaced" setting to Yes and voila! I can open interlaced screens now, like it ain't no thang! Sorry for wasting everyone's time, but you nudged me in the right direction as I would probably never have found the solution on my own. So thanks everyone for your time and your help!!!! And who knows, this thread might help someone else in the future.

30 January 2017, 20:03	#15
Lonewolf10 AMOS Extensions Developer Join Date: Jun 2007 Location: near Cambridge, UK Age: 44 Posts: 1,924	Don't worry, it's one of those cludges that is probably related to AMOS flipping between Editor and Direct mode (and for the reason Cylon stated earlier). Also, if a game screen is large enough you can see the edges of it poking out from behind the Editor window! Anyway, problem is now fixed

06 March 2017, 12:47	#16
AronGooch Posts: n/a	Not sure if I should start a new thread here on this one but i'm also getting this issue in Amos Pro on WB3.1 and setting Editor Screen to Interlaced does nothing to fix this problem. Interestingly running Amos Pro under WB1.3 the issue goes away and the screen is displayed perfectly.

06 March 2017, 13:30	#17
idrougge Registered User Join Date: Sep 2007 Location: Stockholm Posts: 4,332	Makes sense, since Cv365's "success" screen looks like it also uses the old 1.3 Topaz font. However, I've been able to use hires+laced in AMOS Pro under 3.1 in a genlocking application. Note that genlock applications tend to use interlacing regardless of what you tell the Amiga – I seem to remember that the screen turned pixelated whenever the video source was turned off. Does the same error occur in the old AMOS Pro 1.x version?

14 March 2017, 07:37	#19
AronGooch Posts: n/a	Changing the option Editor to interlaced makes the editor showup in the top half of the screen only with the bottom half of the screen showing part of the output screen, interlace not working ie the editor has every second line missing and squished to the top half of the screen if that makes sense. Saving this config as default, exiting and restarting Amos produces the exact same result. Running the program with this option in either mode still produces an Amos output screen as shown at the top of this thread. Workbench 1.3 however shows a working interlaced screen with both frames working correctly. Close workbench instruction doesn't seem to have any effect what so ever either running this from direct mode or before or after the screen open command. Might give this a go in Amos 1.3 and check results this way.

14 March 2017, 07:52	#20
AronGooch Posts: n/a	I just ran the same test with Amos 1.3 but this time in WinUAE as apposed to my real machine test I did earlier with Amos Pro. The results are exactly the same as Amos Pro on my real A600 machine. In WB3.1 the interlaced screen issue is present and running Amos 1.3 in WB1.3 the issue goes away and a proper interlaced screen is displayed.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)