MUFF WIGGLER Forum Index
 FAQ & Terms of UseFAQ & Terms Of Use   Wiggler RadioMW Radio   Muff Wiggler TwitterTwitter   Support the site @ PatreonPatreon 
 SearchSearch   RegisterSign up   Log inLog in 
WIGGLING 'LITE' IN GUEST MODE

Announcing ALM017 - Pamela's NEW Workout
MUFF WIGGLER Forum Index -> Eurorack Modules  
Author Announcing ALM017 - Pamela's NEW Workout
ALM
New Pam is finally here !




‘Pamela’s NEW Workout’ is a compact programmable clocked modulation source for your Eurorack modular synthesiser system. It provides 8 highly editable outputs producing various control voltage signals correlated and synced to a BPM based master clock.

Building on the original ’Pamela’s Workout’, this new evolved model maintains the original’s form factor and intuitive workflow but greatly improves on and adds many new features with upgraded hardware, a new OLED display and rewritten software.

Each output is now able to provide not just clocked triggers but also rhythmic waveforms with many parameters controllable directly and via assigning to external CV control. Pamela has grown beyond a clever clock and now provides almost limitless synced modulation possibilities.

Improvements have been made to overall clock stability and integration with external clocks and devices. Also new are dedicated MIDI and Din Sync clock outputs available via optional expander modules.

Features

- BPM based clock with tempo rates 10-300BPM.
- 8 Clocked voltage outputs each with independent adjustable;
+ Clock divisors and multipliers from /512 to x48 including various non integer factors.
+ Gated, Triangle, Sine, Envelope & random base waveforms.
+ Waveform level and pulse width / skewing.
+ Phase, Delay and delay division (for complex swing)
+ Euclidean and random step skipping with beat based looping for rhythm creation
- All output parameters assignable to x2 CV inputs with individual software offset, attenuation and monitoring.
- Per output and group saving and loading to 200 banks.
- Voltage and direct control of clock stop/start, reset and rate..
- Sync to an external clock input at 48 to 1 PPQN.
- Realtime intuitive user interface with high resolution LED display.
- Provides dedicated DIN Sync and MIDI clock output via optional expander(s).
- Easy firmware upgrades via USB port.
- Unlikely to actually improve aerobic fitness.

For more info visit - busycircuits.com/alm017

Also the Pamela Manual covers all features in detail.

Retail pricing looking like ~ $275 / £230

==

There are also two optional expander modules now available - PEXP-1 & PEXP-2. Both offer additional dedicated fixed clocked outputs (inc MIDI Clock out).



PEXP-1 Features:

- 4HP
- Din socketed Din Sync and MIDI Clock dedicated outputs.
- 4 extra buffered fixed gate outputs – x1, x2, x4 & /4

PEXP-2 Features:

- 2HP
- 3.5mm jack socketed MIDI Clock output
- MIDI wiring orientation switchable (for differing 3.5mm wiring setups)
- Buffered x24 & run jack outputs

Neither of the expanders will work with the original Pamela!

For more info visit - busycircuits.com/alm017-ex

Retail pricing looking like ~ PEXP1 $115 / PEXP2 75$ (UK pricing tbc)

Also the Pamela Manual covers the expanders.

Beginning to ship to stores TODAY.

Please check the ALM Instagram and Twitter (links below) for more demo vids and the like.
strange tales
Don't know if it has been mentioned yet, what's the price on this new version?

Quote:
Unlikely to actually improve aerobic fitness.

waah
ALM
Sorry - updated now with pricing!
davide3737
ALM wrote:
New Pam is finally here !


Excellent!

Has the digital noise problem with the original Pamela been resolved?

When will it be shipping to distributors?
exper
ALM wrote:
Sorry - updated now with pricing!


Glad to see this out. The good thing is that it does so much more that it wouldn't be a bad idea to hang on to your original PW and add the new one.
noisejockey
Wow. Really nice job, ALM. Your ideas for improvements and expansion make total sense.

Even more excited once I read the manual! Built-in attenuation of the waveforms, banks of saved settings, external modulation of the internal modulators, mini USB updating of firmare...makes just want to hug y'all. I can't believe it's no bigger than the original.

Hats off to you.

thumbs up
strange tales
exper wrote:
ALM wrote:
Sorry - updated now with pricing!


Glad to see this out. The good thing is that it does so much more that it wouldn't be a bad idea to hang on to your original PW and add the new one.


Definitely intend on doing this. Leaving original Pam for clocks and divisions and going wild with this thing. It's awesome you can self patch the clocked waveforms into the CV inputs on the new Pam.
ALM
davide3737 wrote:

Has the digital noise problem with the original Pamela been resolved?


The hardware is completely different.

As well as local testing, there was an initial early run of 10 units for Beta testers with testing across a wide range of supplies with no reported noise (or other) issues.

davide3737 wrote:

When will it be shipping to distributors?


Beginning to ship to stores TODAY! (will update post)
noisejockey
strange tales wrote:
exper wrote:
ALM wrote:
Sorry - updated now with pricing!


Glad to see this out. The good thing is that it does so much more that it wouldn't be a bad idea to hang on to your original PW and add the new one.


Definitely intend on doing this. Leaving original Pam for clocks and divisions and going wild with this thing. It's awesome you can self patch the clocked waveforms into the CV inputs on the new Pam.


Someone's gotta try some self-patched audio rate basslines with this thing. :-)
davide3737
ALM wrote:
davide3737 wrote:

Has the digital noise problem with the original Pamela been resolved?


The hardware is completely different.

As well as local testing, there was an initial early run of 10 units for Beta testers with testing across a wide range of supplies with no reported noise (or other) issues.

davide3737 wrote:

When will it be shipping to distributors?


Beginning to ship to stores TODAY! (will update post)


Terrific +2!
bwhittington
How well does the MIDI clock out on the PEXP-1 follow tempo changes from the clock input? I would be completely enthralled by a video illustrating this feature.
ALM
bwhittington wrote:
How well does the MIDI clock out on the PEXP-1 follow tempo changes from the clock input? I would be completely enthralled by a video illustrating this feature.


See https://vimeo.com/204926725
evs
SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger! SlayerBadger!
Paranormal Patroler
Does this contain more clock divisors and multipliers than the original Pam? Says something about non integer options ...
propertyof
phase!! now i know which clock module that i want! w00t

anyway is it still made in england?
curious since it didn't state it like other ALM modules.
ALM
Paranormal Patroler wrote:
Does this contain more clock divisors and multipliers than the original Pam? Says something about non integer options ...


Should be all the originals included.

New ones include /5.3, /2.6, /1.5, x1.3, x1.5, x2.6, x5.3

There is also a /512 divider (cant remember if original pam went that low) and a x48
ALM
propertyof wrote:

anyway is it still made in england?


Yes! I will add.
Battagiovi
WAAAAANT IT SOOOOOOOOOOOOO BAAAAAAAAADDDDDD!!!!!!!

Dead Banana
nimmen
noisejockey wrote:
strange tales wrote:
exper wrote:
ALM wrote:
Sorry - updated now with pricing!


Glad to see this out. The good thing is that it does so much more that it wouldn't be a bad idea to hang on to your original PW and add the new one.


Definitely intend on doing this. Leaving original Pam for clocks and divisions and going wild with this thing. It's awesome you can self patch the clocked waveforms into the CV inputs on the new Pam.


Someone's gotta try some self-patched audio rate basslines with this thing. :-)

Guinness ftw! that sounds like side effect towards "improved aerobic fitness."
tebs213
This looks really impressive. Very excited for some demo videos. I'm trying to be strict about keeping my system a certain size for now and this might really open things up! Thinking about this with a quantizer would be a lot of fun in particular.
Paranormal Patroler
I really appreciate that you made the Pexp-2 to work with both Arturia and Korg. This TRS-to-MIDI standardization has been a pain in the ass for me, I'm writing an article about it hoping to get all Eurorack manufacturers to adhere to one standard. It's nice to see that you took the clever way out, thank you for that.
bobbcorr
Pexp-1 added to Modulargrid. Please review and edit as necessary, thx.
bobbcorr
Can you see a scenario in which you would need BOTH Pexp-1 and Pexp-2?
wonkychris
This looks like a huge improvement, with the Euclidean or division/multiply options and modulation. Extra straight clock out expanders also a big win.

I sold my old one as I couldn't get it to sync right to a clock (specifically an much tanzbar but I also tried a few others). Guess that's sorted now.

It's great having midi clock out but would be really awesome if that could also be used as midi clock in. Any chance?
Paranormal Patroler
Manual and site disagree on the Expanders' requirements on power. Site says Pexp-1 needs 15mA and Pexp-2 needs 25mA and manual says the opposite. Also, page 7 of the manual, first paragraph has "before before". Sorry, I write manuals for a living these days. I found a couple of other small mistakes, ALM let me know if interested.
resynthesize
Interesting, I looked closely at the original pam and octocontroller a few months ago when I needed a clock module. I opted for octocontroller because of the additional synced output types. but the one thing I wish the octocontroller had was cv for some of the type parameters (rate, phase, etc). I suspect we might be seeing some octocontrollers in BST soon.
ALM
Thanks - fixed ! The manual is correct re power consumption. website updated.

Paranormal Patroler wrote:
Manual and site disagree on the Expanders' requirements on power. Site says Pexp-1 needs 15mA and Pexp-2 needs 25mA and manual says the opposite. Also, page 7 of the manual, first paragraph has "before before". Sorry, I write manuals for a living these days. I found a couple of other small mistakes, ALM let me know if interested.
ALM
bobbcorr wrote:
Pexp-1 added to Modulargrid. Please review and edit as necessary, thx.


Thank you! I need to fix power - my bad. Sorry.
Paranormal Patroler
ALM wrote:
bobbcorr wrote:
Pexp-1 added to Modulargrid. Please review and edit as necessary, thx.


Thank you! I need to fix power - my bad. Sorry.


I added Pexp-2, kept power to 15mA. Not sure if depth is indeed 38mm, do check. Thanks.
ALM
bobbcorr wrote:
Can you see a scenario in which you would need BOTH Pexp-1 and Pexp-2?


Note they are exclusive - you could maybe chain with a special cable but never tried!
albiedamned
I used the Rotate setting on the old Pam a lot, but I don't see that in the manual for the New Pam. I'm assuming there's probably another way to do this though. Can you explain?

Also one other question - what is the Envelope shape? Is it like a trapezoid maybe, with an attack, sustain, and release stage?
ALM
albiedamned wrote:
I used the Rotate setting on the old Pam a lot, but I don't see that in the manual for the New Pam. I'm assuming there's probably another way to do this though. Can you explain?


You can rotate the Euclidean patterns. This should cover prior usage? Also Phase setting.

albiedamned wrote:

Also one other question - what is the Envelope shape? Is it like a trapezoid maybe, with an attack, sustain, and release stage?


Its a simple decay only percussive type envelope.
rustyjaw
Wow this sounds sweet. The original Pam has been clocking my modular since I first got it. Sounds like this is a very worthy update!
albiedamned
ALM wrote:
albiedamned wrote:
I used the Rotate setting on the old Pam a lot, but I don't see that in the manual for the New Pam. I'm assuming there's probably another way to do this though. Can you explain?


You can rotate the Euclidean patterns. This should cover prior usage? Also Phase setting.


Does Euclidean mode respect the other settings, like width? In the old Pam's, Euclidean mode was always just a trigger. The use case I am thinking of is wanting to send a 100% step width gate every 4th beat or something similar.

ALM wrote:
albiedamned wrote:

Also one other question - what is the Envelope shape? Is it like a trapezoid maybe, with an attack, sustain, and release stage?


Its a simple decay only percussive type envelope.


So doesn't that make it the same as a fully skewed triangle?
ALM
albiedamned wrote:


Does Euclidean mode respect the other settings, like width? In the old Pam's, Euclidean mode was always just a trigger. The use case I am thinking of is wanting to send a 100% step width gate every 4th beat or something similar.



Yes Euclidean does respect. So in your example, you could do a 1 trig in 4 step Euclidean Pattern and then rotate as required. You'd set width to 100%.

Alternatively you'd do a 25% at a 1/4 of the speed and then alter the phase or delay.

albiedamned wrote:



So doesn't that make it the same as a fully skewed triangle?


No as skewed triangle would be linear (env is exponential) and you couldn't alter the decay time (tri width skews, env width changes decay time).
albiedamned
Awesome! Thanks for the answers.
bobbcorr
ALM wrote:
bobbcorr wrote:
Pexp-1 added to Modulargrid. Please review and edit as necessary, thx.


Thank you! I need to fix power - my bad. Sorry.


Miley Cyrus
igowen
preordered the heck out of this! as much as i love the old-school flair of the display on the original pam, this looks like it adds a boatload of functionality with no additional HP cost. can't wait! It's peanut butter jelly time!
albiedamned
Pre-ordered. And I never pre-order anything.
nickbaba
where are you guys pre-ordering these?

I can't find it listed at any of the stockists...
rikrak
Any idea where I can pre-order in the UK?
digits
nickbaba wrote:
where are you guys pre-ordering these?

I can't find it listed at any of the stockists...


Control NY - preordered mines too.
atte
I'm pretty sure I'm looking at my new clock module

Anyone wants to buy my tempi?
Paranormal Patroler
atte wrote:
I'm pretty sure I'm looking at my new clock module

Anyone wants to buy my tempi?


Ha! Called it. hihi (when the Tempi came out I was amazed why people hadn't been using the old Pam this way).
nickbaba
Ah OK, I see - yeah, me UK too

Can't find any UK pre-order... guess Matt will have them but he doesn't do pre's
Outtatune
Help a brother out here... is there anything a Batumi can do that this can't?
Footkerchief
Outtatune wrote:
Help a brother out here... is there anything a Batumi can do that this can't?


Batumi has independent voltage control of all four channels, enabling all kinds of cross-modulation etc.
ugokcen
Batumi can do free running (unsynced) lfos and has sliders so you can manipulate the lfo rates in real time. It also has 12 outputs as opposed to 8 on the Pam's.

I've been using Batumi for clocking Rene and I'm definitely going to get the new Pam for that. Batumi can then go back to lfo duties like vibrato, pwm etc. Best of both worlds love
Outtatune
I need both. Got it! smile My case is full so I was looking at what 8HP of clock-related kit can be swapped out for this. Perhaps my A-160-2 & A-160-5. Hmmmm...
propertyof
rikrak wrote:
Any idea where I can pre-order in the UK?

nickbaba wrote:
Ah OK, I see - yeah, me UK too

Can't find any UK pre-order... guess Matt will have them but he doesn't do pre's


Rubadub has it listed for pre-order. including the expander.
http://www.rubadub.co.uk/catalogsearch/result/?q=pamela
skeller047
Just pulled trigger on pre-order. CONTROL gonna be bizzzzeeeee....
rikrak
propertyof wrote:
rikrak wrote:
Any idea where I can pre-order in the UK?

nickbaba wrote:
Ah OK, I see - yeah, me UK too

Can't find any UK pre-order... guess Matt will have them but he doesn't do pre's


Rubadub has it listed for pre-order. including the expander.
http://www.rubadub.co.uk/catalogsearch/result/?q=pamela


Excellent - cheers!
digits
Detroit Modular has them for preorder too, they're also good people worth supporting!
hawkfuzz
Forgive my stupidity. This puts out syncable LFOs and random CV? Not just a pulse?
Vcoadsr


https://youtu.be/2w--qmhEqxE

A short ambient drone demo using only Pamela's New Workout for all CV duties/modulation. Using the Randon CV mode + the Loop mode (think Turing machine) for the reoccurring melody parts, Sine/triangle/saw LFOs for Akemie's Castle modulation & gates to the Taiko's.

I've been using a pair of these for the last 3 months during the beta testing and they have become the clock & modulation heart of my system. My guess is this will become as ubiquitous as Maths.

(NOTE: The Pamela's New Workout in this video is a prototype hence the custom red encoder knob - this will be blue for the commercial production runs.)
ugokcen
Great patch Vcoadsr! Nice to see Pamela in action.

There's also a nice video posted on the ALM website, but to be honest it doesn't really explain what the module does. Hopefully someone will post a review soon.

Now the million dollar question: does Tempi offer any advantages over the Pamela's New Workout? With ridiculous number of division/multiplication options, plus the lfos, euclidian rhythms, and that nice screen it seems to me that ALM has built the quintessential clock module. But I know that there are many people who swear by Tempi so I'm curious...
evs
ugokcen wrote:
Great patch Vcoadsr! Nice to see Pamela in action.

There's also a nice video posted on the ALM website, but to be honest it doesn't really explain what the module does. Hopefully someone will post a review soon.

Now the million dollar question: does Tempi offer any advantages over the Pamela's New Workout? With ridiculous number of division/multiplication options, plus the lfos, euclidian rhythms, and that nice screen it seems to me that ALM has built the quintessential clock module. But I know that there are many people who swear by Tempi so I'm curious...


i think they build the quintessential clock module.
however, the only downside is, that it can not be clocked from a very very slow clock. maybe the tempi can..(?)
like you have a maths running, as a very slow lfo, and you would like to use the eoc as the main clock.
this would be not possible with the pam, as it can not go lower than 10bpm...

i somethimes whish it would, but i can live with that.
Vcoadsr
evs wrote:


i think they build the quintessential clock module.
however, the only downside is, that it can not be clocked from a very very slow clock. maybe the tempi can..(?)
like you have a maths running, as a very slow lfo, and you would like to use the eoc as the main clock.
this would be not possible with the pam, as it can not go lower than 10bpm...

i somethimes whish it would, but i can live with that.


The clock goes down to 10 BPM but then you can have a division of /512 at 10 BPM which would give you 1.17 beats per hour if I did my sums correctly. Pretty slow.
Tumulishroomaroom
Ahah indeed ! Can't for for this to hit Modularsquare's shelves
evs
Vcoadsr wrote:
evs wrote:


i think they build the quintessential clock module.
however, the only downside is, that it can not be clocked from a very very slow clock. maybe the tempi can..(?)
like you have a maths running, as a very slow lfo, and you would like to use the eoc as the main clock.
this would be not possible with the pam, as it can not go lower than 10bpm...

i somethimes whish it would, but i can live with that.


The clock goes down to 10 BPM but then you can have a division of /512 at 10 BPM which would give you 1.17 beats per hour if I did my sums correctly. Pretty slow.


No, you did not understand, I was not talking about the outgoing clock.
But about the ingoing clock. It's a matter of how you patch. If you always start with Pam it's no problem, no matter how slow your stuff is. If you start with something different and want to derive clocks from there and you have slow music, you can not use Pam.
hawkfuzz
Tempi's clock settings are delegated by buttons so that's easier than programming...but I think that might be the only advantage. I'm debating the switch....
High Wolf
Just to make sure, is it possible to have one output sending regular trig, one output sending a lfo, one sending a euclidean pattern and one sending enveloppes? Meaning every output is completely independent (except for the tempo)?
Vcoadsr
High Wolf wrote:
Just to make sure, is it possible to have one output sending regular trig, one output sending a lfo, one sending a euclidean pattern and one sending enveloppes? Meaning every output is completely independent (except for the tempo)?


Yep, 8 independent channels completely configurable It's peanut butter jelly time!
High Wolf
Vcoadsr wrote:
High Wolf wrote:
Just to make sure, is it possible to have one output sending regular trig, one output sending a lfo, one sending a euclidean pattern and one sending enveloppes? Meaning every output is completely independent (except for the tempo)?


Yep, 8 independent channels completely configurable It's peanut butter jelly time!


WOW...I really want NOT to want that as I've already have the old Pam but hard to resist!
nickbaba
RubaDub (UK) has them in stock today.
miles_macquarrie
Anybody keeping their old PAM while getting the new one as well?

I'm trying to figure out if I want to sell old for new or just add new. The original pam has always been the heartbeat clock device for me and they just upped the ante big time!
rustyjaw
I was about to order a multiway envelope generator, but I think the new Pam's will fill that need and more.

miles_macquarrie wrote:
Anybody keeping their old PAM while getting the new one as well?

I'm trying to figure out if I want to sell old for new or just add new. The original pam has always been the heartbeat clock device for me and they just upped the ante big time!


I can see keeping the original for clock mult/div duties. Also perhaps as a dedicated Euclidean sequencer, although I never upgraded the firmware on my original to allow this. I heard the firmware upgrade process can be a bit of a nightmare.
zolar_czakl
Vcoadsr wrote:
High Wolf wrote:
Just to make sure, is it possible to have one output sending regular trig, one output sending a lfo, one sending a euclidean pattern and one sending enveloppes? Meaning every output is completely independent (except for the tempo)?


Yep, 8 independent channels completely configurable It's peanut butter jelly time!


Hot damn I need this in my life SlayerBadger!
reflecto
Hopefully the clock input issues sorted out . I sold my mk1 because of that but would give this a try if it reports ok.
uebl
Wow, I was pretty set on getting something like a MN Tempi + XAOC Batumi for clocked modulation duties, but Pam's New Workout lets me seriously reconsider this. Some "menu diving" apart, what would you guys say are the disadvantaged of Pam's New Workout compared to said combination?
evs
uebl wrote:
Wow, I was pretty set on getting something like a MN Tempi + XAOC Batumi for clocked modulation duties, but Pam's New Workout lets me seriously reconsider this. Some "menu diving" apart, what would you guys say are the disadvantaged of Pam's New Workout compared to said combination?


what i said above.
in short: if you don´t want to use pam as a master clock and would like to have it synced to a very very slow clock: not possible. pam goes down to 10 bpm.
all clocks below this will not be accepted.
i see that this is for most people rarely the case.

about the menu diving: its super simple and the best menu you can imagine. i for instance hate menues. had the original pam, and it never was a problem. so intuitiv. and you don´t forget it, even after a long time of not using it..
pitri
Vcoadsr wrote:


https://youtu.be/2w--qmhEqxE



Where is that high pitch noise coming from thats constant all the way through? sounds like a LED hiss - hopefully not caused by the pams zombie
Vcoadsr
pitri wrote:


Where is that high pitch noise coming from thats constant all the way through? sounds like a LED hiss - hopefully not caused by the pams zombie


Hi Pitri,

I hadn't noticed it until I turned the volume right up!

It's 100% coming from the audio interface I was using (Audio Damage ODIO) that connects into my camera - it's categorically nothing to do with the modules in the video.

I double checked this morning and found that the constant high pitch tone is present on the ODIO when nothing is plugged into it - I use the ODIO for convenience when making these vids rather than having a second audio interface/mixer and on the whole it works fine for most things.
strange tales
Just preordered from Perfect Circuit. Now the waiting begins (and have an Akemie's Taiko coming with it as well) It's peanut butter jelly time! It's peanut butter jelly time! It's peanut butter jelly time!
rikrak
nickbaba wrote:
RubaDub (UK) has them in stock today.


Received mine from Rubadub this morning!

Racked it up but haven't had chance to play yet.
propertyof
Control NY has it in stock now. Looking forward for more demos of new pam!
hairychris
I preordered form Red Dog music in the UK... or, rather, I'd previously ordered a PW but they put my order on hold until the new version was released.

Looking forward to receiving it!
noisetheorem
This is one thing I hate about euro. Manufacturers constantly going to V2 with no upgrade path and killing value to the first adopters.

*sigh*.
Paranormal Patroler
noisetheorem wrote:
This is one thing I hate about euro. Manufacturers constantly going to V2 with no upgrade path and killing value to the first adopters.

*sigh*.


Wow. As a first owner of PW I'm a bit hard pressed to agree with you on this occasion. How many years has the first one been out? I mean, come on, it has had its run.

I see your point, but after years of having a module what did you expect? That ALM would never make a better version of it? The hardware and software has been redesigned. The original PW can't possibly do these things with an upgrade.

I think your criticism is fair in some occasions, but not here. Just my 2 cents.
InnnerSight
I had the first one and loved it. Sold it and picked up an Octocontroller.

Just picked up the new one and wow its a beast, on par so far with the octocontroller - although the one dial does hold it back a little, but neither have great interfaces in my opinion, although its difficult to create a great interface for something so small and complex.

All in all loving it.
rikrak
First impressions are great!

Interface is pretty much the same as Old Pam. The new screen is much more legible - though I did find the inverted "selected" text a bit difficult to read at first.

The only time I had to refer to the manual was to work out how to set attenuation when using CV inputs. You need to click once to highlight (eg.) "CV2" and then long-click to get into the CV2 modifiers for that Output. (As opposed to long-clicking when "CV2" is NOT highlighted, which takes you to the Output's settings).

I was able to quickly set up one output to send a ramp to the CV2 input which could then be used by the next output to ratchet my hihats! No need for a sequential switch. And by adjusting the width, phase, delay, etc you have fine control of exactly how you want the multiple triggers to be spaced.

It's a very well-thought out system. There is a mind-boggling amount of complexity in the new modifiers and the way the outputs and CV inputs can interact - but the interface feels even simpler to use than Old Pam and you can be microscopically precise.

I'm most excited by the possibilities of looping the Random Waveform and Random Skip parameters - that sounds VERY useful!
nucleus
InnnerSight wrote:
I had the first one and loved it. Sold it and picked up an Octocontroller.

Just picked up the new one and wow its a beast, on par so far with the octocontroller - although the one dial does hold it back a little, but neither have great interfaces in my opinion, although its difficult to create a great interface for something so small and complex.

All in all loving it.


Agreed, having the octocontroller here, it's a great module but not the best interface but yes how can one put all the functionality and a great interface in a small module? Functionality wise i think it does a really good job i know i really liked mine right when i bought it. I read into pam's description and it looks very good itself.

noisetheorem wrote:
This is one thing I hate about euro. Manufacturers constantly going to V2 with no upgrade path and killing value to the first adopters.

*sigh*.


Pam has been around since i entered eurorack i think its upgrade is not bothersome at all. Same with the morphogene. Their predecessor have been around for years. Some upgrades are way to quick though and render the previous modules almost undesirable on the market.
rikrak
nucleus wrote:
Well, look at disting 4. Pam has been around since i entered eurorack i think its upgrade is not bothersome at all. Same with the morphogene. Their predecessor have been around for years. I bought disting 3 when it became more available with distributors last year, i hardly feel i had it long enough in my rack and now disting 4 is out, rendering the 3 almost undesirable on the market. So i think my purchases 2 times now.


Expert Sleepers have said they will continue releasing firmware for V3 (there was a firmware upgrade just the other day!) - and given how much there is packed in to it, I can't see it becoming useless at any point - regardless of how long they continue to support it.

That said, I hope people continue to stick V3's up for sale because I would gladly buy another 2!
nucleus
rikrak wrote:
nucleus wrote:
Well, look at disting 4. Pam has been around since i entered eurorack i think its upgrade is not bothersome at all. Same with the morphogene. Their predecessor have been around for years. I bought disting 3 when it became more available with distributors last year, i hardly feel i had it long enough in my rack and now disting 4 is out, rendering the 3 almost undesirable on the market. So i think my purchases 2 times now.


Expert Sleepers have said they will continue releasing firmware for V3 (there was a firmware upgrade just the other day!) - and given how much there is packed in to it, I can't see it becoming useless at any point - regardless of how long they continue to support it.

That said, I hope people continue to stick V3's up for sale because I would gladly buy another 2!


I am happy to hear that. I hardly had time to discover mine fully and i know they announced it on their website they will develop their algorithms for both v3 AND v4 which is great. Would be nice to see expert sleepers continue their support for it but i would understand focusing their attention on their latest offering, the v4. I've seen people say they would be happy to have both in their systems. Good for expert sleepers, their product line is great both for disting and for integrating modular with your daw.
nucleus
double post
Recitative
Can it do dotted 8th notes?

(either the new or the old PW)
ALM
Recitative wrote:
Can it do dotted 8th notes?

(either the new or the old PW)


New Pam thats the 1.3 Multiplier iirc.

Old Pam can't do.
Recitative
I suppose my math is wrong, I thought it would be:

X .75
ALM
Recitative wrote:
I suppose my math is wrong, I thought it would be:

X .75.

I would think 1.3 would be a quarter triplet?


But that would mean x2 would be X.5

Your essentially dividing by 1 for it to be a multiplier (i.e for above 1/.5 = x2)

Thus;

0.75= 3/4, 1/(3/4) = 4/3 = 1.33333 =~ 1.3

Quarter triplet is x1.5 (2/3..)

hmmm..... hmmm..... hmmm.....
Recitative
Thanks.
rikrak
I see the ppqn is set to 24 rather than 48, by default.

Is there any advantage to 24 over 48, other than compatibility with MIDI?
ALM
rikrak wrote:
I see the ppqn is set to 24 rather than 48, by default.

Is there any advantage to 24 over 48, other than compatibility with MIDI?


And Din Sync.

48 is there as was (rarely) requested feature for original Pam which couldn't really manage it. Im not sure what uses a x48 clock by default (Korg stuff maybe?). Its not been as tested as much as the 24.
Paranormal Patroler
You get 3 pulses per 32nd note. I mean, that's all one ever needs. Can't imagine anyone needing to move 64ths left or right in time.
rikrak
Thanks. I'm having a lot of fun with this module so far!
skeller047
Paranormal Patroler wrote:
You get 3 pulses per 32nd note. I mean, that's all one ever needs. Can't imagine anyone needing to move 64ths left or right in time.
Slightly OT, but you should see some of the stuff I had to play as a student - some guy once tried to notate jazz swing feel in quadruple time which he interpreted as 3 parts & 2 parts, tied together, of a 64th 5-tuplet. I just played it as jazz 8th notes, and he said it was right... A simple "4x-time swing" notation would have been easier to read.
Chickenbone
Aw man I should have waited to buy a Pam's. I was waiting around for it to show up in bst and once I found and bought one I see this and now V1 is selling $20 cheaper zombie
Paranormal Patroler
skeller047 wrote:
Paranormal Patroler wrote:
You get 3 pulses per 32nd note. I mean, that's all one ever needs. Can't imagine anyone needing to move 64ths left or right in time.
Slightly OT, but you should see some of the stuff I had to play as a student - some guy once tried to notate jazz swing feel in quadruple time which he interpreted as 3 parts & 2 parts, tied together, of a 64th 5-tuplet. I just played it as jazz 8th notes, and he said it was right... A simple "4x-time swing" notation would have been easier to read.


That just goes to show that people need help when notating. I know I've had my teachers cry a few times when reading my scores. Not everything makes sense, so the rule of thumb is a) ask b) keep it simple
funqpatrol
Will it be possible to recall a set of output with CV ala Tempi?
atte
Are these in stock anywhere in EU? Schneiders says anout 4 weeks, EFN doesn't know when it arrives...
ALM
atte wrote:
Are these in stock anywhere in EU? Schneiders says anout 4 weeks, EFN doesn't know when it arrives...


Schneiders & EFN should be more like end of the week / beginning of next.
atte
Sounds great, thanks! I have a gap waiting!

How does it work, will both schneiders and EFN receive stock or does it depend on whether they already ordered or not?
ALM
Yep they have both placed orders.
atte
Amazing! Thanks again applause
bisquick
Sorry if this has been answered, but is it possible to program your own specific patterns? I see that there are LFOs and Euclidean options, but what about your own user-specified pattern? I'd imagine that it's not really made to do that, but maybe it's possible by uploading your own custom waveform or something?
BonJoey
funqpatrol wrote:
Will it be possible to recall a set of output with CV ala Tempi?


I'd also like to know the answer to this
ALM
bisquick wrote:
Sorry if this has been answered, but is it possible to program your own specific patterns? I see that there are LFOs and Euclidean options, but what about your own user-specified pattern? I'd imagine that it's not really made to do that, but maybe it's possible by uploading your own custom waveform or something?


You can 'program' custom patterns by means of the clock modifier, euclidean, looping, random skip etc - all of which also have direct & voltage control.

A waveform is used by a pattern as its output 'shape' - of which you can 'program' by changing its type, level, phase, delay etc again directly or by voltage control.

You cannot upload custom waveforms.
ALM
BonJoey wrote:
funqpatrol wrote:
Will it be possible to recall a set of output with CV ala Tempi?


I'd also like to know the answer to this


Havn't yet got CV controlled loading working in a way Im happy with.
gavechase
So far I'm loving this module, but I have noticed one issue with saving presets. I can't access the extended adjustments if a channel modifier is set to, Off, On, Start Pulse, or Off Pulse. This means that I can't save that channel setting as a preset. Also, if I choose to save all outputs, any channels that use these utility modifiers are not saved.

It's a minor quibble, but it would make saving presets for controlling external gear (I'm clocking a BeatStep Pro and resetting various sequencers with these utility modifiers) possible.
rupa
This module has better ideas than I do. Outstanding.

In order to add something useful i wrote down all the div/mults i could find:

512 384 256 128 96 64 56 48 40 32 29 27 25 24 23 21 19 17 16-6 5.3 5 4 3 2.6 2 1.5 1 1.3 1.5 2 2.6 3 4 5.3 6 8 12 16 24 48
dumbledog
Mine just shipped. So lowest is 10bpm, largest division is 512.... so can this thing make an LFO that cycles once every 51.2 minutes?

E: and a 240Hz drone?
ALM
gavechase wrote:
So far I'm loving this module, but I have noticed one issue with saving presets. I can't access the extended adjustments if a channel modifier is set to, Off, On, Start Pulse, or Off Pulse. This means that I can't save that channel setting as a preset. Also, if I choose to save all outputs, any channels that use these utility modifiers are not saved.


Nice find. Will get a fix sorted. Maybe also add some relevant parameter control (level / delay etc) .

The global 'bank' save may work for you in the interim ?
gavechase
ALM wrote:

Nice find. Will get a fix sorted. Maybe also add some relevant parameter control (level / delay etc) .

The global 'bank' save may work for you in the interim ?


The global bank save does not appear to retain the utility modifier settings either. When I get back to my rack I'll start with a global reset and do some more extensive testing so that I can let you know definitively.

The rest of the module's functions are very well sorted, I appreciate the attention to detail, especially with the CV inputs. Keep up the good work!
ALM
gavechase wrote:

The global bank save does not appear to retain the utility modifier settings either.


Yep your right - sorry. Am on it.
atte
ALM wrote:
gavechase wrote:

The global bank save does not appear to retain the utility modifier settings either.


Yep your right - sorry. Am on it.


So no "send me a patch description + video, then suspect it's the user doing something wrong, then admit it's a bug and suggest a work around"-dance?

I only have three ALM modules (a fourth on the way), and loving them so hard. And this kind of attitude makes me love love them and ALM even more. Other manufacturers (even big ones) could really learn something from such a caring and supportive company.

Thank you ALM, you're the best thumbs up
gavechase
ALM wrote:
Yep your right - sorry. Am on it.


No worries. Given the complexity of the module this is the only bug I've come across, everything else works a charm.

So I had a few minutes to methodically test the save and load features for each utility modifier as well as CV1 and CV2. I have not tested any of the extended adjustments for regular trigger dividers/multipliers, but those generally seem to save and load just fine.

Here's a list of each modifier, whether or not it has an extended adjustment (and the ability to save that individual output), and what shows up on that output if I Save an entire bank and then Load the same global bank.

Modifier, Extended Adjustment, Replaced upon Full Bank Load
Off, No, x48
On, No, x1
StartPulse, No, x1
StopPulse, No, x1
CV1, Yes, /512
CV2, Yes, /9

I hope this is useful for you.
ALM
gavechase wrote:

I hope this is useful for you.


Yes thank you!
igowen
haven't had a huge amount of time to play with mine yet, but so far the flexibility of this thing is just ridiculous. the ENV wave type covers like 75% of what i had been using old pams+maths for. well done ALM! screaming goo yo
atte
Just ordered, can't wait w00t
Paranormal Patroler
atte wrote:
Just ordered, can't wait w00t


SlayerBadger!
L.C.O.
This may be an obvious question, but:

does the module retain the current settings on power cycle?

Thank you!

(I am considering getting this after the new revisions!)
ALM
L.C.O. wrote:

does the module retain the current settings on power cycle?


Yes - all ALM modules do cool
Paranormal Patroler
ALM wrote:
L.C.O. wrote:

does the module retain the current settings on power cycle?


Yes - all ALM modules do cool


SlayerBadger! And that's why we love the original PW as well as the new one. Bloody brilliant.
L.C.O.
ALM wrote:
L.C.O. wrote:

does the module retain the current settings on power cycle?


Yes - all ALM modules do cool


I suspected as much,
But wanted to be %100 clear.
Thank you!
albiedamned
Does the random skip function on the new Pam's work better than the original? I remember on the original, even if you dialed it all the way up to 9, it wouldn't skip that much. I used to set two outputs to 9 and AND them together to get a higher skip rate.
The Illuminaire
Mine should be here any minute now. Sadly, I'm at the office for the next ten hours. So I'll just be staring at it on my lunch break. Hahaha. ::cries internally::
atrostor
L.C.O. wrote:
ALM wrote:
L.C.O. wrote:

does the module retain the current settings on power cycle?


Yes - all ALM modules do cool


I suspected as much,
But wanted to be %100 clear.
Thank you!


After all, you are the patron saint of state-keeping modules. lol
L.C.O.
atrostor wrote:
L.C.O. wrote:
ALM wrote:
L.C.O. wrote:

does the module retain the current settings on power cycle?


Yes - all ALM modules do cool


I suspected as much,
But wanted to be %100 clear.
Thank you!


After all, you are the patron saint of state-keeping modules. lol


Don't know about "saint", but I am determined to keep the issue on the table! I really see a positive change overall: meaning that more and more people are realizing just how important this is.
I am a firm believer in conversation/dialogue as a catalyst for positive change, so yes: you can count on me asking that question ;-)
albiedamned
albiedamned wrote:
Does the random skip function on the new Pam's work better than the original? I remember on the original, even if you dialed it all the way up to 9, it wouldn't skip that much. I used to set two outputs to 9 and AND them together to get a higher skip rate.


Mine arrived today, so I'll answer my own question. The random skip function is much better. You enter a percentage of 0 to 100, and from my brief experimentation just now, the frequency of the skips does seem to match the percentage you selected.

Also, this module is awesome. It took me about 2 minutes to figure out the interface. I normally shy away from complex modules with menus, but just like the original Pam, this one is so simple that it's not an obstacle for me at all. And the new features are amazing. I'm loving the wave forms and the built-in euclidean settings. I need to check out what I can do with the CV control.

I can also report that it synced perfectly to my BeatStep Pro using 24 ppqn, but I never had problems syncing my old Pam to my BSP either.
BonJoey
I got mine yesterday. I've barely even scratched the surface of things it can do, but I already love it.
L.C.O.
Oh crap.
Just went to CONTROL to buy it, and it is sold out!
Are these available anywhere at the moment?
propertyof
L.C.O. wrote:
Oh crap.
Just went to CONTROL to buy it, and it is sold out!
Are these available anywhere at the moment?

if you don't mind buying from UK, Rubadub & Cymru Beats still have it in stock.
Chartreuse-J
Detroit Modular still has them for preorder

Email Shawn at AH, probably got a few there.
L.C.O.
propertyof wrote:
L.C.O. wrote:
Oh crap.
Just went to CONTROL to buy it, and it is sold out!
Are these available anywhere at the moment?

if you don't mind buying from UK, Rubadub & Cymru Beats still have it in stock.


Thanks for the tip.
Ordered.
Will see how the shipping situation plays out.
brandonlogic
perfectcircuitaudio also has them for preorder.
just got mine in for the new pam and 2hp expander.
loved the old pam, couldnt resist to update to the new one!
boramx
Hey folks-
Can pam run from two or three gates tapped into the clock input? That is often my preferred way to set tempos.
albiedamned
boramx wrote:
Hey folks-
Can pam run from two or three gates tapped into the clock input? That is often my preferred way to set tempos.


I'm pretty sure the answer is no. It needs a continuous clock signal.
Southfork
Ordered. Thought had to try this vs temps utile. Will decide on which once I fire both up!
The Illuminaire
I already need another... MY ASS IS BLEEDING

This has quickly became the heart of my system. I need another to dedicate to modulation duties. SlayerBadger!
mutierend
I got lucky and bought my Pamela's New Workout from Control right before they ran out of stock. So glad I got it when I did as I was in desperate need of a stable clock source. I plan to use it to clock my MIDI gear as well.
analoglsd
FYI: Detroit Modular has them in stock currently.
ALM
albiedamned wrote:
boramx wrote:
Hey folks-
Can pam run from two or three gates tapped into the clock input? That is often my preferred way to set tempos.


I'm pretty sure the answer is no. It needs a continuous clock signal.


I think it may actually work if you lower the expected PPQN to 1.
albiedamned
I recorded a song using all 8 outputs of my New Pam tonight. I used quite a few different features - euclidean mode, all the different waveform types (gate, sine, tri, envelope, random), and random skip. I did not do anything with the CV inputs yet. Here's the track, and a more detailed description is below.

[soundcloud url="https://api.soundcloud.com/tracks/312481109" params="auto_play=false&hide_related=false&show_comments=true&show_use r=true&show_reposts=false&visual=true" width="100%" height="450" iframe="true" /]

1: /2, gate, 2 of 3 Euclidean pattern triggering Rings.
2: /2, gate, 5 of 6 Euclidean pattern triggering an envelope (Quadra) which feeds the CV input of an LxD. I didn't like the way the built-in envelope sounded for this part, so I triggered the Quadra envelope instead.
3: /8, triangle wave, modulating the Fold CV of an Ultrafold (used for the 5 of 6 Euclidean pattern sound).
4: /4, sine wave, modulating the Shift CV of the Ultrafold.
5: x1, gate, triggering three different envelopes used for the kick sound.
6: /8, random, feeding a RYO VC Sequencer in CV mode to select one of the 8 steps randomly. The Sequencer goes to a Ladik quantizer and then into a Synth Tech E350 (the lead voice).
7: x4, random, modulating the E350's Morph X input.
8: x4, envelope, random skip 25%, controlling the hi hat.

Recorded in a single take. A little delay and reverb from a Lexicon MX200. No other processing.
brandonlogic
ALM do you know approximately when retailers will get the next batch of these?
Thanks
ALM
brandonlogic wrote:
ALM do you know approximately when retailers will get the next batch of these?
Thanks


Next run is approx 6 weeks away, maybe longer. Doing best to make this happen asap.

Cymru beats have some in UK.

EFN + Schneiders maybe have some left in Europe.

Analog Haven are due a last of initial run likely next week. Detroit Mod maybe have some left.

Think thats it currently. Everyone else sold out.
propertyof
ALM will the next batch have a new firmware updated?
ALM
propertyof wrote:
ALM will the next batch have a new firmware updated?


Im not sure - there is no updated firmware as yet hyper !

If there is though existing units are easily updated via usb connection on side of module.
capski
This thing is amazing. Received this past Saturday from Perfect Circuit (I think I was lucky with an early round pre-order). Only had a couple of hours with it before i had to go out of town for work but basic first patch was just sending it to rings and turing machine. So intuitive.

https://www.instagram.com/p/BRhOvdbDnDm/

Back now ready to push it more. Have an akemie's taiko on the way too - excited to get em going together.
L.C.O.
L.C.O. wrote:
propertyof wrote:
L.C.O. wrote:
Oh crap.
Just went to CONTROL to buy it, and it is sold out!
Are these available anywhere at the moment?

if you don't mind buying from UK, Rubadub & Cymru Beats still have it in stock.


Thanks for the tip.
Ordered.
Will see how the shipping situation plays out.


I have to say that I am totally impressed with Rubadub!
I payed for the module on Monday, and it is in my hands on Wednesday... shipping from UK to USA. This is faster than getting orders from some of the US retailers!

PompeiiRuler
Good to hear about Rubadub's speediness. Just ordred P'sNW off them today. Better start rearranging my rack now!
Southfork
Not going to lie, love this module. Intuitive and ships modulation aswell as clocks, absolute power house.

One thing, I know it's in keeping with the retro feel of the original but why the red oled? It's too dark! Especially compared to o_c, shapeshifter etc. Is it the red Perspex screen? Can it be changed?

Btw best PCB Ever, baby pink with Pamela posing and smiling back at me, made me giggle Miley Cyrus
atte
Just racked my new pam yesterday, and although I haven't had a chance to use it much, I already love it. It syncs rock steady with a clock from my BSP, and navigation seems super easy.

Can't wait to try out all the cool things this module has to offer!
lineidle
ez troops - Aleks at Rubadub here... just confirming we do still have stock just in case that wasn't already clear smile
L.C.O.
Southfork wrote:
Not going to lie, love this module. Intuitive and ships modulation aswell as clocks, absolute power house.

One thing, I know it's in keeping with the retro feel of the original but why the red oled? It's too dark! Especially compared to o_c, shapeshifter etc. Is it the red Perspex screen? Can it be changed?

Btw best PCB Ever, baby pink with Pamela posing and smiling back at me, made me giggle Miley Cyrus


I disagree.
The red display is great.
I appreciate the fact that it does not burn my retinas out, like somemodules do. And the design is really top notch: colors, layouts, even the type style on the display: all looks fantastic to me.

And of course: no need to think about recall or saving with the power cycles! It just does it. Beautiful example on how to seamlessly integrate digital functionality into an "analogue" tactile environment.

Great job ALM!
resynthesize
Is it possible to reduce the time required to push+hold the program knob to flip between the extended and regular settings? I think it could be 0.5 or even 0.25 seconds instead of 1 second and still work fine, switching back and forth between them right now feels sluggish currently (and I find myself doing it alot). Great module otherwise!
Recitative
Advantages or disadvantages to using PAM as an alternative to individual clock divider and multiplier modules?
VZvision
Recitative wrote:
Advantages or disadvantages to using PAM as an alternative to individual clock divider and multiplier modules?


That's a long list. Racked mine a few days ago and off the top of my head:

1. Euclidean rhythms on-board. Would require careful (and multiple) logic functions to replicate on something like a RCD.

2. Modifiable width per channel. Vanilla clock dividers are usually fixed.

3. Saving/loading differing timing arrangements

4. CV inputs that are not just shift/rotate functions since the CV's can be assigned to different parameters. Self patching CV within the module as well is not limited to just triggers modulating outputs since you can output syncable waveforms.

5. Syncable waveforms are selectable per channel, so 4 outs can be standard divisors/multiples while another 4 can send synced waveforms/envelopes/gates to modulation destinations in your system. Ex. Opening a filter or stepping through a switch FM'ing an oscillator via VCA every 8th step (or in a euclidean fashion if you have #1 active)

Guranteed there's more but that was just after two days of fucking around. The workout is only in warm up mode. In keeping with an older part of this thread....

evs
Recitative wrote:
Advantages or disadvantages to using PAM as an alternative to individual clock divider and multiplier modules?


only (?) disadvantage:
you can not use really slow clocks on the input. 10bpm is the slowest.
if you make slow drone stuff thats too fast. than you need to take PAM as the master. (it can output very slow clocks of course.. just not take it..)
Zymos
Just ordered from Detroit Modular, and had a 7 buck credit in my account!
rupa
resynthesize wrote:
Is it possible to reduce the time required to push+hold the program knob to flip between the extended and regular settings? I think it could be 0.5 or even 0.25 seconds instead of 1 second and still work fine, switching back and forth between them right now feels sluggish currently (and I find myself doing it alot). Great module otherwise!


+1 to seeing if the extended/regular switching can be faster while keeping it unsurprising. Would make a great thing even nicer!
evs
resynthesize wrote:
Is it possible to reduce the time required to push+hold the program knob to flip between the extended and regular settings? I think it could be 0.5 or even 0.25 seconds instead of 1 second and still work fine, switching back and forth between them right now feels sluggish currently (and I find myself doing it alot). Great module otherwise!


+1
Southfork
Recitative wrote:
Advantages or disadvantages to using PAM as an alternative to individual clock divider and multiplier modules?


Well if you had say an rcd and scm you'd have double the outputs. They'd be at fixed intervals though.
Recitative
Southfork wrote:
Recitative wrote:
Advantages or disadvantages to using PAM as an alternative to individual clock divider and multiplier modules?


Well if you had say an rcd and scm you'd have double the outputs. They'd be at fixed intervals though.



It would be sweet if the next version of PAM has an extra 4 outputs. 8's not quite enough.
albiedamned
Recitative wrote:
Southfork wrote:
Recitative wrote:
Advantages or disadvantages to using PAM as an alternative to individual clock divider and multiplier modules?


Well if you had say an rcd and scm you'd have double the outputs. They'd be at fixed intervals though.



It would be sweet if the next version of PAM has an extra 4 outputs. 8's not quite enough.


The current one has been out for a month and you already want the next one? What do you think this is, a Disting?
Recitative
I don't have the new one, only the old one. But, if ALM is going to improve on this already wonderful module, more outputs would be great.
atte
Recitative wrote:
I don't have the new one, only the old one. But, if ALM is going to improve on this already wonderful module, more outputs would be great.


Buy two?
rikrak
Recitative wrote:
Southfork wrote:
Recitative wrote:
Advantages or disadvantages to using PAM as an alternative to individual clock divider and multiplier modules?


Well if you had say an rcd and scm you'd have double the outputs. They'd be at fixed intervals though.



It would be sweet if the next version of PAM has an extra 4 outputs. 8's not quite enough.


You know what the solution to that is... 2 Pams! nanners

What an incredible module though. The CV1 and 2 inputs are key to unlocking its power. Try patching one of the outputs into CV1 or 2 and then use that to control multiple parameters across the other channels. By varying the Offset and Attenuation on each parameter that uses the CV input, you can end up with very complex patterns that go way beyond simple clock division/multiplication.
dooj88
i would dearly love for someone to post a demo of their clever pam findings.. i can't wait to see this thing in action. I'm particularly interested in the envelope shapes. zombie Dead Banana Dead Banana
rikrak
rikrak wrote:
You know what the solution to that is... 2 Pams! nanners


Wait... is this possible actually - to have the 2 in sync? Would I need the expansion? Could I make one Pam the master and one the slave?
BonJoey
rikrak wrote:
rikrak wrote:
You know what the solution to that is... 2 Pams! nanners


Wait... is this possible actually - to have the 2 in sync? Would I need the expansion? Could I make one Pam the master and one the slave?


just take an output of one into the clock input of the other? believe in your dreams.
rikrak
BonJoey wrote:
rikrak wrote:
rikrak wrote:
You know what the solution to that is... 2 Pams! nanners


Wait... is this possible actually - to have the 2 in sync? Would I need the expansion? Could I make one Pam the master and one the slave?


just take an output of one into the clock input of the other? believe in your dreams.


As simple as that.

Well, I'm dreaming of another Pam come payday. I don't know of another utility that would add more value to my small system. It's not even double the Pam, really - it's Pam to the power of 2.
Southfork
After a week with new pams i find myself constantly searching for it. clocks, Synced lfos, Random voltage. Loads of save slots. On board attenuation of incoming and outgoing signals, phasing and i haven't once had to think about the interface. This is a near perfect product and fast becoming the heart that feeds the rest of my system. Great stuff ALM!!! thumbs up
atte
BonJoey wrote:
rikrak wrote:
rikrak wrote:
You know what the solution to that is... 2 Pams! nanners


Wait... is this possible actually - to have the 2 in sync? Would I need the expansion? Could I make one Pam the master and one the slave?


just take an output of one into the clock input of the other? believe in your dreams.


Or if you're already clocking it from the outside: mult the clock and run and feed them to both pams
Fiddlestickz
ALM wrote:
bwhittington wrote:
How well does the MIDI clock out on the PEXP-1 follow tempo changes from the clock input? I would be completely enthralled by a video illustrating this feature.


See https://vimeo.com/204926725


$OLD..!!
papx
Ordered it today from Rubadub... look forward to playing with it tomorrow.
erstlaub
papx wrote:
Ordered it today from Rubadub... look forward to playing with it tomorrow.


Haha, Aleks must ahve had a busy morning. Me too. Long term lover of Pam, particularly in combination with Batumi. Wondering if New Pam's might see the Doepfer A149 relegated to the other case, not sure yet but super excited for all the clocked modulation possibilities.
radar24
Does anyone have some sync issue with PEXP-1 MIDI sync out?

I'm syncing MFB Tanzbar with New Pam
I've bought PEXP-1 to use midi sync so I can use regular outs for other things.
but I'm hearing PEXP-1 MIDI sync out lagging. not as tight as when syncing with trigger outs.
MFB Tanzbar's midi sync is pretty tight with other midi sync source
so i think it maybe PEXP-1's issue.
bovaflux
Just installed Pamela's New Workout... this thing is ace. Basic use is super simple, as are most of the advanced functions. Not got into anything too deep yet, but just setting up a bunch of clock divisions and multipliers, a couple of euclidean sequences with skipping beats, an lfo, tweaking one clock to output a pulse instead of a gate.. all very quick and straightforward to do. I love the new screen too! Can't wait to dig into this more!
Jaypee
Can I CV the swing/delay with CV inputs?
boboter
I'm in love with Pam's new Workout. Super easy to operate and insanely flexible. Didn't even have to RTFM.

While using it, two feature wishes occured:

1. It would be great if you could copy and paste the setting of one output to another. This would avoid jumping back and forth between outputs and comparing parameters if you want to have a few similiar but not equal settings.

2. This might not be possible or even desirable, but in some cases it would be cool to have individual outputs ignore the reset trigger and just keep going while the rest starts at the beginning.
dooj88
boboter wrote:

2. This might not be possible or even desirable, but in some cases it would be cool to have individual outputs ignore the reset trigger and just keep going while the rest starts at the beginning.


mine is in the mail, can't wait!

to add to the thought above, might be cool to have a reset behavior submenu, like hard reset all channels, per channel reset selection, or mute on reset so you get a skipped CV instead of restarting the function..
ALM
Jaypee wrote:
Can I CV the swing/delay with CV inputs?


Yes - CV control an outputs delay and/or delay divisor setting.
ALM
dooj88 wrote:
boboter wrote:

2. This might not be possible or even desirable, but in some cases it would be cool to have individual outputs ignore the reset trigger and just keep going while the rest starts at the beginning.


mine is in the mail, can't wait!

to add to the thought above, might be cool to have a reset behavior submenu, like hard reset all channels, per channel reset selection, or mute on reset so you get a skipped CV instead of restarting the function..


You can hard reset everything by via the run input (setting in BPM sub menu - run -> 'N') . You can effectively do per channel resets via the 'loop' parameter.
Jaypee
ALM wrote:
Jaypee wrote:
Can I CV the swing/delay with CV inputs?


Yes - CV control an outputs delay and/or delay divisor setting.


Thanks! SlayerBadger!
dooj88
ALM wrote:
dooj88 wrote:
boboter wrote:

2. This might not be possible or even desirable, but in some cases it would be cool to have individual outputs ignore the reset trigger and just keep going while the rest starts at the beginning.


mine is in the mail, can't wait!

to add to the thought above, might be cool to have a reset behavior submenu, like hard reset all channels, per channel reset selection, or mute on reset so you get a skipped CV instead of restarting the function..


You can hard reset everything by via the run input (setting in BPM sub menu - run -> 'N') . You can effectively do per channel resets via the 'loop' parameter.


sweet!
erstlaub
//sycophant mode engaged

Have to say, well done ALM. Original Pam's remains an awesome module (to the point that I'm having a really difficult time deciding whether I can get away with keeping both) but the new workout is totally sublime. It's a rare 10/10 module for me - I often find I love modules but there is some sort of functional kink, way a knob is mapped or an output that I find I just am not ever really going to use that makes me wish it was different but this is just straight out of the park.

I spent yesterday putting it through its paces in lots of different directions, all of which just work perfectly.

As a big fan of the skippy triggers on the first one, the new percentage approach to things is amazing. Being able to attenuate the level of the waves internally makes everything so much less hassle.

The way you can use the loop setting to essentially 'lock in' loops on the random mode (well all the modes) is ace too and the Euclidean stuff rocks.

I was a little confused about how the CV in was working but then was up early enough this morning to squeeze in a quick workout (geddit) before work and found that additional layer of menu which made everything click and make perfect sense. It's really cleverly done and sooooo useful.

If I was forced to find a slight point of contention, the envelope I feel is a little too low level and fast/poppy not plucky for my general tastes but then came to realise that I could just use the shape control on a sine or triangle to get something closer to what I was needing so still all entirely good.

You've clearly spent the time and brain power getting things to where they are and I just want to say that as a user it's hugely appreciated. I'm sure you'll sell these by the truckload and rightly so, I hope you buy yourself something nice off the proceeds.

Thank you.

EDIT: Ridiculous feature request - is there any chance of a cheeky wee built in quantizer on the RND output? Just a few choice standard scales would do me...
boboter
ALM wrote:
dooj88 wrote:
boboter wrote:

2. This might not be possible or even desirable, but in some cases it would be cool to have individual outputs ignore the reset trigger and just keep going while the rest starts at the beginning.


mine is in the mail, can't wait!

to add to the thought above, might be cool to have a reset behavior submenu, like hard reset all channels, per channel reset selection, or mute on reset so you get a skipped CV instead of restarting the function..


You can hard reset everything by via the run input (setting in BPM sub menu - run -> 'N') . You can effectively do per channel resets via the 'loop' parameter.



Thank you. I may understand it wrong but what I meant with reset was the run input. So if another module sends a trigger, Pam start's from the beginning, but is it possible that e.g. only six of the eight outputs start over and the other two keep their current position?

As I said, this might not really fit to the whole workflow of Pam. Just thought it could be fun.
MATSmile
It could be really cool to have logic combiners (OR, NOR, AND, XOR etc) especially since now we can control PW with CV. Pleaseee ALM
nanners
ALM
Thanks for kind words & feature requests hyper hyper hyper hyper

Noting everything and hope to add some new features (and any bug fixes) in upcoming firmware updates. Im just hanging on atm to initially sort any bug reports or issues first.

A couple of things to keep in mind; Its really important that Pam stays easy to pick up, familiar and quick to use.. it would be easy to ruin this by over doing it feature wise especially adding the kind of things that are better done externally with dedicated modules. Also there is *very* little space left on Pam for much more program code (<1k) so any massive new features are unlikely.
boboter
ALM wrote:
Thanks for kind words & feature requests hyper hyper hyper hyper

Noting everything and hope to add some new features (and any bug fixes) in upcoming firmware updates. Im just hanging on atm to initially sort any bug reports or issues first.

A couple of things to keep in mind; Its really important that Pam stays easy to pick up, familiar and quick to use.. it would be easy to ruin this by over doing it feature wise especially adding the kind of things that are better done externally with dedicated modules. Also there is *very* little space left on Pam for much more program code (<1k) so any massive new features are unlikely.


This is definitely the way to go. Thanks for a fantastic module. And for reading through our blabbering smile
BlackDoors
Just plugged it in - Wonderful module, first impressions are amazing, I can feel it is oozing potential for me. Scared it's made a lot of other things redundant for me at a stroke!

One thing I would ask, that I couldn't work out from the manual:
Is there a quick/easy way of muting individual outputs?

I think this is an area where Tempi scores and with PNW, it's not so easy to drop one output off (without a fade as you turn the encoder). Ok - I *think* could use one of the CV inputs / and a pressure points or something. But is there an easy way within the interface to set / remove mutes?

(Stretch target, ALM: I would really like a mute page with 8 mute checkboxes and the ability to group mutes). Or at least, could the output level selection for an individual output go from 100% to 0% in a single click, before changing to CV01?

Apols if I have missed the 'right' way to do this on the module.

Slipping into neon leggings and leg-warmers for another workout as I type this!

John
brandonlogic
BlackDoors wrote:

(Stretch target, ALM: I would really like a mute page with 8 mute checkboxes and the ability to group mutes). Or at least, could the output level selection for an individual output go from 100% to 0% in a single click, before changing to CV01?


+1 yeah, this would be ace! great suggestion!
BlackDoors
brandonlogic wrote:
BlackDoors wrote:

(Stretch target, ALM: I would really like a mute page with 8 mute checkboxes and the ability to group mutes). Or at least, could the output level selection for an individual output go from 100% to 0% in a single click, before changing to CV01?


+1 yeah, this would be ace! great suggestion!


smile thinking about it may be possible to use 'all output' bank load to achieve a limited version of this functionality? (Ie have 2 banks the same, except for the mutes you want to apply, and switch them on the fly). But I need to try if this achieves the 'bumpless transfer' I'm hoping for.

John
ALM
Currently you can use load and save to do this kind of thing (i.e mute a channel by loading an 'off' modifier save). Admittedly its a bit clunky.

I have some other more immediate ideas to try just worried they may end up causing confusion to people accidentally muting and it looking like the channel is bust.
Zymos
I was never too excited about the original, I guess because I had several other clock and trigger generators.

The New Workout became an essential part of my rig within minutes of installing it- I'd never want to be without it!
cheliosheart
ALM wrote:
A couple of things to keep in mind; Its really important that Pam stays easy to pick up, familiar and quick to use.. it would be easy to ruin this by over doing it feature wise especially adding the kind of things that are better done externally with dedicated modules.


Yes, totally agree, this version of Pam's is well featured, but what makes this module fun to use is how easy and fluid it is to program. The workflow is fast and enjoyable.

One 'feature' I'd be interested in (if it were even possible), when assigning parameters to CV, I kinda want to see the parameter change in the display. I know you can see incoming CV level but for example if I fed a sequencer into the CV in to control clock div/mult and wanted to set precise steps for /1, x1.3, /6, x3, etc. I wish you can see those value changes displayed. It might make precision programming easier. Maybe a technical limitation with the display? I guess it would probably look crazy if you fed it fast modulation.
BlackDoors
ALM wrote:
Currently you can use load and save to do this kind of thing (i.e mute a channel by loading an 'off' modifier save). Admittedly its a bit clunky.

I have some other more immediate ideas to try just worried they may end up causing confusion to people accidentally muting and it looking like the channel is bust.


Thanks for the reply. I think a method of fast muting would add an awesome performance ability to Pam.

On a related performance note, I was a bit surprised that as I turn the encoder, the divisions change immediately at the output. I kind of imagined from reading the manual that you would turn to the desired division, then press the encoder to choose it (again, for performance purposes). I'm guessing that here, loading an individual output setting is a workaround? Also I note that pressing the encoder skips some of the intermediate values as well.

Tbh I'm blown away by the immediacy and depth of the module - and I definitely take the point that people could get confused if the interface isn't right.

Btw Your Pico drums video has now convinced me I need a Pico drums to pair with Pam too. Just fabulous. Too bad I don't even have a spare 3hp! grin

Looking forward to a great weekend of workouts!

John
dooj88
BlackDoors wrote:
ALM wrote:
Currently you can use load and save to do this kind of thing (i.e mute a channel by loading an 'off' modifier save). Admittedly its a bit clunky.

I have some other more immediate ideas to try just worried they may end up causing confusion to people accidentally muting and it looking like the channel is bust.


Thanks for the reply. I think a method of fast muting would add an awesome performance ability to Pam.


that would make for a bitchin' breakout module too if you really want it to be performance worthy! 2HP, 8 mute buttons!
BlackDoors
dooj88 wrote:
BlackDoors wrote:
ALM wrote:
Currently you can use load and save to do this kind of thing (i.e mute a channel by loading an 'off' modifier save). Admittedly its a bit clunky.

I have some other more immediate ideas to try just worried they may end up causing confusion to people accidentally muting and it looking like the channel is bust.


Thanks for the reply. I think a method of fast muting would add an awesome performance ability to Pam.


that would make for a bitchin' breakout module too if you really want it to be performance worthy! 2HP, 8 mute buttons!


Hell yeah. I'm not aware of any 8 way latching illuminated push button mute modules.... perhaps there's a gap in the market! I'm always dropping voices / notes in and out and it's too often achieved by twisting pots on the VCA instead of somewhere handy! Btw, I know I could/should use a proper mixer to do this.
albiedamned
I agree with the previous poster that the envelope is a little too plucky. I think the decay is too exponential. So I guess that's my feature request. Either make it a little less exponential (but still not linear - then it's the same as a skewed triangle), or even better, change the width parameter so that instead of controlling release time it controls envelope curve.
nciviero
Wow this thing looks like a must-have autobuy.

Is there any possibility of a firmware update allowing internal routing of one output to modulate parameters of another? (i.e. instead of cv1 or 2 an option for output1-8) There are just so many parameters to modulate for 2 cv inputs.

I don't know much about the architecture of these things so I don't know if this is possible, but if it is it would be amazing. Or (super wishful thinking) maybe it already has this functionality and I just somehow missed it in the manual.

If that was I feature I would buy two of these.
rikrak
Quick question. Can I use Pam to calibrate / tune some of my other modules. For example, can I send exactly 1v or 4v (say) by setting Level to 20% and 80% respectively?

boboter wrote:

1. It would be great if you could copy and paste the setting of one output to another. This would avoid jumping back and forth between outputs and comparing parameters if you want to have a few similiar but not equal settings.


You can Save an individual Output's settings in its advanced menu. I keep Bank B free for this. So set Output 1, Save to B1, Move to Output 2, Load B1. Done.
brandonlogic
-Edit-
BlackDoors
nciviero wrote:
Wow this thing looks like a must-have autobuy.

Is there any possibility of a firmware update allowing internal routing of one output to modulate parameters of another? (i.e. instead of cv1 or 2 an option for output1-8) There are just so many parameters to modulate for 2 cv inputs.


Awesome suggestion for a number of reasons! Insane self-patch ability.

Linking to my question, it could be used to achieve group mutes (at the expense of one channel, which could be set between 'on' and 'off'. Among a huge number of other antics.

John
BlackDoors
(Duplicate)
ALM
BlackDoors wrote:
nciviero wrote:
Wow this thing looks like a must-have autobuy.

Is there any possibility of a firmware update allowing internal routing of one output to modulate parameters of another? (i.e. instead of cv1 or 2 an option for output1-8) There are just so many parameters to modulate for 2 cv inputs.


Awesome suggestion for a number of reasons! Insane self-patch ability.



I agree - but having played with this kind of internal 'virtual patching' Im not sure it can fit on the h/w without causing issues :(
ALM
rikrak wrote:
Quick question. Can I use Pam to calibrate / tune some of my other modules. For example, can I send exactly 1v or 4v (say) by setting Level to 20% and 80% respectively?


It would at least be 'roughly' 1v or 4v with such levels but could not guarantee exactness to be enough for precise calibration.
rikrak
ALM wrote:
rikrak wrote:
Quick question. Can I use Pam to calibrate / tune some of my other modules. For example, can I send exactly 1v or 4v (say) by setting Level to 20% and 80% respectively?


It would at least be 'roughly' 1v or 4v with such levels but could not guarantee exactness to be enough for precise calibration.


Ah well just a thought!

Regarding CV1&2 modulations, it's worth noting that each parameter that is modified by the CV inputs has its own bipolar attenuation and offset for that CV input! (See pg13 in the manual).
erstlaub
rikrak wrote:
Quick question. Can I use Pam to calibrate / tune some of my other modules. For example, can I send exactly 1v or 4v (say) by setting Level to 20% and 80% respectively?

boboter wrote:

1. It would be great if you could copy and paste the setting of one output to another. This would avoid jumping back and forth between outputs and comparing parameters if you want to have a few similiar but not equal settings.


You can Save an individual Output's settings in its advanced menu. I keep Bank B free for this. So set Output 1, Save to B1, Move to Output 2, Load B1. Done.


I thought I'd give this a quick test with a meter *but* and I might be missing something here, when you select the On modifier (so there's a constant high value when the module is running) there isn't then a context menu to access the additional parameters. I know it's using a hammer to drive in a screw but it'd be well nice to be able to access the level parameter so that a quick to hand offset could be dialled in.

Just for reference, on the meter I was getting an ever so slight fluctuation on that fixed high between 5v and 4.99v (I think depending on LEDs and I'd guess what else is happening in the CPU).
rikrak
erstlaub wrote:

I thought I'd give this a quick test with a meter *but* and I might be missing something here, when you select the On modifier (so there's a constant high value when the module is running) there isn't then a context menu to access the additional parameters. I know it's using a hammer to drive in a screw but it'd be well nice to be able to access the level parameter so that a quick to hand offset could be dialled in.

Just for reference, on the meter I was getting an ever so slight fluctuation on that fixed high between 5v and 4.99v (I think depending on LEDs and I'd guess what else is happening in the CPU).


You can use /1 (Edit: x1, or similar) and set Width to 100%!
erstlaub
d'oh! course you can.

I read 3.99v at 80% (4.03v at 81%) and fluctuating between 0.99v and 1v at 20%.
rikrak
erstlaub wrote:
d'oh! course you can.

I read 3.99v at 80% (4.03v at 81%) and fluctuating between 0.99v and 1v at 20%.


So a difference of 3v, which is all that matters for tuning/calibration, right? Just that the pitch may be a fraction of 1cent flat - or am I missing something else?
erstlaub
I'm not a doctor but aye, I'd say it looks like it'd be fairly decent on paper, practice might yield different results given that the outputs were just measured unloaded (could potentially throw another little drop in there or something).
rikrak
erstlaub wrote:
I'm not a doctor but aye, I'd say it looks like it'd be fairly decent on paper, practice might yield different results given that the outputs were just measured unloaded (could potentially throw another little drop in there or something).


Thanks for investigating. I'll use Pam to tune up later!
erstlaub
Digging a bit deeper today and come across a behaviour that I can't quite get my head around, figured it'd be good if someone else can check this out too.

With nothing plugged into the CV inputs, when I set the wave to CV2 and go into the attenuation menu on that channel, when I dial in any value between +37 and +100% I get what sounds like a sine wave coming out of the channel.

+36 down to -100% it just behaves flat as I'd expect.

In addition to this, if I change the offset value it's as though the modulation moves between 'banks' in blocks of around 20 values (sine, rand, envelope I can find).

I know it's not a normal use situation but just wondered if this was a little bug in the code or if there's some undocumented normaling/internal routing going on?
Migrigsynth
I may have missed this in the earlier part of this thread but, I'm assuming with all the flexibility of parameters that I could program a very slow LFO ( 15 sec to 2 minute range) by out-putting for example a sine wave and using the right clock divider. Am I correct?
papx
This is definitely my favourite module! Amazing CV and rhythmic possibilities.

albiedamned
Migrigsynth wrote:
I may have missed this in the earlier part of this thread but, I'm assuming with all the flexibility of parameters that I could program a very slow LFO ( 15 sec to 2 minute range) by out-putting for example a sine wave and using the right clock divider. Am I correct?


Yes!
nciviero
ALM wrote:
BlackDoors wrote:
nciviero wrote:
Wow this thing looks like a must-have autobuy.

Is there any possibility of a firmware update allowing internal routing of one output to modulate parameters of another? (i.e. instead of cv1 or 2 an option for output1-8) There are just so many parameters to modulate for 2 cv inputs.


Awesome suggestion for a number of reasons! Insane self-patch ability.



I agree - but having played with this kind of internal 'virtual patching' Im not sure it can fit on the h/w without causing issues :(



I kind of figured it would already be in there if it were doable as you clearly thought of everything with the new workout. I still can't wait to get my hands on it.
Migrigsynth
albiedamned wrote:
Migrigsynth wrote:
I may have missed this in the earlier part of this thread but, I'm assuming with all the flexibility of parameters that I could program a very slow LFO ( 15 sec to 2 minute range) by out-putting for example a sine wave and using the right clock divider. Am I correct?


Yes!


thumbs up
Outtatune
Is there anywhere to buy one other than AH? My usual suppliers (Schneider's and Control) don't have them.
exper
Outtatune wrote:
Is there anywhere to buy one other than AH? My usual suppliers (Schneider's and Control) don't have them.


Probably not unless you want to wait for the next batch. Why not just go with AH?
Outtatune
exper wrote:
Outtatune wrote:
Is there anywhere to buy one other than AH? My usual suppliers (Schneider's and Control) don't have them.


Probably not unless you want to wait for the next batch. Why not just go with AH?


It's a long and OT story, but I'd rather wait for the next batch then give AH my money again.

I'll wait.
exper
Outtatune wrote:
exper wrote:
Outtatune wrote:
Is there anywhere to buy one other than AH? My usual suppliers (Schneider's and Control) don't have them.


Probably not unless you want to wait for the next batch. Why not just go with AH?


It's a long and OT story, but I'd rather wait for the next batch then give AH my money again.

I'll wait.


Gotcha. That's too bad, Shawn has always been great to deal with personally.

Well, you can always preorder and wait. At least you'll definitely get one. I have a feeling these will be selling out for while once people realize how much more it can do...
Pighood
So does the new Pam overlap the Triggerman enough to render it redundant?
kythre
Would Pamela's still run at the same BPM if the incoming clock stops? I would like to have my system still running even if I stop my daw because blinking lights are cool
brandonlogic
kythre wrote:
Would Pamela's still run at the same BPM if the incoming clock stops? I would like to have my system still running even if I stop my daw because blinking lights are cool


FYI, if your getting the midi expander you may want to try outputting midi clock to your daw so you can sync your daw to Pam instead of the other way around. Should be more stable that way I imagine!
kythre
brandonlogic wrote:
kythre wrote:
Would Pamela's still run at the same BPM if the incoming clock stops? I would like to have my system still running even if I stop my daw because blinking lights are cool


FYI, if your getting the midi expander you may want to try outputting midi clock to your daw so you can sync your daw to Pam instead of the other way around. Should be more stable that way I imagine!


What's wrong with the other way ?
brandonlogic
kythre wrote:
brandonlogic wrote:
kythre wrote:
Would Pamela's still run at the same BPM if the incoming clock stops? I would like to have my system still running even if I stop my daw because blinking lights are cool


FYI, if your getting the midi expander you may want to try outputting midi clock to your daw so you can sync your daw to Pam instead of the other way around. Should be more stable that way I imagine!


What's wrong with the other way ?


nothing really, personally ive had issues with daw's midi clock outs not being perfectly stable (a little sloppy) and using external hardware's midi clock things always run tighter/smoother. especially syncing modular clock divide/multipliers with them (thats why im excited for the midi out expader!). but if it works for you thats great!
chockfullofthat
brandonlogic wrote:
kythre wrote:
brandonlogic wrote:
kythre wrote:
Would Pamela's still run at the same BPM if the incoming clock stops? I would like to have my system still running even if I stop my daw because blinking lights are cool


FYI, if your getting the midi expander you may want to try outputting midi clock to your daw so you can sync your daw to Pam instead of the other way around. Should be more stable that way I imagine!


What's wrong with the other way ?


nothing really, personally ive had issues with daw's midi clock outs not being perfectly stable (a little sloppy) and using external hardware's midi clock things always run tighter/smoother. especially syncing modular clock divide/multipliers with them (thats why im excited for the midi out expader!). but if it works for you thats great!


Don't you have issues with recording audio to your DAW as a slave? I was considering getting the expander but after some awful experiences with syncing my DAW and gear to my TR-8, I'm now looking at ways for how to make the Pam's the slave to my DAW. Thinking I just need to do the audio track clock method.
erstlaub
Quote:
It is not recommended you sync Pam to computer sourced MIDI clocks. Modern computers tend to give MIDI hardware (particularly over USB) a low priority compared to other system events. This notoriously leads to timing errors in generating the midi clock and thus any slave devices will not sync correctly. For syncing to a computer it is recommend an audio track based clock is used or you use Pamela as the master with MIDI clock from the expander to DAW.


from the manual.
chockfullofthat
Yep. That's where I got the idea hihi
brandonlogic
Quote:
Quote:
or you use Pamela as the master with MIDI clock from the expander to DAW.


from the manual.


chockfullofthat wrote:


Don't you have issues with recording audio to your DAW as a slave?


Nope this has worked fine for me with other midi gear. And I'm running ableton live 64bit on a windows 7 pc and a beringer midi/audio interface, nothin fancy.
kythre
so does Pamela stop when it stops receiving a clock input?
VZvision
kythre wrote:
so does Pamela stop when it stops receiving a clock input?


The run input combined with an incoming clock will start and stop Pam's when the incoming clock stops.

See this as a reference:

http://busycircuits.com/docs/alm004toalm001.pdf
kythre
VZvision wrote:
kythre wrote:
so does Pamela stop when it stops receiving a clock input?


The run input combined with an incoming clock will start and stop Pam's when the incoming clock stops.

See this as a reference:

http://busycircuits.com/docs/alm004toalm001.pdf


wasn't there a free run mode or something?
chockfullofthat
brandonlogic wrote:
Quote:
Quote:
or you use Pamela as the master with MIDI clock from the expander to DAW.


from the manual.


chockfullofthat wrote:


Don't you have issues with recording audio to your DAW as a slave?


Nope this has worked fine for me with other midi gear. And I'm running ableton live 64bit on a windows 7 pc and a beringer midi/audio interface, nothin fancy.


Lucky you. I've been pulling my hair out all week trying to fix this mess and diagnosed it in this way. Using Live, 2011 Quad-Core iMac, Focusrite 2i2, MIDI to USB from TR-8 as main clock.
VZvision
kythre wrote:
VZvision wrote:
kythre wrote:
so does Pamela stop when it stops receiving a clock input?


The run input combined with an incoming clock will start and stop Pam's when the incoming clock stops.

See this as a reference:

http://busycircuits.com/docs/alm004toalm001.pdf


wasn't there a free run mode or something?


Yes it can free run. Either:

1. Don't patch it a clock and have it run freely
2. Patch it a clock but don't patch a run input

Haven't tried #2 but theoretically, it should work.
Zymos
When someone takes the time to post a link to the manual, you could just read the thing.... cool
kythre
Zymos wrote:
When someone takes the time to post a link to the manual, you could just read the thing.... cool


that manual was a single page diagram of using an expansion module
Zymos
Don't say I never gave ya nuthin'

http://busycircuits.com/docs/alm017-manual.pdf
papx
Not sure if this issue has been reported yet, but each time I reset the bank the outputs which had esteps applied do not trigger. To get them started again, I need to set an estep and dial it back to 0.
dash80
Been waiting for payday to finally get one of these and luckily Analogue Haven still has some in stock.

Can't wait to get everything all sync'd up.

Super excited based on the response here and how rock steady it looks! Much needed for my new BSP integration and my old clock module didn't have a clock in...

Praise we're not worthy
brandonlogic
loving the slop feature!

great parameter for NLC Sloth to modulate. so clocks get sloppier or tighter over time.

YAY FOR CV CONTROLLED SLOP!
Worwell
What is the best way to self patch a ratchet/roll for an output? Say I wanted to have a snare hit /3 but then every sixteenth step, it would go to x8 for a second or so?
erstlaub
Worwell wrote:
What is the best way to self patch a ratchet/roll for an output? Say I wanted to have a snare hit /3 but then every sixteenth step, it would go to x8 for a second or so?


This is just off the top of my head but seems right (although ive not had my coffee yet).

Set your snare channel divisor to cv1 or 2

Patch up another channel into the cv in

Setup that channel to output the standard gate/square wave, the divisor to the overall length of pattern you want for your snare, the width to how long you want the divisor to change speed for (you'll have to suss out what % of the full pattern it is), and the phase to the position you want the change to happen at.

After that, you'll have to go back to the original channel and dial into the cv menu and adjust the input offset and attenuation values to hit the values you want.

To find these values, it might be easier to temporarily patch in a channel with its duty cycle (width) set to 0% (always low) to find what offset value gives /3 and then change it to 100% (always high) and adjust the attenuation to find the value that gives the x16 you want.

Once its patched up you might need to dial in a reset value too to have it all snap back together tighly every x beats as ive sometimes found that changing things on the fly can make things a bit drifty.

In short, you're using a user set length of high voltage, at a specified point in time to flip between 2 values if that makes it easier to get your head around.

May try this out once im up and about but scans right at the moment (in bed on my ipad innit).

EDIT: I've risen and caffeinated and it pretty much works as stated, you'll need to tweak values to suit and most probably need to make use of the loop settings to lock it all together. Let me know if it doesn't make sense.
Worwell
erstlaub wrote:
Worwell wrote:
What is the best way to self patch a ratchet/roll for an output? Say I wanted to have a snare hit /3 but then every sixteenth step, it would go to x8 for a second or so?


This is just off the top of my head but seems right (although ive not had my coffee yet).

Set your snare channel divisor to cv1 or 2

Patch up another channel into the cv in

Setup that channel to output the standard gate/square wave, the divisor to the overall length of pattern you want for your snare, the width to how long you want the divisor to change speed for (you'll have to suss out what % of the full pattern it is), and the phase to the position you want the change to happen at.

After that, you'll have to go back to the original channel and dial into the cv menu and adjust the input offset and attenuation values to hit the values you want.

To find these values, it might be easier to temporarily patch in a channel with its duty cycle (width) set to 0% (always low) to find what offset value gives /3 and then change it to 100% (always high) and adjust the attenuation to find the value that gives the x16 you want.

Once its patched up you might need to dial in a reset value too to have it all snap back together tighly every x beats as ive sometimes found that changing things on the fly can make things a bit drifty.

In short, you're using a user set length of high voltage, at a specified point in time to flip between 2 values if that makes it easier to get your head around.

May try this out once im up and about but scans right at the moment (in bed on my ipad innit).

EDIT: I've risen and caffeinated and it pretty much works as stated, you'll need to tweak values to suit and most probably need to make use of the loop settings to lock it all together. Let me know if it doesn't make sense.


Great analysis. Thank you. The phase piece of the patch was what I was missing. I will give this a shot. Cheers.
MoogCloud
Zymos wrote:
Don't say I never gave ya nuthin'

http://busycircuits.com/docs/alm017-manual.pdf


And I thank you as well we're not worthy

My new Pams is in the care of UPS at the moment, destined to arrive day after tomorrow. I can hardly wait!
It's peanut butter jelly time!
Tumulishroomaroom
I've bought one from schneidersladen,probably from the next batch ! I'm waiting eagerly smile
ALM
I've uploaded a new beta '189' firmware for folks to try. It should be pretty solid.

You can download from http://busycircuits.com/firmware/alm017/

I've also uploaded an updated manual which has had some tweaks to the firmware updating instructions as well as covering new features. Please read carefully before trying the update. Also note you can always go back to the release 177 firmware by flashing that.

Here is what is new;

- Add new output muting functionality.
- Add a new vertical offset parameter to outputs.
- Improve expander DIN & MIDI compatibility for syncing.
- Increase overall CV handling precision a little.
- Fix CV2 attenuversion handling - now actually inverts + treats midpoint as 0.
- Keep 'work' bank correctly synced across power cycles when loading/reseting entire banks.
- Fix issue where expander run signal can be left high when clock stopped.
- Fix issue where Euclidean edited outputs could not get reset correctly.
- Allow utility modifier outputs to be saved & recalled.

The downside of this update is that this update exposes a silly bug in the PEXP1 (not PEXP2!) expander module. This bug puts the external gates very slightly out of sync - though external MIDI and DIN syncing should be tighter. The fix unfortunately requires that the PEXP-1 be sent back here to ALM for updating. If this affects you please contact help <at> busycircuits.com and we will get it sorted for you asap. Apologies for any troubles here.

Thanks to all that have reported bugs and helped test fixes!
papx
Can't wait to try it - particularly the muting functionality!
BonJoey
pumped on the muting!
BlackDoors
ALM wrote:
I've uploaded a new beta '189' firmware for folks to try. It should be pretty solid.

Thanks to all that have reported bugs and helped test fixes!


Wow - I just can't wait to try!

Not sure on the etiquette of posting links to music you have made with modules that don't make any sound...... But here is a simple sequence achieved with PNW for all the clocks and LFOs.

[s]https://soundcloud.com/blackdoors/moonlight[/s]

(I used one Octone and one pressure points with a 2hp Tune to get the root note switching working from pressure points... Sound sources (from memory) were just one Rubicon and one Dixie II+ with a couple of filters. Keeping it in the family, Beast's Chalkboard helped!)

Thanks for all the wonderful work on this module. I am looking forward to years of enjoyment from it!

John
Worwell
ALM wrote:
I've uploaded a new beta '189' firmware for folks to try. It should be pretty solid.

You can download from http://busycircuits.com/firmware/alm017/

I've also uploaded an updated manual which has had some tweaks to the firmware updating instructions as well as covering new features. Please read carefully before trying the update. Also note you can always go back to the release 177 firmware by flashing that.

Here is what is new;

- Add new output muting functionality.
- Add a new vertical offset parameter to outputs.
- Improve expander DIN & MIDI compatibility for syncing.
- Increase overall CV handling precision a little.
- Fix CV2 attenuversion handling - now actually inverts + treats midpoint as 0.
- Keep 'work' bank correctly synced across power cycles when loading/reseting entire banks.
- Fix issue where expander run signal can be left high when clock stopped.
- Fix issue where Euclidean edited outputs could not get reset correctly.
- Allow utility modifier outputs to be saved & recalled.

The downside of this update is that this update exposes a silly bug in the PEXP1 (not PEXP2!) expander module. This bug puts the external gates very slightly out of sync - though external MIDI and DIN syncing should be tighter. The fix unfortunately requires that the PEXP-1 be sent back here to ALM for updating. If this affects you please contact help <at> busycircuits.com and we will get it sorted for you asap. Apologies for any troubles here.

Thanks to all that have reported bugs and helped test fixes!


Nice update. The mutes and offset options are very useful. (On a Mac), the update procedure is not as scary as it looks in the manual and linked websites. Hang in there with it.
MATSmile
Any word on logic channel combos? sad banana
gavechase
ALM wrote:
I've uploaded a new beta '189' firmware for folks to try. It should be pretty solid.


Fantastic! Thanks for all your hard work fixing bugs and adding features.
ALM
MATSmile wrote:
Any word on logic channel combos? sad banana


How exactly would it work ? Wouldn't it be better handled by a dedicated logic module ?

The 'virtual patching' idea would maybe cover it but its gonna take a pretty monumental effort to get the to fit & work well. There are literally only bytes of program flash space left..
dooj88
having a blast with mine, nice work on this! awesome you're on top of bug patching!

i've got too many things to left to explore on it, i think i'll wait for a stable release.
MATSmile
ALM wrote:
MATSmile wrote:
Any word on logic channel combos? sad banana


How exactly would it work ? Wouldn't it be better handled by a dedicated logic module ?

The 'virtual patching' idea would maybe cover it but its gonna take a pretty monumental effort to get the to fit & work well. There are literally only bytes of program flash space left..

That's how I see it. Just like clock div/mult it can be used on any chanel and will allow you to chose two currently running channels to combine into logic output. Ex, channel 3 is running OR out of channel 1 (/4) and 2 (/1.5) [or ch. 1 (/4) and Ch. 2 which is running NOR of channels 6 and 7], cv control over PW allows for some crazy swing patterns. Maybe dedicated module is better, but I wouldn't mind saving some hp for Pamela's midi expender. It all really comes down to how hard it will be to implement it.

PS, For some reason many people shy away from logic functions thinking it's math and it's complicated but in reality it's such an amazing tool for altering rhythm and modulation.
L.C.O.
Yeah, install is pretty convoluted at the moment.
But not impossible ;-) (Just did it)

I would imagine some people might get confused with the "brew" and how to "use brew" to install the "dry-util"... etc.

Great to hear that a custom installation app/procedure is in the works.

Thank you for the firmware update!
Great product getting better!

It's peanut butter jelly time!
erstlaub
I hit a few bumps with install on my Mac as Terminal always gives me the cold sweats and for some reason I couldn't get the stuff to install as per the instructions (possibly to do with not having the absolute latest macbook and os) so here's a breakdown of how it worked for me in the hope that anyone else struggling might see hope.

1. DL the new FW file, put it on the desktop

2. Go to http://www.open-tx.org/2013/07/15/dfu-util-07-for-mac-taranis-flashing -utility and install dfu-util that way as the terminal route was giving me bunk about network connections (have had the same issue re. X-code previously)

3. Disconnect your Pam's from the power, plug in the usb cable.

4. Open Terminal and copy and paste the following (minus the quotes) - 'dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D ~/Desktop/alm017-189.bin' - obviously change the filename accordingly. I had an issue copy and pasting from the old pdf manual as a linebreak was copied into terminal as a space which broke things but looks like the manual has been tweaked there too thumbs up

5. Hit enter and watch the code squirt into your module

6. Rejoice.

Thanks so much to ALM for helping the less clever of us through things and hats off once again on an amazing module and following things up so quickly.
rikrak
ALM wrote:
MATSmile wrote:
Any word on logic channel combos? sad banana


How exactly would it work ? Wouldn't it be better handled by a dedicated logic module ?

The 'virtual patching' idea would maybe cover it but its gonna take a pretty monumental effort to get the to fit & work well. There are literally only bytes of program flash space left..


Wherever the parameters CV01/02 appear, could there be Outputs 01 to 08 as well? That would be enough for me.

Thanks for the update! PnW is a contender for Module of the Year, for sure.
Worwell
erstlaub wrote:
Terminal always gives me the cold sweats


Ha. Spot on.
BlackDoors
rikrak wrote:

Wherever the parameters CV01/02 appear, could there be Outputs 01 to 08 as well? That would be enough for me.

Thanks for the update! PnW is a contender for Module of the Year, for sure.


Yes on both counts!

John
rupa
rikrak wrote:

Wherever the parameters CV01/02 appear, could there be Outputs 01 to 08 as well? That would be enough for me.


would it just be one logical operation between these channels? If it was, and it was XOR, I'd be into it. Or am I completely missing the idea?
rikrak
rupa wrote:
rikrak wrote:

Wherever the parameters CV01/02 appear, could there be Outputs 01 to 08 as well? That would be enough for me.


would it just be one logical operation between these channels? If it was, and it was XOR, I'd be into it. Or am I completely missing the idea?


Everywhere you can currently select CV01 or CV02 as a parameter you'd be able to select an Output as that parameter instead. No logic operation involved. Minimal change to the UI but not sure how simple it would be to implement behind the scenes.
MATSmile
rikrak wrote:
rupa wrote:
rikrak wrote:

Wherever the parameters CV01/02 appear, could there be Outputs 01 to 08 as well? That would be enough for me.


would it just be one logical operation between these channels? If it was, and it was XOR, I'd be into it. Or am I completely missing the idea?


Everywhere you can currently select CV01 or CV02 as a parameter you'd be able to select an Output as that parameter instead. No logic operation involved. Minimal change to the UI but not sure how simple it would be to implement behind the scenes.

It's as simple as muting output and plugging it back into CV1/2.
rikrak
MATSmile wrote:
rikrak wrote:
rupa wrote:
rikrak wrote:

Wherever the parameters CV01/02 appear, could there be Outputs 01 to 08 as well? That would be enough for me.


would it just be one logical operation between these channels? If it was, and it was XOR, I'd be into it. Or am I completely missing the idea?


Everywhere you can currently select CV01 or CV02 as a parameter you'd be able to select an Output as that parameter instead. No logic operation involved. Minimal change to the UI but not sure how simple it would be to implement behind the scenes.

It's as simple as muting output and plugging it back into CV1/2.


I do currently route an output into CV1 to do this (not sure why you suggest to Mute it thoughl. However, I'm talking about being able to select, say, Output 2s output value as Output 4s Waveform... Output 5s output value as Output 7s Width and Output 6s Etrig value... etc etc. Currently, using both CV inputs, you can only use a maximum of two Outputs as input values. I would like to access all 8 AND the Cv inputs!
dooj88
I'm certainly not a programmer, but i had an ideas about the muting function implementation. Instead of putting in a menu option for muting each output, it would be really cool if it would be possible to mute an output by selecting the channel's top menu and double clicking the Program encoder, or holding play/stop and clicking the Program encoder. Would make performing a breeze with easy access like that
Worwell
dooj88 wrote:
I'm certainly not a programmer, but i had an ideas about the muting function implementation. Instead of putting in a menu option for muting each output, it would be really cool if it would be possible to mute an output by selecting the channel's top menu and double clicking the Program encoder, or holding play/stop and clicking the Program encoder. Would make performing a breeze with easy access like that


That's what you can do with the new firmware. Program and stop/start mutes the channel.
Abyssinianloop
I had success installing the new firmware on Windows. There are a few tricky points that aren't explicit. For those having trouble, here's what I did.

You're going to download a few things, and it's best to keep them in the same folder. So create a folder, and keep the path short and simple. I created a folder in Downloads called Pam (Downloads\Pam)

1. Download the new firmware and put it in the folder you created.

2. Download this tool called Zadig from http://zadig.akeo.ie/
It helps make the usb connection between your computer and the module.

3. Download the dfu-util files from this site:
http://dfu-util.sourceforge.net/
This site is a little confusing, and it's not totally clear which files to grab, but this is what you want-- About half way down the page is the link to the releases. We are advised to use the version 8.0 files, so scroll down and click into the "dfu-util-0.8-binaries" folder and inside that click on the "win32-mingw32" folder.
Ultimately this is where you want to be:
http://dfu-util.sourceforge.net/releases/dfu-util-0.8-binaries/win32-m ingw32/
Download the 5 files to the folder you created on your computer.

4. Disconnect Pamela's power cable. (I remove her completely from my rack)

5. Connect Pamela to your computer with a usb to mini-usb cable.

6. Run Zadig
Select: List all devices from the options menu
Select: STM 32 BOOTLOADER from the devices drop-down
Select: WinUSB
Click "Install Driver"

7. Open a terminal in Windows (you can usually find one at "All Programs\Accessories\Command Prompt")
Next you'll be entering the command to run the dfu-util program that updates Pam's firmware. You're going to need to specify the location of dfu-util as well as the new firmware file in the command--or to simplify things, (this is why I put everything in the same folder) change to that directory first.

8. In terminal type:
cd Downloads\Pam
(this should change the directory to Downloads\Pam. Your path may be a bit different, so figure out what it is and type it in. You can right click and view properties on a file in the folder to see the path.)

9. Now that you are in the \Pam folder you can type the command directly without specifying the location of the utility or the target file.
Type or (copy/paste for accuracy):
dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D alm017-189-BETA.bin


Done!
dooj88
Worwell wrote:
dooj88 wrote:
I'm certainly not a programmer, but i had an ideas about the muting function implementation. Instead of putting in a menu option for muting each output, it would be really cool if it would be possible to mute an output by selecting the channel's top menu and double clicking the Program encoder, or holding play/stop and clicking the Program encoder. Would make performing a breeze with easy access like that


That's what you can do with the new firmware. Program and stop/start mutes the channel.


MY ASS IS BLEEDING we're not worthy
atte
Nice update, update process went pretty smooth from my linux desktop (debian stable).
erstlaub
Ahhaaaa. Did a wee bit of rearranging yesterday and decided that it sometimes feels like a bit of a waste of New Pam's using it for boring straight clock duties (although it does it so well) that I might as well throw old Pams into the mix too.



It locks together quite nicely using one channel of Old Pams to the clock in (set to 24x) and another channel set to chuck out a high signal as active to run. The one thing that looks a little *off* is that where Old Pams is set to 66bpm, new Pam's screen is reporting it playing back at 65bpm although playing back a drum patten using triggers from both modules doesn't sound to be drifty.

I've also had both sync'd up using BSP as a master (BSP clock and run multed to both) which worked quite well although it's sometimes a bit hit and miss and takes a few stops and starts to get everything starting in the right place for some reason.

I think the closest to totally solid was patched up as per above with BSP clock and run's feeding Old Pams.
iatroim
Abyssinianloop wrote:
I had success installing the new firmware on Windows. There are a few tricky points that aren't explicit. For those having trouble, here's what I did.

You're going to download a few things, and it's best to keep them in the same folder. So create a folder, and keep the path short and simple. I created a folder in Downloads called Pam (Downloads\Pam)

1. Download the new firmware and put it in the folder you created.

2. Download this tool called Zadig from http://zadig.akeo.ie/
It helps make the usb connection between your computer and the module.

3. Download the dfu-util files from this site:
http://dfu-util.sourceforge.net/
This site is a little confusing, and it's not totally clear which files to grab, but this is what you want-- About half way down the page is the link to the releases. We are advised to use the version 8.0 files, so scroll down and click into the "dfu-util-0.8-binaries" folder and inside that click on the "win32-mingw32" folder.
Ultimately this is where you want to be:
http://dfu-util.sourceforge.net/releases/dfu-util-0.8-binaries/win32-m ingw32/
Download the 5 files to the folder you created on your computer.

4. Disconnect Pamela's power cable. (I remove her completely from my rack)

5. Connect Pamela to your computer with a usb to mini-usb cable.

6. Run Zadig
Select: List all devices from the options menu
Select: STM 32 BOOTLOADER from the devices drop-down
Select: WinUSB
Click "Install Driver"

7. Open a terminal in Windows (you can usually find one at "All Programs\Accessories\Command Prompt")
Next you'll be entering the command to run the dfu-util program that updates Pam's firmware. You're going to need to specify the location of dfu-util as well as the new firmware file in the command--or to simplify things, (this is why I put everything in the same folder) change to that directory first.

8. In terminal type:
cd Downloads\Pam
(this should change the directory to Downloads\Pam. Your path may be a bit different, so figure out what it is and type it in. You can right click and view properties on a file in the folder to see the path.)

9. Now that you are in the \Pam folder you can type the command directly without specifying the location of the utility or the target file.
Type or (copy/paste for accuracy):
dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D alm017-189-BETA.bin


Done!


Nice write up.

Just a heads up, you can open command line straight to a directory by typing cmd into the folder path bar at the top of explorer while in said directory.

Figured this might help with steps 7/8 if people aren't comfortable navigating directories in command line.
ugokcen
Finally got my hands on Pam today hihi

The interface and the screen is great, very intuitive. This is the kind of module that will make the rest of your system immensely more capable. I spent hours patching different clocks into Rene's X an Y inputs for example. Synced lfos into the Loquelic Iteritas works wonders as well because Pam's got attenuation built in! Rockin' Banana!

Random skips and the ability to loop it is like a turing machine for your drums. Being able to rotate the euclidian patterns is super handy, lots of happy accidents!

I have only one quibble: the slop parameter is too strong even at 1%. At 10% it's like the drummer you kicked out after one practice. Maybe that could be re-calibrated?

Also, would it be possible to add a randomize levels parameter similar to the randomized skip parameter? It could 'humanize' lfos and envelopes when introduced ever so slightly.

Overall, thumbs up
ugokcen
Something's up with my Pam... sad banana

First thing I noticed today is that the module did not retain settings on power down. It goes back to the initial setting of 120BPM, all 8 outputs at x1 after a power cycle. Tried it in two cases, make noise powered skiff and a doepfer 6U, same thing.

After that I tried saving and loading banks and those don't work either! I go to the save menu and select a bank, click, and then the screen goes back to "??" as the manual says it should. But then when I try to load that bank all outputs have their parameters set to zero. I tried saving in many different locations and also the "global" save under the bpm screen. Nothing works very frustrating

Finally I tried updating the firmware, which went fine. However the same problem persists. Everything else works as it should.

Is there anyone who came across a similar behaviour? Please tell me I'm doing something stupid and it's not an hardware issue.
ALM
Ugokcen - can you try powering on Pam with the program knob held down to get into 'service' more - then scroll too 'Clear' and set to 'OK' to clear and reset the internal storage.

If that does not help then please shoot an email to help <at> busycircuits.com and will get you sorted asap.
ugokcen
Nope, that didn't help. I just shot you an email.

By the way, am I the only unlucky one? Do the saving and loading of banks work properly for everyone?
rikrak
ugokcen wrote:
Nope, that didn't help. I just shot you an email.

By the way, am I the only unlucky one? Do the saving and loading of banks work properly for everyone?


Saving/Loading banks and retaining settings on power cycle are all working fine here.
Zymos
Save and load works for me.
I do with there was some sort of "operation completed" confirmation, but it's not that big a deal.
miles_macquarrie
Anyone know of any US retailers with the new Pam in stock? I just sold my OG pam to help fund the new one and I'd love to replace ASAP

Cheers,
Miles
monads
ALM wrote:
I've uploaded a new beta '189' firmware for folks to try. It should be pretty solid.


Are we still in "beta" stage? I'm waiting for the official release before updating.

Thanks in advance ALM!
monads
Abyssinianloop
I dont see any reason not to update the firmware. It's nothing but fixes and impovements as far as I can tell.
Abyssinianloop
miles_macquarrie, keep an eye on the overseas retailers too. I got mine from Cyrmu Beats in Wales when all of the US retailers were out of stock. It took about a week and a half to arrive and was $40 cheaper than the US retailers wanted for "pre-orders."
miles_macquarrie
Abyssinianloop wrote:
miles_macquarrie, keep an eye on the overseas retailers too. I got mine from Cyrmu Beats in Wales when all of the US retailers were out of stock. It took about a week and a half to arrive and was $40 cheaper than the US retailers wanted for "pre-orders."



Good to know. Thank you.
iatroim
Abyssinianloop wrote:
I dont see any reason not to update the firmware. It's nothing but fixes and impovements as far as I can tell.


Agreed. I've been running the 189 firmware since it was released and haven't had any issues.
ALM
I've just uploaded a new 191 firmware which has just a single minor fix over 189 ('de-slopped' outputs fall back into sync correctly). I've had no other bug reports on so not calling it a beta anymore hyper .

See http://busycircuits.com/firmware/alm017/

Upcoming store restocks (few weeks away) will likely ship with this 191 version.
propertyof
Awesome! Thanks ALM
w00t
monads
ALM wrote:
I've just uploaded a new 191 firmware which has just a single minor fix over 189 ('de-slopped' outputs fall back into sync correctly). I've had no other bug reports on so not calling it a beta anymore hyper .


Sweet! Going to update over the weekend Rawk!
iatroim
ALM wrote:
I've just uploaded a new 191 firmware which has just a single minor fix over 189 ('de-slopped' outputs fall back into sync correctly). I've had no other bug reports on so not calling it a beta anymore hyper .

See http://busycircuits.com/firmware/alm017/

Upcoming store restocks (few weeks away) will likely ship with this 191 version.


Just updated to 191. Is the firmware update supposed to clear all the banks? It did with this update, but I don't remember if it did with 189 or not.

Just curious, I don't have a problem with starting over since I didn't save much on 189; it being a beta and all.
monads
iatroim wrote:


Just updated to 191. Is the firmware update supposed to clear all the banks? It did with this update, but I don't remember if it did with 189 or not.

Just curious, I don't have a problem with starting over since I didn't save much on 189; it being a beta and all.


The manual does say "updating the firmware is likely to clear all saved outputs."
monads
erstlaub wrote:
I hit a few bumps with install on my Mac as Terminal....

2. Go to http://www.open-tx.org/2013/07/15/dfu-util-07-for-mac-taranis-flashing -utility and install dfu-util that way as the terminal route was giving me bunk about network connections (have had the same issue re. X-code previously)

3. Disconnect your Pam's from the power, plug in the usb cable.

4. Open Terminal and copy and paste the following (minus the quotes) - 'dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D ~/Desktop/alm017-189.bin' - obviously change the filename accordingly. I had an issue copy and pasting from the old pdf manual as a linebreak was copied into terminal as a space which broke things but looks like the manual has been tweaked there too thumbs up

5. Hit enter and watch the code squirt into your module



#2 didn't work for me above. I'm running macOS Sierra 10.12.4. I went and followed the instructions per the manual by installing 'brew' and then running the 'brew install dfu-util' command line in Terminal. After that I followed instructions #4 & 5 above and was good to go.
iatroim
monads wrote:
iatroim wrote:


Just updated to 191. Is the firmware update supposed to clear all the banks? It did with this update, but I don't remember if it did with 189 or not.

Just curious, I don't have a problem with starting over since I didn't save much on 189; it being a beta and all.


The manual does say "updating the firmware is likely to clear all saved outputs."


Thanks! I didn't read the manual this time, I just ran the command with the updated path. I guess I just didn't remember from when I did the first upgrade.
L.C.O.
It seems that after the update the RUN/STOP CV control stopped working.
Or am I missing something?
ALM
L.C.O. wrote:
It seems that after the update the RUN/STOP CV control stopped working.
Or am I missing something?


Could you elaborate a bit ?

And was this 189 -> 191 ?
L.C.O.
ALM wrote:
L.C.O. wrote:
It seems that after the update the RUN/STOP CV control stopped working.
Or am I missing something?


Could you elaborate a bit ?

And was this 189 -> 191 ?


I have updated to, and am currently running the beta 189.

the RUN CV seems to only stop the module, does not start it back up. So, after the module is manually started, when I patch the CV to RUN, it will stop the clock on the "down" edge of the gate, but will not start it up with the "rising" edge of the incoming gate (which is how the module behaved in the previous firmware).

I am relatively new to Pam, so perhaps I am overlooking something, but I did notice that change between the firmware versions.

Is there some way that the user needs to define how the RUN CV behaves?
Spiked Lunch
Just got a quick Q about the random waveforms if someone doesn't mind answering.

Is the random waveform of the smooth fluctuating type and what are the parameters?

Thanks!
erstlaub
Spiked Lunch wrote:
Just got a quick Q about the random waveforms if someone doesn't mind answering.

Is the random waveform of the smooth fluctuating type and what are the parameters?

Thanks!


They are stepped, basically each clock event seeds a value, the same modifier parameters for all channels apply (random skipping percentage, delay, level, offset, euclidian parameters and slop) the only thing that doesn't do anything as per the manual is the width setting.

So for example you can have a set of random voltage changing at /4 of your clock, randomly skipping X triggers, attenuated down to 1v (20%) and set to a euclidian pattern of 6 beats in 9 spaces.

It's very, very excellent.
Spiked Lunch
erstlaub wrote:
Spiked Lunch wrote:
Just got a quick Q about the random waveforms if someone doesn't mind answering.

Is the random waveform of the smooth fluctuating type and what are the parameters?

Thanks!


They are stepped, basically each clock event seeds a value, the same modifier parameters for all channels apply (random skipping percentage, delay, level, offset, euclidian parameters and slop) the only thing that doesn't do anything as per the manual is the width setting.

So for example you can have a set of random voltage changing at /4 of your clock, randomly skipping X triggers, attenuated down to 1v (20%) and set to a euclidian pattern of 6 beats in 9 spaces.

It's very, very excellent.


Thanks for your quick and nicely explained reply.

I was really hoping the waveforms were smooth fluctuating rather than stepped (I've got that covered elsewhere).

I used to have a V1 PW, & loved the Euclidean firmware!
ALM
Spiked Lunch wrote:


I was really hoping the waveforms were smooth fluctuating rather than stepped (I've got that covered elsewhere).



Run it through a low pass ?
erstlaub
Given that it's unused but still exists in the context of the setting, I wonder if there'd be any possibility of the shape parameter could some day be used for a slew? I expect a smooth line takes more code/maths/processing than a step however and I'm not sure she can take it captain.

Theoretically with a bit of clever patching however, you could easily roll Pam's into spitting out smooth fluctuations by patching a random channel into the CV in and setting the cv in to the level setting of a sine channel meaning that the level of the peaks of the sine will be set at random levels (i think)...?
ALM
erstlaub wrote:
Given that it's unused but still exists in the context of the setting, I wonder if there'd be any possibility of the shape parameter could some day be used for a slew?


Agree would be nice. Never got it to work that well in past attempts :(
ALM
L.C.O. wrote:

Is there some way that the user needs to define how the RUN CV behaves?


I assume your not using an external clock ?

With the newer update run (to work correctly) expects an external clock to be present. This slightly improves syncing but means run does not work by itself.

To get the old behaviour back I need to think about things a bit as to avoid a third run option.
L.C.O.
ALM wrote:
L.C.O. wrote:

Is there some way that the user needs to define how the RUN CV behaves?


I assume your not using an external clock ?

With the newer update run (to work correctly) expects an external clock to be present. This slightly improves syncing but means run does not work by itself.

To get the old behaviour back I need to think about things a bit as to avoid a third run option.


Wait, so in the new firmware, the RUN CV is no longer a way to turn the. Lock on and off?
Abyssinianloop
L.C.O. wrote:
ALM wrote:
L.C.O. wrote:
It seems that after the update the RUN/STOP CV control stopped working.
Or am I missing something?


Could you elaborate a bit ?

And was this 189 -> 191 ?


I have updated to, and am currently running the beta 189.

the RUN CV seems to only stop the module, does not start it back up. So, after the module is manually started, when I patch the CV to RUN, it will stop the clock on the "down" edge of the gate, but will not start it up with the "rising" edge of the incoming gate (which is how the module behaved in the previous firmware).

I am relatively new to Pam, so perhaps I am overlooking something, but I did notice that change between the firmware versions.

Is there some way that the user needs to define how the RUN CV behaves?


Unlike you, I was getting perfect start/stops on firmware 189. With a beatstep pro as the master clock patched into Pam's Run input and nothing patched to the clock input.
Now on firmware 191 it seems that Pam needs something patched into the clock as well, for the run to work. I'm not sure how to achieve this. Multing the bsp clock out to both clock and run gives Pam a headache and she starts babbling nonsense. I think i'm going to roll back to 189, it seemed to work great for me.
ALM
Abyssinianloop wrote:

Unlike you, I was getting perfect start/stops on firmware 189. With a beatstep pro as the master clock patched into Pam's Run input and nothing patched to the clock input.
Now on firmware 191 it seems that Pam needs something patched into the clock as well, for the run to work. I'm not sure how to achieve this. Multing the bsp clock out to both clock and run gives Pam a headache and she starts babbling nonsense. I think i'm going to roll back to 189, it seemed to work great for me.


Patch the *clock* from the BSP into the Pamela clock - dont patch it also into the run! You dont need to patch anything into the the run - just turn it off in the pam BPM sub menu.. Or you can leave it on and split the run out of the BSP din sync signal (patched into Pam run input).

I think there is some confusion here - only the slop changed between 189 & 191, nothing sync related. What changed from 177 to 189 is now you cant correctly remotely start/stop via the run input *without* an external clock also being patched (into clock input). Hopefully not too bigger deal for most and Im working on a fix to bring old behaviour back.
Abyssinianloop
ALM wrote:

Patch the *clock* from the BSP into the Pamela clock - dont patch it also into the run! You dont need to patch anything into the the run - just turn it off in the pam BPM sub menu.. Or you can leave it on and split the run out of the BSP din sync signal (patched into Pam run input).

I think there is some confusion here - only the slop changed between 189 & 191, nothing sync related. What changed from 177 to 189 is now you cant correctly remotely start/stop via the run input *without* an external clock also being patched (into clock input). Hopefully not too bigger deal for most and Im working on a fix to bring old behaviour back.


Yes sorry, I think I was mixed up in my memory between 177 and 189/191 behavior. I apologize for any confusion that may have caused.

And thank you for explaining this connection for me. I think I was confused about how the Clock and Run inputs worked.
ALM
Abyssinianloop wrote:


Yes sorry, I think I was mixed up in my memory between 177 and 189/191 behavior. I apologize for any confusion that may have caused.



No problem at all - glad it makes sense now.

Also I now have a version which fixes up the run input again as before. If any one wants to test (and is slaving pam via run & clk inputs) shoot me a pm. Seems solid to me.
rikrak
Quick question. I'm running 191.

RESET on the "All Outputs" menu resets all Outputs' rate (ie "MODIFIER") to x1.

However, RESET on a single Output does not reset that Output's rate - it is unaffected.

Is this the expected behaviour? I would prefer to reset ALL that Output's parameters when I select RESET on an Output.
ALM
rikrak wrote:

Is this the expected behaviour? I would prefer to reset ALL that Output's parameters when I select RESET on an Output.


Yes always been this way.
L.C.O.
ALM wrote:
Abyssinianloop wrote:


Yes sorry, I think I was mixed up in my memory between 177 and 189/191 behavior. I apologize for any confusion that may have caused.



No problem at all - glad it makes sense now.

Also I now have a version which fixes up the run input again as before. If any one wants to test (and is slaving pam via run & clk inputs) shoot me a pm. Seems solid to me.


PM
Sent.
p.
rikrak
ALM wrote:
rikrak wrote:

Is this the expected behaviour? I would prefer to reset ALL that Output's parameters when I select RESET on an Output.


Yes always been this way.


I'll get used to it! Cheers for the reply.
ALM
Uploaded firmware 192 with a fix for the run input again start/stoping the clock without an external clock patched.

Grab it from http://busycircuits.com/firmware/alm017/

Thanks for everyones help!
atte
Amazing, thanks thumbs up
Worwell
ALM wrote:
Uploaded firmware 192 with a fix for the run input again start/stoping the clock without an external clock patched.

Grab it from http://busycircuits.com/firmware/alm017/

Thanks for everyones help!


Thanks for all the updates. This is a great module.

In considering whether I need to update, can someone explain the behavior with this feature. Say, I patched a manual gate into the Run with no external clock attached, would each new gate turn Pams on and off? Would the state change just while the gate is high or would it toggle on and off? Thanks in advance.
iatroim
Worwell wrote:
ALM wrote:
Uploaded firmware 192 with a fix for the run input again start/stoping the clock without an external clock patched.

Grab it from http://busycircuits.com/firmware/alm017/

Thanks for everyones help!


Thanks for all the updates. This is a great module.

In considering whether I need to update, can someone explain the behavior with this feature. Say, I patched a manual gate into the Run with no external clock attached, would each new gate turn Pams on and off? Would the state change just while the gate is high or would it toggle on and off? Thanks in advance.


It will cause the clock to run while receiving a CV signal and stop when the signal is not present. I'm not sure of the exact voltage it starts/stops the trigger, but I believe it's fairly low.
BonJoey
ALM wrote:
Uploaded firmware 192 with a fix for the run input again start/stoping the clock without an external clock patched.

Grab it from http://busycircuits.com/firmware/alm017/

Thanks for everyones help!


we're not worthy
L.C.O.
ALM wrote:
Uploaded firmware 192 with a fix for the run input again start/stoping the clock without an external clock patched.

Grab it from http://busycircuits.com/firmware/alm017/

Thanks for everyones help!


Fantastic!

So inspiring to see your amazing work.

I just wanted to once again point out how Pam is a stellar example of digital module that work in a super intuitive fashion, without compromising depth and functionality.

I am especially impressed with the fact that the module maintains it's state through power cycles, and at the same time gives user great amount of control over various settings, presets, etc.

Just a great design!

Thank you for your hard work!
p.
ALM
hyper hyper hyper hyper hyper hyper hyper hyper

ALM will be at Superbooth later this week. Booth 0502. Please come by if you have any questions regarding or would like to check out a demo of the new Pam.
jwise
I successfully updated Pamela's New Workout to firmware v192 on Windows 10 without any problem. Just had to move the .bin file to the root of C:\ so the util could find it. And the advice in the manual that says use version 8 not 9 - pay attention.
funqpatrol
Not sure if this is in the works but would love to be able to recall a saved group by CV?

Is that a reasonable request? smile
adderbrew
Is there anywhere that still has this in stock?
dash80
I've been having pretty good usage with the stock og firmware and haven't really noticed any problems, but also haven't dove too deep yet.

Will have to update soon. Thanks for all the hard work, ALM!
Abyssinianloop
funqpatrol wrote:
Not sure if this is in the works but would love to be able to recall a saved group by CV?

Is that a reasonable request? smile


Maybe like a sequential switch, where a CV causes the loading of a bank either moving forward or backward through the banks. I can see that being pretty awesome.
atte
Abyssinianloop wrote:
funqpatrol wrote:
Not sure if this is in the works but would love to be able to recall a saved group by CV?

Is that a reasonable request? smile


Maybe like a sequential switch, where a CV causes the loading of a bank either moving forward or backward through the banks. I can see that being pretty awesome.


+1
analoglsd
I'm using a Mac running 10.8.5 and have made ZERO progress attempting any of the update procedures outlined here.
Can anyone make a very clear list of operations to take to get the firmware into the module.
I do not speak any computer language. I know synths, not computers.
Any help would be appreciated.
analoglsd
Also, if there's anyone in the San Francisco Bay Area that would like to visit the Vintage Synthesizer Museum for free for any hour, come over and update this fucking module, and I'll hook you up!
exper
Analoglsd, at which point are you stuck? Did you install homebrew and then dfu-util in Terminal?
dooj88
A stable update eh? Very very nice! I've got a project tomorrow.
analoglsd
exper wrote:
Analoglsd, at which point are you stuck? Did you install homebrew and then dfu-util in Terminal?


Installed homebrew. Once installed it provided a link to the Apple App store for something else I needed to download, but I wasn't able to because I'm running 10.8.5...
Installed dfu-util in Terminal as far as I know. I downloaded it and installed it. The only thing I can find related to is is a Terminal screen that comes up and says this:
Last login: Sat Apr 22 17:59:54 on ttys000
Lances-iMac:~ LanceHill$ /opt/local/bin/dfu-util ; exit;
dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Error: You need to specify one of -D or -U

Usage: dfu-util [options] ...
-h --help Print this help message
-V --version Print the version number
-v --verbose Print verbose debug statements
-l --list List the currently attached DFU capable USB devices
-e --detach Detach the currently attached DFU capable USB devices
-d --device vendor:product Specify Vendor/Product ID of DFU device
-p --path bus-port. ... .port Specify path to DFU device
-c --cfg config_nr Specify the Configuration of DFU device
-i --intf intf_nr Specify the DFU Interface number
-a --alt alt Specify the Altsetting of the DFU Interface
by name or by number
-t --transfer-size Specify the number of bytes per USB Transfer
-U --upload file Read firmware from device into <file>
-D --download file Write firmware from <file> into device
-R --reset Issue USB Reset signalling once we're finished
-s --dfuse-address address ST DfuSe mode, specify target address for
raw file download or upload. Not applicable for
DfuSe file (.dfu) downloads
logout

[Process completed]
erstlaub
Did you try the method i got to work that posted a few pages back? It might be down to older OS issues, i hate that apple constantly have us over a barrel with that.
ALM
analoglsd - it looks like dfu-util is installed ok.. Just type the *full* dfu-util command from the manual (copy and paste it) into the terminal window with Pam connected and all should work ok.
L.C.O.
ALM wrote:
analoglsd - it looks like dfu-util is installed ok.. Just type the *full* dfu-util command from the manual (copy and paste it) into the terminal window with Pam connected and all should work ok.


But also, one must remember to use the correct name of the firmware file at the end of that pathname...
Abyssinianloop
I'm hoping someone using Pam's New with a Beatstep Pro can clear something up for me. Sometimes I like to use Pam as the master clock and sometimes I like to use the BSP.

I'm using the the latest firmware for both:
Pam 192
BSP 1.4.0.20

To use BSP as a master clock and start/stop both Pam and BSP from the BSP, I set both to PPQN 24 and patch the clock out of BSP into the Clk input on Pam with Run set to N.

This way everything works well and even though Pam displays a bpm that is off only by 1 (example: BSP shows 120 and Pam shows 119), everything sounds right and syncs well.

alternatively

To use Pam as the master, I patch one of Pam's outputs to BSP clock in. However, PPQN 24 doesn't work. 120 bmp on Pam translates into something super slow like 5 on the BSP. I have to set both to PPQN 1 to make things work. Then they sink well and show identical bpm. But if I try keeping PPQN 1 and using BSP as the master, using 120 bpm on the BSP causes Pam to max out at 300.

What's going on here, anyone else experience the same?
ALM
Abyssinianloop wrote:


To use BSP as a master clock and start/stop both Pam and BSP from the BSP, I set both to PPQN 24 and patch the clock out of BSP into the Clk input on Pam with Run set to N.

This way everything works well and even though Pam displays a bpm that is off only by 1 (example: BSP shows 120 and Pam shows 119), everything sounds right and syncs well.


If this is a problem you can calibrate/trim Pams internal clock to get a better visual match - Power Pam on with the program knob held down and adjust the 'Calib' value.. likely by just +/- 1.

Note this wont actually change the syncing (it will be just as tight either way) - it just alters Pams idea of 'representing time' slightly.

Abyssinianloop wrote:


To use Pam as the master, I patch one of Pam's outputs to BSP clock in. However, PPQN 24 doesn't work. 120 bmp on Pam translates into something super slow like 5 on the BSP. I have to set both to PPQN 1 to make things work. Then they sink well and show identical bpm. But if I try keeping PPQN 1 and using BSP as the master, using 120 bpm on the BSP causes Pam to max out at 300.


Sorry I dont completely follow. If Pam is the master you shouldn't need to change its PPQN value (under BPM screen) - thats just for incoming clock. Or are you saying adjusting PPQN on BSP alters it for both incoming and outgoing clock ? I usually use the din sync or midi input on the BSP to slave it to Pam (via expander or uses a x24 & 'on' output for din sync) and that seems to 'just work'.
Abyssinianloop
ALM wrote:

Sorry I dont completely follow. If Pam is the master you shouldn't need to change its PPQN value (under BPM screen) - thats just for incoming clock. Or are you saying adjusting PPQN on BSP alters it for both incoming and outgoing clock ? I usually use the din sync or midi input on the BSP to slave it to Pam (via expander or uses a x24 & 'on' output for din sync) and that seems to 'just work'.


Thanks for your help. I just double-checked. Yes, the BSP PPQN setting seems to affect both incoming and outgoing clock. So, when outgoing, I've found that Pam likes BSP to be set to 24. When incoming to the BSP clock in, the BSP seems to like being in PPQN 1 with a x4 Pam output, and as you said--it makes no difference what Pam's PPQN is set to.

I guess it boils down to a crazy BSP clock input? I'll look around the BSP settings software to see if I can find any other setting options.

I've never used the BSP midi in/out.
ALM
Abyssinianloop wrote:


I guess it boils down to a crazy BSP clock input? I'll look around the BSP settings software to see if I can find any other setting options.



Yep could well be.. googling around it seems its behaviour changes between firmware versions ?

FWIW Driving it via Pam and a DSG (or similar Din Sync adaptor) to its Din Sync input its just worked for me in the past.
Abyssinianloop
The other BSP-related thing I've noticed is that when slaving Pam to the BSP (BSP clock out to Pam Clk with Run set to N and PPQN 24), although the tempo is synced, there seems to be a small difference between Pam's gates and the BSP's drum gates. So that if I have Pam triggering Dinky's, and BSP drum gates triggering other Dinky's parameters, I have to shift the BSP drum gates back by -10 for them to land at the same time as Pam.
hihache
I have an original Pam's and I love it.

One of the features with new Pam's says "waveform levels." Does that mean I am able to control 0-5V level of each trigger/gate? Essentially I want to know if it would be useful for doing funny things to the 0-5V modulation inputs on Sid's Guts.
ALM
Abyssinianloop wrote:
The other BSP-related thing I've noticed is that when slaving Pam to the BSP (BSP clock out to Pam Clk with Run set to N and PPQN 24), although the tempo is synced, there seems to be a small difference between Pam's gates and the BSP's drum gates. So that if I have Pam triggering Dinky's, and BSP drum gates triggering other Dinky's parameters, I have to shift the BSP drum gates back by -10 for them to land at the same time as Pam.


This is more a Dinky thing than a specific Pam one. The parameter inputs on the Dinky need to be set when the trigger arrives. If Pam is slaved (and is the trigger source) it will likely be very very slightly behind (~microseconds) the master and thus gate like params (from master) could get missed as effectively not set when trigger arrives.
ALM
hihache wrote:
Does that mean I am able to control 0-5V level of each trigger/gate?


Yes hyper
dash80
Abyssinianloop wrote:


...

What's going on here, anyone else experience the same?


I've only used my BSP as the master clock, into Pam, and have noticed the slight difference in BPM reading between the two. But they are both in sync.

Just for ease of mind knowing they are and as said, you can hold *SHIFT* and turn the BPM knob to do fine tuning to get it matched.

Besides that, I haven't tried much else, but it's been solid as a rock with the original firmware.
insect
was nice to see new Pam on the Superbooth It's peanut butter jelly time! It's peanut butter jelly time! It's peanut butter jelly time!

Do you know when a new stock will be available in Germany? Any other shops then Schneiders too??

I have the old pam and the sync to Yarns or via Din Sync I would call it wonky. How does sync the new Pam compared to the old? Is there a kind of test out there in the interweb?
chockfullofthat
Any update on availability on the second batch? I'm sitting on a preorder atm.
ALM
Second batch started shipping out today. Expect stock to start re-appearing at dealers over next couple of weeks.
propertyof
ALM wrote:
Second batch started shipping out today. Expect stock to start re-appearing at dealers over next couple of weeks.

yes! right on time! got my pam wristband from superbooth ready, cant wait to wiggle with pam! hyper
Fiddlestickz
So any of this new batch heading to Perfect Circuit..?
cliffemu
ALM wrote:
BonJoey wrote:
funqpatrol wrote:
Will it be possible to recall a set of output with CV ala Tempi?


I'd also like to know the answer to this


Havn't yet got CV controlled loading working in a way Im happy with.


If you could do this, it seems you would effectively create an 8 channel, cv-addressable cv programmer. Imagine those possibilities smile
ALM
Fiddlestickz wrote:
So any of this new batch heading to Perfect Circuit..?


Yes and other US and international dealers. Please email your favourite store for more info hyper
hihache
Fiddlestickz wrote:
So any of this new batch heading to Perfect Circuit..?


I put my preorder in last week thumbs up
boboter
Can someone help me with the update process? I'm on OSX 10.10.5 and tried everything mentioned in the manual as well as the tips in this thread. Still, terminal always says "command not found".

I don't understand Terminal at all so it sure is my fault. I just copied various versions of the command line and pressed enter. Pam is hooked up via USB and file-destination and -name are entered properly.

hmmm.....
ALM
If you enter just 'dfu-util' in the Terminal and hit return what do you get ?
boboter
It then also says 'Command not found'.
ALM
It looks like you dont have dfu-util installed ? What does 'brew install dfu-util' give you ?
boboter
Another 'command not found'.
ALM
You need to first install 'Brew' - see pg 20 of the manual. Basically follow instructions here - https://brew.sh/ and then run 'brew install dfu-util' .

Alternatively you could try installing the dfu-util via the .pkg linked earlier in the thread which has worked for some (eg see https://www.muffwiggler.com/forum/viewtopic.php?p=2518038#2518038 )

Once either of the above steps are completed, then follow the instructions on pg 21 of the manual.
Torn n Frayed
Control has them in stock currently.
boboter
ALM
The update worked find now. Thanks a lot for your help and patience.
uebl
muting and vertical offsets? man, this is getting better and better. so glad I got one.
miles_macquarrie
I have not updated yet, but this thing is so badass. As a OG pam user the new features are really easy to understand and I didn't even need to look at the manual to get started. I had a Octocontroller and found it to not be as fun to use. Using the menu doesn't feel like menu diving at all. <3
ALM
FYI all new restocked Pams going out atm should come with the latest 192 firmware already installed.
uebl
firmware update worked just as described; great!
richardisabelle
They have arrived at Perfect Circuit. I had one on preorder and it shipped today.
trickness
I'd love to see a series of video tutorials by ALM on YouTube. It's a very easy to use module (got mine yesterday!) but some deep tricks would be nice to see.
esotericmetal
Just ordered one! Excited to get my hands on it.
boboter
Man, the offset parameter in the new OS makes Pam such a great module. I just ordered a second one.

I believe it is one of the best modules ever.
Jezzameister
I seem to have an issue with the New Pams module.

The bpm is not what it says it is. When recording into my DAW, I found that 120bpm on Pams is actually 120.27bpm. This problem means I can't use the module as a master clock because it is slightly out of time with my logic projects and other gear etc.

I think this is causing the 'wrong bpm display' when using an external clock (as mentioned above in other posts)

Firmware is up to date and I have tried calibration, but it is still out of time...

The module has some great functions, but if this problem continues I am likely to return it. Any solutions?
ALM
If you want Pam (or any other bit of gear) to match BPM's very precisely with other gear then you need to physically sync them..
Jezzameister
But I'd like to use pams as my master clock.

Is it possible to calibrate it so that the 120 shown on the display is actually 120bpm? Atm it's showing in logic as 120.27.

Ive also got Mutable Yarns and when it displays 120, it is actually 120bpm.

Thanks
ALM
Jezzameister wrote:
But I'd like to use pams as my master clock.

Is it possible to calibrate it so that the 120 shown on the display is actually 120bpm? Atm it's showing in logic as 120.27.


Thats still 120 bpm rounded... How many decimal places of accuracy do you need ? and why ?

I can look into adding finer calibration of the clock but Im just trying to understand if its really a practical problem or not..? Logic wont care if its not precisely 120 bpm ?

If yarns is more accurate for your needs, use that as your master and slave Pam to it ? Wont Yarns be getting its clock from the DAW (via physical MIDI) anyway though ?
c0nsumer
ALM wrote:
Jezzameister wrote:
Is it possible to calibrate it so that the 120 shown on the display is actually 120bpm? Atm it's showing in logic as 120.27.


Thats still 120 bpm rounded... How many decimal places of accuracy do you need ?


Not trying to be too critical here, and I'm considering buying a PNW myself soon, but one decimal place seems like a reasonable thing. I have to admit that, on its face, this disparity does give me a bit of pause... Especially as I'll be using it with a BSP and it'd irk me if one device said one BPM and another said nearly another.

Although, at the same time, I do recognize that the job of the master clock is to be the source of truth. So no matter what it actually is, so long as things are in sync and sound good then it's good.
Jezzameister
Lets say I make some drum loops on my modular rack with Pams as my master clock (without logic) and record them straight onto a tascam recorder. When I later import them into logic, I then have to guess the bpm to make them fit to grid because the bpm displayed on pams is slightly off. It would better if there wasn't any decimal points at all.

I understand that I can use yarns as my master clock to slave pams but I am actually planning to sell yarns so I would like pams to be my master clock.
c0nsumer
Jezzameister wrote:
Lets say I make some drum loops on my modular rack with Pams as my master clock (without logic) and record them straight onto a tascam recorder. When I later import them into logic, I then have to guess the bpm to make them fit to grid because the bpm displayed on pams is slightly off. It would better if there wasn't any decimal points at all.

I understand that I can use yarns as my master clock to slave pams but I am actually planning to sell yarns so I would like pams to be my master clock.


The thing is, there's really no such thing as a perfect clock... So while it can be pretty darn accurate there's always going to be some skew.

Hell, if you had two identically functioning oscillators, then took one into a plane for some wiggling, it'd be running at a different rate than the one still on the ground. Thanks, relativity!

But, at the same time, I do have the not-great feels from seeing one thing saying 120 BPM and another saying 120.27 (or as I recall reading here on MW some cases with the BSP reporting 121 and the PNW 120) when one is sync'd to the other...
ALM
Jezzameister wrote:
Lets say I make some drum loops on my modular rack with Pams as my master clock (without logic) and record them straight onto a tascam recorder. When I later import them into logic, I then have to guess the bpm to make them fit to grid because the bpm displayed on pams is slightly off. It would better if there wasn't any decimal points at all.


Pretty sure Logic has the ability to detect tempo of imported audio.

And they'll alway be *some* decimal places (which is why Logic and other DAWs offers up this kind of functionality?)
ugokcen
I have not tried syncing my DAW (Logic) to Pam, but I've done it the other way around using an audio pulse from the computer and the sync is absolutely dead-on. What may be causing the confusion is that the tempo displayed in Logic is different from what's displayed on Pam, sometimes as much as 1 bpm. I don't know why that is, maybe ALM could look into that?

Not that it matters in the end, but it creates a suspicion that something is amiss.
ALM
c0nsumer wrote:


Not trying to be too critical here, and I'm considering buying a PNW myself soon, but one decimal place seems like a reasonable thing. I have to admit that, on its face, this disparity does give me a bit of pause... Especially as I'll be using it with a BSP and it'd irk me if one device said one BPM and another said nearly another.



I measured this kind of accuracy during development but in doing this also measured alot of (slight) variation in representation of bpm in external gear.

I'll add investigating finer clock calibration to the TODO but Id still be prepared to be irked if you sync multiple bpm displaying devices.

As long as its sonically in sync and sounds good thats what really matters right ?
Zymos
Ive had all kinds of gear synced with each other, and a tempo display that does NOT vary by a fraction of a BPM is more the exception than the rule.
Doesn't mean the BPM is not steady, just that what is displayed may be slightly vague. If I let things run for 20 minutes and can't hear the tempos drifting, I'm not going to pay attention to the display.

But, if you have some way to measure exactly, and one thing shows a steady 120 BPM yet something clocked by it shows a steady 120.1 BPM, that's something else. Though how much it matters is the real issue...
Jezzameister
The problem is, if somebody asks me to create a drum loop for a track thats at 120bpm and I do it with Pams and its actually 120.27bpm. When I send them the loop, it will be out of sync with their track which is running at 120bpm. In other words I need it to be more accurate than a quarter of a bpm out.

I can create tempo related loops on the Korg Volcas, Prophet 6, Microkorg and Mutable Yarns and drop them into a logic or pro tools session running at 120bpm and they are all in sync. But when I try the same thing with Pams its not in sync because its not running at exactly 120bpm.

Other people send me tempo related stems created on all kinds of different gear and they always run in sync in my sessions. I don't have to vary the decimal place to make them in sync.

I hope that makes sense, I'm just trying to explain the way I work and how i want to use Pams. The module is great but I just wonder if there is a way to make it even more accurate?
Zymos
OK, I hear ya- was just wondering if things were actually out of sync, or if that was only based on a tempo readout somewhere.

That's a bummer- I think the way most people use the module, it's not an issue, but I don't think you are wrong for wanting it to work in your situation too.
ALM
OK I will investigate and try for better/more control over the calibration in a future update.

In the meantime if you need a very specific BPM and even after calibrating Pam you still don't get what you want either;

- Slave Pam to external clock which gives you what you want. Ignore any subtle difference in displayed BPMs. If it sounds in sync it is.

- Learn/use your DAW's tools to make minor tempo adjustments to, or sync to, audio imports.

- Just don't worry about, instead just make music & enjoy hyper
Krater
Awaiting the delivery of my new Pam today hyper but will keep the old one though. What is the best way to sync the two?
ugokcen
Jezzameister has a fair point, though I don't work in that way. But i might in the future so it would be nice to see this addressed.


Quote:
- Slave Pam to external clock which gives you what you want. Ignore any subtle difference in displayed BPMs. If it sounds in sync it is.


I can confirm that this method does work perfectly.
ALM
Krater wrote:
Awaiting the delivery of my new Pam today hyper but will keep the old one though. What is the best way to sync the two?


Using either Pam as master - One output at x24 into slaved pam clock input. Another output set to 'constant on' into slaved pam run input.

Ideally use new Pam as master + 2hp Pam Exp-2 expander - then use x24 & run outputs of the expander into old pam. That way you don't lose any editable outputs.
Krater
Thanx!
chockfullofthat
Got mine a couple of days ago. Easier than expected menu diving. The clock was about 1.5 bpm fast out of the box but calibration got it within 0.1 bpm of the displayed value. Liking it a lot.
guestt
This is tickling my interest a lot, good work(out)!!

I must admit the BPM calibration is of some concern to me too, as rightly pointed out irrelevant in most situations, but I'd feel frustrated when in a position where I needed it to be right.

So +1 for better control over calibration from me too; if it's sorted I'm going to find it difficult to resist smile)))
erstlaub
Krater wrote:
Awaiting the delivery of my new Pam today hyper but will keep the old one though. What is the best way to sync the two?


When I slave mine, i tend to use old Pam's as the master seeing as it *only* does gates/triggers and it makes me sad to tie up 2 channels on new Pams that could also be doing modulation things.

They always sync perfectly although the BPM displays have a discrepancy of 1 bpm between them on mine as I've not got round to doing the display calibration thing yet.
ALM
erstlaub wrote:

When I slave mine, i tend to use old Pam's as the master seeing as it *only* does gates/triggers and it makes me sad to tie up 2 channels on new Pams that could also be doing modulation things.


Just to reiterate this is what the 2HP PEXP2 expander is really useful for.. it gives you the extra outputs specifically for the slaving another Pam (old or new). Thus you dont lose any channels (and you get a midi clock out).
jasev
Just got one of these can't wait to get it racked up tomorrow
AThousandDetails
Going to get mine Monday! Anyone is using ERM Multiclock+ to sync the new Pamela? Is it more stable than the old PAM?

I had tons of issues syncing old Pam with Syncgen, A4 and even Multiclock+ which later i found a way to make it more stable with the multiclock+ and it is now flawless...

Thanks!
MossGarden
ALM wrote:
Krater wrote:
Awaiting the delivery of my new Pam today hyper but will keep the old one though. What is the best way to sync the two?


Using either Pam as master - One output at x24 into slaved pam clock input. Another output set to 'constant on' into slaved pam run input.

Ideally use new Pam as master + 2hp Pam Exp-2 expander - then use x24 & run outputs of the expander into old pam. That way you don't lose any editable outputs.


I was thinking of using this expander in future to sync my mother 32. Midi clock out to M32, then Run to M32's sequencer. I can't see any reason this wont work? I would then use the x24 to clock my Beatstep Pro
Tumulishroomaroom
I clock my Mother 32 with one out of the new Pamela and I works perfectly.
behndy
only 5 pages in, trying to read EVERYTHING because y'all are interesting, INTERESTING buggari-boos.

but. just got in my New Pam's and had to wurmp around. so. damn. GOOD.

having a problem, sure it's my fault, but trying to use Pam's to clock a Beatstep Pro, and it was running at 1/16 of the tempo on the Pam's.

went in to the BSP software to play with the settings, at 24 PPQN (the default) it's 1/16, 48 PPQN it's i THINK at 1/32 of tempo, and at 1 Step it's at 1/4 of tempo.

which is betttttttterrrrrrrrr...... but. would love to know what i'm doing wrong.

moop?
iatroim
behndy wrote:
only 5 pages in, trying to read EVERYTHING because y'all are interesting, INTERESTING buggari-boos.

but. just got in my New Pam's and had to wurmp around. so. damn. GOOD.

having a problem, sure it's my fault, but trying to use Pam's to clock a Beatstep Pro, and it was running at 1/16 of the tempo on the Pam's.

went in to the BSP software to play with the settings, at 24 PPQN (the default) it's 1/16, 48 PPQN it's i THINK at 1/32 of tempo, and at 1 Step it's at 1/4 of tempo.

which is betttttttterrrrrrrrr...... but. would love to know what i'm doing wrong.

moop?



̶M̶a̶k̶e̶ ̶s̶u̶r̶e̶ ̶y̶o̶u̶ ̶s̶e̶t̶ ̶t̶h̶e̶ ̶P̶P̶Q̶N̶ ̶r̶e̶s̶o̶l̶u̶t̶i̶o̶n̶ ̶a̶s̶ ̶2̶4̶ ̶P̶P̶Q̶N̶ ̶o̶n̶ ̶t̶h̶e̶ ̶P̶N̶W̶ ̶a̶s̶ ̶w̶e̶l̶l̶.̶ ̶I̶'̶m̶ ̶r̶u̶n̶n̶i̶n̶g̶ ̶m̶i̶n̶e̶ ̶f̶r̶o̶m̶ ̶a̶ ̶T̶e̶m̶p̶e̶s̶t̶ ̶>̶ ̶K̶e̶y̶s̶t̶e̶p̶ ̶>̶ ̶P̶N̶W̶ ̶a̶t̶ ̶2̶4̶ ̶P̶P̶Q̶N̶ ̶a̶n̶d̶ ̶a̶t̶ ̶1̶x̶ ̶i̶t̶ ̶c̶l̶o̶c̶k̶s̶ ̶p̶e̶r̶f̶e̶c̶t̶l̶y̶ ̶w̶i̶t̶h̶ ̶n̶o̶ ̶d̶r̶i̶f̶t̶.̶

Whoops I misread that. I believe the sync in on the Beatstep is also set by the PPQN defined in the Arturia control panel. I'm not sure why it wouldn't be in tempo if they're set the same.
behndy
jia. i left the Pam's alone, it is default setup at 24.

in the BSP software menu you can set it to 24 or 48 PPQN or 1 Step.

i'm super new to all modular stuff, so am probably missing something simple.
funqpatrol
I've asked before but will there be a chance to get CV over preset loading? Thanks! smile
jasev
funqpatrol wrote:
I've asked before but will there be a chance to get CV over preset loading? Thanks! smile


Be a good feature if at all possible??
ALM
funqpatrol wrote:
I've asked before but will there be a chance to get CV over preset loading? Thanks! smile


How would you use it ? What sort of thing would you see yourself doing with it ?
dooj88
i noticed cracking when using the sin and triangle shapes to open/close a VCA - specifically veils. but when i A/B it with a similar shaped signal from maths, there is no crackling. i shot a video, but the maths signal was too hot and distorted the recording.. (noob boob had the attenuator too high and didn't check recording afterwords..) anyway, i'll shoot another video this evening. but here's a decent enough example of the behavior:
https://youtu.be/3uCM_RPaMy0
(i normalized the audio, so if you have to crank the volume, i made sure there are no peaks that are super loud..)

things i've tried:
-changing level of signal, still there but attenuated
-different shapes still have same behvior (envelope, sin, tri)
-trying different output channels/jacks there is no change
-had a high power load on my PSU before, but i got another yesterday, and after reducing the whole load by half that the circuit pam was on, the crackling persisted.

i noticed this when i first got it, and just decided to just not use it for VCA modulation, but now i'd like to know what's going on. another note, i haven't updated the firmware since i received it at the end of march.

any other things to try? anyone else hearing this?
cryptogreen
Jezzameister wrote:
The problem is, if somebody asks me to create a drum loop for a track thats at 120bpm and I do it with Pams and its actually 120.27bpm. When I send them the loop, it will be out of sync with their track which is running at 120bpm. In other words I need it to be more accurate than a quarter of a bpm out.

I can create tempo related loops on the Korg Volcas, Prophet 6, Microkorg and Mutable Yarns and drop them into a logic or pro tools session running at 120bpm and they are all in sync. But when I try the same thing with Pams its not in sync because its not running at exactly 120bpm.

Other people send me tempo related stems created on all kinds of different gear and they always run in sync in my sessions. I don't have to vary the decimal place to make them in sync.

I hope that makes sense, I'm just trying to explain the way I work and how i want to use Pams. The module is great but I just wonder if there is a way to make it even more accurate?


I honestly thought that was what I was paying for when I bought PNWO, especially when I read phrases like "Improvements have been made to overall clock stability," and "BPM based clock with tempo rates 10-300BPM." The natural conclusion was that PNWO would sync to the grid when the DAW and PNWO display the same rate.

I love the workflow the module provides more than I thought I would, but the honeymoon ended abruptly when I realized what you see is not what you get with PAM.

So PLEASE, if it is possible, quantize pam so she can play along with my ipad or whatever without being made a slave.
ALM
cryptogreen wrote:

So PLEASE, if it is possible, quantize pam so she can play along with my ipad or whatever without being made a slave.


For two things to stay in reliably in sync you absolutely have to physically sync them!

The precision of the clock calibration to match external BPMs can likely be increased (and am investigating as previously stated) but depending on just this to keep sync reliably with external equipment is a very bad idea. Its like a band trying to keep time to a drummer with there eyes and ears closed.
cryptogreen
I was reflecting that all the devices i have that currently are able to stay in sync in definitely without having to be physically connected are on a network. So I suppose the analogy would be the band playing with eyes and ears closed but with a psychic connection.

I suppose it was naive to think that a module would have the same clock accuracy as a laptop, but i am confused as to the limitations. There definitely are atomic clocks that have no perceivable clock drift at all. They can be pretty inexpensive as well, although they are wall clocks. Can you help me understand what prevents PNWO getting that level of accuracy?
esotericmetal
Just wanted to say that this module is brilliant! Amazing how much you can do with just 8hp. Been using it with a mother-32, 0-coast and a small 96hp rack and it's working out very well. Haven't even tried out any of the euclidean stuff yet.
behndy
yessssssss. Pam's so GOOD.

simple patterns from the Beatstep Pro into the Basimilus Iteritas Alter with all the envelopes and clock division yumminess of the Pam's -



i've only had her a day and i lurrrrrrrv her.
cryptogreen
@esotericmetal The euclidean stuff is brilliant. It's the perfect thing for people like me that never learned how to properly sequence drum machines.
ugokcen
Quote:
I was reflecting that all the devices i have that currently are able to stay in sync in definitely without having to be physically connected are on a network.


Can you explain further how you are getting your gear in sync without a physical connection? Are you talking about different bits of software running on the same computer?

Even with just laptops and software it was notoriously difficult to get two computers in sync until Ableton came along with their "Link" technology. While that is not a physical connection, it is a wireless connection nonetheless. And before computers were standard production tools getting midi gear synced to tape was an even more troublesome affair.

Pioneer's CDJs also need to be physically connected to stay in sync and those things don't drift at all.

Long story short, I don't believe it's possible to get different bits of hardware to sync without a physical connection. But I may be proven wrong, so please let us know!
aroom
Quote:
I don't believe it's possible to get different bits of hardware to sync without a physical connection.


I don't believe it neither. It's just an hardware clock issue. There aren't two clocks in this world who are exactly on the same pace. Right?

We use atomic clock to keep everyone in time, but it's a matter of correcting everyone's clock being connected (radio waves, internet, with your fingers)

So it's the same with computers, electronics. It's just a quartz clock. You need to sync it, master / slave.


I wonder now if you work on a daw with a specific bpm, and share the file. When you open it on another computer, it would just stretch/correct it, to keep the same value, same loop?
guestt
I think you're also talking about the clocks being in phase, i.e. they both start at exactly the same time and hit the next bar at exactly the same time. If there is even just a tiny discrepancy between the start times then the phase difference will become more pronounced over time.

What I think the problem here is is that 120bpm is not actually 120bpm or close enough to not matter when recording a single bar as a sample loop that can be loaded up in a DAW and used without time stretching.

I can do this with a whole load of gear too, usually the Octatrack, when I record a 4 bar sample at 120bpm, I can copy it to my computer and load it up into Ableton as a loop and it works perfectly without time stretch. 120bpm should be 120bpm. I don't think there's any reason not to have this level of accuracy, we're no where near the accuracy of an atomic clock for this to work correctly.

It would be interesting to see just how many samples there are different between different devices. When recording 4 beats or one bar at 120bpm is 2 seconds of music! At 96KHz that's 192000 samples. So in theory the clock should be at least this accurate, which is not really very accurate at all.

I think anyway, maybe I missed something! Happy to be proven wrong smile

p.s. for what it's worth I also think that you should sync too! Ableton Link has been an absolute godsend for syncing DAW/iPad/Octatrack/Modular together - it's amazing!
dooj88
dooj88 wrote:
i noticed cracking when using the sin and triangle shapes to open/close a VCA - specifically veils. but when i A/B it with a similar shaped signal from maths, there is no crackling. i shot a video, but the maths signal was too hot and distorted the recording.. (noob boob had the attenuator too high and didn't check recording afterwords..) anyway, i'll shoot another video this evening. but here's a decent enough example of the behavior:
https://youtu.be/3uCM_RPaMy0
(i normalized the audio, so if you have to crank the volume, i made sure there are no peaks that are super loud..)

things i've tried:
-changing level of signal, still there but attenuated
-different shapes still have same behvior (envelope, sin, tri)
-trying different output channels/jacks there is no change
-had a high power load on my PSU before, but i got another yesterday, and after reducing the whole load by half that the circuit pam was on, the crackling persisted.

i noticed this when i first got it, and just decided to just not use it for VCA modulation, but now i'd like to know what's going on. another note, i haven't updated the firmware since i received it at the end of march.

any other things to try? anyone else hearing this?


Bumping this since its in the middle of the sync discussion
cryptogreen
Baddcr wrote:
I think you're also talking about the clocks being in phase, i.e. they both start at exactly the same time and hit the next bar at exactly the same time. If there is even just a tiny discrepancy between the start times then the phase difference will become more pronounced over time.

What I think the problem here is is that 120bpm is not actually 120bpm or close enough to not matter when recording a single bar as a sample loop that can be loaded up in a DAW and used without time stretching.

I can do this with a whole load of gear too, usually the Octatrack, when I record a 4 bar sample at 120bpm, I can copy it to my computer and load it up into Ableton as a loop and it works perfectly without time stretch. 120bpm should be 120bpm. I don't think there's any reason not to have this level of accuracy, we're no where near the accuracy of an atomic clock for this to work correctly.

It would be interesting to see just how many samples there are different between different devices. When recording 4 beats or one bar at 120bpm is 2 seconds of music! At 96KHz that's 192000 samples. So in theory the clock should be at least this accurate, which is not really very accurate at all.

I think anyway, maybe I missed something! Happy to be proven wrong smile

p.s. for what it's worth I also think that you should sync too! Ableton Link has been an absolute godsend for syncing DAW/iPad/Octatrack/Modular together - it's amazing!


I am using two ipads and a laptop along with my modular. Sometimes I even use Ableton link. But I find it isn't always necessary. I can start a loop on one ipad and just press play on the other one with my own sense of timing and they won't noticeably drift for several minutes.

PNWO has about the same degree of accuracy as my akai tomcat, which goes out of sync after a bar or two unless you sync it. I guess I was just hoping things were different. Maybe one day they will be, but I shouldn't let that stop me from enjoying the module (which is still amazing) or making music. Rockin' Banana!
guestt
Hehe, yeah! Back in the day, before the gear revolution, when we spent a lot of time trying to sync two computers running cubase (what a royal pain in the ass that was!) we often got fed up of trying and resorted to fingers poised over the mouse and 1&2&3&4&in! We got very very good at it, and after a few false starts could often have one or two hour jam sessions without significantly losing sync. That took years of practice though wink
c0nsumer
Can any of you tell me how well PNW can work for ratcheting? I've been thinking of picking up a Doepfer A-160-5 for CV controlled ratcheting (so I can set up or disable ratcheting via CV), and it sounds like PNW can do this as well (via CV control of a multipler parameter).

Have any of you done this / can you tell me how well it works out?

Thanks!
ugokcen
Look, I know nothing about the inner workings of PNW, but its clock sounds rock solid when it's on its own, and also when synced to a DAW with an audio pulse. My guess is this is just confusion about the what is on the display.

ALM: make sure that a 1 bar loop at 120 bpm is exactly 8 seconds long and all your troubles will vanish!
c0nsumer
ugokcen wrote:
ALM: make sure that a 1 bar loop at 120 bpm is exactly 8 seconds long and all your troubles will vanish!


...but time is relative and 8 seconds in one place is not the same as 8 seconds in another. wink
guestt
I was under the impression that the original poster of this problem had recorded loops that should have been 120bpm but were not and the display issue is separate, very common in many devices and not related.
Zymos
Am I mistaken, or is someone claiming PNWO is defective because it doesn't stay in sync when they don't sync it??
guestt
Zymos wrote:
Am I mistaken, or is someone claiming PNWO is defective because it doesn't stay in sync when they don't sync it??


I hope not - that would be very silly indeed!

It's not a complaint about what bpm is displayed either!

The complaint is, as I understand it, that 120bpm is not actually 120bpm and is quite a way out - which I think is a valid concern. There's no reason for this not to be accurate.
Zymos
Nope, different poster-

"I honestly thought that was what I was paying for when I bought PNWO, especially when I read phrases like "Improvements have been made to overall clock stability," and "BPM based clock with tempo rates 10-300BPM." "

As ALM said, if you want things to be in sync, then sync them.
ALM
Baddcr wrote:
Zymos wrote:
Am I mistaken, or is someone claiming PNWO is defective because it doesn't stay in sync when they don't sync it??


I hope not - that would be very silly indeed!


Nope this is how Im reading it too. Its very silly - it ruining this thread.

Baddcr wrote:

The complaint is, as I understand it, that 120bpm is not actually 120bpm and is quite a way out - which I think is a valid concern. There's no reason for this not to be accurate.


People have reported a 0.1BPM difference to an external unsynced clock once calibrated to it. Thats just under 7ms of difference on an 4 bar 120bpm loop - trivially fixed when importing into a DAW.

I repeat (please pay attention where I say looking to improve in a future update..) :-

ALM wrote:
OK I will investigate and try for better/more control over the calibration in a future update.

In the meantime if you need a very specific BPM and even after calibrating Pam you still don't get what you want either;

- Slave Pam to external clock which gives you what you want. Ignore any subtle difference in displayed BPMs. If it sounds in sync it is.

- Learn/use your DAW's tools to make minor tempo adjustments to, or sync to, audio imports.

- Just don't worry about, instead just make music & enjoy hyper


As for why there is not an Atomic clock in Pamela and it not being BPM accurate to an infinite amount of decimal places its purely because I never paid it that much attention believing it good enough and it more important to keep stable and physically sync very well to an external clocks (which is where alot of effort was put) if you wanted to match something. Also I had in mind that its trivial to fix BPMs in DAWs nowadays and believed that no one surely seriously syncs things by effectively not syncing them!

Can we please leave it at that.
adderbrew
Don't worry about the nitpickers, I just got mine last week, and I swear, this is the best damn thing to come to my rack! I need the expander badly razz
guestt
Right, thanks for the clarification ALM

I understood the difference to be much greater - if that's all it is it's within acceptable limits and I am now quite perplexed about what this whole thing has been about!

seriously, i just don't get it
MoogCloud
ALM wrote:
Baddcr wrote:
Zymos wrote:
Am I mistaken, or is someone claiming PNWO is defective because it doesn't stay in sync when they don't sync it??


I hope not - that would be very silly indeed!


Nope this is how Im reading it too. Its very silly - it ruining this thread.

Baddcr wrote:

The complaint is, as I understand it, that 120bpm is not actually 120bpm and is quite a way out - which I think is a valid concern. There's no reason for this not to be accurate.


People have reported a 0.1BPM difference to an external unsynced clock once calibrated to it. Thats just under 7ms of difference on an 4 bar 120bpm loop - trivially fixed when importing into a DAW.

I repeat (please pay attention where I say looking to improve in a future update..) :-

ALM wrote:
OK I will investigate and try for better/more control over the calibration in a future update.

In the meantime if you need a very specific BPM and even after calibrating Pam you still don't get what you want either;

- Slave Pam to external clock which gives you what you want. Ignore any subtle difference in displayed BPMs. If it sounds in sync it is.

- Learn/use your DAW's tools to make minor tempo adjustments to, or sync to, audio imports.

- Just don't worry about, instead just make music & enjoy hyper


As for why there is not an Atomic clock in Pamela and it not being BPM accurate to an infinite amount of decimal places its purely because I never paid it that much attention believing it good enough and it more important to keep stable and physically sync very well to an external clocks (which is where alot of effort was put) if you wanted to match something. Also I had in mind that its trivial to fix BPMs in DAWs nowadays and believed that no one surely seriously syncs things by effectively not syncing them!

Can we please leave it at that.


==============================================

Pam's New Workout is an awesome module. The ease of use, rapidity with which I can modify 8 outputs, the clarity of the screen, cause me to judge this module as one which Exceeded My Expectations. It's one of the few modules that hit that subjective mark. Excellent work!

It's peanut butter jelly time! applause thumbs up
Outtatune
Just to add to the "I love Pam's" theme. In my rig it replaced my Doepfer A-160-2 and A-160-5 combo, in the same HP, and with a tonne of additional features that are easy to access. I went from unboxing to using it in a live performance within 48 hours!

I'm syncing my Pam's with my Octatrack, Yarns, and Erica MIDI Trigg and the whole setup is rock solid.
skeller047
Two points:

1) Pamela's New Workout is everything and more than I expected, and it is the heartbeat of my rack now.

2) To those that complain about sync issues, and 120 BPM on device A is not the same as 120 BPM on device B, I have only this to say.

Go listen to some great "in the pocket" dance music - for example, James Brown's "I Feel Good". If you can get any device to sync with that, without some beat detector feeding a sync device, then I want to know what that is.
A great, danceable, booty-moving beat may not be accurate to the microsecond (or even millisecond), but who cares?

In other words, get a life, stop complaining about non-existent issues, learn how to sync things properly and, most importantly, make some good music!
dudeman
just fired mine up and gotta say WOW i'm super impressed!!!!! seems a really nice mix of intuitive and simple but also deep

big ups!!!
insect
just want to add my 2 sync cents here:

I can report that Pams New Workout is (rock) solid sync. Much much better then the old. If you have sync probs, it´s maybe your source doesn´t deliver a rock solid stable clock?

I sync Pam via Din Sync. For example Pam reports "unstable clock" in the display from the Elektron Analog Four (bpm swithching from 127 to 128), but clocking from Analog Rytm (which is clocked from Logic Pro X via ES Usamo) is stable and it doen´t drift! we're not worthy we're not worthy we're not worthy we're not worthy we're not worthy Sometimes it´s maybe 10 or 20ms late when pressing start - but then just press start again and it will start in phase. Btw. when Analog Rytm and Logic says 120bpm also my Pam says 120bpm.

Euclidean rhytm and propability over lfos is pretty much SlayerBadger! SlayerBadger! SlayerBadger!

@alm is there a way to change the base of the output clock? like a pre - divider / mutliplier? The base (x1) is bpm based, so it´s 1/4. But how can I send clocks like 3/16 or 7/16 or 11/16?

Ratcheting in Euclidean Rhytm would be a nice feature too smile
ALM
insect wrote:

@alm is there a way to change the base of the output clock? like a pre - divider / mutliplier? The base (x1) is bpm based, so it´s 1/4. But how can I send clocks like 3/16 or 7/16 or 11/16?


Not sure I 100% follow but does the loop option do what you want ? That will essentially reset the output what ever the mult/div on a x1 beat.

insect wrote:
Ratcheting in Euclidean Rhytm would be a nice feature too smile


So if you increased the multiplier on an euclidean rhythm rather than get spread over a smaller amount of time (i.e getting faster) - it would cover the same amount of time but become more dense ? I.e the steps would decrease but the the triggers increase. Make sense ? That could be pretty nice.
insect
okay not checked the loop function yet ... will have another workout tonight. But basicly what I mean is to have for example a "devide by 3" "devide by 5" "devide by 7" .... but not based on full beats / bpm, based on 1/8 or 1/16.
So at the moment "divide by 3" means 3 beats - based on 1/16 it would be every 3rd 1/16

For the Euclidean Ratcheting ... I have Multiplier set to x4 for 1/16. Lets say I set Euclidean to 3 out of 31 ... so a trig is not fired very often. But would be nice to have an option to say, when it fires of, then please another 2, 3, 4 shots

a simple example would be a double hit of a snare drum ... so one hit on the beat and another 1/16 behind.

000X0000000X000 without ratcheting
000XX000000XX00 with ratcheting
ALM
insect wrote:
okay not checked the loop function yet ... will have another workout tonight. But basicly what I mean is to have for example a "devide by 3" "devide by 5" "devide by 7" .... but not based on full beats / bpm, based on 1/8 or 1/16.
So at the moment "divide by 3" means 3 beats - based on 1/16 it would be every 3rd 1/16


OK think I follow - maybe use a channel to 'multiply/divide' another by voltage control of the level (turn it off completely).

You also may be able to do something similar to this to get the racheting on euclidean to work how you want.
c0nsumer
Just picked up a Pamela's New Workout from Detroit Modular; can't wait to get home...
cryptogreen
ALM wrote:
Baddcr wrote:
Zymos wrote:
Am I mistaken, or is someone claiming PNWO is defective because it doesn't stay in sync when they don't sync it??


I hope not - that would be very silly indeed!


Nope this is how Im reading it too. Its very silly - it ruining this thread.


Sorry, wasn't trying to lower the tone of the discussion. I just want 120 bpm to be 120.00 bpm. Didn't realize it would upset anyone or draw derision to myself. seriously, i just don't get it

PNWO is awesome, I'm happy it exists and I really look forward to being able to calibrate it so it's display will be as accurate as other digital clocks I have outside eurorack. thumbs up

Physically syncing works great, so until the update comes I'll just use the es-8 to do that. Much love!
nciviero
Put this in my system last night and I'm absolutely blown away by the way it unlocks the functionality of the rest of my system. Considering how much depth is packed into such minimal controls it is incredibly intuitive to use. I thought learning the menuing might be a bit laborious, but right off the jump I'm flying with this thing.

Kudos to ALM, particularly for incorporating offset and attenuation into every parameter input and every output.
chockfullofthat
For some reason my DAW works horribly when receiving an external clock so my plan to make Pam's my main clock with the midi OUT expander has gone out the window. Can anyone recommend a method other than audio pulses to sync Pam to my DAW? uMidi?
cheeseandbiscuits
Wow just brought Pams New Workout home, replaced my old workout... which i loved, but......

This thing is SO GOOD!!! Amazing module, what a smash!!
I Sync my modular with Circadian Rhythms receiving Silent Way Sync from Ableton... New Pams is DEAD ON and it's rock solid!! Prayers have been answered!

Couple things tho, when i sync it (although it's dead on so I'm not complaining, my DAW says 114bpm and pams says 113). Anyone else get this?

Also is there any way to calibrate the slop? It's an awesome feature, but even at 1% it seems a little much.. It's sort of derailing a groove rather than humanizing it, which is cool sometimes but would love a finer control. It came with firmware 192

Congrats ALM u really improved this thing above and beyond!!
cryptogreen
cheeseandbiscuits wrote:

Couple things tho, when i sync it (although it's dead on so I'm not complaining, my DAW says 114bpm and pams says 113). Anyone else get this?


No, mine does this too. The BPM is more of a general unit of measure (120 on pam is actally 120.3 bpm for me), ALM is working on calibration improvements.

As long as you know that, it's easy to work around it.
c0nsumer
So... Got home, put in the rack... After reading the manual I was a bit confused by some things. So, I started playing around... Darn am I impressed. While I didn't get into any of the more advanced waveform stuff, it was really simple to start rhythmically modulating both drums and filters.

Really liking this, nice work. grin

Oh, and in my quick playing of 4 PPQN syncing with a BeatStep Pro, the BPM displayed on both matched. So... <shrug>

I particularly liked how the PPQN screen showed a small BPM counter at the top, which made setting up the right PPQN super simple. Great attention to detail there!
MossGarden
My pams is out for delivery today, can't wait to get out of work and clock the shit out of things! Dead Banana
ALM
cheeseandbiscuits wrote:

Couple things tho, when i sync it (although it's dead on so I'm not complaining, my DAW says 114bpm and pams says 113). Anyone else get this?


You can calibrate the internal clock to closer match an external one. Power up Pam with the program knob held down and then adjust the 'Calib' value probably just by +/-1. This wont affect the actual syncing just the representation of BPM.

cheeseandbiscuits wrote:

Also is there any way to calibrate the slop? It's an awesome feature, but even at 1% it seems a little much.. It's sort of derailing a groove rather than humanizing it, which is cool sometimes but would love a finer control. It came with firmware 192


Still working on finding a good balance here !
3D_PIPES
Newb here. I was going to pick up a Xaoc Batumi Quad LFO in the future. Would the new PWO be a comparable product since it appears to provide 8 LFOs in addition to clock division?
chockfullofthat
Yes it's a comparable product, but it blows it out of the water imho. There is so much functionality in this product.
GorillaMuseum
Mine arrives next week!
erstlaub
3D_PIPES wrote:
Newb here. I was going to pick up a Xaoc Batumi Quad LFO in the future. Would the new PWO be a comparable product since it appears to provide 8 LFOs in addition to clock division?


They both have their massive merits, if I someone forced me at gunpoint to take one of them out of my case I'd probably stick with Pam's but i'd miss Batumi like hell.

The main differences are that Batumi has a very immediate and knob (well slider) based interface where sometimes you just want to grab and manually wiggle in your frequency. It also outputs bipolar voltages in the region of +/-5-7v whereas Pam's can only deliver 0 to +5v and finally, sometimes you want to have 4 completely unrelated, freerunning, non sync'd LFOs rattling around which is sort of possible but quite a bit more work to *dial in* with Pam's

Pam's is an absolute beast though, it has an unbelievable feature set packed into just 8hp, my advice would be the standard Muffs 'get both' answer but quite probably get Pam's first.
Zymos
I tend to see the LFOs as more of a bonus feature. Not that they aren't totally useful and usable.

The envelopes are a genius addition though, since with the Euclidean features you are already halfway to a full drum machine- just add VCAs and some noise sources. I usually use 2-3 outputs as triggers for drum modules, 1-2 as envelopes and the rest for clocks out to other things or LFOs.

That old TV show was wrong- 8 is NOT enough!
c0nsumer
Hell, even just pointing PNW at a Delptronics LDB2x+2e with a weird pulse division and a sine made for some real fun sounds.
cryptogreen
Zymos wrote:
I tend to see the LFOs as more of a bonus feature. Not that they aren't totally useful and usable.

The envelopes are a genius addition though, since with the Euclidean features you are already halfway to a full drum machine- just add VCAs and some noise sources. I usually use 2-3 outputs as triggers for drum modules, 1-2 as envelopes and the rest for clocks out to other things or LFOs.

That old TV show was wrong- 8 is NOT enough!


My immediate thought after making a couple of drum patterns with PNWO, was I wanted a full blown sequencer from ALM. The interface is just amazing, it makes me want more of it.
dooj88
dooj88 wrote:
dooj88 wrote:
i noticed cracking when using the sin and triangle shapes to open/close a VCA - specifically veils. but when i A/B it with a similar shaped signal from maths, there is no crackling. i shot a video, but the maths signal was too hot and distorted the recording.. (noob boob had the attenuator too high and didn't check recording afterwords..) anyway, i'll shoot another video this evening. but here's a decent enough example of the behavior:
https://youtu.be/3uCM_RPaMy0
(i normalized the audio, so if you have to crank the volume, i made sure there are no peaks that are super loud..)

things i've tried:
-changing level of signal, still there but attenuated
-different shapes still have same behvior (envelope, sin, tri)
-trying different output channels/jacks there is no change
-had a high power load on my PSU before, but i got another yesterday, and after reducing the whole load by half that the circuit pam was on, the crackling persisted.

i noticed this when i first got it, and just decided to just not use it for VCA modulation, but now i'd like to know what's going on. another note, i haven't updated the firmware since i received it at the end of march.

any other things to try? anyone else hearing this?


Bumping this since its in the middle of the sync discussion


rebumping so it doesn't get buried again sad banana
MossGarden
Been wiggling with my new pams! It's peanut butter jelly time!

It's utterly magical! I can't believe its only 8hp yet does so much so well. Utterly gobsmacked t how fast you can make interesting things happen. I'd say this is an essential module! Dead Banana
3D_PIPES
chockfullofthat wrote:
Yes it's a comparable product, but it blows it out of the water imho. There is so much functionality in this product.


erstlaub wrote:
3D_PIPES wrote:
Newb here. I was going to pick up a Xaoc Batumi Quad LFO in the future. Would the new PWO be a comparable product since it appears to provide 8 LFOs in addition to clock division?


They both have their massive merits, if I someone forced me at gunpoint to take one of them out of my case I'd probably stick with Pam's but i'd miss Batumi like hell.

The main differences are that Batumi has a very immediate and knob (well slider) based interface where sometimes you just want to grab and manually wiggle in your frequency. It also outputs bipolar voltages in the region of +/-5-7v whereas Pam's can only deliver 0 to +5v and finally, sometimes you want to have 4 completely unrelated, freerunning, non sync'd LFOs rattling around which is sort of possible but quite a bit more work to *dial in* with Pam's

Pam's is an absolute beast though, it has an unbelievable feature set packed into just 8hp, my advice would be the standard Muffs 'get both' answer but quite probably get Pam's first.


Thanks for the responses! Truth is I will likely purchase both at some point as I do like the feature set of both modules. I was also planning on picking up a MN Tempi for clock/division in addition to the Batumi so it is looking like the PWO might be worth checking out first.
ugokcen
I also have both the Batumi and the PNW and they do make a fantastic combo. Like the other poster said the immediacy of Batumi in free-running mode and the self-patching ability is where it really shines. Before I got Pam's I wasn't really taking advantage of that because Batumi had to be in "divide" mode to generate synced lfos and clocks (note that you can't mix-and-match modes on the Batumi).

Tempi doesn't have lfos so that's why I went for the PNW instead. But Tempi has mute buttons which would be useful for live performance/jamming so the choice depends on how you plan to use it.
aroom
ugokcen wrote:
But Tempi has mute buttons which would be useful for live performance/jamming so the choice depends on how you plan to use it.



from Pam's New manual :

Mute
Mutes and unmakes an output .
An output can still be edited whilst muted.
Note an output can have its mute state quickly toggled by clicking and holding the program knob and then clicking the start/stop button.


did you try this shortcut ? is it handy ?
c0nsumer
Can someone tell me how to assign a CV input to selecting the multiplier of a given output? I can't figure this out, and I'm looking for function similar to the CV input of the Doepfer A-160-5.

Thank you!
MossGarden


New Pams being clocked by BSP, sending ALL modulations to other modules. Its also generating a looped melody a la Turing Machine which is being sent to Braids (internally quantized, in ZLPF mode). Arpeggiated voice is Rings and at times, Wavefolded Warps which I blend in occasionally Warps is going into streams channel 1 in VCFA mode. Braids is also being sent to Clouds for random glitchy+ambience. Kick is from Peaks, snare is from Mother 32, hihats are just white noise from Kinks going into Streams Channel 2 in LPG mode. Bass sound is Tides, an envelope from peaks opening up it's built in vca. I think that's it appart from a touch of verb from my mixer.

I utterly love pams

screaming goo yo
c0nsumer
c0nsumer wrote:
Can someone tell me how to assign a CV input to selecting the multiplier of a given output? I can't figure this out, and I'm looking for function similar to the CV input of the Doepfer A-160-5.

Thank you!


Bah. I was overthinking it. Didn't realize I just had to set the multiplier to CV1 or CV2. I was looking too deep in the menu under the waveform settings.

Yay!
rikrak
c0nsumer wrote:
c0nsumer wrote:
Can someone tell me how to assign a CV input to selecting the multiplier of a given output? I can't figure this out, and I'm looking for function similar to the CV input of the Doepfer A-160-5.

Thank you!


Bah. I was overthinking it. Didn't realize I just had to set the multiplier to CV1 or CV2. I was looking too deep in the menu under the waveform settings.

Yay!


Note that you can long-press on the *highlighted* "CV1" or "CV2" to adjust the offset and attenuation specifically for the parameter being modified by CV. This way you can fine tune the desired effect. cool
c0nsumer
rikrak wrote:
Note that you can long-press on the *highlighted* "CV1" or "CV2" to adjust the offset and attenuation specifically for the parameter being modified by CV. This way you can fine tune the desired effect. cool


That explains the only menu I was getting to before... I thought that was all of the CV parameters and in there I should be able to set the thing for CV to control there. Nope, I was thinking of it backwards. grin

My hope here is to use a combination of Velocity out (from the BeatStep Pro) and some logic to control ratcheting (with rests).
monads
ALM wrote:
I've uploaded a new beta '189' firmware for folks to try. It should be pretty solid...

The downside of this update is that this update exposes a silly bug in the PEXP1 (not PEXP2!) expander module. This bug puts the external gates very slightly out of sync - though external MIDI and DIN syncing should be tighter. The fix unfortunately requires that the PEXP-1 be sent back here to ALM for updating. If this affects you please contact help <at> busycircuits.com and we will get it sorted for you asap. Apologies for any troubles here.


So I take the above is still true for 192 firmware users? I've been thinking of ordering a new PEXP1 but not sure the version I'll receive (restock) has the fix and seems a waste to order New and send for service. How will I know the PEXP1 is the latest version with fixed bug???
ALM
monads wrote:

So I take the above is still true for 192 firmware users? I've been thinking of ordering a new PEXP1 but not sure the version I'll receive (restock) has the fix and seems a waste to order New and send for service. How will I know the PEXP1 is the latest version with fixed bug???


Existing stock should have been replaced. Advise you email your dealer or help <at> busycircuits to double check if concerned.
AThousandDetails
Loving this new version of Pamela grin

My experience so far is that it sounds tight smile I'm clocking it with my ERM Multiclock+ and it's flawless. The BPM counter on Pamela say 126 while i am at 127, but since it's in sync who cares right?

This is a solid module grin totally recommend it!
brandonlogic
ALM wrote:
MATSmile wrote:
Any word on logic channel combos? sad banana


How exactly would it work ? Wouldn't it be better handled by a dedicated logic module ?

The 'virtual patching' idea would maybe cover it but its gonna take a pretty monumental effort to get the to fit & work well. There are literally only bytes of program flash space left..


I'm thinking about getting this for logic fictions to sit right next to Pam. Seems like it would be a lot of fun and only 4hp and cheap https://www.modulargrid.net/e/ladik-b-020-bool3-logic-module

c0nsumer
Check out the Doepfer A-166 as well. It's 8HP but a bit more than twice the functionality because of the input jacks being normalized to the one above.
brandonlogic
c0nsumer wrote:
Check out the Doepfer A-166 as well. It's 8HP but a bit more than twice the functionality because of the input jacks being normalized to the one above.

thanks for pointing that one out, i think im gunna snag one!
c0nsumer
brandonlogic wrote:
c0nsumer wrote:
Check out the Doepfer A-166 as well. It's 8HP but a bit more than twice the functionality because of the input jacks being normalized to the one above.

thanks for pointing that one out, i think im gunna snag one!


You're welcome! I grabbed one at the same time as PNW. I'm using it in conjunction with a BeatStep Pro to do ratcheting with rests.

Clock and run out from the BSP into PNW.

Velocity output from BSP goes to PNW CV in which controls the multiplier of an out. That out goes to one logic input, and the BSP's gate out goes to another.

The I then send the AND output to the envelope generator (which in turn opens the VCA -- traditional east coast style stuff).

The result is that I can use Velocity to control the steps of ratcheting, and rests work fine. Just have to be sure that the gate length on the ratcheting steps are as long as the ratchet needs to trigger, else one operator into the AND will go low and nothing will come out. To start I just set all the gates to 99% length and play from there.

I need to constrain the inputted CV so it's easier to scale between, say, 1 and 4 pulses per step, but that's just something I haven't done yet... Should be pretty easy to do either in PNW itself, or using an attenuating offset (O/A/X2).
reodjectz
c0nsumer wrote:
rikrak wrote:
Note that you can long-press on the *highlighted* "CV1" or "CV2" to adjust the offset and attenuation specifically for the parameter being modified by CV. This way you can fine tune the desired effect. cool


That explains the only menu I was getting to before... I thought that was all of the CV parameters and in there I should be able to set the thing for CV to control there. Nope, I was thinking of it backwards. grin

My hope here is to use a combination of Velocity out (from the BeatStep Pro) and some logic to control ratcheting (with rests).


I'm doing something similar and in addition to the offset and attenuation it would be nice to pick which multiplies it sweeps through (only powers of 2, triplets, all).

What I would also really like would be 2 decimal places in the BPM, and some way to do fine BPM adjustment. Right now a slow ramp between tempos is too choppy.

-selfish
c0nsumer
reodjectz wrote:
I'm doing something similar and in addition to the offset and attenuation it would be nice to pick which multiplies it sweeps through (only powers of 2, triplets, all).


I would definitely like it if the PNW displayed what is being set from CV, but I can imagine that getting really fiddly since CV can change faster than the display can update, etc. It was quite a pain to figure out what's, say, /3 vs /2.6, though...

reodjectz wrote:
What I would also really like would be 2 decimal places in the BPM, and some way to do fine BPM adjustment. Right now a slow ramp between tempos is too choppy.


Can you clock your PNW from the BSP? It allows decimal place tempo adjustments...
ALM
c0nsumer wrote:

Can you clock your PNW from the BSP? It allows decimal place tempo adjustments...


Or even just a Square wave LFO with fine control over frequency.
reodjectz
ALM wrote:
c0nsumer wrote:

Can you clock your PNW from the BSP? It allows decimal place tempo adjustments...


Or even just a Square wave LFO with fine control over frequency.


Thanks for the ideas.
funqpatrol
ALM wrote:
funqpatrol wrote:
I've asked before but will there be a chance to get CV over preset loading? Thanks! smile


How would you use it ? What sort of thing would you see yourself doing with it ?



Well instant loading of a whole set of clocks and their parameters by CV would mean pretty incredible sequences, am I the only one to see the potential of this?
Shwaj
funqpatrol wrote:
ALM wrote:
funqpatrol wrote:
I've asked before but will there be a chance to get CV over preset loading? Thanks! smile


How would you use it ? What sort of thing would you see yourself doing with it ?



Well instant loading of a whole set of clocks and their parameters by CV would mean pretty incredible sequences, am I the only one to see the potential of this?


Since Rossum allows something similar in Control Forge, I'd have to say no, you're not the only one.
ALM
funqpatrol wrote:
ALM wrote:
funqpatrol wrote:
I've asked before but will there be a chance to get CV over preset loading? Thanks! smile


How would you use it ? What sort of thing would you see yourself doing with it ?



Well instant loading of a whole set of clocks and their parameters by CV would mean pretty incredible sequences, am I the only one to see the potential of this?


Sorry I meant more from a practical perspective - in terms of how it would actually work patch wise + set up UI wise. Also if you had any specific use cases ?

I have some ideas by means reassigning the run input to trigger a load - and that would be either the next numbered bank or maybe selection dependent on a CV input value. Im also thinking about it only loading entire banks rather than being per output - I think this would just end up to fiddly/convoluted UI wise to be useful.
funqpatrol
ALM wrote:
funqpatrol wrote:
ALM wrote:
funqpatrol wrote:
I've asked before but will there be a chance to get CV over preset loading? Thanks! smile


How would you use it ? What sort of thing would you see yourself doing with it ?



Well instant loading of a whole set of clocks and their parameters by CV would mean pretty incredible sequences, am I the only one to see the potential of this?


Sorry I meant more from a practical perspective - in terms of how it would actually work patch wise + set up UI wise. Also if you had any specific use cases ?

I have some ideas by means reassigning the run input to trigger a load - and that would be either the next numbered bank or maybe selection dependent on a CV input value. Im also thinking about it only loading entire banks rather than being per output - I think this would just end up to fiddly/convoluted UI wise to be useful.



Yes loading an entire bank of clocks on a CV input value was pretty much my suggestion, not per output smile I think the Tempi has this feature but 100% sure. Patch wise I have drum sequences in mind basically I see myself having to fiddle too much with mult/div if I want to try out different settings, being able to load a whole different set at once would be awesome imo. but just the idea of sequencing different sets of clock imo is super powerful, I hope you can implement that!
rikrak
+1 for this. It would make the saved bank slots much more useful for me. How fast would the bank load?

So far as UI goes, I think you'd need a way to limit the range of the banks selectable by the CV input. I may only need, say, 8 banks to be accessible and it would be tricky to dial a bank in if all (100+?) of them were accessible over the 5v. Just a thought.
resynthesize
c0nsumer wrote:


I would definitely like it if the PNW displayed what is being set from CV, but I can imagine that getting really fiddly since CV can change faster than the display can update, etc. It was quite a pain to figure out what's, say, /3 vs /2.6, though...



+1, I would really like this as well. I was playing with changing the multiplier via CV yesterday and it's hard to figure out which rate is set. Seeing the current value on the display would be killer.

While I'm here, I'll also reiterate my desire for a shorter "long presses" to get into the submenus Guinness ftw!
ALM
resynthesize wrote:

+1, I would really like this as well. I was playing with changing the multiplier via CV yesterday and it's hard to figure out which rate is set. Seeing the current value on the display would be killer.


The old Pam kind of did this and people would think the trigger was actually broken as the knob wouldn't change value any more (as under CV control).

I think I could make it more obvious on new Pam but its really not as helpful as you'd think, especially at speed - less so than just using your ears smile
Zymos
One thing that kind of bugs me (and that I realize may just be a limitation of the interface) is that you can't tell what bank you are in. Cool that it starts up on the last used one, but I can never remember which that one was.

Though having a preset system at all is a huge plus- a way to sequence them would be a great addition.
As for specific use cases, for me it would mostly be different drum patterns, since that has turned out to be my main use for the module.
ALM
Zymos wrote:
One thing that kind of bugs me (and that I realize may just be a limitation of the interface) is that you can't tell what bank you are in.


Note your not actually 'in' any saved bank - your always in the 'workbank' and when you save/load you actually copy settings to/from a 'savebank'. Changes in a loaded bank wont get reflected back unless you explicitly save. But agree it would be nice to know where you'd loaded from - perhaps 'Load/save' option would show this by default (and if it had been edited).
Zymos
ALM wrote:
perhaps 'Load/save' option would show this by default (and if it had been edited).


That would be really helpful.
Fleuw
So if i may ask what is the best way to sync up the rest of my Midi gear if i would get PNW?
Is it to have the PNW as master via expander or sync it via some Midi -> clock solution?
Looks like a really nice module with loads of functions i could use in my eurorack.
guestt
Thanks to all the posts here and diligent resolution of questions, I've got one on the way - thank you everyone This is fun!
uebl
Maybe I missed it in the v0.2 manual and I didn't find an answer to this when I looked at the last 5 pages of this thread or so, so excuse me if this has already been answered: is there a way to get a MIDI clock out (to use with a 3.5mm to MIDI cable) from PNW without using one of the expanders? Many thanks!
fourhexagons
I'm trying to setup CV control over Euclidean Step & Fill (Trig), but I'm running into some funny behavior.

My first attempt is to set ETrig to 1 and use CV to modulate EStep. What happens, though is that ETrig defaults to 0 when I assign EStep to a CV source.

Is this a bug, or am I missing something? Ideally, I would want to be able to set ETrig to a value and have it retain that value when EStep is assigned to CV. And then, say I set ETrig to 5 and then lowered EStep via CV to 3, then it would just use the highest value possible for ETrig, in this case, 3.
ALM
uebl wrote:
Maybe I missed it in the v0.2 manual and I didn't find an answer to this when I looked at the last 5 pages of this thread or so, so excuse me if this has already been answered: is there a way to get a MIDI clock out (to use with a 3.5mm to MIDI cable) from PNW without using one of the expanders? Many thanks!


No, you need an expander - The 2HP Pexp2 if you want 3.5mm MIDI socket.
ALM
fourhexagons wrote:
I'm trying to setup CV control over Euclidean Step & Fill (Trig), but I'm running into some funny behavior.

My first attempt is to set ETrig to 1 and use CV to modulate EStep. What happens, though is that ETrig defaults to 0 when I assign EStep to a CV source.

Is this a bug, or am I missing something? Ideally, I would want to be able to set ETrig to a value and have it retain that value when EStep is assigned to CV. And then, say I set ETrig to 5 and then lowered EStep via CV to 3, then it would just use the highest value possible for ETrig, in this case, 3.


You cant have more triggers than steps (and thus trigger numbers get clipped). Can you be more careful with you CV source so it does not pull the number of steps down to 0 (assume this is what is happening) or alternatively also control Etrig with the same cv source but different attenuation/offset ?
Daisuk
Can anyone with an es-3 confirm whether or not the new Pam slaves/syncs well to it? smile

Edit - having gone through the entire thread now it seems like it should sync perfectly. Nice. Mr. Green
uebl
ALM wrote:
uebl wrote:
Maybe I missed it in the v0.2 manual and I didn't find an answer to this when I looked at the last 5 pages of this thread or so, so excuse me if this has already been answered: is there a way to get a MIDI clock out (to use with a 3.5mm to MIDI cable) from PNW without using one of the expanders? Many thanks!


No, you need an expander - The 2HP Pexp2 if you want 3.5mm MIDI socket.


Thanks for getting back to me so quickly. And this feature won't be implemented in a future firmware update?
fourhexagons
ALM wrote:
fourhexagons wrote:
I'm trying to setup CV control over Euclidean Step & Fill (Trig), but I'm running into some funny behavior.

My first attempt is to set ETrig to 1 and use CV to modulate EStep. What happens, though is that ETrig defaults to 0 when I assign EStep to a CV source.

Is this a bug, or am I missing something? Ideally, I would want to be able to set ETrig to a value and have it retain that value when EStep is assigned to CV. And then, say I set ETrig to 5 and then lowered EStep via CV to 3, then it would just use the highest value possible for ETrig, in this case, 3.


You cant have more triggers than steps (and thus trigger numbers get clipped). Can you be more careful with you CV source so it does not pull the number of steps down to 0 (assume this is what is happening) or alternatively also control Etrig with the same cv source but different attenuation/offset ?

Thanks for the quick response. So it was pulling it down to 0 and thus breaking the logic. Okay, yeah that makes sense. I was using a fixed channel from Voltage Block (plan ol' 0-5v offset). I don't have an additional scale/offset available in this use case, but at least I understand what's going on.

I've read this entire thread, so I'm aware how many people request new additions to what is already a super-comprehensive (and brand new) module, but I'm gonna do it anyway razz

Is there any chance you'd consider adding attenuation/offset to the CV inputs from within Pam's? I could imagine that a good place to situate it would be in the global menu after Run and before Save. As in CV1at|00, CV1of|00, CV2at|00, CV2of|00.
ALM
uebl wrote:


Thanks for getting back to me so quickly. And this feature won't be implemented in a future firmware update?


yep right, it wont happen - it needs the physical hardware in the expander to work.
ALM
fourhexagons wrote:


I've read this entire thread, so I'm aware how many people request new additions to what is already a super-comprehensive (and brand new) module, but I'm gonna do it anyway razz

Is there any chance you'd consider adding attenuation/offset to the CV inputs from within Pam's? I could imagine that a good place to situate it would be in the global menu after Run and before Save. As in CV1at|00, CV1of|00, CV2at|00, CV2of|00.


Maybe read the entire manual too.. cool
fourhexagons
ALM wrote:
fourhexagons wrote:


I've read this entire thread, so I'm aware how many people request new additions to what is already a super-comprehensive (and brand new) module, but I'm gonna do it anyway razz

Is there any chance you'd consider adding attenuation/offset to the CV inputs from within Pam's? I could imagine that a good place to situate it would be in the global menu after Run and before Save. As in CV1at|00, CV1of|00, CV2at|00, CV2of|00.


Maybe read the entire manual too.. cool

Nice one. d'oh!

I actually just discovered this while working hands on with Pam's. I had missed your reply until now and somehow had missed that on page 14 of the manual. Your implementation of a per-parameter atten/offset is so much more flexible!
fourhexagons
I have Ch 4 on Pamela's NEW Workout outputting a 12:7 Euclidean rhythm at x4. The classic Ghana Bell Pattern. When I adjust ERot via the encoder, I can hear the rotation of the rhythm, however, when I adjust it via CV, nothing happens.

I'm using a Maths Ch3 for the +/-10v offset and have the internal attenuation @ +100% and internal offset @ 0%. When I visually monitor the incoming CV value, I can see the value move from nothing to full as I sweep the Maths offset throughout its range, but again, it's not affecting the actual rotation of the pattern.

Again, bug or user error?

Also, I have another feature question. This time, I read through the manual to be sure it's not already present. oops

Is it even possible within the firmware to add a 2* multiplier and negative offset to incoming CV? That is (provided my understanding is correct) one could then use a 0-5v CV and convert it to +/-10v for use in CV input 2. I see that attenuation is bipolar, but offset is not, and of course, there's no gain multiplier.
oinkbanana
fourhexagons wrote:
Is it even possible within the firmware to add a 2* multiplier and negative offset to incoming CV? That is (provided my understanding is correct) one could then use a 0-5v CV and convert it to +/-10v for use in CV input 2. I see that attenuation is bipolar, but offset is not, and of course, there's no gain multiplier.

I think 0-5v is a limitation of the output.
fourhexagons
oinkbanana wrote:
fourhexagons wrote:
Is it even possible within the firmware to add a 2* multiplier and negative offset to incoming CV? That is (provided my understanding is correct) one could then use a 0-5v CV and convert it to +/-10v for use in CV input 2. I see that attenuation is bipolar, but offset is not, and of course, there's no gain multiplier.

I think 0-5v is a limitation of the output.

Thanks, oinkbanana. What I'm referring to, though, is to be able to utilize the +/-10v CV input (CV2) as if it were a 0-5v CV input. The primary CV source in my case is the Voltage Block and it only outputs 0-5v, so when I use it in the +/-10v CV input on Pamela, I can only span half of the range, either the bottom half or the top half (and I would love to span the entire thing without the need for an external utility).
ALM
Thanks fourhexagons - looking into whats up with cv control of euclidean rotation.

Note CV2 is +/-5v (not 10v) though I see the point your making. Maybe allowing the CV offset to go negative or attenuation to +/-200% would help here. I need to think on it.. Adding to the list smile
resynthesize
ALM wrote:
resynthesize wrote:

+1, I would really like this as well. I was playing with changing the multiplier via CV yesterday and it's hard to figure out which rate is set. Seeing the current value on the display would be killer.


The old Pam kind of did this and people would think the trigger was actually broken as the knob wouldn't change value any more (as under CV control).

I think I could make it more obvious on new Pam but its really not as helpful as you'd think, especially at speed - less so than just using your ears smile


Thanks for the response. I'm trying to create some voltage tables for the ER-101 to CV control the clock multipliers and still having trouble. Would it be possible to provide a table of voltages that correspond with each multiplier rate? I'm thinking of something like this:

Rate, Voltage
x1, 1.0v
x1.3, 1.5v
x1.5, 2.0v

etc. My goal is to be able to sequence the multiplier easily, and this would really help. Thanks again!
ALM
resynthesize wrote:


Thanks for the response. I'm trying to create some voltage tables for the ER-101 to CV control the clock multipliers and still having trouble. Would it be possible to provide a table of voltages that correspond with each multiplier rate?


Use the CV attenuation and offset to dial down the range and it should be simpler, not needing a table. i.e. For something roughly like x1 -> x8;

1. Assign desired output multiplier to CV1.
2. Offset the CV to approx 75% - this should be x1
3. Lower the CV attenuation to approx 15-20%
4. 0-5V into CV should now give multiplier increments in approx 1v steps.

Adjust steps 2 & 3 to taste.
resynthesize
ALM wrote:
resynthesize wrote:


Thanks for the response. I'm trying to create some voltage tables for the ER-101 to CV control the clock multipliers and still having trouble. Would it be possible to provide a table of voltages that correspond with each multiplier rate?


Use the CV attenuation and offset to dial down the range and it should be simpler, not needing a table. i.e. For something roughly like x1 -> x8;

1. Assign desired output multiplier to CV1.
2. Offset the CV to approx 75% - this should be x1
3. Lower the CV attenuation to approx 15-20%
4. 0-5V into CV should now give multiplier increments in approx 1v steps.

Adjust steps 2 & 3 to taste.


d'oh! I didn't know pam had offset and attenuation built in for CV control, that is AWESOME! I'll try this out but sounds like it should do the trick.
ALM
resynthesize wrote:


d'oh! I didn't know pam had offset and attenuation built in for CV control,


waah waah waah

Are folks not reading the manual or is it just not very clear/obvious within ?

I realise it is a little hidden on Pam itself.

waah waah waah
resynthesize
ALM wrote:
resynthesize wrote:


d'oh! I didn't know pam had offset and attenuation built in for CV control,


waah waah waah

Are folks not reading the manual or is it just not very clear/obvious within ?

I realise it is a little hidden on Pam itself.

waah waah waah


I did read the manual front to back when I first got it, but the part about CV attenuation must have slipped my mind. Although, once you mentioned it, I intuitively knew that it was probably a long press on the CV1 parameter to get into the offset submenu, so that's something.
z3r01
Edit: Bug was fixed in ver 191. Sorry for the confusion. - z3r01

Quick question about the 'slop' behaviour in Pamela's New Workout.

If I were to manually tweak the 'slop' parameter to any thing other than 0%, and shortly after, turn the 'slop' parameter back to 0%, that output would be out of sync (or out of phase) with the main clock. No other parameters were tweaked.

I understand that 'slop' introduces timing errors, but I am of the idea that if I were to set that parameter back to zero, that it would 'snap back' to the main BPM. I read through the whole manual but there wasn't anything written about this, so I am not sure if this was intended behaviour, or something else.

If it wasn't intended, could someone try it out on their Pam to see if you are experiencing this as well? Just a quick simple test, the settings were:

Output 1:
Wave: Gate
Div: /1


Output 2:
Wave: Gate
Div: /1

All other settings were set to default (both phases set to 0, no delay, no Euclidean, no loop etc.)

Now, tweak just output 1's 'slop' parameter, and once the sloppiness kicks in, set it back to 0%. Does the 'phase'/timing of output 1 differ from that of output 2?

Tried this with and without an external sync source, to make sure that it wasn't my external MIDI clock messing things up, and the same behaviour was observed. If I were to press stop, and start again, everything goes back to normal.

Thanks in advance!

thumbs up
ALM
z3r01, do you have the latest 192 firmware ? 'deslopping' should have been fixed in 191 - see http://busycircuits.com/firmware/alm017/ChangeLog.txt
z3r01
ALM wrote:
z3r01, do you have the latest 192 firmware ? 'deslopping' should have been fixed in 191 - see http://busycircuits.com/firmware/alm017/ChangeLog.txt


Thanks for the prompt reply, ALM.

Ah ok ok, I haven't updated it yet (still on 189). Glad to see that it has been fixed.

I did try searching for a changelog to see if it was a bug but couldn't seem to find a change log either on the website, or in one of the threads here, hence the confusion.

Apologies for the gaffe, and oversight. Thank you! thumbs up
erstlaub
ALM wrote:
resynthesize wrote:


d'oh! I didn't know pam had offset and attenuation built in for CV control,


waah waah waah

Are folks not reading the manual or is it just not very clear/obvious within ?

I realise it is a little hidden on Pam itself.

waah waah waah


It is totally clear but i think there's just that mental gap/space between reading the manual and practical application. I still find it mindblowing and amazing that there is essentially offset AND attenuation on both the inputs and the outputs. On many many modules we're spoiled with just one of those on one end so to have both on both I think makes it somehow easier to pass over?
guestt
ALM wrote:
resynthesize wrote:


d'oh! I didn't know pam had offset and attenuation built in for CV control,


waah waah waah

Are folks not reading the manual or is it just not very clear/obvious within ?

I realise it is a little hidden on Pam itself.

waah waah waah


I've had very little time with it so far, but perhaps part of the problem is that it is so intuitive that reading the manual may seem superfluous - of course this is not true, so I'd take this as a compliment on a well designed module rather than anything else wink
rikrak
ALM wrote:
resynthesize wrote:


d'oh! I didn't know pam had offset and attenuation built in for CV control,


waah waah waah

Are folks not reading the manual or is it just not very clear/obvious within ?

I realise it is a little hidden on Pam itself.

waah waah waah


It's very easy to find your way around every menu item and option without the manual - EXCEPT for the CV attenuation.

This may be because it is the ONLY situation (I believe...) where long-pressing while an entry is high-lighted has a different effect than if the entry is not high-lighted.

I can't see how else you could have done it, but it feels a little incongruous with the rest of the module.

For my own part in not ready the manual thoroughly, I hadn't realised that the clock PPQN could be set to CV until reading it in this thread. Last night I had one of the outputs feeding euclidean sine waves into the Tempo, leading to some very interesting time-based feedback behaviour!
ALM
I just spun a new 195 BETA firmware and would appreciate folks trying it out and reporting any issues. It should be pretty solid + you can always roll back to 192 if problems.

You can grab from http://busycircuits.com/firmware/alm017/

Changes include (from http://busycircuits.com/firmware/alm017/ChangeLog.txt );

- Tweak program knob handling a little. 'Push twists' dont kick in right away. reduce hold time by ~ 20%
- Fix voltage control of euclidean params.
- Shave a few bytes off the filesize via envelope optimisation.
- Improve clock calibration resolution & handling. Now 0-100, below 50 slower, above 50 clock faster.
- Implement a basic 'screensaver' dimming the OLED after 10 mins of no interaction.

I've also made an initial alpha release of a simple cross platform GUI firmware updater tool. Currently there is only a Mac build (10.10+) available. If anyone has experience of building QT apps on windows please drop me a mail/PM. Sources available on busycircuits github.

The updater is available here; http://busycircuits.com/firmware/alm017/experimental-updater/

Please also check the associated README - http://busycircuits.com/firmware/alm017/experimental-updater/README.tx t
brandonlogic
ALM wrote:
I just spun a new 195 BETA firmware and would appreciate folks trying it out and reporting any issues. It should be pretty solid + you can always roll back to 192 if problems.

You can grab from http://busycircuits.com/firmware/alm017/

Changes include (from http://busycircuits.com/firmware/alm017/ChangeLog.txt );

- Tweak program knob handling a little. 'Push twists' dont kick in right away. reduce hold time by ~ 20%
- Fix voltage control of euclidean params.
- Shave a few bytes off the filesize via envelope optimisation.
- Improve clock calibration resolution & handling. Now 0-100, below 50 slower, above 50 clock faster.
- Implement a basic 'screensaver' dimming the OLED after 10 mins of no interaction.

I've also made an initial alpha release of a simple cross platform GUI firmware updater tool. Currently there is only a Mac build (10.10+) available. If anyone has experience of building QT apps on windows please drop me a mail/PM. Sources available on busycircuits github.

The updater is available here; http://busycircuits.com/firmware/alm017/experimental-updater/

Please also check the associated README - http://busycircuits.com/firmware/alm017/experimental-updater/README.tx t


very nice, thank you!
are you planing on adding that select save states with cv that was talked about on the previous pages?
ALM
brandonlogic wrote:

are you planing on adding that select save states with cv that was talked about on the previous pages?


Yes I would very much like to add this and some other bits BUT there is very very little space left on Pam so I cant make any promises!
dooj88
ALM wrote:

- Tweak program knob handling a little. 'Push twists' dont kick in right away. reduce hold time by ~ 20%
- Fix voltage control of euclidean params.
- Shave a few bytes off the filesize via envelope optimisation.
- Improve clock calibration resolution & handling. Now 0-100, below 50 slower, above 50 clock faster.
- Implement a basic 'screensaver' dimming the OLED after 10 mins of no interaction.


nice! thumbs up
hold time reduction is very welcome and smart going on screen saver! i know it would be a total waste of space, but having flying toasters or something pop up on screen dim would be hilarious.
BonJoey
ALM wrote:


I've also made an initial alpha release of a simple cross platform GUI firmware updater tool. Currently there is only a Mac build (10.10+) available. If anyone has experience of building QT apps on windows please drop me a mail/PM. Sources available on busycircuits github.

The updater is available here; http://busycircuits.com/firmware/alm017/experimental-updater/

Please also check the associated README - http://busycircuits.com/firmware/alm017/experimental-updater/README.tx t


I'm getting a Forbidden "You don't have permission to access..." page when I try to download the .dmg file. I'm not sure if that's exclusive to me though.

Either way, thanks for the update and continuing to improve an already great module!
ALM
BonJoey wrote:


I'm getting a Forbidden "You don't have permission to access..." page when I try to download the .dmg file. I'm not sure if that's exclusive to me though.



Oops! Sorry - should be ok now hyper
ugokcen
Any chance of improving the "Slop" parameter? I find it too much even at 1%, and I think few others have commented on that too. What is the maximum people use it at? Maybe take that to be the new "100" and scale it back from there.
BonJoey
ALM wrote:
BonJoey wrote:


I'm getting a Forbidden "You don't have permission to access..." page when I try to download the .dmg file. I'm not sure if that's exclusive to me though.



Oops! Sorry - should be ok now hyper


Excellent! Thanks!
brandonlogic
ugokcen wrote:
Any chance of improving the "Slop" parameter? I find it too much even at 1%, and I think few others have commented on that too. What is the maximum people use it at? Maybe take that to be the new "100" and scale it back from there.


I enjoy the current maximum slop I must admit zombie
c0nsumer
brandonlogic wrote:
ugokcen wrote:
Any chance of improving the "Slop" parameter? I find it too much even at 1%, and I think few others have commented on that too. What is the maximum people use it at? Maybe take that to be the new "100" and scale it back from there.


I enjoy the current maximum slop I must admit zombie


I personally just wish it scaled a little more. I haven't played with it a ton, but I found that it jumps up... really fast.

On the Beatstep Pro I've really liked the randomness + probability and swing settings on there for making what I want to happen.
ALM
I wonder if its more just the way the (simple) slop algorithm works - it never (intelligently) attempts to catch up or get back in time like a human would.

This means even a small amount of sloppiness will get increasingly very sloppy over time as it drifts more and more out.
jtregoat
ALM wrote:
I wonder if its more just the way the (simple) slop algorithm works - it never (intelligently) attempts to catch up or get back in time like a human would.

This means even a small amount of sloppiness will get increasingly very sloppy over time as it drifts more and more out.


I think this would definitely do it

about to try out the mac installer + beta firmware
ugokcen
Quote:

This means even a small amount of sloppiness will get increasingly very sloppy over time as it drifts more and more out.


Aha, so that's it. What I expected was something akin to the "humanize" parameters you find in DAWs. You select the notes and the function moves them slightly off the grid, which means that when your pattern repeats they are in exactly the same place.

I don't know about others but I feel like reaching for the "slop" when I'm using the Euclidean patterns, so maybe the slop could loop too?
erstlaub
The updater failed to work for me sadly (10.10.5) but the normal method via terminal did. I just got the 'Update failed - Is device connected?' error.

I also tend to find the slop a little too 'all or nothing', I wonder if something as simple as an exponential ramp rather than a linear one would give more scope for the 'just a wee bit wonky' end of the spectrum rather than 'who let the drummer get this drunk?'
ALM
erstlaub wrote:
The updater failed to work for me sadly (10.10.5) but the normal method via terminal did. I just got the 'Update failed - Is device connected?' error.


waah Did it just do this immediately as soon as you hit 'flash' ? and I assume Pam was connected ?

Anyone else tried as yet ?


erstlaub wrote:

I also tend to find the slop a little too 'all or nothing', I wonder if something as simple as an exponential ramp rather than a linear one would give more scope for the 'just a wee bit wonky' end of the spectrum rather than 'who let the drummer get this drunk?'


Working on it.. hyper
erstlaub
Yep, Pam's connected with a cable that's confirmed working for updating via terminal, hit flash and it gives me the error. Tried a few times just incase.

Is there any way i can debug/extract any useful info to share with you that might help work out if it's my macbook that's at fault?
ALM
erstlaub wrote:

Is there any way i can debug/extract any useful info to share with you that might help work out if it's my macbook that's at fault?


I think console in Applications -> Utilities -> Console should show you a crash log. I think it might be libusb crashing. If you could email me a screenshot / dump of it, it would be much appreciated.
erstlaub
I just tried it again to capture a log in console and it worked perfectly!

I wonder if I was being a dolt and doing something stupid, if I try to reload and older FW through the app it gives me that error but the newest one works.

Sending you the log which I've just checked and does also contain the attempts at 17.46 or thereabouts.

Thanks for the continued awesome work.

we're not worthy
monads
Love the dimming OLED after 10 mins feature!! No issues here loading the update via the Terminal (Sierra v10.12.5)!! Thanks for the improved/continued updates thumbs up
atte
195-beta works fine here.

Sorry, but I don't really get the dimming feature, why would I want that? Is there a way to turn it off?

In fact I'd like to be able to turn the brightness of the OLED up! Two weeks ago I rehearsed with a friend, since the weather was nice, we decided to do it outside in his garden. Even though we were in the shade a lot of displays were hard to read, but pams looked like the module was simply turned off.

BTW: I'm on linux and didn't take the time to try the firmware upgrader, but a while back I wrote a (dead simple) bash script, basically as a wrapper around the command line. In case anyone finds it useful, here it is:


Quote:
#!/bin/bash
if [ -z `which dfu-util` ]; then
echo dfu-util not installed...
exit
fi

if [ -z "$1" ]; then
echo "usage: $(basename $0) firmware.bin"
exit
fi

dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D "$1"
ULTRAsomething
Quote:
Sorry, but I don't really get the dimming feature, why would I want that?


OLEDs, for all their wondrous goodness, have one achilles heel: limited lifespan. Consequently, most devices that use OLEDs need screen savers in order to disable them when not needed. Just looking at a few of my OLED devices — Intellijel Rainmaker; DSI Pro-2; MacBook Pro Touchbar; Control Forge (beta software) — all have OLEDs and all have screen savers that kick in after x amount of time to preserve the life of the display.

I, for one, am thrilled that the screen dimming has been added. I've been keeping my Pam's in a remote case so I can turn it on/off as needed. Now I can incorporate it into my main system, which stays on 24/7.
Splinter(UA)
Please tell me what kind of clock jitter in the new version "Pamela"???
Migrigsynth
Is there a way to display the firmware version on my Pamela?
jasev
Migrigsynth wrote:
Is there a way to display the firmware version on my Pamela?


power on with program knob held
Migrigsynth
Thanks, I think I read that somewhere but I couldn't remember what the procedure was until I read your answer. Thanks again thumbs up
Migrigsynth
erstlaub wrote:
The updater failed to work for me sadly (10.10.5) but the normal method via terminal did. I just got the 'Update failed - Is device connected?' error.




I just tried the updater also and it failed. I got the same air as posted above ( update failed – is device connected? )
ALM
Migrigsynth wrote:

I just tried the updater also and it failed. I got the same air as posted above ( update failed – is device connected? )


What OS X version and did the error come up right away ?
Migrigsynth
ALM wrote:
Migrigsynth wrote:

I just tried the updater also and it failed. I got the same air as posted above ( update failed – is device connected? )


What OS X version and did the error come up right away ?


I'm on 10.10.5. Yes, it failed immediately and gave the error " update failed – is device connected? "

I was able to perform the update using homebrew and the terminal. It worked smoothly. Although, it's relatively intimidating for me to use the terminal. Firmware 195 up and running!! :
Rockin' Banana!

I am relatively new to modular but I must say this module is really fantastic!!!
jasev
ALM wrote:
resynthesize wrote:


Thanks for the response. I'm trying to create some voltage tables for the ER-101 to CV control the clock multipliers and still having trouble. Would it be possible to provide a table of voltages that correspond with each multiplier rate?


Use the CV attenuation and offset to dial down the range and it should be simpler, not needing a table. i.e. For something roughly like x1 -> x8;

1. Assign desired output multiplier to CV1.
2. Offset the CV to approx 75% - this should be x1
3. Lower the CV attenuation to approx 15-20%
4. 0-5V into CV should now give multiplier increments in approx 1v steps.

Adjust steps 2 & 3 to taste.


i don't suppose anyone could explain whats going on with the external CV here could they?? Just so i can understand whats going on? I understand that external CV is controlling a selected output to control whatever . Just would like to know whats happening to external cv after its getting offset by 75% and attenuated 15-20% at the input and the adjusting of steps 2 and 3

Cheers
fourhexagons
ALM wrote:
Thanks fourhexagons - looking into whats up with cv control of euclidean rotation.

Note CV2 is +/-5v (not 10v) though I see the point your making. Maybe allowing the CV offset to go negative or attenuation to +/-200% would help here. I need to think on it.. Adding to the list smile

Great!
fourhexagons
ALM wrote:
resynthesize wrote:


d'oh! I didn't know pam had offset and attenuation built in for CV control,


waah waah waah

Are folks not reading the manual or is it just not very clear/obvious within ?

I realise it is a little hidden on Pam itself.

waah waah waah

Ha. A contributing factor could be that the functions are mentioned in the manual within a paragraph, yet there is no heading or bold text to make it easy to find when skimming.

This is all personal aesthetic, but I could envision an organizational scheme like this, where 'Voltage Control' is the H1 (largest), 'CV Assigning' is the H2 (second largest), and 'Attenuation and Offset' is, therefore, an H3 (third largest).

Quote:

Voltage Control
As well as direct user control, Pamela’s clock and outputs can be assigned to external voltage control via 4 upper external signal inputs - clock, run, CV 1 & CV 2.

CV Assigning
An output modifier and many of its extended parameters can be externally voltage controlled by assigning its parameter value to either of the CV inputs.
CV 1 responds to voltages between 0 and 5v, whilst CV 2 responds to voltage between -5 & +5v (ie with 0 being 50%). Voltages input outside of this range are safe but will be ignored.

Attenuation and Offset
With a value assigned to a CV input, it can be further controlled by setting a per-parameter attenuation and offset value to the incoming CV value. Pushing and holding the encoder knob whilst a parameter CV option is highlighted (in selection) will access sub-screens to set these values as well as provide the ability to visually monitor the applied CV value.


The idea is basically to add in H3's under the main H2 headings that are already present. A simpler approach would just be to boldface a few of the important embedded things like 'per-parameter attenuation and offset' in the second paragraph.

Whatever the case, my opinion is that ALM manuals are very well-written. I work with Xaoc to help write their manuals, and copy editing is part of my dayjob. So, yeah, my 2 cents This is fun!
ALM
Thanks for input fourhexagons! I added in another header for now.

AM working on a separate FAQ too which I hope will help also.
ALM
jasev wrote:
ALM wrote:
resynthesize wrote:


Thanks for the response. I'm trying to create some voltage tables for the ER-101 to CV control the clock multipliers and still having trouble. Would it be possible to provide a table of voltages that correspond with each multiplier rate?


Use the CV attenuation and offset to dial down the range and it should be simpler, not needing a table. i.e. For something roughly like x1 -> x8;

1. Assign desired output multiplier to CV1.
2. Offset the CV to approx 75% - this should be x1
3. Lower the CV attenuation to approx 15-20%
4. 0-5V into CV should now give multiplier increments in approx 1v steps.

Adjust steps 2 & 3 to taste.


i don't suppose anyone could explain whats going on with the external CV here could they?? Just so i can understand whats going on? I understand that external CV is controlling a selected output to control whatever . Just would like to know whats happening to external cv after its getting offset by 75% and attenuated 15-20% at the input and the adjusting of steps 2 and 3

Cheers


Its not changing the external cv in any way - Think of it as fine tuning the actual range of values that the 0-5v control voltage can actually effect. The offset basically sets the minimum value the 0V would map too (of which at 75% of the total list of factors maps too x1, 79% could map to x1,5, 83% to x2 etc..). The attenuation then controls the range the CV can effect added on top of this minimum... so at 5V it may only get up too x8 on this with this attenuation. You can visualise it by looking at the little bar graph monitor or by mapping to something like Level of which you can then easily monitor externally. Hope that helps.
fourhexagons
ALM wrote:
Thanks for input fourhexagons! I added in another header for now.

AM working on a separate FAQ too which I hope will help also.

Oh, great. Glad it was helpful.

And hey, in off-topic news, I just played a show with Robert A. A. Lowe this past weekend and while we were checking out each others' cases, he sung praises about ALM016 / PE-1. What a great concept. My entry into recording was with a 424 Portastudio way back when they first came out.
dumbledog
ALM wrote:
You can visualise it by looking at the little bar graph monitor

Whoa wait what
fourhexagons
dumbledog wrote:
ALM wrote:
You can visualise it by looking at the little bar graph monitor

Whoa wait what

Yeah, that bar graph is a useful feature.
jasev
ALM wrote:
jasev wrote:
ALM wrote:
resynthesize wrote:


Thanks for the response. I'm trying to create some voltage tables for the ER-101 to CV control the clock multipliers and still having trouble. Would it be possible to provide a table of voltages that correspond with each multiplier rate?


Use the CV attenuation and offset to dial down the range and it should be simpler, not needing a table. i.e. For something roughly like x1 -> x8;

1. Assign desired output multiplier to CV1.
2. Offset the CV to approx 75% - this should be x1
3. Lower the CV attenuation to approx 15-20%
4. 0-5V into CV should now give multiplier increments in approx 1v steps.

Adjust steps 2 & 3 to taste.


i don't suppose anyone could explain whats going on with the external CV here could they?? Just so i can understand whats going on? I understand that external CV is controlling a selected output to control whatever . Just would like to know whats happening to external cv after its getting offset by 75% and attenuated 15-20% at the input and the adjusting of steps 2 and 3

Cheers


Its not changing the external cv in any way - Think of it as fine tuning the actual range of values that the 0-5v control voltage can actually effect. The offset basically sets the minimum value the 0V would map too (of which at 75% of the total list of factors maps too x1, 79% could map to x1,5, 83% to x2 etc..). The attenuation then controls the range the CV can effect added on top of this minimum... so at 5V it may only get up too x8 on this with this attenuation. You can visualise it by looking at the little bar graph monitor or by mapping to something like Level of which you can then easily monitor externally. Hope that helps.


Shot cheers for this.

Think i need to CV school
ALM
Having no reported problems with the 195-Beta, I've now spun a non beta 196 release which also includes some tweaks to the slop parameter to hopefully make it a little more 'predictable'/natural.

You can grab it here;
http://busycircuits.com/firmware/alm017/alm017-196.bin

List of changes here;
http://busycircuits.com/firmware/alm017/ChangeLog.txt

Enjoy! When I next get a clear chunk of time I plan to attack the voltage controlled loading again. Not making any promises tho.. hyper
fourhexagons
I'm unable to find any info on backing up saved banks. Is this possible? As in, is there a way to backup and then reload saved presets upon firmware update?
ALM
fourhexagons wrote:
I'm unable to find any info on backing up saved banks. Is this possible? As in, is there a way to backup and then reload saved presets upon firmware update?


Not currently possible Im afraid.
funqpatrol
ALM wrote:

Enjoy! When I next get a clear chunk of time I plan to attack the voltage controlled loading again. Not making any promises tho.. hyper


Wow thanks that would take the pam to the next level really
dooj88
ALM wrote:
Having no reported problems with the 195-Beta, I've now spun a non beta 196 release which also includes some tweaks to the slop parameter to hopefully make it a little more 'predictable'/natural.

You can grab it here;
http://busycircuits.com/firmware/alm017/alm017-196.bin

List of changes here;
http://busycircuits.com/firmware/alm017/ChangeLog.txt

Enjoy! When I next get a clear chunk of time I plan to attack the voltage controlled loading again. Not making any promises tho.. hyper


thanks! slop on 192 was acting a bit like a burst generator when turned up really high. interesting, but unexpected. this'll be great.
guestt
funqpatrol wrote:
ALM wrote:

Enjoy! When I next get a clear chunk of time I plan to attack the voltage controlled loading again. Not making any promises tho.. hyper


Wow thanks that would take the pam to the next level really


Yes please!

I totally get that it might not be possible, so, after giving it some thought I think I'd sacrifice some functionality for this.

Would you consider an alternative firmware that really nailed the clock division side of things with the voltage controlled loading of presets over say the more exotic waveform outputs?

I have a multitude of function generators and LFOs, but what I always seem to struggle with is this level of clock manipulation and I would swap over in an instant smile
soundslikejoe
New user here.... and I LOVE THIS THING!

This may already be possible, or have been mentioned before in this thread....

I would like the multiple/divide function to be activated on a second select. It would make manual dynamic clock changes more musical to be able to select new multiplications or divisions without having every stage between active. For example... moving from 2x to /2 has several stages between.... and they are audible as scrolling from setting to setting. If the changing clocks were activated on a second click (as an exit and activate), the between clocks wouldn't fire or effect the output.... making a clean change from 2x to /2 or to any other clock setting.

Not sure if that makes sense.... or if it's already possible and I'm just a blockhead. Thx!
esotericmetal
ALM wrote:

Enjoy! When I next get a clear chunk of time I plan to attack the voltage controlled loading again. Not making any promises tho.. hyper


Holy crap, this would would awesome.
rikrak
soundslikejoe wrote:
... or if it's already possible...


Set it to a CV input and send it a stepped voltage? Pretty sure it will jump directly to the respective settings.
chockfullofthat
FYI I've synced the Pam's to my DAW perfectly with Bastl Klik if anyone is looking for a cheap solution.
erstlaub
Figured I'd put this here with a little breakdown of what Pam's was doing. Closest I've come to using all the channels at once as I usually end up splitting a clock off to slave other modules to but tried to keep it fairly self contained.

[bandcamp width=100% height=120 album=3736948621 size=large bgcol=ffffff linkcol=0687f5 tracklist=false artwork=small]

Dull patch notes:

The main sections are Tides being played via Brainseed, level controlled by a Maths channel to the level input and the shape input being modulated via Pams.

A drone via Warps parasites chebyschev shaper folding together its internal oscillator at a fixed pitch and the bipolar output of Tides being modulated by smooth random voltages from Peaks in tap lfo mode (clocked by Pams).

Red noise from Quantum Rainbow 2 being fed to Ripples with it's inputs being rhythmically modulated by Pams.

Peaks bass drum being triggered via a trigger stream from Pams fed into blinds and also being opened by Pams to allow only 2 consecutive triggers pass.

PNW Channels

Channel 1 - x4 sending steady stream of triggers into Blinds
Channel 2 - /4 with width set to 10% which lets first 2 beats of trigger stream pass through Blinds and into Peaks in BD mode.
Channel 3 - /2 sending a clock to Peaks channel 2 in clocked LFO mode outputting random smoothed voltages to Warps level 2 input
Channel 4 - /12 Sine Wave attenuated, slowly modulating the FM input of Ripples
Channel 5 - x4 (playing in a 7/9 euclidian pattern) Sine Wave with width (shape) set to 5% to make a smooth envelope rhythmically modulating Ripples main frequency input
Channel 6 - /8 Sending a slow clock into Brainseed which is sending pitch CV to Tides, trig out of Brainseed is triggering a Maths channel that is plugged into the level input of Tides to open the VCA
Channel 7 - /12 sine wave gently modulating the shape parameter of Tides
dooj88
very nice erstlaub. that's some satisfying wavefolding action right there.
BlackDoors
ALM wrote:
Having no reported problems with the 195-Beta, I've now spun a non beta 196 release which also includes some tweaks to the slop parameter to hopefully make it a little more 'predictable'/natural.

You can grab it here;
http://busycircuits.com/firmware/alm017/alm017-196.bin

List of changes here;
http://busycircuits.com/firmware/alm017/ChangeLog.txt

Enjoy! When I next get a clear chunk of time I plan to attack the voltage controlled loading again. Not making any promises tho.. hyper


Thank you! Installed in mere seconds using the updater.

John
brandonlogic
c0nsumer wrote:
brandonlogic wrote:
c0nsumer wrote:
Check out the Doepfer A-166 as well. It's 8HP but a bit more than twice the functionality because of the input jacks being normalized to the one above.

thanks for pointing that one out, i think im gunna snag one!


You're welcome! I grabbed one at the same time as PNW. I'm using it in conjunction with a BeatStep Pro to do ratcheting with rests.
.


really been enjoying this a166/pam combo, with paths too, endless possibilities, really fun way to patch some really interesting percussion patterns (lots of happy accidents).

here was my first test with it when i got it: https://www.instagram.com/p/BUnCV8pFku1
dooj88
it took 20 minutes or so to figure out the update process for windows, so to save time in case i forget in the future, i wrote down step by step directions. hope this helps if you're lost or frustrated::

put the download file "alm017-196.bin" in root of c drive
create a new folder in root of c drive. call it "update" (relevant what it's called in order to maintain consistency with the command line at the end). paste all the downloads from the "dfu-util-0.8-binaries" page (i downloaded all 7 files) inside the folder.

run "zadig-2.3" which loads it as a driver as outlined in Pam manual:
options, list all devices
--select STM 32 BOOTLOADER
--select WinUSB near green arrow

connect pam

open CMD, (right click, 'run as admin' to be safe..)

copy the following file line, making sure you change the last part "alm017-196.bin" to reflect the newest file name:

C:\Update\dfu-util-0.8-binaries\win32-mingw32\dfu-util.exe dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D c:/alm017-196.bin

in CMD, right click and paste. update should execute.


This is fun!
oinkbanana
Just spent a bunch of time getting setup to update the pam. 3 computers later, and back to the original one I got it all figured out. ya know that last try where you do all the same steps excepts you asked your buddy to watch over your shoulder if you're reading wrong, but for some reason it all worked... LOL

but I'm grateful It worked and I'll be checking out the new calibration tomorrow... enough for today. At least I know it'll be smooth for next time.

Thanks.
propertyof
my pam's finally arrived this afternoon! hyper
just want to make sure now, i want to update the firmware, version 196 is the latest one right?
i'm using windows 10 pro, hope there will be no problem.
monads
propertyof wrote:
i want to update the firmware, version 196 is the latest one right?


Yup, that's the latest right now.
propertyof
update complete. nanners
undulatex
me too is in love with pam. works pretty great even with sloppy external clock on low ppqn, which i didn't dare to hope for.

but as a eurorack/patching pre-schooler im a bit confused over the possibilites to use the cv inputs to patch the thing into itself. seems to work sometimes but sometimes not and im not sure if im doing it right...
can someone provide a few patch examples to try out?
what values should i set and which cv input should i use?
for example, can i somehow make an "inverted" euclidean pattern with triggers on the skipped steps? can it be explained to someone without a clue? smile
nciviero
undulatex wrote:

can i somehow make an "inverted" euclidean pattern with triggers on the skipped steps? can it be explained to someone without a clue? smile


Take a copy of the euclidean clock and invert it with an attenuverter. Then plug that into the +/- input and apply it to the level of a straight clock of the same division. You may have to apply a 100% offset in the cv2 settings, I don't have my system in front of me and I haven't used the +/- a ton yet.
Daisuk
dooj88 wrote:
it took 20 minutes or so to figure out the update process for windows, so to save time in case i forget in the future, i wrote down step by step directions. hope this helps if you're lost or frustrated::

put the download file "alm017-196.bin" in root of c drive
create a new folder in root of c drive. call it "update" (relevant what it's called in order to maintain consistency with the command line at the end). paste all the downloads from the "dfu-util-0.8-binaries" page (i downloaded all 7 files) inside the folder.

run "zadig-2.3" which loads it as a driver as outlined in Pam manual:
options, list all devices
--select STM 32 BOOTLOADER
--select WinUSB near green arrow

connect pam

open CMD, (right click, 'run as admin' to be safe..)

copy the following file line, making sure you change the last part "alm017-196.bin" to reflect the newest file name:

C:\Update\dfu-util-0.8-binaries\win32-mingw32\dfu-util.exe dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D c:/alm017-196.bin

in CMD, right click and paste. update should execute.


This is fun!


Thanks a lot for this! Made updating a breeze. we're not worthy This is fun!

New Pam's is fucking ace, by the way! Mr. Green Mr. Green we're not worthy
neilmcm1975
I am trying to clock Pams from my erm multiclock and its 1bpm out , the erm says 122bpm and the Pams 121bpm anyone have any isssues with external clocking.
Daisuk
neilmcm1975 wrote:
I am trying to clock Pams from my erm multiclock and its 1bpm out , the erm says 122bpm and the Pams 121bpm anyone have any isssues with external clocking.


Pam says 119 BPM when I'm sending 120 BPM clock from Ableton Live through an ES-3 as well, but the sync is dead on, so I couldn't care less personally. smile
neilmcm1975
Daisuk wrote:
neilmcm1975 wrote:
I am trying to clock Pams from my erm multiclock and its 1bpm out , the erm says 122bpm and the Pams 121bpm anyone have any isssues with external clocking.


Pam says 119 BPM when I'm sending 120 BPM clock from Ableton Live through an ES-3 as well, but the sync is dead on, so I couldn't care less personally. smile


Thanks Daisuk just wanted to see if this was normal .
ALM
Yes its normal. They are in sync but each device simply has a slightly different representation of X BPM. If its annoying, you can ‘fine tune’ Pam’s internal clock to better match external devices - See Appendix I in the manual.
Orange
Pamela....she is with me w00t
Got her last week, playing with her tonight...
She won't leave me.
Damn, she is so nice, I love her!
jwise
I'm trying to understand why if I set my PNW to 120bpm and I'm sending it as an external clock to something like the Stillson Hammer I have to multiply the output signal by 4 in order to get 120bpm at the sequencer? I'm guessing it has something to do with the 16 steps, pulses, and accuracy of notes occurring on exact pulses as opposed to the 2 beats per second.

If anyone could explain this to me or direct me to a forum post that has laid this out for someone who is five years old, I'd appreciate it.
ALM
jwise wrote:


If anyone could explain this to me or direct me to a forum post that has laid this out for someone who is five years old, I'd appreciate it.


Simply the number of expected pulses per step (or quarter note) differs between different sequencers. This is is part of the reason why (original) Pam was created - something to sync everything up..

(Also see page 15 in the Pamela manual)
monads
governor blacksnake wrote:
Stillson Hammer requires one clock per 16th note, or 4PPQ.


The above.
Roy72
I've been trying to find out, but is there CV control of divisions in the New Pam's? so I can say modulate between 1/2, 1/4 and 1/8s?
LongLostDonut
dooj88 wrote:
it took 20 minutes or so to figure out the update process for windows, so to save time in case i forget in the future, i wrote down step by step directions. hope this helps if you're lost or frustrated::

put the download file "alm017-196.bin" in root of c drive
create a new folder in root of c drive. call it "update" (relevant what it's called in order to maintain consistency with the command line at the end). paste all the downloads from the "dfu-util-0.8-binaries" page (i downloaded all 7 files) inside the folder.

run "zadig-2.3" which loads it as a driver as outlined in Pam manual:
options, list all devices
--select STM 32 BOOTLOADER
--select WinUSB near green arrow

connect pam

open CMD, (right click, 'run as admin' to be safe..)

copy the following file line, making sure you change the last part "alm017-196.bin" to reflect the newest file name:

C:\Update\dfu-util-0.8-binaries\win32-mingw32\dfu-util.exe dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D c:/alm017-196.bin

in CMD, right click and paste. update should execute.


This is fun!


Thank you, that was really helpful and I now have an updated Pam It's peanut butter jelly time!

The only change I'd make to the instructions you posted is that you need to connect Pam to your PC before you you run Zadig, as I didn't see the STM 32 BOOTLOADER option in the drop down before it was connected.

Once Pam was connected, this option appeared in the drop down, so I selected it, then WINUSB in the right hand option and pressed the 'Replace Driver' button. Then when I ran the command line, the update worked.

I've only quickly used the new update, but Slop seems much better and I'm loving the slightly quicker hold-press timing.
uebl
thanks to the updater, the update to 196 was even easier than the last one thumbs up
propertyof
ok so i got my new pam 2 weeks ago but i forgot to mention that the glass screen position is not permanently fixed since arrival, maybe because too excited to play with it. i mean, if you touch the screen with your finger, you can move the glass. it's smaller than the display hole of the metal faceplate, there's maybe about 1 mm extra room left.
is it normal or mine is defected?
i'm worried it will collect more dust to the inside part of oled display, it's already cought some.
Shledge
I'm really liking mine - at the moment it's synced with my BSP and is quickly proving to be the heart of my system. cool

However, some feedback:
- I know we have a 1ppqn mode, but is it possible to have a true "one step" mode so it'll play nicely with any normal clock source? At the moment it causes a delay with anything below 4ppqn (particularly with anything as a multiple of the original speed) and causes issues if I try to use a clock with a deliberate pattern.
- I think the addition of a freerunning mode would be nice, where does advance by an external clock, but does not assume it's running or not by it. In other words, if the clock stalls, it doesn't advance to the next step rather than stopping completely.
- is there a reason why LFOs are at such a low samplerate, especially at slower speeds?
ALM
propertyof wrote:

is it normal or mine is defected?


Please can you send a photo to help <at> busycircuits.com ?
propertyof
ALM i emailed you a video for a better perspective/details. my phone's camera sux.
void23
I just received a New Pamela's last night and at first, had a hell of a time trying to sync it with a clock coming in through Yarns; clock out of phase, and it didn't seem to be picking up the reset signal correctly. I just updated from 192 to 196 and thing seem to be working better with Yarns finally.

That said, the full plan was to switch from Yarns to a Doepfer A-190-8 to save some space, but Pamela's is definately not happy with the clocks coming from the Doepfer module. Anyone have any luck with that combo and have any tips. Additionally, I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's. Both Grids and TINRS Tuesday are out of phase with a Pamela's clock, but work fine with the Yarns clock. I've tried setting the gate length down, but no luck so far.

Before Pamela's, I used the A-160 series dividers and everything worked perfectly. The hope was to have cleaner patching a greater flexability with Pamela's but it just seems so darn picky and inconsistent about what clock it will take and whether other modules will take it's clock.
ALM
void23 wrote:

That said, the full plan was to switch from Yarns to a Doepfer A-190-8 to save some space, but Pamela's is definately not happy with the clocks coming from the Doepfer module.


Can you provide a little more detail so I can try and help ? What clock output multiplier on the A-190 are you using ? How are you driving the A-190 via usb or via the midi Din ? Whats that connected too ?

How is Pam 'not happy' with the clock ? Is Pam complaining the incoming clock is unstable ?

void23 wrote:

Additionally, I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's. Both Grids and TINRS Tuesday are out of phase with a Pamela's clock, but work fine with the Yarns clock. I've tried setting the gate length down, but no luck so far.


Sorry I dont completely follow.

How do you mean ' I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's'

How do you know grids etc are out phase with Pams clock ? Are you driving Pam from something else and they are out of sync with that ?

void23 wrote:

Before Pamela's, I used the A-160 series dividers and everything worked perfectly.


Have you used with the A-190 and it stayed in time ?
void23
ALM wrote:
void23 wrote:

That said, the full plan was to switch from Yarns to a Doepfer A-190-8 to save some space, but Pamela's is definately not happy with the clocks coming from the Doepfer module.


Can you provide a little more detail so I can try and help ? What clock output multiplier on the A-190 are you using ? How are you driving the A-190 via usb or via the midi Din ? Whats that connected too ?

How is Pam 'not happy' with the clock ? Is Pam complaining the incoming clock is unstable ?

void23 wrote:

Additionally, I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's. Both Grids and TINRS Tuesday are out of phase with a Pamela's clock, but work fine with the Yarns clock. I've tried setting the gate length down, but no luck so far.


Sorry I dont completely follow.

How do you mean ' I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's'

How do you know grids etc are out phase with Pams clock ? Are you driving Pam from something else and they are out of sync with that ?

void23 wrote:

Before Pamela's, I used the A-160 series dividers and everything worked perfectly.


Have you used with the A-190 and it stayed in time ?


First, the chain is Analog Rytm -> 190-8 -> Pamela's. I've tried both 4ppqn and 24ppqn out of the A-190-8 and every combo of the right side, "state" outputs with run on Pamela's toggled both ways.

As for the 24ppqn issue, if I mult the Yarns 24ppqn clock between Grids / Tuesday and Pamela's, everything is fine and dandy. Reset is coming from Yarns. If I go x24 out of Pamela's or try and use a reset tick, say /16, from Pamela's, everything goes out of phase.

I've used the Yarns > Doepfer stuff for about 9 months and it's been completely, rock solid since day 1.

If you PM me contact information, I can send you additional information / videos, etc, to help debug.
ALM
void23 wrote:


If you PM me contact information, I can send you additional information / videos, etc, to help debug.


Yep cool please if you can shoot a video of whats going and send to help <at> busycircuits.com . Lots of people use Yarns and Pam together and report as rock solid (see here and here for example) so I think something weird is going on.

Be good to know if Pam is reporting the A190-8 as being unstable (look on the PPQN screen when synced) and if you can explain in more detail your reset setup you mention - Could that be causing issues ? What exactly are you reseting ?
guestt
Seeing as I've been cited as successfully using Yarns and Pams together I thought it would be helpful to add some details.

Octatrack > Yarns > Pams working tip top here at whatever resolution set to, so long as they match up.

Ideally you need the O/ parameter of Yarns set to 96 and the PPQ setting on Pams to be 24.

But you can do the same with O/ = 16 and Pams set to 4PPQ

Cheers Guinness ftw!
void23
Baddcr wrote:
Seeing as I've been cited as successfully using Yarns and Pams together I thought it would be helpful to add some details.

Octatrack > Yarns > Pams working tip top here at whatever resolution set to, so long as they match up.

Ideally you need the O/ parameter of Yarns set to 96 and the PPQ setting on Pams to be 24.

But you can do the same with O/ = 16 and Pams set to 4PPQ

Cheers Guinness ftw!


But until the latest firmware, you'd get out an out phase mess until it received a subsequent reset. I ended up returning the Pamela's and went back to using Doepfer dividers; much more reliable.
ALM
void23 wrote:


But until the latest firmware, you'd get out an out phase mess until it received a subsequent reset. I ended up returning the Pamela's and went back to using Doepfer dividers; much more reliable.


I think your referring to the run input / reset bug which only appeared in the 191 firmware but was promptly fixed in 192 !

Im sorry you felt the need to return your pam :( If you'd got in touch and sent a vid Im sure we could of figured out what was going on.

Many thanks Baddcr for your info!
dooj88
LongLostDonut wrote:
dooj88 wrote:
it took 20 minutes or so to figure out the update process for windows, so to save time in case i forget in the future, i wrote down step by step directions. hope this helps if you're lost or frustrated::

put the download file "alm017-196.bin" in root of c drive
create a new folder in root of c drive. call it "update" (relevant what it's called in order to maintain consistency with the command line at the end). paste all the downloads from the "dfu-util-0.8-binaries" page (i downloaded all 7 files) inside the folder.

run "zadig-2.3" which loads it as a driver as outlined in Pam manual:
options, list all devices
--select STM 32 BOOTLOADER
--select WinUSB near green arrow

connect pam

open CMD, (right click, 'run as admin' to be safe..)

copy the following file line, making sure you change the last part "alm017-196.bin" to reflect the newest file name:

C:\Update\dfu-util-0.8-binaries\win32-mingw32\dfu-util.exe dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D c:/alm017-196.bin

in CMD, right click and paste. update should execute.


This is fun!


Thank you, that was really helpful and I now have an updated Pam It's peanut butter jelly time!

The only change I'd make to the instructions you posted is that you need to connect Pam to your PC before you you run Zadig, as I didn't see the STM 32 BOOTLOADER option in the drop down before it was connected.

Once Pam was connected, this option appeared in the drop down, so I selected it, then WINUSB in the right hand option and pressed the 'Replace Driver' button. Then when I ran the command line, the update worked.

I've only quickly used the new update, but Slop seems much better and I'm loving the slightly quicker hold-press timing.


oh yeah, good call. i'm not sure if the program needs a hardware prompt to actually display the option for the bootloader for pam's, since this is what worked for me. but to eliminate any possible hiccups that might be smart to reverse that.
Mashmore
Patiently awaiting perfect circuit to get more in stock. Really looking forward to trying.
insect
If you have an Analog Rytm, it´s an easy task to sync new Pam. Just use DIN Sync out from Analog Rytm (via one of the 2 Midi outs) to clock Pamela`s New Workout. Pam love the clock from AR .. really! Just need that expert sleepers Din sync to 2 mini mono jacks.

So you can leave all the special midi things to yarns or your doepfer module.


Btw. I bought that cable 3 or months ago from Analogzone in Hungary. Seems they were the only shop in EU who still had some cables stocked. Would be nicer to buy such a cable directly from ALM wink



void23 wrote:
ALM wrote:
void23 wrote:

That said, the full plan was to switch from Yarns to a Doepfer A-190-8 to save some space, but Pamela's is definately not happy with the clocks coming from the Doepfer module.


Can you provide a little more detail so I can try and help ? What clock output multiplier on the A-190 are you using ? How are you driving the A-190 via usb or via the midi Din ? Whats that connected too ?

How is Pam 'not happy' with the clock ? Is Pam complaining the incoming clock is unstable ?

void23 wrote:

Additionally, I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's. Both Grids and TINRS Tuesday are out of phase with a Pamela's clock, but work fine with the Yarns clock. I've tried setting the gate length down, but no luck so far.


Sorry I dont completely follow.

How do you mean ' I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's'

How do you know grids etc are out phase with Pams clock ? Are you driving Pam from something else and they are out of sync with that ?

void23 wrote:

Before Pamela's, I used the A-160 series dividers and everything worked perfectly.


Have you used with the A-190 and it stayed in time ?


First, the chain is Analog Rytm -> 190-8 -> Pamela's. I've tried both 4ppqn and 24ppqn out of the A-190-8 and every combo of the right side, "state" outputs with run on Pamela's toggled both ways.

As for the 24ppqn issue, if I mult the Yarns 24ppqn clock between Grids / Tuesday and Pamela's, everything is fine and dandy. Reset is coming from Yarns. If I go x24 out of Pamela's or try and use a reset tick, say /16, from Pamela's, everything goes out of phase.

I've used the Yarns > Doepfer stuff for about 9 months and it's been completely, rock solid since day 1.

If you PM me contact information, I can send you additional information / videos, etc, to help debug.
esotericmetal
Was able to update to 196 with the mac updater. Worked great. Couldn't have been quicker or easier really.

Though I did have to dig through this thread to find the link. Is there a reason the firmware updates for this module aren't on the official website?
void23
insect wrote:
If you have an Analog Rytm, it´s an easy task to sync new Pam. Just use DIN Sync out from Analog Rytm (via one of the 2 Midi outs) to clock Pamela`s New Workout. Pam love the clock from AR .. really! Just need that expert sleepers Din sync to 2 mini mono jacks.

So you can leave all the special midi things to yarns or your doepfer module.


Btw. I bought that cable 3 or months ago from Analogzone in Hungary. Seems they were the only shop in EU who still had some cables stocked. Would be nicer to buy such a cable directly from ALM wink



void23 wrote:
ALM wrote:
void23 wrote:

That said, the full plan was to switch from Yarns to a Doepfer A-190-8 to save some space, but Pamela's is definately not happy with the clocks coming from the Doepfer module.


Can you provide a little more detail so I can try and help ? What clock output multiplier on the A-190 are you using ? How are you driving the A-190 via usb or via the midi Din ? Whats that connected too ?

How is Pam 'not happy' with the clock ? Is Pam complaining the incoming clock is unstable ?

void23 wrote:

Additionally, I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's. Both Grids and TINRS Tuesday are out of phase with a Pamela's clock, but work fine with the Yarns clock. I've tried setting the gate length down, but no luck so far.


Sorry I dont completely follow.

How do you mean ' I can't get anything to sync faster than 4ppqn with a clock coming out of Pamela's'

How do you know grids etc are out phase with Pams clock ? Are you driving Pam from something else and they are out of sync with that ?

void23 wrote:

Before Pamela's, I used the A-160 series dividers and everything worked perfectly.


Have you used with the A-190 and it stayed in time ?


First, the chain is Analog Rytm -> 190-8 -> Pamela's. I've tried both 4ppqn and 24ppqn out of the A-190-8 and every combo of the right side, "state" outputs with run on Pamela's toggled both ways.

As for the 24ppqn issue, if I mult the Yarns 24ppqn clock between Grids / Tuesday and Pamela's, everything is fine and dandy. Reset is coming from Yarns. If I go x24 out of Pamela's or try and use a reset tick, say /16, from Pamela's, everything goes out of phase.

I've used the Yarns > Doepfer stuff for about 9 months and it's been completely, rock solid since day 1.

If you PM me contact information, I can send you additional information / videos, etc, to help debug.


Wasn't able to ship due to the holiday, so I decided to pull the Pamela's back out and try DIN Sync from the A4. Still not happy though, most starts are out of phase until a reset tick syncs them back. There's also a bit of lag coming from Pamela's. it's all very similar to what's described in this thread.

https://www.muffwiggler.com/forum/viewtopic.php?t=114313&start=20&sid= eee6131a577e97ee97028b043eebab3f

Another thing I noticed is that Pamela's needs the input ppqn to be twice the fastest output. 48ppqn in and 24ppqn through an out is good (but not perfect). 24ppqn in and 24ppqn out never syncs.
ALM
void23 wrote:
There's also a bit of lag coming from Pamela's. it's all very similar to what's described in this thread.

https://www.muffwiggler.com/forum/viewtopic.php?t=114313&start=20&sid= eee6131a577e97ee97028b043eebab3f



That thread is 3 years old and for the original old Pamela not the new one (Which has completely different h/w and rewritten software)..

Please just shoot support an email and we'll figure out whats going on with your setup.
ALM
insect wrote:
Would be nicer to buy such a cable directly from ALM wink


See the D.S.G -> http://busycircuits.com/alm004/
MossGarden
Want to update to 196, will my saved states be wiped? I have a gig this weekend and will hold off if they will vanish.

hmmm.....
ALM
MossGarden wrote:
Want to update to 196, will my saved states be wiped? I have a gig this weekend and will hold off if they will vanish.


Yes - hold off till after your gig.
MossGarden
Cheers ALM applause
jtregoat
hey ALM

having a LOT of fun with the PNW smile. haven't had a chance to update yet because I'm waiting for one of those mini usb cables to come in the mail.

love everything. wanted to make one request though... a cue option? for changing the patterns. for example, I'm doing a retrig on something, and I want it to suddenly jump from x1 to x4 or to /8.

I like as it is currently, because it's nice to scroll through and what find feels right when I'm creating a sound, but it would be cool if there were a performance option so that I could change the parameter without it being audible, primarily for the context of a live performance. i don't think I'd want it to be like a master channel thing, probably something that you can turn on per output would be ideal (or both...)

no idea how difficult this is, but would be helpful to me and i'm sure some other people using PNW for a live application! of course, thank you for all of your work and support that you do already smile just some feedback/suggestions
ALM
jtregoat wrote:

love everything. wanted to make one request though... a cue option? for changing the patterns. for example, I'm doing a retrig on something, and I want it to suddenly jump from x1 to x4 or to /8.


Use the save banks for this kind of thing (i.e loading in a new setup for a channel). Also mutes may be of related use.
jtregoat
ALM wrote:
jtregoat wrote:

love everything. wanted to make one request though... a cue option? for changing the patterns. for example, I'm doing a retrig on something, and I want it to suddenly jump from x1 to x4 or to /8.


Use the save banks for this kind of thing (i.e loading in a new setup for a channel). Also mutes may be of related use.


got it right, duh! haven't really been saving yet, mostly just jamming live atm thank you for the advice
soundslikejoe
ALM wrote:

Use the save banks for this kind of thing (i.e loading in a new setup for a channel). Also mutes may be of related use.


That works if you know you were going to do it before you decided to make the change. Live improvisation... saved banks won't fit the flow, but they are fun for system wide changes!

I've tried CV changes too for cleaner clock execution (using Pressure Points as static voltage). It gets closer.... but with only two CVs inputs.... and still requires pre-planning (not always happening in live improvisation). Not the best solution for those who are exploring "playing the modular" as a live instrument.

Having the "click to engage new time" when modifying a channel's clock would be a live performance heaven. It would be...
It's peanut butter jelly time!
guestt
Last night I set up Pams to work with the Shuttle Control from Endorphin.es and am happy to report that it works perfectly.

I used the Synchronisation PPQN (original) and Start/Stop Gate on the Shuttle control and 24PPQ on Pam's

Super tight; I can jam using the stop start buttons on the Octatrack!

Aside: Maybe I missed something but I don't understand why folks think that things are going to be in phase without a reset signal seriously, i just don't get it
jtregoat
soundslikejoe wrote:
ALM wrote:

Use the save banks for this kind of thing (i.e loading in a new setup for a channel). Also mutes may be of related use.


That works if you know you were going to do it before you decided to make the change. Live improvisation... saved banks won't fit the flow, but they are fun for system wide changes!

I've tried CV changes too for cleaner clock execution (using Pressure Points as static voltage). It gets closer.... but with only two CVs inputs.... and still requires pre-planning (not always happening in live improvisation). Not the best solution for those who are exploring "playing the modular" as a live instrument.

Having the "click to engage new time" when modifying a channel's clock would be a live performance heaven. It would be...
It's peanut butter jelly time!


Yeah I messed with the save banks and it's really not the same - takes a bit of the live jam away because you have to fiddle to get those saves preset, when you don't know which one will be best. but, I'm happy either way and do what I can to finagle it, just glad the suggestion is out there if it's at ever feasible in the future smile definitely would be heaven for live performances and would change the game for this clock for live people imo
void23
Baddcr wrote:
Last night I set up Pams to work with the Shuttle Control from Endorphin.es and am happy to report that it works perfectly.

I used the Synchronisation PPQN (original) and Start/Stop Gate on the Shuttle control and 24PPQ on Pam's

Super tight; I can jam using the stop start buttons on the Octatrack!

Aside: Maybe I missed something but I don't understand why folks think that things are going to be in phase without a reset signal seriously, i just don't get it


Yes, one would expect a reset signal to work with Pamela's just like the nine other devices I have in my rack with resets that seems to work perfectly with Yarns. wink
esotericmetal
Is it possible to sync the sq-1 with Pam as master clock (without the expanders)? I thought that I could just send a gate signal into the sync-in on the sq-1 but it doesn't seem to work. Are there some specific settings I need to use? I've tried this same thing with some other devices and it seemed to work fine.
ALM
esotericmetal wrote:
Is it possible to sync the sq-1 with Pam as master clock (without the expanders)? I thought that I could just send a gate signal into the sync-in on the sq-1 but it doesn't seem to work. Are there some specific settings I need to use? I've tried this same thing with some other devices and it seemed to work fine.


Should just work (does for me). You have to press play on the SQ-1 for it to start iirc. Also make sure you are sending it a pulse and not some other waveform.
Shledge
You'll need to set up the SQ-1 to be in 1-step mode, otherwise it's 4ppqn IIRC.
esotericmetal
How do you change it to 1-step mode? Can't seem to find anything about that in the manual. Is that the same thing as the step resolution in global settings?

I am sending it a short pulse and have the play button on. It does play along but the timing is just not synced with Pam.
slidearind
Hello ALM,

Pams appears to be out of stock almost everywhere. I've had it on order at my local shop in Toronto for 2 weeks.

Do you have any news on when the next shipment will go out?

Thanks!
ALM
slidearind wrote:

Do you have any news on when the next shipment will go out?


Restocks just started shipping out this week. cool
aroom
hi ALM

I've got some question regarding PNW and midi clock sync.

Right now, I'm using my Kenton Pro Solo MK2 to sync my daw and my modular like this :

daw > rme midi out > kenton pro solo mk2 > tempi or varigate 8+ clock in

could I do it like this with PNW ?

daw > rme midi out > midi to mini-jack cable adapter > PNW > varigate 8+ clock in


What kind of midi to mini-jack adapter would I need for a midi clock sync ? The one with one mini-jack or two ? Do I need to connect both CLK and RUN inputs ? I've seen that expert-sleepers is doing both kind of adapter.


I know it's stated in your manual (appendice IV) but I'm confused about the difference between DYN sync and MIDI sync, if there is any.


I also know and understand you point on encouraging us to use PAM as a master instead of syncing it via usb midi. But right know a rather have my DAW clock as a master (I understand both unit can't be precise about the BPM value and rather have a 120 BPM on my daw that a 119.9483, not a complaint)

So my second question is : if I want to use an audio track as a clock to sync PAM, do I need to have an audio interface with DC coupled audio outputs ? (my RME doesn't have DC coupled audio in or out, like the MOTU units) And how do produce an reliable audio clock track ?


thanks for the help, I've searched the thread, but it's not clear for me yet
ALM
That wont work - Pam doesn't take a direct midi clock in. You'd do like;

daw > rme midi out > kenton pro solo mk2 > pam

Alternatively with the audio track it may well just work with the RME output. Google is your friend for tools creating audio clock track. Others with more experience in this kind of setup Im sure can provide more info - I've only every really used expert sleepers h/w (and software - sync plugin) for audio syncing to daw.
Shledge
esotericmetal wrote:
How do you change it to 1-step mode? Can't seem to find anything about that in the manual. Is that the same thing as the step resolution in global settings?

I am sending it a short pulse and have the play button on. It does play along but the timing is just not synced with Pam.


There is a 1ppqn mode, but it's not a true 1-step mode as you'd expect on something like a sequencer. It's best to keep it at 24ppqn and either use a fast LFO, or anything that can output a clock signal at 24ppqn.

I generally find it works well being synced up to my BSP, with MIDI clock via my DAW.
slidearind
ALM wrote:
slidearind wrote:

Do you have any news on when the next shipment will go out?


Restocks just started shipping out this week. cool


Wow! That was fast! Cheers, and I'm looking forward to some clock madness!
guestt
void23 wrote:
Baddcr wrote:
Last night I set up Pams to work with the Shuttle Control from Endorphin.es and am happy to report that it works perfectly.

I used the Synchronisation PPQN (original) and Start/Stop Gate on the Shuttle control and 24PPQ on Pam's

Super tight; I can jam using the stop start buttons on the Octatrack!

Aside: Maybe I missed something but I don't understand why folks think that things are going to be in phase without a reset signal seriously, i just don't get it


Yes, one would expect a reset signal to work with Pamela's just like the nine other devices I have in my rack with resets that seems to work perfectly with Yarns. wink


Please forgive me but I'm not sure what your point is, are you saying it doesn't work for you? If that's the case drop a support email to ALM I'm sure they will sort you out smile

For the record, everything works as expected and is absolutely spot on here!! I couldn't be happier - 100% reliable!
ALM
FWIW if you are reseting slaved sequencers etc from Pam use an output with the modifier set to the little 'rising step' symbol connected to any reset inputs.

This will only issue a trigger when Pams clock stops thus resetting external synced sequencers to an initial state for when Pams clock starts again.

This avoids problems dealing with how different sequencers respond differently to a reset in respect to a running clock - especially when starting.
soundslikejoe
Curious... How would you guys do this with Pams New WO?

I want to improvise sudden tempo changes in a performance. Have it set to something very slow. Then jump to a much faster tempo at some point. Then move back and forth. I don't know the exact tempos... but they would all be some math relationship... x2, 75%, 125%, etc.

Ideas?
monads
Since we're talking about clocking from other sources....I tested clocking from HexInverter Midi2CV (sync output 24ppqn) with PNW set at 1ppqn and no issues. If you set PNW anything higher than 1ppqn it wont sync properly.

It takes about a few secs to sync up after pressing play from the DAW so you'll have to adjust the sequence if you want everything aligned after recording. Not sure this is the best way but just wanted to share. This option also allows for Tempo control from the DAW (speed up, slow down, etc.).
guestt
monads wrote:
Since we're talking about clocking from other sources....I tested clocking from HexInverter Midi2CV (sync output 24ppqn) with PNW set at 1ppqn and no issues. If you set PNW anything higher than 1ppqn it wont sync properly.

It takes about a few secs to sync up after pressing play from the DAW so you'll have to adjust the sequence if you want everything aligned after recording. Not sure this is the best way but just wanted to share. This option also allows for Tempo control from the DAW (speed up, slow down, etc.).


How can this even work at all? 24PPQN to 1PPQN should be total fail!

As for syncing to a DAW, well, that has never worked and never will with current technology, it's the worst of all sync stories; you're far better off using a spare audio out channel and a pulse rather than midi for computer to modular sync.
monads
Baddcr wrote:
How can this even work at all? 24PPQN to 1PPQN should be total fail!


I have no clue! It just worked. When I left PNW at default 24ppqn it didn't work. But set to 1ppqn it was good. Not saying I'm syncing up this way hihi But it wasn't horrible either.
ALM
monads wrote:
Baddcr wrote:
How can this even work at all? 24PPQN to 1PPQN should be total fail!


I have no clue! It just worked. When I left PNW at default 24ppqn it didn't work. But set to 1ppqn it was good. Not saying I'm syncing up this way hihi But it wasn't horrible either.


Are you sure you don't have the Midi2CV set to output a custom clock division of 1 ppqn instead of 24 ppqn hmmm..... ? See pg5 in the Midi2CV manual.
monads
ALM wrote:
Are you sure you don't have the Midi2CV set to output a custom clock division of 1 ppqn instead of 24 ppqn hmmm..... ? See pg5 in the Midi2CV manual.


Not that I'm aware of. Running the original V4.0 for the Midi2CV. Not using the more advanced v5.7.3 and it's extra features/programming.
guestt
v4.0 "This jack outputs an analogue version of the MIDI clock in the digital data stream. It is 24ppqn and can be divided down for use driving sequencers and the like. "

Worth checking!!
ALM
monads wrote:

Not that I'm aware of. Running the original V4.0 for the Midi2CV. Not using the more advanced v5.7.3 and it's extra features/programming.


If you drive something like an envelope/vca with the Midi2CV clock does it appear to be 1ppqn though ?
monads
Guess I'll have to run some tests to figure out. The v4.0 (user/setup manual v1.0) doesn't explain how the clock can be divided down even though it mentions. v5.7.3 (user/setup manual v2.0) explains "programming the clock divider", however was written for v5.7.3 and that's why I'm confused.
thewizmusic
FYI for anyone that wants to use the beatstep pro with the new firmware and still use clock in sync. if you take a channel and turn the multiplier up to 48 (on PNWO) the beatstep pro syncs. the start at play, although still in sync, has a little drift. Meaning it doesn't always start the same way like it does with midi in but its very usable. Just wanted to mention it because alot of people were pissed about them screwing this up.

I have been trying to find out which would be better using the expansion with midi out syncing to ableton (If I remember correctly PNWO manual says it is best as master) and also using silent way sync into PNWO. I prefer Ableton being master but PNWO as master with midi seems more stable. Also setting up silent way sync with clk and run input and settings on the plugin can get confusing. I have gotten it to work with both clk and run and just clk. What do you guys recommend? Im running straight out of a motu card
ChappySinclair
Anybody had any experience using PNW with the Bastl Tea kick? I've read that the Tea Kick gets a bit ornery when it doesn't get the triggers it wants.
Zymos
ChappySinclair wrote:
Anybody had any experience using PNW with the Bastl Tea kick? I've read that the Tea Kick gets a bit ornery when it doesn't get the triggers it wants.


Constantly- no issues here.
ChappySinclair
Zymos wrote:
ChappySinclair wrote:
Anybody had any experience using PNW with the Bastl Tea kick? I've read that the Tea Kick gets a bit ornery when it doesn't get the triggers it wants.


Constantly- no issues here.


Awesome, thanks for your input. I plan on getting both of them soon.
ChappySinclair
dbl post
gagatoio
The manual says how to connect the PEXP-2 to a Make Noise ... device.
I guess this refers to the 0-Coast?

Does anybody have any experience with PNWO + Pexp-2 + 0-Coast?
do you use the 3,5mm MIDI-jack (only) or any other ideas about all this?
I'm really wondering how others approach this.

Thanks This is fun!
Selektro
hello,

anyone tried DIYing the expanders?
want to make a 2hp hidden output jack module for Grids and would love to get that and pexp-2 all in one.

Could anyone with one share details on the components? or would ALM mind doing? or would ALM mind if anyone else does??!

possible can of worms i know, no problems if not, i know a lot of work does into designing and producing this stuff, Love akemies castle and New pams has just arrived and i think i need another!

cheers
ALM
Selektro wrote:
hello,

anyone tried DIYing the expanders?
want to make a 2hp hidden output jack module for Grids and would love to get that and pexp-2 all in one.



Easiest option is going to be grab a 2hp Pexp-2 and remove/modify the panel for an extra output jack - the actual pcb is pretty tiny.
AndreasD
Selektro wrote:

anyone tried DIYing the expanders?



I wanted the Run and the 24ppq clock for my Komplex sequencer.
Those signals are directly on the Expander connector on PNW's back. As far as I gathered the pinning is (ref pic on page 22 in PNW manual):
green:5V
yellow: Run (3.3V!)
orange: 24ppq Clock (3.3V!)
red: inverted clock?
brown: GND

Because it's all 3.3V signals, I gather that's direct from the cpu. So I added a high impedance buffer and adapt the 3.3V to 8V clock and run levels.
I put the 2 jacks on an existing DIY module that already had +-12V supply.

Works fine since weeks.
ALM
The 'inverted clock' is the MIDI clock out (again at 3.3v).

You need to buffer and level shift all outputs or external stuff wont work and you may well kill your Pam.

Only DIY if you really know what your doing, are happy to void your warranty and willing to risk frying your Pam. I can only support the official expanders !

Please strongly consider purchasing the official expanders and supporting ALM hyper
Migrigsynth
Here's a basic self generating track driven by Pamela's New Workout called Audio 90b. Awesome Module!!!


https://seekalternateroute.bandcamp.com/track/audio-90b


[bandcamp width=400 height=120 track=1162933110 size=large bgcol=ffffff linkcol=0687f5 tracklist=false artwork=small]
captainhooke
This thing is mental, had my first play yesterday night and it completely opened up my rack. Really impressed.

The incoming CV attenuation and offset per channel is sick, and the monitoring of the incoming CV looks slick.

Was a bit doubtful about the menu diving issue, but it's intuitive and after one evening I already feel pretty comfortable with it. still a lot to discover.

for a "small" rack (6u/104hp) like mine you can not really ignore it.

genius.
stwerewolf
Sorry if this has already been asked; does the MIDI expander work with the old Pamela?
captainhooke
stwerewolf wrote:
Sorry if this has already been asked; does the MIDI expander work with the old Pamela?




from their website http://busycircuits.com/alm017-ex/
funqpatrol
ALM how is the new firmware with VC over set loading is going? wink
mcpepe
Can you get noise from the new pamela?

I just bought and tried the other day without success. I got random cv stepped, but not continously. Is it possible?
nso_music
Loving this module, amazing work ALM. I would love to see a built-in slew parameter someday for use on the random wave though applause
Migrigsynth
A slew parameter on the random wave would be very cool
th0mas
Anyone else waiting on shipping, and have any clue when more are arriving? I've been waiting for a delivery from MoogAudio in Montreal since June 19th
mcpepe
I am trying to update my New Pamela's Workout to the latest firmware.

I already succesfully installed Brew

But when I execute ‘brew install dfu-util’ in the Terminal I get errors:
Quote:
MacBook-de-Jose:~ mcpepe$ brew install dfu-util
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:465:in `block in expand_dependencies'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:109:in `block in action'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:107:in `catch'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:107:in `action'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:86:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:83:in `each'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:83:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:463:in `expand_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:366:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
MacBook-de-Jose:~ mcpepe$


I am using OSX 10.7.5 Lion
guestt
Try the approved answer here:

https://stackoverflow.com/questions/36237537/brew-doctor-warning-how-t o-add-git-to-path

Good luck!
mcpepe
No. I didnt have luck!. When I tried the brew doctor it says:

Quote:
MacBook-de-Jose:local mcpepe$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: The system curl on 10.8 and below is often incapable of supporting
modern secure connections & will fail on fetching formulae.

We recommend you:
brew install curl

Warning: Git could not be found in your PATH.
Homebrew uses Git for several internal functions, and some formulae use Git
checkouts instead of stable tarballs. You may want to install Git:
brew install git

Warning: No developer tools installed.
Install the Command Line Tools from
https://developer.apple.com/download/more/
or via Xcode's preferences.


Warning: You have MacPorts or Fink installed:
/opt/local/bin/port

This can cause trouble. You don't have to uninstall them, but you may want to
temporarily move them out of the way, e.g.

sudo mv /opt/local ~/macports

Warning: You are using macOS 10.7.
We (and Apple) do not provide support for this old version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.


I think this OSX10.7 thing is the problem...
Thanks anyway!
guestt
Well, chances are 10.7 should be fine, these are common tools and there is a strong legacy support inherent in them. Sometimes it can be a problem of course, but you really should try the suggestions in the error message you just posted one by one... don't give up!
mcpepe
I tried everything in this post with no luck:

Quote:
MacBook-de-Jose:~ mcpepe$ cd /usr/local
MacBook-de-Jose:local mcpepe$ git
-bash: git: command not found
MacBook-de-Jose:local mcpepe$ git config --list --local
-bash: git: command not found
MacBook-de-Jose:local mcpepe$ brew install dfu-util
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:465:in `block in expand_dependencies'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:109:in `block in action'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:107:in `catch'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:107:in `action'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:86:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:83:in `each'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:83:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:463:in `expand_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:366:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
MacBook-de-Jose:local mcpepe$ brew install git
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
MacBook-de-Jose:local mcpepe$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: The system curl on 10.8 and below is often incapable of supporting
modern secure connections & will fail on fetching formulae.

We recommend you:
brew install curl

Warning: Git could not be found in your PATH.
Homebrew uses Git for several internal functions, and some formulae use Git
checkouts instead of stable tarballs. You may want to install Git:
brew install git

Warning: No developer tools installed.
Install the Command Line Tools from
https://developer.apple.com/download/more/
or via Xcode's preferences.


Warning: You have MacPorts or Fink installed:
/opt/local/bin/port

This can cause trouble. You don't have to uninstall them, but you may want to
temporarily move them out of the way, e.g.

sudo mv /opt/local ~/macports

Warning: You are using macOS 10.7.
We (and Apple) do not provide support for this old version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.
MacBook-de-Jose:local mcpepe$ brew install curl
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:465:in `block in expand_dependencies'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:109:in `block in action'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:107:in `catch'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:107:in `action'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:86:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:83:in `each'
/usr/local/Homebrew/Library/Homebrew/dependency.rb:83:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:463:in `expand_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:366:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
MacBook-de-Jose:local mcpepe$ brew install git
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
MacBook-de-Jose:local mcpepe$ https://developer.apple.com/download/more/
-bash: https://developer.apple.com/download/more/: No such file or directory
MacBook-de-Jose:local mcpepe$ brew update
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
MacBook-de-Jose:local mcpepe$ cd /usr/local/Library/Homebrew
-bash: cd: /usr/local/Library/Homebrew: No such file or directory
MacBook-de-Jose:local mcpepe$ git pull origin master
-bash: git: command not found
MacBook-de-Jose:local mcpepe$ cd /usr/local/Homebrew/
MacBook-de-Jose:Homebrew mcpepe$ git pull origin master
-bash: git: command not found
MacBook-de-Jose:Homebrew mcpepe$ cd /usr/local/Homebrew/Library/Homebrew/MacBook-de-Jose:Homebrew mcpepe$ git pull origin master
-bash: git: command not found
MacBook-de-Jose:Homebrew mcpepe$ brew update && upgrade
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
MacBook-de-Jose:Homebrew mcpepe$ brew install git
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
MacBook-de-Jose:Homebrew mcpepe$ brew install git
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
Error: Git must be installed and in your PATH!
Error: undefined method `>=' for nil:NilClass
/usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.r b:72:in `default_compiler'
/usr/local/Homebrew/Library/Homebrew/tab.rb:188:in `empty'
/usr/local/Homebrew/Library/Homebrew/tab.rb:157:in `for_formula'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:485:in `effective_build_options_for'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:431:in `block in expand_requirements'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:232:in `block in prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `catch'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:230:in `prune?'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:221:in `block (2 levels) in expand'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/l ib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:220:in `block in expand'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `each'
/usr/local/Homebrew/Library/Homebrew/requirement.rb:219:in `expand'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1479:in `recursive_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:430:in `expand_requirements'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:364:in `compute_dependencies'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:136:in `verify_deps_exist'
/usr/local/Homebrew/Library/Homebrew/formula_installer.rb:129:in `prelude'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:335:in `install_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:226:in `block in install'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/install.rb:224:in `install'
/usr/local/Homebrew/Library/Homebrew/brew.rb:95:in `<main>'
MacBook-de-Jose:Homebrew mcpepe$ which -a git
MacBook-de-Jose:Homebrew mcpepe$ brew config
HOMEBREW_VERSION: >1.2.0 (no git repository)
ORIGIN: (none)
HEAD: (none)
Last commit: never
Core tap ORIGIN: (none)
Core tap HEAD: (none)
Core tap last commit: never
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: dual-core 64-bit core2
Homebrew Ruby: 2.0.0-p648 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.0.0-p648/b in/ruby
Clang: N/A
Git: N/A
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
Java: 1.6.0_65-b14-462
macOS: 10.7.5-i386
Xcode: N/A
CLT: N/A
X11: 2.6.5 => /usr/X11
MacPorts/Fink: /opt/local/bin/port
guestt
OK, I can see now, you don't know what you're doing do you, that's ok, but it's tough the first time and even tougher trying to step back in time like this smile

There's a chance you could get it to work, but you're probably going to have to install an older version of git, one that was current around the time of 10.7 or some point after that when it was still supported, and/or probably an older version of Xcode too...

At this point it's probably best to either:

a) use a more modern machine/OS

b) contact ALM direct as they will know what the requirements actually are and wether it is possible or not.
mcpepe
Thanks Baddcr.

You are right. I dont know what I am doing! very frustrating

I will try with a newer Windows machine from a friend and let's see.

I remember I read somewhere that ALM were going to make an easier updater app. So maybe in the future this is more straight foward operation
Jondue
Has anyone had success clocking an Analog 4 using PNW with the PEXP1 expander? Am I correct in assuming that using this pair I can start/stop my A4 by pressing the start/stop button on PNW?

Thanks!
3lbFlax
Jondue wrote:
Has anyone had success clocking an Analog 4 using PNW with the PEXP1 expander? Am I correct in assuming that using this pair I can start/stop my A4 by pressing the start/stop button on PNW?

Thanks!


I don't have the PEXP1, but I have synced my A4 up to assorted devices and this should be fine - just make sure the A4 is set to receive MIDI clock and transport in the MIDI settings page, and regular MIDI is enabled (not just USB MIDI). It's all around page 50 of the manual (might move slightly in different versions, perhaps).

Should be a nice setup if you have the CV outs from the A4 set up, you'll have access to some very interesting synced / complex LFO and gate possibilities to complement the clocks from PNW.
blastedheath
This will no doubt be the next module I buy, great work ALM!
Jondue
3lbFlax wrote:
Should be a nice setup if you have the CV outs from the A4 set up, you'll have access to some very interesting synced / complex LFO and gate possibilities to complement the clocks from PNW.


Great, thanks for the response! Yes, the CV outs on A4 are indeed awesome. I think this will be the sync solution I have been looking for hihi
Nutritional Zero
th0mas wrote:
Anyone else waiting on shipping, and have any clue when more are arriving? I've been waiting for a delivery from MoogAudio in Montreal since June 19th


I actually biked down to Moog earlier this morning to ask about it since Moog's website is unhelpful. They don't have it and don't have an exact ETA. Perhaps they hit a production snag? Doing a bit of snooping on our neighbours to the south, Control in Brooklyn is also taking preorders, but the expected arrival date is listed as "Early August" which is now.

I'm probably just going to preorder from somewhere and forget all about it so that it's a nice surprise one day.
ratchet
I may (probably) be a little stupid but can someone advise how best to set this up with a my Elektron Analog 4 and uMidi without using DIN Sync? Or should I just give in and use DIN Sync? At the moment I take midi clock from the A4 to the uMidi and then output CV clock around the system.

My thinking with the PNW was to clock it from the uMidi and then use it with all it's multiplication and division goodness and to provide modulation, gates for switches etc in my system. But (I believe) PNW expects PPQN24? I have played around adjusting this to work with a 1/16 clock from the uMidi but then the BPM display is way off.

Am I just overly complicating things by going A4 to uMidi to PNW? Should I be using PNW as the Master instead of the A4? Any suggestions? The whole PPQN24 confuses me to start with.

I have searched the thread but will confess to being a little lazy and not reading every post in the (so far) 27 pages!
guestt
Hey ratchet,

You're not doing anything wrong, it's pretty straight forward but it can be confusing if you have never done it before!

Midi set to output on A4

Midi cable from A4 to uMidi

Set clk using the divide button to 1 so you get 24ppqn - pulses per quarter note - think about it this is really fast which is what you want!

Patch clk out to PNW Clock in

Patch run out to PNW Run in

Should be good to go! If you're not then Pam might need her settings returned to default.

Don't worry if BPM is slightly off on PNW - it should sound spot on!
ratchet
Thanks Baddcr.

After I switched the system off last night (and posted above) I did think - 'Of course the CLK out on the uMidi'. I had been trying with the 1/16th out.

I think you've confirmed it. I shall have a play tonight.
Nino
Does anyone know when PNW is gonna be restocked? It's sold out almost everywhere.
ratchet
Nino wrote:
Does anyone know when PNW is gonna be restocked? It's sold out almost everywhere.


Where are you? Rubadub in Glasgow have them. I just bought mine from them on Monday. Arrived Tuesday!
ratchet
So (and as advised by Baddcr) I have now connected the uMidi CLK out to PNW (rather than the 1/16th output) and had a bit play.

Now working as hoped. One thing that seems counterintuitive (to me) is that I have to multiply an output by x4 to get a 16th clock out. I guess this makes sense if the PPQN24 system and the outputs work on a 4 beats to the bar as base. I'm probably displaying a further lack of understanding there.

Anyway - I've got everything working as I want if not in the manner I expected at first. I can see this being great fun clocking my system and my Rene in particular.
guestt
Nice one ratchet

Glad you got it working smile

...and yes x4 is normal!
ratchet
Thanks Baddcr. Having great fun putting some odd stuff (timing, waves etc) from PNW into Rene's y clk with a steady 16th into the x clk.

I think there will be a lot of experimentation this weekend.
ben_hex
Pamela's NEW Workout from ALM Busy Circuits is killer! Really enjoying my time with it so far and here's a little drum jam with rhythms and modulation all coming out of the NEW Pam.

https://www.youtube.com/watch?v=PfYBVpwAVjs&lc=z22ocptgzlzec5eoz04t1ao kguslsukwtfiyg3napsicrk0h00410

ALM
I've uploaded a new 197 Alpha 'experimental' firmware which adds some requested new features, mainly around save banks. They includes the following (quoting the ChangeLog)

- Load and Save options now display last bank they were loaded from (or saved too).
- Run input can now be assigned to perform two new actions;
+ Load the next or previous full save bank from current (i.e a -> b -> c ->d, d -> c -> b)
+ Rotate all current outputs
Direction of both is dependant on CV input 1 being high or low.
- Output multples/divisions can now be changed without having to cycle through every option. With a factor highlighted, push and hold program knob whilst twistsing and changing value. Change will not get committed until knob is released.

You can download the firmware here - http://busycircuits.com/firmware/alm017/alm017-197-ALPHA.bin . Note installing will wipe any existing save banks.

It seems pretty solid but has not had a massive amount of testing and there are some larger than usual changes contained to free up space for the new features. Thus there may well be some bugs. If you find any let me know. You can always downgrade to the 196 firmware.

Please note however there is now a mere handful of bytes of program space left on the flash. Its highly unlikely there will be any new features now beyond bug fixes / minor tweaks. There just isn't the space left. The new Pam does waaaaaaaay more than I initially imagined I could get it to do. A lot of features people request can be accomplished by using another module in tandem (i.e low pass the random to get slopes). Please keep all this in mind before you go to request a new feature hyper

Also most stores now have restocks but there are more going out in coming week(s).
guestt
Amazing - thank you ALM

The rotation / next / previous features really complete this module imho!

Looking forward to trying it out!
rikrak
Wow! What an update - can't wait to fire it up later.

The Load Next/Previous sounds like an absolute killer feature!

Cheers! Guinness ftw!
rikrak
[edit: sent support email - to discuss ALPHA]
soundslikejoe
ALM wrote:

- Output multples/divisions can now be changed without having to cycle through every option. With a factor highlighted, push and hold program knob whilst twistsing and changing value. Change will not get committed until knob is released.

applause
Hug
erstlaub
Still deeply loving New Pam's although I can't say I've got much use for some of the newer additions myself (I can totally see how they're useful to others).

There is one really tiny fly in my ointment (I'd barely even class it as a fly, more a gnat or flea) which is that I would LOVE LOVE LOVE being able to change the mult/divisor from inside the advanced menu on each channel too instead of having to come out and go back in.

I'm not sure if it'd fit but it's the one thing that I find a bit cumbersome, particularly with how dramatic some of the cooler options can change the amount of events happening, it'd be nice to just scroll through rather than the press change press dance.

Cheers for all the hardwork in the first place ALM and further thanks for all the ongoing toil.
vingtdieux
thumbs up
interpolate
Sorry if this has been asked a billion times, but how well does Pamela handle swing?

I really like on the Elektron's how you have a global swing you apply, and it only applies to the off beat 16th notes.

Can I get a swung clock out of Pamela with swing on the off beats and not on the "on" beats?
guestt
Not to my knowledge interpolate


...but you could dedicate two channels at half time, offset one set of triggers 50%, add swing to the off beat channel and then mix the signals together before they hit your sound source.
ALM
To do swing on a pam channel simply set the delay divisor parameter to 2 and then adjust the delay parameter (either direct or via voltage control) for how much swing your want.

Further experiment with the delay divisor and also the the channel multiplier to something non integer/odd for some really strange swings.
guestt
Oh nice ALM - didn't know that was possible - thanks!!!
ALM
Baddcr wrote:
Oh nice ALM - didn't know that was possible - thanks!!!


Yep and also possible in original Pam.
guestt
I never had the original so it's still quite new and obviously still learning grin
djthopa
Sorry if this has been asked before.
How can i assign cv1 or cv2 to change divisions of a channel?
Have not figured out how to do it so far.
Cheers
erstlaub
Just scroll right through the divisors at the top level and you can pick cv1 or 2.

remember, as with all cv setting options, you can long hold the button when a cv setting is highlighted to access the offset and attenuation parameters, handy for dialing in a base/centre division to modulate around.
ben_hex
I'd second that erstlaub, would be great to have it as as scroll-able feature in that outputs menu as well as having to hold to go back out.

Absolutely loving the module! Full video coming this week. But for now here's a little dub techno number jamming with it and the Elektron Analog Four.

https://youtu.be/Na0FqiyC9vc

dooj88
ben_hex wrote:
I'd second that erstlaub, would be great to have it as as scroll-able feature in that outputs menu as well as having to hold to go back out.

Absolutely loving the module! Full video coming this week. But for now here's a little dub techno number jamming with it and the Elektron Analog Four.

https://youtu.be/Na0FqiyC9vc



nice one ben, smooth patch. i've pretty much got down all the basic stuff, but haven't yet messed around with CV assignments. hoping to see some of that in your upcoming video!

(is that a new camera as well? quality looks great!)
rikrak
ben_hex wrote:
Absolutely loving the module! Full video coming this week.


You might want to include the new Rotate mode(s!) and Preset Loading via CV. I've been playing with the upcoming release and the new modes give Pam superpowers!
djthopa
Thanks for the replies!

I saw the cv1 and cv2 on trigger channels, but did not know that implied that they corresponded to modifying divisions.

So if i want to asign say cv1 to shape of an lfo, do i select lfo, and long hold to enter the submenu and assign to cv1?

Or cv1 is predeterminded to be assgined to divisions?

Sorry im not in front of the modulat atm.

Cheers
erstlaub
If you're at the top level (bpm, channel div/mult) the cv1 or 2 setting means the cv will control the division of that channel.

In the sub menu (long press on a channel) you can dial any of the parameters to be cv controlled.

So you could use cv1 to control the division of channel 1 and cv2 to control the amount of random skipping on channel 2 for example.

Whenever you have a cv1 or 2 highlighted, a long press opens up a different menu that lets you add offset and attenuate the incoming cv, it sometimes takes some tweaking to find the sweet spot to get divisions cv ing nicely but once you do its so ace.
ben_hex
dooj88 hey, thanks for the kind words. No new camera. But I haven't been posting videos here that much as I got told to stop making so many threads for videos. So I've held off. I think quality has gone up lately with some more care and attention towards the lighting. Nothing particularly new just me getting more familiar I guess. thumbs up
djthopa
erstlaub wrote:
If you're at the top level (bpm, channel div/mult) the cv1 or 2 setting means the cv will control the division of that channel.

In the sub menu (long press on a channel) you can dial any of the parameters to be cv controlled.

So you could use cv1 to control the division of channel 1 and cv2 to control the amount of random skipping on channel 2 for example.

Whenever you have a cv1 or 2 highlighted, a long press opens up a different menu that lets you add offset and attenuate the incoming cv, it sometimes takes some tweaking to find the sweet spot to get divisions cv ing nicely but once you do its so ace.


Hey, thanks for the detailed info, i understand it much better know, will play
with the settings to find the sweet spots. Planning on doint it with mutable shades or levit8.

Thanks!
void23
I've about had it with this thing. It just won't sync reliably with the Analog Rytm over MIDI / Yarns or DIN Sync. Support has no solution but to say "it's not our modules problem, it's X" even though Doepfer clocks work just fine.

I was trying to decide whether I should just give up on DIN Sync an just get a PEXP-1 so just for fun, I tried running it with no clock input tonight and found that it takes three cycles for a 24ppqn pulse to just simply line up with /16 pulse. What's going on? Its like futzing MIDI clocks in Ableton all over again but in the modular world.

[s]https://soundcloud.com/john-belew/pamelas-no-sync[/s]

On top of everything else, I've discovered during testing tonight that the reset pulses behave differently based on which output you use when using DIN Sync from the AR. A reset based on a run / stop might trigger, sometimes, on output 1, but never fires on output 8.

I wish had just returned this thing when I had the chance for something that worked, but my optimism on trying to solve the problems based on the promised features got the better of me.
ntkrw
Sorry if this questions had answered before.

Do the power (bus power) required during the firmware update?

How to check the firmware version?

Thanks!
rikrak
ntkrw wrote:
Sorry if this questions had answered before.

Do the power (bus power) required during the firmware update?

How to check the firmware version?

Thanks!


No, you remove the power cable and attach Pam only by USB.

New Alpha firmware came out couple of days ago but I would wait for the upcoming bugfixed release.
erstlaub
djthopa wrote:
erstlaub wrote:
If you're at the top level (bpm, channel div/mult) the cv1 or 2 setting means the cv will control the division of that channel.

In the sub menu (long press on a channel) you can dial any of the parameters to be cv controlled.

So you could use cv1 to control the division of channel 1 and cv2 to control the amount of random skipping on channel 2 for example.

Whenever you have a cv1 or 2 highlighted, a long press opens up a different menu that lets you add offset and attenuate the incoming cv, it sometimes takes some tweaking to find the sweet spot to get divisions cv ing nicely but once you do its so ace.


Hey, thanks for the detailed info, i understand it much better know, will play
with the settings to find the sweet spots. Planning on doint it with mutable shades or levit8.

Thanks!


No worries, something I have found extremely cool and useful is using another channel of pams to modulate another's parameters (although naturally it takes up a channel). I find that modulating the divisor of one channel with a regular square trig/gate means you have can set your base rate by offsetting the 'low state' and then use the level to dial in the multiplied rate. You can then set where and for how long the changes happen with the phase and width settings if that makes any sense.

Edit, here's some settings to dial in that'll hopefully make more sense of what I'm talking about.

1. It's cool to setup a standard x1 division with a bass drum on it and just leave that running in the background as it lets you hear how the beats are falling. I used channel 5 just so it was out of the way of the others but it's not important.

2. Set channel 1's divisor to CV1, then long press with CV1 highlighted to drill down into the CV settings menu. Set offset to 84% and attenuation to 07%. Patch the output of Channel 1 to a hihat/snare/noise/whatever.

3. Patch Channel 2's output to CV1 input. Set Channel 2's modifier to /4, long press to drill down, use a standard square wave/gate/trig waveform and then set width to 25% and phase to 75% (so this means that the wave goes high for the last quarter of it's cycle).

You'll now hear the last 'bar' played with a roll/fill.

I find it's a bit easier using the CV settings menu to dial in what I need rather than the level setting on the modulating channel (this can all get a bit head twisty as you can attenuate and offset on both the receiving and the sending channels).
ben_hex
I'm aware this is long so timings and things covered below! smile

https://www.youtube.com/watch?v=Alu_cCDJIts



SKIP THROUGH THIS BEAST OF AN OVERVIEW WITH THE TIMING LINKS BELOW! :-)

Oh Pamela ... how beautiful you are, you're latest workout giving us modular geeks all we could have dreamt of and more! Gate, LFOs, stepped random, random skipping (of gates, of LFOs, of ANYTHING!) delay, swing, offset, phase, width / skewing, euclidean parameters (not just for gates but for LFO cycles too!) slop / humanise, saving everything, syncing like a trooper ... I could go on. This is ace, grab a cuppa and strap in for a tour of Pamela.

TIMINGS / LINKS / SKIP THROUGH TO YOUR HEARTS CONTENT

00:38 - OVERVIEW AND BUILDING A PATCH

- what is Pamela’s NEW Workout
- building a patch with drums, riffs, random and modulation

06:24 - LFOS

- delaying & swinging
- randomly skipping LFO cycles
- euclidean LFOs
- looping / locking modified LFOs
- influencing phase with CV inputs

15:08 - ENVELOPES

- patching a drum sound
- width control of release time

17:58 - CREATING MELODIES

- stepped random
- looping random sequences
- attenuating, offsetting, tuning
- creatively influencing melodies
- non destructive euclidean editing

21:33 - CREATING BEATS

- timing divisions
- phase offset for beat placement
- flams
- swing
- random skipping
- slop “humanize”

26:38 - MODIFIERS & SYNCING OTHER DEVICES

- gate on start
- gate on stop (reset)
- always on (run signal)
- always off
- syncing other devices with always on / run signal

30:50 - SYNCING PAMELA AS A SLAVE

- clock input
- PPQ / PPQN
- run and reset inputs

32.54 - CV INPUTS

- assigning CV over various parameters
- attenuating incoming CV
- offsetting incoming CV
- CV input monitor

36:35 - EXPANDERS

- Pexp-1
- Pexp-2
- syncing Elektron Analog Four via MIDI out.


If you've liked this video of Pamela's NEW Workout from ALM Busy Circuits here is the mentioned Elektron Analog Four jam video - https://youtu.be/Na0FqiyC9vc
dooj88
applause It's peanut butter jelly time! Dead Banana Dead Banana
Jondue
ben_hex wrote:

36:35 - EXPANDERS

- Pexp-1
- Pexp-2
- syncing Elektron Analog Four via MIDI out.


Hell yes. Thanks for demoing this!!
Jondue
dbl
ALM
Uploaded an slightly updated firmware - adds a number of fixes and tweaks to the new output rotate control (thanks rikrak!). Its looking pretty solid now and is a lot of fun - please do try and report back. You can download here;
http://busycircuits.com/firmware/alm017/alm017-197-BETA.bin

PS: Bens video above is great - highly encourage all to watch. Super informative & useful. hyper hyper hyper
funqpatrol
rikrak wrote:
ben_hex wrote:
Absolutely loving the module! Full video coming this week.


You might want to include the new Rotate mode(s!) and Preset Loading via CV. I've been playing with the upcoming release and the new modes give Pam superpowers!


Whaaaat?! has preset loading via CV been implemented already?
rikrak
funqpatrol wrote:
rikrak wrote:
ben_hex wrote:
Absolutely loving the module! Full video coming this week.


You might want to include the new Rotate mode(s!) and Preset Loading via CV. I've been playing with the upcoming release and the new modes give Pam superpowers!


Whaaaat?! has preset loading via CV been implemented already?


Yes, you can now Load Next/Previous Bank via a high/low voltage to CV1 and a gate into Run.

See the changelog here
Zymos
That top row rotation solves a problem I was going to run into (when I got around to updating). I use output 8 to send a clock to the rest of my system, but rotating all 8 outputs was going to screw that up.
So thanks for that!
funqpatrol
This is just awesome thanks @ALM
cptnal
Sold! we're not worthy
Catflap
Just pulled the trigger on this one It's peanut butter jelly time!
guestt
Thank you ben_hex

I learned a few things there SlayerBadger!
aroom
hi ALM

I had an idea while hiking today. Would it be possible to have an expander with 8 inputs to control the 8 outputs ?

for example, we could use PNW as a 8 envelops generators. or anything else that the module can produce - a lot - with an external trigger sequencer.
ALM
aroom wrote:
Would it be possible to have an expander with 8 inputs to control the 8 outputs ?


Sorry it would not be possible for the Pamela h/w to support something like this.
Nino
Allthough i'm quite sad that iirc saved presets get erased when updating the fw i snapped a PNW today – and i'm SO excited that i made this picture

Zymos
I'm sad about loosing presets too. So I'm happy that there is not much space for more features, because that means there wont be too many more updates.

Sorry, all you people requesting your cool ideas...
Catflap
Can't wait for this to arrive.
At the moment Im syncing my modular to Ableton like this

DAW > Analog4 (using OB) > M32 midi in > M32 to clock rest of system.
Im having no major issues with this method so far.

Would inserting PNW after the M32 cause any issues? Would I be better of using an audio pulse from Ableton direct into Pams' clk in?
guestt
Catflap wrote:
Would inserting PNW after the M32 cause any issues?


Don't know the M32 clock output but you're introducing a potential for problems if it isn't anything less than super tight!

Catflap wrote:
Would I be better of using an audio pulse from Ableton direct into Pams' clk in?


Almost certainly yes! This will make for a far more flexible setup smile
Chickonies
First off, I love this module immensely.

How feasible would it be to add tempo division latching to each output?

The octocontroller has a feature which I have come to like where a change in the division doesn't take place until the next beat or bar. It's great for live wiggling and making wub wub wubba wubbas. Am I right in thinking that a division change takes place instantly with Pam's? So if an output division is at 1 and I turn to 4 real quick it will start playing the next 16th beat? If turn it less quickly it might play all sorts stutter beats as I pass over the 1.5 and 2.7 divisions.

I could see an option on each output called latch div that controls how long it takes for a change in the division to take an effect.
A number value N in the same range of the tempo divisions would delay the change until the next Nth beat. So if the division is set to 1 then a latch div of 4 would cause the division to change only every 4 beats. A latching phase would let you make the change happen on any beat of a measure. A latching div value of 0 would be the standard behavior.

These same settings could be used on the CV settings (where offset and attenuation are set) to basically function like a sample and hold on the incoming CV.

Also, the latching could apply to all the settings of each output, so if I change the width setting it wouldn't happen until the next measure or whatever based on the latch settings.

All of this can be done with a sample and hold I know. Some us don't have a lot of those, just like we might not have a lot of attenuators and offsetters. But one of the best things about Pam is the built in attenuation and offset so I thought latching settings fit in with the spirit of the module and without making the menus any deeper.

Just an idea.
lisa
Chickonies wrote:
Am I right in thinking that a division change takes place instantly with Pam's?

Firmware 197: "With a factor highlighted, push and hold program knob whilst twistsing and changing value. Change will not get committed until knob is released."

Also: "Please note however there is now a mere handful of bytes of program space left on the flash. Its highly unlikely there will be any new features now beyond bug fixes / minor tweaks. There just isn't the space left."
bemushroomed
lisa wrote:
There just isn't the space left."


it's always possible to have 2 firmwares, one with some of the features removed (that some people might not be interested in) and new ones added in its place.. Let people choose which version is more to their liking. But yes i get it that it's probably a lot of testing and work.
bemushroomed
Edit: Nvm, successfully updated to 197BETA.
rikrak
bemushroomed wrote:
Edit: Nvm, successfully updated to 197BETA.


"File downloaded succesfully" indicates a succesful flash.
th0mas
just got a ship notice from Moog, sounds like the units are flowing again w00t w00t
atimbral
Just a report about the little updater program; it did not work for me. I'm on Mac 10.10.5. There was no error indication; just the normal dialog box that stated that the update was successful. The time it took to 'update' was very short, <1 sec, not the normal few seconds.But checking the module showed that the firmware did not actually change.

I updated just fine using the Terminal method, using the same cable and port; just as simple IMO. Thanks for 197!!
cptnal
Just ordered mine. Picking it up after work. hyper
Catflap
New Pam arrived today, loving it so far love
Menu is a breeze to use
The screen is super slick and easy to read considering how small it is.. and my eyesight is very poor.
Possibilities are endless with this thing
Screws came with washers! applause
Just a great product ALM .. bravo.
echox
Picked mine up yesterday. Quiet happy smile

Would be great to have a easier access to Un/Muting Channels. If the LEDs would be a toggle switch this would be great.

I think I will solve this with an additional modul smile
cptnal
Installed! Just spent an hour listening to it pinging SMR in a Euclidian stylee. Genius module.
fiiiu
ALM wrote:
albiedamned wrote:
boramx wrote:
Hey folks-
Can pam run from two or three gates tapped into the clock input? That is often my preferred way to set tempos.


I'm pretty sure the answer is no. It needs a continuous clock signal.


I think it may actually work if you lower the expected PPQN to 1.


Maybe I've missed it, but has anyone tried this? Thanks smile
Outtatune
I've had this thing for a while now but only just started to deep dive yesterday. This thing is awesome! So much power in 8HP.

Anyway here is 40 seconds of Soundcloud noise of Pam's driving two Pico Drums, a LI, a VCA being fed white noise, Branches, and Doepfer Seq Switch. Trying out Pam's trigs, envelopes, phase settings, euclidean settings, and other random stuff:

[soundcloud url="http://api.soundcloud.com/tracks/339408035" params="color=ff5500&auto_play=false&hide_related=false&show_comments= true&show_user=true&show_reposts=false&visual=true" width="100%" height="450" iframe="true" /]

Tres cool ALM. Tres cool.
bemushroomed
I really like it except for the display / text, it's just way too tiny. Also reading the extremely thin black text on the red background is very difficult. It does help using reading glasses though (only module i need glasses for). But it's an immensely useful module, up there with my favorites, like Batumi..
Torn n Frayed
bemushroomed wrote:
I really like it except for the display / text, it's just way too tiny. Also reading the extremely thin black text on the red background is very difficult. It does help using reading glasses though (only module i need glasses for). But it's an immensely useful module, up there with my favorites, like Batumi..


Agreed the text is very hard to read being red on black..
toneburst
Is it possible to add swing/shuffle to a clock output?

a|x
erstlaub
toneburst wrote:
Is it possible to add swing/shuffle to a clock output?

a|x


You can set a trigger delay and the rotation where it falls in addition to also changing the slop parameter (and of course any of those also by CV) so yes absolutely, it just takes a little bit more tweaking than say turning up the shuffle knob on the beatstep pro or in ableton but then it's also more flexible.

edit: (and of course you can also dial in any set of euclidian measures/events and also chuck a % of triggers to randomly skip in there too)
rikrak
toneburst wrote:
Is it possible to add swing/shuffle to a clock output?


Yes. There are two parameters for every output, Delay % and Delay Step. By default these are 0 and 0. Setting them to 15 and 2 would give a 15% delay to the start of every other Gate (or waveform or trigger) on that Output.

That's the easiest way, but it can get much more complex, as erstlaub says.
bemushroomed
If you come up with any cool shuffle's / swings, please share your settings, how you did it.

"I merely delay the second 16th note within each 8th note. In other words, I delay all the even-numbered 16th notes within the beat (2, 4, 6, 8, etc.)"

This is what I'm after really (quote from Roger Linn on Swing).

Guess i'll give it a shot when i get the time though..
stylesforfree
Nino wrote:
Allthough i'm quite sad that iirc saved presets get erased when updating the fw i snapped a PNW today – and i'm SO excited that i made this picture



Haha, awesome...

So can anyone comment on upgrading from pamelas workout to pamelas new workout?

It's a shame that the module and expanders dont come as an all in one module. £388 is just too steep, I would like to clock my mpc from pams. Also a shame you cant do this with the original module. Sighs.
Worwell
Great updates. Big thanks to ALM. This module is excellent and keeps getting better.
jtregoat
updated with the most recent firmware, using the mac update, worked perfectly!

thank you SOOOO much for being able to pick the speed before it changes! great for performance
lisa
stylesforfree wrote:
I would like to clock my mpc from pams. Also a shame you cant do this with the original module. Sighs.

It's a shame that your MPC lacks a clock input, maybe?

To me the expanders makes perfect sense. Not all euro crackheads care about getting a midi output. I do, so I got me an expander. Win-win. thumbs up
th0mas
Got my Pams last week, and it's been the heart of every patch I've made since. Love it.

I've got a feature request. I do however empathize that the extended settings can only get so long before it becomes overly cumbersome, so I get it if it's not going to happen.

Could we also be able to set a "step skip" and "step delay"?

step skip = only play the trigger once every N steps.
step delay = wait N steps before playing the trigger.

so, if I wanted to play a snare on 2 and 4 I would set a step delay of 1 and delay of 1.

Or if I wanted a quarter note trigger at the start of every fourth bar it would be "wait 12 notes, play the trigger, and then wait 15 after that"
step modifier = /1
step delay = 11
step skip = 15

Does everyone else solve this by setting a slower modifier, adjusting width and delay?
erstlaub
th0mas wrote:
Got my Pams last week, and it's been the heart of every patch I've made since. Love it.

I've got a feature request. I do however empathize that the extended settings can only get so long before it becomes overly cumbersome, so I get it if it's not going to happen.

Could we also be able to set a "step skip" and "step delay"?

step skip = only play the trigger once every N steps.
step delay = wait N steps before playing the trigger.

so, if I wanted to play a snare on 2 and 4 I would set a step delay of 1 and delay of 1.

Or if I wanted a quarter note trigger at the start of every fourth bar it would be "wait 12 notes, play the trigger, and then wait 15 after that"
step modifier = /1
step delay = 11
step skip = 15

Does everyone else solve this by setting a slower modifier, adjusting width and delay?


Yeah, all the parameters are already there to do exactly what you want. Sometimes it takes a wee bit more brain power to get there (until you've got it straight in your head) but between the division, phase, rotation and delay you can essentially drop triggers on whatever beat of a pattern you need.

For 2/4 snares for example, you'd just need to set your division/mult to half the channel driving your bassdrum and then shift the phase of it by 25 or 50% depending on where you wanted them to fall.

Don't forget also about the loop length/reset parameter.
Wiresandones
Although still love my original- new one sure looks amazing. Probably break down and pick one up soon.

I saw a few comments about how hard the red bg and black letters are hard to read (this is when a parameter is being edited) After watching the great Ben hex video, that seems to be the case.
I'm wondering if a future update option would be available to simply put a box around the parameter that is being edited (but leaving the letters in the same red and black bg.) That way there is an indication that editing is happening but make it clearer. I realize that my experience is only from a video of a display but had the idea so thought I'd ask.
Zymos
Hasn't been an issue for me, and my eyesight is not that great and the lighting in my room is not very bright....
bemushroomed
Wiresandones wrote:

I saw a few comments about how hard the red bg and black letters are hard to read (this is when a parameter is being edited) After watching the great Ben hex video, that seems to be the case.
I'm wondering if a future update option would be available to simply put a box around the parameter that is being edited (but leaving the letters in the same red and black bg.) That way there is an indication that editing is happening but make it clearer. I realize that my experience is only from a video of a display but had the idea so thought I'd ask.


That sounds like a pretty good idea, or even just a * to indicate that editing is going on would be better imo.

Again, my eye sight isn't perfect but it's also not so bad that i wear glasses unless i'm reading a book (screens are usually ok, even my tiny phone), text here is just too thin and smears with the red.
echopraxia
this module is so sick. cant wait to get this firmware update happening
suthnear
I am obviously missing something but because the multiplication and division occurs with relation to beats and not sixteenths, it doesn't seem to be possible to create clocks/lfos in odd multiples of sixteenths: e.g. 3/5/7/9.

Am I correct in thinking this?
erstlaub
suthnear wrote:
I am obviously missing something but because the multiplication and division occurs with relation to beats and not sixteenths, it doesn't seem to be possible to create clocks/lfos in odd multiples of sixteenths: e.g. 3/5/7/9.

Am I correct in thinking this?


Not at the module to check atm but isn't the loop/reset setting based on actual beats rather than divisions? Perhaps you can dial up some wrong numbers using that?
novim
Whoo! Mine's been stuck at Customs for a week It's peanut butter jelly time!
bemushroomed
novim wrote:
Whoo! Mine's been stuck at Customs for a week It's peanut butter jelly time!


I heard they're having a blast with it at the customs, they practically get nothing done It's peanut butter jelly time! Rockin' Banana! nanners
bemushroomed
This module can not be clocked by anything external it seems, I've tried both with my uMIDI and with Varigate 8+ neither of these are accepted, the display will say "unstable", it can be up to a 4 BPM difference. That's a bit of a bummer since i do use the uMIDI to be able to sync to Cubase..
erstlaub
bemushroomed wrote:
This module can not be clocked by anything external it seems, I've tried both with my uMIDI and with Varigate 8+ neither of these are accepted, the display will say "unstable", it can be up to a 4 BPM difference. That's a bit of a bummer since i do use the uMIDI to be able to sync to Cubase..


Mine is slaved to my BSP totally solidly and I've also had it running locked to Old Pam's too (via a TRS cable with 2 mono jacks on the end into the Clock and Run inputs). What do you have the module's receive PPQN set to?
bemushroomed
erstlaub wrote:
bemushroomed wrote:
This module can not be clocked by anything external it seems, I've tried both with my uMIDI and with Varigate 8+ neither of these are accepted, the display will say "unstable", it can be up to a 4 BPM difference. That's a bit of a bummer since i do use the uMIDI to be able to sync to Cubase..


Mine is slaved to my BSP totally solidly and I've also had it running locked to Old Pam's too (via a TRS cable with 2 mono jacks on the end into the Clock and Run inputs). What do you have the module's receive PPQN set to?


24 with Cubase / uMIDI and i believe it was 4 or 8 for Varigate which was compatible with Pam to get the correct BPM.

I also did an experiment with a pulse .wav as a clock through Cubase. While Varigate 8+ was able to be clocked perfectly from Cubase using this method, Pam was lagging behind and the two sounds (one bassdrum from modular, one bassdrum playing from Cubase, at the same time) was not in sync with Pam (most of the time anyways).
ALM
erstlaub wrote:
th0mas wrote:


Does everyone else solve this by setting a slower modifier, adjusting width and delay?


Yeah, all the parameters are already there to do exactly what you want. Sometimes it takes a wee bit more brain power to get there (until you've got it straight in your head) but between the division, phase, rotation and delay you can essentially drop triggers on whatever beat of a pattern you need.

For 2/4 snares for example, you'd just need to set your division/mult to half the channel driving your bassdrum and then shift the phase of it by 25 or 50% depending on where you wanted them to fall.

Don't forget also about the loop length/reset parameter.


Yep and simple Euclidian setups with rotation.
ALM
echox wrote:


Would be great to have a easier access to Un/Muting Channels. If the LEDs would be a toggle switch this would be great.



You know you can quickly mute/unmute an output by holding the program knob down and clicking start/stop whist on any of the channels editing screens right ?
ALM
bemushroomed wrote:
This module can not be clocked by anything external it seems, I've tried both with my uMIDI and with Varigate 8+ neither of these are accepted, the display will say "unstable", it can be up to a 4 BPM difference. That's a bit of a bummer since i do use the uMIDI to be able to sync to Cubase..


Is this with the beta firmware ? If so can you also try with release and see if any different ?

Your using 24 PPQN and a run signal from the umidi ? Have you other stuff synced OK to the umidi midi clock ?
toneburst
Probably a silly question, but I'm scratching my head trying to work out how to stop the module skipping steps.

It seems the extended RSkip parameter has a minimum value of 01, which skips one clock in every 100.

How to set this to 00? It seems to go from 01 to 100, when turning the encoder counter-clockwise.

a|x
ALM
toneburst wrote:
Probably a silly question, but I'm scratching my head trying to work out how to stop the module skipping steps.

It seems the extended RSkip parameter has a minimum value of 01, which skips one clock in every 100.

How to set this to 00? It seems to go from 01 to 100, when turning the encoder counter-clockwise.



Are you sure your not setting it to CV 01 ? There is 00 % ...
toneburst
Sorry, yeah, that's an RTFM- I was doing exactly that.
Thanks for the quick reply.

a|x
NeonCore
bemushroomed wrote:
This module can not be clocked by anything external it seems, I've tried both with my uMIDI and with Varigate 8+ neither of these are accepted, the display will say "unstable", it can be up to a 4 BPM difference. That's a bit of a bummer since i do use the uMIDI to be able to sync to Cubase..


Mine slaves from the uMIDI just fine. I use the run and 24ppq clock out of the uMidi with both Logic and Live with zero lag.
suthnear
erstlaub wrote:
suthnear wrote:
I am obviously missing something but because the multiplication and division occurs with relation to beats and not sixteenths, it doesn't seem to be possible to create clocks/lfos in odd multiples of sixteenths: e.g. 3/5/7/9.

Am I correct in thinking this?


Not at the module to check atm but isn't the loop/reset setting based on actual beats rather than divisions? Perhaps you can dial up some wrong numbers using that?


Possibly, but if loop is based on beats - i.e. fourths - then this won't help. Also, I am not sure that loop applies to the LFOs.

3/16ths is a *very* common ratio: it's the same as dotted eighths. So, is it possible to get a clock or an LFO based on this with PNW?
ALM
suthnear wrote:

3/16ths is a *very* common ratio: it's the same as dotted eighths. So, is it possible to get a clock or an LFO based on this with PNW?


Yes - x1.3 multiplier gives you a dotted eighth. Also see x1.5, x2.6, x5.3 (and similar divisions) give you more dotted and triplet like factors.
n0rd
ALM wrote:
Recitative wrote:
I suppose my math is wrong, I thought it would be:

X .75.
I would think 1.3 would be a quarter triplet?

But that would mean x2 would be X.5
Your essentially dividing by 1 for it to be a multiplier (i.e for above 1/.5 = x2)

Thus;
0.75= 3/4, 1/(3/4) = 4/3 = 1.33333 =~ 1.3
Quarter triplet is x1.5 (2/3..)

ALM wrote:
suthnear wrote:

3/16ths is a *very* common ratio: it's the same as dotted eighths. So, is it possible to get a clock or an LFO based on this with PNW?


Yes - x1.3 multiplier gives you a dotted eighth. Also see x1.5, x2.6, x5.3 (and similar divisions) give you more dotted and triplet like factors.


Am I the only one who doesn't like seeing "x1.3" denoting "dot"?

From wiki: (https://en.wikipedia.org/wiki/Dotted_note)
"A dotted note is a note with a small dot written after it. In modern practice the first dot increases the duration of the basic note by half of its original value."

So if the original value is 1, then 'dotted' would be described as "1.5".
And if the original value is 0.5, then 'dotted' would be "0.75".

So maybe what you have labelled as "x1.3" should be displayed as "3/4" or "0.75".
Just seems strange to label "a note and a half" with "x1.3". (Same for all the other 'x.3' or 'x.6' values etc)

Steve
ALM
n0rd wrote:

And if the original value is 0.5, then 'dotted' would be "0.75".

So maybe what you have labelled as "x1.3" should be displayed as "3/4" or "0.75".
Just seems strange to label "a note and a half" with "x1.3". (Same for all the other 'x.3' or 'x.6' values etc)



Quoting an older post in this thread on exact same thing;

ALM wrote:

But that would mean x2 would be X.5

Your essentially dividing by 1 for it to be a multiplier (i.e for above 1/.5 = x2)

Thus;

0.75= 3/4, 1/(3/4) = 4/3 = 1.33333 =~ 1.3

Quarter triplet is x1.5 (2/3..)
n0rd
A double speed clock is half the time (ie the math is "time divided by two" or "t/2") but it would be labelled '2' or 'x2' and not '0.5'.

Same for a 'dot'. It should also be labelled as such (1.5) and not 'x1.3' regardless if 1.333 is being used internally to calculate the time.

I've looked at many H/W and plugins and none that I can find ever state "1.3" when denoting a 'dot' or "note and a half". In fact, any time a x.3 or such is used it's to denote a triplet!

Steve
ALM
*sigh*

n0rd wrote:
A double speed clock is half the time (ie the math is "time divided by two" or "t/2") but it would be labelled '2' or 'x2' and not '0.5'.


Yes and by that same logic x1.3 in the context of the Pam UI its correct.

Pam is denoting a clock speed that goes at 1.3x the speed of the master clock.

The fact that it happens to 'fit' other musical naming conventions is irrelevant the context of Pam - its not denoting x4 a '16th' or x2 an '8th' ?
DanJGW
I received the new Pams today after being a massive fan of Dinky's and Akemies Taiko (along with Muskrat, my favourite percussion modules) and although I've only had a quick half hour I'm blown away with just how intuitive and easy to navigate it is. The 'slop' function is genius and can't wait to get balls deep in the rest of Pam.
toneburst
To answer my own question (now that I have one smile ), yes, it is possible, and a lot more, besides...

Great module. The option to have LFOs on all 8 outputs definitely takes it to another level of usefulness (and fun).

a|x
suthnear
ALM - thanks very much for that explanation. Of course 1.333 is the same as dotted eighths as it's 4 ticks in 3 bars (and similarly for 2.666 and 5.333). I was also thinking musically rather than mathematically...

But given the multiply and divide factors on display in both ben_hex and clock face modular's videos, it would appear that clocks of other odd numbers of sixteenths are not possible. Don't suppose there's any chance of adding some of these if the firmware ever gets updated again?
neilmcm1975
I am finding this impossible to update tried around 20 times now and ready to give up this what i have put in terminal and keep getting the same thing , installed the df util.pkg from the link in the thread , tried the home-brew site and still bashing my head .

this is what terminal says
Last login: Fri Sep 1 22:08:20 on ttys001
Mcmeechans-Mac:~ neilmcmeechan$ brew install dfu-util
-bash: brew: command not found
Mcmeechans-Mac:~ neilmcmeechan$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
==> This script will install:
/usr/local/bin/brew
/usr/local/share/doc/homebrew
/usr/local/share/man/man1/brew.1
 /usr/local/share/zsh/site-functions/_brew
/usr/local/etc/bash_completion.d/brew
 /usr/local/Homebrew
==> The following new directories will be created:
/usr/local/Cellar
/usr/local/Homebrew
/usr/local/Frameworks
 /usr/local/bin
/usr/local/etc
/usr/local/include
/usr/local/opt
/usr/local/sbin
 /usr/local/share
/usr/local/share/zsh
/usr/local/share/zsh/site-functions
 /usr/local/var

Press RETURN to continue or any other key to abort
Mcmeechans-Mac:~ neilmcmeechan$ brew install dfu-util
-bash: brew: command not found
Mcmeechans-Mac:~ neilmcmeechan$
devslashnull
neilmcm1975 wrote:
I am finding this impossible to update tried around 20 times now and ready to give up this what i have put in terminal and keep getting the same thing , installed the df util.pkg from the link in the thread , tried the home-brew site and still bashing my head .

this is what terminal says
Last login: Fri Sep 1 22:08:20 on ttys001
Mcmeechans-Mac:~ neilmcmeechan$ brew install dfu-util
-bash: brew: command not found
Mcmeechans-Mac:~ neilmcmeechan$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
==> This script will install:
/usr/local/bin/brew
/usr/local/share/doc/homebrew
/usr/local/share/man/man1/brew.1
 /usr/local/share/zsh/site-functions/_brew
/usr/local/etc/bash_completion.d/brew
 /usr/local/Homebrew
==> The following new directories will be created:
/usr/local/Cellar
/usr/local/Homebrew
/usr/local/Frameworks
 /usr/local/bin
/usr/local/etc
/usr/local/include
/usr/local/opt
/usr/local/sbin
 /usr/local/share
/usr/local/share/zsh
/usr/local/share/zsh/site-functions
 /usr/local/var

Press RETURN to continue or any other key to abort
Mcmeechans-Mac:~ neilmcmeechan$ brew install dfu-util
-bash: brew: command not found
Mcmeechans-Mac:~ neilmcmeechan$


did you actually press "RETURN" and complete the install of homebrew? If you did then you probably just need to add /usr/local to your path i.e "export PATH=$PATH:/usr/local/bin >> ~/.bash_profile" and logout/login etc.
neilmcm1975
yeah i pressed return and get this

==> /usr/bin/sudo /bin/mkdir -p /usr/local/Cellar /usr/local/Homebrew /usr/local/Frameworks /usr/local/bin  /usr/local/etc /usr/local/include /usr/local/opt /usr/local/sbin /usr/local/share  /usr/local/share/zsh /usr/local/share/zsh/site-functions /usr/local/var
Password:
erstlaub
Hi Neil,

I had some difficulty a while back getting terminal to work for me (down to me not really understanding lots about how it works).

https://www.muffwiggler.com/forum/viewtopic.php?p=2518038#2518038

Have a squatch at that post and see if anything helps.

There's an updater app too (can no longer find the link in the thread/alm site so will DM you).
bravedog
I've been through the manual and 1st 7 pages of this thread and am not sure if this version still has CV in option to control tempo! The only mention in the manual I find is "Voltage and direct control of clock stop/start, reset and rate" which seems to indicate yes, - but then in the CV assign section it nowhere mentions assigning to tempo but only to the list of parameters which in the manual above that don't include tempo. So I THINK it still does this and the manual just assumes of course, but otoh maybe you've removed this option for greater assign flexibility with the other parameters? I use this on almost every patch but no-one else seems to mention it! Clarification would be most helpful! thx
soundslikejoe
Couldn't you just send Square Wave LFO into the CLK input (and then manual or CV control the LFO frequency) for CV control over tempo? No?
bravedog
yes there are workarounds, such as the one you suggest, requiring more modules, but... does your answer mean there is NOT any longer direct CV control option of tempo???
dumbledog
Per the manual:

External Clock Control.
Pamela can be driven by, and thus sync to, an external clock. This could be something simple like square wave LFO or something slightly more complex like a Din Sync signal from external hardware patched into the ‘Clk’ and run inputs. You can also control the tempo directly with just a voltage level.

...

To change these settings - select the top level BPM clock screen and then press and long hold the program knob for just over 1 second. The ‘external’ Clock sub menu will be displayed. From this sub menu you can change both the expected PPQN value or assign it to ‘CV” where a voltage level (Patch to to CV1) controls tempo.
atimbral
bravedog wrote:
yes there are workarounds, such as the one you suggest, requiring more modules, but... does your answer mean there is NOT any longer direct CV control option of tempo???

Yes, there is definitely the ability for direct CV control (manual pg 14), but rather than absolute bpm, it appears to be control of the multiplier. I'm not certain of that, but I do know that I haven't found it possible to do small bpm changes via CV; it always seems to jump 10 or 20 or whatever big amount of bpm, even with the larger -5 to +5 swing of CV2.

Anybody know a way to do finer grained bpm changes with CV? (and of course you can use an external clock or LFO, but it would be more convenient to do this exclusively in Pams) Maybe possible in a future firmware update?
erstlaub
atimbral wrote:
bravedog wrote:
yes there are workarounds, such as the one you suggest, requiring more modules, but... does your answer mean there is NOT any longer direct CV control option of tempo???

Yes, there is definitely the ability for direct CV control (manual pg 14), but rather than absolute bpm, it appears to be control of the multiplier. I'm not certain of that, but I do know that I haven't found it possible to do small bpm changes via CV; it always seems to jump 10 or 20 or whatever big amount of bpm, even with the larger -5 to +5 swing of CV2.

Anybody know a way to do finer grained bpm changes with CV? (and of course you can use an external clock or LFO, but it would be more convenient to do this exclusively in Pams) Maybe possible in a future firmware update?


Are you attenuating the incoming cv? Remember that whenever you set any parameter at any tier to be controlled by cv1 or 2, you can long press/hold with the cv1/2 option highlighted and then access further offset and attenuation options.

You can dial in attenuation and offset at either (or even both) end - at the input via the top level cv menu, or the destination via the long press depending on options and use case.
atimbral
erstlaub wrote:
atimbral wrote:
bravedog wrote:
yes there are workarounds, such as the one you suggest, requiring more modules, but... does your answer mean there is NOT any longer direct CV control option of tempo???

Yes, there is definitely the ability for direct CV control (manual pg 14), but rather than absolute bpm, it appears to be control of the multiplier. I'm not certain of that, but I do know that I haven't found it possible to do small bpm changes via CV; it always seems to jump 10 or 20 or whatever big amount of bpm, even with the larger -5 to +5 swing of CV2.

Anybody know a way to do finer grained bpm changes with CV? (and of course you can use an external clock or LFO, but it would be more convenient to do this exclusively in Pams) Maybe possible in a future firmware update?

Are you attenuating the incoming cv? Remember that whenever you set any parameter at any tier to be controlled by cv1 or 2, you can long press/hold with the cv1/2 option highlighted and then access further offset and attenuation options.

You can dial in attenuation and offset at either (or even both) end - at the input via the top level cv menu, or the destination via the long press depending on options and use case.

Yes, using both attenuation and offset. That's why I speculate that it seems to be CVing the multiplier rather than actual bpm. ALM?
bravedog
atimbral wrote:

Yes, there is definitely the ability for direct CV control (manual pg 14), but rather than absolute bpm, it appears to be control of the multiplier.


atimbral, I know CV as one of the parameters can control multiplier but this isn't what I want and as you say is far from smooth... but dumbledog above says "From this sub menu you can change both the expected PPQN value or assign it to ‘CV” where a voltage level (Patch to to CV1) controls tempo" which DOES sound like what I want... but maybe not and he's just saying the CV in then goes through the division settings which would be far from smooth and really isn't CV control of tempo in the sense I mean, which IS how the Tempo input on my [the old] PW works...then you're worrying me since you seem to have a unit which doesn't assign CV to directly control tempos? [I have old PW but am considering upgrade and won't if no longer direct tempo control by CV, not thru workaround or multiplier only] thx
atimbral
bravedog wrote:
atimbral wrote:

Yes, there is definitely the ability for direct CV control (manual pg 14), but rather than absolute bpm, it appears to be control of the multiplier.


atimbral, I know CV as one of the parameters can control multiplier but this isn't what I want and as you say is far from smooth... but dumbledog above says "From this sub menu you can change both the expected PPQN value or assign it to ‘CV” where a voltage level (Patch to to CV1) controls tempo" which DOES sound like what I want... but you're worrying me since you seem to have a unit which doesn't assign CV to directly control tempo as dumbledog says? Can anyone with a unit verify dumbledog's description? [I have old PW but am considering upgrade and won't if no longer direct tempo control by CV, not thru workaround or multiplier only] thx

hmmm ... Well, to give you a more definite answer, I'll have to put my Pams (old & new) back in my rack; I've been playing with the Temps Utile the past few days. Maybe I can get around to doing that today. I do seem to remember though that the old Pams did have a finer grained CV of tempo. I'll check it out.
dumbledog
bravedog wrote:

atimbral, I know CV as one of the parameters can control multiplier but this isn't what I want and as you say is far from smooth... but dumbledog above says "From this sub menu you can change both the expected PPQN value or assign it to ‘CV” where a voltage level (Patch to to CV1) controls tempo" which DOES sound like what I want... but maybe not and he's just saying the CV in then goes through the division settings which would be far from smooth and really isn't CV control of tempo in the sense I mean


After some experimenting I think I get what you're saying. There's definitely some sort of quantization going on when you CV control the clock. I'm feeding CV1 a constant voltage, have Channel 1 set to 48x and listening to that directly. As I lower the voltage, the frequency of Ch1 drops down in steps.

Looks like it rounds off to the nearest multiple of 6. I can make it 120 or 126BPM, but not 123.
soundslikejoe
That's might be helpful if you're doing even metric divisions through CV control. Would make dialing in the CV to change from 1/2 to double or some even metric variation much easier than a standard continuous voltage
atimbral
OK, I put both the old and new Pams together to compare how bpm tracks CV.

New Pams will only track in very large increments if you CV the modifier, i.e. the multiplier. Dumbledog is correct in the best way to CV bpm. (Thanks!). You need to set the PPQN to CV and use CV1. Then 0 - 5V gives you 10 - 250 bpm, in 6 bpm increments.

Old Pams is finer-grained; 0 - 5V gives 25 - 273 bpm in 1 bpm increments. So if that's really important then you'll want to keep it.

Maybe ALM can enlighten us further on the design choices made!
bravedog
[deleted, updated with better info in a later post]
atimbral
Also, after using old Pams for awhile, I was surprised at how much I've missed old Pams nice bright display, always available at a glance. With new Pams the screen saver dims it, so when you want a quick look at bpm, you have to click or turn the encoder. Even then, it's not very bright; some of the modifiers especially are kind of hard to read.

So many nice features though in new Pams; it's not fair to complain about a small detail.
EPTC
atimbral wrote:
With new Pams the screen saver dims it, so when you want a quick look at bpm, you have to click or turn the encoder.


I'm wondering (haven't checked) if the screen saver mode is a simple y/n variable somewhere in the menu. It's not in the original firmware, so you could conceivably get it back to a constant screen brightness if you reset things back to version 192, or previous: http://busycircuits.com/firmware/alm017/ChangeLog.txt - Granted you'd lose a few enhancements but maybe it'd be worth it. Maybe on/off could be added to a future update.

I had the original version 177 installed until yesterday, when the weekend gave me some time to update it. I don't know what took me so long - the mutes and new variables in version 197 beta are terrific! I know mutes have been around since version 189, but new to me, and wow are they incredibly nicely implemented. Those mutes!

Just want to confirm with others that if you have Homebrew installed on your mac the updating process for Pam's takes under twelve seconds with a single command. Thank you ALM! Love it.
ALM
atimbral wrote:


Maybe ALM can enlighten us further on the design choices made!


Sounds like more a bug than a design choice cry I will have a look at improving so more like original Pam.

Would still advise doing this kind of thing via voltage controlled LFO (or even low freq VCO). It may require an extra module but it will free up a CV input and give you much finer grained control over tempo (even with CV control as original Pam).
ALM
suthnear wrote:

But given the multiply and divide factors on display in both ben_hex and clock face modular's videos, it would appear that clocks of other odd numbers of sixteenths are not possible. Don't suppose there's any chance of adding some of these if the firmware ever gets updated again?


What would these multiples these would be in Pam speak ?
soundslikejoe
Pam should be able to multiply and divide using irrational numbers like Pi --- and then it should be able to create generative music without the use of any additional modules.
hihi

Square LFO to Clk input FTW!
Nino
Will Pexp-1 also transmit MMC messages or just the tempo?
Or: Can i sync AND start/stop a DAW running using Pexp-1?
jwise
soundslikejoe wrote:
Pam should be able to multiply and divide using irrational numbers like Pi --- and then it should be able to create generative music without the use of any additional modules.


This would be AMAZING! +1 thumbs up we're not worthy It's peanut butter jelly time!
ALM
Nino wrote:
Will Pexp-1 also transmit MMC messages or just the tempo?


Just Tempo, Start and Stop messages.

Nino wrote:

Or: Can i sync AND start/stop a DAW running using Pexp-1?


Yes assuming DAW can (and is setup too) respond to Midi clock.
Nino
Thats just what i need, thanks for the quick response. nanners
atimbral
ALM wrote:

Sounds like more a bug than a design choice cry I will have a look at improving so more like original Pam.

Yes! That would be great if possible.

There is one other important difference between old/new Pams bpm CV that maybe you could look into: In new Pams, when a CV change to a new bpm is made, the previous bpm is still active for 1 more cycle before it actually changes to the new bpm. This is especially noticeable when going from a low bpm (say 10) to a higher one, resulting in a significant lag before the new bpm kicks in. Old Pams doesn't do this; the change is immediate.

Thanks!
BaloErets
As a long time user of a Tempi, and a 4 day user of the New Pams, I have to say that this module is fantastic! The menu is awesome which makes the UX amazing. Software routing of CV destination is very cool. And tonight, I had it running as an 8 oscillator drone with CV over wavetables, Phase Modulation, and even some nifty bit-crushing using the Euclidian Steps and Triggers. Will have to make a video of that!

But above all, I gotta say that a Tempi and Pams can reside in a system so harmoniously. They play really well with eachother, and work extremely complementary.

Pam's new workout has raised the bar on mkII iterations, as far as I'm concerned

applause we're not worthy thumbs up
bravedog
ALM wrote regarding CV control of tempo:

ALM wrote:

Would still advise doing this kind of thing via voltage controlled LFO (or even low freq VCO). It may require an extra module but it will free up a CV input and give you much finer grained control over tempo (even with CV control as original Pam).


I'm not sure but think you mean, run an LFO into Pam clock input, and use CV to control the LFO?

This works fully if the 0-5V CV range input to the LFO corresponds to an LFO output of Pam's 10 [or 25 for old]-300 BPM range, ie 0V --> 10 BPM and 5V --> 300 BPM from the LFO. Assuming smooth response curve to rate change and no delay at Pam clock input. Otherwise not.

Hm, if LFO CV response is standard 1V/octave [doubling cycle rate each 1V], if LFO rate for 5V in is set with offset [not attenuator, which would destroy the 1V/octave response] to 300 BPM, Pam's maximum, at 0V the LFO should output 9.375 BPM, not far off Pam's minimum, so this isn't such a bad approximation and would lose only a bit of response near 0V. If LFO includes offset [not attenuator!] with CV in this indeed works with one additional module, otherwise use of an external offset isn't much problem.

Can anyone confirm if New Pam's clock input indeed has smooth rapid response to rapidly changing input rate at its full BPM range? If so yes this could work for me and make an upgrade worthwhile.
-------------------
BTW ALM in spite of what in my case is perhaps a serious loss of functionality in New Pam, Pam is a great unit! I use it in almost every patch. Thx
behndy
can't remember if someone asked this, but can one control the division of an output through CV?

it is FUN wubbling back and forth through the divisions for stuttery beat goodness.
Nino
Of course you can nanners
dumbledog
Is there a way to do that through specific divisions though? I love mixing whole/quarter/eighth/sixteenth notes in my stuff but don't necessarily want triplets or dotted notes in there.
toneburst
You can set a minimum and maximum value that the incoming CV is mapped to, I believe. I don't think you can prevent incoming CV selecting a particular division within that range, though. You'll just have to make sure to only send the CV voltage required to select the division you want.

a|x
joskery
I tried looking it up in the manual, but:

Is it possible to save multiple configurations of ALL outputs – as in, have presets where you can change what all the outputs spit out in one go?

Thanks!
ALM
joskery wrote:
I tried looking it up in the manual, but:

Is it possible to save multiple configurations of ALL outputs – as in, have presets where you can change what all the outputs spit out in one go?

Thanks!


See pg 13 - 'Loading, Saving and Reseting ALL 8 outputs at once'. Is that it ?
joskery
ALM wrote:
joskery wrote:
I tried looking it up in the manual, but:

Is it possible to save multiple configurations of ALL outputs – as in, have presets where you can change what all the outputs spit out in one go?

Thanks!


See pg 13 - 'Loading, Saving and Reseting ALL 8 outputs at once'. Is that it ?


Yep, that would be it, however I'm a bit unclear about the following:

"A full bank (i.e 8 grouped by letter) of outputs can be loaded, saved or reset via
the BPM sub menu."

the (i.e) part can, to my eye, be saying that one full bank is 8 outputs, and each output has a letter, or that it's possible to save 8 banks of outputs, and each bank has a letter from a- ... whatever the eighth alphabet is. smile

Thanks!
ALM
Each bank is represented by a letter and a bank contains a full 'snapshot' of all 8 outputs referenced by the letter and the output number. So within Bank A, Output 1 is A1, Output 2 A2 etc... 8 is A8. Make sense ?
joskery
Okay, so, in other words, I can save 8 full snapshots – thanks, that's what I hoped to hear!

Call me heretic, but I just love 'presets' in modular MY ASS IS BLEEDING
ALM
joskery wrote:
Okay, so, in other words, I can save 8 full snapshots


26 full snapshots (a-z)
joskery
Okay. The part in the manual doesn't make sense to me even now that I know what the deal is. But that's secondary smile Thanks so much for the help, Mr. Busy Circuits!
propertyof
i missed the latest firmware update info. does firmware 197 has a final version released now?
ALM
propertyof wrote:
i missed the latest firmware update info. does firmware 197 has a final version released now?


Not yet but I just uploaded a 'BETA-2' which should improve the CV control of BPM.

Id really like to get some more feedback before I spin a 198 release. Please do let me know if you are using the beta and have no issue (or not!).
batch
After several years of trying to hold out have finally given in and bought Pam's New Workout and the Exp 2. They are arriving today and having watched Ben Hex's overview am kicking myself for not jumping onboard sooner.

Anyway, here is the question (and please note, module is not in hand yet). When setting modifiers for gate length or phase it's done in percent of step. Are there any options for decimals or fractions that would be more musically related?

What I really want to be able to do is have a modifier that could be shifted by 7/8 (87.5%) to create a gate that was as follows:

_ _ _ _ | _ _ _ _ | _ _ _ _ | _ _ * *

Where each "_" is a beat at 0V and a "*" is at 5V.

Am thinking that /16 and phase shifting by 87% would get close but it will be slightly off.

Reason for doing this is to use a switch to create a drum fill on the last two beats of every 4 bars.

If this isn't possible today, would it be possible to add a few musically related fractions to the percentages? 1/3rds, 1/8ths, 1/16ths? Or figure out a way to have 1 or 2 decimals?
ALM
Armstrb, You could do it with an euclidean setup I think; /16 divider, 8 steps, 1 trig and rotate.
batch
Nice! Hadn't thought of that, will give it a shot when it arrives.

Very excited!

Thanks for quick response
jhsa
ALM wrote:
Id really like to get some more feedback before I spin a 198 release. Please do let me know if you are using the beta and have no issue (or not!).

Installed a moment ago and gave a quick spin. First try with CV control for BPM seemed to work ok with slow triangle lfo (and faster one). Other functions I used also worked like previously, not very deep test tho. thumbs up
brianobush
I understand the basic Estep and Etrig for Euclidean patterns, but the Erot is a bit confusing to me. If we have Estep at 5, Etrig at 2, how would a value of 2 for Erot change the sequence?
soundslikejoe
What this guy said....
|
|
|
v
BaloErets
In that scenario, viewing "\" as a step and "*" as a trigger, a rotation of 0 would be
*\\*\
A rotation of 1 would be
\*\\*
And therefore a rotation of 2 would be
*\*\\

Hope that helps. Can't promise that it's exactly the hits are in their right spots, but it should explain how the rotation works.
brianobush
Thank you both for a good explanation.
nolongerhuman
Does anyone know offhand what type of knob is on Pamelas New Workout? Doesn't look like a Rogan or a Selco exactly, but close to both.
exper
nolongerhuman wrote:
Does anyone know offhand what type of knob is on Pamelas New Workout? Doesn't look like a Rogan or a Selco exactly, but close to both.


Not certain, but I'm pretty sure its a Selco w/nutcover and the cap is just the plain, encoder variety. It's a size somewhere between the 11mm and 15mm selco knobs.

If it's another brand I'd like to know, because they might beeasier to get as replacements for other modules. I keep putting off ordering Selcos from Thonk...
atimbral
ALM wrote:
propertyof wrote:
i missed the latest firmware update info. does firmware 197 has a final version released now?


Not yet but I just uploaded a 'BETA-2' which should improve the CV control of BPM.

Id really like to get some more feedback before I spin a 198 release. Please do let me know if you are using the beta and have no issue (or not!).

Tried the BETA-2 firmware, and yes, the CV control is nice and smooth now, changing in 1 bpm increments through the whole range, 10 to 296. Thanks!

However, it still has the same problem I reported earlier: It now takes 2 clock cycles for the new clock rate to take effect. e.g. If I'm at 10 bpm and CV change to 296 bpm, 2 more clocks at 10 bpm will play before playing at 296.

If I remember right, it seems that the earlier rev. 197 did the same thing but only played 1 clock at the old bpm before changing to the new bpm.

The original Pam's did this correctly. The new clock speed begins immediately when the CV change is made.
ALM
atimbral wrote:

Tried the BETA-2 firmware, and yes, the CV control is nice and smooth now, changing in 1 bpm increments through the whole range, 10 to 296. Thanks!


hyper hyper hyper hyper

atimbral wrote:

However, it still has the same problem I reported earlier: It now takes 2 clock cycles for the new clock rate to take effect. e.g. If I'm at 10 bpm and CV change to 296 bpm, 2 more clocks at 10 bpm will play before playing at 296.


Do you see it on small (<10bpm) changes too ? May well have to live with this.
atimbral
ALM wrote:
Do you see it on small (<10bpm) changes too ? May well have to live with this.

Yes. Any CV change to clock speed has a time lag of 2 clock cycles.

I guess the clearest way to put it is to ask a question: Why doesn't a CV change cause an immediate change to the clock speed in new Pam's like it does in old Pam's?

I use this a lot with a touch pad like Soundmachines LS1 or Make Noise Pressure Points/Brains. Touching the pad sends a gate to Pam's Run input and a voltage to the CV input. This makes it easy to control the pacing of a musical gesture or phrase in an expressive way, from single notes at slower speeds to bursts or flurries at the quickest speeds.

If this can't be fixed, then I'll just have to use both old & new Pam's! nanners
ALM
atimbral wrote:

I guess the clearest way to put it is to ask a question: Why doesn't a CV change cause an immediate change to the clock speed in new Pam's like it does in old Pam's?


Well it should do :( but the code is completely different to original Pam. Im investigating as to why its happening but I wasn't seeing it on small changes (though I only quickly checked). Knowing how your using it is helpful - thanks. Maybe the lag is connected to the run input. Will further investigate..
behndy
i haven't updated since i got the New Pam's about....... 2 months ago? i think?

but i just started having the mismatched tempo thing people were complaining about earlier. i'm using Pam's to clock everything in my system, and it is sending out a tiny bit faster than the DAW i record into thinks it should be.

sending out 30 bpm from Pam's, everything (4 Vox, Clouds, Batumi, Basimilus, Transient, BitBox, uBraids) is staying matched up in time to each other, no drift. but when i record into Cubase i get everything starting at the 1, then a tad in front of the one, then a little more, repeat.

what am i doing wrong? will updating her help?

thanks!
ALM
behndy, you have a few options;

1. Physically sync your DAW to Pam via MIDI or Audio pulses etc so BPM's precisely match.

2. Uses your DAWS timestretch / import tools to better fit the recording to the DAWs grid.

3. Recalibrate Pams internal clock so that its representation of X BPM better matches your DAWs representation of X BPM (see Pam manual for details).
Shledge
behndy wrote:
i haven't updated since i got the New Pam's about....... 2 months ago? i think?

but i just started having the mismatched tempo thing people were complaining about earlier. i'm using Pam's to clock everything in my system, and it is sending out a tiny bit faster than the DAW i record into thinks it should be.

sending out 30 bpm from Pam's, everything (4 Vox, Clouds, Batumi, Basimilus, Transient, BitBox, uBraids) is staying matched up in time to each other, no drift. but when i record into Cubase i get everything starting at the 1, then a tad in front of the one, then a little more, repeat.

what am i doing wrong? will updating her help?

thanks!


How is it being slaved?
oinkbanana
ALM wrote:
3. Recalibrate Pams internal clock so that its representation of X BPM better matches your DAWs representation of X BPM (see Pam manual for details).

is it normal that a calibration at 50bpm be different than a calibration at 100bpm, or 150bpm? If the bpm is a factor of the sample rate, shouldn't the DAW representation be 100% accurate? what sample rate is PAM running at?
captainhooke
ALM wrote:
behndy, you have a few options;

1. Physically sync your DAW to Pam via MIDI or Audio pulses etc so BPM's precisely match.

2. Uses your DAWS timestretch / import tools to better fit the recording to the DAWs grid.

3. Recalibrate Pams internal clock so that its representation of X BPM better matches your DAWs representation of X BPM (see Pam manual for details).


How solid is it if I were to use PAM as master clock for my DAW and external gear, will this sync up everything tightly? Have a lot of clocks (Ableton, Beatstep Pro, SQ-1 and more) which I want perfectly synced. Always struggling with keeping them all going solid. Considering using PAM as a master with the extensions if it could offer solid clock to all smile
behndy
Shledge wrote:
behndy wrote:
blah blah timing issues etc


How is it being slaved?


she is NOT. Pam's is the clock for everything eurorack.

ALM wrote:
behndy, you have a few options;

1. Physically sync your DAW to Pam via MIDI or Audio pulses etc so BPM's precisely match.

2. Uses your DAWS timestretch / import tools to better fit the recording to the DAWs grid.

3. Recalibrate Pams internal clock so that its representation of X BPM better matches your DAWs representation of X BPM (see Pam manual for details).


hurm. i guess 1 would be easiest, 3 makes more sense though, since recording other hardware's audio into my computer has never been problematic.

the weird thing to me is this is the first time this had happened. and i've recorded euro ramble bits at least a few hundred times with the same setup, Pam's clocking my entire modular system, and never had it not be rock solid in sync.

headed to work now, but when i get home i'll try some other hardware with its own clock that has stayed in sync to make sure it's external, not something with the computer.

but is there something that would crop up after working fine? does she need to be recalibrated occasionally?

thanks for the help!
ALM
behndy wrote:
does she need to be recalibrated occasionally?


Maybe ! Thats why calibration controls are present in anything right ?

Likely only needs a tiny tweak.

But if you are serious about it being 100% in time with your DAW then please physically sync it hyper hyper hyper
Sleipnir
atimbral wrote:
ALM wrote:
Do you see it on small (<10bpm) changes too ? May well have to live with this.

Yes. Any CV change to clock speed has a time lag of 2 clock cycles.

Do you get the lag when changing divisions as well? Might be a workaround for now.
Shledge
behndy wrote:
she is NOT. Pam's is the clock for everything eurorack.


So your DAW is slaved to it?

You're going to have sync issues regardless if Pams or the DAW are not slaved. They need the exact clock or the sync will drift.
behndy
Shledge wrote:
behndy wrote:
she is NOT. Pam's is the clock for everything eurorack.


So your DAW is slaved to it?

You're going to have sync issues regardless if Pams or the DAW are not slaved. They need the exact clock or the sync will drift.


i don't have my DAW slaved. i have the Pam's Expander that has MIDI and DIN out, but i have always run clocks into different modules, then recorded the audio out into my DAW, and always been sync'd, no slide. this is the first time it got buggery'boo'd.

if it is the Pam's (still going to record different Box Dependant Tempo things to make sure it's not the computer), i'd rather try to calibrate it so it's in sync again.
Shledge
...or you could just slave it and save the hassle. No slaving = you're going to get drift. It's like expecting two VCOs to be in perfect tuning.

This happens with a lot of my gear, even if they all show the same BPM. Slaving them is the only way to keep them in proper sync. As for my PNW, I slave mine via a BSP, with MIDI clock and it's rock solid.
droningspaghettimonster
one question- do the lfos lag/hick while the module receives clock like batumi and tides or does it learn the clock and not hick like audio damage sequencer 1 since it has a run input too? Engine has taken over seq 1 and i only use it for gates and lfos... And those lfos are reliable, always. But i guess the new pamela module should be the perfect replacement for seq 1 and than some.... hmmm.....
batch
ALM wrote:
Armstrb, You could do it with an euclidean setup I think; /16 divider, 8 steps, 1 trig and rotate.


Got the module. Love it awesome!!!

/4, 8 steps, 1 Trig and rotate gets me there.
dp
Loving Pams,
I know someone else mentioned it before but I couldn't see an answer
Can the display be made any brighter? and can the screen dimmer mode be switched off?
cptnal
Fun with random - Turn the slop WAY up on a few channels of gates. Adjust tempo/division of each to taste. Combine in a mixer/ninja star and use at the destination of your choice. screaming goo yo
resynthesize
I think I found a bug with 197-beta1. To reproduce:

1) Clock pam externally
2) Set RUN? to rotate row
3) Insert a regularly occurring trigger into the run jack
4) Stop external clock.

PAM will stop for a second, and then start running by itself again. It won't respond to external clock again until you set RUN? back to "reset" and stop/start again.

Another thing I've noticed is that the the select RUN? option is immediately effective while still in the run menu as incoming triggers occur. This has bitten me a few times when I have a fast trigger patched and scroll by the "load bank" option, causing me to lose all of my settings. Maybe an encoder push could be required before the selected option takes effect.
resynthesize
oh also, +1 on either disabling or providing an option to disable the screen saver dimming.
c_code
holy red stripe, this module is a feature fest SlayerBadger!
pineal
I sold my Pamela's for the New Pamela. Now always I see a message "unstable clock" in the BMP menù. Either using daw sync, or slaved to a Pioneer Toraiz and even with my Elektron machinedrum. Now, with the oldest I never had sync problem, now I read the wrong BPM, alway 1 less of the correct one (ie 119 instead of 120, 135 intead 136). I tried with firmware 196 and 197 beta-2.
Any suggest please? thank you
glassofwater
droningsphagettimonster wrote:
one question- do the lfos lag/hick while the module receives clock like batumi and tides or does it learn the clock and not hick like audio damage sequencer 1 since it has a run input too? Engine has taken over seq 1 and i only use it for gates and lfos... And those lfos are reliable, always. But i guess the new pamela module should be the perfect replacement for seq 1 and than some.... hmmm.....


Get the Pexp-1 expander. Easiest way of syncing it with the Engine. ^_^

Eurorack: solve it by spending more money.
ALM
pineal wrote:
I sold my Pamela's for the New Pamela. Now always I see a message "unstable clock" in the BMP menù. Either using daw sync, or slaved to a Pioneer Toraiz and even with my Elektron machinedrum. Now, with the oldest I never had sync problem, now I read the wrong BPM, alway 1 less of the correct one (ie 119 instead of 120, 135 intead 136). I tried with firmware 196 and 197 beta-2.
Any suggest please? thank you


What PPQN are you using for the sync ? Does it sound in sync ?

See manual, this thread etc for re-calibrating the Pam internal clock to have its representation of X BPM match other devices representation.
pineal
I use 24 PPQN. Does it sound in sync ? No.
I tried to re-calibrate the Pam internal clock.. using value of 16, 50, 99 etc.. It doen't working. I read in the manual that Pamela's clock is EXTREMELY stable.. how to sync to an audio track based clock?
ALM
pineal wrote:
I use 24 PPQN. Does it sound in sync ? No.


And old Pam synced fine ?
soundslikejoe
pineal wrote:
I sold my Pamela's for the New Pamela. Now always I see a message "unstable clock" in the BMP menù. Either using daw sync, or slaved to a Pioneer Toraiz and even with my Elektron machinedrum. Now, with the oldest I never had sync problem, now I read the wrong BPM, alway 1 less of the correct one (ie 119 instead of 120, 135 intead 136). I tried with firmware 196 and 197 beta-2.
Any suggest please? thank you


I found that sync from DAW via ES3 and Sleepers Sync requires a negative value for the "Clock Low" --- but it syncs tight every time. Also get good sync when using Yarns from MIDI input to PNW.

What device are you using for MIDI to analog clock?
pineal
And old Pam synced fine ?[/quote]

Yes, using Hexinverter MIDI2CVC syncedfine with old Pamela
ALM
pineal wrote:


Yes, using Hexinverter MIDI2CVC syncedfine with old Pamela


And what happens with MIDI2CVC and new Pam ?

Everything else - DAW, h/w etc is the same ?
pineal
And what happens with MIDI2CVC and new Pam ?

Everything else - DAW, h/w etc is the same ?[/quote

Yes my setup it's the name
ALM
pineal wrote:
And what happens with MIDI2CVC and new Pam ?

Everything else - DAW, h/w etc is the same ?[/quote

Yes my setup it's the name


OK very strange esp if it worked with original Pam.

Could you shoot help <at> busycircuits.com a mail detailing your setup and please if possible attached a stereo wav with one channel the clock from MIDI2CVC going into Pam and the other channel a x4 clock coming out of Pam ? That'll really help me figure out whats going on. Also please reset the x4 channel before recording (so no extra settings) and let me know the firmware version. Thanks!
monads
pineal wrote:
Yes, using Hexinverter MIDI2CVC syncedfine with old Pamela


Did you try the below??? I never got around to confirming my Midi2CV settings questioned about....but worth a quick try for you.


monads wrote:
Since we're talking about clocking from other sources....I tested clocking from HexInverter Midi2CV (sync output 24ppqn) with PNW set at 1ppqn and no issues. If you set PNW anything higher than 1ppqn it wont sync properly.

It takes about a few secs to sync up after pressing play from the DAW so you'll have to adjust the sequence if you want everything aligned after recording. Not sure this is the best way but just wanted to share. This option also allows for Tempo control from the DAW (speed up, slow down, etc.).
pineal
[quote="monads"]
pineal wrote:
Yes, using Hexinverter MIDI2CVC syncedfine with old Pamela


Did you try the below??? I never got around to confirming my Midi2CV settings questioned about....but worth a quick try for you.


[quote="monads"]Since we're talking about clocking from other sources....I tested clocking from HexInverter Midi2CV (sync output 24ppqn) with PNW set at 1ppqn and no issues. If you set PNW anything higher than 1ppqn it wont sync properly.

hi, yes I've tried at 1ppqn..at 2, 4, 8 ,16 and 24.. same unstable clock. But from Logic's sequencer it's in sync, despite Pamela's shows "untable clock" at 24 ppqn, and change beetween 119/120 at 24ppqn. I'll post a short video about it
ALM
pineal wrote:


hi, yes I've tried at 1ppqn..at 2, 4, 8 ,16 and 24.. same unstable clock. But from Logic's sequencer it's in sync, despite Pamela's shows "untable clock" at 24 ppqn, and change beetween 119/120 at 24ppqn. I'll post a short video about it


It would be much more useful if you could email me a recording of the Midi2CV clock going into Pam on one channel and whats coming out on the other!
Norgatron
Just wanted to say that I woke up yesterday looking for a divider to set the Sync input on my Jellyfish V2 delay from the BSP Clock Out and went to bed with a Pamela's New! Workout on order from Post Modular. eek!

It was a bit over my budget for this month but once I understood what it was capable of I had to have it. The fact that it has great aesthetics and is British designed and built just tipped me over the edge, and by the time I got to the end of Ben's video it was ordered. w00t

As well as driving the Jellyfish's delay syncI will probably use it across my new live rig as a source of LFOs and synced modulations in general, a buddy for Kinks and Function ands loads of stuff I haven't thought of yet. I'm pretty excited.
cptnal
Norgatron wrote:
Just wanted to say that I woke up yesterday looking for a divider to set the Sync input on my Jellyfish V2 delay from the BSP Clock Out and went to bed with a Pamela's New! Workout on order from Post Modular. eek!

It was a bit over my budget for this month but once I understood what it was capable of I had to have it. The fact that it has great aesthetics and is British designed and built just tipped me over the edge, and by the time I got to the end of Ben's video it was ordered. w00t

As well as driving the Jellyfish's delay syncI will probably use it across my new live rig as a source of LFOs and synced modulations in general, a buddy for Kinks and Function ands loads of stuff I haven't thought of yet. I'm pretty excited.


You won't regret it This is fun!

And remember that, despite its being at heart a clocking module, it's also great for random.
erstlaub
Norgatron wrote:
Just wanted to say that I woke up yesterday looking for a divider to set the Sync input on my Jellyfish V2 delay from the BSP Clock Out and went to bed with a Pamela's New! Workout on order from Post Modular. eek!

It was a bit over my budget for this month but once I understood what it was capable of I had to have it. The fact that it has great aesthetics and is British designed and built just tipped me over the edge, and by the time I got to the end of Ben's video it was ordered. w00t

As well as driving the Jellyfish's delay syncI will probably use it across my new live rig as a source of LFOs and synced modulations in general, a buddy for Kinks and Function ands loads of stuff I haven't thought of yet. I'm pretty excited.


I'd heartily recommend knocking up the cable to slave new (or old) Pam's to the BSP too. It's just a TRS cable with 3.5mm mono jacks on the end, one carries the clock, the other the run and it starts Pam's when you hit start on the BSP.
Norgatron
erstlaub wrote:
Norgatron wrote:
Just wanted to say that I woke up yesterday looking for a divider to set the Sync input on my Jellyfish V2 delay from the BSP Clock Out and went to bed with a Pamela's New! Workout on order from Post Modular. eek!

It was a bit over my budget for this month but once I understood what it was capable of I had to have it. The fact that it has great aesthetics and is British designed and built just tipped me over the edge, and by the time I got to the end of Ben's video it was ordered. w00t

As well as driving the Jellyfish's delay syncI will probably use it across my new live rig as a source of LFOs and synced modulations in general, a buddy for Kinks and Function ands loads of stuff I haven't thought of yet. I'm pretty excited.


I'd heartily recommend knocking up the cable to slave new (or old) Pam's to the BSP too. It's just a TRS cable with 3.5mm mono jacks on the end, one carries the clock, the other the run and it starts Pam's when you hit start on the BSP.


Oh, right, so the sync out on the BSP has run on the ring? Sweet. I will definitly do that, cheers! It's peanut butter jelly time!
hawkfuzz
Is there a menu layout available anywhere?
monads
ALM wrote:
propertyof wrote:
i missed the latest firmware update info. does firmware 197 has a final version released now?


Not yet but I just uploaded a 'BETA-2' which should improve the CV control of BPM.

Id really like to get some more feedback before I spin a 198 release. Please do let me know if you are using the beta and have no issue (or not!).


I'm still on 196. Is 198 getting closer or should I just go 197 BETA-2???
ALM
monads wrote:


I'm still on 196. Is 198 getting closer or should I just go 197 BETA-2???


198 will get closer if you try 197 BETA-2 and report back any issues hyper
atte
It would be awesome to be able to load banks by CV. Any chance this could happen?
ALM
Just uploaded 198 release proper - no longer a beta !

Grab via http://busycircuits.com/firmware/alm017/alm017-198.bin

From Changelog ( http://busycircuits.com/firmware/alm017/ChangeLog.txt );

Ver 198 (25/10/17)
==
- Fix bug where output end pulse type may not fire.
- Fix bug with cv of looping not working correctly.
- Load next (not prev) bank when CV 1 is low.
- Allow external clock to still work with new run options.
- Extend screensaver timeout a little (15 mins)

From the last non Beta release I can summarise new features as :

- Voltage control of Bank switching and stepped rotation of outputs.
- Push+hold program knob on highlighted output modifier to change without committing until knob release.
- UI now displays last saved/loaded bank.
- Improve voltage control of Tempo.
- Handful of bug fixes + minor tweaks

Also please keep in mind Pam's internal program storage is completely FULL. I really wouldn't expect any new features from now on - there just isn't the space!! Even bug fixes have me pretty anxious now !!

Big thanks to all who provided feedback and reported bugs on the betas!

Please enjoy hyper hyper hyper
guestt
Amazing we're not worthy we're not worthy we're not worthy

It was good anyway, but this is above and beyond!
atte
WOW!

Can't wait to try out bank switching, I love it already!!!!

And I see the manual is already updated, fantastic!

Thanks for making a great module even greater!
monads
Awesome we're not worthy
interpolate
I think rotation makes this module a must have now.
Southfork
This module is still very high on my list for best modules of 2017. Love it even more Lotsa Love
propertyof
awesome been looking for the update! definitely best of '17! we're not worthy we're not worthy
behndy
wowsers. thank you!
dumbledog
interpolate wrote:
I think rotation makes this module a must have now.

Seriously, I was considering getting a Tempi specifically for rotation but this solves that problem.

Switching between 2x/4x/2x/1x on a sequence is so damn nice.
Dark Barn
Ahhh! Sounds amazing! Probably no way to exclude an output from rotating is there?
ALM
Dark Barn wrote:
Ahhh! Sounds amazing! Probably no way to exclude an output from rotating is there?


Kind of - you can optionally rotate just the top 4 rather than all 8.
resynthesize
i've been heavily using the rotation feature since it was released in beta form a little while ago. tons of fun combined with euclidian patterns! i'll usually restrict rotation to the top 4 and use output 5 on /4 or /8 patched to the run jack to trigger rotation.

one piece of advice, make sure you unpatch the run jack before making any changes to it's options - "reset all" is right next to the rotate options and i've accidently wiped out all my settings a couple of times by errant triggers coming in while scrolling past that option.
Dark Barn
ALM wrote:
Dark Barn wrote:
Ahhh! Sounds amazing! Probably no way to exclude an output from rotating is there?


Kind of - you can optionally rotate just the top 4 rather than all 8.


Wow! Thank you for thinking of this! It's peanut butter jelly time! nanners
creativesounds
Quote:
Using either Pam as master - One output at x24 into slaved pam clock input. Another output set to 'constant on' into slaved pam run input.


So is it safe to assume I can just do the same thing with two of Pam's NEW Workouts? (I believe this quote was for 1 new and one old workout modules)
mcpepe
Don't we still have yet an updater app for Windows?

It's in the pipeline?


Thanks!
ALM
creativesounds wrote:
Quote:
Using either Pam as master - One output at x24 into slaved pam clock input. Another output set to 'constant on' into slaved pam run input.


So is it safe to assume I can just do the same thing with two of Pam's NEW Workouts? (I believe this quote was for 1 new and one old workout modules)


Yes of course. Also with new, you can you use the 2hp expander x24 & run outs to save 2 outs on the master.
ALM
mcpepe wrote:
Don't we still have yet an updater app for Windows?


The command line 'dfu-util' app works for windows.

The GUI app is 'cross platform' and simple sources available (see busycircuits github) - I've just never had any success getting it to build/link on Windows (limited experience). If anyone can help, shoot me a mail.
pitri
ALM wrote:
creativesounds wrote:
Quote:
Using either Pam as master - One output at x24 into slaved pam clock input. Another output set to 'constant on' into slaved pam run input.


So is it safe to assume I can just do the same thing with two of Pam's NEW Workouts? (I believe this quote was for 1 new and one old workout modules)


Yes of course. Also with new, you can you use the 2hp expander x24 & run outs to save 2 outs on the master.


did you try by now to hook both expanders onto one pams?
creativesounds
pitri wrote:
ALM wrote:
creativesounds wrote:
Quote:
Using either Pam as master - One output at x24 into slaved pam clock input. Another output set to 'constant on' into slaved pam run input.


So is it safe to assume I can just do the same thing with two of Pam's NEW Workouts? (I believe this quote was for 1 new and one old workout modules)


Yes of course. Also with new, you can you use the 2hp expander x24 & run outs to save 2 outs on the master.


did you try by now to hook both expanders onto one pams?


I don't have the expanders. I was thinking it would be more efficient to just buy another Pam and then I have 8 more highly configurable clocks/lfos/etc.
Outtatune
Updated. Happy. Thanks @ALM!
mrerdat
198 firmware rules. Output rotation is a game changer we're not worthy
charonme
almost perfect, I considered this to work as LFOs, but sadly the outputs don't go below zero :(
soundslikejoe
charonme wrote:
almost perfect, I considered this to work as LFOs, but sadly the outputs don't go below zero :(


Neither does Intellijel Quadra or Maths... or any other cycling function... unless you use an offset. All great LFOs... and lots of modules have offset controls built into the CV input.

So... 2-cent. Nothing to be sad about.
dooj88
damn, 198 brings the meta mode home. sweeet!
adh82
Is there anyway of programming your own gate pattern?
behndy
so, amongst all the other ridiculously awesome things i love about this module, the PEXP expander is so GOOD.

i just hooked the MIDI out into my Digitakt, hit play, perfect lock in tempo and start/stops the sequences.

so. freaking. EASY.

looooooooooooooove you ALMsters.
Tumulishroomaroom
behndy wrote:
so, amongst all the other ridiculously awesome things i love about this module, the PEXP expander is so GOOD.

i just hooked the MIDI out into my Digitakt, hit play, perfect lock in tempo and start/stops the sequences.

so. freaking. EASY.

looooooooooooooove you ALMsters.

Yep, so good to sync a drum machine ! In my case it's very handy since the Tanzmaus doesn't have a trig input. And the 4 additional "boring" clocks a very welcomed !
Zymos
soundslikejoe wrote:
charonme wrote:
almost perfect, I considered this to work as LFOs, but sadly the outputs don't go below zero :(


Neither does Intellijel Quadra or Maths... or any other cycling function... unless you use an offset. All great LFOs... and lots of modules have offset controls built into the CV input.

So... 2-cent. Nothing to be sad about.


Plenty of LFOs are bipolar....
soundslikejoe
Zymos wrote:
soundslikejoe wrote:
charonme wrote:
almost perfect, I considered this to work as LFOs, but sadly the outputs don't go below zero :(


Neither does Intellijel Quadra or Maths... or any other cycling function... unless you use an offset. All great LFOs... and lots of modules have offset controls built into the CV input.

So... 2-cent. Nothing to be sad about.


Plenty of LFOs are bipolar....

Yet another reason not to be sad about PNW being unipolar.

And.... every LFO can have complete polarity control when used with the appropriate utility module(s).
dooj88
i might've made a mistake with the command line last time i posted (there were extra characters referring to dfu- util..). so I just ran the 198 update doing the following and it was a breeze. will post again for reference. i'm on windows 7, but should work for 10 as well.

Quote:

DIRECTIONS:::::::::::::::::::::::::::::::

-put the download file "alm017-198.bin" in root of c drive
-create a new folder in root of c drive. call it "update". paste all the downloads from the "dfu-util-0.8-binaries" page (referred to in the manual, i downloaded all 7 files) inside the folder.

-connect pam

-run "zadig-2.3" which loads it as a driver as outlined in Pam manual:
--options, list all devices
--select STM 32 BOOTLOADER
--select WinUSB near green arrow

-open CMD, (right click, 'run as admin' to be safe..)

-copy the following file line, making sure you change the last part "alm017-198.bin" to reflect the newest file name (in case you've updated before):

C:\Update\dfu-util-0.8-binaries\win32-mingw32\dfu-util.exe -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D c:/alm017-198.bin

-in CMD, right click and paste


happy days nanners
charonme
soundslikejoe wrote:
Zymos wrote:
soundslikejoe wrote:
charonme wrote:
almost perfect, I considered this to work as LFOs, but sadly the outputs don't go below zero :(


Neither does Intellijel Quadra or Maths... or any other cycling function... unless you use an offset. All great LFOs... and lots of modules have offset controls built into the CV input.

So... 2-cent. Nothing to be sad about.


Plenty of LFOs are bipolar....

Yet another reason not to be sad about PNW being unipolar.

And.... every LFO can have complete polarity control when used with the appropriate utility module(s).


When I say "LFO" I mean nice smooth sine waves. What excited me about PNW was 8 outputs in 8hp. If I had enough space for dedicated LFOs or even utility modules just to adjust some offsets (let alone using maths for LFOs!) I wouldn't be considering PNW in the first place
BlueWolfSe7en
Any idea when the next batch will hit the UK?
Made some changes to my case & this is a must now :-)
ALM
BlueWolfSe7en wrote:
Any idea when the next batch will hit the UK?
Made some changes to my case & this is a must now :-)


If all goes to plan, restocks should start shipping out mid/late this month. hyper
BlueWolfSe7en
ALM wrote:
BlueWolfSe7en wrote:
Any idea when the next batch will hit the UK?
Made some changes to my case & this is a must now :-)


If all goes to plan, restocks should start shipping out mid/late this month. hyper


Awesome stuff, thanks for the fast response :-)
cityz3n
ALM wrote:
BlueWolfSe7en wrote:
Any idea when the next batch will hit the UK?
Made some changes to my case & this is a must now :-)


If all goes to plan, restocks should start shipping out mid/late this month. hyper


For the impatient ones, like me.
Soundria.com has them still in stock.
BlueWolfSe7en
cityz3n wrote:
ALM wrote:
BlueWolfSe7en wrote:
Any idea when the next batch will hit the UK?
Made some changes to my case & this is a must now :-)


If all goes to plan, restocks should start shipping out mid/late this month. hyper


For the impatient ones, like me.
Soundria.com has them still in stock.


Sweet, for UK buyers that works out around £24.00 more expensive tho.
Damn the state of the pound against the euro!
studioqmp
Nobody uses Pam with the Tiptop Circadian Rhythm? I can not manage sync with both properly. May pam be a slave or a master.
behndy
i'm a bit of a git about clock syncing multiple devices. wanted to send the Pam's PEXP1 MIDI out to at least 4, maybe more, devices. anybody have a recommendation for a (preferably rackmount instead of tabletop) thing to look at for this?

thanks!
void23
studioqmp wrote:
Nobody uses Pam with the Tiptop Circadian Rhythm? I can not manage sync with both properly. May pam be a slave or a master.


You might be out of luck. I’ve never gotten Pamela’s to send a reliable 24ppqn and reset.
studioqmp
Actually the best way i find to sync Circadian Rhymth with Pamela is to set the Pam at 4ppqn... But it is very not stable.
ALM
behndy wrote:
i'm a bit of a git about clock syncing multiple devices. wanted to send the Pam's PEXP1 MIDI out to at least 4, maybe more, devices. anybody have a recommendation for a (preferably rackmount instead of tabletop) thing to look at for this?


Kenton midi thru box ? Not rackmount though.
pre post eros
behndy wrote:
i'm a bit of a git about clock syncing multiple devices. wanted to send the Pam's PEXP1 MIDI out to at least 4, maybe more, devices. anybody have a recommendation for a (preferably rackmount instead of tabletop) thing to look at for this?

thanks!


MIDI Solutions T8 should fit the bill...

http://www.midisolutions.com/prodt8.htm
behndy
thanks! have a Kenton on the way, trying that first.

woot!
Catchthehare
Does anyone have experience or a setup for PNWO and CV.OCD external sync? I'm using my Digitakt to drive the clock through CV.OCD to Pam's CLK, but I can't figure out Run start/stop. I only get about 4PPQN this way. It syncs fine, but no Run start stop. Im using latest firmware and also don't have RUN 'N' option in Pam's, only 'Y'
Is this correct?
Nino
I just did the update to the latest fw – i’m not a 100% sure if this behaviour wasn't the same in beta, but when i run a stepped random x1 on let’s say 4 channels they all spit out the very same voltages. Is that normal and if yes: why :)
ALM
Catchthehare wrote:
Does anyone have experience or a setup for PNWO and CV.OCD external sync? I'm using my Digitakt to drive the clock through CV.OCD to Pam's CLK, but I can't figure out Run start/stop. I only get about 4PPQN this way. It syncs fine, but no Run start stop. Im using latest firmware and also don't have RUN 'N' option in Pam's, only 'Y'
Is this correct?


I set this up for a friend a while back - IIRC one gate (to pams clock input) was set to 'clock tick' , ck.rate to '24ppqn' and trig as trigger. The second gate (into Pams 'run') was set to 'transport run' and trig as 'gate' .

Pams old Run 'N' option is called "RS' - reset.
ALM
Nino wrote:
I just did the update to the latest fw – i’m not a 100% sure if this behaviour wasn't the same in beta, but when i run a stepped random x1 on let’s say 4 channels they all spit out the very same voltages. Is that normal and if yes: why smile


I cant seem to reproduce this. A Random waveform output right ? Did you load all the outputs from the same save maybe ?
Nino
I manually set all four channels to stepped rnd before starting Pam.

What i did now:
-pam doesn't run
-load bank B (which is empty since i just updated)
-manually set all 8 outputs to x1 stepped random
-press start

1,2,5,6,7 and 8 show the same signal
3 and 4 also show the same signal, but diferent from the others
i gonna do the same thing with empty bank C now

Now all 8 are the same.

edit: ok, after a global reset every stepped random i set is different
ALM
@Nino Ok played some more and it seems it can happen - not 100% sure as to how or why yet. Quick workaround is just reset the channel.

This may well of been apparent in early firmwares too ?

Will investigate...
Nino
Thanks a lot so far nanners
Catchthehare
ALM wrote:
Catchthehare wrote:
Does anyone have experience or a setup for PNWO and CV.OCD external sync? I'm using my Digitakt to drive the clock through CV.OCD to Pam's CLK, but I can't figure out Run start/stop. I only get about 4PPQN this way. It syncs fine, but no Run start stop. Im using latest firmware and also don't have RUN 'N' option in Pam's, only 'Y'
Is this correct?


I set this up for a friend a while back - IIRC one gate (to pams clock input) was set to 'clock tick' , ck.rate to '24ppqn' and trig as trigger. The second gate (into Pams 'run') was set to 'transport run' and trig as 'gate' .

Pams old Run 'N' option is called "RS' - reset.


Many thanks for this, I'll try it out.
soundslikejoe
Struggling to update PNW firmware. I did it before... but can't figure it out again.

Can anyone link to more clear instructions for Windows update? I followed the manual... and installed the various software... but when running from Command Line (manual references terminal) I get an error that "dfu-utl not found" or something like that.

very frustrating
Nino
I remember receiving the same message.
Two times i had trouble updating the fw but i don't know which was the one when i got that message, but either one of these helped

-i tried another USB cable and it worked
-installed brew (again?) and it worked
Karabekian
dumbledog wrote:
interpolate wrote:
I think rotation makes this module a must have now.

Seriously, I was considering getting a Tempi specifically for rotation but this solves that problem.

Switching between 2x/4x/2x/1x on a sequence is so damn nice.


Yeah, this is a pretty big game changer. I was thinking of picking up a Tempi for the same reason.

With the price of the two, I'll probably just end up picking up another Pams.
Karabekian
Quote:

DIRECTIONS:::::::::::::::::::::::::::::::

-put the download file "alm017-198.bin" in root of c drive
-create a new folder in root of c drive. call it "update". paste all the downloads from the "dfu-util-0.8-binaries" page (referred to in the manual, i downloaded all 7 files) inside the folder.


Which seven files are they?

In the Win32 folder, there are five files:

dfu-prefix.exe
dfu-suffix.exe
dfu-util.exe
dfu-util-static.exe
libusb-1.0.dll


In the root folder above that, there are two files.

build-mingw32-libusb.sh
dfuse-pack.py


but in the root folder to that there are a whole bunch of 0.8 update files.

I'm assuming it's these seven?

I'm not much for the tech side of things and I really don't wanna fuck up my Pams!
BlackDoors
Catchthehare wrote:
Does anyone have experience or a setup for PNWO and CV.OCD external sync? I'm using my Digitakt to drive the clock through CV.OCD to Pam's CLK, but I can't figure out Run start/stop. I only get about 4PPQN this way. It syncs fine, but no Run start stop. Im using latest firmware and also don't have RUN 'N' option in Pam's, only 'Y'
Is this correct?


Simplest way to slave PNW to Digitakt is to set one of the DT's MIDI outs to DIN Sync and connect Pam's Clock/Run from there (if you have the right lead), was working ok here?
Karabekian
Is there any further documentation that outlines exactly how clock rotation works? Or how to change banks (I read via the changelog that this is via the RUN input)?
ALM
Karabekian wrote:
Is there any further documentation that outlines exactly how clock rotation works? Or how to change banks (I read via the changelog that this is via the RUN input)?

Check the 'Run Input' section (pg 15) in the manual ?
http://busycircuits.com/docs/alm017-manual.pdf
Karabekian
ALM wrote:
Karabekian wrote:
Is there any further documentation that outlines exactly how clock rotation works? Or how to change banks (I read via the changelog that this is via the RUN input)?

Check the 'Run Input' section (pg 15) in the manual ?
http://busycircuits.com/docs/alm017-manual.pdf


Thanks!
WiffSnuggler
What an amazing module! thank you!!!!

really want 198
updating looks like a pain D:
I don't want to mess anything up
not familiar with terminal at all

someone make a video I can follow step by step.
BEERS WILL APPEAR IN YOUR PAYPALL
Mashmore
WiffSnuggler wrote:
What an amazing module! thank you!!!!

really want 198
updating looks like a pain D:
I don't want to mess anything up
not familiar with terminal at all

someone make a video I can follow step by step.
BEERS WILL APPEAR IN YOUR PAYPALL


If you are updating with a Mac the installer program works perfect for me.
Karabekian
Love the rotating clock feature. Any chance of a update in the future that allows two rows of four rotating? Or to turn on/off clocks for rotation?
swhic
soundslikejoe wrote:

Neither does Intellijel Quadra or Maths... or any other cycling function... unless you use an offset. All great LFOs... and lots of modules have offset controls built into the CV input..


will 3xMia / shades/ triatt be good for that purpose then?
dooj88
Karabekian wrote:
Quote:

DIRECTIONS:::::::::::::::::::::::::::::::

-put the download file "alm017-198.bin" in root of c drive
-create a new folder in root of c drive. call it "update". paste all the downloads from the "dfu-util-0.8-binaries" page (referred to in the manual, i downloaded all 7 files) inside the folder.


Which seven files are they?

In the Win32 folder, there are five files:

dfu-prefix.exe
dfu-suffix.exe
dfu-util.exe
dfu-util-static.exe
libusb-1.0.dll


In the root folder above that, there are two files.

build-mingw32-libusb.sh
dfuse-pack.py


that's exactly what my file structure looks like. you're good there.

Quote:
but in the root folder to that there are a whole bunch of 0.8 update files.


not sure which 0.8 update files you're referring to. where did you download them from? the way i set this up, there are duplicate files in this folder tree, since i wasn't exactly sure what the command string is doing. extra files won't hurt. it's not exactly organized, but it works. here's what i have, the 'win32....' folder at the top of the structure is a duplicate of the one already in the 'dfu...' folder. like i said, i'm not a programmer, just messed about with the command line till it worked. hope that helps some.



Karabekian
Thanks!

I gave up on Windows in the end and just found a coder with a Mac to sort it all for me applause
behndy
murrrr i've been lagging on updating a few modules, and havna tried the Pam's yet. i only have Windows machines at the house, hope it's not as messy as it sounds
WiffSnuggler
Mashmore wrote:
If you are updating with a Mac the installer program works perfect for me.

Is it just drag and drop?
cliffemu
“An output modifier and many of its extended parameters can be externally voltage controlled by assigning its parameter value to either of the CV inputs.“
-From the manual.

Is there a list of the cv input destinations anywhere?
Wondering specifically if CV in can be routed to waveform offset, but I’m curious about the rest as well.
Thanks...
ALM
WiffSnuggler wrote:
Mashmore wrote:
If you are updating with a Mac the installer program works perfect for me.

Is it just drag and drop?


Yes. It seems to work well on Mac OS 10.10 and up.
ALM
cliffemu wrote:

Is there a list of the cv input destinations anywhere?
Wondering specifically if CV in can be routed to waveform offset, but I’m curious about the rest as well.


OTOH Its every parameter except 'preset' loading/saving (loading you can now do with triggers in latest firmware).
WiffSnuggler
ALM wrote:
WiffSnuggler wrote:
Mashmore wrote:
If you are updating with a Mac the installer program works perfect for me.

Is it just drag and drop?


Yes. It seems to work well on Mac OS 10.10 and up.


Alrighty, so I don't need terminal on mac? Will be trying when I get home tonight
WiffSnuggler
https://www.youtube.com/watch?v=_xdWcZJZeYs&feature=youtu.be

can someone help?
my pams is jittering when i use its clk slave in from BSP, things are in time I guess , but are happening slightly before or after my BSP drums.
super annoying sounds like two two kicks slightly separated from each other.
clk on my beatstep 100, pams wants to jitter between 99 and 100 as seen in the video.

any help would be greatly appreciated!
Shledge
Make it start at the same time by splitting clock out to seperate run/clock cables.
BaloErets
WiffSnuggler wrote:
https://www.youtube.com/watch?v=_xdWcZJZeYs&feature=youtu.be

can someone help?
my pams is jittering when i use its clk slave in from BSP, things are in time I guess , but are happening slightly before or after my BSP drums.
super annoying sounds like two two kicks slightly separated from each other.
clk on my beatstep 100, pams wants to jitter between 99 and 100 as seen in the video.

any help would be greatly appreciated!


Any chance you're on the latest firmware for the BSP? Multiple reports of issues with the BSP not keeping a steady clock out from the last update.
WiffSnuggler
BaloErets wrote:
Any chance you're on the latest firmware for the BSP? Multiple reports of issues with the BSP not keeping a steady clock out from the last update.


EDIT: Im on 1.4 bsp firmware...im wondering if I should update... is there an archive of past BSP firmwares? On Arturia's site they only have they 2.0.0.2 or whatever. I dont think pams is the problem here its always been very ace, but is it normal for a tempo to jitter like that?
BaloErets
I know it's been mentioned that there is very little space left for feature requests and improvements. With that said, I am humbly going to request a clocking feature, because I will regret it if I don't ask thumbs up

Any chance that we could get an option for a semi non-quantized clock? In the sense that the clock at x1 would still be perfectly synced to the BPM, but the clock multiplier/divisor could be set within 1 decimal increments. So we could dial in, for example, x1.9 or /2.7?
Mashmore
Just kind of thinking out loud. I know space is tight but would being able to change the modifier value via semitones be doable? Everything about this module kicks ass just seem to spend more time than id like searching for ratchets and sweet spots when Im wanting to use external cv.
dooj88
he said there are bytes worth of space left. if anything is going to be added, it'll have to be in an alternate firmware.
soundslikejoe
Question about Clocking PNW to a DAW.

Right now I'm sending clock via ES3 and Silent Way (audio pulse). Obviously... PNW wants to calculate the incoming signal, but this causes a stutter in the Start of the clock. It usually puts everything behind by 1 beat.

What's the best workflow for clocking PNW with a DAW for a tight sync between Transport START and PNW Start?
Muse FTW
soundslikejoe wrote:
Question about Clocking PNW to a DAW.

Right now I'm sending clock via ES3 and Silent Way (audio pulse). Obviously... PNW wants to calculate the incoming signal, but this causes a stutter in the Start of the clock. It usually puts everything behind by 1 beat.

What's the best workflow for clocking PNW with a DAW for a tight sync between Transport START and PNW Start?


Interested in this, too. I've had this problem since I got the module months ago.
boboter
Muse FTW
soundslikejoe

If I understand you correctly, that should be quite normal. Every external clocked device is a bit behind the beat. In Ableton you can adjust the delays of the individual tracks, so you can make the incoming audio sit nicely on beat. If you just use hardware sound sources this is a bit easier than if you want to sync plugins and hardware.

Are you just sending a pulse via silent way, or also a run-signal on a separate channel? The latter makes sure that Pam always starts at the right time. So even if you have a delay, it will be consistent every time. Clock + Run Signal is basically Din Sync. And Pam follows that nicely.

I use an old Innerclock SyncGen to sync the modular. But it should be the same with Silent Way / ES3.
soundslikejoe
boboter wrote:
Muse FTW
soundslikejoe

If I understand you correctly, that should be quite normal. Every external clocked device is a bit behind the beat. In Ableton you can adjust the delays of the individual tracks, so you can make the incoming audio sit nicely on beat. If you just use hardware sound sources this is a bit easier than if you want to sync plugins and hardware.

Are you just sending a pulse via silent way, or also a run-signal on a separate channel? The latter makes sure that Pam always starts at the right time. So even if you have a delay, it will be consistent every time. Clock + Run Signal is basically Din Sync. And Pam follows that nicely.

I use an old Innerclock SyncGen to sync the modular. But it should be the same with Silent Way / ES3.


I wouldn't say that "every external clocked device is a bit behind the beat" but only those that are connected to PNW. In this instance, I'm scoring a film and the sequence start time is pretty critical... as it has to align with live instruments and other soft synths. Stuttering for a beat doesn't happen when moving the clock directly to the sequencer or into an analog clock.... or with MIDI clocked gear.

So I guess the question is more... Is it possible to set PNW clock and then have it ignore the "calculate clock" process? That would eliminate the stutter. It's also not really necessary if the clocks are already set. "We're working at 89 BPM all day Pam. Stop trying to figure it out."

Also wonder... If using the MIDI expander for PNW, would the stutter be less? With MIDI Clock, the clock is always output from the DAW (when stopped). This would also eliminate the calculation phase.
ALM
soundslikejoe wrote:


Right now I'm sending clock via ES3 and Silent Way (audio pulse). Obviously... PNW wants to calculate the incoming signal, but this causes a stutter in the Start of the clock. It usually puts everything behind by 1 beat.

What's the best workflow for clocking PNW with a DAW for a tight sync between Transport START and PNW Start?


Use the silent way 'sync' app. Make sure you have a 24 PPQN clock and your using the run signal.

If everything is out by a beat(!) you are sending too low a resolution clock or something else is wrong. As others have mentioned Pam will lock instantly to a din dync type clock.
soundslikejoe
ALM wrote:


Use the silent way 'sync' app. Make sure you have a 24 PPQN clock and your using the run signal.

If everything is out by a beat(!) you are sending too low a resolution clock or something else is wrong. As others have mentioned Pam will lock instantly to a din dync type clock.


YES! This would be my problem! I forgot that I had mucked around with PPQN setting in both (1). It seemed that I had achieved a proper DAW sync a few months ago, but I wasn't sure what I was missing. Thx for the tip!
strange tales
behndy wrote:
murrrr i've been lagging on updating a few modules, and havna tried the Pam's yet. i only have Windows machines at the house, hope it's not as messy as it sounds


(for the sake of clarity I'm gonna edit this for exact steps.)

Yea, it's not that hard. Just copy the files from dfu-util to a folder, and then open Command Prompt and change the directory to where you extracted the dfu-util stuff. So:

1. Plug unpowered Pam's in.

2. Download and open Zadzig (it should just be a loose .exe file). Click on the drop down list and look for STM32 BOOTLOADER. You might have to click Options -> List all Devices for it.

3. Download the dfu-util files (http://dfu-util.sourceforge.net/releases/). 0.9 worked for me no problem. Extract the files somewhere.

4. Open command prompt as an administrator (right-click -> run as administrator) and do:
cd <<Path to where you put dfu-util files>>

5. Download the Pam's firmware from the ALM site

6. Run the command in the manual:
dfu-util -a 0 -d 0x0483:0xdf11 --dfuse-address 0x08000000 -D <<Path to firmware.bin>>

Quick, easy, and update complete.
behndy
well Strangey Ends, because i adore you and you have MY GODDESS as an avatar, i will try it tonight.

not a huge deal, but it's going to wipe any saved settings?
strange tales
Manual says it's likely to remove any saved settings, so I would remember what you want before hand.

If you have any problems send me a message here or on ILF.
behndy
boom chickah wah. INTO IT. thanks pimpers.
swhic
can the added vertical offset make the uni lfo bi? ta!
themodularlife
Hello guys, Output 4 of my PNW suddenly stopped working and I'm not sure of what to do. It was running just fine but then I tried to use gate out 4 to trigger Maths and it did nothing. I switched cable, still nothing, switched from Maths to 0 coast tempo in, no response. However, the LED still works just fine, it feels like it sends a +0v instead of a +5v. I resetted both chan4, and the Pam itself thru the main menu, turned the case off & on a couple times, still nothing. Any idea of what should I do? Thanks!
Mashmore
themodularlife wrote:
Hello guys, Output 4 of my PNW suddenly stopped working and I'm not sure of what to do. It was running just fine but then I tried to use gate out 4 to trigger Maths and it did nothing. I switched cable, still nothing, switched from Maths to 0 coast tempo in, no response. However, the LED still works just fine, it feels like it sends a +0v instead of a +5v. I resetted both chan4, and the Pam itself thru the main menu, turned the case off & on a couple times, still nothing. Any idea of what should I do? Thanks!


Hmmm. If I were you and nothing seem to fix it I would reflash Pam’s with the most recent firmware again and cross my fingers.
Zymos
I think you could just cross your fingers and get the exact same result...
BaloErets
themodularlife wrote:
Hello guys, Output 4 of my PNW suddenly stopped working and I'm not sure of what to do. It was running just fine but then I tried to use gate out 4 to trigger Maths and it did nothing. I switched cable, still nothing, switched from Maths to 0 coast tempo in, no response. However, the LED still works just fine, it feels like it sends a +0v instead of a +5v. I resetted both chan4, and the Pam itself thru the main menu, turned the case off & on a couple times, still nothing. Any idea of what should I do? Thanks!


Have you tried this;

1. Go in the main menu scroll to where you see the BPM and then long click to get into the system level menu.
2. Scroll one click counter-clockwise to get to the "Reset ??". Select that, and turn until it reads "YES". Select that and see if you problem goes away.

EDIT; Sorry, I didn't read the part where you took the time to explain you already tried resetting both the channel and all of Pams. My bad waah
Mashmore
Zymos wrote:
I think you could just cross your fingers and get the exact same result...


Yes this is probably true.......
Bignorthumbrian
My PNW arrived yesterday.....and to say I’m happy with it, would be an understatement, thank you DivKid....your videos make me buy stuff I never knew I needed
yeatsvisitslincoln
Bignorthumbrian wrote:
My PNW arrived yesterday.....and to say I’m happy with it, would be an understatement, thank you DivKid....your videos make me buy stuff I never knew I needed


I just got mine yesterday, and basically have the same thing to say, as well. I haven't even read the manual, but I watched the video a couple months ago and it took me maybe 5 minutes to get some really nice rhythmic and melodic stuff going. Pam made it so amazingly easy.
lisa
I adore Pam's. It's really the heart of every modular track that I make and I haven't even explored the CV inputs yet. With the Pexp-1 I'm seldom running short on outputs.

Just a little love where love is due. love
Shledge
My first impression of PNW was the opposite. Was initially really disappointed with it at first, mainly with keeping it in sync.

Since then, I'd happily buy a 2nd one. It's really the heart of my modular.
behndy
Shledge wrote:
My first impression of PNW was the opposite. Was initially really disappointed with it at first, mainly with keeping it in sync.

Since then, I'd happily buy a 2nd one. It's really the heart of my modular.


jia. i mean. i adored her from first patch.

but i'm seriously thinking about grabbing another. one for all the clockings, one for envelope outs.
plutino
Is there any way to exclude an output from rotation similar to the TEMPIs mod-enabled option. I don't think there is but not convinced I'm not just missing something.
Zymos
You can exclude 5-8, but not any specific one...
guestt
It's a little wasteful, but if you want say only 3, set 2 channels out of the 4 to be the same, it works fine!
LongLostDonut
Apologies if this has been covered (I've done a scan/search) but I'm trying to get Pam's to start when I hit 'play' in Reaper, but not be clocked by Reaper.

Previously, I have gotten Pam to sync to Reaper's clock by playing a simple 'click' sample at 16ppqn out of dedicated output & into Pam's Clk input. Run is set to 'RS'.

However, this can sometimes be a touch glitchy (my PC/soundcard being a touch shit, I guess), so I'd rather have Pam's being the clock for all my gear, but being triggered to start by Reaper, so I can multitrack stuff.

I can't work out how to get a suitable continuous signal out to start and keep playing Pam's. The 16ppqn sample just makes it blink every now and then. I tried playing a continuous square wave, but nothing happens.

Any help welcomed!
Shledge
Probably not at a high enough volume - it'll need to be at modular levels. I've done it myself but it needs a high enough volume.
LongLostDonut
Thanks Shledge, I'm sure that's right in some way - but as you'll see from below even if I get the level loud enough for it to do something, it's still not working as desired - it would be great if you could share how you did it.

With a bit more playing around this morning, I tried playing a sine wave out at loud enough volume and can get PNW to run, but the note of the sine determines the tempo Pam plays at and changing the tempo on Pam's has no effect.

I'm guessing this has something to do with CV being sub-audio rates, I tried triggering run from a sine out of Batumi and it has the expected behaviour (+0 runs Pam, -0 stops it)... but when I move the lfo into audio territory, Pam starts to change tempo in response to the frequency.

Not quite sure if it would be possible to get 'round this - as I am guessing any signal sub-audio rate coming out of my soundcard won't be low enough to make Pam run. It would be good if it ignored any kind of rate information on run, as surely setting that is what the clk input is there for?
Shledge
I think I understand now - the issue isn't the clock signal itself but how to send a start/stop signal. You won't be able to directly send a continuous signal directly since most audio interfaces are AC coupled.

You can always send a pulse to a clock divider (one that sends gates, not triggers), then patch the /2 output into the run input of PNW. It will act like a flip-flop, allowing you to toggle it on and off.
Mend
Really love PNW! I'm a bit confused by the rotating clock feature. I've read the manual but I'm still not understanding how to trigger it. Can someone guide me by giving a simple example?
Shledge
I think DivKid covered it in his PNW video.
Mend
Shledge wrote:
I think DivKid covered it in his PNW video.
I'll rewatch it then. Thanks!
dumbledog
I'm not sure if I've never noticed until now since I'm usually using an external clock, but my PNW is running a hair slow -- enough to make multitracking long pieces difficult. Setting it to 100 BPM yields instead 99.84 BPM, while 175 BPM becomes 174.69 BPM. Basically I'm off consistently slow by about 0.15% (or 0.0015).

I've measured this using Ornament and Crime's References mode (using 48ppqn) as well as Logic Pro's BPM counter, and just by setting Logic's tempo so that notes still line up after ten minutes or so. Newest firmware, nothing plugged into any of the top CV inputs, fresh off of a settings reset.

Any ideas?

(edit: one workaround -- Silent Way Sync --> ES-8 --> Pam's Clk input gives me the exact BPM)
alanza
yup, you gotta sync it. I have no idea how people expect their different clocks to stay exactly in time without synching!
swhic
it would be nice to have a mixing utility! possible with firmware update?
rikrak
Mend wrote:
Shledge wrote:
I think DivKid covered it in his PNW video.
I'll rewatch it then. Thanks!


Hmmm. I thought he put the video out before the release of the (stable version of the) firmware that added Rotating Clock.

Anyway, it is very simple to test.

1) Set Output 1, 2, 3, 4 to different multiples (so that it is easier to see that the rotation is happening).

2) Long-press on BPM screen to enter Global Settings. Set "Run?" to "RA" to Rotate All 8 outputs or "RS" to Rotate the Single top row of 4 Outputs only.

3) Send a Gate High into the Run Input every time you want to Rotate the Outputs.

Done.
dumbledog
alanza wrote:
yup, you gotta sync it. I have no idea how people expect their different clocks to stay exactly in time without synching!


Well I was expecting to have to shift the notes a bit forward or backward to land on the timeline correctly, but I also rather expected them to agree on what is meant by "138 bpm."
rklem
I got my PNW a few days ago and I really like it, but the display is so dim that it's hard to read. I can't imagine that this is intentional. Is there a hidden command to adjust the brightness?
BaloErets
rklem wrote:
I got my PNW a few days ago and I really like it, but the display is so dim that it's hard to read. I can't imagine that this is intentional. Is there a hidden command to adjust the brightness?


No something is not right there. On a fresh bootu