__Background__
So you dupe FIAB and skip the cs. Right afterwards, the first FIAB instance ends, om0 is set. Then it fades and after that, om0 is set again.
At this point you want to have a call and hold it. If you do not hold it before om0 is set, you lose it.
That must be the reason that "the call goes away too fast" - the phone rings but is not held, om0 is set -> the call "goes away too fast" (I hate that phrase - the call does not go away if you hold it. It "stays" or it "goes away" - "goes away "too fast" suggests that it could "go away slow enough").
An example of a failure is [this](https://www.youtube.com/watch?v=emliHbVSCqY). **Don't copy what he did, ** use the micro-optimizations I describe in *1)*. Notice how there is a delay of several frames between him holding TAB and the stats menu appearing, showing that the TAB button is not acknowledged as being held. By the time it is, the call is already gone.


__These help__
0) Set key repeat rate and delay to the fastest (use Windows search for "keyboard" - whatever it is in your language)
https://cdn.discordapp.com/attachments/271678111748194304/373956839559397386/unknown.png

Btw, there is a bug in the forum software: images with query string - e.g. *?width=136* - are not shown as image [bug report](https://www.speedrun.com/The_Site/thread/onfz6/24#sx285)



1) Minimize the time where no pause buffering happens:
1.1) start PBing asap: During the cs, hold Esc and shortly afterwards* skip the cutscene with the left mouse button (non-mouse buttons, even shift, would "drop" Esc -> no pause buffering).
* "shortly after" because there is a delay between holding Esc and the OS (Windows) "mashing" it for you - hold down a button in a text box (e.g. Windows search) to see what I mean.

1.2) hold the call asap after the phone rings (not counting time in the pause menu):
- For this you need to have a shift button bound to "action" (the right shift button for example, if you like to use left shift for something else)
- Once the phone rings, hold shift. This makes the game ignore Esc. If the game is unpaused, the call is held now, ez. If the game ends up paused, simply unpause without letting go off shift (this only works with shift and mouse buttons. The others are dropped on unpausing and only ever count as pressed again when you release and re-press. Todo: look into mouse buttons, IIRC, there were problems with those).



2) Make sure that gta_sa.exe gets all the CPU power it can get. This makes pause buffering more effective
- affinity / priority:
* set gta_sa.exe priority to high (not real-time: [10:01 PM] Anti: really choppy audio and the mouse not working sometimes iirc)
* set gta_sa.exe affinity to a core other than #0: Afaik, every process uses CPU #0 by default
** in general, set the core affinity of other processes to the cores that gta_sa.exe does not use - if you feel lazy, only do it for OBS and LiveSplit, those make a big difference
* maybe even set it to all cores just for the dupe. Reset claims that that makes pause buffering unstable (cause a crash - or app hang?) - test it for yourself
* for all this, remember to have prio installed ( [resources](https://www.speedrun.com/gtasa/resources) -> ctrl-f for prio, read the description )

- overclocking
Well, look into this yourself, maybe for your hardware there is software that allows temporarily overclocking your CPU using hotkeys.



3) misc
- Reset claims that looking towards the casino while pause buffering helped. I have tested it and did not find any effect. Maybe it does have an effect when there are a bunch of objects on the screen, though, who knows?