Template talk:Infobox synthesizer

message: The current description of memory, above, pertains to patch storage. Samplers have a different dimension: the size of RAM available for samples. ROM-based sample playback synths also have ROM. Some (such as Emu samplers, Roland Fantom, Yamaha Motif, and Korg Triton) may support both ROM and RAM samples. To further complicate things, many ROM-based synths use data compression, and only express the size in terms of its "linear equivalent" - i.e., the size when expanded to uncompressed data.  It seems like it might make sense to separate these three items clearly, as in:
Patch memory: 4 banks of 128 Programs each, 128 Multis
ROM sample memory: 128MB (compressed data; stated size is linear equivalent)
RAM sample memory: 2MB stock, expandable to 32MB
Daniel Alan Phillips 19:10, 7 March 2007 (UTC)
thread_title: Memory

message: Filter is currently defined as filter type, while attenuator is defined as amplitude envelope type. These two terms both refer to audio-path components (filter and amp, respectively), and so should be parallel items; currently, filter refers to an audio component, and attenuator refers to a control component. I'm not sure how best to approach this without disrupting existing articles. Some suggestions:
LFOs currently have their own line item. So should envelopes.
I'm not as certain about this next item:
Attenuator could be retained in its current state to refer to the ability to control amplitude in analog synths, and for modular synths to indicate the actual number of VCAs provided (since some may have multiple modulatable amplitude components; the MS-20, for instance, has two). For instance, some synths have a dedicated ADSR; some allow a switch between an envelope and the note gate; etc. This might be a good way to preserve existing articles.
Daniel Alan Phillips 18:49, 7 March 2007 (UTC)
thread_title: VCF and VCA

message: I don't know much about editing templates, but can something be done so that this info about Minimoog doesn't fill up the whole page:
-- Krash 14:40, 18 December 2005 (UTC)
replies: text: Sure, just use breaks to put info on the next line.fataltourist 15:54, 18 December 2005 (UTC)

text: Hi, I come here from the X-Station article with the same problem. Can't we solve this by making the box a fixed width that automatically enforces a page break if a line becomes to long? Because adding all those page breaks manually throws us all back to the time before we had word processors :-) Thanks, Peter S. 01:56, 10 June 2007 (UTC)
thread_title: Column width?

message: Is there a long-but-not-very-tall lipsum image that could be substituted for No_image.png so there's not all that pesky white space when we don't have a real pic?
Oddly enough, I had been thinking about a Moog info box and I, yesterday, stumbled across this one quite by chance.  I've been trying to come up with what parameters might be included so it was interesting to get to compare with someone else's good idea.  I thought manufacturer, dates produced, and original price were important, so I added them.  But before this template gets dropped into too many more articles, I got a couple more mods to consider. 
I don't understand why "Keyboard" gets its own little section at the bottom.  All info about the keyboard could easily cram into a single section.  I was thinking about a "Left hand control" section as well.  Some that I've considered but don't really seem like a good idea after extensive thought include inputs/outputs, special features (too similar to "Onboard effects"), quantity produced...I'm sure I'll keep thinking of them.  Below is an example of what the modified template might look like. I think it's worth picking at this thing if it's going to go into a number of articles.-- Krash 00:20, 19 December 2005 (UTC)
thread_title: Picky stuff

message: I've been working on a new infobox, inline with the majority of other WP infoboxes (it used :Template:Infobox software as a style guide – the current one seems not to have (drastically) changed since about 2005).  My design can be seen at User:Cycle~/Infobox synthesizer and an example at User:Cycle~/Infobox synthesizer#Example.  This diff shows what the infobox would look like on the Minimoog page – no changes (other than the template address) had to be made.  What do people think?  Cycle~ (talk) 18:00, 23 January 2009 (UTC)
replies: text: I'm going to update it (briefly) to see how much more work needs to be done on it.  Cycle~ (talk) 18:19, 23 January 2009 (UTC)
replies: text: No comments? I'll leave it as it is for the time being then.  Cycle~ (talk) 23:49, 29 January 2009 (UTC)
thread_title: New design

message: The distinguish between "wavetable synthesis" and "sample-based synthesis" seems required. As written on the article, the "wavetable synthesis" is a sound synthesis technique employing the array of single cycle waveform (i.e. table of waveforms) to change the timbre dynamically along with the time evolution, or by keyboard velocity, etc. And it may be probably categorized as a sub-category of "sample-based synthesis". 
Although the most "sample-based synthesis" are based on waveform-table lookup technique (i.e. wavetable), however, most of these does not implement the exact "wavetable synthesis" which was developed by Wolfgang Palm and Michael Mcnabb in the late-1970s. For example, Yamaha CS1x seen on above #Syntax Guide is not the wavetable synthesis but the sample-based synthesis.  The notation "wavetable" as an abbreviations of "sample-based synthesis" tend to cause many confusions.
Thus, the description on #Syntax Guide should be changed, as following:
:: Sample-based (Yamaha CS1x, Korg M1, Roland D-50, etc)
:: Wavetable (PPG Wave, etc)
best, --Clusternote (talk) 00:41, 20 February 2015 (UTC)
thread_title: Wavetable

message: I suggest that this template be edited to include "Variants" (or "Similar"), "Developed from" and "Developed into" fields similar to Template:Infobox aircraft type to more clearly describe relationships between successive or related synths that use similar technology, such as the Roland JV/XV series, Yamaha DX/TX/SY, and so forth. I realize that the lines between generations are sometimes blurry but it would provide useful information in any case. Carguychris (talk) 17:25, 12 October 2020 (UTC)
thread_title: Add fields?

message: I think the infobox link for timbrality should be changed to this page. I am familiar with timbre, but I have never heard of timbrality and the concept of having multiple "parts". When I clicked on the link though, it just took me to the page for timbre. Zackarhino (talk) 02:01, 30 May 2024 (UTC)
replies: text: Not done for now: You might want to gain consensus. Try opening a discussion in WP:MUSIC. ABG  (Talk/Report any mistakes here)  06:07, 30 May 2024 (UTC)
thread_title:  Semi-protected edit request on 30 May 2024