Monthly Archives: March 2014

Using SimpleScreenRecorder on OpenSuse 13.1

Using SimpleScreenRecorder on OpenSuse 13.1

It’s hard to find a quick tutorial for using SSR on Linux, so I write one. This configuration is used by me.

If you wish to record something on your desktop with microphone and then use it both under Windows and Linux, you should make some settings in SSR.

In Audio Input,  you should choose:

1/ PulseAudio because it’s more useful than ALSA or JACK

2/ Source: I use the option without “Monitor of” (I can’t record my voice with the “Monitor of” option – no voice recorded from my microphone)

As to codecs,  you should choose:

1/ Container: AVI

2/ Video: WMV2

3/ Audio: WMAV2

This configuration is useful because:

1/ You can use your microphone with no problem

2/ Those codecs cooperate with Windows software

3/ The quality of video and audio is very good

4/ It’s supported by most software

Warning: When you record with using a laptop, you have to choose between internal and external microphone. In Windows, you can choose at the moment of your plugging a headphone and microphone. In Linux, it’s not so easy. To do that, you should install pavucontrol. It’is a simple GTK based volume control tool (I use it with KDE). Run pavucontrol. You should see the window with options that control Pulse Audio. You should be especially interested in Input Devices and Output Devices.

If you wish to use the internal microphone, just select this option. If you wish to plug the headphone and microphone, just select the external microphone. Using the external microphone is a better solution because when you record using the laptop speaker only, there will be much background noise.

However, you can have still problem with background noises when you try to record with full volume. I think the 80% of volume during recording with microphone is the best.

Debugowanie gry w Unity3D z MonoDevelop\Game Debugging in Unity3D with MonoDevelop

Debugowanie gry w Unity3D z MonoDevelop\Game Debugging in Unity3D with MonoDevelop

In Polish:

1/ Uruchomione Unity3D i MonoDevelop

2/wstawienie pułapek (breakpoints) do kodu w MonoDevelop, w miejscu, gdzie podejrzewamy buga

3/ MonoDevelop: Run -> Attach to Process

4/ Pojawia się okno wyboru procesów do dodania

5/ Klikamy proces naszego Unity3D -> Attach

6/ Teraz Unity debugger jest dołączony do MonoDevelop

7/ Klikamy Play w Unity3D

8/ Kiedy dojdzie wykonanie programu gry do pułapki, następuje przerwanie gry (w pułapce strzałka)

9/ Teraz możemy stosować step over, step into i step out

In English:

1/ Start Unity3D and MonoDevelop

2/Insert breakpoints you want

3/ MonoDevelop: Run -> Attach to Process

4/ We see the window with processes to add

5/ Click the process for Unity3D -> Attach

6/ Now Unity Debugger is attached to MonoDevelop

7/ Click Play in Unity3D

8/ When the game runs a breakpoint, the game is paused (you can see an arrow in the breakpoint)

9/ Now you can use step over, step into and step out just like in other IDEs