£2200. shipping in January (probably!)
https://www.synclavier.com/synclavier-regen/
Synclavier Regen
- Jackjackdaw
- Posts: 1468
- Joined: 12 Jan 2019
I watched the Loopop video on this. It seems to me such a silly idea. Back in the day they were dying to get the synth inside the computer, now we have the synth in the computer they bring it back out and stick it in a box, with no computer editor and charge an arm and a leg for it.
Yeah, I know what you are saying. There are two real advantages to running software in a dedicated hardware box:Jackjackdaw wrote: ↑01 Nov 2022I watched the Loopop video on this. It seems to me such a silly idea. Back in the day they were dying to get the synth inside the computer, now we have the synth in the computer they bring it back out and stick it in a box, with no computer editor and charge an arm and a leg for it.
1. It's OS agnostic. You can turn it on in 3 years time and not have to worry about whether it is compatible with your latest PC/Mac setup or have to hunt around for the unlock code because it has lost its authorisation.
2. It (normally!) has loads of dedicated controls so you can get hands on with it.
It's this latter point that Synclavier seem to have missed. Adding a handful of knobs that automatically map to whatever function you have on the screen would have been very cheap and easy to do. I'm imagining that they'll launch a Pro version with knobs and maybe a keyboard and, surely, a PC editor is on the way. But it's just nice to see the Synclavier brand back in the market. It's also nice to see outputs on balanced XLR connectors - perhaps a clue as to their target market, along with the price of course...
- Jackjackdaw
- Posts: 1468
- Joined: 12 Jan 2019
Fair points. And if you really love the Synclavier then maybe it has an appeal.
UI RANT:
Synclavier never had the UI figured out. Back when I was the “Fairlight guy” in Nashville, Synclavier offered me free training in hopes of selling a system to the studio where I worked. I had learned the CMI basics in a three day training session. I studied Synclav for 6 weeks and never could make any music on it.
It claimed to be superior to CMI because it had the hardware interface, but in practice they kept changing functions and moving them around (weekly updates in some cases, which turns out are not always a good thing). One ‘final straw’ example was the explanation for the CHORUS effect. There was a dedicated CHORUS button on the front panel, so simple right? However, they started using that for something else, and you had to press a different button for CHORUS. It get’s worse - the button showed CHORUS as active when it was flashing mostly off (or on, can’t remember!). Not when it was on, or off, or flashing - you had to remember if it was ON when it was flashing mostly on or mostly off (flashing regularly had a DIFFERENT function/meaning).
So all the effort and advantage into a hardware interface was erased because you had to REMEMBER so many workarounds and light patterns that it was FAR more difficult to work with than the CMI with it’s 100% software interface (and light pen!). This was likely the first time I REALLY experienced the software advantage for complex systems.
Of course I could not recommend the studio purchase of the Synclavier system after that experience, probably the exact opposite of what they had hoped would happen.
Side note – at that same time period I had also learned the SSL, which WAS a great integration of hardware and software which was done right. When they updated things they had a solid foundation to build on, meaning it was obvious they had planned for new features in such a way as to not ‘break’ existing features when added, unlike the Synclavier!
Synclavier never had the UI figured out. Back when I was the “Fairlight guy” in Nashville, Synclavier offered me free training in hopes of selling a system to the studio where I worked. I had learned the CMI basics in a three day training session. I studied Synclav for 6 weeks and never could make any music on it.
It claimed to be superior to CMI because it had the hardware interface, but in practice they kept changing functions and moving them around (weekly updates in some cases, which turns out are not always a good thing). One ‘final straw’ example was the explanation for the CHORUS effect. There was a dedicated CHORUS button on the front panel, so simple right? However, they started using that for something else, and you had to press a different button for CHORUS. It get’s worse - the button showed CHORUS as active when it was flashing mostly off (or on, can’t remember!). Not when it was on, or off, or flashing - you had to remember if it was ON when it was flashing mostly on or mostly off (flashing regularly had a DIFFERENT function/meaning).
So all the effort and advantage into a hardware interface was erased because you had to REMEMBER so many workarounds and light patterns that it was FAR more difficult to work with than the CMI with it’s 100% software interface (and light pen!). This was likely the first time I REALLY experienced the software advantage for complex systems.
Of course I could not recommend the studio purchase of the Synclavier system after that experience, probably the exact opposite of what they had hoped would happen.
Side note – at that same time period I had also learned the SSL, which WAS a great integration of hardware and software which was done right. When they updated things they had a solid foundation to build on, meaning it was obvious they had planned for new features in such a way as to not ‘break’ existing features when added, unlike the Synclavier!
Selig Audio, LLC
Hehe. Great Rant.selig wrote: ↑01 Nov 2022UI RANT:
Synclavier never had the UI figured out. Back when I was the “Fairlight guy” in Nashville, Synclavier offered me free training in hopes of selling a system to the studio where I worked. I had learned the CMI basics in a three day training session. I studied Synclav for 6 weeks and never could make any music on it.
It claimed to be superior to CMI because it had the hardware interface, but in practice they kept changing functions and moving them around (weekly updates in some cases, which turns out are not always a good thing). One ‘final straw’ example was the explanation for the CHORUS effect. There was a dedicated CHORUS button on the front panel, so simple right? However, they started using that for something else, and you had to press a different button for CHORUS. It get’s worse - the button showed CHORUS as active when it was flashing mostly off (or on, can’t remember!). Not when it was on, or off, or flashing - you had to remember if it was ON when it was flashing mostly on or mostly off (flashing regularly had a DIFFERENT function/meaning).
So all the effort and advantage into a hardware interface was erased because you had to REMEMBER so many workarounds and light patterns that it was FAR more difficult to work with than the CMI with it’s 100% software interface (and light pen!). This was likely the first time I REALLY experienced the software advantage for complex systems.
Of course I could not recommend the studio purchase of the Synclavier system after that experience, probably the exact opposite of what they had hoped would happen.
Side note – at that same time period I had also learned the SSL, which WAS a great integration of hardware and software which was done right. When they updated things they had a solid foundation to build on, meaning it was obvious they had planned for new features in such a way as to not ‘break’ existing features when added, unlike the Synclavier!
Back in the day I always wanted to get my grubby paws on a Fairlight or a Synclavier. The closest I got was to be in the same room as a powered down CMI. The guy I was with refused point blank to turn it on, because he knew he'd never get me off it, even though I didn't know what to do with it. And that's the only reason I didn't become the next Thomas Dolby.
- integerpoet
- Posts: 845
- Joined: 30 Dec 2020
- Location: East Bay, California
- Contact:
I keep "looking at" (thinking about buying) hardware and thinking these thoughts.selig wrote: ↑01 Nov 2022There was a dedicated CHORUS button on the front panel, so simple right? However, they started using that for something else, and you had to press a different button for CHORUS. It get’s worse - the button showed CHORUS as active when it was flashing mostly off (or on, can’t remember!). Not when it was on, or off, or flashing - you had to remember if it was ON when it was flashing mostly on or mostly off (flashing regularly had a DIFFERENT function/meaning).
As soon as the box get complicated enough to be interesting, it starts having these problems.
Menu diving being another.
Hardware interface obviously feels good.
Maybe each knob/switch/button should have its own dedicated little screen.
Then the designers wouldn't be forced to commit to the hardware configuration too soon.
And I'm sure that wouldn't be expensive at all.
- Shocker: I have a SoundCloud!
- crimsonwarlock
- Posts: 2467
- Joined: 06 Nov 2021
- Location: ##########
So... if you remove the badge and this thing was launched without leaning on legacy I am not sure I'd have given it more than a passing glance. Yes there are possibly some really sweet and unique ideas hidden in there, but the whole UX just seems like it was designed by someone that doesn't create sounds and hasn't touched anything electronic in say 30 years to understand that it should be obvious what to do next. No manual needed.
I watched Loopop explain the journey for creating sounds and it's a spiders web of what appears to be random button pressing. Am I missing something here? Am I being overly negative. When you watch say Loopops video on the ASM Hydrasynth you instantly get it and say I want one. This just leaves me cold... thinking I'd be smacking it one before I even manage to make my first patch.
Maybe im not the target audience?
Sorry.
I watched Loopop explain the journey for creating sounds and it's a spiders web of what appears to be random button pressing. Am I missing something here? Am I being overly negative. When you watch say Loopops video on the ASM Hydrasynth you instantly get it and say I want one. This just leaves me cold... thinking I'd be smacking it one before I even manage to make my first patch.
Maybe im not the target audience?
Sorry.
Check my Soundcloud:
pricey !but i guess you get a loy for the money.
Reason 12 ,gear4 music sdp3 stage piano .nektar gxp 88,behringer umc1800 .line6 spider4 30
hear scince reason 2.5
hear scince reason 2.5
-
- Information
-
Who is online
Users browsing this forum: Rising Night Wave and 5 guests