Images demaged inside the project

infuzion · 5 Jan 2010

Dj-Grobe wrote: Some idea or suggestion or fix?

If you're not touching the graphics inside the OSM (I'm assuming you're not 🙂 ), then either SM de- & re-compresses the images, or SM has memory management issues, which is a reportable bug.

I'm glad to see you're still working on that project; it is quite inspirational to me! How has the response been though the years? Aside from the requests for multitouch 😉

Dj-Grobe · 5 Jan 2010

The project is alive !! and im working on a big update. (finish very very soon)

Im really happy to see you apreciate my work. 😍 High number of persons colaborate on this project, Malc, Oddson, Angular, You! infuzion, Acrobat , aliasant, rl, exonerate, sunsynth and probably i forgot few names, sorry.........

MonoTouchLive is a clear example of "if you can dream it you can do it jijijij" but is a perfect example about the wonderfull colaborative comunity SM have !! starting by Malc the developer. Special thanks to Malc, Angular Momentum and the brilliant mind of Oddson, the guru and wonderfull SM helper !

Whats new? Now with version 3 , my software open the door to multitple layouts on single software, not only MIDi controller for ableton. I rewritten, more of 80% of aplication , and that make positive impact in the speed of software, size and cpu usage, older bugs, etc etc.

I launch version 3 public beta 2 in few days, and with that version i enable TRAKTOR PRO GUI.

The response in all this years is wonderfull, (some bad feedback some times due older WRONG article from Peter Kirn on createdigitalmusic.com blog, where he with a big quote of ignorance or non expereince about my project,inform on that very popular blog "i stole lemur ableton layout to lemur" ....................fortunately he explain few years after...... is a mistake.....now all is ok)

Anyway 99% is really positive feedback and i have big number of happy users, the only one big barrier i have is NO MULTITOUCH ON SM...........you know! lol

Due all positive feedback, i know multitouch is a great feature for SM and really can atract new customers to SM, not only to my software. Infuzion multitouch not is only "a isolated non usefull GEEK wish from my mind", more of 4 years of experience working with this software, with touchscreen and reading ideas from my users, from hobbyist and from curious visitors of my web site teachme and open my mind in new directions! : )

About this bug, yes is some strange bug, i not touch that demaged graphics, i think is related to some trouble when save images, i see aparently demage is progresive and is increased with number of time project is saved or something like that. (can confirm this but think that happen)

aliasant · 5 Jan 2010

I reported that bug months ago. Maybe even when Malc was struggling with the 1.1.3 betas. If you re import the images its all ok again but after a while, maybe weeks or months, you will see it again.

I know Malc looked at it and had a couple of ideas but other things came in the way 🙁

Send him a reminder 🙂

Dj-Grobe · 5 Jan 2010

Thanks aliasant for confirm ! Due number of images i use, this is very ver problematic bug. I have to change high number of images with high frequency ! Hoppe malc can work on fix this.

DigitalWhiteByte · 5 Jan 2010

I confirm this issue. try to save the osm file without compression.

infuzion · 5 Jan 2010

Nice to hear the good news Dj-Grobe! I'm afraid I need to say that if you need multi-touch in the next 6 months, you'd better learn C++. :/

aliasant wrote: I reported that bug months ago. Maybe even when Malc was struggling with the 1.1.3 betas. If you re import the images its all ok again but after a while, maybe weeks or months, you will see it again.

Related bug-tracking bump.

Dj-Grobe · 5 Jan 2010

Learn c++ for rewrite all my project from scratch take more of 6 months........... I hoppe see multitouch in the next months on SM. if that not hppen is very possible i have to stop my project.........hoppe that not happen 😮

infuzion · 6 Jan 2010

You know, this reminder of a bug came in good timing; I just got off the phone with someone who will have his SM VST on 2 PCs at NAMM, & his GUI had the same image denigration issues. I told him about your findings & he was like "No wonder I was getting so many complaints [from my beta testers]!". His text was imprinted on the PNGs, & were becoming illegible. So you helped save the day!

Dj-Grobe · 6 Jan 2010

Hoppe Malc can detect asap what is the problem for fix in the next beta release.

Anyway i think this can be little hard to debug, i see the bug is absolutly random or progressive, i cant detect yet exactly how reproduce the problem when i want. I just suspect this start a little before of version 1.1.3 If somebody have more info, that can be really great and usefull for debug this little issue.

infuzion · 6 Jan 2010

