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.
Pages: 1
Not a problem
The location is relative to the vhost's public_html directory. So to protect the /home/username/public_html/media/videos/flv folder, you would actually set the location variable to being:
<Location /media/>
...
...
...
</Location>By protecting the /media/ directory, any directory below it is automatically protected as well.
Ah, ok. I just saw that. Are you adding your code to the vhost config for the domain you are testing? The code is vhost domain specific. You will know that is is working because when you visit the real path to the domain (http://example.com/stream), you will immediate get a authentication required dialog box (see http://vscdemo2.vsharesolutions.com/flvideo/). If you do not get the authorization required message, your auth code is not in the vhost config for the site properly.
As a note, I have a test server running Arch and have it working on it just fine.
I guess the real question is are you getting a 404, a 401, or a 403 with your links?
Your config has ip limiting turned on. Are you sending the IP with your secret, file path, and hex time? Send me a copy of the PHP code that you are using to generate the paths.
I am actually the one who setup and installed this for Eri.
First, mod_auth_token is similar to, but not quite the same as mod_secdownload... especially if you are using 1.0.6 (it says that it is beta, but it is pretty much production ready). The biggest difference is that mod_auth_token has the ability to limit the URLs to the user that requested the link (by their IP address). This allows for better hotlink protection since the URL is only valid for a single user, regardless of the time.
Getting mod_auth_token setup and installed is relatively easy to do. What steps are not working for you? Also, if you would like, I can install this for you as well.
I believe that he is aware that using high profile for something higher than 480p would mean that they won't play on older devices. It's actually just a moot point really because any resolution higher than 480p would not play on those older devices anyway so it really doesn't matter which profile is used.
As for a higher resolution than 480x320, this is a personal preference. Having built a mobile mod, I would say that yes, it is definitely worth having higher resolutions than 480x320. You cannot buy a device today that isn't, at the bare minimum, qHD (940x560). In fact, every mobile device made since 2010 has the capability of playing at least 720p video (nearly all 2011+ devices can play 1080p video). Further, many of the devices coming out now (Q4 2011 and Q1 2012) devices have 720p or greater displays on the devices themselves as well. With more and more content being watched and retrieved on mobile devices, I would say that at some point in the very near future, most major video sites will want to display HD quality and resolution videos to mobile devices.
Cool. So, because this works, it also poses two problems.
This code (in baseline) cannot be used for HD videos
Without baseline, this code cannot be used with older hardware mobile devices
For the first, while baseline can be used for videos up to 480p, it is terribly inefficient when used for any videos above that. I do not own a copy of the script so I do not know exactly how it looks, but if your script allows for the settings to be changed from an admin panel, I would offer a new option that allows for users to toggle between baseline, main, and high profile... depending on what your target mobile devices are. For the second, if you want to support older devices, you will be forced to use baseline profile with videos no bigger than 480x320. If you can make these options rather than hard coding them, it will probably work better for your customers.
Hold the presses!!!!!
I found the problem! It was sitting right in front of me. Try this conversion string:
/path/to/ffmpeg -threads 4 -y -i 'PATH_TO_SOURCE_VIDEO' -r 29.97 -vcodec libx264 -acodec libfaac -ar 44100 -ab 128k -ac 2 -b 320k -s 320x240 -vpre baseline -flags +loop -cmp +chroma -partitions 0 -subq 1 -trellis 0 -refs 1 -coder 0 -me_range 16 -g 300 -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -maxrate 10M -bufsize 10M -rc_eq 'blurCplx^(1-qComp)' -qcomp 0.6 -qmin 10 -qmax 51 -qdiff 4 -level 30 -f mp4 PATH_TO_OUTPUT_VIDEOHere is what I did and here is what I found out:
This is not an OS related problem because any OS greater than Android 2.0 should be just fine. Rather, this is a hardware issue. The HTC Hero supports Baseline (max L3), but DOES NOT support any video resolution higher than 480x320. The reason why the videos you initially created with my string didn't work was because the video output was set to 640x480. I have changed it such that the videos that are encoded using this string are 320x240. Also, I have modified it such that the bitrate is smaller (due to the resolution being smaller). This code should work for him. If it does, there is a followup explanation to why this would probably need to be a one-off fix and not a mainstream change.
Also, please post what devices you are testing and what OS they are running (For example, iPhone 4S iOS 5 or Motorola Droid X Android 2.3.4, etc). The videos that were posted work on my Droid (Motorola Droid, Android 2.2), my Droid X (Motorola Droid X, Android 2.3.4), Droid 2 Global (Motorola Droid 2 Global, Android 2.3.4), iPhone 4 (Apple iPhone 4 iOS 5), iPhone 4S (Apple iPhone 4S iOS 5), iPod 3rd Generation (Apple iPod 3rd Gen iOS 5), iPad (Apple iPad iOS 5), iPad 2 (Apple iPad 2 iOS 5), HTC Evo 4G (HTC Evo 4G, Android 2.3), and Samsung Epic 4G Touch (Samsung Epic 4G Touch, Android 2.3).
Note that most of these (sans the iPod and Droid) are more recent devices. I'm curious if you are having issues playing back videos due to specific issues with your server configuration.
As a quick test, Eri, I'm going to email you a link (not sure if I can post it here as it takes you to my mod which runs on a different script). Can you go to that link with your devices and tell me if the videos play for you? If so, please post back here in this thread and let me know.
Hi,
A former customer of mine (Eri) asked me to look into this issue that he was having with the mobile side of his site. I have a mod for another script that allows for videos to be played on just about every device (that will play H.264 video). Try using the following conversion string, upload the video, and then test to see if it works. This is one of the strings that I use with my own mod:
/path/to/ffmpeg -threads 4 -y -i 'PATH_TO_SOURCE_VIDEO' -r 29.97 -vcodec libx264 -acodec libfaac -ar 44100 -ab 128k -ac 2 -b 960k -s 640x480 -vpre baseline -flags +loop -cmp +chroma -partitions 0 -subq 1 -trellis 0 -refs 1 -coder 0 -me_range 16 -g 300 -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -maxrate 10M -bufsize 10M -rc_eq 'blurCplx^(1-qComp)' -qcomp 0.6 -qmin 10 -qmax 51 -qdiff 4 -level 30 -f mp4 PATH_TO_OUTPUT_VIDEOThis code will create a video using the proper baseline codec that will have the following:
Size: 640x480
BR: 960K
AR: 128K
BC: H.264
AC: AAC
AF: 44.1 Khz
AO: Stereo 2 Channel
Note that this is just a test video that would be created. For your own site, you would probably change the size, audio, and video bit rates.
Pages: 1