Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - pld

Pages: 1 [2] 3
Also is it normal that the encoder clicks represent two turns? To make a fine change I have to go really slow to avoid skipping on another value.
Is that with the encoders from the kit?
If not, there's a menu setting to switch between 12/24 steps which could help...

preenfm2 and preenfm3 / Re: [Fixed] OS not finding /pfm2 directory
« on: June 04, 2014, 10:44:37 AM »
The preenfm2 is always ready to receive success.
And it certainly deserves lots of success. SCNR :)

preenfm2 and preenfm3 / Re: 1.B13 : arpeggiator new modes
« on: May 09, 2014, 01:28:16 PM »
"option to have independent row for each of the 4 instruments "

There's a new setting ("unlinked edit") to change the behaviour when you press INST:
Default is the way it has been, i.e. when you press INST, you edit the same parameters for each instrument ("linked").
With the new option, the last-used row is stored per instrument, so you can have inst 1: arp user pattern, inst 2: fx, inst 3: matrix..., and edit them independently ("unlinked").

If that makes sense :)

Related: The case when you press INST while editing a user pattern, and the next instrument doesn't have one active, should also be fixed.

preenfm2 and preenfm3 / Re: Possible arpeggiator modes/directions
« on: May 04, 2014, 09:47:47 AM »
Great. Sorry about that...
Do you think it's worth having arp parameters controllable by CC?
I did a quick test and changing patterns on-the-fly worked. That might be easier than an internal sequencer...

preenfm2 and preenfm3 / Re: Possible arpeggiator modes/directions
« on: May 03, 2014, 03:31:22 PM »
No, I missed something; I pushed a fix to the branch. The last "cleanup" commit was a bit too aggressive ::)

preenfm2 and preenfm3 / Re: Possible arpeggiator modes/directions
« on: April 29, 2014, 08:37:29 PM »
Is one really clearer than the other ;-)
Ok, not really :) But they sort of map to the ROR and LSR type instructions...

I don't know what you plan to do for the arp step seq.
It started with a suggestion in the firmware thread:
...possibilities of an arp step sequencer where for instance you could program it to play user arp 1 four times then user arp 2 three times etc.
So maybe less of step sequencer, more of a pattern chain. That also gives bettern acronyms than ASS...

My thinking was 1-4 slots/links consisting of { pattern, count, modifier, value }.
The modifier would affect some parameter of the arp/pattern while that link was playing.
Some modifiers I had off the top of my head were
  • transpose: +- value
  • step: change ordering of notes; normal is step 1 (c-e-g), step 2 gives (c-g-e-c-...)
  • division: somehow modifiy the division parameter
  • octave: modify octave parameter
How this might tie in with the matrix I'm not too sure, the vague idea was adding matrix destinations that do the same thing as the modifiers. Or something :)

So yeah, it's a bit half-baked, but kids these days call it agile  :P

preenfm2 and preenfm3 / Re: Possible arpeggiator modes/directions
« on: April 29, 2014, 07:34:11 AM »
Quick braindump after I did a quick&dirty implementation of the step sequencer without a UI:
  • How about 'rotate' or 'permutate' instead of 'cycle', and 'shift' instead of 'supercycle'?
  • Doing these mods in the arp step sequencer (ASS ???) will work, but it might be even cooler to have both so they add to each other
  • Which ties in with the request to have arp parameters modifiable via matrix, so we have the additional parameters 'hidden' as matrix destinations?

preenfm2 and preenfm3 / Re: Possible arpeggiator modes/directions
« on: April 28, 2014, 08:57:16 PM »
I don't get how Supercycle is different from Cycle with octave >=2.
Hm, how to describe... Writing it out is probably better:

Played: c1, e1, g1
UpCy, octave=2: [c1-e1-g1 e1-g1-c1 g1-c1-e1] [c2-e2-g2 e2-g2-c2 g2-c2-e2]
UpSc, octave=2: [c1-e1-g1 e1-g1-c2 g1-c2-e2] [c2-e2-g2 e2-g2-c3 g2-c3-e3]
UpSc, octave=1: [c1-e1-g1 e1-g1-c2 g1-c2-e2] repeat

Where [] is one cycle which ends when each played note has been used as the starting note, then the arpeggiator octave changes.
UpCy muddles around in the played notes, but UpSc arpeggiates the ascending chord inversions, so when the arpeggiator switches octave, it continues seamlessly.
If that helps ;)
You can get the same result by manually playing the chord inversions with 'Up' direction, for 'cycle' you'd have to used 'plyd' and hit the right ordering.

Hm, maybe 'supercycle' should be 'auto inversion' or something, and I'm admittedly not convinced 'cycle' is useful, but it was easy to implement both :P

