Cromio -
I'd wait a few weeks and see what Roland does. If they add the 1.51 waves to 2.0, your efforts to record all those waves may be for naught.
Of course, if there's a few waves that you simply can't live without - go for it!
v2?
Re: v2?
it's done!
(the easy part at least)
I've got all 342 samples from v1.51 in my computer
[wav mono 16bit 44100Hz]
now comes the more delicate task to crop the files, removing all silence from the beggining and the end...
(uncut as they are they use around 40MB)
- at a first glance I can tell you that nott all the files make perfect loops (so it will be needed to create the loop zone inside the V-Synth)
- there are several files that sound exactly the same (I suppose the idea is to make the multi-sampled patches, only I thought the samples should be different among them, well at least at a first earing they sound just the same)
- also samples like: 316 ElementMenu 1 only hive me a little sound while their info states they need a lot of memory (2.6MB, for this case) so it might not be possible to get to these menus
- I've also discovered that there are a few of them that are also in v.2 (so once again if using patches with these samples in v.2 we may save some space if we re-direct the patch to the preset sample of v.2)
(the easy part at least)
I've got all 342 samples from v1.51 in my computer
[wav mono 16bit 44100Hz]
now comes the more delicate task to crop the files, removing all silence from the beggining and the end...
(uncut as they are they use around 40MB)
- at a first glance I can tell you that nott all the files make perfect loops (so it will be needed to create the loop zone inside the V-Synth)
- there are several files that sound exactly the same (I suppose the idea is to make the multi-sampled patches, only I thought the samples should be different among them, well at least at a first earing they sound just the same)
- also samples like: 316 ElementMenu 1 only hive me a little sound while their info states they need a lot of memory (2.6MB, for this case) so it might not be possible to get to these menus
- I've also discovered that there are a few of them that are also in v.2 (so once again if using patches with these samples in v.2 we may save some space if we re-direct the patch to the preset sample of v.2)
-
realtrance
- Posts: 128
- Joined: 16:39, 8 April 2005
Re: v2?
DodgingRain,
Many's the time I've heard the cry of, "be original! use your own waves" only to listen to the results and find out that the "originality" is pretty samey, all the way around.
While I _do_ sample, edit, encode and use my own waves, I also like to have the extensively-worked waves Roland included with the original instrument. There's a lot of material in those samples to work with, and having it just lost with the OS update is not a tradeoff I'm interested in.
Besides, v2.0 really provides -- along with a sampleset more in tune with a more conventional audience -- some new "template" capabilities that I find much too standard and conventional to find useful for the way I do things.
When I program a patch from scratch, I really do it from scratch -- I don't need no stinkin' templates.
When I really want to start from nothing, I start with my own samples as well.
If you've used _all_ the elements available, intelligently, to create _one_ patch from the ground up, you'll find it's quite a bit of work, even once you're familiar with the instrument.
I'm happier to have the groundwork laid on the sampling side than on the patch construction side, basically. And happier with, say, a larger collection of noise sounds and ethnic instruments than I am with umpteen drumloop samples (which v2.0 seems to be full of) as a starting point. But, that's just my tastes.
Many's the time I've heard the cry of, "be original! use your own waves" only to listen to the results and find out that the "originality" is pretty samey, all the way around.
While I _do_ sample, edit, encode and use my own waves, I also like to have the extensively-worked waves Roland included with the original instrument. There's a lot of material in those samples to work with, and having it just lost with the OS update is not a tradeoff I'm interested in.
Besides, v2.0 really provides -- along with a sampleset more in tune with a more conventional audience -- some new "template" capabilities that I find much too standard and conventional to find useful for the way I do things.
When I program a patch from scratch, I really do it from scratch -- I don't need no stinkin' templates.
When I really want to start from nothing, I start with my own samples as well.If you've used _all_ the elements available, intelligently, to create _one_ patch from the ground up, you'll find it's quite a bit of work, even once you're familiar with the instrument.
I'm happier to have the groundwork laid on the sampling side than on the patch construction side, basically. And happier with, say, a larger collection of noise sounds and ethnic instruments than I am with umpteen drumloop samples (which v2.0 seems to be full of) as a starting point. But, that's just my tastes.
-
Watermelon
- Posts: 138
- Joined: 10:35, 16 August 2004
Re: v2?
Soundman wote:
The point is whether upgrading any software product should render any work done on previous versions unuseable.
Although I totally agree, it would have been much worse for us if Roland decided to launch the V-Synth XT with its own set of new patches (the V2 patches) and leave V-Synth with 1.51. Then we wouldn't complain about the compatibility issue, but the lack of Roland support towards V-Synth pionners
At least, now, we have the choice either to keep 1.51 (assuming these were the sounds we were really looking forward when buying teh V-Synth) or upgrade towards the new XT set. I decided to upgrade and translated the incompatible patches by looking for similar waveforms in the new OS.
The point is whether upgrading any software product should render any work done on previous versions unuseable.
Although I totally agree, it would have been much worse for us if Roland decided to launch the V-Synth XT with its own set of new patches (the V2 patches) and leave V-Synth with 1.51. Then we wouldn't complain about the compatibility issue, but the lack of Roland support towards V-Synth pionners
At least, now, we have the choice either to keep 1.51 (assuming these were the sounds we were really looking forward when buying teh V-Synth) or upgrade towards the new XT set. I decided to upgrade and translated the incompatible patches by looking for similar waveforms in the new OS.
Let them pray?
Tarquin -
What is patch no. 412 " Let me Pray" about on the V2 V Synth? Is this a rename of "Let them Pray"? Certainly sounds that way. Hope so.
Anyone else noticed this one? Is it like the original V1.5x patch?
Just noticed the manuals for the XT are available here -
http://www.roland.com/products/en/_supp ... &iCncd=690
What is patch no. 412 " Let me Pray" about on the V2 V Synth? Is this a rename of "Let them Pray"? Certainly sounds that way. Hope so.
Anyone else noticed this one? Is it like the original V1.5x patch?
Just noticed the manuals for the XT are available here -
http://www.roland.com/products/en/_supp ... &iCncd=690