Tech Support

We are working with it right now. No emails for now, emails enhancements are postponed to 3.9.3. We have this in our wishlist, but for some time later on. We still have to do things which are more critical to everyone using KVS.

Added support for ranking models and content sources by various criteria. This feature will allow you display model or content source rank (e.g. #1, #2 and etc) plus show the difference between current and previous rank. For example in model_view or content_source_view block you can use this code: Rank: #{{$data.rank}} ({{if $data.rank<$data.last_rank}}{{$data.last_rank-$data.rank}} positions up{{elseif $data.rank>$data.last_rank}}{{$data.rank-$data.last_rank}} positions down{{else}}same as before{{/if}}) For list_models or list_content_sources block the code is pretty similar, but $data should be replaced with $item: Rank: #{{$item.rank}} ({{if $item.rank<$item.last_rank}}{{$item.last_rank-$item.rank}} positions up{{elseif $item.rank>$item.last_rank}}{{$item.rank-$item.last_rank}} positions down{{else}}same as before{{/if}}) This code can show: Rank: #5 (10 positions up) The feature is configured in Settings -> Content Settings, after update the ranking will not be activated, you need to manually enable it if needed:

In all categorization (categories, models, tags, content sources) and also in channel / channel group editors we added a sidebar displaying some object info, which is not displayed inside editor itself:

We didn't promise that. We said that these features will be considered for 3.9.3, but this doesn't mean that they will be 100% added. We will see that when we come closer to 3.9.3, we still have to complete many features planned for 3.9.2. Not possible, for many billings you should set prices on billing side, not KVS. KVS cannot manage price settings for > 50% of billings. If you want to adjust prices for other billings, this is possible, but you need to adjust it manually each time you want to reduce them.

Model screenshots do not support multiple formats. In 4.0 we are planning enhancements for custom fields, which will allow more control on them, for example it will be possible to indicate that some file fileds are for images and specify the list of thumb formats for each of them. But until then it is not possible to have thumbs for model screenshots, you can show just vertical thumbs for models as for now.

In 3.9.2 it will be possible now to show video / album pages (and embed codes) for content which is still in process or processing ended up with error. Previously such content sent 404 error. In order to enable that you should change option in Settings -> Website settings: This enhancement can be extremely useful for "upload and share" sites, since users can start sharing the uploaded videos even before their processing is completed.

Yes, since these videos need to be marked with specific category (e.g. Personal videos) or channel or flag, they can be listed on separate page if needed. And based on the proposed template changes only user who is set to own such videos will be able to see them, for other users you can show a trailer or screenshot or whatever else info that this video is only for a single user. Another possible and probably better way is to create them as premium videos, like this section: http://www.kvs-demo.com/premium/ Same thing, but you don't need to create a new category / channel / flag for them.

Moved last post to the right topic: http://www.kernel-video-sharing.com/forum/forum/general-discussion/business-discussion/403-new-feature-requests-in-kvs Please note that this topic is related to 3.9.2 implementation and discussion around the features we have already reported here, not about new potential features for future releases.

Well. Sounds like possible for me. You can create a category named "Personal videos" and upload such video into that category and the important thing to make sure that user of this video is set to the user who paid for it. E.g. this user will become owner if this video. Then in video_view block template you can do a simple smarty logic to check whether this video has "Personal videos" category assigned, then simply show it only for the user who owns it. Instead of category you can use channel or admin flag, any data which can separate such kind of videos from all other videos.

There are multiple ways you can do that in KVS. The proposed best way for most users is to use admin flags to set up featured videos section. This approach can be used not only for featured videos / albums, but also for creating other similar sections when you need to manually select content that should appear in them: preview gallery on index page, contests, featured content and similar. First you need to go to Categorization -> Flags and create a new flag under videos group. You can set any title / external ID, title is only used in admin panel for you, while external ID will be used to refer to this flag when configuring list_videos block to filter only videos with such flag. Here is what we've entered: Title: Featured video External ID: flag_featured_video Admin panel: enable Use this flag as administrator's flag for content Now you can go to individual videos and set this flag in Administrator's flag field. All videos you apply to this flag will be subjects to display in featured block on your site: Finally you need to show them on index page (or other page if you need so). In order to do that go to Website UI -> Pages -> Index page and add list_videos block into desired place of template where you want to display featured videos: {{insert name="getBlock" block_id="list_videos" block_name="Featured Videos"}} After you save page changes, KVS will create a new block on this page named "Featured Videos". You can now edit settings of this block by clicking on block name in pages list: You should set up block template and configuration parameters. You can use the following block template, which will render list of videos in most KVS themes without any issue: <div id="{{$block_uid}}"> {{assign var="list_videos_title" value="Featured Videos"}} {{include file="include_list_videos_block_common.tpl"}} {{assign var="pagination_no_links" value="videos"}} {{include file="include_pagination_block_common.tpl"}} </div> For parameters you should use: items_per_page: set the number of featured videos you want to display, e.g. 12 show_with_admin_flag: here is where you configure this block to filter only videos marked with Featured flag, set flag_featured_video here to refer the flag ID you've created for this sort_by: select sorting you need Make sure you also set cache lifetime in this block settings. If content of this block is not changed often, set it to 86400 seconds, which means 24 hours. After you save this block settings you should be able to see featured videos block on your page with the videos you selected by using admin flag.

Added ability to display related search queries for the given category or tag. Previously it was only possible to display related queries for another search query. This functionality is typically used for advanced SEO keywords handling. This is done by search_results block. We added 4 parameters to hook on category ID / directory (or tag ID / directory) passed in page URL. In most cases only directories are used for tags and categories: Here is an example of 2 related search queries displayed for category named "Techno":

This is already possible with audit plugin. Audit plugin has content validation option, which can also validate missing hotlinks and embed codes (this part of validation will only work if missing embed codes return 404 error, there is no other way to check). Please note that this validation may take long time depending on your database volume. Content that have errors will be marked with invalid state and you can filter it out in admin panel: Then you can check each manually if needed, each video / album has validate option in content menu: But please also note that validation indicates also videos with missing screenshots or screenshot source files. It doesn't 100% mean that video files are missing, there can be other files missing. So if you have too many videos marked with error state, you should better check them manually to see what's exactly wrong. Videos with missing screenshots can be easily fixed by removing missing screenshots or adding new manually.

We can add this flag, no problem with that. However we will not be able to add filtering for this flag, as adding this will invalidate caching for all list_videos blocks and will generate much pain for high profile projects during next update. So we only add such fixes in major releases (e.g. 3.8.0, 3.9.0). We do not have any major release left. So we would better postpone this to 4.0 together with similar flag for VR videos. However there is a workaround you can use to display this flag in videos list if you have 4k format. You should first look into your 4k format postfix (e.g. _4k.mp4) and then in videos list template you can use this code: {{assign var="postfix4k" value="_4k.mp4"}} {{if $item.formats[$postfix4k].postfix==$postfix4k}} 4K Ultra HD {{/if}} It was possible to use this approach before for HD videos as well, but the filtering (e.g. display only HD or 4K videos) can only be possible with the flag we added in 3.9.0 for HD videos.

Starting with 3.9.2 KVS will monitor all changes in theme files (including JS and CSS files) and will keep version history for them. This is needed for security reasons as well as will allow rollback any template changes that were done incorrectly. This functionality will also keep track of changes done on filesystem, but with 1 hour delay. The new functionality is available in Website UI -> Change history section. It is a table of changes with details page, where you can see old VS new content. We didn't add visual compare utility for now to save dev time, we will probably add it in future. Meanwhile it can be used with any online text compare tools available for free.

Added support to limit video format download speed in embed codes. Like for other speed limitations this is configured in video format settings for each format individually. See this post for more info on this: http://www.kernel-video-sharing.com/forum/forum/educational-support/educational-series/34-how-to-save-bandwidth-with-kvs-tube-script Now it will also be possible to override speed limit for embed codes, while having no or higher limit directly on your site: You can use it to save some bandwidth if your videos are embedded heavily.

KVS allows embedding of your content by default. In order to disable that go to Settings -> Embed player settings and remove all video formats from display slots: Your embed codes will not be showing video player anymore. Now if you also want to redirect traffic from all other sites that used your embed codes, you can add this block of code in Embed code template: <script> if (window.top != window.self) { window.top.location = '{{$data.canonical_url}}'; } else { window.location = '{{$data.canonical_url}}'; } </script> Then all users which open other sites with your embed codes will be redirected to your videos that were embedded.

In 3.9.1 we did some GUI change in video screenshot editor, which faded-out screenshots selected for deleting. It turned out that this feature brought inconvenience to users which created many screenshots initially and then manually chose which screenshots should be kept. In order to do that you normally first click on Select all screenshots for delete option and then uncheck screenshots you want to keep. With fade-out enabled this can be inconvenient and may not allow you choose screenshots: So in 3.9.2 we added one more option to disable fade-out to make sure you can clearly see all screenshots:

By default KVS comes with local storage servers for videos and albums (if ultimate package). When you add a new storage server the first thing you should ask yourself is whether you want it to be in a new server group or in an existing server group. The difference is described in details in this article: Storage system in KVS tube script Here is short summary. New server group: You want to extend storage space. You want new content to be copied to new server, while old content should remain on old server. Existing server group: You want to load balance content traffic between multiple servers. You want to migrate existing content to a new server. NOTE: content servers for videos and albums work in exactly same way, so we will only describe that for videos. How to migrate your existing content to a new server or CDN The most common scenario is when you already have local storage and want to migrate to a remote server or CDN. In order to do that you should do the following steps: Step 1. Add a new content server into the same storage group where your old server is located. Don't worry, the new server will be added in Disabled status, so it won't affect your site users. You can find more info about adding new storage servers below. Step 2. Start content sync process for the new storage server. This process can be started in servers list in KVS admin panel. It will automatically copy all content stored in the group to a new server. NOTE: sync process will create a background task and you will be able to see its progress in the list of background tasks. Based on how many content you have, this task may take days and even weeks and it will be interrupted by processing new videos if any. If you want to manually copy content files via FTP, you can do that and skip this step. Step 3. When sync process is over, if possible verify the size of content folders on both servers to make sure they have the same size. At the same time verify that KVS is not showing any errors for the new server. There will be errors until all content is synced, but there should not be any errors afterwards. Step 4. Enable new server in storage group and disable the old one. Now your users will see content from the new server. Step 5. When you are sure there are no issues, delete old server. NOTE: KVS will stop copying new videos to the old server only after you delete it from KVS. Please make sure you remember where video files are stored on filesystem before deleting old server from KVS, see step 6 for more details. Step 6. When deleting server from KVS in step 5, KVS won't physically delete any video files there. Deleting a storage server from KVS only removes it from KVS records and doesn't affect anything on filesystem. This is done for security reasons, otherwise you could accidentally remove storage server from KVS and delete all your videos files. So the only way to delete video files from the old server (e.g. free the disk space) is to do that manually from server side. We recommend you to wait for 5-7 days after deleting old storage server from KVS so that you are 100% sure that all your site is working without any issues and all videos are playing fine. When you are sure everything is OK, you are good to delete old video files from server HDD. How to add a new content server System requirements for a content server in KVS: PHP 7.1+ No specific PHP modules required Apache and / or Nginx (recommended for better performance and content protection) NOTE: Apache is NOT strictly required for remote content server, you can have Nginx + PHP. You can add a content server in admin panel in Settings -> Storage servers. For server URL you should specify any URL that you want your content to be served from. It is a common practice to use IPs and subdomains here, as well as subfolders. It is not recommended to store content in www root folder, as this may bring some problems in future. So here is the recommended URL patterns: http://123.124.125.126/videos http://storage1.domain.com/videos http://storage2.domain.com/videos NOTE: if your site works via HTTPS, all your storage servers should also use HTTPS. This is why it is better to use subdomains here, as SSL certificates can support wildcard (*) subdomains and you can install the same certificate on all storage servers. Streaming type is an important option, which indicates the type of your storage server. If this server is external CDN provider, then you should select CDN (CDN configuration for videos and albums is a topic of another article, will not be covered here). If your server doesn't have nginx installed, then you should choose HTTP 302 redirect. This option means that KVS will redirect to video files directly without any protection. Video files which are available via direct links can be easily hotlinked by other sites and someone can be stealing your traffic. This is the common issue with wordpress and other scripts, they do not allow protecting your video files. KVS keeps this option for specific cases, but its usage is not recommended. In most cases your storage server should have nginx installed and in this case you should select nginx streaming type. The next set of options are related to server connection. KVS uses these settings to copy files to remote servers. In most cases you will need to specify FTP connection details here. The most confusing option here can be FTP folder. In order to specify it correctly you should first login to your FTP using standard FTP client and see where you come into. It can be possible that your FTP is directly configured to the needed folder, but in most cases FTP will be configured into home folder of FTP user or www root folder. Since your content will be stored somewhere in subfolder (e.g. http://storage1.domain.com/videos), you should specify RELATIVE path to this subfolder in this field. For example if your FTP is configured into www root (http://storage1.domain.com), then you need to specify: videos If your FTP is configured into user's home folder, then you will need to specify more subfolders to come to /videos: public_html/videos or www/videos or even data/domain.com/public_html/videos NOTE: each storage or conversion server in KVS should have unique folder. Do not configure different servers into the same folder on filesystem, this may result in data loss. Sometimes if you specify wrong FTP folder KVS will show error that it is not able to validate connection. However in many cases there will be no error, and the files will be copied to the wrong place and will not be available to the outside. Then after you add some videos to this server KVS will show an error on it, indicating that video files are not working from this server. Control script URL field is not editable. This field is built automatically from the URL field you specified above. It indicates where you should put KVS control script on this server, so that it is integrated with KVS. Control script serves 2 things: it provides info about server (its load and disk space) and implements protection for your content. There is a link near by to download this script and you should copy it manually to the storage server so that it is available at the displayed Control script URL. So if your storage server has this URL: http://storage1.domain.com/videos Then you should copy control script here: http://storage1.domain.com/remote_control.php You can manually run this script via browser and make sure it is working and returns "connected" word. Until this happens, you won't be able to save this server. Finally, there is Time offset field. In order to implement content protection KVS generates links which expire after some time (usually after 1 or 2 hours). In order to have this working, it is required that timezones on both servers are synced. If you don't want to configure the same timezone on your remote server, then you need to specify time offset, e.g. how many hours your storage server's timezone is behind or ahead in comparison to main server. However due to different daylight saving concepts in US and Europe it can be possible that after some time this difference will be shifted 1 hour back or forth. So the best way to ensure that remote server will not have any problem is to configure the same timezone on main server and remote server. Then you will not need to specify any time offset. Here is an example configuration for a remote storage server: Finalizing protection for nginx After the server is added, open it for editing. You may see that in server settings there is a textarea with nginx config displayed (if your Streaming type is set to nginx): You should add this piece of code into nginx config of your storage server to make sure that protected files are not available via direct links. After modifying nginx config you should restart nginx. There is no common guide on where do you find your nginx config. It depends on your server panel vendor. Most server panels do allow restarting nginx from panel GUI, but do not allow modify nginx config directly. You should figure this out with your host support. But if you do not configure this, your video files will still be available via direct links and no protection will be possible. CDN storage When adding CDN storage you should use CDN option in Streaming type field. Then you also need to put your CDN control script into /admin/cdn folder (create this folder as it doesn't exist by default), specify its name in CDN control script field and specify your secret key in Streaming key field: CDN control script is a PHP script that should be implemented by your CDN provider. This script implements content protection logic by creating temporary links to video or image files. Moreover, this script is responsible for invalidating content on CDN servers when files are replaced (modified) or deleted. NOTE: invalidation process may be very important for a tube site. Consider you have DMCA claim that requires you to delete copyrighted content. If invalidation is not working correctly, your CDN will continue to stream video files that should return 404 instead. Thus you may experience troubles with providing proof of deletion. Each CDN provider has its own API for protection and invalidation, there are no standards in this field. Therefore KVS requires that each provider implements their API and provides their CDN control script to customers for use in KVS. If no such script is provided, it will still be possible to use this CDN in KVS with default CDN control script, but no content protection or invalidation will be implemented and you will be missing these important features. CDN providers: if you are willing to implement CDN control script for your CDN, just ask customer to send you default CDN control script that can be downloaded in admin panel. This script provides a basic skeleton with all the needed functions having empty or basic implementation. If you want to use default CDN control script: Download default CDN control script and upload it to /admin/cdn folder. Specify cdnapi.php in CDN control script field. Specify any text in Streaming key field as this value is not used by default control script. Troubleshooting issues KVS will validate basic issues when you try to save server settings in admin panel. After you add server, KVS will validate it on background every 5 minutes to check if it operates successfully. Even if initially you didn't have any errors, new errors may appear later due to various factors. First, FTP connection or remote server configuration may be changed externally and some functionality will simply stop working. Also when you add a server which doesn't have any videos yet, KVS is not able to check if videos are streamed correctly or not. Only after you add some videos, this check will happen on background. All issues found on background are immediately reported to KVS start page as they all are considered CRITICAL and may indicate that your remote server is not working correctly and users are not able to see videos or photos. You should make sure to fix them ASAP. Errors from background checks are not very detailed and just indicate some set of issues. In order to get more details you should try to save server settings in admin panel. NOTE: if server reports an error and you have already fixed it, please give it 5 minutes to do re-check and verify this error is fixed. Until that, server may still show this error. This only applies for background checks on existing servers. When you save server settings in admin panel, all issues are validated right a way without any delay. If saving server in admin panel still shows validation errors, these errors are not yet fixed. Here is the list of errors you can get when saving server settings: - This connection folder is already used by another server. This issue means that you are trying to configure this server into a folder, which is already used by another storage or conversion server. You should never do this, each storage or conversion server in KVS should be configured into a separate folder on filesystem. - Unable to connect to host : post. KVS is not able to connect to the specified FTP host or port. If the entered data is valid, most probably your FTP is protected by firewall and you should make sure that your main server's IP is whitelisted. Also sometimes your FTP may be configured for using non standard FTP port, you should check this as well. - Unable to login with credentials provided. Either FTP username or password is not valid. - Put / get / chmod / delete operations failed, insufficient permissions possible. When validating server connection, KVS will try to put a test file to the server and then delete it. You will get this error if any of the mentioned operations failed, which probably indicates wrong FTP folder or FTP configuration issue. Try to log in to FTP manually using desktop FTP client and try to copy any file into the specified folder. Can you do this manually? Also this error can happen if /tmp folder on your main KVS installation does not exist or is not writable. In order to check that go to Plugins -> Audit and run installation check. It will show error for tmp folder if anything is wrong. - Control script failure. As we mentioned in this article, for remote storage servers you need to manually copy control script to make it available under the displayed Control script URL. You will get this error if KVS is not able to connect to it. Try opening control script URL in browser, do you see "connected" word printed? If you don't see it, then most probably you didn't copy control script to the mentioned location, or copied it to the wrong FTP location, or there is an issue with running PHP scripts on your storage server. If script works in browser but you still see this error, it can indicate that your main server is not able to connect to this URL due to DNS or other routing issue on your main server. You can check that by using server command line and typing the following command with your control script URL: curl -I http://storage1.domain.com/remote_control.php - Remote server time is not synchronized with primary server time. As we said already, it is recommended that PHP timezones on both servers are synced. You can get rid of this error by specifying timezone offset either positive (e.g. 2) or negative (e.g. -2). This error will show timestamps on both servers to give you clue how many hours you should specify. - This script is configured with another secret key, please update its secret key. Each remote control script has secret key hardcoded in it for protection. In some cases, specifically if you use multiple KVS installations and for each of them configure the same remote storage server, you can get this error. If you already had remote_control.php script on your storage server, then most probably it is already used by other KVS installation. If you indeed have other KVS configured with the same storage server, better contact support to make sure you don't harm another installation. If you modify secret key in remote_control.php and it turns out that this file is also used by another KVS, it will stop working there. Troubleshooting content check found errors The final validation that happens for every storage server is verifying that random videos can be played. If this check fails, you will see content check found errors issue displayed for server. You can further open content test page to see test logs, which include HTTP headers logs. Here are possible reasons: Your server doesn't have nginx installed but in KVS settings you set its streaming type as nginx. In this is true, then you need to change server's streaming type option to 302 redirect. Your nginx is not configured correctly, you should ask your host support to make sure that nginx configuration printed in KVS server settings was correctly added to nginx config for this server domain. CDN API script is not working as expected or the issue is at CDN provider's end. If your server is CDN, please open content test log for this server and send HTTP headers log to your CDN provider to describe the issue. Your Apache is configured with MultiViews option enabled, which prevents KVS from serving content correctly. In this case content test HTTP headers log will show 404 error. The requested file is missing on your server and thus returns 404 error which you can see in content test HTTP headers log. In most cases this happens because your FTP configuration has been changed externally and suddenly FTP user's home folder was changed to another one. KVS started copying new files to another location and of cause these new files are no more available under the old URL, configured in KVS server settings. You should login with FTP manually and check if its location is the same as what you have specified in server URL. If the location is different, then you should check with your host support where the correct location is and ask them to move content files from this new location to the old location and re-configure FTP user back to have home folder at the old location. For example your URL is configured as http://storage1.domain.com/videos and FTP access was configured directly into this folder. As time passed, KVS put many content into this folder but then suddenly your host support changed FTP access directly to domains www folder, e.g. this one: http://storage1.domain.com. The new files are no more copied under /videos folder, but copied under / folder instead. These new files will no more be available under http://storage1.domain.com/videos URL and KVS will report content check error.

Rating in KVS is a number from 0 to 5 due to historical reasons. Initially it was a 5-star rating where users could vote not just as "like" or "dislike", but also use other rating values. In modern themes almost everybody is using likes or dislikes. So do KVS themes. However internally the rating is still calculated as a plain number, where "like" is a 5-star vote and "dislike" is a 0-star vote. By default rating is displayed as % amount of likes using this code: Inside list block (means for each video / album / model / etc. in the list): {{assign var="rating" value="`$item.rating/5*100`"}} {{if $rating>100}}{{assign var="rating" value="100"}}{{/if}} {{$rating}}% Inside view block: {{assign var="rating" value="`$data.rating/5*100`"}} {{if $rating>100}}{{assign var="rating" value="100"}}{{/if}} {{$rating}}% If you want to change this with the number of likes and dislikes, or show them additionally to % rating, you can use this code: Inside list block (means for each video / album / model / etc. in the list): {{assign var="likes" value=0}} {{assign var="dislikes" value=0}} {{if $item.rating>0}} {{assign var="likes" value=$item.rating*$item.rating_amount/5|replace:",":"."|round}} {{assign var="dislikes" value=$item.rating_amount-$likes}} {{/if}} {{$likes}} likes and {{$dislikes}} dislikes Inside view block: {{assign var="likes" value=0}} {{assign var="dislikes" value=0}} {{if $data.rating>0}} {{assign var="likes" value=$data.rating*$data.rating_amount/5|replace:",":"."|round}} {{assign var="dislikes" value=$data.rating_amount-$likes}} {{/if}} {{$likes}} likes and {{$dislikes}} dislikes

One more set of enhancements into conversion engine added. Background task logging was adjusted to provide easy-to-read info about task processing phases and timings. This will help to understand which operations take much time and can provide hint for optimizations. For example copying files to remote storage servers may take much time and will indicate poor connection between servers. Since we are planning to add more complexity into video conversion engine in future, having this info may become extremely useful for big projects. This information will be available in Administration -> Background tasks log section for every new task processed after update: Another enhancement is designed to speed up initial video conversion for projects that have many content uploaded by users and provide videos in multiple qualities. As one can see from the previous task operations breakdown screenshot, conversion engine spent 36+19=55 seconds on creating 720p and 480p video formats, which are conditionally-optional (e.g. they are only auto-created for video source files which support their sizes). Also conversion engine spent 16+27=43 seconds to create required video formats, which are 360p and Trailer. So total time spent on processing this video is almost 2 minutes and the video will become active only after full processing is done. If your project already has a queue of 100 videos to be processed, a newly uploaded video will become active in ~200 minutes after upload, because all previously uploaded videos should be processed first. Starting from 3.9.2 you can enable half-processing for the uploaded videos, which will postpone optional formats creation and will activate videos faster, but only with required formats. Then it will add additional tasks to queue to create the remaining conditionally-optional formats. It may take actually longer due to more filecopy operations that will happen, but new videos will become available faster. The new option is located in Settings -> Content Settings area:

This is possible with HLS, which will be part of 4.0 implementation. However the current player behavior is also good. If user changes quality manually, player will remember that and next time this quality will be automatically selected for this user on all other videos.

Please use this topic to post any features you think are missing in KVS. Usually customers send them directly to our support, but if you want to post them here, you are also welcome.

Just added a set of enhancements into video formats settings, watermarking and trailer creation. Now KVS fully supports scrolling watermarks. You can upload your watermark text as image and configure it to be scrolling from right to left, or from left to right for a certain duration. One of the following watermark positions is supported: - Top of the video - Bottom of the video - Both top and bottom (random) Also you can define set of time points where you want this watermark to start scrolling in seconds and / or percents. Thus you can configure that your watermark is displayed 3 times per video, on 10th second, on 50% of the video and on 100% of the video (at the very end, KVS will automatically start showing it before the video ends). Here are the new settings, they appear only if you select scrolling positions: Here is how it scrolls on top of video (note the video is vertical, so there are empty black boxes on sides which are not parts of video): Another promised enhancement is related to trailer creation optimization and better quality. We changed the logic of trailer creation to use new ffmpeg features, which resulted in faster time and less quality loss. Also we added support for crossfade as a bonus to this enhancement. Now when you configure trailer creation you can choose either you want 1s or 2s crossfade (more options here would bring more code complexity, so we decided to keep only 2 possible scenarios + no crossfade of cause): The trailers now look more advanced and lets say more professional with that. Finally a small enhancement that was really missing in video format settings is ability to configure download file order. When you enable downloading for multiple video formats, they are typically displayed as a list in site design. Before they were displayed in random order, so now you can fully control this:

We have already replied this ticket for you. New theme version already includes access code field in signup block. For old theme versions you need to manually update template, this was described in this post: http://www.kernel-video-sharing.com/forum/forum/general-discussion/announcements/30-kvs-3-9-1-implementation?p=54#post54

After month of fighting with spam we had to put all forum posts to be approved before they can be posted.