General support topic for Aeva Media (Latest release: July 28, 2010)

[Nao 尚]

petesky,
I didn't reply because I didn't understand your problem...
I tested and it works fine for me. No error at all when deleting a profile.

[z3us]

OK, I will take a look at it. I suppose its a non free addon, right?

[Filipina]

Hello so another post about "doesn't exist" but not this one. I am not much on understanding this so walk me through how I can fix it I have the fresh beta 5 on fresh SMF 2.0RC2

Tried to delete one of the gallery profile permissions with no albums in it and got this error 

Table 'XXXXXXXXX.smf_aeva_album' doesn't exist
File: /xxxxxxxxxxxx/penpal-community/Sources/Aeva-Admin.php
Line: 787

Thanks

[Nao 尚]

Yup. (I mostly put in there the features I really didn't want to program, but had too much pressure to make, so I asked people if they were willing to pay for them, they said yes, and most of them didn't buy Foxy! when I put the feature in it. So funny.)
Anyway-- the Imageshack thingy, I didn't want to program, so I put it in there.

[Nao 尚]

Oh... Right! I see now.

The problem was that I never deleted a profile without selecting a fallback profile. I forgot I'd implemented the ability to remove a profile without selecting a fallback *if* the source profile wasn't in use at all.
The code path was buggy indeed.
It should say aeva_albums, not aeva_album. At line 787, as you pointed out.
Same goes for you, petesky!

[tfs]

@tfs> Actually, I thought of 'another way' of making it... But it would be complicated and would hardly give excellent results.
- Load the big file
- Copy a small part (like 1/4) of it, destroy the big file
- Resize the small part, save to temp file
- Redo process until all parts are done...
- Make a big file with all resized parts.
Of course it'll give you ugly seams around the small parts. They can be avoided by resizing parts that are bigger than the part that will be used in the end. But it's really, really complicated to implement as you can imagine... Still, I don't see any other way to make a memory-efficient resize process.

What if you just could figure out how to determine if the image was too big to be processed, and then inform the user that memory limitations would forbid the image from being processed into a preview and a thumbnail?  Of course, then you'd have a bunch of images with no preview or thumbnail, and since they were too big to be processed, they'd be slow to load the full sized image.

Maybe give them the option of aborting the upload, and suggesting they reduce the image size.  With the way digital cameras are now days, it seems like they're all 8 megapixels or more.  Since I run a small family site, everyone knows me and has my email address.   I end up getting the pictures emailed to me with the explanation that they wouldn't upload.  Of course, they're all > 4000 pixels long side.  I reduce them to 1400 pixels long side using Irfanview, and they upload every time.

I have never really tried to use the ...

Max width pixels
Max height pixels
Allow resizing of large pictures

...settings.  Would the resizing of larger pictures possibly get around this issue?  Or will that be constrained within the same memory limitations as the generation of previews and thumbnails?  I had always assumed it would have the same problem, and so I've never tried using it.

[Nao 尚]

tfs,
I just tried on my server, which has neither IMagick nor MagickWand installed... And it has ImageMagick in command line! I never knew that.
I tested it via SSH, doing stuff like this:

convert huge.jpg -thumbnail 256x64 thumb.jpg

This returned a 256x64 pic from a 11000x5000 (50+ megapixels!) picture, in less than 5 seconds!
No memory issues! Woohoo!
From that point, I have no idea why you're having trouble even with IMagick when it comes to large images.
It might be interesting to add an option like, "use GD2 for everything, and ImageMagick command-line for large JPG files" (or all JPG files?)
I still don't know much about IM, frankly... And I'm a bit uncomfortable with it. But I did a simple @exec('convert -version', $test_im); and $test_im[0] returned the version number, so I could run that line and, if it's allowed by your server, I could completely bypass IMagick for simple operations like a resize.

Regarding your question on these extra features, no, "allow resizing of large pictures" will simply attempt taking the source picture and resizing it to the max width & max height (keeping the correct aspect ratio), and will then save it and check whether it's still above the maximum allowed filesize. Meaning it won't help you here.

