The Lightroom 4 Presets System v1.2 & Digital DVD by SLR Lounge

Mình chia sẻ link download bộ Preset trị giá 250$ này mong mem nào có tài khoản premium ở http://extabit.com download về và chia sẻ lại cho các thành viên khác trong diễn đàn.

Download: http://www.mediafire.com/?asqvnuv6uagdhgg

The Lightroom 4 Presets System v1.2 & Digital DVD by SLR Lounge is a collection of 216 Presets including 189 Develop Presets, 27 Brush Presets, and a nearly 6 hour digital DVD featuring over 40 video tutorials to teach you how to get the most from this powerful system!
We are confident that this is the best Lightroom 4 Preset System available. It is designed to not only be powerful enough to create any effect, but also intuitive enough to achieve them in just a few clicks saving you boat loads of time!

​

​

The LR4 Preset System is designed for virtually any look and effect, for example:

• Basic Color Correction
• Faux HDR Processing
• Vintage Fades and Washes
• Black and White and Antique Efects
• Tilt Shift and Toy Camera Special Effects
• Detail Enhancing
• Portrait Retouching
• and more, the sky is the limit!

What’s Included in the System
189 Develop Presets – From 1-Click Mixologies, to Base Adjustments, to every type of curve (vintage, poppy, etc) you can imagine, to Color Toning and Special Effects; this system has everything you need to pull off virtually any look and effect within just a couple of clicks!
27 Brush Presets – For advanced retouch and detail enhancing, we have included 26 Brush Presets that will help you retouch skin, enhance eyes, enhance backgrounds, and more!
28 Mixologies – We have also included 28 One-Click Mixology Presets which include some of our favorite go-to studio effects, as well as some awesome creative effects and examples. Each built with the LR4 Preset System.
Preset System Digital DVD Download – Included in your purchase is the LR4 Preset System Digital DVD which contains 44 HD tutorials teaching you everything you need to know about the Lightroom 4 Preset System. From installation and updating, to how we created each and every Mixology, to advanced effects and retouching.
Ongoing Mixologies and Tutorials – We will constantly be releasing new Mixology recipes and tutorials showing you how to get the most from your LR4 Preset System! Simply follow us onFacebook and on the SLR Lounge Lightroom Page to see the latest and greatest!
DVD Table of Contents
Besides the actual presets and the exercise files, we’ve included the following video tutorials:

Chapter 1 – Intro and Install​

1. Introduction​

2. Preset Demonstration​

3. First Time Preset Installation​

4. Installing Updates​

5. Develop Presets Introduction​

6. Brush Presets Introduction​

7. Setting Standard Import Preset​

8. Customizing Standard Import Preset​

​

Chapter 2 – Creating Mixologies​

1. Soft Portrait Standard Color​

2. Soft Portrait Standard Desaturated​

3. Soft Portrait Standard B&W​

4. Vivid Landscape Standard Color​

5. Vivid Landscape Standard Desaturated​

6. Vivid Landscape Standard B&W​

7. Vivid Landscape HDR Light​

8. Vivid Landscape HDR Strong​

9. Vivid Landscape HDR B&W​

10. Vivid Landscape HDR Grunge​

11. Vivid Landscape HDR B&W Grunge​

12. Stylized Color Contrast Crush​

13. Stylized Color Teal Orange Crush​

14. Stylized Color Yellow Violet Crush​

15. Stylized Color Whimsical Green​

16. Stylized Color Whimsical Yellow​

17. Vintage Fades Neutral Fade​

18. Vintage Fades Cool Fade​

19. Vintage Fades Warm Fade​

20. Vintage Fades Bronzed Fade​

21. Vintage Fades Warm Punchy Vintage​

22. Vintage Fades Subtle Poppy Vintage​

23. B&W Fades Bright Fade​

24. B&W Fades Fade With Clipped Blacks​

25. B&W Fades Soft Film Fade​

26. B&W Fades High Contrast Film​

27. Toy Camera Warm Faded Slide Film​

28. Toy Camera Poppy Orange Teal Slide Film​

​

Chapter 3 – Brushes & More​

1. Retouching a Portrait Part I​

2. Retouching a Portrait Part II​

3. Detail Enhancing​

4. Creative Brushing​

5. Tilt Shift Effect​

6. Advanced Dust Correction Curve​

7. Removing HDR Effects Over Skin​

Raspberry Pi with two or more webcams

