Hi everybody. Working on a new batch of songs and I've bumped into a glitch today. I go to audio select export select 24-bit select my folder and everything seems to render okay except for 1 Real Track. The one that's giving me a fit right now is a pedal steel patch. All the rest of thr tracks play just find
I've saved closed and reopened biab and still.
Anybody got a clue?
WSS

Steve,

It would help to know the number of the pedal steel Realtrack causing grief so that others can test it.

Regards,
Noel

Just try to another batch and three or four of the tracks won't play. Double quick in Windows nothing. Cakewalk import audio double click Nothing. Some of them work.
WSS

Actually sir it's no longer just a pedal steel oh, as a matter of fact on one of my other attempts to pedal steel actually transferred. This time I created a new tracks folder and exported the whole song again.
This time the entire mix render came through the drums came through and the piano came through. None of the guitars or anything else work in the folder.
Guitar to 2911
Bass 2915
Steel 2883
Now none of them show up. Actually they show up but they won't play.
WSS

The style itself is Dickson pop country RT 281.
I think I will try return to factory settings and see if that helps. That seems to be the advice everybody has as a first line of defense no matter what goes wrong.
WSS

HI Steve

Odd that some work and some do not.
But why are you rendering in 24 bit?
How are you listening to the rendered tracks , is the receiving player 24 bit and or the pc sound card? you say if you double click in windows is why I ask.
Don’t want to muddy the waters but just try at 16 bit. For a quick test.
Mike

I have always used 16 bit until now. All my files in Cakewalk are 24-bit and my buddy is going to engineer this upcoming CD wants me to have the tracks in 24 bit. That might be the problem and I also assume that Cakewalk Lori sample 16-bit files I will try that now. Thanks.
WSS

Hey Mike. That did the trick everything rendered and everything worked. Very strange. This is the third song I've rendered at 24-bit and the first time I've had problems. Oh well. My hearing is right between Beethoven and Pete Townshend so 16-bit is great with me! It's going to wind up on a CD sooner or later anyway. Thank you very much.
WSS

Ha ha... Steve you are not alone. I was having same issue. No sound on some 24BIT export, but 16bit worked ok. Since nobody mentioned this before, I thought that it is my PC issue. I guess not.
I wrote email yesterday to tech support and provided my SGU. So hopefully we will hear from them tomorrow here, in this thread.

Steve,

As I see it, there is nothing to be gained in rendering to 24 bit. Because BIAB are 16 bit, algorithms have to translate 16-bit information into 24 bits and that has the potential to reduce the quality of the audio.

If you load a 16 bit track into Cakewalk as part of a 24 bit project, Cakewalk should manage it fine and the quality is less likely to be compromised.

Just my tuppence worth. It's possible I'm wrong. Rest assured that if I am, others who know more than I do will correct me.

Regards,
Noel

Noel,
You are correct, it is interpolating and DAW will do the trick.
However, if it is a specific advertised "feature" that does not work, it should be fixed. No excuses.

I got very frustrated yesterday, because I thought it related to the other, EOSerror that I had with BIAB and it took quite a bit of my time to figure out what was actually going on. So instead of doing some music stuff, I was testing things.

What got me confused is that rendered (24bit) files had some "weight" (8+ meg) but no player or DAW would play them.

P.S. Going back to philosophy of "features". I rather see 5 big things done the right way, than see 50 features that need significant ironing and beta testing.

I agree 100%. Totally.

I know that you didn't interpret it this way but I'll just clarify my comments for other readers. I wasn't trying to say "don't export at 24-bit". It's just that I've found it better to leave any of these kinds of audio adjusts to the final render if possible. It usually helps with sound the final output quality.

Regards,
Noel

Noel Rusty Mike
Hey guys thanks for the input, glad I (we) get it figured out. Yes there's probably no real need to render to 24-bit. I haven't had a problem with 16 ever. Still even though it's not necessary and I won't use it again that's a feature that probably should work and there must be some reason it doesn't. It's not like I'm recording on a Commodore 64.
Cheers
WSS

HI Steve and all

Yes its true that in the end of the day you will finish up at16 anyway for the cd.
I guess the reason your cakewalk man wants 24 bit is to give him a bit more headroom for mixing (I wont go into that!).
However as has been stated by others above Cakewalk will convert incoming 16 bit to its project rate if that is set to 24, and makes a dam good job of it with floating point. (sorry here I go again)
I always have my Cakewalk projects set to 24 but normally import from Biab 16 bit
I have other music programs where I work at 24 bit like Albeton live 8, Magix music maker etc.
Also for me once I leave the midi domain I have to have 16 bit wav files to feed back to my Yamaha Clavinovia if I want to use the audio engine in there to play along to.

Importantly do what works for you and what your gear can do with less stress, BIAB has enough to do to run the complex program without having to do bit conversions at the same time. This sort of thing is best done in the DAW that is not concerned with all the musical arrangement side.
Just my thoughts
Mike

This will be fixed in the next build - (714)

Alright Andrew!

P.S. Would still prefer 24Bit source files... and if really-really need it for some reason, down-scale them to 16 bit not the other way around

If it something you see as useful, please cast your vote. The up scaling we kind of got, now time for 24bit source files:
https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=572705&Searchpage=1&Main=45008&Words=24bit&Search=true#Post572705