@sundown

I only know what the term "used to" mean. It was an interval of time between when the
electron gun was turned off after reaching the bottom of the screen and before it was
turned on again at the top of the screen.
During this time you could perform graphic changes without the human eye's ability to
see the changes being made. Read:flicker
On our old standard NTSC that time period occured approximately 30 times per second
-60 interlaced fields.
Code had to finish running before the electron beam was turned on again at the top of
the screen or the human eye would detect the changes being made.
8bit computers made fine use of interrupts like these, which were sometimes referred to
as "raster" interrupts.
There was also on both 8bit and classic Amiga a "scanline" interrupt, where graphic changes
could be made on each individual line of the display. This is well illustrated in the Newtek
programs (Digiview) where the entire set of color registers was changed on each scanline to
achieve more color. In the case of scanline interrupts, there is -very- little time between
the electron beam leaving the right side of the screen and appearing again on the left side
of the screen. If you used the Newtek program, you may have even noticed "jitter" when
moving the mouse in this extended graphics mode.
Things may have changed a lot, but they could also be quite similar. Dunno. I don't program anymore.

Best Wishes,
#6

Last edited by number6 on 25-Jul-2005 at 03:12 PM.
Last edited by number6 on 25-Jul-2005 at 03:10 PM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@sundown

Quote:

@antony We would feel better if we knew why it worked & if its the right thing to do without risking other problems with other programs. It's one of those subtle little changes that can come back & haunt you later after you forgot you changed it.

Of course, I wasn't recommending anything, just asking what's the current state of INTERRUPT tooltype.

