Forum Activity for @brian

ffmpeg issue revisited (nearer a solution)

Using Jamroom


a 1 gig video is going to use about 4-5 gigs of RAM, and could take many hours to convert - like 2-3 hours. Make sure you've allowed up to say 6gigs of RAM to be used per process in your php.ini (memory_limit).

ffmpeg issue revisited (nearer a solution)

Using Jamroom

I apologize - I'm not trying to make you frustrated, but if the post above about post_max_size is indicative of the 'expert' opinion, then you've got the wrong experts.

the ffmpeg bundled with Jamroom should run on your server without issue.

ffmpeg issue revisited (nearer a solution)

Using Jamroom


Probably not.

Your ffmpeg issues are unique to your server, and unfortunately we've provided all the feedback we can - figuring out the root cause of why ffmpeg does not function properly on your server is something you and your hosting provider and going to have to figure out.

I know what Lightspeed is, but have never used it. The fact you're having image issues with Apache makes me believe your server was never setup properly and is still misconfigured. Since we don't do server support here in the forum it's something you'll want to work with your hosting provider on. If they cannot help you, you should consider alternate hosting and find a hosting provider that really knows what they are doing.

ffmpeg issue revisited (nearer a solution)

Using Jamroom

post_max_size has nothing to do with running a system() call - post_max_size is used when a form is posted to enforce a max upload size.

uploaded videos not working in Firefox, possibly other browsers as well...

Using Jamroom


No - you will just need to run the "Verify Video Files" tool after upgrading - that will fix everything up.

Contact Form Spam

Using Jamroom

cleantalk.org can be integrated into Jamroom - it would just require a custom module that would take their API and use Jamroom's existing events to check the posted info via their API and then respond accordingly.

If you'd be interested in sponsoring development of the module let us know

Thanks!

Image Public URL with Size

Jamroom Developers

You are probably seeing Chrome's aggressive caching. I would recommend developing on Firefox, and just use Chrome for checking/testing - Chrome is very aggressive about caching and will continue to show you old images/pages even when those underlying images or pages have changed.

uploaded videos not working in Firefox, possibly other browsers as well...

Using Jamroom

This appears to have started with recent Chrome/Safari updates, and it looks like the "check for FLV support first then fallback to HTML5" method that is currently being used in the Video module no longer works. I've already coded a fix in for this, which is currently being tested. The "fix" is that we have to move to HTML5 first, then fallback to FLV. So how it works:

Currently:
- an FLV video file (MP4 with an FLV wrapper) is created as the "desktop" version
- a lower resolution MP4 is created for mobile only

Change in upcoming Video 2.0.0b1:
- an M4V (MP4 in M4V container) is created as the desktop version (note that M4V is used instead of MP4 so it is supported correctly in Safari/Chrome)
- an MP4 version is created for mobile (no longer low resolution)

This should fix things up for all browsers EXCEPT Opera (which appears to still have issues with a movie file being streamed from a script versus a direct video file link). This also should improve the quality of the video on mobile.

Note that Video 2.0.0b1 requires Jamroom Core 6.1.0, and after updating you will want to run the new "Verify Video Files" tool so the proper files are created. Note that it is a fairly quick process since we don't have to re-encode - we're just moving the existing converted MP4 file from an FLV container to an M4V. The amount of disk space used will also go up a little bit for new videos as the new mobile MP4 is no longer capped at 320x200.
updated by @brian: 05/30/17 02:12:49PM

Disqus Module Acting Strange?

Using Jamroom

That sounds correct - I apologize, but if different URLs had the same ID number in them, then only ONE of them is going to show the previous comments now. There's no other way to move forward with this, since the identifier that was being used was based just on the ID and not the module+ID. NEW comments on the blog should work going forward.

Let me know if that helps.

Disqus Module Acting Strange?

Using Jamroom

I've put in a small change on your site that should hopefully fix this up - let me know if that looks better.