v6.05+dev0316 - March 16 2020

[xpander]

v6.05+dev0316 - March 16 2020

+ File copying: when making byte-for-byte copy of media, preserve file modification time [t=231551]
+ ReaVerb: regenerate impulse on the fly during slider movements, mousewheel [t=232772]
+ macOS: add prefs/general/advanced options to disable mousewheel/swipe/move throttling
# ReaControlMIDI: improve .INS file loading (better handling of whitespace/quote characters)

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

[weedboy]

+ macOS: add prefs/general/advanced options to disable mousewheel/swipe/move throttling <-- I'm not sure what this means, but this fixes unresponsive GUI on macOS for me!!! It feels just like Windows now, so responsive and smooth. Thanks you so much, devs!! You are the best.

Already tested on two different macs, el capitan, and high sierra. Both without metal.

[vanhaze]

Mmmm, curious about this too..
I see the three mouse throttle settings are enabled by default.
Have to examine yet if disabling those result in any (more) smoother GUI operations ..

[mlprod]

No WAV/INFO meta data UTF fix yet?

//M

[nofish]

Take marker disappears when resizing item (seems only when 'loop source' is enabled here).

[tvm79]

+ macOS: add prefs/general/advanced options to disable mousewheel/swipe/move throttling

Wow! Thanks so much for this! Huge difference on MacOs Mojave

[babag]

thanks for this!

+ ReaVerb: regenerate impulse on the fly during slider movements, mousewheel [t=232772]

[juliansader]

Just a reminder about the horrifying bug that was (as far as I can tell) introduced in v6.0, and which causes the REAPER-provided WDL/swell function StretchBlt to fail on OSX with Metal.

Originally Posted by Justin

I’ll look to see if it is possible, it might be extremely difficult though.

Any news about this?

[Justin]

Originally Posted by juliansader

Just a reminder about the horrifying bug that was (as far as I can tell) introduced in v6.0, and which causes the REAPER-provided WDL/swell function StretchBlt to fail on OSX with Metal.



Any news about this?

To be fair, this is not a bug -- the things you're doing with that extension are not part of the official API and _NOT_SUPPORTED_.

[Justin]

Originally Posted by mlprod

No WAV/INFO meta data UTF fix yet?

//M

Hmm can you provide more information?

[mlprod]

Originally Posted by Justin

Hmm can you provide more information?

Sure!

This...

# Metadata: support UTF-8 encoding in MP3 ID3 tags

...should be done for WAV/BWF metadata as well.

[schwa]

Originally Posted by mlprod

...should be done for WAV/BWF metadata as well.

What is not working as you expect?

[mlprod]

Originally Posted by schwa

What is not working as you expect?

Same thing as wasnt working on the MP3s before. Using non-ASCII characters like åäö will render "nonsense" outside of reaper. You know what I mean?

[Tod]

I'm having problems with controllers in the midi editor. As you can see in this video, the first pass plays correctly but the next 3 plays do not.

This is: Reaper v6.05rc2/x64

https://youtu.be/xs0aa0xKoAk

[akademie]

Originally Posted by xpander

v6.05+dev0316 - March 16 2020
...
+ File copying: when making byte-for-byte copy of media, preserve file modification time [t=231551]
...

Great.
Thank you, thank you.

[J Reverb]

i am legend
testing yjr zombie

midi ..... xxx

[juliansader]

Originally Posted by Justin

To be fair, this is not a bug -- the things you're doing with that extension are not part of the official API and _NOT_SUPPORTED_.

Some of the stuff that the ReaScriptAPI extension does -- such as window opacity -- do go beyond the official API, but StretchBlt with SRCCOPY_USEALPHACHAN is plain WDL/swell, provided natively by REAPER, so I really hope that it would be considered "supported".

[Justin]

Originally Posted by mlprod

Same thing as wasnt working on the MP3s before. Using non-ASCII characters like åäö will render "nonsense" outside of reaper. You know what I mean?

"outside of reaper" can you be more specific?

We are encoding as UTF-8, some applications may be using a different character set. There is a CSET chunk we can add, however depending on what software you're using it may or may not actually use it. I suppose we could add "encode as 7-bit ASCII" and "encode as 8-bit ASCII" options (similar to MIDI string exports).

[kapverden]

Originally Posted by Justin

"outside of reaper" can you be more specific?

We are encoding as UTF-8, some applications may be using a different character set. There is a CSET chunk we can add, however depending on what software you're using it may or may not actually use it. I suppose we could add "encode as 7-bit ASCII" and "encode as 8-bit ASCII" options (similar to MIDI string exports).

I can't speak for mlprod but i can recreate it if i render a wav with ÖÄÜå etc in the title and then open it in macOS (10.12.6) finder via spacebar / quick open.

[schwa]

Originally Posted by kapverden

I can't speak for mlprod but i can recreate it if i render a wav with ÖÄÜå etc in the title and then open it in macOS (10.12.6) finder via spacebar / quick open.

If you have a wav file with non-ascii metadata text that does display properly in that context, could you share it please?

[DanSwizer]

