Friday, March 24, 2017

Blog wczerni.pl - Wizerunek i styl.

Tym razem coś dla Pań, ale i Panów, i po polsku. Doskonały blog o stylu i wizerunku.

Gorąco polecam.

http://www.wczerni.pl/


Wednesday, March 22, 2017

Fedora 24: Recording with Ardour, QJackCtl and Zoom 2g.1u Guitar Effects Pedal.

I assume that you have Ardour (I have version 5.5.0-1), JACK, QJackCtl already installed and Zoom correctly connected to your computer via USB.

[GUITAR]---INPUT[ZOOM]---USB---[PC]PHONES---AUX[AMP]PHONES---d(-_-)b
                OUTPUT-------------------------INPUT

First launch QJackCtl and configure the JACK server. Do not start the server yet. Click Setup... button.


From Settings tab select Advanced tab.
Select as an Input Device and choose the hw:CODEC USB Audio CODEC.


Launch the Ardour and select the following settings for the new session and click Start button. 


Once the Ardour is started check if the JACK is running and you see the connections. If JACK is not running click the Start button.


Click the Connect button and then Expand All. You may need to click Refresh too.


Add a new track(s).



Right click on the track and select Inputs... and Outputs... to configure the connections respectively.
Repeat the same for all other tracks you added and the Master track.

Track(s)


Master:

You can also configure Inputs... and Outputs... in the Mixer. 
Click the Mixer button in Ardour main window on the toolbar.
Click the "Track Name" in the Mixer for each track and select Inputs... and Outputs... to configure them.




You can start recording now.

Note: Of course, it is a very basic configuration to just get you started. I guess, it should work with any USB audio interface really. If you want to learn more please see the reference below.

Reference:



Saturday, October 1, 2016

Fedora 24: invisible mouse cursor after login to VM running on KVM.

Issue: In Fedora 24 after login into the VM running on a local host in KVM the mouse cursor becomes invisible.

Environment: 
Host
    - Fedora 24
    - kernel 4.7.4-200.fc24.x86_64
    - virt-manager-1.4.0-3.fc24.noarch
    - virt-viewer-4.0-1.fc24.x86_64
    - qemu-kvm-2.6.1-1.fc24.x86_64
VM
    - SUSE Linux Enterprise Server 12 SP1
    - kernel 3.12.49-11-default
    - video QXL / Spice
    - gnome-shell-3.10.4-40.1.x86_64

Solution:
I found that changing the screen resolution to a different value resolves the issue and mouse cursor becomes visible again.
To automate this workaround I wrote the following simple script named chres.sh:

     #!/bin/bash
     # Change the resolution
     XRANDR=`which xrandr`
     SCREEN="Virtual-0"
     $XRANDR --output $SCREEN --mode 1280x720
     sleep 1
     $XRANDR --output $SCREEN --mode 1280x800
     exit

I then created the autostart folder in ~/.config/ and added chres.sh to it and made it executable.
Finally, I created the following file in ~/.config/autostart/ named chres.desktop:

     [Desktop Entry]
     Name=chres
     GenericName=Changing resolution
     Comment=To change the resolution in Gnome session 
     Exec=/home/username/.config/autostart/chres.sh
     Terminal=true
     Type=Application
     X-GNOME-Autostart-enabled=true

Now when I login to Gnome session the chres.sh runs automatically changing quickly the resolution and resolving the issue, so the mouse cursor is immediately visible and available. 
If you have the same issue, you may need to check if the xrandr is installed in the same path and what is your default screen.


I hope this will help.