Serious bug in internal resampler
-
- KVRist
- 256 posts since 3 May, 2009
Hi, i was it noted before in previous releases (8.6.9) and is still there in the last version of Mulab
Some samples at any sample rate diferent from the sr proyect so Mulab needs to resample
i leave the proyect for reproduce the issue.
And, another one.
the new rack created doesn't route to rack channel, yes, i'm using a custom template.
the same issue with the metronome that i posted before.
Some samples at any sample rate diferent from the sr proyect so Mulab needs to resample
i leave the proyect for reproduce the issue.
And, another one.
the new rack created doesn't route to rack channel, yes, i'm using a custom template.
the same issue with the metronome that i posted before.
You do not have the required permissions to view the files attached to this post.
-
dreammachine_nl dreammachine_nl https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=30537
- KVRist
- 60 posts since 23 Jun, 2004
Hi Jo,
About his first remark: a while ago I noticed something about these conversions too. Today I've spend some more time figuring this out; it's not about sample rate actually but about bit depth.
Loading a wave file in 8PCM/16PCM/24PCM/32Float-bit (at any sample rate) to a 'Sample' (that is Audio Sequence, Pitched Sample or Sliced Multi-Sample) works fine (tested on Mulab 8.6.20 internal sample rate 48k).
Loading a wave file 16PCM or 32Float at any sample rate to an 'Audio Stream' works fine. A 'Muwave' file is created in that same directory (correctly converted to the internal sample rate of MuLab at that moment).
Loading a wave file in any other bit-depth to an 'Audio Stream' will result in an wrongly converted Muwave file and its playback via the composer will sound bad.
Regards, TDM
About his first remark: a while ago I noticed something about these conversions too. Today I've spend some more time figuring this out; it's not about sample rate actually but about bit depth.
Loading a wave file in 8PCM/16PCM/24PCM/32Float-bit (at any sample rate) to a 'Sample' (that is Audio Sequence, Pitched Sample or Sliced Multi-Sample) works fine (tested on Mulab 8.6.20 internal sample rate 48k).
Loading a wave file 16PCM or 32Float at any sample rate to an 'Audio Stream' works fine. A 'Muwave' file is created in that same directory (correctly converted to the internal sample rate of MuLab at that moment).
Loading a wave file in any other bit-depth to an 'Audio Stream' will result in an wrongly converted Muwave file and its playback via the composer will sound bad.
Regards, TDM
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Please elaborate and also list the steps to reproduce the issue. Thx.FabBad wrote: Sun Sep 20, 2020 9:44 pm And, another one.
the new rack created doesn't route to rack channel, yes, i'm using a custom template.
the same issue with the metronome that i posted before.
-
- KVRist
- Topic Starter
- 256 posts since 3 May, 2009
My bad at typing quick, sorry.
The thing is, when in a custom template from scratch, i expected to the new racks will route to the MASTER rack, that is, i previously created a rack and rename it with "master" then if i add new rack is supossed to route directly to master, nor soundcard output.
steps:
_empty template (trully empty)
_add new rack and rename "Master"
_add new rack and see where is its audio connected
Is a similar issue when deleted and added again the "Metronome" module, it's doesn't works, so when i going to the button and right clicked "Edit Metronome Sound" it is apears as a new one.
steps:
_in any template, delete the metronome module
_add metronome module in "add module" and connect it to hardware output
And another one!
This is not buggy thing but suggestive.
It is about the preview of samples in instruments like multisampla, waveform editor and alt+right click general.
it's seems that some routes direclty to hardware out and the others goes to the "preview" rack
So, i proposse to an option to any preview routes directly to the preview rack always.
That sample preview module whould be nice if it routes to "preview monitor"
Thanks for your time in reading this and the support to the users.
The thing is, when in a custom template from scratch, i expected to the new racks will route to the MASTER rack, that is, i previously created a rack and rename it with "master" then if i add new rack is supossed to route directly to master, nor soundcard output.
steps:
_empty template (trully empty)
_add new rack and rename "Master"
_add new rack and see where is its audio connected
Is a similar issue when deleted and added again the "Metronome" module, it's doesn't works, so when i going to the button and right clicked "Edit Metronome Sound" it is apears as a new one.
steps:
_in any template, delete the metronome module
_add metronome module in "add module" and connect it to hardware output
And another one!
This is not buggy thing but suggestive.
It is about the preview of samples in instruments like multisampla, waveform editor and alt+right click general.
it's seems that some routes direclty to hardware out and the others goes to the "preview" rack
So, i proposse to an option to any preview routes directly to the preview rack always.
That sample preview module whould be nice if it routes to "preview monitor"
Thanks for your time in reading this and the support to the users.
You do not have the required permissions to view the files attached to this post.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
When inserting a new rack (template or not) it is auto-routed to the rack that is used most as target rack. That could be the rack named "Master", but maybe not. Of course you can always change the output of a new rack.FabBad wrote: Mon Sep 21, 2020 4:28 pm The thing is, when in a custom template from scratch, i expected to the new racks will route to the MASTER rack, that is, i previously created a rack and rename it with "master" then if i add new rack is supossed to route directly to master, nor soundcard output.
Previews indeed should always go to the "Preview Monitor" rack (if any).It is about the preview of samples in instruments like multisampla, waveform editor and alt+right click general.
it's seems that some routes direclty to hardware out and the others goes to the "preview" rack
So, i proposse to an option to any preview routes directly to the preview rack always.
Thanks for reporting that inconsistent case. It will be fixed in the next update.
-
- KVRist
- Topic Starter
- 256 posts since 3 May, 2009
How? where's the option? I missing something?you can always change the output of a new rack.
You do not have the required permissions to view the files attached to this post.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
In the above example you give the first 2 racks are routed to the audio output. That's why the 3rd rack you create is also routed to the audio output, just like the other 2 racks. If most of your racks would be routed to rack X (eg Master) then the next new rack you create is also auto-routed to rack X. Of course you can always change the output of a rack by clicking its output display.