Justin please don`t forget about this small UI bug here) https://forum.cockos.com/showthread.php?t=232701

[kapverden]

Originally Posted by schwa

If you have a wav file with non-ascii metadata text that does display properly in that context, could you share it please?

@mlprod would need to jump in here.
I don't have my Wavelab licenser with me atm.
Afai remember Wavelab allows also non-ASCII.

[mlprod]

Originally Posted by schwa

If you have a wav file with non-ascii metadata text that does display properly in that context, could you share it please?

Sent to support at cockos via wetransfer!

[schwa]

Thanks for sending the file! I think you misunderstood though -- we are looking for an example of a file with embedded non-ascii metadata, generated by some other application, that does display properly in media playing applications.

As far as we can tell, there is a text encoding specification for mp3/id3 metadata, but not for for wav/info or wav/bext metadata. There is a RIFF CSET chunk specification that can define a text code page for the whole file, but we can't find any media reading applications that actually make use of it. So if there is any way to accomplish this, we need to find an example of a file that does display properly in some file reading applications, so we can see exactly what's encoded in the file.

[mlprod]

Originally Posted by schwa

Thanks for sending the file! I think you misunderstood though -- we are looking for an example of a file with embedded non-ascii metadata, generated by some other application, that does display properly in media playing applications.

As far as we can tell, there is a text encoding specification for mp3/id3 metadata, but not for for wav/info or wav/bext metadata. There is a RIFF CSET chunk specification that can define a text code page for the whole file, but we can't find any media reading applications that actually make use of it. So if there is any way to accomplish this, we need to find an example of a file that does display properly in some file reading applications, so we can see exactly what's encoded in the file.

Ahh gotcha. New file, same song exported FROM Sonoris sent now.

/M

[kapverden]

I tested rendering with embedded metadata.

Via the $marker wildcard the ISRC now can be read from a DDP-marker, thats great, thanks so much!

It would be great if the same would work for other fields such as artist, song name etc.
Also if it would check the timeline for an album marker, for album title / album artist etc.

But the latter would only work if a time range is rendered? Instead of a region ?

@ThomasE had some great ideas about this, afai remember.

Anyways, thanks for considering.

[clepsydrae]

Originally Posted by xpander

+ File copying: when making byte-for-byte copy of media, preserve file modification time [t=231551]

...would be awesome if it also preserved peak files that it doesn't need to regenerate, AFAICT.

[schwa]

Originally Posted by mlprod

Ahh gotcha. New file, same song exported FROM Sonoris sent now.

Thanks, mystery now solved. As least some of the playback applications that read the non-ascii metadata in that wav file properly are not looking at the INFO chunk at all, they are looking at the ID3 tag those applications also embed.

There is not a rigid specification for how to embed ID3 tags in wav files (as compared to mp3 files) so we didn't think it was widely used, but it looks like at least some applications can read it.

[svijayrathinam]

+ macOS: add prefs/general/advanced options to disable mousewheel/swipe/move throttling

This has made reaper snappier in a very big way !! Thank you so much for this.

[vanhaze]

I totally don't het this Feature...

I see in my Reaper that the 3 options are ENABLED by default.
You mean better GUI performance after you have DISABLED the 3 ?

[mlprod]

Originally Posted by schwa

Thanks, mystery now solved. As least some of the playback applications that read the non-ascii metadata in that wav file properly are not looking at the INFO chunk at all, they are looking at the ID3 tag those applications also embed.

There is not a rigid specification for how to embed ID3 tags in wav files (as compared to mp3 files) so we didn't think it was widely used, but it looks like at least some applications can read it.

Ahh ok. Are you saying that the wav I sent you had an ID3 tag?
When I import that file into reaper I get the correct song title as INFO INAM, which is how it should be I guess?

[svijayrathinam]

Originally Posted by vanhaze

I totally don't het this Feature...

I see in my Reaper that the 3 options are ENABLED by default.
You mean better GUI performance after you have DISABLED the 3 ?

Yes.. exactly. Disable the three and restart reaper. You will find zooming in and out cursor moves etc are very very snappier .

[schwa]

Originally Posted by mlprod

Ahh ok. Are you saying that the wav I sent you had an ID3 tag?
When I import that file into reaper I get the correct song title as INFO INAM, which is how it should be I guess?

Yes, it's all a bit complicated. REAPER writes and reads the INFO tags as UTF-8, but apparently that is not common. Instead most applications seem to read INFO tags as 7-bit ascii and some read them as 8-bit ascii. Some applications will ignore the INFO tag if there is an ID3 tag present, as in the last file you sent, and ID3 tags have a well-specified way to store the text encoding.

[mlprod]

Originally Posted by schwa

Yes, it's all a bit complicated. REAPER writes and reads the INFO tags as UTF-8, but apparently that is not common. Instead most applications seem to read INFO tags as 7-bit ascii and some read them as 8-bit ascii. Some applications will ignore the INFO tag if there is an ID3 tag present, as in the last file you sent, and ID3 tags have a well-specified way to store the text encoding.

I see, sounds complicated for sure. Anything you can do about this?

[mlprod]

Originally Posted by kapverden

I tested rendering with embedded metadata.

Via the $marker wildcard the ISRC now can be read from a DDP-marker, thats great, thanks so much!

May I ask how you managed to do this?
As far as I can see it just reads the first 12 characters from the marker name...

[kapverden]

Yes, sorry, my post can be misread.
It doesn't extract just the ISRC from the DDP marker.
It extracts the whole marker text.
I tested with the Sonoris ISRC Editor.

[mlprod]

@Schwa Is there anyway to incorporate some kind of new wildcard ($ddpmarker?) that will read the text string from a DDP marker, find "ISRC=" and then outputting the twelve next characters?

This would make the whole ISRC thing with ISRC tagging more useful for mastering engineers, but of course this solution is just an idea.

[kapverden]

@Schwa
there were some excellent ideas regarding the metadata by you and ThomasE in this prerelease thread:
https://forum.cockos.com/showthread....21#post2248021
posts #12, #13# and #14.

Thanks