The forum is here for legacy reasons. No new posts will be created. User registration is disabled! If you have any questions, please email us or check https://www.adultscriptpro.com for more details!
You are not logged in.
I will add this feature. Need to either find some space for the id search or add 2 more search fields.
Its a bug. Fixed.
Ahh...your are right. I left it this way because i wanted to implement automatic category detection (its there, but its not bullet-proof) and also option for the csv to contain the category. I dont think any of the methods would work, because not all csv have category or tags for category detection, so your idea is better.
Please explain: "Maybe a check for the category with csv upload would be nice smile". Currently the CSV Importer supports category assign.
Yes. When you will upgrade from BETA3 to BETA4 you will need to run a script to convert your old thumbs to the new scheme (its already done). Basically except for
some parts of the mobile module. BETA4 is done.
This site: http://www.callejerospajeros.es/ already has the thumb scheme implemented.
Go to Admin -> Tools -> Orphan Videos. A list with videos will appear, you can edit each video (this was done right now, just for you, i will make it look better tomorrow, with video thumbs/delete/suspend option).
I just tested the video upload. It works correctly. Writing a tool now to find video orphans (videos that have no categories SET). Will update your site in a few minutes.
Will be fixed in BETA4.
I will leave this bug for BETA4 to be fixed as i'm planning to change the forum bbcode parsing code. Currently we support a few bbcode standard notations, i want to add more and also make sure nesting quotes work.
Checking (and fixing) this now. I have ssh root access to your server.
Hi,
This is a bug that appears when you order videos by longest. The bug is actually in the code that
formats seconds to timecode (if the video > 3600 seconds the bug will appear).
Video durations after fix will appear:
Seconds < 3600, 00:00
Seconds > 3600, 00:00:00
Fixed in BETA4.
This is a bug that will appear if you have more than 32000 videos. Its already fixed in the upcomming BETA4.
The videos thumbs scheme changed from:
THUMB_URL/VIDEO_ID/THUMB.jpg
to:
VIDEO_ID -> 000000000 + VIDEO_ID
EXAMPLE: VIDEO_ID = 23456
THUMB_URL/000/023/356/THUMB.jpg
This new scheme will support 999999999 videos.
Hi,
The thumb storage method will be changed (a lot of work, but its required). Currently there is only one user that reached the ext3 folder limit, so its better to change this
during the BETA to prevent this for future users. The alternative would be to use ext4 for the partition (or reiserfs, which is better for small files like video thumbs), however
not all hosting companies allow this.
Hmmm...i think its because there is no category assigned. As a temporary fix you can disable the related_category feature in admin. Will be fixed.
No worries at all...whenever you have some free time. It doesnt matter even if its finished at the end of January. Merry Christmas and A Happy New Year! Ich kann auch deutsch sprechen aber nicht so gut schreiben :-) Danke schon fur das deutsche Übersetzung :-)
Still need to do this
Is this still happening in BETA3 for you? (works on my testing box).
Thank you!
This is outdated. The premium module is finished (and was included in BETA3).
Complete CDN support needs to be added (dont know exactly in which release, however it is necesary). It will work like this
- CDN url (and ftp access) for css/js/images (not sure about thumbs though)
- CDN url (and ftp access) for videos (this is implemented as multi-server, and it will have a option for CDN).
Is CRF prodoucing good results in terms of quality for you? if not you can increase/decrease (must be integer/float) the value of -crf (you will need to edit libraries/framework/video.php for this).
Basically here's how it works.
1. CRF (this means ffmpeg choses the bitrate for you, the filesize and bitrate cannot be estimated, however this produces very good results at small filesizes). I recommend this option.
2. Auto + 1pass (this calculates the bitrate based on the video dimensions (resizing) compared to the standard of 1280x720 (720p)).
2. Auto + 2pass (this calculates the bitrate based on the video dimenstions (resizing) compared to the standard of 1280x720 (720p)). This would get you better video and audio quality (it also depends on the video dimensions). The conversion takes a long time and will use more server resources (CPU).
I tested all these options and i think its better to use CRF (all uploaded good quality videos will have good quality after conversion, filesize is good and the conversion time is smaller than 2 pass/1 pass auto).
To answer your question, you can have auto + 1pass (however i think ffmpeg knows better when calculating the bitrate with CRF).
My conversion method is based on http://rob.opendot.cl/index.php/useful- … ing-guide/ and discussion with a ffmpeg/h264 developer which recommends this. I will do some more debugging once christmas/new year is over and see why the filesize is 3*CRF with auto 1pass (i think it also depends on the uploaded video, for example for the vidz videos, the videos have a small size because the width and height (and bitrate is like 300kb/s) are low and also the audio samplerate is 22050 and audio bitrate is 38kb/s).
Hi,
Here are a few screenshots (its not even close to 10% done). Probably will change a lot. It will 100% support iphone/android and should also support almost anything (we use jquery mobile
which is a cross mobile browser framework).
You dont need to have a multimedia mobile :-), but if your visitors have multimedia mobile they will see the mobile page :-) (the normal page works in android also, however a mobile only page is better).