Dj-Grobe wrote: Hope Malc can detect asap what is the problem for fix in the next beta release. Anyway i think this can be little hard to debug, i see the bug is absolutely random or progressive, i cant detect yet exactly how reproduce the problem when i want. I just suspect this start a little before of version 1.1.3 If somebody have more info, that can be really great and useful for debug this little issue.

When was it last that a new version made smaller compressed OSMs? Not too long ago?

Workarounds: 1) As soon as you load a new bitmap, save that module that contains the bitmap into the Toolbox. 2) Just have the bitmap re-load everytime you open the OSM. Slow & messy, but works.

malc · 6 Jan 2010

@Dj-Grobe:

Do you use images which have transparent backgrounds?

Trying my best to reproduce this. Until I can it's pretty much impossible to look into it. Even if there were things to try we'd still need a way of confirming whether they worked or not so any help you can give in finding a repeatable case would be incredibly useful.

Thanks.

@infuzion:

I don't recall the compression stuff changing. I'd be interested to know when/if the osms got smaller too 🙂

malc · 6 Jan 2010

Hold the front page, I just might have a lead. Just a lead mind, but progress at least! 🙂

Dj-Grobe · 6 Jan 2010

I realy know this is very hard to reproduce or detect why happen, aparently is random, lot of times i saved the project and reopen and all is ok, but in some moment i reopen and few images are showed demaged.

About transparent pngs, YES MALC, you are in the correct way, all my PNGs are transparent images : ) Hoppe this help !

aliasant · 6 Jan 2010

Confirming that all mine are .pngs as well. Made from Photoshop CS4.

Dj-Grobe · 6 Jan 2010

Aliasant, transparent PNGs?

aliasant · 6 Jan 2010

Dj-Grobe wrote: Aliasant, transparent PNGs?

Sorry. Yes Meant that 😉

malc · 6 Jan 2010

Cool. I can reproduce this now (by hacking the code to repeat the some of the steps it goes through during the save/load process). It's not the compression, it's a switch of pixel formats that appears to be the cause. Should be able to sort this now.

Dj-Grobe · 6 Jan 2010

Great !! Im happy to test this asap you want : )

Thanks MALC !! really older ugly bug fixed : )

aliasant · 6 Jan 2010

SWEEEEET MALC 🙂

malc · 6 Jan 2010

Just double-checking this and I found you can reproduce this easily with 1.1.5:

1. Drag a bitmap knob to an empty schematic (or add a bitmap module and load in an image which has transparent parts (transparency is required, it seems fine with fully opaque images).

2. Save the file and close it

3. Open the file again

4. Repeat steps 2 & 3 a few times (4 or more will do)

5. With the file open, zoom the schematic so you can see the image pixel detail clearer

6. Drag in a new bitmap knob to compare (or drag in a bitmap module and load in the original image again)

You should see some degradation. At normal zoom level it isn't immediately apparent but when zoomed in it is. It gets progressively worse with the number of saves and reloads. Note that it's the save, close and subsequent re-loading that causes the degradation, not simply saving on its own.

Would be interesting to have someone confirm the above just so I can be doubly sure I've got this right.

Cheers!

infuzion · 6 Jan 2010

malc wrote: Just double-checking this and I found you can reproduce this easily with 1.1.5:

I just tried with 1.1.6b3 1)with a bitmap knob 2) then my own pic that I turned the white in to a transparency & saved in Photoshop CS4 3) Then tried a JPG, max quality

I have not seen any degradation in about 5 saves.

Dj-Grobe · 7 Jan 2010

Malc , i suspect that is what happen, now you can reproduce the same i cna confirm that is what happen, i dont know know why but i can easy reproduce that with the logo of my software and with buttons or other objects need mroe number of save and load...........anyway i stay now 99% secure thsi is what happen...... And can confirm this happen only to transparent PNGs, i have few opaque png on my project and i never see that images demaged. I think you go by the correct way.

If want some test, contactme to my e-mail adress:

[email removed]

Or send private.

Best regards !

aliasant · 7 Jan 2010

Gotta confirm too.

Did it twice and I started to see it on the 7th saved version in both tests.

It is visible on the outer rim of the silverish back knob but I cant really see anything on the top knob.

I did continue this til 15th save and still couldnt see anything on the top knob. Possibly because it is a blackish knob and the artifacts are black or at least dark?

malc · 7 Jan 2010

Cool thanks. See 1.1.6 beta4 for the fix.