Raspberry Pi with two webcams

Provided they are plugged directly into the Raspberry Pi's two USB ports directly, I've been able to connect it to two web-cameras at once, and stream the pictures using the open source Motion software (which also records images for any movement). Watching a double webcam feed from Safari on my iPad, while controlling the Raspberry Pi using Panic Inc's SSH application Prompt was kind of fun!

As you might guess from past blog posts, I was trying (several) Microsoft Live Vision USB webcams, with the aim of using them via the RPi and a long ethernet cable to monitor my bird nesting box cameras. My plan (outlined back on this post) is to use power-over-ethernet (POE) to supply 5V to the Raspberry Pi, which will be down the garden within USB range of the birdbox or birdboxes. But first, to get this working indoors - which meant initially a long wait before my RPi was delivered.

Meanwhile, other people were also experimenting with using the RPi as an IP-webcam, like Jeremy who tried bothffserver on his RPi and then later switched to using Motion on a battery powered RPi webcam with wifi and more. Nice blog!

Motion under Raspbian

I decided to try the recently released Raspbian-based SD card image, specifically the 2012-07-15-wheezy-raspbian.ziprelease. During the first boot I used the menu to expand the file system to take the whole SD card, enabled SSH access, and set my keyboard and locale, and opted not to boot to the graphical desktop. I then ran an update, and installed Motion, the Apache webserver, Emacs, etc.

$ sudo apt-get update

$ sudo apt-get upgrade

$ sudo apt-get install motion

$ sudo apt-get install apache2

$ sudo apt-get install emacs

Initial experiments with an un-powered and a powered USB hub were not fruitful - the second webcam wouldn't register - in fact in some configurations even low power devices like my mouse or keyboard wouldn't work. So rather than trying this with a USB keyboard and mouse, I switched to SSH access and used the only two USB ports for two webcams - which worked.

$ ls /dev/vid*
/dev/video0  /dev/video1

I've already been running motion for a while now on an old laptop, so the configuration wasn't too hard - I knew that on my laptop getting several USB cameras running at once meant sticking with the default low resolution of 320x240 pixels. I went with two camera configuration files as ~/webcam/cam1.conf which is just:

videodevice /dev/video0
webcam_port 8081

And likewise for the second camera, configuration file ~/webcam/cam2.conf is just:

videodevice /dev/video1
webcam_port 8082

These are very short because everything else is in /etc/motion/motion.conf, the main configuration file, most of which remains with the default values. The main change is two thread settings pointing at the above per-camera settings:

webcam_localhost off
thread /home/pi/webcam/cam1.conf
thread /home/pi/webcam/cam2.conf

The only other configuration change so far is for making this act like an IP-webcam was to change the default (secure) setting restricting this to the same machine (local host). Note you must also ensure the two camera streams are on different ports (I went for the motion default of 8081, and 8082 for the second camera).

I then setup a minimal webpage by creating the file /var/www/webcam.html showing the two images side by side (which would be served by Apache). Initially I've just hard coded the RPi's hostname to access the two webcams, but I think a little Apache magic is a better solution considering my IP address is allocated by DHCP and will change, but this works for now.

Update: As requested in the comments, here's the simple HTML for the page I access as http://raspberrypi/webcam.html from within my home network (this should be edited if you change the default hostname of raspberrypi):

$ more /var/www/webcam.html

Raspberry Pi Webcameras

Update: If you want motion to auto-start when the computer is rebooted, you need to edit the file/etc/default/motion to say start_motion_daemon=yes and this will happen automatically via the/etc/init.d/motion startup script. I'm using this now that I have installed a Raspberry Pi in my garden. Note I added$all to the Required-Start list to hopefully ensure that the USB system, ethernet, and date-time (via the network) are live before starting Motion.

Data Sync

It would be nice if DropBox could run on the Raspberry Pi - but right now it doesn't. You can go here to vote for DropBox to support Linux on the ARM processor. That rules out one way to automatically collect movement triggered images from the RPi - but there are several other options here, perhaps rsync to a separate image server?

Update - More USB devices?

As I noted in the introduction, I could only get two USB webcams to work when directly connected - and thus had to log into the RPi by SSH to control it. Even trying two cameras and a keyboard via a powered or unpowered hub proved problematic.

