ModularGrid uses so-called cookies to ensure it's so-called functionality. We also use dubious tracking scripts. Find out more in the Privacy Policy. We use cookies and wanna let you know.
I think what you are offering is more than fair. For the information and service you provide it is easily worth what you are charging. While I could probably get by with a free account, I'll pay the small fee just to support this excellent service.
Thanks!
I applaud you for not thinning out the screenshot database. I hate seeing broken links in forum posts.
Yes. Key strategy here is to slow down the growth of screenshot data through the limits in the standard account..
I think what you are offering is more than fair. For the information and service you provide it is easily worth what you are charging. While I could probably get by with a free account, I'll pay the small fee just to support this excellent service.
I applaud you for not thinning out the screenshot database. I hate seeing broken links in forum posts.
I couldn't figure out how to get the manufacturer name in the "ADD" form to add these two FMR modules into Modular Grid. Nor could I find the category of "compressor" for the description.
To address the above bullet points, won't you need to clean up some of the "Main (copy) (copy) (copy) (copy) (copy)" entries?
I would think something like deleting ">10, not accessed in 1yr" racks would be acceptable.
-- Sleipnir
That's always a little problematic. Many of the racks screenshots are embedded in forums. Deletion would result in a lot of broken images which does not look good.
I delete older empty racks and unused anonymous accounts though.
To address the above bullet points, won't you need to clean up some of the "Main (copy) (copy) (copy) (copy) (copy)" entries?
I would think something like deleting ">10, not accessed in 1yr" racks would be acceptable.
"!The VCA Output of the Synthesizer Box module is internally patched to the Left and Right inputs of the Outs module. The internal patching can be disrupted by plugging a patch cable into the Left input of the Outs module.
!The Midi2 module Gate1 is internally patched to the 1V/O input of the Synthesizer Box module. The internal patching can be disrupted by plugging a patch cable into the 1V/O input of the Synthesizer Block module.
!The CV1 Output is internally patched to the Envelope input of the Synthesizer Box module. The internal patching can be disrupted by plugging a patch cable into the Envelope input of the Synthesizer Box module. "
I am getting "moderated" on Gearslutz to oblivion for "trying to fish their users" when announcing the new 500 series mg planner. This way pisses me off because they have no problem letting their users embed mg screenshots for discussion which adds value to their forum, imo.
Mod says, they are working on a "very large project so why would we promote of someone else's database??".
Can't wait to see this.
Perhaps they are right I don't know, but I am feeling the strong urge to block all Gearslutz image hotlinking.
Don't know why I post this, perhaps I should go for a walk in the zoo.
Hulk off.
drone patch. of course, in a performance, all parameters can change, but this is a nice way to begins.
and there's some internal connections given by pittsburgh system from factory.
Contacted PGHmod and heard back almost immediately that they have a quick fix.... no specifics though. I happen to be headed to PGH for a few days in a couple weeks for a gig so just going to stop by the shop then.
-- grieve
Today I introduce the Unicorn Account which is a payable upgrade for registered ModularGrid users.
Before you unpack your torches and pitchforks please read on:
In the last three years I have understand that a complete free an unlimited webapp comes with some significant problems.
And that's not only me doing an unpaid fulltime job.
The main problem is the excessive accumulation of digital garbage which eventually spoils the fun and value in use for everybody. You have mods in forums to care about such but that does not work on a web-based modular planner.
The Unicorn Account should address these:
Satisfy the calls for even bigger Racks for the Pros while preventing the polluting of the database by some Newbs
Keep the amount of Racks at a healthy minimum, make browsing through the Racks interesting again.
Prevent the webspace been eaten by zillion rack screenshots of final_system(copy)(copy)(copy)(copy)
Better statistics, tame the need of users to build another Math-only Monsterrack
Better server performance for everyone. Better protection from DOS.
Bring in some cash, obviously.
Chances are you won't notice
The standard MG account will be always free and still lets you create 10 racks, each of the size of a massive Doepfer monster case! That should be more than enough for 95% of all MG users.
(Remember you can always copy modules in two opened browser windows with the c,p,x keyboard shortcuts.)
You won't lose what you already got
I thought a lot about to make this change happen without taking away what users already have.
The solution: If you already have a large or a lot of racks, you can still use them for free!
You just won't be able to resize your big rack and you can not create new ones if you are over the limit.
I have an Elite 208, which is good. I was hoping to get the Pittsburgh since it could stand upright behind it (the Elite case won't stand on its own).
I do have a fried Make Noise power board that I've been meaning to get fixed. Maybe I could get the Pittsburgh case and switch out the power supply for the MN board.
(I prefer the "no fuss" look of the Elite & Pittsburgh cases to some other more rugged designs. I'm just using them in my apartment but I need the flight cases because I don't have enough space.)
Instead of the 208, I'd go for another case. The PGH supplies can be weird. Some modules have issues when powered by them. Perhaps try a monorocket 208 hp case instead.
hmm, I was planning on getting a 208 and Shapeshifter this month. I might hold off after reading this.
Interested in knowing how this turns out. Hope you get it fixed!
Traded my SCM+BO for a pair of Z4000 VC EG's. Really excited about having a dedicated & marvelous ADSR for each of my main voices in this case. Now.... just where to arrange things. again. Got the 2nd Pressure Points this morning! :) now we're cooking..
In sketch a patch: When i choose to sketch a patch, it seems to use an old, outdated (cached?) version of my rack, which i dont seem to have a way of changing.
EDIT: Nevermind, reading the SaP FAQ solved my problem. All is whale, remain clam :D
One of the 1st few sessions exploring the MakeNoise Wogglebug and Tiptop Audio Z4000 Envenlope Generator (amazing). Here... a single Braids is the sound source.
the Stepped Out of the wogglebug into 1/v of Braids, whilst sending the Random Gate Burst to Rene, and Renes CV out to FM of same Braids in Meta Mode..,
with the Random Gate Burst also multed to tiptop z4000 gate in, which is the final cv to Linix.
heres a lil viddy of the result.
this lil patch has definitely opened my "control" of the woggle a bit more:
This is the system I hope to build over the next year or two, in a Goike 104HP x 15U curved ergo case.
(I have the Expert Sleepers and Pittsburgh modules already.)
this is part of my current trogotronic modular set-up. in addition to these mods, I have the prototype Valkyrie cv. I have been running each synth into separate amplifiers to create far-panned, distopian walls of screaming ear-torture, or microscopic, stuttering, alien conversations between the units. i use the make noise function as my clock, subdivide with the rcd, and warp the pulse with the 333. this system is simple as fuck but articulate and mind-melting. all hail trogotronic!
Contacted PGHmod and heard back almost immediately that they have a quick fix.... no specifics though. I happen to be headed to PGH for a few days in a couple weeks for a gig so just going to stop by the shop then.
To start, don't patch into the Phonogene just yet. First, take a minute to get the Math's Channel 1 and 4 cycling in a way that opens the VCA's on the Optomix channel 1 and 2 in an interesting way. This is a lot easier to hear with just the DPO sequence and effects.
Now, load the sample of choice into the Phonogene and set to loop. Chop the sample into several smaller pieces using the splice button. Patching from the Rene's Qcv to the Organize input will choose a new splice for each stage of the Rene. While the Phonogene's volume is low (between the panning), increase the Gene Size. As the Phonogene output starts to gain amplitude, slowly scroll through the sample with the Slide knob to find an interesting transient and leave the knob put. Finally, switch the Qcv to the Varispeed input and attenuate in order to sequence the pitch of the sample.
For interesting changes in timbre, switch between splices with the Organize knob. This will likely require you to find a new transient with the Slide knob. Note, the Phonogene's Live/Loop knob back will act as volume control.
To start, don't patch into the Phonogene just yet. First, take a minute to get the Math's Channel 1 and 4 cycling in a way that opens the VCA's on the Optomix channel 1 and 2 in an interesting way. This is a lot easier to hear with just the DPO sequence and effects.
Now, load the sample of choice into the Phonogene and set to loop. Chop the sample into several smaller pieces using the splice button. Patching from the Rene's Qcv to the Organize input will choose a new splice for each stage of the Rene. While the Phonogene's volume is low (between the panning), increase the Gene Size. As the Phonogene output starts to gain amplitude, slowly scroll through the sample with the Slide knob to find an interesting transient and leave the knob put. Finally, switch the Qcv to the Varispeed input and attenuate in order to sequence the pitch of the sample.
For interesting changes in timbre, switch between splices with the Organize knob. This will likely require you to find a new transient with the Slide knob. Note, the Phonogene's Live/Loop knob back will act as volume control.
Haven't had any issues with either of my two 104 cases. The only minor complaint I would have is not really a big deal... but the coating has a bit of tack to it and the lid wants to stick when trying to take it off sometimes. I played at an outdoor festival recently and the little bit of extra heat made it stick pretty bad... had to gently use a screwdriver to get the lid unstuck.
Still having issues with the 208 case. Weekend blown just testing different configurations. Going to contact PGH tomorrow and likely put everything back into the two 104 cases until it gets sorted out.
Thanks. Hopefully I can get it all playing well together. Still working through documenting a battery of tests.
I have 2x MOVE 104s as well... and just moved most of my modules over to this new MOVE 208. I plan on using one of the 104s for a modulation rack of sorts with a Vectr, Teleplexer and other odds and ends in it to sort of break out a tactile control / modulation / performance kit into its own case. Maybe even throw a guitar strap on it.
Then I have an Octatrack running into the Yarns to sequence and master clock everything. With everything running into a Presonus 16.0.02 mixer for mixer workouts and midi controls of mixer scenes. + Virus Ti2 desk for digi poly, Analog4 for analog/acid lines, Minitaur for a touch of Moog bass/filter, and Lemur for some custom/extended control of the Octatrack.
Octatrack also sending MIDI to a macbook running visuals via COGE. So everything is all synced up and triggered tight.
Thanks exper. Going to do some tweaking today so I can say I did my due diligence before reaching out to the PGH folks. Did a manual add up of the power specs in a spreadsheet as well rather than just going by the specs here on MG.
3 of the modules on the bottom rail have jumpers to offset some of the power to the +5 so going to try that since I wasn't currently using any +5 on the bottom... and double check all my connections while I am at it. Then see what happens. Thanks again.
Yes I would take it with PGH. I know there have been other power issues with their cell cases as well. Technically I'm running much higher mA levels with only 1.4A per 6u without any power outages with MN powered busboards. You should be fine if it was working properly.
I just picked up a new Pittsburgh Modular Move 208 case and arranged these modules into it. I seem to be having some power issues however despite the fact that everything adds up well within spec... even when dividing case spec between the two rails.
Am I missing something here?
MOVE 208 // +12v @ 2A, -12v @ 2A, and +5v @600mA // 12VAC 5.0A AC Power Adapter
FULL // 996 mA +12V | 455 mA -12V | 301 mA 5V
TOP RAIL // 400 mA +12V | 137 mA -12V | 170 mA 5V
BOTTOM RAIL // 596 mA +12V | 318 mA -12V | 131 mA 5V
It seemed to start first with the Shapeshifter... it would power down, followed by the rest of the top rail, then a few seconds later the bottom rail would go out. So then I read there have been some issues with Shapeshifters that require a new fuse and some soldering I will contact them about. So I disconnected the Shapeshifter and took it completely out of the equation.
Now after about 10-15 minutes of operation the whole bottom rail shuts down out of nowhere.
Does this seem like an issue I should bring up with Pittsburgh Modular regarding the case?
I just added in the QCD Expander and the 3 drum modules to my setup... all in the bottom... so the case and those 4 modules are my new variables in the setup.
Any advice would be greatly appreciated.
TROUBLESHOOTING TESTS:
FAILED // I noticed I wasn't using any +5 on the bottom... so I switched the jumpers on the QCD, QPLFO, & Basimulus to offset some of the power to the +5.
This piece was inspired by the "phasing" early tape compositions of Steve Reich, the nighttime sounds of late summer, and most importantly the amplified sound of my unborn son's heartbeat.
Having heard baby's heartbeat amplified at a prenatal visit, I was immediately struck by the energy, rhythm and cuteness, and also immediately thought of recreating it with my synthesizer. I created the sound with the DPO, Pressure Points, MATHS and modDemix, then recorded and spliced it with the Phonogene and used the EOS as master clock for the piece.
The melodic portion of the patch is based on a 4-step René sequence with several different rhythms bringing the timbres in and out. The modDemix, DPO Ext Src, and Pressure Points were the main nodes of expression. The Pressure Points in particular intensifies the echos, reverb and synced VCOA, and the tuned voltages change the overall rhythm for each section via the Erbe-Verb predelay control. This made it easy to intensify the patch periodically before brining it into a new section.
Toward the end I also played the René pads manually for higher notes before the coda. Ultimately this may have been unnecessary to the piece but this recording was my favorite take otherwise.
I made four versions of this patch before I found one that recorded to my satisfaction. Earlier versions used multiplied master clock via Echophon for unusual rhythmic juxtapositions (5 on 4 etc.), and/or feedback networks based on the CV output of the Erbe-Verb fed by the "heartbeat". These versions were interesting, but in both cases the upbeat rhythm of the "heartbeat" was compromised, or at least no longer seemed like the centerpiece of the patch, so I kept searching.
Yes, it's a killer module. Unique aspect is to do frequency dependent envelope following.
As far as i know only other module doing this is the Buchla 296 spectral processor.
But it's a power bitch!
A Eurocrack Pusher: "The first time is for free" ;)
A screenless alternative to hardwired and software samplers. With a turntable or other sound source in the Phonogene's input, the Varispeed knob controls the quality and length of the sample recorded. Setting the Varispeed to around 2 oclock will typically allow for several bars to be captured via the record button while in Live mode. Note: the ideal position can take some trial and error to find, depending on the tempo of the record and length of the phrase you are sampling.
Using the record button to start and stop the record like a traditional cassette recorder, it is possible to grab a loop that is the same tempo as the turntable and in the same time signature. Therefore, once the sample has been recorded to memory, switching from live to loop on a downbeat of the audio source will start the loop playback in time with the original phrase. (Note: if the Varispeed knob was set to 12:00 when the loop was recorded, switching from live to loop will not initiate playback of the loop until you manually move the Varispeed control.)
Using the splice button, you can easily cut the sample into smaller pieces in time with the original sample. If you mess up the splices, just hold the splice button down until the record light flashes and try again. By setting the splice knob full CCW it is possible to select which splice is played back by patching from a row of tuned voltages on the Pressure Points (row 2 on this patch sheet) to the Organize CV INput. In this way, each pad can have an independent control over which splice is played.
Patching from the Pressure Points Channel 4 Gate output to the play input on the Phonogene will send a gate that will initiate playback when a pad is pressed on the Pressure Points. Doing this also allows for the monophonic retriggering of splices (in MPC terms, all splices act as if in the same Mute Group with Poly set to 1).
Because the ideal Varispeed setting can be tricky to find, it is best to use an offset into the Varispeed input to control the playback speed and direction once the loop has been captured. This way you can change the Varispeed setting without altering the position of the Varispeed panel control, and getting back to the "ideal" setting can be done quickly and consistently. Using a row of tuned voltages on the Pressure Points allows each pad independent control of playback speed; however, this means each pad/splice will be in a different timing. For the example in the video, I put each tuned voltage at full clockwise and attenuated on the Phonogene so that regardless of the pad selected, the splices would always be in tempo with one another. As an added bonus, the next loop recorded from the same source material was in time with the original loop/splices!
Lastly, I run everything through the Erbe-Verb because everything sounds better through the Erbe-Verb ;-)
Enjoy!
Lee Coleman
