DSD Render glitches

[crna59]

Has anyone noticed that there are ticks/pops at the beginning and end of the file that you split and DSD Render? I'm having problems with this on both my Masscore and Native systems.

Win 7 Pro Masscore 9
Win 7 Pro Native 8.1

You can fully zoom in and the waveform does not line up between tracks and you get these ticks/pops. Is there a way to put a millisecond fade at the beginning/end of the files without having to do it by hand? I thought there was a check box at one time that would do this?

[allemano bernard@neuf.fr]

Hi,

In all setting /application/play back/record : auto deglitching

Also, in all settings/ etc... editing : auto crossfade by default

Also, in all settings/ etc.../record : auto crossfade

Best,

Bernard

[Graemme]

This doesn't work in DSD mode... only DXD / PCM.

Hi,

In all setting /application/play back/record : auto deglitching

Also, in all settings/ etc... editing : auto crossfade by default

Also, in all settings/ etc.../record : auto crossfade

Best,

Bernard

[Graemme]

There never has been any automatic fade creation for rendering in DSD (or PCM, for that matter). It's still a manual labour kinda' thing.

Also, *any* file played back in DSD mode will 'click' at the beginning /end of the file as well as at the start and stop of playback. DSD mode is a raw recorder / player with none of the conveniences of the DXD / PCM modes.

Graemme

Has anyone noticed that there are ticks/pops at the beginning and end of the file that you split and DSD Render? I'm having problems with this on both my Masscore and Native systems.

Win 7 Pro Masscore 9
Win 7 Pro Native 8.1

You can fully zoom in and the waveform does not line up between tracks and you get these ticks/pops. Is there a way to put a millisecond fade at the beginning/end of the files without having to do it by hand? I thought there was a check box at one time that would do this?

[crna59]

This is happening if I'm in DSD or DXD mode.

I transfer a 33 minute tape, just split tracks and DSD Render out and still get ticks/pops at the beginning/end of each track.

Driving me f*in crazy.... the labels don't like it either!!

[Graemme]

Exact Pyramix version # ?

Maybe I wasn't clear: I assume that you are creating small fades at the in and out points of your split DSD clips before rendering them? Those fades should be at least 1mS long.

[crna59]

Pyramix Masscore 9.06, build 23165

and Pyramix Native 8.1.10, build 21289

I don't want to have to go in and create the fades, I want them to automatically be done for me so I won't have these clicks/pops!

[Graemme]

Well, they aren't and haven't ever been...This has been requested for years...Perhaps now that rendered DSD files have become a delivery format, this feature might become reality. But for now, it ain't.

There are newer versions of PMX 8.1 (8.1.12 hot fix build 21893) but anything newer than b21893 seems to make DSD-Render problems worse.

Pyramix Masscore 9.06, build 23165

and Pyramix Native 8.1.10, build 21289

I don't want to have to go in and create the fades, I want them to automatically be done for me so I won't have these clicks/pops!

[crna59]

Thanks Graemme.....

[tailspn]

Blowing up the time and amplitude scale on the timeline (4X amplitude, ~10 milliseconds/major div time scale), and monitoring the the sound as you search around for a low/no click start allows you to pretty easily find a silent start. The problem arises, besides it taking ten seconds to a half a minute or so to find a "zero offset" crossing, is that the tail of the preceding "new" end is packed with zeros for several bit times, meaning that new end point is not at the zero crossing. Bottom line, you can easily most always make a silent start, but the end of file will click.

My experience (having done several thousands of these slices) is you can make it much quieter than a random slice point (like a DSD EM track marker). But even doing a DXD fade in and out still leaves a click, once DSD rendered.

[crna59]

Blowing up the time and amplitude scale on the timeline (4X amplitude, ~10 milliseconds/major div time scale), and monitoring the the sound as you search around for a low/no click start allows you to pretty easily find a silent start. The problem arises, besides it taking ten seconds to a half a minute or so to find a "zero offset" crossing, is that the tail of the preceding "new" end is packed with zeros for several bit times, meaning that new end point is not at the zero crossing. Bottom line, you can easily most always make a silent start, but the end of file will click.

My experience (having done several thousands of these slices) is you can make it much quieter than a random slice point (like a DSD EM track marker). But even doing a DXD fade in and out still leaves a click, once DSD rendered.

I've been doing several thousand of these as well and every time the label comes back saying "in/out point has glitch"... I even tried the DXD thing and still get them. I don't have time for a normal Render. Just takes too damn long when you have a dozen or so albums to do.

Don't get me started on having more than one project on the time line when you do a DSD render. This is a known bug....

[tailspn]

Yep, that's my experience also. The most notable and consistent click occurs in the start and stop from dead silence/no signal. There's no quiet point. In inter-track hall ambiance you can find and create a silent DSD start point. The end of the file just will not be click-less, because the actual content stop point gets shifted earlier by several bit times by the Slice Command, back into click noise territory.

Doing a DXD fade is also worthless, giving you the in/out click of DSD no signal before and after the fade. The only complete solution is converting the entire file to DXD, and inserting fades, which of course, is no solution at all. If you can take the time to find silent slice points, you can usually create satisfactory sliced files. At least get the clicks down to the tick level.

Additionally, if you record your transfers in 256fs, instead of 64fs, there's virtually no click on in/outs.

[crna59]

Thanks Tom... to make things quicker, I've had to set one of my zoom settings all the way in so I can see the zero crossing. I'll do a few albums to see how it works. Little slower than I had planned, especially when track markers are in the middle of a crescendo!

[draudio2u]

Hello,
Anyone know if this "start/Stop" tic issue has been solved? I always deliver full DSD Edit Masters but now have requests for DSD Tracks for internet download. Can't seem to get around the start/stop tic.

Running 9.1.8 build 26726 in Native (Mytek converters).

Thanks