Sound interesting...
Where else ? I don't know. We may hide them by default and activate them in the setting... I'd like not to have 20 rows in engine menu when new users turn on their preenfm for the first time.
Yeah, it's getting a bit overwhelming...

Anyway those new rows won't be in 1.00.  But that must not prevent you from coding it ;-)
I'll probably do it soonish because otherwise I'll lose my train of thought :) Then we can re-evaluate where/if to put it.
You can cherry-pick the 'chord' commit out of the branch since it shouldn't have any other implications.

preenfm2 and preenfm3 / Re: Possible arpeggiator modes/directions
« on: April 28, 2014, 07:09:58 PM »
I don't understand what Sc is in ""UpSc", "DnSc", "UDSc".
Supercycle. I'm open to better names ;) Maybe UpCo (Cycle octave?) The normal 'octave' setting works on top of that so it should go up seamlessly.
If I have time I can try and record a test later.

Please no aditional sub-page, specialy in the engine menu which is already busy.
Doh! Coming home I had a whole plan for the "arp step sequencer" combined with the cycles, but that would be 1 control row + 2 if enabled  :P
I agree that the engine menu is getting a bit overloaded... but where else?

preenfm2 and preenfm3 / Possible arpeggiator modes/directions
« on: April 28, 2014, 11:06:45 AM »
Howdy all,

so while porting the 'chord' mode from MIDIpal yesterday I was playing around with these, but I'm not sure how useful they are since I'm coming at this mostly from a code point of view :)
I forget if these have a well-defined name, so if they do let me know...

1. cycle
Played notes: C-E-G
Result (up): C-E-G E-G-C G-C-E repeat...

2. cycle with octave (supercycle?)
Played notes: C1-E1-G1
Result (up): C1-E1-G1 E1-G1-C2 G1-C2-E2 repeat...

If that makes sense :)
They seemed to work for Down, U&D, and with the regular octave parameter as well.

Downside: an explosion of "Dire" entries if I add "UpCy", "DnCy", UDCy", "UpSc", "DnSc", "UDSc".
So during my morning commute I thought about just adding "Cycl", with a separate sub-page for editing, e.g. [ Dire (up,down,u&d), Octv (yes/no) ]
The "arp step sequencer" as suggested in the firmware thread is something I need to give some thought, but now that I'm thinking about it  :) it might provide similar effect if it has some kind of "offset" parameter as well. Hm...

Suggestions welcome :)

preenfm2 and preenfm3 / Re: New Kits
« on: April 28, 2014, 10:02:30 AM »
any news on firmware updates.
Aside from some experiments that aren't fit for human consumption there are some small things I've fixed/added to the code, but I'm not sure what Xavier's timeframe is for the next update.
I think he been focussed on the editor and I've been avoiding "unofficial" releases :)

preenfm2 and preenfm3 / Re: New Kits
« on: April 27, 2014, 08:24:22 PM »
Mouser claims to have 14 available.
Heh, the list of items in "Customers Who Bought This Item Also Bought" looks very familiar... DAC? Audio jacks? Switches? Pots? Hm...)

preenfm2 and preenfm3 / Re: PreenFM2 with VFD (test)
« on: April 19, 2014, 03:45:01 PM »
Too bad it's so expensive.
Yes, they are quite pricey... but I think back when I bought it, it was cheaper than an OLED :)

preenfm2 and preenfm3 / Re: PreenFM2 with VFD (test)
« on: April 18, 2014, 10:03:05 AM »
Purely out of curiosity I tested the graphics mode of the VFD (140x32 pixels).
It's probably too much work to actually support the features in the firmware so this will probably just remain an experiment.
The logo is 32x32 and seemed a good idea, but bitmapped graphics + non-square pixels = blargh  ::)

Yeah, my pictures suck ;)

preenfm2 and preenfm3 / PreenFM2 with VFD (test)
« on: April 15, 2014, 09:30:34 PM »
I have a VFD (Noritake GU140x32f-7806) that's been gathering dust forever so I figured I might as well give it a try...
When I checked the datasheet it seemed easy enough, the dimensions and connection appear to be identical to the OLED Xavier is using for the new kits.
Except I had shortened the PCB for another project so I had to *ahem* improvise a bit...

The datasheet claims "LCD compatible" but of course it didn't work ::)
After hacking some timings in the firmware - I guess the LCD/OLED are more tolerant? - it seems to work. The photo isn't great, it looks much better live.
Not sure whether to keep it...
  • It does have a bit of noise (high-pitched) but that might be inaudible in a case...
  • The top of the display is almost flush with the buttons and ideally, there'd be a color filter or protection, so that might be more involved
  • It might be the improvised connection, but I think it flickers occasionally. Or it's just using 10x as much power ;)
  • But it's graphics capable so that could be fun :) (although a lot of work)

Pages: 1 [2] 3