|
|
|
01-04-2016, 12:30 PM
|
#1
|
Human being with feelings
Join Date: Sep 2010
Location: Saint Paul, MN
Posts: 534
|
v5.12pre3 - January 4 2016
v5.12pre3 - January 4 2016
+ FLAC: add support for writing arbitrary bit depths between 16 and 24 bits (encoded as 24-bit)
+ Super8: improve performance with low latencies and long loops
+ VST3: always keep first input bus connected
+ VST3: improve UI feedback for preset/program selection
+ VST3: improve bus-disconnected notifications on stop/reset/channel count change
+ WavPack: add support for writing arbitrary bit depths between 16 and 24 bits (encoded as 24-bit)
__________________
Mac Studio M1 MAX / 64GB / 2TB HD / macOS Ventura 13.6.3 / RME BabyFace Pro FS / SSL UF8 + UF1 + UC1 / Roland SYSTEM 8 / Kontrol S61 mk3 / Keylab 61 mkII / Komplete 14 / Omnisphere / Keyscape / Trilian / V Collection X / UVI Falcon
|
|
|
01-04-2016, 12:49 PM
|
#2
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
+ FLAC: add support for writing arbitrary bit depths between 16 and 24 bits (encoded as 24-bit)
interesting, thanks! any info on what use this might have? Guess it can be used to optimise file reduction?
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
01-04-2016, 01:58 PM
|
#3
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
Originally Posted by musicbynumbers
+ FLAC: add support for writing arbitrary bit depths between 16 and 24 bits (encoded as 24-bit)
interesting, thanks! any info on what use this might have? Guess it can be used to optimise file reduction?
|
If you record 24 bit from most interfaces, at best the bottom few bits are going to be noise (since no real-world converter really has a noise floor that low). This noise doesn't compress well, so using for example 20-bit mode still keeps a -120dB noise floor, but often makes files 30-40% smaller than the full 24-bit.
|
|
|
01-04-2016, 02:08 PM
|
#4
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
Quote:
Originally Posted by Justin
If you record 24 bit from most interfaces, at best the bottom few bits are going to be noise (since no real-world converter really has a noise floor that low). This noise doesn't compress well, so using for example 20-bit mode still keeps a -120dB noise floor, but often makes files 30-40% smaller than the full 24-bit.
|
Brilliant! That's very useful and a lovely "touch" of genius there, nice bit of thinking!
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
01-04-2016, 03:19 PM
|
#5
|
Human being with feelings
Join Date: Jul 2006
Posts: 12,480
|
Quote:
Originally Posted by grayter1
v5.12pre3 - January 4 2016
+ FLAC: add support for writing arbitrary bit depths between 16 and 24 bits (encoded as 24-bit)
+ WavPack: add support for writing arbitrary bit depths between 16 and 24 bits (encoded as 24-bit)
|
Cool. Can you update FLAC to 1.3.1 and Wavpack to 4.75.2 too?
https://xiph.org/flac/changelog.html
http://wavpack.com/changelog.txt
|
|
|
01-04-2016, 03:53 PM
|
#6
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
Originally Posted by Dstruct
|
Hmm it's a pain in the ass unfortunately, and there aren't any significant bugs I can see that need to be addressed (the main WavPack bug i see is one that we worked-around 5 years ago anyway)... so I'll put it off for now.
|
|
|
01-04-2016, 04:07 PM
|
#7
|
Human being with feelings
Join Date: Jul 2006
Posts: 12,480
|
Ok
|
|
|
01-04-2016, 04:16 PM
|
#8
|
Human being with feelings
Join Date: Jul 2006
Posts: 12,480
|
In volume fader scaling mode (+ "Default" fader range setting) the volume envelope knob goes from -inf to -15.5dB up to 6.02dB
Can we have 0.0dB as "middle"?
|
|
|
01-04-2016, 04:24 PM
|
#9
|
Human being with feelings
Join Date: Jul 2006
Posts: 12,480
|
Also
Shouldn't volume fader scaling mode override the envelope range setting automatically too (grey it out) and follow the volume fader range setting?
|
|
|
01-04-2016, 05:19 PM
|
#10
|
Human being with feelings
Join Date: Apr 2011
Location: Canada
Posts: 454
|
Quote:
Originally Posted by Justin
If you record 24 bit from most interfaces, at best the bottom few bits are going to be noise (since no real-world converter really has a noise floor that low). This noise doesn't compress well, so using for example 20-bit mode still keeps a -120dB noise floor, but often makes files 30-40% smaller than the full 24-bit.
|
Thanks for this option. I just tried it in Wavpack and it works great Most of the time I use wavpack as my default recording format since it has low CPU overhead and ~ 50% file size reduction, but with this latest option I was able to get even more file size reduction (from ~530kbps with 24/24bit to ~390kbps with 20/24bit on my UAC-2 interface) with no perceived change in sound. BTW Justin, thanks for still supporting Wavpack, I greatly appreciate it
Oh, forgot to say that there is a small GUI bug introduced with the added wavpack bit depth option; it "pushes" the bottom "Do not include markers or regions" and the "Embed project tempo(use with care)" option too low and they are now partially cut-off. (sorry, no time for a screen cap)
Chuck
|
|
|
01-04-2016, 07:28 PM
|
#11
|
Human being with feelings
Join Date: Mar 2010
Location: Adelaide, South Australia (originally from Geelong)
Posts: 5,598
|
Quote:
Originally Posted by Justin
If you record 24 bit from most interfaces, at best the bottom few bits are going to be noise (since no real-world converter really has a noise floor that low). This noise doesn't compress well, so using for example 20-bit mode still keeps a -120dB noise floor, but often makes files 30-40% smaller than the full 24-bit.
|
Great stuff Justin! Love your work. I'm using flac almost exclusively now so this is a major update for me and I dare say many others too.
|
|
|
01-05-2016, 11:55 AM
|
#12
|
Human being with feelings
Join Date: Apr 2010
Posts: 1,247
|
Quote:
Originally Posted by Justin
If you record 24 bit from most interfaces, at best the bottom few bits are going to be noise (since no real-world converter really has a noise floor that low). This noise doesn't compress well, so using for example 20-bit mode still keeps a -120dB noise floor, but often makes files 30-40% smaller than the full 24-bit.
|
a bug report - the progress window when rendering items as a new take (24-20bit) is visible only for very short, after one file already got rendered, so now it is useless. Before you could see at least until when the conversion is happening, now it is moreover a wild guess. Very satisfied with this kind of compression. My projects are now very small in filesize. THANKS!
__________________
W10 (64) Lenovo E540 - SSD; Lenovo B590; W7 (32), Compaq 610 (2.1Ghz core 2 duo, L2 cache, 2GB RAM); DPA 4018, Schoeps MK2, Schoeps MTSC 64, Neumann mk184, AEA Ribbon 88mk, AKG SolidTUBE; Focusrite Scarlett 18i20, recording merely live acoustic music.
|
|
|
01-05-2016, 12:21 PM
|
#13
|
Human being with feelings
Join Date: May 2010
Location: Austin, TX
Posts: 791
|
# before OR removes all results
Another user found this so I'm just reporting:
Click Edit Shortcuts from the Window Screen Sets tab.
The automatically applied filter no longer works "Screenset: Load window set # OR Screenset: Save window set #"
It appears that the # symbol occurring before OR is removing all results.
Looks like the issue started sometime after 5.02pre4 and before 5.05pre13.
btw, if this is the wrong place since it's not related to this pre, just let me know where you prefer this kind of thing for future reference.
Thx
|
|
|
01-05-2016, 01:39 PM
|
#14
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
Originally Posted by lachrimae
Another user found this so I'm just reporting:
Click Edit Shortcuts from the Window Screen Sets tab.
The automatically applied filter no longer works "Screenset: Load window set # OR Screenset: Save window set #"
It appears that the # symbol occurring before OR is removing all results.
Looks like the issue started sometime after 5.02pre4 and before 5.05pre13.
btw, if this is the wrong place since it's not related to this pre, just let me know where you prefer this kind of thing for future reference.
Thx
|
Thanks, fixing
|
|
|
01-12-2016, 05:47 PM
|
#15
|
Human being with feelings
Join Date: Jun 2008
Location: Whales, UK
Posts: 6,009
|
are these changes in 5.111? or 5.12pre10 ?
i'm in some sort of wormhole where latest release isn't or is or something as stuff in latest changelogs isn't what we see above.
edit: i figured the Relase .111 was a rename of the .12 pres - obviously not, now installing latest pre from lol. hmm.
|
|
|
01-12-2016, 11:19 PM
|
#16
|
Human being with feelings
Join Date: Mar 2007
Location: Wellington, New Zealand
Posts: 2,261
|
Nah, .111 was a sneaky release to get some bug fixes out that were done in the .12 pres, now it looks like it's back to the .12 pres proper.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 10:45 AM.
|