Using a powered hub is the recommended solution, so perhaps my hub just wasn't up to the job? However, I've been reading about an alternative hack to bypass the RPi's F1 and F2 polyfuses as described on The IO Blog, Himesh's blog, and elsewhere including this forum thread USB Port Current Boost. You would of course still need to use a sufficiently strong power supply.

UBUNTU: Mount .nrg audio CD images

This PPA can be added to your system manually by copying the lines below and adding them to your system's software sources.

deb http://ppa.launchpad.net/cdemu/ppa/ubuntu YOUR_UBUNTU_VERSION_HERE main 

sudo add-apt-repository ppa:cdemu/ppa
sudo apt-get update
sudo apt-get install gcdemu
gnome-session-properties

makeself - Make self-extractable archives on Unix

EX: makeself --nox11 --bzip2 --nowait /home/dangquang/Downloads/hplip-3.13.10 mysetup.run "install hplib GUI" ./hplip-install

makeself.sh is a small shell script that generates a self-extractable tar.gz archive from a directory. The resulting file appears as a shell script (many of those have a .run suffix), and can be launched as is. The archive will then uncompress itself to a temporary directory and an optional arbitrary command will be executed (for example an installation script). This is pretty similar to archives generated with WinZip Self-Extractor in the Windows world. Makeself archives also include checksums for integrity self-validation (CRC and/or MD5 checksums).
The makeself.sh script itself is used only to create the archives from a directory of files. The resultant archive is actually a compressed (using gzip, bzip2, or compress) TAR archive, with a small shell script stub at the beginning. This small stub performs all the steps of extracting the files, running the embedded command, and removing the temporary files when it's all over. All what the user has to do to install the software contained in such an archive is to "run" the archive, i.e sh nice-software.run. I recommend using the "run" (which was introduced by some Makeself archives released by Loki Software) or "sh" suffix for such archives not to confuse the users, since they know it's actually shell scripts (with quite a lot of binary data attached to it though!).
I am trying to keep the code of this script as portable as possible, i.e it's not relying on any bash-specific features and only calls commands that are installed on any functioning UNIX-compatible system. This script as well as the archives it generates should run on any Unix flavor, with any compatible Bourne shell, provided of course that the compression programs are available.
As of version 2.1, Makeself has been rewritten and tested on the following platforms :

• Linux (all distributions)
• Sun Solaris (8 and above)
• HP-UX (tested on 11.0 and 11i on HPPA RISC)
• SCO OpenUnix and OpenServer
• IBM AIX 5.1L
• MacOS X (Darwin)
• SGI IRIX 6.5
• FreeBSD
• UnicOS / Cray
• Cygwin (Windows)

If you successfully run Makeself and/or archives created with it on another system, then let me know!

Examples of publicly available archives made using makeself are :

• Game patches and installers for Id Software games like Quake 3 for Linux or Return To Castle Wolfenstien ;
• All game patches released by Loki Software for the Linux version of popular games ;
• The nVidia drivers for Linux
• The installer for the Linux version of Google Earth
• The VirtualBox installers for Linux
• The Makeself distribution itself ;-)
• and countless others...

Important note for Apache users: By default, most Web servers will think that Makeself archives are regular text files and thus they may show up as text in a Web browser. The correct way to prevent this is to add a MIME type for this file format, like so (in httpd.conf) :
AddType application/x-makeself .run
Important note for recent GNU/Linux distributions: Archives created with Makeself prior to v2.1.2 were using an old syntax for the head and tail Unix commands that is being progressively obsoleted in their GNU forms. Therefore you may have problems uncompressing some of these archives. A workaround for this is to set the environment variable $_POSIX2_VERSION to enable the old syntax, i.e. :
export _POSIX2_VERSION=199209

Usage

The syntax of makeself is the following:
makeself.sh [args] archive_dir file_name label startup_script [script_args]

