Insert empty space in tempo mapped song working correct ?

nofish · 10-03-2012, 07:10 AM

[img]http://img690.**************/img690/696/inserttime1.png[/img]

[img]http://img528.**************/img528/69/inserttime2.png[/img]

[img]http://img585.**************/img585/175/inserttime3.png[/img]

Pic 3 is what happens when I run the action 'Insert empty space in selection, what I intuitively thought would happen is pic 2 (I did this manually). Difference is the tempo marker also getting moved to the right which results in the tempo marker not landing on a bar anymore which screws up the whole grid.

Have others here done this, thoughts ?

(in the above project: Timebase for items/...: Beats (pos., length, rate), Timebase for tempo/time sig. markers: Beats)

witti · 10-03-2012, 07:33 AM

Same is happening here. Looks like a bug !

Picture 2 is what i would expect here, too.

nofish · 10-03-2012, 07:45 AM

Thanks.
So I'm not the only one thinking this, that's good to know.

I'd suggest waiting a bit seeing if there are any different opinions/thoughts coming up and if not, fill a bug report.

witti · 10-03-2012, 08:13 AM

Maybe it's not a bug.

Inserting empty space should happen before the second time marker (67 bpm). Or any time marker, which is exactly at the point of time selection start point.

nofish · 10-03-2012, 08:17 AM

Are you saying it's technically correct then how it is currently and rather a FR for the (optional) new behaviour in pic 2 ?

(just want to make sure I understand correctly)

witti · 10-03-2012, 08:29 AM

It looks like that the new time selection length is calculated with the 67 bpm. But in my opinion this time marker should be also shifted to the right, because it is simply not belonging to the new created empty space. Sorry, my english is bad, so it's hard for me to explain.

Maybe it's just a matter of when what is happening. I mean the order.

How it should be:

-move tempo marker/items/empty space right by time selection length
-(which is) insert empty space in time selection, using prior tempo settings

I think what it now does: (i could be wrong)

-fit time selection length to tempo marker at time selection start point (or maybe tempo markers somewhere between start and end point)
-then shift the tempo marker/items/empty space by time selction length to the right

Hope anybody understands my explanation.

schwa · 10-03-2012, 08:36 AM

I'd expect to see this:

.. which although different from both your expectation and what actually happens now, is closer to your expectation.

The current behavior does need fixing when the project timebase is beats.

nofish · 10-03-2012, 08:58 AM

Personally I'm fine with this (and can follow re-thinking it), my main point was the tempo marker not landing on the full bar (when project timebase is beats), which obviously will get fixed.
Thanks schwa.

TheWhistler · 11-12-2012, 04:03 AM

Quote:

Originally Posted by schwa

I'd expect to see this:

.. which although different from both your expectation and what actually happens now, is closer to your expectation.

The current behavior does need fixing when the project timebase is beats.

When will this be fixed?

gofer · 11-12-2012, 11:08 AM

Quote:

Originally Posted by TheWhistler

When will this be fixed?

I didn't test any further, but as it looks, the next release has it fixed. This is the result I get in the current pre-release version (v4.30rc2):

That's looking alright to me. It's basically as requested in the OP rather than what Schwa said he'd expect, if I understand correctly.
I'm glad about that, as it gives the result I'd expect as well (the added tempo marker could be argued about, but I don't mind it).

TheWhistler · 11-12-2012, 11:44 PM

Quote:

Originally Posted by gofer

I didn't test any further, but as it looks, the next release has it fixed. This is the result I get in the current pre-release version (v4.30rc2):

That's looking alright to me. It's basically as requested in the OP rather than what Schwa said he'd expect, if I understand correctly.
I'm glad about that, as it gives the result I'd expect as well (the added tempo marker could be argued about, but I don't mind it).

That is promising. Thank you. I recognized there were a lots of trouble with tempo markers and signature changes lately. I thought they have fixed it yet.
But hopefully in the next release. I will give the pre-release a try.
Do you know how to install a pre safely alongside with a regular release?

mwe · 11-13-2012, 12:52 AM

Quote:

Originally Posted by TheWhistler

Do you know how to install a pre safely alongside with a regular release?

You can do a portable install to a different directory, USB drive etc. It won't have any of your customizations and the nag screen will display if you don't copy your license file. You can export your config from your production setup and import it into the portable install.

You can get 4.30rc2 here

TheWhistler · 11-13-2012, 09:35 PM

Quote:

Originally Posted by mwe

You can do a portable install to a different directory, USB drive etc. It won't have any of your customizations and the nag screen will display if you don't copy your license file. You can export your config from your production setup and import it into the portable install.

You can get 4.30rc2 here

Thank´s I´ll try that. I am a bit hesitant with pre-releases. Don´t I have to first install it regularly and then make a portable install of it?

mwe · 11-13-2012, 09:58 PM

When you launch the installer you'll see a check box for portable installation. Check that and then browse/enter the destination where you want the installer to put the files. It will install everything into a single directory so that it's self contained. Copy your license file into that directory as well if you like.

TheWhistler · 11-14-2012, 01:29 PM

Quote:

Originally Posted by gofer

I didn't test any further, but as it looks, the next release has it fixed. This is the result I get in the current pre-release version (v4.30rc2):

That's looking alright to me. It's basically as requested in the OP rather than what Schwa said he'd expect, if I understand correctly.
I'm glad about that, as it gives the result I'd expect as well (the added tempo marker could be argued about, but I don't mind it).

4.30 is already released, so no need to install rc2. But sadly, it behaves like 4.261.
When I remove 4 bars at the start with this action "item: remove content (trim) behind item" REAPER cuts the 4 bars but the tempo markers I have placed before lose their relative positions.