| Author
|
Cubase 8 Pro
|
Dypden
Started Topics :
2
Posts :
12
Posted : Mar 8, 2016 20:30
|
I'm very interested thank you 
Quote:
|
I remember that little annoyance when working on a friend's studio using Cubase 5 recently. I know he had some work around for it, though. I can ask if you're interested 
|
|
|
|
|
TimeTraveller
IsraTrance Full Member
Started Topics :
80
Posts :
3207
Posted : Mar 27, 2016 14:34
|
I encounter first serious problems in Cubase ever. For some reason, if I load one specific of my unfinished works, there immidiately no audio output. Nothing is on solo etc. Moreover, even no signal is poping up in any fader.
I checked device settings and soundcard is still activated.
All my plug ins in these project are native Cubase 8 plug ins + Synth 1 and Bazille. I than only have samples, in 16 bit and in 24 bit - I recorded some sounds in different bitrates when I was in Goa. Don't think that's the reason. Also this project worked like a charm, even a half year ago.
It comes even worse, after I close that previous project and try another project, that then also doesn't work. No other. When I try to listen to any song on lets say windows media player or foobar - also then there is no output.
I than even cannot load any webside in any browser like firefox or explorer etc. The sound settings of computer says everything is ok.
When I try to close Cubase and restart, the problem remains. When close Cubase and start Renoise - no sound. All I than can do is restart the computer and than all works. Problem is I need to work on that track, since that's the best one I so far have and would like to make it finish 
For some reason all works also in Cubase, if I do not touch that single project.
I also use Kaspersky Virus projections on PC.
Damn PC's never ever. Does anyone got a good advice what to do?
 https://soundcloud.com/shivagarden |
