Mysterious 9.5.1 & 9.5.2 bugs on MacOS X 10.7.5

[bitley]

Easier to refer to the Reason build than the version name... this is a released version and I am running it on MacOS X 10.7.5. Since I upgraded Reason on this machine I have a "slight" problem; I can't save my songs.

---

Write Problem
The Operation could not be completed because of a write problem

OK

---

Yes, super OK... I just made a great little tune and of course I never want to save it.

I have six hard drives / partitions on this machine - a 24 gb ram Xeon based 2 x 2,66 Mac Pro and not any hackintosh or anything like that - and two of them are SSDs. I ran disk control yesterday, prior to starting this Reason session. No issues with any of the disks.

Now I have to try to bounce out my arrangement as an audio file just to not lose it forever.

[bitley]

Arrgh...

Alright, it's on that Allihoopa place for now... https://allihoopa.com/s/bIV7qgoX

[Loque]

Save the songfile in the cloud?

I am sure you tried several hard drives?

[JiggeryPokery]

I reported the same issue to PH last week. For what it's worth, I've had no response, which is baffling given that it looked to me at the time like a real showstopper bug that one would might guess could affect R10 too.

I couldn't confirm it was a Reason bug or a Windows one involving VSS (although that's what Windows was reporting an error in), but what is interesting is that you're on Mac, and in both cases there were no issues before 9.5.2.

I also posted about it on the 9.5.2 thread, and had no response there , either, and was roundly ignored.

viewtopic.php?p=353606#p353606

Doing some further reading, I am wondering if the issue could be something like a bad block on the SDD. But then, that doesn't explain why Save As wouldn't work to an entirely different drive. I'm still of the view the way Reason is locking file from the system might still be a related, i.e., trying to write a locked file to a bad block, Reason is then assuming it can't be written anywhere.

My old mate just suggested a really obvious thing to try that of course didn't occur to me at the time, but if it happens again open a new songfile ... and simply copy everything from the locked file to the new file, and try to save that.

[bitley]

Really mysterious as this should be of highest priority for them. Maybe it’s the dreaded power user bug?

[bpmorton]

On my Windows box I have been running Reason as admin for a couple of years now because it does not allow me to save files unless I'm admin. Maybe this is the same kind of problem?

[bitley]

Unfortunately not. I am admin. Loving this mac by the way. I usually use a newer one but on this I can easily connect 2 screens. I even tried tilting one of them so now that's my "reason rack" screen / perfect for text editing as well.

Anyway... I needz a new Reason fix because I can't stand my favourite app having a bug like this.

[bitley]

Reason updates ( why can't I enclose pictures on this forum? )

These are the ones available on Propellerhead's webpage:

9.5.2
9.2
9.1
8.3.2
8.1
7.1
6.5.3
5.0.1
4.0.1
3.0.4 & 3.0.5

Where are 9.5 and 9.5.1? I'd happily go back to one of those simply to start saving songs...

[bpmorton]

Unfortunately not. I am admin. Loving this mac by the way. I usually use a newer one but on this I can easily connect 2 screens. I even tried tilting one of them so now that's my "reason rack" screen / perfect for text editing as well.

Anyway... I needz a new Reason fix because I can't stand my favourite app having a bug like this.

Is 10.7.5 the latest Mac OS? My last Mac was a G5 running 10.2 I think. Anybody else with 10.7.5 having issues?

[bitley]

Ok renamed this thread to get some action here.

No 10.7.5 is pretty old but it would support Reason 9.5.x without problems.

[bitley]

propellerhead support contacted here as well, no response.

[madmacman]

Where are 9.5 and 9.5.1? I'd happily go back to one of those simply to start saving songs...

Links still work (even when removed from web page):

http://cdn.propellerheads.se/Reason9/Re ... dbanks.dmg

[bitley]

Oh thank you very much! I will see if this provides a solution for now. Lovely!

[bitley]

Result after going back to 9.5.1: Yup, working now. Will test more.

[bitley]

Hm, interesting.

Apparently I can make the error come back on 9.5.1 as well; I have made a default track which loads just fine but this is the error as far I can see. Without a default track I can save just fine. With a (custom) default track I get the "read problem" when trying to save.

[bitley]

I give up on Reason...

This occured on 9.5.1 now after successfully saving for a couple of times. All I did was changing presets and just noodling on the keyboard without recording anything. I press save just for the program to remember which preset I was playing. Suddenly I get:

Read problem | The Operation could not be completed because of a read problem | OK |

[FlowerSoldier]

Wow, that sounds super frustrating. I tried updating my mac to high sierra 10.12 for 5 hours yesterday. Ended up just giving up. I hope you get it figured out.

[stratatonic]

I give up on Reason...

This occured on 9.5.1 now after successfully saving for a couple of times. All I did was changing presets and just noodling on the keyboard without recording anything. I press save just for the program to remember which preset I was playing. Suddenly I get:

Read problem | The Operation could not be completed because of a read problem | OK |

Probably using a cracked version of Way Beyond Fairlight...

[CephaloPod]

10.7 is Lion, correct? I mean...that's a pretty old OS, released 7 years ago.

[bitley]

Right but it says Reason 9.5.x supports it and on some Mac computers it's not possible to update to anything newer.

This bug in Reason is the most severe one I have experienced since using it from 1.0 and upwards.

Totally frustrating.

[CephaloPod]

Right but it says Reason 9.5.x supports it and on some Mac computers it's not possible to update to anything newer.

This bug in Reason is the most severe one I have experienced since using it from 1.0 and upwards.

Totally frustrating.

Yeah, if the props say it's supported then they need to back their product. That said, I could see why it might take them awhile to troubleshoot it. First step: find a machine running Lion.

[jugger]

My older Macbook 2008 still runs 10.7 as it cannot be upgraded anymore since 10.8 and anything upwards requires 64-bit processor architecture which this Macbook doesn't have. However it still runs Reason very well.

Haven't used it for a while now but when I get home from work I will check if I have this save problem with 9.5.2 and will report back.

[bitley]

I've now re-installed Mac OS X 10.7 on top of itself so to speak, making it repair eventually tampered files (by other software or so as I stick to tampering with sounds myself). It seems more stable but I run 9.2.1 now as I don't dare changing anything until it feels ultra rock solid like Reason always have before. The cmd S routine all the time...

[bitley]

(By the way; 10.7 was released in 2012 so it's not ultra old imho).

[jugger]

Running 10.7.5, updated Reason to 9.5.2d21. Created several song files with multiple instruments and effects(both native and VST), also starting with a custom template song, and saving many times over after changing some presets, but haven't so far being able to reproduce the write problem.

Have to experiment some more later on..