Setting INTERRUPT=No would change the way VBlank interrupts are generated (I don't remember the details, though). I'll post more when I get the chance to test this on my machine after installing the sound card.

@antony

Quote:

@Samwel I have kept quiet on this topic since I don't have a sound card installed in my A1. I think I have a SBLive 5.1 stashed somewhere, I'll try to dig it up and see what happens, but it will take at least a few days.

I was able to reproduce this on my machine (A1-XE G3 750FX 800 MHz, Radeon 9000 Pro, SoundBlaster Live 5.1).

However, when I used my work-in-progress version of AmiPDF which uses a slightly different approach for displaying the page, it doesn't happen. It shouldn't matter, though. The issue needs a bit more investigation at my end...

@antony &
@thread

Hi,

Repeating the link for those who might not have read the posts from Guru Meditation and DaveAE:

http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=14095&forum=14

Also, there are distinctly different issues being discussed in this thread.
Please do not confuse them. Audio/network is IMO not at all related to the
latest issues being discussed in this thread.
At last count we are discussing (3) different issues here (minimum).

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@antony

Cool, glad you're on top of it. I'll leave INTERRUPT set to Yes & wait for the update. Are you also working on AmiGS? This program has the same problem.

_________________
Hate tends to make you look stupid...

@sundown

Doing the same here just to take one thing out of the loop, so to speak.

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@sundown

Quote:

@antony Cool, glad you're on top of it. I'll leave INTERRUPT set to Yes & wait for the update. Are you also working on AmiGS? This program has the same problem.

Yep, these two share the same code base so they generally have the same features/problems.

@thread

I've been out of the loop for awhile, so I've missed alot of the audio/sound discussions about the µA1-C.

I was wondering if this problem has been fixed yet.

I am still using the original audio drivers that came with AmigaOS4 update 3.

I have tried AmigaAMP v2.15 Test1, and audio stops or cuts out or crackles if I scroll up and down through a file displayed in AmiPDF, or scrolling around large jpeg pictures that are bigger than the screen.

Resizing windows does not seem to cause any problems at all for me.

I still have interrupt set to yes in tooltypes in Devs:Monitors/Radeon icon.

redfox

µA-C

Last edited by redfox on 21-Aug-2005 at 06:36 PM.
Last edited by redfox on 21-Aug-2005 at 06:10 PM.

@Samwel

I can not reproduce this on my end.

Try sing Tunenet instead of Amigaamp.

_________________
µA1-C/750FX@800Mhz/OS4.1 FE up#1
A4000/CSPPC 060-233/146Mb/CVPPC /OS3.9
A3000/CSPPC 060/233/64MB/Prometheus w/ Voodoo3/ OS3.9
A3000/PIV, A3000T/PIV

@redfox

The developer (antony) is working on the problem so we just have to wait. I did have INTERRUPT set to 'NO' for a couple of week with no other noticeable ill effects. If it really bothers you, then change the tooltype to 'NO' & check that the problem is gone. Just make a note of what you changed so you can remember to undo it with the next update.

_________________
Hate tends to make you look stupid...

@Kraftwerk2

The problem is real, you may be one of the lucky ones. For some it shows up right away with scrolling, for me, I had to zoom in & scroll rapidly. The developer (antony) has duplicated the problem on his system, see post #43.

_________________
Hate tends to make you look stupid...

@sundown

Thanks for the update.

redfox

@sundown

He also is using a SB Live card. I am using the onboard sound of the µA1.

No problem here.

Have you tried with Tunenet and not AmigaAmp?

I stopped using AmigaAmp because it always exits with an error.

_________________
µA1-C/750FX@800Mhz/OS4.1 FE up#1
A4000/CSPPC 060-233/146Mb/CVPPC /OS3.9
A3000/CSPPC 060/233/64MB/Prometheus w/ Voodoo3/ OS3.9
A3000/PIV, A3000T/PIV

@sundown

I voted NO. It's the SBLive5.1 sound card. I don't have that~ PCI128v4.1 by
Creative works OK. Checked out against ANR, TuneNet, AmigaAmp, SongPlayer, etc.
I thought this was cleared up months ago?

@Kraftwerk2

There is no difference which sound card you have.
This is probably due to AmiPDF/AmiGS hogging all CPU power while
doing this. But as the author pointed out this might be fixed in an
internal version not released yet.

Follow my instructions on post #20 and I'm SURE you'll reach the
same result as I have. And yes, I also have a µA1-C and using the
onboard sound.
It's important that you keep the mousebutton pressed down through
the whole test. Doing a small scroll and then releasing the button
will not disturb the sound. It takes about 1-2 sec before it happens.

_________________
/Harry

[SOLD] µA1-C - 750GX 800MHz - 512MB - Antec Aria case

Avatar by HNL_DK!

@Kraftwerk2

He also is using a SB Live card. I am using the onboard sound of the µA1.
-------------------------------------------------------------------------------

I'm using a µA1 & I can reproduce the audio cut out, but it doesn't jump out & bite me. There is a delayed effect & the more scrolling you do, the more it happens. I would say under normal AmiPDF use I would probably not hear the problem, but others have more sensitive systems & the problem shows up easier. The problem is real as too many of use can reproduce it.

I can reproduce the effect with all the players I have.

_________________
Hate tends to make you look stupid...

Snuffy my friend,

You're getting this problem confused with the audio/internet lockup problem. That problem was tracked back to the SB audio card. The built in SB audio on the µA1 was not a problem that I recall. This problem is a audio cut out/scrolling bug in AmiPDF & AmiGS.

On a more serious not, why the hell were you not in the Sunday chat? We miss you.

_________________
Hate tends to make you look stupid...

@sundown

Well I can reconstruct this now, but with a few qualifiers.

I need to zoom in about 4 times and scroll for about 5 seconds before I notice a short drop in the audio.

The reason I never noticed it before was simply because this is something that I never would have though of doing. I usually read PDF file full screen, so I never need to scroll.

Even with only zooming in once it works fine and has no drop outs. After scrolling twice the dropouts start.

Since zooming in seems to eat alot more memory (I get out of memory errors when zooming into large PDF files at some point). I can see how with all that memory to manage timing can get to be critical.

So, while a bug. It is something I never would have noticed.

[EDIT} I tried changing the AHI prefs to 97% CPU usage, but that did not help.

Last edited by Kraftwerk2 on 22-Aug-2005 at 01:52 PM.

_________________
µA1-C/750FX@800Mhz/OS4.1 FE up#1
A4000/CSPPC 060-233/146Mb/CVPPC /OS3.9
A3000/CSPPC 060/233/64MB/Prometheus w/ Voodoo3/ OS3.9
A3000/PIV, A3000T/PIV

@sundown

Not confused --> I'm NOT using Update#3; ergo, no problem! In UD#3 my printer
and driver won't work -- EpsonColor. UD#3 wasn't as functional as UD#2.

-> "On a more serious note, why the hell were you not in the Sunday chat? We
miss you."

Oops! Umm, I joined the Bodies in AWOL; I tripped and fell through a stargate;
these aliens just like abducting me ; *cough* Actually I don't get home 'till
after 10PM and kind of tired out! Sorry! Season adjustments coming soon and get
back to the chats.

A G3 *should* have enough power to do some simple scrolling. AWeb and IBRowse scroll fine and fast without any sound problems. Ok, IBrowse has a bit distorted sound while scrolling, but no dropouts (think this is the emulation).