• args are optional options for Makeself. The available ones are :
  • --version : Prints the version number on stdout, then exits immediately
  • --gzip : Use gzip for compression (is the default on platforms on which gzip is commonly available, like Linux)
  • --bzip2 : Use bzip2 instead of gzip for better compression. The bzip2 command must be available in the command path. I recommend that you set the prefix to something like '.bz2.run' for the archive, so that potential users know that they'll need bzip2 to extract it.
  • --compress : Use the UNIX "compress" command to compress the data. This should be the default on all platforms that don't have gzip available.
  • --nocomp : Do not use any compression for the archive, which will then be an uncompressed TAR.
  • --notemp : The generated archive will not extract the files to a temporary directory, but in a new directory created in the current directory. This is better to distribute software packages that may extract and compile by themselves (i.e. launch the compilation through the embedded script).
  • --current : Files will be extracted to the current directory, instead of in a subdirectory. This option implies --notemp above.
  • --follow : Follow the symbolic links inside of the archive directory, i.e. store the files that are being pointed to instead of the links themselves.
  • --append (new in 2.1.x): Append data to an existing archive, instead of creating a new one. In this mode, the settings from the original archive are reused (compression type, label, embedded script), and thus don't need to be specified again on the command line.
  • --header : Makeself 2.0 uses a separate file to store the header stub, called "makeself-header.sh". By default, it is assumed that it is stored in the same location as makeself.sh. This option can be used to specify its actual location if it is stored someplace else.
  • --copy : Upon extraction, the archive will first extract itself to a temporary directory. The main application of this is to allow self-contained installers stored in a Makeself archive on a CD, when the installer program will later need to unmount the CD and allow a new one to be inserted. This prevents "Filesystem busy" errors for installers that span multiple CDs.
  • --nox11 : Disable the automatic spawning of a new terminal in X11.
  • --nowait : When executed from a new X11 terminal, disable the user prompt at the end of the script execution.
  • --nomd5 and --nocrc : Disable the creation of a MD5 / CRC checksum for the archive. This speeds up the extraction process if integrity checking is not necessary.
  • --lsm file : Provide and LSM file to makeself, that will be embedded in the generated archive. LSM files are describing a software package in a way that is easily parseable. The LSM entry can then be later retrieved using the '-lsm' argument to the archive. An exemple of a LSM file is provided with Makeself.
• archive_dir is the name of the directory that contains the files to be archived
• file_name is the name of the archive to be created
• label is an arbitrary text string describing the package. It will be displayed while extracting the files.
• startup_script is the command to be executed from within the directory of extracted files. Thus, if you wish to execute a program contain in this directory, you must prefix your command with "./". For example, ./program will be fine. The script_args are additionnal arguments for this command.

Here is an example, assuming the user has a package image stored in a /home/joe/mysoft, and he wants to generate a self-extracting package named mysoft.sh, which will launch the "setup" script initially stored in /home/joe/mysoft :
makeself.sh /home/joe/mysoft mysoft.sh "Joe's Nice Software Package" ./setup
Here is also how I created the makeself.run archive which contains the Makeself distribution :
makeself.sh --notemp makeself makeself.run "Makeself by Stephane Peter" echo "Makeself has extracted itself"

Archives generated with Makeself 2.1 can be passed the following arguments:

• --keep : Prevent the files to be extracted in a temporary directory that will be removed after the embedded script's execution. The files will then be extracted in the current working directory and will stay here until you remove them.
• --verbose : Will prompt the user before executing the embedded command
• --target dir : Allows to extract the archive in an arbitrary place.
• --nox11 : Do not spawn a X11 terminal.
• --confirm : Prompt the user for confirmation before running the embedded command.
• --info : Print out general information about the archive (does not extract).
• --lsm : Print out the LSM entry, if it is present.
• --list : List the files in the archive.
• --check : Check the archive for integrity using the embedded checksums. Does not extract the archive.
• --nochown : By default, a "chown -R" command is run on the target directory after extraction, so that all files belong to the current user. This is mostly needed if you are running as root, as tar will then try to recreate the initial user ownerships. You may disable this behavior with this flag.
• --tar : Run the tar command on the contents of the archive, using the following arguments as parameter for the command.
• --noexec : Do not run the embedded script after extraction.

Any subsequent arguments to the archive will be passed as additional arguments to the embedded command. You should explicitly use the -- special command-line construct before any such options to make sure that Makeself will not try to interpret them.

License

Makeself is covered by the GNU General Public License (GPL) version 2 and above. Archives generated by Makeself don't have to be placed under this license (although I encourage it ;-)), since the archive itself is merely data for Makeself.

Download

Get the latest official distribution here (version 2.1.5).
The latest development version can be grabbed from GitHub. Feel free to submit any patches there through the fork process.

Version history

