v6.42+dev1123 - November 23 2021

[vitalker]

v6.42+dev1123 - November 23 2021

• * Includes feature branch: optimized/parallelized peak building
• * Includes feature branch: media explorer toolbar
• * Includes feature branch: media item fixed lanes
• * Includes feature branch: JSFX internals overhaul/cleanup/modernization
• * Includes feature branch: r8brain free samplerate conversion mode
• * Includes feature branch: Windows very long pathname support
• * Includes feature branch: media explorer crossfades
• * Includes feature branch: recording files wildcard support
• * Includes feature branch: video render/convert normalization
• * Includes feature branch: media item notes improvements
• * Includes feature branch: .caf media format support
• * Includes feature branch: ASWG metadata support
• + Media explorer: add optional media information box
• # Media explorer: add action to show/hide toolbar to "show" menu
• # Metadata: fix reading BWF preferred position when it is zero

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[Funkybot]

Originally Posted by vitalker

[*]+ Media explorer: add optional media information box

Thanks devs! This is exactly what I was picturing yesterday and much slicker when you may want to see the properties than a modal window. Nice update!

[o_e]

I do not want to be annoying, but the .caf import still does not work correctly here (item length is not correct)

[schwa]

Originally Posted by o_e

I do not want to be annoying, but the .caf import still does not work correctly here (item length is not correct)

There may not be anything we can do about that. That particular .caf file is aac-encoded, which REAPER cannot decode natively. REAPER passes the file off to ffpmeg, vlc, or avfoundation for decoding.

[o_e]

Originally Posted by schwa

There may not be anything we can do about that. That particular .caf file is aac-encoded, which REAPER cannot decode natively. REAPER passes the file off to ffpmeg, vlc, or avfoundation for decoding.

Thanks for the quick answer!
Does it make sense if I experiment with the video decoder priority, like this for example:

[schwa]

Originally Posted by o_e

Thanks for the quick answer!
Does it make sense if I experiment with the video decoder priority, like this for example:

You can definitely try changing the order, although you can't currently see which decoder actually handled the file. For the next build we'll add that info to the source properties dialog.

[FeedTheCat]

Maybe a bit nitpicky, but is there a reason the text here is cut off? Seems like the space is reserved for something but I can't figure out what.

[Phazma]

Originally Posted by schwa

You can definitely try changing the order, although you can't currently see which decoder actually handled the file. For the next build we'll add that info to the source properties dialog.

Wouldn't a reliable way to test this (before the next build) be putting only a single decoder into the video decoder priority box a test them all one at a time? If the file is never imported correctly it means that none of the tested decoders are able to decode the file properly.

Originally Posted by FeedTheCat

Maybe a bit nitpicky, but is there a reason the text here is cut off? Seems like the space is reserved for something but I can't figure out what.

I confirm. I thought that space might be used by the Bpm indication but it seems excessive to me for that purpose.

Btw regarding Bpm, there was a recent update to limit bpm display to 3 decimals. Would it be feasible to reduce that even more to 2 or 1 decimal? I think a higher precision is rarely needed for most music/ loops and if it is needed we still see the full Bpm value at the bottom of the MX.

[blumpy]

Not sure if this should be a feature request/build request, but perhaps render normalization and limiting should be added to subproject renders?

[Phazma]

Originally Posted by vitalker

[*]+ Media explorer: add optional media information box

Small graphical nitpick: the height doesn't equal that of the preview window which looks a bit odd.



Also, I would argue, that the media information box should have the same width as the MX preview area at minimum MX width.

Originally Posted by vitalker

[*]# Media explorer: add action to show/hide toolbar to "show" menu

Great, that helps to toggle its visibility rather quickly.

Btw as you have moved 'Start on Bar' and 'Autoplay' to the MX toolbar and that seems to be a definitive decision, would you consider moving tempo match there too?

That would allow to put the pitch and rate controls in line with the transport controls even at minimum MX width and make this area of the MX more compact, which again would allow a little more space for the file list. Here a mockup showing this at minimum MX width:



Looks also much more tidy, in my opinion.

[MonkeyBars]

• razor selection still overlaps add media lane bar which is confusing
• add media lane bar doesn't register/add lanes when drag-copying razor area

[FeedTheCat]

Originally Posted by Phazma

Btw as you have moved 'Start on Bar' and 'Autoplay' to the MX toolbar and that seems to be a definitive decision, would you consider moving tempo match there too?

That would allow to put the pitch and rate controls in line with the transport controls even at minimum MX width and make this area of the MX more compact, which again would allow a little more space for the file list. Here a mockup showing this at minimum MX width:



Looks also much more tidy, in my opinion.

I like it. The half/double options seem rather situational anyway (and can be achieved by setting the rate to 0.5/2?)

[musicbynumbers]

Thanks for this!

