KVR Audio

davidv@plogue · Post by **davidv@plogue** » Fri Jun 07, 2013 10:09 pm

Sendy wrote: I still don't know what "monotonicity" does (I didn't see it covered in the manual), though obviously it has quite a strong effect on the stability of the sound.

From wikipedia: Monotonicity
The ability of a DAC's analog output to move only in the direction that the digital input moves (i.e., if the input increases, the output doesn't dip before asserting the correct output.) This characteristic is very important for DACs used as a low frequency signal source or as a digitally programmable trim element.

So basically when monotonicity=100% all the bits of the DAC influence the output as math perfect as you'd expect. When you drift from that you start to get weird shaveshaping due to bits slightly changing 'weight', or electronically speaking if you think of a 'Resistor ladder' made DAC, that the resistances are way out of tolerance. 95-100% should be used to stay in the 'realistic range', though realism sometimes gets in the way of FSU, so you can do what you want.

As far as changing the pitch of the IRs, thats slightly more complex than wave playback

dayjob · Post by **dayjob** » Sat Jun 08, 2013 12:41 am

chip crusher sounds great. hifi lofi! i really dig it. so many uses.

t3toooo · Post by **t3toooo** » Sat Jun 08, 2013 1:25 am

so how many samples of latency does chipcrusher add exactly?

paulbreeze · Post by **paulbreeze** » Sat Jun 08, 2013 11:42 am

Nice plugin. However the installer/plugin has one minor problem. The installer lets you choose a custom directory for Chipcrushers Data (bg noises, ir), but the plugin still tries to load it from the default C:\Program Files\Plogue\chipcrusher\Data . First bg noises and post-processing did not worked for me, so I had to create a junction point for it. Now they also work fine.

Thanks,

davidv@plogue · Post by **davidv@plogue** » Sat Jun 08, 2013 1:26 pm

paulbreeze wrote:Nice plugin. However the installer/plugin has one minor problem. The installer lets you choose a custom directory for Chipcrushers Data (bg noises, ir), but the plugin still tries to load it from the default C:\Program Files\Plogue\chipcrusher\Data . First bg noises and post-processing did not worked for me, so I had to create a junction point for it. Now they also work fine.
Thanks,

Hum, can't reproduce this, I always install the data files myself outside of Program Files:

And it works fine, presets and all.
Note that the RTAS and Aria engine cannot be moved, they always should be on the system drive.

Thats On XP of course, but I tested this on W7 fine too. Are you using W8?

davidv@plogue · Post by **davidv@plogue** » Sat Jun 08, 2013 1:28 pm

t3toooo wrote:so how many samples of latency does chipcrusher add exactly?

We are currently fixing the reported value, so I can't give you a precise figure at the moment, as its not trivial. Depends on the Sample Rate of course, and whether or not you use 'live' mode.

paulbreeze · Post by **paulbreeze** » Sat Jun 08, 2013 1:47 pm

Interesting...

I use Vista x64 and installed with custom data directory to : 'C:\ProgramData\Plogue\chipcrusher' (note, no 'Data' at the end). Now this did not work at all.

I had to create a junction point in the 'C:\Program Files\Plogue\chipcrusher' directory named 'Data' :

Directory of C:\Program Files\Plogue\chipcrusher
06/08/2013 13:36 <JUNCTION> Data [C:\ProgramData\Plogue\chipcrusher]

Also did a test where I copied the data directories (bgnoise, impulses) bellow a 'Data' directory 'C:\ProgramData\Plogue\chipcrusher\Data' but this didn't helped either.

So for me the only solution was :

C:\Program Files\Plogue\chipcrusher>mklink /j Data c:\ProgramData\Plogue\chipcrusher
Junction created for Data <<===>> c:\ProgramData\Plogue\chipcrusher

32bit VST directory :

64bit VST directory :

Notice the automatically added extra 'Plogue Art et ...' at the end of the VST paths :

Here is a snapshot of the 64bit VST directory. The VST file name is also "strange" :

Are you sure that your version is the same which share-it sends out currently to custommers ?

Thanks,

whyterabbyt · Post by **whyterabbyt** » Sat Jun 08, 2013 2:03 pm

paulbreeze wrote:Nice plugin. However the installer/plugin has one minor problem. The installer lets you choose a custom directory for Chipcrushers Data (bg noises, ir), but the plugin still tries to load it from the default C:\Program Files\Plogue\chipcrusher\Data . First bg noises and post-processing did not worked for me, so I had to create a junction point for it. Now they also work fine.

Thanks,

Ran into the same problem (64-bit version) with a custom install location for the main folder, the plugin, and the 'patch data'. It was immediately obvious something was wrong; if post-processing was on, the output was muted.
A reinstall changing to the default 'patch data' folder (ie inside the main folder) rectified it.

Arglebargle · Post by **Arglebargle** » Sat Jun 08, 2013 3:45 pm

I discovered a problem yesterday, wherein a track with Chipcrusher on it became out of sync with the rest of the project. It didn't happen with the default preset, but after a few preset changes the problem became apparent.

I'm running Reaper, and have never had this problem before.

Arglebargle · Post by **Arglebargle** » Sat Jun 08, 2013 3:53 pm

Ok, I am able to reproduce the problem. I put Chipcrusher on a track, the PDC is 2048. Select the preset Vocals\Crisps and the PDC jumps to 17408 and the track becomes unsynced with the rest of the song. From that point on, if I disable all the modules, the track is still out of sync. If I switch presets, track is unsynced. Only thing I can do is delete the instance and add another one.

davidv@plogue · Post by **davidv@plogue** » Sat Jun 08, 2013 4:40 pm

paulbreeze wrote:Interesting...

Ahh OK! Now I get the issue, (sorry took a while to wake up here)
The installer asks for two folders for the data and setup files, but they indeed should always be together. (a chipsounds installer left over).

So for the record, until we ship 1.002, always install to

chipcrusher Main folder: somewhere\chiprusher
chipcrusher Data folder: somewhere\chiprusher\Data

In my case that would be:

E:\trunk\AriaProducts\1015
E:\trunk\AriaProducts\1015\Data

VST's can be installed anywhere still

BTW This is a Windows only thing.
Thanks for spotting this, and sorry for the messup.

davidv@plogue · Post by **davidv@plogue** » Sat Jun 08, 2013 4:45 pm

Arglebargle wrote:Ok, I am able to reproduce the problem. I put Chipcrusher on a track, the PDC is 2048.

We are aware of the Latency host reporting issues, and we are going to fix them for v1.002, which hopefully should next friday (or before) if all goes well...

Regards

paulbreeze · Post by **paulbreeze** » Sat Jun 08, 2013 4:45 pm

Thanks,

3ee · Post by **3ee** » Thu Jun 13, 2013 10:42 am

Sendy wrote:Speaking of resonance, would it be possible to be able to tune the impulse up and down in a similar way to how the noise samples might be pitchable in a future update?

That would be awesome!
Finetuning the overall "EQ bands" all at once or great for some heavy automation duties.

there would be one problem tho... the spectrum extremes need to be controlled a bit to make every IR usable with that parameter.

davidv@plogue · Post by **davidv@plogue** » Thu Jun 13, 2013 11:22 am

3ee wrote: there would be one problem tho... the spectrum extremes need to be controlled a bit to make every IR usable with that parameter.

We didnt add this feature to the list, at least for the near future.
However the 4 most requested features/fixes are currently being QA'd . More later...

New! Chipcrusher! - Advanced Bitcrusher, Speaker Simulator and Noise Machine from Plogue