PlanetZ forums - scopeusers.com

hello,

i have recently re-installed SX 1.06, with a reload of my machine, and i usually remember to set things correctly. however i wonder if i have missed something obvious that someone could help me with.

i record synth parts into cubase via an A16 Ultra and a Pulsar II card. i am running SFP 4.0. i have checked all my settings there and i think i have everything as it should be.

basically the recording levels are insane, no matter how low i have the actual synth part to be recorded. (i am recording 32 bit float files at 48Khz.)

the recorded files' levels are so high in fact that i have to normalize each recording- this isn't ususally a problem if the levels are a bit high, but they are just way up there, and i can't remember having this sort of problem before. i seem to incur a bit of artifacts, especially on the parts that clipped, after normalizing the recording.

i would like to just get the recording levels down so i don't have to normalize so drastically, and hopefully avoid the artifacts in the process.

i keep thinking that i have just missed something very simple; if this rings a bell with anyone who would be willing to help out the hopelessly dense i would greatly appreciate it.

i suppose this is probably an sx issue, but i thought that someone here may have had a similar experience or could point out the blatantly obvious...

cheers

<font size=-1>[ This Message was edited by: AEP on 2004-12-20 20:15 ]</font>

i still use this version and what i have noticed is that the graphics in cubase sx looks like they are higher than the level recorded. it happens after a certain level.

I use a channel.dev before asio source to monitor levels. At high levels, and when there is no clipping (margin in channel shows -3 db for ex) then the graphic of sx looks like it is saturated, but it is not (always) the case...

I try to have my highest volumes at -6 db in Scope (according the margin level meters) and it looks fine in cubase. I didn't have any real problems with that. I did a lot of voice recordings during the last monthes, and also all kinds of synths and fx from scope.

the only real problem this sx version has is that it looses vst inserted effects on projects save (sometimes works, sometimes doesn't). so i save a different version every time i do something, so i can go back easily and the amount of stuff to redo is minimal. this is the ony serious bug in this version.

I hope it helps.

<font size=-1>[ This Message was edited by: Mehdi_T on 2004-12-21 06:22 ]</font>

thanks-

the thing is, the levels in SFP are comparatively MUCH lower than what is represented sonically in sx. i don't think this is a graphical error as much as a recording level error in sx.

the levels have to be reduced in SFP to the point where they are barely monitorable; itherwise the recorded part is clipping all over the place.

i can see the louder levels graphically and can hear them sonically- sx is definitely recording things at an extreme level

Are you sure you have 32 bit recording enabled in SX project setup window?

/dave

On 2004-12-21 15:21, dbmac wrote:
Are you sure you have 32 bit recording enabled in SX project setup window?

/dave

yes

It's a known SX 1.x bug with floating p. asio drivers, fixed in ver. 2

I've never had this prob (still using SX1.06)
May be you've got some signal routing that's bypassing the fader, like a compressor or such. Or you've got something routed back via SFP.

yeah, this never happened before...

i'll check to see, but i don't believe i have anything routed back through SFP.

i am POSITIVE i have just overlooked something really simple----AAAARGGGGHHHH!!!!

lol

I'm not using 1.06 anymore, as I have SX 3, but didn't 1.06 show an overload on Master meters when using Fl.P. asio drivers? I remember such a thing....

FI.P. drivers? don't know those...

i am using asio scope

damn acronyms! Fl.P.=Floating Point.

LOL!!!

and i'm in telecom! you'd think i would have figured that one out... duh...