Sorry for the delay. We've been investigating this and have hopefully found the problem. We are hoping to get an update out in the next 48 hours.
Mike
Sorry for the delay. We've been investigating this and have hopefully found the problem. We are hoping to get an update out in the next 48 hours.
Mike
Hi ya. The bug has been fixed and if you purchased directly from out website there is an update available through the app. If you purchased through the App Store we are hoping they will have it approved ASAP.
It was given to Apple a while ago and we are still waiting for approval but hopefully that will be done soon.
Hopefully that will have you up and running ASAP.
Mike
Thanks for the feedback. We have identified the problem and are working on a fix to be ready for when macOS is released.
Regards
Mike
This is coming and I'm hopefully going to get some time to finish it over the next week or so. It has taken too long but is coming, I promise
Mike
The license scheme for GD has changed from a file to a license key. An email was sent to all current license holders but some didn't make it through spam filters etc.
You can get your new license key by requesting your licenses using the email used during purchase at https://71squared.com/licenses
If you have any problem drop an email to [email protected]
Mike
Hi Chad
Due to the nature of the Deep Dream engine and that it uses a Neural Network you are unlikely to get the same results each time you run the same image through the app. This is expected behaviour as the Deep Dream engine may see different patterns in different orders each time the image is run through the app.
Hope that helps.
Mike
This is unusual behaviour and not something we've come across before. Its a generic answer, but have you run First Aid on your drive using Disk Utility. Maybe there are some permissions which have been messed up. The other option is to delete Focused and re-install.
Let me know how you get on.
Mike
Hi ya
Unfortunately we've not got much out to anyone over the last few months for Deep Dreamer. It's still being worked on, primarily around the stabilising of the GPU mode and we have been experimenting with being able to teach it new images. Unfortunately this stuff just eats cycles and with only two of us that can cause things to slow down significantly.
We are planning on getting an updated release out to address the GPU issues that some people have been having. I appreciate the heads up to the info you provided. We've seen these and been using them while working on stability.
Thanks again for the feedback
Regards
Mike
Hi ya
If you can drop an email to [email protected] we'll get the issue sorted out for you.
Regards
Mike
Thanks for the feedback. It's great to hear you are enjoying the app. That's the best feedback we can get
We'll continue to monitor changes to the Deep Dream engine and work on enhancements to Deep Dreamer.
Regards
Mike
Hi ya
When using Markdown a double carriage return is needed to identify a new paragraph. If you have a number at the start of the line and perform a single carriage return then Markdown treats that as a list and increments the number.
Using a double carriage return will give you the behaviour you need.
Mike
Hi ya, that is actually proving a difficult question to answer. The size of image that works depends on a number of factors including the GPU being used and the memory available. As mentioned above we have regularly processed images on that are 4096x2048 but this can consume a huge amount of memory due to the way the sampling is done in the Google Deep Dream engine.
We have found that our users get much more consistent results using smaller images of 2048x2048 and smaller.
We will add this information to the website as it is an important piece of info.
I hope that helps.
Mike
So you'd think, but the problem is that we cannot get downloads to give us the same problem you are having. We have tried on all the machines we have and asked our beta testers as well and everyone can download the file without any problems, hence the delay as we really don't know what the problem is.
This is a pain, but if you have access to another machine, does it download on that machine or provide the same problem?
Thanks
Mike
Hi David
Can I check if you have the option to always show scroll bats switched on in System Preferences. To my knowledge this is the only situation where you will constantly see the scroll bar in white?
Thanks
Mike
Thanks for the feedback. Sprite sheets are not supported at the moment but this is at the top of our features for the next version. Currently most of the platforms that Particle Designer exports for don't support a single system with multiple emitters. For this reason you can export a stage file from PD which allows you to read in details of where multiple emitters should be placed to work together. Admittedly this is a file that would need to be read manually and then used to manually place the emitters together.
We are reviewing the different particle systems in frameworks at the moment and reaching out to see if the framework owners/maintainers would be willing to make changes to the particle systems to better support this ability.
With the ability to export to a sprite sheet, this would mean that no extra support is needed and therefore the timeline approach in PD would allow for some cool effects to then be exported to a sprite sheet. This is also on the list
We are prototyping ideas and changes at the moment for the next version. I don't have a time frame just yet but we want it to be ASAP.
Hope that helps and thanks again for the feedback.
Regards
Mike
Thanks for the heads-up. We will look into the download issue and see what is happening. I'll get back to you ASAP.
Regards
Mike
If you can drop your details such as the email address you used during purchase, name etc to [email protected] we'll help track down the license and get you up and running
Regards
Mike
Thanks. This is proving to be a difficult issue to track down but hopefully we will make progress with it soon.
Mike