Enter your MediaPIG Account email address and password and logon to MediaPIG.
MediaPIG automatically caches your MediaPIG account on each machine you use.
If you do not want to cache the MediaPIG account credentials on the current machine:
Check [ ] Do not cache credentials.
4.1 - Config Overview
MediaPIG High Level Configuration Overview
MediaPIG is based on content organized into Categories of the same content type where each category may contain one to many assets.
Movies can only be added to 'Movie Categories' and TV Shows and their episodes can only be added to 'TVShow Categories'.
Each asset such as a 'Movie' or 'TVShow' must be self contained in its own strongly named directory.
Each asset will require a unique .nfo file, a poster and optionally fanart or other image.
These supplementary files (.NFO/Images/Artwork) are collectively and generally known as 'metadata' and support files for content.
The .NFO files are critical to loading data into MediaPIG becoming a central part of how MediaPIG loads data into the database while the images provide a more rich environment to select content based on images.
From this point onwards we will refer to all '.NFO/Images/Supplementary data' as 'Metadata'.
Content MetaData
MediaPIG offers two main primary methods of identifying, collecting and adding metadata content for Movies and TVShows.
Unconfigured Scraping - MediaPIG does no scraping or modifications of images/artwork or .NFO files by default.
Configured Scraping - MediaPIG performs the scraping and can modify/download images/artwork and recreates the .NFO files.
These methods will collect relevant mediainfo, metadata and files about the content including acquiring posters, fanart, actor and thumb images, subtitle files, and other auxillary files or data bits.
Unconfigured Scraping
Users are responsible to determine how to collect, rename, organize and add metadata about local assets. Pre-existing .nfo/metadata must exist.
MediaPIG scraping settings can be left 'unconfigured' (the default settings) which prevents any scraping or pre-processing behaviours.
This natural 'unconfigured' design of MediaPIG is to implement a true 'PERSISTENT METADATA' design philosophy. This means that by leaving MediaPIG scraper settings as 'Unconfigured'
you will ensure that MediaPIG will not scrape, download, rename, re-organize data in the system related to assets automatically.
Your posters and artwork remain intact, "as is" and the system adminisrator of the MediaPIG implementation must use external scraping tools or another process to perform all of the scraping activities.
Essentially by default using this approach users are fully responsible to do everything to prepare media content to add to MediaPIG.
Strongly Named Assets Required
All assets added to category folders for processing into MediaPIG must be strongly named, organized by unique directories and have certain criteria requirements to work as expected.
Assets without .NFO files or not named properly will not be seen by the MediaPIG processing engine and will be ignored.
Configured Scraping
MediaPIG is configured to collect metadata about local assets based on using internet services to add content.
Scraping Integration Services Under Development
Functionality to provide scraping of multiple internet metadata services is currently in development and is not initially available in MediaPIG.
MediaPIG scraping settings to use internet services must be fully configured to provide automatic metadata scraping or pre-processing behaviours.
Activating scrapers within MediaPIG will require additional category folder configuration settings, API KEYs for related services, and some additional setup.
MediaPIG will then begin to scrape, download, rename, re-organize data in the system related to assets automatically.
Your posters and artwork may be changed during the scraping activities without notice and no archiving or backup of prior .nfo information or artwork will occur.
MediaPIG does not currently engage in any type of metadata archiving unlike TinyMediaManager which has a variety of metadata archiving strategies.
Using this approach MediaPIG will attempt to do everything to prepare media content for addition into MediaPIG.
Integrated Scraping
Using this approach requires an integrated approach to selectively identify each asset. Its a combination of automatically identifying the metadata options for each asset and having the user decisively select which service and asset id tags will be associated to the asset.
Using the additional option [X] Auto-Update this asset using defined service and ID tags users can make MediaPIG automatically refresh TVShows without prompting each time after the initial definition is selected.
Configuration Table
Review the following configuration table which outlines what a UNCONFIGURED vs CONFIGURED MediaPIG implementation looks like and what would happen under each scenario. Starting with a virgin unconfigured system allows expert users to define categories, add pre-processed carefully crafted content folders and load their assets directly into MediaPIG zero scraping required. This ultimate level of control is the basic default design but by no means does the system need to remain without any automated features enabled.
| Unconfigured |
|
Configured |
| Requires Categories within MediaPIG |
|
Requires Categories within MediaPIG |
| Requires pre-scraped content, strongly named |
|
Requires pre-processing folders, strongly named
Requires per-category Pre-Processing configuration in MediaPIG |
Scraping folders located outside of MediaPIG Category folders
Unscraped content cannot be placed into MediaPIG category folders |
|
Scraping folders located inside or outside of MediaPIG Category folders
Unscraped content can be placed inside MediaPIG category folders |
| Users required to pre-scrape all content |
|
MediaPIG can force rescraping content, as directed by users or automatically. |
Gaurantees 100% control over category content.
Content never changes unless users rescrape/reload. |
|
MediaPIG scraping may update content depending on settings.
Content might change if configured as such. |
|
|
|
Intial version only supports UNCONFIGURED environments
Functionality to provide scraping of multiple internet metadata services is currently in development and is not initially available in MediaPIG.
This means you cannot currently placed unscraped raw content into category folders and expect MediaPIG to see the content.
ALL CONTENT MUST CURRENTLY BE PRE-SCRAPED, STRONGLY NAMED, WITH VALID .NFO FILES.
MediaPIG recommends using TinyMediaManager for scraping metadata, downloading trailers, subtitles, renaming content strongly.
Configuration Process
The basic steps to get a MediaPIG up and running quickly involves the following high level steps
Requires User Supplied Content
Obviously the pre-requirement is actually having Movies or TV Show content to put into MediaPIG.
If you do not have any Movies or TV Show content to load into MediaPIG that is in the correct format and processed into separate folders with valid .NFO files there is little to no purpose to install and use MediaPIG at this time.
- SQL Server Installation
- MediaPIG Installation
- Create and Verify MediaPIG Account
- Create Database Process
- Connection/User Profiles
- Create Categories
- Scraping Configuration
- Reprocess Existing Content into MediaPIG
- Scrape new Content : Outside MediaPIG
- Scrape new Content : Inside MediaPIG
The MediaPIG Installation process installs MediaPIG which will require the user to have an existing SQL Server already installed and available.
The user will execute MediaPIG
MediaPIG Category Overview
Categories store content.
Caetgories can have one to many source folders. A source folder is a parent folder which contains multiple sub-folders of content.
For example: You create a Category named "MY TVSHOWS"
"MY TVSHOWS" example contains 2 Parent Source Folders:
Source Folder 1 : C:\TV SHOWS\ - Example of fully localized installation, you have everything loaded onto one machine including assets.
Source Folder 2 : \\PC2\SMBSHARE\TV SHOWS - Exmple of a UNC/SMB Shared folder on another computer
Each parent source folder contains their own respective TV Series based content but collectively all of the content in both source folders now belongs to the same category.
MediaPIG supports 1 to many, ie: 1, 2, 4, 10 or any number of different SMB shares.
Collectively, all of the source folders would contain different TV Shows and as such, would all appear under the one category "MY TVSHOWS" as one large category.
Large categories are fully supported and are not really much more load than smaller categories.
You cannot mix TV Show and Movie content into the same 'Source Folder', this would not work well.
Example of what these 'source folders' would contain
You do not require to use local drive assets, localized assets is optional and in most case not desired.
You can alternatively use any number of windows SMB/UNC Pathing options such as \\Server\Share\Path or \\Server\Z$\Path etc.
Each Source Folder
C:\TV SHOWS\ contains 4 Sub-Folders with 4 different TV Shows.
C:\TV SHOWS\TVSHOW1 (1999)\
C:\TV SHOWS\TVSHOW2 (2000)\
C:\TV SHOWS\TVSHOW3 (2001)\
C:\TV SHOWS\TVSHOW4 (2023)\
Each TVSHOW# folder acts as a 'Parent' TV Show folder containing one to many SEASONS where each season # is uniquely named:
C:\TV SHOWS\SPECIALS
C:\TV SHOWS\SEASON 1\
C:\TV SHOWS\SEASON 2\
How you decide to organize your content becomes more up to you than MediaPIG
For example: You could create 5 different categories for your top favorite Movie Genres and organize it that way.
You could create "TVSHOWS", "CLASSIC TV", "CARTOONS", "ADULT CARTOONS", "MOVIES - HORROR"
You are fully in control of the name of the category, you dont even have to call it TVSHOWS if you really dont want to.
You can do whatever suits your preference, calling TVSHOWS "CouchTime" or "DadsBinge" or "Moms" or "KidsTV" is all very acceptable.
Same naming applies to Movies.
Categories are organzied folders where Movies have a unique folder per movie inside the parent category folder(s).
Movie Categories and Related Assets
Each Movie folder contains only one movie with all of its accompanying assets such as:
- Artwork : Poster, Fanart, Banner, Thumb .JPG, .GIF or .PNG image files.
- Additional artwork, logos and other .JPG, .GIF or .PNG image files.
- Actors : Actor named .JPG, .GIF or .PNG image files.
- Trailers : 1 to many Trailers with MovieName-trailer.ext naming convention.
- Sub-Titles : Strongly named .SRT subtitle files.
- .NFO Files : Movie.nfo and strongly named Movie-Name.nfo files.
- Extras : An extras folder for any non-movie related assets, video snippets, files etc.
Extra files are not imported or accessible directly within MediaPIG at this time.
TV Show Categories and Related Assets
Each TV Show folder contains only one TV Show with all of its accompanying assets such as:
- Season ### : Season folders per season. i.e.: SEASON 1, SEASON 2 etc.
Each season must have a strongly named season folder. (Case insensitive).
- Episodes : Epsisode files reside in the SEASON ### folders.
Each Episode file must be strongly named as follows:
TVSHOW - S####E#### - Episode Name.EXT
MediaPIG supports up to 9999 seasons per TV Show and 9999 episodes per season #.
MediaPIG only supports the following video formats:
".MP4",".MOV",".MKV",".M4V",".FLV",".DIVX",".AVI",".MPG",".MPEG",".WMV"
- Specials : Specials fodler per TV Show folder. Contains additional videos.
Each video in the specials folder conforms to the naming standard:
TVShow - S00E01 - SpecialName.Ext
The S00 tag indicates that the content is a specials entry.
The E01 tag indicates the sequence of the special episode, each video must have a unique special S00E#### tag.
- Artwork : Poster, Fanart, Banner, Thumb .JPG, .GIF or .PNG image files.
- Additional artwork, logos and other .JPG, .GIF or .PNG image files.
- Actors : Actor named .JPG, .GIF or .PNG image files.
- Trailers : 1 to many Trailers with MovieName-trailer.ext naming convention.
- Sub-Titles : Strongly named .SRT subtitle files.
- .NFO Files : Movie.nfo and strongly named Movie-Name.nfo files.
- Extras : An extras folder for any non-movie related assets, video snippets, files etc.
Extra files are not imported or accessible directly within MediaPIG at this time.
Section Item 4.3 - MediaPIG Install or Launch
MediaPIG Installation
The MediaPIG installation process is as simple as ensuring you have the .NET 6.0 runtime installed first.
Click the Download button anywhere on the main MediaPIG website to guide you through the high level basics.
Starting MediaPIG
Once installed starting MediaPIG can be done in multiple ways:
- Click Launch MediaPIG Client from MediaPIG homepage to launch MediaPIG and update as required.
- Click the installed MediaPIG icon on any Windows Desktop once installed.
4.4 - Configure MediaPIG account to use MediaPIG.
To configure MediaPIG accounts to use MediaPIG jump to the MediaPIG Account Section.
MediaPIG Accounts →
4.5 - Create Database
This section will guide you through the process to create a MediaPIG Database.
Requires a Running SQL Server
This section assumes you have already installed SQL Server Successfully.
Overview
This is a relatively easy process.
All you really must do is provide the SA password (OR The SA Account name) and associated password, a server name and a database name.
The system will determine if you are creating or replacing an existing database and advise as such.
Once you have successfuly continued after the first screen, all that is left is to provide the MEDIAPIG_DATAWRITER account password. This account is used by MediaPIG during normal read/write of the system during application usage and has less privileges than the SA account. This account is normally always cached by default to make using MediaPIG much easier.
Follow these database create steps
Tip
Click the first create database image below.
Use the left and right arrow buttons or keyboard to navigate between the steps until completed.
4.6 - Connection Profiles
Connection Profiles
The 'MediaPIG Database Connector' profiles define what and how MediaPIG database's will be used each time MediaPIG is started.
The connection profile used can be set to a single default profile, or multiple connection profiles may be defined.
In additiona, users may elect to force MediaPIG to automatically use the default defined connection profile each time the application starts and hide the database connection and selection window on startup. This provides a smooth child friendly startup process.
Tip
You can change databases after logged into any non-child profile account.
You can re-enable the database connection window using the Systems Option panel in MediaPIG's main chevron menu.
Connection Profile Configuration Process
MediaPIG comes without any database connection profiles defined.
Follow these steps to create or manage database connection profiles.
Example Database Connection Profile Window - One default profile was already defined:
| The above 'MediaPIG Database Connector' window illustrates a profile was already defined.
The system is also set to [x] Enable Profile Selector on Startup by default.
This option ensures that the 'MediaPIG Database Connector' window always displays when starting.
This can be useful if you are changing databases frequently. For children or individuals with disabilities it is recommended you turn this option off for their machines.
Create a new 'MediaPIG Database Connector'
Follow these steps to create or manage database connection profiles.
Step 1 - Start MediaPIG
Step 2 - At the MediaPIG Database Connector window, click the Configuration Slider.
Step 3 - On the MediaPIG Configuration panel click 'Create Profiles'
Step 4 - Configure the connection profile as illustrated.
Once the configuration is completed successfully, Click Save to return to the 'MediaPIG Configuration Panel'.
Click the X to close the 'MediaPIG Configuration' panel.
The 'MediaPIG Database Connector' panel should now list your newly created 'Connection Profile'.
The 
(star) in front of your profile name indicates the default MediaPIG Profile.
Use the Ellipsis button to the right of your profile name to edit and re-define your profile settings.
Use the Star button to the left of your profile name to select the default profile.
This is useful when you have more than one profile and want to change the default assigned profile on the current machine.
Tip
You could define only ONE profile on your children's machines and multiple profiles on other machines if desired.
This allows you to isolate different databases on different user machines for greater security.
They couldnt 'accidentally' get to any MediaPIG database with adult content if they dont have a profile connecting to it.
Connection, Profile, SQL, Network, Driver or Database Errors
MediaPIG will display the following generic error that covers all connection issues of many types.
If any issues arise while trying to automatically connect the MEDIAPIG_DATAWRITER account to MediaPIG, the system will display the above error message and automatically force the Connection Profile window to appear, even if you have it set to hide on startup. This will allow administrator users the opportunity to fix any issues and continue the logon. Once fixed, the MediaPIG client will continue to start automatically in subsequent runs.
4.7 - User Profiles
Creating User Profiles
This section will guide you through the process to create MediaPIG User Profiles.
User Profiles are stored within each database uniquely. These user profiles are the primary user separation configurations that keeps 'KIDS' 'Categories' separated from 'ADULT' or 'NON-CHILD' 'Categories'.
User Profile Configuration Process
MediaPIG databases are built with only 1 default Admin 'User Profile' by default.
Follow these steps to create or manage MediaPIG User Profiles.
Example User Profile Window - One default profile was already defined:
Bunny
4.8 - Create Categories
Section Item Text Goes Here
4.9 - Scraping Configuration
Section Item Text Goes Here
4.10 - Existing Content
Section Item Text Goes Here
4.11 - Adding New Content
Section Item Text Goes Here
4.12 - Advanced Configuration
Section Item Text Goes Here
4.13 - File Organization
Section Item Text Goes Here
4.14 - Staging Content
Section Item Text Goes Here
4.15 - Processing Content
Section Item Text Goes Here
4.16 - Scraping Content
Section Item Text Goes Here
4.17 - Additional Configuration
Installing Microsoft SQL Server Native Client Drivers
After the MediaPIG is installed, you need to locate the new MediaPIG 
shortcut on your desktop.
Right click on the shortcut, Click "Open File Location", Open the "Tools" sub-folder.
Run the sqlncli_x64.msi package to install the drivers.
No reboot required
If you do not install this package, your MediaPIG may not be able to locate and access SQL Servers.
If you have an alternate SQL Server driver package or version installed, you can always try those first there are a variety of other thirdparty drivers and native client versions that may work.
4.18 - Configuration Recap
Configuration Recap will outline the basic high-level configuation tasks for creating a manually controlled and managed system vs automatic or semi-automatically managed system.
Manual VS Automatic Scraping
Manually Controlled Scraping
vs
Automatic Scraping
Users can use either and/or both methods of Manual vs Automatic Scraping
The decision on how to scrape content for loading into MediaPIG is flexible.
Experience vs Inexperience
Users with experience and or preference for 100% control may elect to only use the manual approach.
Users with less experience and or no control preference may elect to only use the automatic approach.*
Automatic Processing Warning
Automatic Processing Warning
*Using any automatic approach comes with a certain level of risk over your files.
Using any level of automatic processing may experience filename and or directory name changes and files may be relocated within sub-folders automatically as part of the automatic renaming conventions used by MediaPIG.
Possible outcomes of automatic processing:
- The content of .NFO files or artwork may change automatically without notice.
- The directory names or filenames of content may be renamed without notice.
- Files within folders may be relocated within the assets parent folder.
- Unknown files or additional artwork or other files may be renamed, relocated or removed without notice.
Automatic Processing Responsibility
Users accept responsibilty of turning on any level of automatic processing within MediaPIG.
Users accept any and all of the outcomes of the resulting processing.
Assistance from MediaPIG after the fact is not possible, do so at your own risk.
MediaPIG does NOT alter metadata within media files
Content of actual Media files themselves will remain unchanged.
MediaPIG will never add, delete or update metadata within Media files directly or indirectly.
Manually Controlled Scraping
Configuration for a manually controlled system will require users to do the following high level tasks to get content into MediaPIG
- Setup external folders for containing processing directories
- Scrape media information/metadata, artwork and content renaming external of MediaPIG using another third party tool
- Manually move the folders that are fully processed which contain all relevant .nfo files and artwork into the appropriate MediaPIG category folder
- Manually execute the MediaPIG category reprocessing tasks to load and process categories either in whole or in part to add content to MediaPIG
Automatic Content Scraping
Configuration for a automatic system will require users to do the following high level tasks to get content into MediaPIG
- Setup all the category folders and assign them to categories within MediaPIG
- Setup MediaPIG categories with an associated PROCESSING staging folder within MediaPIG
- Enable MediaPIG category scraping options to allow MediaPIG to rename files and folders automatically
- Enable MediaPIG scraping options and define API KEYS required to scrape from various metadata services
Note: Users are response for acquiring their own personal API KEYS for use in MediaPIG
MediaPIG provides NO API KEYS for scraping any content from any service.
- When reprocessing categories, ensure you select options as needed to engage scraping or rescraping processes wihtin MediaPIG
4.2 - SQL Server Install
4.3 - MediaPIG Install
4.4 - MediaPIG Account
4.5 - Create Database
4.6 - Create Categories
4.7 - General Config
4.8 - Profile Config
4.9 - Scraping Config
4.10 - Existing Content
4.11 - New Content
4.12 - Advanced Config
4.13 - File Organization
4.14 - Staging Content
4.15 - Processing Content
4.16 - Scraping Content
4.17 - Additional Config
4.18 - Configure Recap
8.1 - Launch
Soft Launch in October 2023 - Open Beta
Focused on ensuring MediaPIG application worked at launch time.
The main goal was ensuring the update processes and user account features all function as expected.
8.2 - Quality of Life
Quality of Life Improvements
Rolled out 1st of each month
Focused on rolling out quality of life corrections, smoothing out the experiences, correcting any missing or features not functioning as expected.
The main goal is to ensure we shore up the core functionality especially configuration adjustments and so forth.
Ongoing for the life of the product beginning November 2023
8.3 - Scrapers
Scrapers Released
December 2023
First major feature release is the release of our internal scrapers aimed at providing internal scraper support.
The main goal is to ensure we provide functionality within MediaPIG to perform iMDB/TheTVDB/TheMovieDB scraping features.
Soft target for March 2024*
8.4 - Streaming
Streaming Support and UX Enhancements
November 2024
Optimistically intending to produce some form of streaming functionality to add support for Android and Mobile devices.
The release of the streaming features along with required UX Enhancements seem to fit together.
Targeting November 2024 or later
8.5 - Adding Category Types
Adding Additional Category Types
Future Features*
Adding additional category types such as Audio and Photo Albumn support is intended to extend media functional across the spectrum.
Adjusting for a quality Audio playing system requires some additional considerations and changes.
Future Features not slated for any particular timeframe or release schedule.
8.6 - Other Features
Other Features
Future Features and Other Changes or Additions TBD
To be announced as we go.
Section Item 9.1 (FAQ Category One)
What's sit amet quam eget lacinia?
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo. Nullam dictum felis eu pede mollis pretium.
How to ipsum dolor sit amet quam tortor?
Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero. Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui.
Can I bibendum sodales?
Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui.
Where arcu sed urna gravida?
Aenean et sodales nisi, vel efficitur sapien. Quisque molestie diam libero, et elementum diam mollis ac. In dignissim aliquam est eget ullamcorper. Sed id sodales tortor, eu finibus leo. Vivamus dapibus sollicitudin justo vel fermentum. Curabitur nec arcu sed urna gravida lobortis. Donec lectus est, imperdiet eu viverra viverra, ultricies nec urna.
Section Item 9.2 (FAQ Category Two)
What's sit amet quam eget lacinia?
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo. Nullam dictum felis eu pede mollis pretium.
How to ipsum dolor sit amet quam tortor?
Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero. Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui.
Can I bibendum sodales?
Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui.
Where arcu sed urna gravida?
Aenean et sodales nisi, vel efficitur sapien. Quisque molestie diam libero, et elementum diam mollis ac. In dignissim aliquam est eget ullamcorper. Sed id sodales tortor, eu finibus leo. Vivamus dapibus sollicitudin justo vel fermentum. Curabitur nec arcu sed urna gravida lobortis. Donec lectus est, imperdiet eu viverra viverra, ultricies nec urna.
Section Item 9.3 (FAQ Category Three)
How to dapibus sollicitudin justo vel fermentum?
Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero. Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui.
How long bibendum sodales?
Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui.
Where dapibus sollicitudin?
Aenean et sodales nisi, vel efficitur sapien. Quisque molestie diam libero, et elementum diam mollis ac. In dignissim aliquam est eget ullamcorper. Sed id sodales tortor, eu finibus leo. Vivamus dapibus sollicitudin justo vel fermentum. Curabitur nec arcu sed urna gravida lobortis. Donec lectus est, imperdiet eu viverra viverra, ultricies nec urna.
