User Interface
Hi John
My research and experience has shown me that bi/multi phospor Lifetime LED's are worth looking at. They can give you between 6000 to 10000 hours of use. this is based on research by T. Nakamura *, K. Katayama, H. Mori, S. Fujiwara, who have been working with lifetime LED's for some years now. These ZnSe-based LED produce a pretty bright light with a long lifetime in hours.
I don't know where you are in your production scope, but the use of a silicon-rubberized type tactile surface for both knobs and the mob and pitch wheel can be of good use. It would give you an almost seemless touch, with the ability to withstand hours of torture,heat(venue dependant) and temperature changes.
I am really looking forward to not only a sonically superior sounding, but a superior built machine.
My research and experience has shown me that bi/multi phospor Lifetime LED's are worth looking at. They can give you between 6000 to 10000 hours of use. this is based on research by T. Nakamura *, K. Katayama, H. Mori, S. Fujiwara, who have been working with lifetime LED's for some years now. These ZnSe-based LED produce a pretty bright light with a long lifetime in hours.
I don't know where you are in your production scope, but the use of a silicon-rubberized type tactile surface for both knobs and the mob and pitch wheel can be of good use. It would give you an almost seemless touch, with the ability to withstand hours of torture,heat(venue dependant) and temperature changes.
I am really looking forward to not only a sonically superior sounding, but a superior built machine.
-
- Site Admin
- Posts: 2002
- Joined: Sat Apr 07, 2007 3:00 am
- Contact:
Hi All,
Today, for the first time, I brought the Solaris prototype over to a person who is pretty experienced in working with synthesizers, but had no experience with my Scope plug-in of Solaris. (If you know the plug-in, you already know most of the hardware's functionality and structure).
I was very interested to get his feedback, as often times we are too 'intimate' with a design, and can overlook things, or not consider some obvious points, etc. I'm happy to say that he was able to grasp the layout and structure fairly quickly, but of course, I was there to give an in-person tutorial, too. I hope to post some basic videos soon giving a similar 'peek' at the way Solaris works, since most of the potential user base so far are people who don't have a Scope DSP system, and would appreciate a more detailed look at the User Interface.
(This person's online name is 'Carbon111', and perhaps I can get him to candidly share some of his impressions with the Forum readers here.)
Edit Update: Looks like carbon111 already posted in 2 places (same review). You can take a look here, plus other comments:
http://www.vintagesynth.org/phpBB2/view ... hp?t=32155
He also put something on matrixsynth.com, but since this site constantly gets updated and added to, you may have to scroll down to see it: http://matrixsynth.blogspot.com/
Not sure how he got physical modeling added in there...unless he's referring to the tube/comb filter use for plucked string-type sounds.
Today, for the first time, I brought the Solaris prototype over to a person who is pretty experienced in working with synthesizers, but had no experience with my Scope plug-in of Solaris. (If you know the plug-in, you already know most of the hardware's functionality and structure).
I was very interested to get his feedback, as often times we are too 'intimate' with a design, and can overlook things, or not consider some obvious points, etc. I'm happy to say that he was able to grasp the layout and structure fairly quickly, but of course, I was there to give an in-person tutorial, too. I hope to post some basic videos soon giving a similar 'peek' at the way Solaris works, since most of the potential user base so far are people who don't have a Scope DSP system, and would appreciate a more detailed look at the User Interface.
(This person's online name is 'Carbon111', and perhaps I can get him to candidly share some of his impressions with the Forum readers here.)
Edit Update: Looks like carbon111 already posted in 2 places (same review). You can take a look here, plus other comments:
http://www.vintagesynth.org/phpBB2/view ... hp?t=32155
He also put something on matrixsynth.com, but since this site constantly gets updated and added to, you may have to scroll down to see it: http://matrixsynth.blogspot.com/
Not sure how he got physical modeling added in there...unless he's referring to the tube/comb filter use for plucked string-type sounds.
-
- Posts: 76
- Joined: Mon Jan 21, 2008 4:07 am
- Location: Greece
- Contact:
I second that, all the little details will eventually make the difference. Good quality knobs and buttons, the keyboard, the LCD contrast, the illuminosity of the LEDs, and the quality of the chassis as a whole.I am really looking forward to not only a sonically superior sounding, but a superior built machine.
Btw, I am not sure about the 8 + 8 arrangement beneath the main display. Maybe it will be difficult to adjust something in the upper row, the Andromeda has a similar arrangement but it's very ergonomic because it's not so dense, arranged in this "wavy" pattern.
-
- Site Admin
- Posts: 2002
- Joined: Sat Apr 07, 2007 3:00 am
- Contact:
-
- Posts: 76
- Joined: Mon Jan 21, 2008 4:07 am
- Location: Greece
- Contact:
-
- Site Admin
- Posts: 2002
- Joined: Sat Apr 07, 2007 3:00 am
- Contact:
Rotary encoders
Hi John,
In sonicstate.com's Solaris video there are some sequences where you turn Solaris's knobs. At 8:24 it seems you have to turn the knob quite a lot to make a large parameter change. This leads me to wonder about the resolution of the rotary encoders. What is their "physical" resolution (i.e. how many impulses per 360 deg)?
How does Solaris handle the encoder impulses? Is there a constant relation between encoder movement and parameter range (e.g. 360 deg to cover the parameter's full range)?
In performance situations I think a static encoder response with 1 revolution coverering the full parameter range is preferable. OTOH, when programming the synth you want maximum parameter resolution. This can be accomplished by using not only the angular velocity but also the acceleration of the encoder when translating knob movement into parameter values. This scheme can be described as dynamic encoder response. Does Solaris use acceleration sensing for its encoders?
If the encoder response can be switched between static and dynamic, the user can optimize Solaris's front panel for performance use as well as sound design. Can this be done on Solaris?
In sonicstate.com's Solaris video there are some sequences where you turn Solaris's knobs. At 8:24 it seems you have to turn the knob quite a lot to make a large parameter change. This leads me to wonder about the resolution of the rotary encoders. What is their "physical" resolution (i.e. how many impulses per 360 deg)?
How does Solaris handle the encoder impulses? Is there a constant relation between encoder movement and parameter range (e.g. 360 deg to cover the parameter's full range)?
In performance situations I think a static encoder response with 1 revolution coverering the full parameter range is preferable. OTOH, when programming the synth you want maximum parameter resolution. This can be accomplished by using not only the angular velocity but also the acceleration of the encoder when translating knob movement into parameter values. This scheme can be described as dynamic encoder response. Does Solaris use acceleration sensing for its encoders?
If the encoder response can be switched between static and dynamic, the user can optimize Solaris's front panel for performance use as well as sound design. Can this be done on Solaris?
Encoders
Please, let me refer to the Xpander discussion group at
http://launch.groups.yahoo.com/group/xpantastic
Here are their information related to encoders:
> Hi! For the encoder you can try here:
> http://www.rs-components.com/
> There are many type of rotary encoders. Take a look at 265-2906 (RS
> code). This is a horizontal, endless rotary encoder with 30 stops/15
> impulses.
> I think it's quite the same of the Xpander
> I've found this rotary encoder: ALPS STEC16B02, a 16mm horizontal
> encoder,
> with 24 detents, 6mm axe...
> You can find it in the RS electronics or in the Distrelec catalog. I think
> they are the same of the original one
http://launch.groups.yahoo.com/group/xpantastic
Here are their information related to encoders:
> Hi! For the encoder you can try here:
> http://www.rs-components.com/
> There are many type of rotary encoders. Take a look at 265-2906 (RS
> code). This is a horizontal, endless rotary encoder with 30 stops/15
> impulses.
> I think it's quite the same of the Xpander
> I've found this rotary encoder: ALPS STEC16B02, a 16mm horizontal
> encoder,
> with 24 detents, 6mm axe...
> You can find it in the RS electronics or in the Distrelec catalog. I think
> they are the same of the original one
Yamaha 01x rotary encoders
Xpander encoders are fairly large, but for example 01x has got a row of smaller rotary encoders. They are located just under the display. Please, see the Yamaha 01X Demo by Bert Smorenburg at
http://www.youtube.com/watch?v=U6bwiz2ta4s
Check especially the following positions:
2:06
2:22
2:59
A nice feature in 01X's encoders is that you can set the default value by just pushing on top of the encoder. Secondly, the encoders are speed-sensitive, i.e., the quicker you turn them the quicker will the values change in comparison to the linear speed. Third, pressing a shift button will allow the values change even more rapidly, or, to activate a second function.
Cheers,
Tiitu.
http://www.youtube.com/watch?v=U6bwiz2ta4s
Check especially the following positions:
2:06
2:22
2:59
A nice feature in 01X's encoders is that you can set the default value by just pushing on top of the encoder. Secondly, the encoders are speed-sensitive, i.e., the quicker you turn them the quicker will the values change in comparison to the linear speed. Third, pressing a shift button will allow the values change even more rapidly, or, to activate a second function.
Cheers,
Tiitu.
Last edited by Tiitu on Wed Jan 23, 2008 10:58 pm, edited 1 time in total.
-
- Site Admin
- Posts: 2002
- Joined: Sat Apr 07, 2007 3:00 am
- Contact:
I checked with my coder about this, and here's what he had to say:
"I implemented an acceleration sensing for the knobs, however, I have an internal integer value for each parameter, some go from -1000 to 1000 and others from 0 to 127, etc...so now it's difficult to have a knob routine that's suitable for all. Once we have all parameter ranges fixed, we either try to make all parameters internally about the same range, or I can have different routines for different ranges. Now we have some parameters that are borrowed from MIDI, and others that display in their "natural" values. For example, the DADSR is in seconds, but the mod amount from -63 to 63, whatever that means...So after fixing all parameter types, I will adjust the knob accelerator."
john b.
"I implemented an acceleration sensing for the knobs, however, I have an internal integer value for each parameter, some go from -1000 to 1000 and others from 0 to 127, etc...so now it's difficult to have a knob routine that's suitable for all. Once we have all parameter ranges fixed, we either try to make all parameters internally about the same range, or I can have different routines for different ranges. Now we have some parameters that are borrowed from MIDI, and others that display in their "natural" values. For example, the DADSR is in seconds, but the mod amount from -63 to 63, whatever that means...So after fixing all parameter types, I will adjust the knob accelerator."
john b.
Hi John,
If the range of 'sound variation' is not too different in case of different parameters, then the normalized internal range is a good idea. On the other hand, using the original ranges is more straightforward and you can do the required transformation from 500 to 63, for example,, in the sub-routine. But, in some cases a different internal velocity curve may be required. This can be programmed later, in order to normalize the user experience, too.
... Now, it occurred to me, if I don't remember wrong, that pushing and rotating the 01X enconders, increased the speed a lot. Double function encoders like these can be quite useful in many other purposes, too. Sliders, on the other hand, are sometimes better, because they allow you to see and visually remember the settings. And, you can change 10+ parameters at the same time with your fingers, instead of rotating only two knobs at a time! I think that's why Korg selected them in their M3 keyboard instead of the knobs (not endless rotary) used in their earlier Karma keyboard.
A different kind of parameter control (just for 'brain storm'):
http://www.vintagesynth.com/roland/pgs.shtml#pg1000
With a PG-1000 you can change all the parameters of a D-50 keyboard as well as the D-550 rack module! The size of the PG-1000 controller is approximately 40cm x 30cm x 4cm. The sliders cannot ofcourse replace endless rotary encoders.
...
Recording parameter changes could be a useful function in order to make the sound more living and performances repeatable. Maybe this is something that can be done already, or, is better to leave to DAW.
Cheers,
Tiitu.
If the range of 'sound variation' is not too different in case of different parameters, then the normalized internal range is a good idea. On the other hand, using the original ranges is more straightforward and you can do the required transformation from 500 to 63, for example,, in the sub-routine. But, in some cases a different internal velocity curve may be required. This can be programmed later, in order to normalize the user experience, too.
... Now, it occurred to me, if I don't remember wrong, that pushing and rotating the 01X enconders, increased the speed a lot. Double function encoders like these can be quite useful in many other purposes, too. Sliders, on the other hand, are sometimes better, because they allow you to see and visually remember the settings. And, you can change 10+ parameters at the same time with your fingers, instead of rotating only two knobs at a time! I think that's why Korg selected them in their M3 keyboard instead of the knobs (not endless rotary) used in their earlier Karma keyboard.
A different kind of parameter control (just for 'brain storm'):
http://www.vintagesynth.com/roland/pgs.shtml#pg1000
With a PG-1000 you can change all the parameters of a D-50 keyboard as well as the D-550 rack module! The size of the PG-1000 controller is approximately 40cm x 30cm x 4cm. The sliders cannot ofcourse replace endless rotary encoders.
...
Recording parameter changes could be a useful function in order to make the sound more living and performances repeatable. Maybe this is something that can be done already, or, is better to leave to DAW.
Cheers,
Tiitu.
Who is online
Users browsing this forum: No registered users and 32 guests