Propellerhead Software has been bought

[Orbit-50]

should simply add manual overwrite (shift+space) to the stop transport button > option/keyboard control edit mode, double click on the stop button / shift+space

I gotta look into this because I'm not totally getting it from what you're showing there. Tomorrow I'll reinstall Reason and try it. Thanks.

[Orbit-50]

I just looked it up in the manual. It seems as if though even though you can assign a different key command, you still have to manually tell the the cursor to go back to the start point by hitting the shortcut each time. It won't do it automatically. I want to be able to hit the spacebar to stop the transport, then hit play, and the cursor returns to the beginning of the bar automatically, and starts playback from that point without having to manually hit any other keys to tell it to do so. Thanks for trying to help though. I really appreciate it.

[bmrzycki]

Reason lost its charm for me in the 6.5 -> 7.0 time-frame. At 6.5 and older everyone had the same devices and a big part of the community was creating interesting devices through combinators. The PHeads regularly added new devices to the rack and carefully thought about the interactions between them.

The switch to RE changed all that. The annual upgrades to the DAW contained next to no devices, nominal upgrades to workflow, and things I didn't care at all about like a flattened GUI. The devices that would normally be bundled with a major release are now separate purchases in the prop shop.

Now users don't bother making new devices, they just go buy a new almost-but-not-quite-VST in the store and even the PHead devices no longer feel as deeply integrated into the host. I can't resell them and I really dislike the time-based demoing. No two users has the same set of devices which fragments the community that used to exist around the product. Once this changed I had to view it as just another DAW in the market. When I compare it as a DAW I find it lacking on many fronts. I'd rather use tools like Bitwig and Reaper and download my instruments/FX from the entire internet instead of a curated store-front. I've also filled the "love of wiring devices" that I got from combinators with MUX.

[jinotsuh]

Even the workflow is not all that, IMHO...

i have to agree... everything in Reason is a workaround...

So it's like SONAR then

[flugel45]

Even the workflow is not all that, IMHO...

i have to agree... everything in Reason is a workaround...

So it's like SONAR then

It is for me, in that I don't have a problem with either. Both are rock solid and run like a breeze on my system.

But I'm still on Reason 8, and don't have any use for the rack extensions. I just like messing about with the patching capabilities.

[keel]

I just looked it up in the manual. It seems as if though even though you can assign a different key command, you still have to manually tell the the cursor to go back to the start point by hitting the shortcut each time. It won't do it automatically. I want to be able to hit the spacebar to stop the transport, then hit play, and the cursor returns to the beginning of the bar automatically, and starts playback from that point without having to manually hit any other keys to tell it to do so. Thanks for trying to help though. I really appreciate it.

Very same to me. I've sent them message about this and they just said it is forwared to team.. And then I sent it later again, ask'd any news about it, no answer. This thing is so annoying that it keeps me away from buying it. And of course, lack of PDC. Or long midi notes doesn't play middle of them.. So annoying to play pads always from the beggining. Jesus. Very basic things and developers ignoring them = not worth of spend your money on this company.

[Trancit]

... And of course, lack of PDC....

PDC or at least APDC is impossible to realize in a modular enviroment like Reason... this is the price you have to pay for flexibility...

[Nielzie]

Reason lost its charm for me in the 6.5 -> 7.0 time-frame.

for me too. That's exactly why I stopped upgrading from that point.

[aMUSEd]

Reason lost its charm for me in the 6.5 -> 7.0 time-frame. At 6.5 and older everyone had the same devices and a big part of the community was creating interesting devices through combinators. The PHeads regularly added new devices to the rack and carefully thought about the interactions between them.

The switch to RE changed all that. The annual upgrades to the DAW contained next to no devices, nominal upgrades to workflow, and things I didn't care at all about like a flattened GUI. The devices that would normally be bundled with a major release are now separate purchases in the prop shop.

Now users don't bother making new devices, they just go buy a new almost-but-not-quite-VST in the store and even the PHead devices no longer feel as deeply integrated into the host. I can't resell them and I really dislike the time-based demoing. No two users has the same set of devices which fragments the community that used to exist around the product. Once this changed I had to view it as just another DAW in the market. When I compare it as a DAW I find it lacking on many fronts. I'd rather use tools like Bitwig and Reaper and download my instruments/FX from the entire internet instead of a curated store-front. I've also filled the "love of wiring devices" that I got from combinators with MUX.

Good points, it did seem this might happen back when they brought out REs. For me I just use it to get access to instruments like the RMI Harmonic Synth and Parsec.

[keel]

... And of course, lack of PDC....

PDC or at least APDC is impossible to realize in a modular enviroment like Reason... this is the price you have to pay for flexibility...

Why? Gol said same on FL and Ableton guys ignored it for years too. Yet people complained more and more and they finally add it. Sure it is possible. It is needed now, especially with all those RE's.

[Trancit]

... Sure it is possible...

It is not...

FLS is about 10% (or perhaps much less) as modular as Reason and even there are many issues, if APDC is working or not...

One thing is for sure: APDC in Reason will never happen, it can never happen.
If you don´t believe me, we¨ll see and talk again in 10 years

[bungle]

Perhaps explain why it isn't possible, instead of just saying impossible, point being, it is very surprising how many things developers say are impossible until miraculously they find it possible.

[sfxsound3]

If the app can compute all instruments, fx, the UI, MIDI and audio flow, CV, automation and what not, it should be able to compute PDC as well. The app is a closed system, i.e. any delay introduced at any point is visible, it is known. I'd say automatic PDC is exactly the point of a modular environment, otherwise it becomes unworkable, even as a concept. PDC should have been implemented before the first delay-introducing device was released.

But it's not. Like so many basic features. Why? Because you have to 1. wait for it; and 2. you have to pay for it. And this is exactly the reason why I'm not using.... erm, this quite inappropriately named program.

Oh, and it sounds bad.

[EvilDragon]

Any feedback in the structure and PDC cannot work.

[bungle]

Why ?
If it is read ahead then it can compensate for that too, feedback would be an issue if it was real time but nothing in audio on computers is realtime, feedback would be a big issue for resource use at low latency, but that is not 'impossible'
It is unwise with feedback, not impossible.