[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4721: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3851)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4723: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3851)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4724: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3851)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4725: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3851)
New MMBforums • View topic - Issue reports

Issue reports

Upcoming mother of all image editors

Re: Issue reports

Postby Rachel » Fri Oct 11, 2013 7:52 am

Rachel
 
Posts: 1920
Joined: Fri Nov 19, 2010 3:56 pm
Location: Oak Ridge, North Carolina

Re: Issue reports

Postby JEL » Fri Oct 11, 2013 11:22 pm

DAP (AOPs):
PhotoReactor (flows, effects and scripts):
JEL
 
Posts: 294
Joined: Fri Jan 06, 2012 9:35 pm

Re: Issue reports

Postby munki » Sat Oct 12, 2013 3:50 pm

I was referring to the beep sound emitted by PR when resources are too low for proper functioning as mentioned by Rachel. This occurs when either operating on a large image file or when swapping to a new image file/flow while PR is still unloading the previous operation from memory/swap space.

You are correctly quoting Rachel's other point but mis-quoting my answer which was regarding Rachel's other point.
munki
 
Posts: 40
Joined: Tue Aug 06, 2013 8:24 pm

Re: Issue reports

Postby munki » Sat Oct 12, 2013 4:04 pm

Jel, I can't reproduce your crash problem when I try on Win8 x64 / PR 1.05. I don't use flow snapshots at all usually but when I tested just now, I seem to be able to save them before or after rendering without issue. I can save a full flow snapshot or a snapshot of a flow that is empty (no blocks inserted).

Is it an intermittent problem or every time, and is it only after have done some other work in PR? Let me know if you want to test to see if there's any way I can help.

As I mentioned to Rachel, can you not save a .flow periodically or at least just before you save a snapshot?

Personally I find the concept of flow snapshots a bit weird, there's no way I'd trust important photoshop work to be embedded in a jpeg file rather than saving a proper psd. I don't know what the obsession is here with snapshots, .flow is the goto format of PR, shapshots are just a gimmick.

Best,

-andy
munki
 
Posts: 40
Joined: Tue Aug 06, 2013 8:24 pm

Re: Issue reports

Postby Rachel » Sat Oct 12, 2013 8:42 pm

I save the snapshot in order to share the work here.
Rachel
 
Posts: 1920
Joined: Fri Nov 19, 2010 3:56 pm
Location: Oak Ridge, North Carolina

Re: Issue reports

Postby munki » Sat Oct 12, 2013 9:16 pm

Well I understand this but, when I use photoshop I might export a jpeg to show people but I keep my proper photoshop file with my work in it.

As for sharing from PR, people can just as easily share the flow file (.flow) as the flow snapshot? Or does the forum only allow jpeg files? I haven't actually tried so I don't know. This forum looks like phpBB to me so I assume posting of .flow files could be enabled easily.

People seem to be posting a jpeg of their resulting image and also a snapshot so it seems to me that you could share a jpeg of the result and a .flow file. It's two files either way so no extra work in posting.

TBH I'm mostly concerned that some people might be using snapshots to save their work long term and I think that is probably an unstable way to work due to the problems with snapshots at the moment and the fact that the flow data could be lost fairly easily if they mess with the jpeg at all. That could lead to loss of work and sadness.

Of course people should do just whatever they feel comfortable with, I just wanted people to know they have choices.

All the best,

-andy
munki
 
Posts: 40
Joined: Tue Aug 06, 2013 8:24 pm

Re: Issue reports

Postby JEL » Sat Oct 12, 2013 11:42 pm

DAP (AOPs):
PhotoReactor (flows, effects and scripts):
JEL
 
Posts: 294
Joined: Fri Jan 06, 2012 9:35 pm

Re: Issue reports

Postby munki » Sun Oct 13, 2013 10:54 am

No, doesn't crash for me.

Could you try running PR with administrator privileges? - right-click >> run as administrator. If that does help you can do it always by going into the shortcut properties and you'll find always run as administrator in the compatibility panel if I remember rightly.

Brilliant idea yes, but at present are you not building an archive of flakey jpegs that are unstable and might not load back in? Several bugs IMO including Fluff butt's. Better if Oscar embedded the flow schematic as jpegs in the flow file I think like the jpegs we find in tiff, psd or RAW files. It would be shown as a thumb in Explorer or larger in the PR browser. Proprietary format so no confusion for other apps that handle jpegs.


Anyway, I don't mean to argue with people about it, just voicing my concerns in the issues thread or suggesting workarounds for those with less IT experience.


All the best,


-andy
munki
 
Posts: 40
Joined: Tue Aug 06, 2013 8:24 pm

Re: Issue reports

Postby Rachel » Sun Oct 13, 2013 2:20 pm

Dear Andy,

As a person with less IT experience I want to say thank you. Sometimes I find myself taking the long way around and then discovering that there is a button for that! The more conversation the better. I haven't decided what is the best way for me to save flows that I create or the ones our members are so generous to share. As a flow file I have little information about what it does, imbedded in an images gives me more to go on and that is how I started to save flows, but as I go I find that the flow snapshot gives me a before and after and the actual flow so I can compare it to similar ones. Creating a Virtual effect is great is I have a significant name and icon to remind me what I am using. Easy for the first 30 but after that....
Rachel
 
Posts: 1920
Joined: Fri Nov 19, 2010 3:56 pm
Location: Oak Ridge, North Carolina

Re: Issue reports

Postby munki » Sun Oct 13, 2013 8:01 pm

Thank you Rachel, it's definitely good to share info, especially when software is very new.

It might be overkill but if you wanted to get really, really organised, maybe just for favourite flows or definite "keepers" then what I do is create a sub-folder for each type or style, say for example my watercolour sketch effect thing. Then I put the flow files inside, together with any other files like textures and copies of the images before and after that work with that style. and an VRBOX that I make. If you like you could also put a snapshot in there. In my case where I use not just PR I save my files for other software in the folder too.

The .flow files I put in there can have many versions as I work to make it better so I might end up with a bunch of files named watercolour-1.flow, watercolour-2.flow ... and I always know which is the latest as it has the bigger number at the end. If I mess up I can load an older one from before it went wrong.

Another time when I look in that folder I can find all the things I need to make that style of picture together with jpegs or pngs that show me what the style looks like. If I want to create a new, similar style I can just copy the whole folder with a different name and use all those bits to branch off on a new flow.

It might seem a bit OCD or time consuming, but stuff like this saves a lot of time at the other end when you want to find things later.

All the best,

-andy
munki
 
Posts: 40
Joined: Tue Aug 06, 2013 8:24 pm

PreviousNext

Return to Photo Reactor

Who is online

Users browsing this forum: No registered users and 1 guest