[Nao 尚]

More crap...

http://phpthumb.sourceforge.net/

Sounds like a neat library. Fall backs to ImageMagick if too much memory is required for PHP. Has support for BMP resizing (which I always planned to add at some point...).
Downside: even compressed and without its txt files, the library is 86Kb... Argh. All of that just for resizing a pic...?!
I looked into v1.4.x, it has the basic features + ImageMagick support, and compressed to 44Kb, which is better.
Still, it's a bit overkill...

[Filipina]

Ok thanks Nao.. now after correcting the code I get this as admin when trying to delete the profile name with no albums

"Sorry, but you are not allowed to access the gallery"

Maybe I need superadmin privileges

[Nao 尚]

Hmm...?
I don't know.
Try selecting a fallback profile before deleting the other one.

[Filipina]

noper didn't work.. now I got two profiles that will not delete.

[Filipina]

does this mean anything... notice this in my browser when i am in admin

xxxxxxx/index.php?action=admin;area=aeva_perms;bf1c23da514=67463e0b48eabffbb60314d8c3985417

EDIT - I just went into phpmyadmin and deleted them for now

[tfs]

http://phpthumb.sourceforge.net/

Sounds like a neat library.

That is pretty impressive.  Plenty of demo source code too.  I don't think anyone would mind having the Aeva Media package file be 40 or 80k larger for some of that ability.  I saw that it includes watermarking as well.

[clemenzo]

Not sure if I missed anything but would it be possible to center align and use same font size for the copyright message like simpleportal and simplemachines do. It is fine to be on a new line, but I thought it would blend in better that way.

Best is to have it center aligned, above the "XHTML RSS WAP2" line, using same font type and size. Thanks! Looking forward to the final release!

[Nao 尚]

Can anyone confirm Filipina's bug?

tfs, I think when you have a package that reaches 670Kb already, 750Kb is like adding insult to injury.
I did notice that it offers watermarking, but really it's not that hard to implement the basic concept of watermarking in the first place (I think it can be done in about 15 lines?). What's hard is everything around that: offering a choice of text or picture, storing a "favorite" watermark picture for the owner, adding permissions (it needs at least two...), etc, etc... Really, implementing the watermarking itself is the easy, fun part. I don't see the point in relying on another library to do it, when it's the ONLY fun part to make.

Anyway-- have you tried ImageMagick from the command-line? I'd be interested in knowing whether it works for you too.
http://noisen.com/bigpic.jpg
This is the one mine managed to resize.... Try putting it onto your server and calling a line similar to what I put above. Just put it into an exec() call if you need to call it from PHP.

@clemenzo> What theme are you using? Are you talking about the auto-embed copyright or gallery copyright?
As for being close to release-- I think I'm ready for RC... I will add further features in future versions. Don't want to make people wait too long for a usable version, and the current one is pretty solid.

[clemenzo]

Sorry, I am using the default smf2.0 RC2 core theme and refers to the auto-embed copyright. The gallery one is fine. See the footer at my test site. It is probably due to the simpleportal mod since there are video embed on the homepage?

Thanks for looking into this!

[Arantor]

Yeah, wherever video embed is used, the copyright will be applied, IIRC.

[Nao 尚]

@clemenzo> Core is not the default theme in RC2. Curve is. And the copyright notice is optimized for integrating finely and quietly into the SMF copyright stuff. It shouldn't stand out. Unfortunately, I just had a look at RC2's footer and it seems it isn't behaving the same as in RC1. (I wrote the copyright code last year, at RC1 time.) Maybe it would warrant rewriting.

[Nao 尚]

Ah!! Silly me... I've just looked at my code, and it's a small bug. In RC2+Curve, the *first* link is the right one, and AM checks for all links except for the first one... Ah! I'll fix this in the next release. Thanks for pointing it out.

This is how it looks like after fixing it. Exactly how I designed it to be
Will be in rev 201. Would you like to test it? Find the attached Aeva-Embed.php and put it into your Sources folder. Please tell me if it works.

[MultiformeIngegno]

Tested! It works!!