BEGINNER: Simple filter

Warmonger · 25 Jun 2012

I didn't find a direct implementation of digital elliptic filter unfortjnatelly. Most of these are analog or use Matlab functions. My guess is that they are not really that simple.

If other filters are enough, try this page: http://www-users.cs.york.ac.uk/~fisher/ ... /trad.html

Exact position of graphics can be tweaked in GUI area component, modifying the following values:

trogluddite · 25 Jun 2012

I'm not much of a filter expert, so I can't really comment on the exact filter responses you're looking for, but I would make the following points...

SBMastering wrote: I changed the code to mono

Do you mean going inside the code to change 'streamin' to 'monoin' etc.? If so, this should not be necessary - a straight 'streamin/out' declaration is a 'general purpose' stream connector that should work equally well with mono, mono4 and poly. (there are exceptions, but they are very rare, and not any filters that I know of). Code (and assembly) modules with 'stream...' connectors will pick up the data type according to what kind of links they are wired up to (the type propagates from right to left). What is quite common is to find module connectors which have been assigned a fixed type - so that they no longer use SM's 'automatic type detection'. This can lead to accidental connection between incompatible data types (e.g. mono to poly). To alter these, right click on the circle of the module input or output (you have to do this from within the module) - a drop down will appear where you can select a new data type (or none at all, if you want to return to 'auto'). If this doesn't get you unstuck, don't hesitate to post the schematic (or part of it, or a link). It really is the best way for folks to get their heads around the problem, and will usually get it fixed much quicker - often by a return post of schematic, so that you can 'contrast and compare' to get some good building tips. The files really are very small, and you can always delete them later if you are feeling guilty about hogging the server!

To move your GUI elements more accurately, select them for editing on the panel as usual - then use the cursor keys. On their own, they will snap to grid, but if you hold down CTRL, you can nudge one pixel at a time. 'Sub-pixel' positions are not recommended - SM's anti-aliasing is a bit crude, and it tends not to look nice!

The problem you had with using literal co-ordinate values is quite common. It is often a side effect of the way SM nests sub-module panels within a main panel. In general, co-ordinates fed into an MGUI 'X,Y' inputs set the position of the 'sub-panel' within the master, relative to the top left of the master (Y co-ordinates are positive as you move downwards). Co-ordinates for 'Areas' etc. within a sub-module refer to the top left of the sub-module. Erm, except that they don't always! When you move anything manually in panel edit mode, or move a 'parent' panel within a 'grandparent', the fixed 'MGUI' co-ordinates often get over-ridden -the various MGUI's that the view 'chain' passes through seem to interact in a very peculiar way sometimes. With 'synchronised' modules in particular, I have often had to resort to deleting and replacing things to clear up the mess! It's also worth noting that the co-ordinates you see when moving stuff in 'panel edit' view can be shown either as grid units ("sqr", of 8px per grid by default), or alternatively in pixels (useful when 'measuring up' for Photoshopped backgrounds etc.) - click on the label to toggle between them. You can also change the default grid size in the options menus - though I don't recommend this, as it can lead to panels which don't display correctly if you post the schematic for other users to have a look at.

If an element disappears from the panel, you can usually get it back. In 'panel editing' mode, you will see a red line at the border to indicate when there's something 'beyond a 'viewport' edge - to go find it, grab the little handle at the mid-point of the viewport edge (worth zooming in, they are very small) - this lets you resize the viewport independently of the main module re-sizing handle, allowing you to expand the view until you can see your rogue graphic. Alternatively, you can sometimes get them back by just cutting the offending module from the schematic, and then pasting it back in, or by deleting the MGUI primitive and replacing it with a fresh one.

SBMastering · 25 Jun 2012

Thanks guys!

When I left the code alone, the hi and low pass worked as they should! Before, I changed the polyins to monoins. I'm not sure why that made it not work.

I tried the nudge thing -- that worked too. That's a REALLY good one to know.

I will keep it in mind going forward about posting screen captures.

Also, perhaps coding the eliptical filter could be a contribution I could make at some point.

martinvicanek · 26 Jun 2012

You can grab a steep lowpass filter from here. The offering includes Butterworth and Chebyshev filters of various orders (up to 10). 🙂

trogluddite · 26 Jun 2012

SBMastering wrote: posting screen captures.

Posting the SynthMaker .osm document itself is just as easy (and small file)- and often more useful, as folks that then dig around inside modules etc.