• v1.0: Initial public release
• v1.1: The archive can be passed parameters that will be passed on to the embedded script, thanks to John C. Quillan
• v1.2: Cosmetic updates, support for bzip2 compression and non-temporary archives. Many ideas thanks to Francois Petitjean.
• v1.3: More patches from Bjarni R. Einarsson and Francois Petitjean: Support for no compression (--nocomp), script is no longer mandatory, automatic launch in an xterm, optional verbose output, and -target archive option to indicate where to extract the files.
• v1.4: Many patches from Francois Petitjean: improved UNIX compatibility, automatic integrity checking, support of LSM files to get info on the package at run time..
• v1.5.x: A lot of bugfixes, and many other patches, including automatic verification through the usage of checksums. Version 1.5.5 was the stable release for a long time, even though the Web page didn't get updated ;-). Makeself was also officially made a part of the Loki Setup installer, and its source is being maintained as part of this package.
• v2.0: Complete internal rewrite of Makeself. The command-line parsing was vastly improved, the overall maintenance of the package was greatly improved by separating the stub from makeself.sh. Also Makeself was ported and tested to a variety of Unix platforms.
• v2.0.1: First public release of the new 2.0 branch. Prior versions are officially obsoleted. This release introduced the '--copy' argument that was introduced in response to a need for the UT2K3 Linux installer.
• v2.1.0: Big change : Makeself can now support multiple embedded tarballs, each stored separately with their own checksums. An existing archive can be updated with the --append flag. Checksums are also better managed, and the --nochown option for archives appeared.
• v2.1.1: Fixes related to the Unix compression (compress command). Some Linux distributions made the insane choice to make it unavailable, even though gzip is capable of uncompressing these files, plus some more bugfixes in the extraction and checksum code.
• v2.1.2: Some bug fixes. Use head -n to avoid problems with POSIX conformance.
• v2.1.3: Bug fixes with the command line when spawning terminals. Added --tar, --noexec for archives. Added --nomd5 and --nocrc to avoid creating checksums in archives. The embedded script is now run through "eval". The --info output now includes the command used to create the archive. A man page was contributed by Bartosz Fenski.
• v2.1.4: Fixed --info output. Generate random directory name when extracting files to . to avoid problems. Better handling of errors with wrong permissions for the directory containing the files. Avoid some race conditions, Unset the $CDPATH variable to avoid problems if it is set. Better handling of dot files in the archive directory.
• v2.1.5: Made the md5sum detection consistent with the header code. Check for the presence of the archive directory. Added --encrypt for symmetric encryption through gpg (Eric Windisch). Added support for the digest command on Solaris 10 for MD5 checksums. Check for available disk space before extracting to the target directory (Andreas Schweitzer). Allow extraction to run asynchronously (patch by Peter Hatch). Use file descriptors internally to avoid error messages (patch by Kay Tiong Khoo).

Links

• Check out the "Loki setup" installer, used to install many Linux games and other applications, and of which I am the co-author. Since the demise of Loki, I am now the official maintainer of the project, and it is now being hosted on icculus.org, as well as a bunch of other ex-Loki projects (and a lot of other good stuff!).
• Bjarni R. Einarsson also wrote the setup.sh installer script, inspired by Makeself. Check it out !

Contact

This script was written by Stéphane Peter (megastep at megastep.org) I welcome any enhancements and suggestions.
Contributions were included from John C. Quillan, Bjarni R. Einarsson, Francois Petitjean, and Ryan C. Gordon, thanks to them! If you think I forgot your name, don't hesitate to contact me.
icculus.org also has a Bugzilla server available that allows bug reports to be submitted for Loki setup, and since Makeself is a part of Loki setup, you can submit bug reports from there!

Fix Random Freezes With Ivy Bridge Integrated HD 4000 Graphics

From link: http://www.howtoeverything.net/linux/hardware/random-freezes-integrated-hd-4000-graphics

If you equipped your system with an Ivy Bridge Intel processor with HD 4000 graphics and use the latest LTS Ubuntu version (12.04) or Linux Mint (13/Maya), you might also experience unpredictable system freezes from time to time. This article outlines the reason and the fix.

The Issue
If you are using any Linux distribution that utilizes the Linux Kernel 3.2, as Ubuntu 12.04, Linux Mint 13 or every other distribution based on it does, you run into a bug causing a system freeze because some problem between this kernel and your integrated graphics chip. You might have chosen this version of Ubuntu since it is a LTS one. Also the most obvious reason to think of would be that system freezes are caused by compiz or any other window decorator or window manager, it is really just a incompatibility with the kernel.

