5.0rc5 - July 7 2015 - Page 2

Fergler · 07-09-2015, 05:55 AM

Quote:

Originally Posted by Sexan

After working a while on a project in V5,this whole flow idea isn't very good in practice,constantly looking and searching for mute solo fx after any adjustment,the main problem is the flow should not happen on vertical change

Bingo, I love the concept behind it but in execution it really doesn't work at all. The V4 theme was smart in it's adjustments to size and everything was flush and aligned, always in the same quadrant of the track panel space. V5 feels unadaptive despite adaptivity being the main goal.

schwa · 07-09-2015, 06:14 AM

Quote:

Originally Posted by EnGee

Hi there,

As I understand the function of Media Explorer review when using the option "Tempo match off" is to play the Midi file at the original tempo and when you change it to "Tempo match on", it would play the midi file at host's tempo.

MIDI is always previewed at the host tempo. It's somewhat unusual for a MIDI file to have a single tempo embedded; normally if a MIDI file contains tempo information, it's in the form of a complete tempo map. You can import that tempo map with the MIDI file, but it will then become the project tempo map, which would make it pointless to preview the MIDI file using the embedded tempo map for the preview but the existing project tempo map for the existing project media.

Importing a MIDI file at a different fixed tempo from the project tempo map requires an extra step after import, selecting source properties and enabling "ignore project tempo, use ____".

We can add the feature of previewing a MIDI file at its embedded tempo if the file contains a single tempo, but that would definitely be something for after 5.0 is released.

daxliniere · 07-09-2015, 06:14 AM

I really love that 'ESC = close window' in REAPER. It doesn't work for LUA windows.
Possible tweak, please?

'Chromeless' (no titlebar) would be nice, too.

schwa · 07-09-2015, 06:19 AM

Quote:

Originally Posted by daxliniere

I really love that 'ESC = close window' in REAPER. It doesn't work for LUA windows.

If you mean ReaScript windows with a @gfx section, the script itself should handle this, by terminating itself if gfx.getchar() returns 27 which is the ASCII code for ESC.

If you mean the IDE window, ESC is used in the editor in some situations (such as canceling selection or search).

daxliniere · 07-09-2015, 06:25 AM

A really dumb (for me) thing I just discovered. If you start Render To File without stopping playback first, the resultant output file has a buffer burst at the start.

It's kinda user-error, but I wanted to report it anyway.

(Note to self, don't rush

)

daxliniere · 07-09-2015, 06:28 AM

Quote:

Originally Posted by schwa

If you mean ReaScript windows with a @gfx section, the script itself should handle this, by terminating itself if gfx.getchar() returns 27 which is the ASCII code for ESC.

Hey Schwa, thanks for the reply.
One example would be Airon's colour swatch script. So you're saying this can be incorporated into any ReaScript with graphics? That's awesome. I'll put out the word.

Justin · 07-09-2015, 07:14 AM

Quote:

Originally Posted by daxliniere

Hey Schwa, thanks for the reply.
One example would be Airon's colour swatch script. So you're saying this can be incorporated into any ReaScript with graphics? That's awesome. I'll put out the word.

Yes. Ideally any reascript that uses gfx.* should periodically call gfx.getchar(), and if that value is negative (or optionally, 27 for escape), it should stop deferring itself. Negative return value from gfx.getchar() implies that the user closed the window.

daxliniere · 07-09-2015, 07:39 AM

Thanks, Justin, I'll add that to my post.

Cheers,

Luxmaji · 07-09-2015, 09:05 AM

Quote:

Originally Posted by Fergler

Bingo, I love the concept behind it but in execution it really doesn't work at all. The V4 theme was smart in it's adjustments to size and everything was flush and aligned, always in the same quadrant of the track panel space. V5 feels unadaptive despite adaptivity being the main goal.

Agree.... I'm a pre-release lurker that visits daily to keep up with the development. I felt it time for me to install 5 over the weekend. I could not agree with you more, the theme is a step backwards and I was very disappointed in my experience with it. This is a grand opportunity for the developers to take a hold of. A 'full number' release brings about expectations, right or wrong. Why not have a theme that shines? Take that time to get it right as it is the first impression. I’m still holding out on final judgement as it is a work in progress, yet something tells me that ‘they’ don’t see it near as broken as others do. And that scares me.

L

EvilDragon · 07-09-2015, 09:15 AM

Quote:

Originally Posted by Luxmaji

yet something tells me that ‘they’ don’t see it near as broken as others do. And that scares me.

That unfortunately seems to be the case. Both WT and devs seem to see it as an improvement, when in fact it really is a step back, I feel the same. v4 default theme was much more solid feeling than v5, which is all over the place, inconsistent, and just (ironically) NOT flowing well.

When reviews officially pan Reaper again for having a non-inviting GUI, it's going to be the case of "hate to say I told you so".

Luxmaji · 07-09-2015, 09:32 AM

Quote:

Originally Posted by EvilDragon

When reviews officially pan Reaper again for having a non-inviting GUI, it's going to be the case of "hate to say I told you so".

Exactly - I genuinely care about how Reaper is perceived and a proud evangelist. Nothing would make me happier than to see it succeed far greater than it is today. With 100% confidence, it's current state will not enable that to happen. It will only add fuel to the past fires burning in the ones that have turned their backs to it. There's still hope and I'll hang on to that for the time being.

Doc Shay · 07-09-2015, 09:50 AM

Thank you Devs for fixing the Fx browser issue, really appreciate it.

EnGee · 07-09-2015, 05:32 PM

Quote:

Originally Posted by schwa

We can add the feature of previewing a MIDI file at its embedded tempo if the file contains a single tempo, but that would definitely be something for after 5.0 is released.

Thank you Schwa. The option of Tempo match off or on is in the drop down list (beside the half and double tempo which are working fine), so I thought it might be some implementation forgotten.

Glad if it will be added after the 5th release

That is very reasonable. Thanks again

dekadenz · 07-09-2015, 05:43 PM

Waves SoundShifter Graphic VST3 does not detect waveform, time, playback start & stop, which renders it broken.
Do not suggest automation because it isn't sample-precise and limited to block size.

daxliniere · 07-10-2015, 03:37 AM

My assistant just told me about a bug he's experiencing on his Mac with v4.78 (I think it's x64, waiting for him to confirm).

When he enables "Optimize for tonal content" with multiple items selected, it switches all of those items to take 1.
Works fine with only a single item selected.

schwa · 07-10-2015, 06:20 AM

Quote:

Originally Posted by daxliniere

When he enables "Optimize for tonal content" with multiple items selected, it switches all of those items to take 1.

Ouch! Probably an easy fix but I can't reproduce naively. How many items are selected on how many tracks?

daxliniere · 07-10-2015, 06:24 AM

Quote:

Originally Posted by schwa

Ouch! Probably an easy fix but I can't reproduce naively. How many items are selected on how many tracks?

Many on about 40 tracks (CTRL+A), but most won't have stretch markers.
FWIW, I've never seen that on PC and I do that particular operation probably 25 times a week.

(BTW, sorry everyone for making your browsers ultra-wide on this page. :s )