tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
[CWBRN-46607] 'Render bit depth' setting broken in Manchester for bounce to track.
Sorry to bring this up again but I use this feature a lot and would love to get confirmation. It is also a problem that could well go unnoticed as there are no obvious indicators without checking the rendered file. Can anyone reproduce this? 1.Create a new empty project with a bit depth setting of 16 2. Insert any soft synth (a simple instrument track will do) and record a short midi clip on the track 3. Select instrument track then choose 'bounce to track' from the tracks dropdown menu (The source and category settings do not matter in the dialogue box so just click OK) 4. Right click on the resulting bounced audio clip and choose associated audio files. It will show the file has a bit depth of 16 (as it should) 5. Now go to preferences/file/audio data, and change the render bit depth to 24 6. Repeat steps 3 and 4. The resulting file will still have a bit depth of 16 instead of 24 as it should have after changing the render setting. The same problem happens when bouncing audio tracks as well. The project will only render bounced audio at it's original bitrate setting. I have checked in X3 and it worked correctly there.
post edited by tenfoot - 2016/02/23 20:00:54
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 02:14:31
(permalink)
I can confirm this, but simply closing/re-opening the project allowed it to adopt the new setting. I don't recall ever trying to change bit depth with a project open in X3, and don't have it on this machine to try.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 05:32:13
(permalink)
brundlefly
I can confirm this, but simply closing/re-opening the project allowed it to adopt the new setting. I don't recall ever trying to change bit depth with a project open in X3, and don't have it on this machine to try.
Thanks very much brundlefly! I have noticed that sometimes a project restart caused the changes to stick, but in other projects it did not, so I will do a little more digging there. I did test it on X3 and it does change immediately in all projects without restart. EDIT: Upon further testing reopening the project or sonar did not allow the sample rate to stick in any project no matter what plugin is used. The problem persists.
post edited by tenfoot - 2016/03/10 06:27:40
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 10:57:57
(permalink)
If not inadvertent, I'd speculate the change might have something to do with the addition of plugin upsampling. Or possibly related to recent streamlining of the code to speed new track insertion, arming, etc, where a developer saw SONAR constantly checking the global render depth setting and decided it was wasted effort for 99% of users 99% of the time.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 11:04:27
(permalink)
May also be a side effect of adding Bit Depth to the "New Project" dialog.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 11:58:08
(permalink)
I thought about that New Project feature, but that's record bit depth, right?
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 12:02:23
(permalink)
Yes, you are correct. It should not affect render bit depth. Still, if I were to test when the change occurred it would be on my list of versions to test.
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 12:13:21
(permalink)
I have also discovred that the freeze synth function DOES respond immediately to any render bit depth change. Given that, surely it must be inadvertent that the bounce dialogue does not?
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 13:55:36
(permalink)
Yes, that inconsistency doesn't seem right. I would say this should be moved to Problem Reports, and you should get a CWBRN entered.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 14:08:27
(permalink)
Moved.
Also removed duplicate report in "Problem Reports"
Now all that is needed in the CWBRN.
Please add it to the subject line when available.
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/23 19:48:25
(permalink)
Thanks for your help guys.
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/24 09:40:21
(permalink)
Actually Brundlefly closing and reopening the project does not adopt the new setting in any projects I have tried. The only way to bounce with the new sample rate is via freeze synth which is a pain.
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/25 11:53:00
(permalink)
Hmmm... I can double-check later, but it definitely worked for me. Is this possibly synth-specific? I think I used TruePianos.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: 'Render bit depth' setting broken in Manchester for ALL bounce to track functions. HEL
2016/02/25 20:29:06
(permalink)
Could well be. The projects are quite large with many synths so I guess I am stuck with freeze synth or recording the synth output real time for now. Still - better than no option at all! Not holding much hope for a quick fix on this one as it doesn't seem to bother too many people.
Onward and upward! Thanks again for the help:)
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|