|
|
|
frisbeehead
IsraTrance Junior Member
Started Topics :
10
Posts :
1352
Posted : Mar 27, 2016 19:03
|
Try to start a new project and import the tracks to the new one. I've never had such problems myself on Cubase, but I've had to deal with buggy projects on Logic and that's the work around for it.
It seems like there's something weird going on with your system. If my intuition isn't playing tricks here, it might have to do with the audio driver priority thing clashing with some other thing within your system - probably some system definitions that don't play well with it.
Mind you, once you turn on Cubase it overrides some of the system settings by definition. Such things as screen savers, turning disks off, so on and so forth. So it's best to let the system get out of its way and let it do its thing, I think. The more opposite directions coming from the system, so to speak, the more likely you're to run into trouble. But I really think that importing all the tracks to a new clean session will do the trick here. Cheers |
|
|
|
frisbeehead
IsraTrance Junior Member
Started Topics :
10
Posts :
1352
Posted : Mar 27, 2016 19:11
|
|
It can also be some buggy plug-in or simply that you're hitting your system's memory limits, in which case all sorts of weird behavior is to be expected. |
|
|
|
TimeTraveller
IsraTrance Full Member
Started Topics :
80
Posts :
3207
Posted : Mar 27, 2016 19:21
|
Yeah .. thaught about it also.. Just the whole project got round 50+ tracks. Lots of unbounced strange connections to group channels with side chainings and other stuff. A bit of a pain in the ass to export it all but that's maybe still a chance to get my project working again. The strange thing is that I can start all other projects before that one.
I noticed that the meter on VST Performance got a high real time peak on that project. Too high. Its quite odd, the avarage peak meter is nothing - but that real time peak is on overload.. Cannot get the reason why but I think this indicates on that problem. The damn thing is that it pops up even before I push on play.
I think your idea is a good chance to get my project working again. I work now on another track and keep it sinking in my head for a few days but at some point I will export all them tracks and give it another chance that way. Hopefully that will work. Cheers
https://soundcloud.com/shivagarden |
|
|
|
TimeTraveller
IsraTrance Full Member
Started Topics :
80
Posts :
3207
Posted : Mar 27, 2016 19:22
|
Quote:
|
On 2016-03-27 19:11, frisbeehead wrote:
It can also be some buggy plug-in or simply that you're hitting your system's memory limits, in which case all sorts of weird behavior is to be expected.
|
|
i need to analyze or inserts and sends.. but the instruments should all work. Thanks.. another good hint to look a bit deeeper (inserts)
https://soundcloud.com/shivagarden |
|
|
|
frisbeehead
IsraTrance Junior Member
Started Topics :
10
Posts :
1352
Posted : Mar 27, 2016 21:11
|
If you've got the 8.5 update you can select those tracks and import them all to a new project.
I honestly don't know if it (already) handles such things as mixer routings and all of that. if it doesn't, it sure should - and it might be good for us to say so on their forum, after we check it. I know it's possible in Logic, ever since the 9 version.
Even if it only allows you to import all the individual tracks alone, along with their channel settings intact (this I can confirm myself), it would be down to saving those channel presets and then putting them back in place on the new one.
If you do this one track at a time, despite being more tedious, will also be a good chance to check if there's any faulty plug-in causing this situation. All in all, you'll get a much more organized and manageable project when you're done with it, I think.
Also, I've felt from the first moment that Cubase is a bit more picky with plug-ins then Logic was. Most of my crashes are related to faulty plug-ins. Surely the pace of updates in both hosts and OS doesn't help much. Everything seems to be just fine now with all my arsenal though. But it took a while to get to this point. Cubase was good for me at 8.0.3. Third party plug-ins took a little longer.
Also, I avoid using the VST3 option on mostly all third parties, most specially prior to testing them. Some of them can turn any project into havoc or crash the whole thing the moment you select them. At least on my system. So that's also something to look for |
|
|
|
TimeTraveller
IsraTrance Full Member
Started Topics :
80
Posts :
3207
Posted : Mar 27, 2016 22:47
|
there is also the option to bounce all tracks at once . So that you get seperate audio tracks. But du to more complex connection it would make no sense for me it would take more time, at least for me.
Dunno if there is the function that you mentioned, that includes group, send etc connections. That would be fine. Need to look for it.
I still don't have 8,5. Need to consider now every single buy even for refrigator since i don't have any income at this time, and money shrinks.
I managed to solve my problelm! Thanks for the hint with plug ins.. What I did is to delete only the insert plug ins that way bypassed..... and than after an houre and a new try, it works!
Strange... i thaugt when the plug ins are on bypass - grey - than they are like frozen, and it does not make anything to the VST Performance meter or better said to CPU. I did notice that after I removed all bypassed plug ins which were between 10-15, the meter wasn't overload anymore and everything worked again.
Still strange behaviour since I never had any problems as I worked on that track some months ago.
And seems that bypass means not freeze or does not remove additional math for cpu, maybe not enough of it.
Also not sure, if I automated some bypass on some tracks, I rarely do automate bypass but could be here. However so nice to have my track again. I think I need to bounce to audio still much faster.
Nice tweeking psycubasers!
https://soundcloud.com/shivagarden |
|
|
|
vipal
IsraTrance Full Member
Started Topics :
123
Posts :
1397
Posted : Mar 28, 2016 12:51
|
i had some weird issues recently that went away when i converted all files to the 24 bit the project was in (some imported samples were 16 bit).
since then i take notice to keep everything in the same bitdepth as the project.
http://soundcloud.com/vipal |
|
|
|
TimeTraveller
IsraTrance Full Member
Started Topics :
80
Posts :
3207
Posted : Mar 28, 2016 15:23
|
Quote:
|
On 2016-03-28 12:51, vipal wrote:
i had some weird issues recently that went away when i converted all files to the 24 bit the project was in (some imported samples were 16 bit).
since then i take notice to keep everything in the same bitdepth as the project.
|
|
Useful advice. I remember during my sae time one of the very first things they thaught were like it's standard to keep a project in one sample rate and one bit rate but I haven't followed this each time, especially since Cubase 8.
I assume you convert 16 bit-samples to 24 bit, to keep the project stable.
When rendering to audio the standard is always in 32 bit, do you change that also to 24 bit or have you jumped on the 32bit way?
I feel 24 bit rate is enough but I'm not sure if 32 bit could be significantly better.
Different sample rates in one project is a guarantee for mess, but I thaught that high bit depth is just a headroom for peaks and it's not dramatic to have some signans in different bit rates.
https://soundcloud.com/shivagarden |
|
|
|
frisbeehead
IsraTrance Junior Member
Started Topics :
10
Posts :
1352
Posted : Mar 28, 2016 18:59
|
I think bypassing the whole chain should indeed work as you expected and release all the resources used. Surely no way they'd make the cpu meters go up, unless there's something wrong with at least one of them?
I think the sample rate is more problematic then the bit depth on a project situation. And up sampling is rather pointless in most situations and can also lead to a lot of quantization errors or even chip monk like audio. I take care to down sample stuff it needed and make good use of dithering while doing so. I can get very anal with the details and more often then not, I do eheh.
32 bit floating point is convenient - specially if later on you need to exchange files with other people for mix work or something like that, so you don't have to worry about filling those bits with signal, but it also comes with the cost of a much higher disk imprint. So I don't make much use of it for my own projects, specially on the laptop, since space is more of an issue with it.
If I'm not mistaken here, with 24 or 16 bit files, you still need to care for a decent signal to noise ratio, making proper usage of the available bit depth (which is sort of the same thing) whilst with 32 bit floating point you're free to print those files worry free. Just takes that bit more space on your hard drive due to all the extra bits on the equation.
|
|
|
|
TimeTraveller
IsraTrance Full Member
Started Topics :
80
Posts :
3207
Posted : Mar 28, 2016 23:43
|
After progressing on with my project the problem occured again. It made me almost get crazy.
It took me longer than a whole movie I wanted to see with my girlfriend (on tv lol) to solve that problem.
Dunno why but it really releases power on my VST performance meter when removing already bypassed plug ins. It was my only chance to delete some stuff I wanted to keep for future. Like bypassed instruments with midi files etc.
Maybe it still lies on some other problem that I can't locate now but deleting bypassed stuff helped here.
Certainly different sample rates in one project will cause more problems than bitrates or guaranteed and always.
Sure if you convert 16 bit file to 24 bit you would do it just to make all files in the same bit rate, but maybe you also could prevent your system from quantizations errors with this method. It certainly is, as you said, you would waste harddisk space while giving them audio files just additional zeros (and not ones since there is no information on them 8 more bits).
I also dislike the idea of wasting hd space but Vipal mentioned some issues. Still its possilbe his issues had maybe another reason.
Not sure if I really need more than 24 bit to prevent any loss but I always inspire myself from reading and open up my horizon for fresh news.
All I know about bit range is that each bit has a capacity of 6 dB. Signals over 96dB hit over the maximum headroom of 16 bit range, the wave than results in a square. For example a trumpet at its loudest can only be recorded in 24 bit if you want the whole information.
I think just from this that 24 bit should be enough for my cpu. Than again sure it's not just about loudness which affects the bits and the cpu when it comes to work in our daw's.
Isn't signal to noise ratio more a term relevant when it comes to lower bits (first bits) f.e. when you record some quite signals that are more in the near of the footroom? Like signals that peak maybe at -30 dBFs.
Than it's about having good ad/da converters but I'm not completely sure here. Maybe I confuse it with THD here.
Though therefore it's important to record not too soft, to try to use every single "bit" to get rid of any unwanted noise or to use the fader in the mix as near as possible to the max without the master going red. That's a way not to loose any bit too.
Also I think more on details than I should lol but I think that's a good way to get better quality.
https://soundcloud.com/shivagarden |
|
|
|
frisbeehead
IsraTrance Junior Member
Started Topics :
10
Posts :
1352
Posted : Mar 29, 2016 06:47
|
My understanding of it is the same as yours. In any recording there's going to be some level of noise, so recording at low levels will give you less usable signal then making use of the available headroom (or bits).
This is only relevant during two occasions: one is when recording external sources and the other is when printing files, specially mixes. But when recording, I think of signal to noise ratio as the distance between the good signal and its noise floor. The more distance the better the signal, 'cause the easiest it is to process it without the noise also building up and creeping in. Something within this lines. For rendering files, this is also a concern if you're a perfectionist, making full usage of the bits available is a good thing, specially when you have recordings from external sources in there. Uffff...
|
|
|
|
vipal
IsraTrance Full Member
Started Topics :
123
Posts :
1397
Posted : Mar 29, 2016 10:22
|
|
Dypden
Started Topics :
2
Posts :
12
Posted : Apr 11, 2016 10:51
|
Quote:
|
On 2016-03-08 19:10, frisbeehead wrote:
Yes, they have improved it. Tried it just now to be sure.
Take a look at this screenshot:
https://www.dropbox.com/s/a8se0upeniupnd4/Screen%20Shot%202016-03-08%20at%2017.05.22.png?dl=0
Project's tempo is set at 150 bpm and the sample previews with no time stretch or pitch change.
I remember that little annoyance when working on a friend's studio using Cubase 5 recently. I know he had some work around for it, though. I can ask if you're interested
|
|
I'm running C8.5 trial at the moment, and I still have the same issue. Just to be sure; does the sample (i.e. clap/snare sample) loop in sync with the beat in your project or does it just play once? |
|
|
|