Are Google Chrome or Chromium responsible?
Since the last Google Chrome and Chromium Update, you might think that these browsers are responsible, since you suddenly find some entries in your syslog that contain:
audit ... comm="chromium-browse" reason="seccomp" sig=0 syscall=4 compat=0 ... code=0x50002
Unfortunately it is a bit more complicated: not the browsers themselves are creating the errors, but they are just printing errors logged in the syslog that are the effect of the  problem with the kernel. Most of the times you might even experience the freezing issue using Chrome or Chromium, but this is not mainly because of these browsers but because you use them most of the time you use your computer. This makes it significantly more possible that you experience the issue while browsing the internet.

The Fix
If you upgrade to the next highest version of your distribution (e.g. Ubuntu 12.10 or Linux Mint 14) you automatically get the newer Linux Kernel version 3.5 and won't experience the problem anymore. If you don't feel like upgrading, it is also possible to install the kernel of the next Ubuntu / Linux Mint version without doing an complete system upgrade. If you are using Ubuntu 12.04 or Linux Mint 13 you can install a package called linux-generic-lts-quantal. It is a special meta package to equip the LTS (Long Time Support) versions Ubuntu 12.04 / Linux Mint 13 with the most uptodate kernel from the next Ubuntu version, which is codenamed Quantal Quetzal. Install it like this:

• open up a terminal window and copy/paste the following into it and hit return
• sudo apt-get install linux-generic-lts-quantal
• if asked whether to install all necessary packages enter Y
• reboot to use the newest kernel
• you can still boot with the old kernel through your boot menu 

Is it really fixed?
Fixing an issue like this always comes with the uncertainty whether the problem is really gone for good. A couple of things you can check to be reassured:

• booting your system with the new kernel and using Chromium or Chrome shouldn't produce any of the above mentioned syslog entries anymore
• playing a couple of youtube videos in full HD and holding ALT + Tab to switch between them very fast shouldn't make the system hang anymore
• if you're using animations with compiz, you should also notice that everything moves much more fluently now. You won't get the small hangs anymore, that you might have experience e.g. when unminimizing windows from heavy applications. 

Additionally: we applied the fix to one of our own machines, which stalled at least once per day because of this issue. It now has worked flawlessly for a whole week 24/7, even with running burn-in tests during nights! So it seems the kernel upgrade really resolved this issue for good, and the best thing: you can stick to the latest LTS version from Ubuntu and Linux Mint without the need for doing a distribution upgrade just because of the newer kernel.

Set up USB for Virtualbox

Note: There is no longer a "pay" version for individual copies/licenses of VirtualBox. For more information please see:http://www.virtualbox.org/wiki/Licensing_FAQ

For Precise Pangolin 12.04

This was tested with VBox 4.1.12-Ubuntu_r77245 (Ubuntu Reps) with Matching Extensions, and Guest Additions.

Add yourself to the user group vboxusers.

However the Manage Groups Applet is no longer installed in 12.04 by default.

Open Software Centre, Search "Gnome-System-Tools" and install.

Tap Super Key to get the Dash, Type "user" and click the Users and Groups icon to start up the Groups Manager. Click "Manage Groups", find vboxusers, click properties, add your own and any other desired users to the vboxusers group.

Click OK.

Now log out and back in, to make use of available USB devices. Connect USB Devce(s)

===FOR PERSISTENT CONNECTION TO VM===

Open VBox, go to Settings for the VM, Go to USB.

Click USB+ Icon and select device from List (Be careful not to select your mouse device)

This will add a Filter Spec to the List, repeat as necessary for more devices

Start VM - Devices should appear in Guest OS, and mount or request drivers etc as normal for the OS.

Devices Mounted in Guest OS will likely be unavailable in Host OS

===FOR TEMPORARY CONNECTION TO VM===

Insert USB Device & Wait for it to activate in Host OS

Start or go to VM

Right Click USB Icon in the VM Status Bar at bottom of screen, OR from Menu go Devices > USB Devices, and select desired device.

Devices should appear in Guest OS, and mount or request drivers etc as normal for the OS.

Devices Mounted in Guest OS will likely be unavailable in Host OS

Date calculation in iReport: set default of Date input at the first day of current month

new GroovyShell(new Binding()).evaluate("""
Calendar c = Calendar.getInstance()
c.set(Calendar.DAY_OF_MONTH, 0)
return "" + (c.getTime().getYear() + 1900) + "-" + c.getTime().getMonth() + "-" + c.getTime().getDay()
""")