I hope this box can become moveable and resizable

[o_e]

Originally Posted by Phazma

Wouldn't a reliable way to test this (before the next build) be putting only a single decoder into the video decoder priority box a test them all one at a time? If the file is never imported correctly it means that none of the tested decoders are able to decode the file properly.

I tried some online converters, converting .caf into .wav, the wav also have that extra space plus extra space at the start, very strange!

[schwa]

Maybe that's just how long the media is?

[Phazma]

Originally Posted by o_e

I tried some online converters, converting .caf into .wav, the wav also have that extra space plus extra space at the start, very strange!

Originally Posted by schwa

Maybe that's just how long the media is?

If I use Myriad to convert it to wav this problem does not happen.



Myriad however is a pretty advanced audio file converter and in its file analysis window it even gives an option to display Apple Loops metadata.

So my guess is that the key to decoding these files correctly is to be able to read the specific Apple Loops metadata format and if a decoder (or converter) can't do that, the information will be just interpreted as an extra bit of silence at the start or end of the file.

Btw an option in the MX to trim silence at file start below x dBFS when importing media would be a possible solution for situations like these, in the case of a file having unwanted silence at the beginning.

[schwa]

What is the exact length in seconds of the "correctly" decoded media?

[edit] it's 6.00 seconds exactly, right?

[Phazma]

Originally Posted by FeedTheCat

I like it. The half/double options seem rather situational anyway (and can be achieved by setting the rate to 0.5/2?)

Ah right, there's those options too. Yes I agree with you.
Otherwise another solution could be to have 2 buttons in the MX toolbar: one for tempo match on/off and the other one for toggling between 0.5/1.0/2.0 playback speed. Not sure if that would be overkill though.

[Phazma]

Originally Posted by schwa

What is the exact length in seconds of the "correctly" decoded media?

[edit] it's 6.00 seconds exactly, right?

Here is a screenshot of the full file analysis by Myriad. The Length is 0:06:000.

[daniellumertz]

Lanes Height seems broken when changing between tracks


Only if the item came from the track below this happens

[EvilDragon]

Originally Posted by Phazma

Small graphical nitpick: the height doesn't equal that of the preview window which looks a bit odd.

Agreed!

I would really appreciate if devs would take a bit more care about alignments and layouts. This stuff is not meaningless and improves UX.

[PhelixK]

Originally Posted by Phazma

Small graphical nitpick: the height doesn't equal that of the preview window which looks a bit odd.



Also, I would argue, that the media information box should have the same width as the MX preview area at minimum MX width.

The box appears to align with the total height, including markings and rulers if/when displayed in preview area. At least I assume this was the intention. But I agree, this doesn’t align optically and does support your suggestion to adjust the info area.

Besides this, I think it would be cool if the box could inherit color of the preview media item background (the same and reused bg color for MI on odd tracks). It should be safe for most themes if not all.
Also, some time ago I suggested an option to pick a theme color only for the preview bg. That would be even more cool and possibly enable to tame the square boxy look.

Furthermore, in terms of workflow and order of information, I will personally prefer if the info area is situated to the left side of the preview, but I’m sure there may be strong personal preferences against this

– hope it explains my idea, if not I’ll post a mock-up.

[svijayrathinam]

As we are working on media explorer, it will be very useful to have an option to insert selected file as impulse in focussed reaverb plugin.

[ovnis]

" Lanes Height seems broken when changing between tracks"

Confirmed.Broken.

[bFooz]

Originally Posted by EvilDragon

I would really appreciate if devs would take a bit more care about alignments and layouts. This stuff is not meaningless and improves UX.

+ 1

[ovnis]

Hi, It would be great to have the possibility to choose the color for this element (wave frame). If it's not possible, options between black, white and grey.

[WyattRice]

Thanks for all the media explorer additions.
Would a custom action like this be possible to add to the tool bar?

Insert Items as new takes and Move media items to source preferred position (BWF start offset) on the same track?

See older post.
https://forum.cockos.com/showpost.ph...6&postcount=14

Thanks, Wyatt

[Reflected]

Originally Posted by EvilDragon

Agreed!

I would really appreciate if devs would take a bit more care about alignments and layouts. This stuff is not meaningless and improves UX.

spot on!

[daniellumertz]

RE don't stay at envelope

[PitchSlap]

I often like to preview samples in the ME an octave up or down for creative purpose, so added toolbar actions for +12/-12, but there's no action to reset the pitch to 0.

Ideally, there could be actions for increase/decrease by 1 octave, that way it doesn't require an additional toolbar action just to change the pitch back to zero.


I tried making custom actions (increase by +1 semitone x 12 etc.), but they don't seem to work.


It would also be useful if there was a toggle action for reverse playback for the same reason (only 1 toolbar space needed).

Thanks for the consideration!