Tone2 support forum

General Category => RayBlaster => Topic started by: Markus Krause on December 01, 2012, 04:10:19 PM

Title: RayBlaster feature requests
Post by: Markus Krause on December 01, 2012, 04:10:19 PM
You can request features for RayBlaster withing this thread.

We read and discuss every single request. Some requests will be included in future updates. Please note that there many different people with many different needs and there are technical restrictions.
Title: Re: RayBlaster feature requests
Post by: emotica on December 01, 2012, 08:30:20 PM
I reported a bug already earlier via the form and here is a little request, just by using the demo:

One thing that I don't like is, that it's not showing the names of the used files inside the oscillators if you use a preset, but the blank "Load Wave1" text. With a custom patch I do get the actual name of the file used. If you tweak a preset and change the wave to just realize how much better the original one used was, it could be handy to know the names. It would be interesting to know certain combination of wave-forms and filter types for some sounds. :)
Title: Re: RayBlaster feature requests
Post by: RSJ on December 02, 2012, 06:50:36 PM
Hi
I would like to have the option to change the start for both wave 1 and wave 2. It would also be nice to have end for both wave 1 and wave 2.
In the short time I have spend with RayBlaster, then Im not sure if it can loop forward? i did only hear it loop backward, so that is also a feature I would like to have if its not already there.
Title: Re: RayBlaster feature requests
Post by: silikonanswer on December 02, 2012, 07:28:55 PM
What about some tutorial video/s? Just with the basics becuase it is not the typical substractive synth.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 03, 2012, 02:01:31 PM
I always like consistency,
so how about the save favourite function that was in electraX but not in Saurus or at least in the demo of Rayblaster?

thanks
rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 03, 2012, 05:00:32 PM
Quote
In the short time I have spend with RayBlaster, then Im not sure if it can loop forward?

The loop position is defined by the LFO. Use a triangle LFO for forward-backward and a negative send level of the LFO in the Matrix to reverse the playblack.
In the tutorial section and the handboock there are several basic patches which show such setups.

Quote
What about some tutorial video/s?


If there are several people who are interested in it we will create a more detailed sound design tutorial for RayBlaster.

Quote
showing the names of the used files inside the oscillators


Gladly i was smart enough to reserve some bytes in the RayBlaster patch format for such a request. :-)
Implementing could be problematic because of possible compatibility problems in various host. I could also lead to confusion from user-side, becuase all waveforms are stored within the patches.
If you can't remember which wav you used in a patch you can also use the 'export wave' function and then reload it.
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 03, 2012, 05:08:27 PM
Quote
how about the save favourite function that was in electraX

From the technical side it is no problem to implement such a feature. I will add this if there are several users who request it.

Meanwhile you can create your own 'zvenx favourites' directory by creating a directory in 'RayBlaster_sounds'.

Example:
C:\Program files\Steinberg\VstPlugins\RayBlaster_sounds\ZvenxFavourites

Then place your favourite RayBlaster fxp files within it. The directory will show up as soon as you restart the plugin.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 03, 2012, 05:37:49 PM
Hi Markus,
I had done that with Saurus, but then you have to retype the name of the patch and navigate to the write folder almost everytime. I soon gave up that approach.

rsp
Title: Re: RayBlaster feature requests
Post by: Krokodilen on December 03, 2012, 06:53:16 PM
Hi,

I relly like the RayBlaster and especially the resynthesis feature. To smooth the use of that feature I would like to be able to set an other dir for samples rather than the default \RayBlaster_samples. I have my samples at a different disk and it takes some klicking every time to get to them.

By the way.. will my samples be saved with the patch?

Regards
K
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 03, 2012, 07:37:52 PM
Hi,

I relly like the RayBlaster and especially the resynthesis feature. To smooth the use of that feature I would like to be able to set an other dir for samples rather than the default \RayBlaster_samples. I have my samples at a different disk and it takes some klicking every time to get to them.

By the way.. will my samples be saved with the patch?

Regards
K

What i could do is that Rayblaster_samples is only selected as directory as long else no other directory has been selected to load a sample. From the aspect of usability this would make sense and could help to fasten the workflow.
RayBlaster saves all samples with the fxp file. This has several big advantages:
- patches still work even if the original wav files has moved or has been deleted
- patches do also work and sound the same on other systems
- faster loading times
- everything is in one single and compact file
Title: Re: RayBlaster feature requests
Post by: Krokodilen on December 03, 2012, 08:02:47 PM
What i could do is that Rayblaster_samples is only selected as directory as long else no other directory has been selected to load a sample. From the aspect of usability this would make sense and could help to fasten the workflow.
RayBlaster saves all samples with the fxp file. This has several big advantages:
- patches still work even if the original wav files has moved or has been deleted
- patches do also work and sound the same on other systems
- faster loading times
- everything is in one single and compact file

Hi,

and thanks for a quick reply.

Yes, I would like the suggested Dir: workflow enhancement.

I think it's great that samples are stored in the fxp file.
(I have an old Roland Fantom x and knows all abut the hassle of finding a "missing" sample... :)

Thx
K
Title: Re: RayBlaster feature requests
Post by: Krokodilen on December 04, 2012, 01:02:14 PM
Hi again..

This is so a minute detail but... the MIDI parameter for "Osc Wa" has the same name for both Osc1 and Osc2. The funktion is there but their names should read Osc1 Wa and Osc2 Wa. As is they are both named Osc1 Wa.

Thx
K
Title: Re: RayBlaster feature requests
Post by: silikonanswer on December 04, 2012, 02:59:32 PM
First of all, many thanks for this present  ;), Where should I put these files?
Title: Re: RayBlaster feature requests
Post by: zvenx on December 05, 2012, 02:37:21 PM
Not sure if this is the correct thread.....

But I just realised in RayBlaster (and will go thru some stuff in Saurus and ElectraX as well).
Markus do you play keyboards?
I just realised you don't use pitch bend in any of the patches I played from you just now in RayBlaster....
even the lead patches....... to me this is like building a piano without any pedals or a guitar where you can't bend the strings.

so my request is for Markus to use pitch blend in his patches.
rsp

edit: Seems ElectraX does have many MF patches that do use pitch bend for pitch bending, and a few in Saurus do as well......

rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 05, 2012, 04:44:20 PM
Hi zvenx,

in many of my patches for RayBlaster i used the pitchwheel as an additional bipolar modulation source in the matrix. I found it much more exciting to have two controls (pitchwheel+modwheel) which can morph the sound in realtime.
But it's as always a question of personal taste. I have noted your request for a more classic usage of the pitchwheel for my future patches.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 05, 2012, 04:57:54 PM
understood.. yes I do realise it was mapped.... but not in the classical/traditional sense......

well not a biggie as it isn't that hard to do so when I want to use the patch.....

btw and I couldn't find it in the glance at the manual, but i assume  2 steps are one semitone if you use it to modulate osc pitch?..and is 100% fine 1 semitone or..?
is that info all there in the manual and I missed it?
thanks
rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 05, 2012, 05:16:14 PM
in the matrix:

100 as send level equals 1 semitone when routed to fine
100 equals 12 halftones or one octave when routed to semi
100 equals 4 octaves (if i remember right) when routed to pitch

you can also route several times to the same target. This way you can get a larger range if you need this.
by pressing shift while you move the slider you can adjust more fine.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 05, 2012, 05:26:09 PM
thanks for the info.....

but I am sure you see my next feature request coming a mile away :-)
whereas for fine 100% makes sense.

for me the semi where then one semi is 100/12

and for pitch where 100/48 is one semi it may not be optimal unless you doing a lot of microtonal stuff.


so I would love if fine remains as it is.

semi goes integers up to 12, or even 24 if so inclined, with each integer representing a semitone

and for pitch integers up to 48 if you wish, with each integer a semitone.

for those using microtonal wouldn't the fine allow them to do what they want to do (don't use microtonal stuff so I may be completely missing elements of it)

rsp
Title: Re: RayBlaster feature requests
Post by: zvenx on December 05, 2012, 07:48:23 PM
thanks for the info.....

but I am sure you see my next feature request coming a mile away :-)
whereas for fine 100% makes sense.

for me the semi where then one semi is 100/12

and for pitch where 100/48 is one semi it may not be optimal unless you doing a lot of microtonal stuff.


so I would love if fine remains as it is.

semi goes integers up to 12, or even 24 if so inclined, with each integer representing a semitone

and for pitch integers up to 48 if you wish, with each integer a semitone.

for those using microtonal wouldn't the fine allow them to do what they want to do (don't use microtonal stuff so I may be completely missing elements of it)

rsp

I guess the problem though is these parameters are use for any modulator source and target...hmmmm

maybe a separate one like omnisphere and so many others?
rsp
Title: Re: RayBlaster feature requests
Post by: himalaya on December 06, 2012, 01:20:40 AM
Hi Richard,
Interesting that you have noted the pitch bend wheel and its unorthodox use. I actually love that the pitch bend in Rayblaster (and Saurus) can be assigned to other parameters than the traditional pitch. It's just so useful for certain patches, especially those which do not benefit from bending the pitch via the wheel. For me it's a resourceful way of having two timbre related controllers right at my fingertips. The only better way is when I have a midi controller with two mod wheels (in addition to the pitch wheel). Like on the Yamaha SY77 or Alesis Fusion. It also helps that the soft synth in question has two dedicated mod wheels pre assigned on the UI (SS springs to mind).

I've also used the pitch wheel for other parameters (perhaps more in the Saurus patches).  :)
Title: Re: RayBlaster feature requests
Post by: zvenx on December 06, 2012, 01:34:53 AM
:-)....oh trust me, I did go thru your patches too and noted they were some NEEDING pitch bend :-), but for the most parts you at least used them in almost all your lead patches.....I sometimes even use them in pads to create and atmosphere....
but if there was a matrix AND (yes I know the argument will be made no gui real estate space) have a permanent pitch bend slider as well....that would work....the slider could be set at zero, or whatever value the user/patch creator wants them to.

rsp
Title: Re: RayBlaster feature requests
Post by: himalaya on December 06, 2012, 01:59:58 AM
Yeah, with sounds which benefit from pitch bends (like leads) the pitch bend wheel was assigned in the traditional fashion. For pad I mostly like going up a 5th or a 7th, but often I find having an additional timbre related parameter instead.

Re mod matrix, during beta I thought ( and have suggested a FR ) that it would be useful for users if the initialized patch had the pitch bend pre-assigned to at least +- 2 semitones.

Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 06, 2012, 09:51:51 AM
Quote
it would be useful for users if the initialized patch had the pitch bend pre-assigned to at least +- 2 semitones.


Request will be implemented in the next update.
Title: Re: RayBlaster feature requests
Post by: HiEnergy on December 06, 2012, 04:29:08 PM
I would like to request the possibility for subfolders in the RayBlaster_waves folder for hierarchically categorizing single-cycle waves in the same way, the sounds are categorized under RayBlaster_sounds.
As I have gazillions of single-cycle waves (more that fit onto the pop-up) I wish there was a cascading pop-up.
Currently I just can't use all of them at once.
Title: Re: RayBlaster feature requests
Post by: Burkuagh on December 09, 2012, 09:05:03 PM
I love the new Sine-Hz in the mod matrix but I find my use of them somewhat limited due to them being free lfos.  I like my songs and patches to be identical every time I play them and using free lfos, for the most part, adds an undesirable level of randomness.

I would love it if they could be set to retrigger with each note.
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 10, 2012, 10:04:47 AM
To get a retriggering sine LFO:

- Select the first waveform in the LFO section
- Set LFO phase to 'Synced 360' or which start phase you want
- Select the desired frequency with 'FREQ'
Title: Re: RayBlaster feature requests
Post by: Cobi on December 10, 2012, 08:46:40 PM
Hi! As a first-time customer I'd like to congratulate the Tone2 guys on a great synth!

After a bit of experimenting, there are a few things that I think could be improved...

Firstly I would like to have a double-click to reset parameter function.. I've found that sometimes its a bit fiddly to simply reset the key follow knob for example. A simple double click would definitely quicken the workflow.

Secondly, another request would be that after selecting a sample/loop for resynthesis, for the preset arrows to cycle through the rest of the samples in the folder you last selected, rather than the buttons redirecting you to Rayblaster's default presets again.

Lastly, it would be nice to have some browse buttons for the wave select sections too, I made a quick muckup of what they could look like.. (don't laugh :D)
(http://i.imgur.com/25MEg.jpg?1)

And if those buttons were implemented then it would be good for them to cycle through the waves within the last selected folder like I suggested in my second request.  :)
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 11, 2012, 08:08:31 AM
Hello Cobi,

we've already taken care of this:
- You can use the mousewheel to cycle through the wave list selectors.
- ctrl + left click resets a parameter to the default value.
Title: Re: RayBlaster feature requests
Post by: Cobi on December 11, 2012, 01:52:42 PM
Great, thanks for the heads up Markus!
Title: Re: RayBlaster feature requests
Post by: Cobi on December 12, 2012, 02:19:25 PM
Scrolling through the wave list selectors with the mouse wheel doesn't seem to work when Rayblaster is dragged over to a second monitor. It starts working again when its dragged back to the main monitor though. Does anyone else have this problem?

I'm using Ableton Live 8 Suite 32bit, Win7.
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 12, 2012, 02:42:56 PM
Hello Cobi,

It's a known weakness of Ableton ('the Ableton focus problem') which been confirmed by the development team of Ableton. It affects various plugins from various developers on Ableton PC. It did not appear in other hosts that we tested. We can't fix it from our side, since it is a technical problem of the host and not a bug in our plugin.
The Ableton team wrote to us that they are aware of the problem and promised to adress it in a future update. Updating your Ableton to the lastet version might help to solve it.

Sometimes it helps to click on a knob first to force the focus on the plugin. Then the mousewheel might work.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 12, 2012, 06:23:47 PM
Maybe it is in this thread and I missed it, but it is my feature request for this and every tone2 synth.

Right click midi learn to cc..for every knob/slider etc

rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 12, 2012, 07:40:58 PM
Hello zvenx,

Midi learn is already available in Gladiator v2.2, v2.3 and electrax.

electrax: click on the help button

Gladiator PC : shift and leftmousebutton and ctrl
Gladiator mac: shift and lemousebutton and apple

The configuration is stored in gladiatormidi.cfg and electraxmidi.cfg. If you delete the file you will reset it to the factory settings.

Please take a look at the handbook and to this forum for the details. If you need further assistance you can also send an email to Bastiaan.

We will implement a midi learn feature in a future update of RayBlaster if enough customers request it.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 12, 2012, 07:43:58 PM
Hi Markus, will check it,
but afaik or thought I knew... it was available in the matrix....where you had access to more than the four cc's in rayblaster, but yes let me go read the help menu now and see what I have been missing. Maybe they are pre-assigned and not midi learn?

rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 12, 2012, 07:49:19 PM
update: i added more info to the previous post.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 12, 2012, 07:54:14 PM
thanks markus... will check it out now.

So Easy in ElectraX.... I either knew that and forgot or missed that......

haven't gotten the gladiator one working yet..

but would be nice in Saurus too.. I seem to recall asking for that after a demo video (Mark Mosher perhaps?) that used either Ableton or Novation stuff to circumvent that limitation.

rsp
Title: Re: RayBlaster feature requests
Post by: zvenx on December 12, 2012, 08:12:23 PM
....
Gladiator mac: shift and lemousebutton and apple
.......

I assume it is left mouse button, but I tried that and several other combinations, but I couldn't get it to work on my mac.

rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 12, 2012, 10:12:31 PM
I will take a look at this tomorrow. It is 10PM at nigth now and i need to get some sleep now.
Title: Re: RayBlaster feature requests
Post by: zvenx on December 12, 2012, 11:34:20 PM
:-)
totally undestood. I am surprised you are even responding at this hour..

Tomorrow
rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 13, 2012, 10:07:34 AM
Hello zvenx,

i examined midi learn in Gladiator. I found out that you must install Gladiator v2.3 or v2.2. In 2.4 we had to remove the feature to be compatible with 64 bit audiounits. Sorry that i posted missinformation in my previous post. It's sometimes difficult to have all updates and differences between the versions in mind.

Best Regards,
Markus
Title: Re: RayBlaster feature requests
Post by: zvenx on December 13, 2012, 12:45:44 PM
no wonder I couldn't get it to work :-)
thanks for the update Markus....

so in effect does that mean for Gladiator 2, this request is a dead issue for any updates to come?
thanks
rsp
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 13, 2012, 02:42:43 PM
Hello zvenx,

we're getting offtopic here. This thread is about RayBlaster and not Gladiator.

Gladiator v2.3 is very stable and relieable, so everyone got the free choice which version is used and noone is forced to update it.

It always depends how many customers request a feature. Beside of that there are also technical restrictions and compatibility issues with various hosts that we must deal with.

Best Regards,
Markus
Title: Re: RayBlaster feature requests
Post by: zvenx on December 13, 2012, 03:32:49 PM
Hello zvenx,

we're getting offtopic here. This thread is about RayBlaster and not Gladiator.

.......

True,
I made the request in Gladiators forum.
thanks
rsp
Title: Re: RayBlaster feature requests
Post by: Cobi on December 15, 2012, 11:03:54 AM
Hello Cobi,

It's a known weakness of Ableton ('the Ableton focus problem') which been confirmed by the development team of Ableton. It affects various plugins from various developers on Ableton PC. It did not appear in other hosts that we tested. We can't fix it from our side, since it is a technical problem of the host and not a bug in our plugin.
The Ableton team wrote to us that they are aware of the problem and promised to adress it in a future update. Updating your Ableton to the lastet version might help to solve it.

Sometimes it helps to click on a knob first to force the focus on the plugin. Then the mousewheel might work.

Ok thanks Markus, will just have to wait and see if the Ableton guys sort the problem out!
Title: Re: RayBlaster feature requests
Post by: Burkuagh on December 21, 2012, 09:35:10 AM
I would love to have some way of cycling through the "Load Wave 1" and "Load Wave 2" files other than the drop-down menu.  Preferably < > arrows like in the preset window. 
Title: Re: RayBlaster feature requests
Post by: IngoWeidner on December 21, 2012, 10:40:38 AM
I would love to have some way of cycling through the "Load Wave 1" and "Load Wave 2" files other than the drop-down menu.  Preferably < > arrows like in the preset window. 
You could use the mouse wheel at the current version.


Ingo
Title: Re: RayBlaster feature requests
Post by: Ajnariom on January 28, 2013, 03:43:33 PM
...
Quote
What about some tutorial video/s?


If there are several people who are interested in it we will create a more detailed sound design tutorial for RayBlaster.
...

I also ask about tutorial videos.
Title: Re: RayBlaster feature requests
Post by: Markus Krause on January 29, 2013, 01:44:17 PM
Here is a feature overview video:

http://www.tone2.com/html/impulse_modelling_synthesis__i.html (http://www.tone2.com/html/impulse_modelling_synthesis__i.html)
-----------------------------------

The handbook has a section where the tutorial patches are explained. Make sure that you don't miss it.

--------------

If there is a demand on a tutorial video for sound design with RayBlaster we can record something.
Title: Re: RayBlaster feature requests
Post by: Cobi on February 06, 2013, 06:10:07 PM
+1 for some tutorial videos.

Especially regarding the resynthesis and loop resynthesis features.

Another feature request: When I'm going through samples/loops to resynthesize I think its quite a clunky slow setup that you need to go through for every different sample you want use.. Having to click 'File' then 'Resynthesis' then 'Ok' then browsing to find your sample and then clicking 'Open' and then 'Ok' yet again isn't great for workflow..

I think it would be much better if you could cycle through the samples in the last selected folder by using the main preset arrows (An idea which I suggested in my first post).. that way users could make a folder of all the sounds they might want to resynth. Another way to improve this would be to be able to drag and drop audio files directly onto Rayblaster to automatically resynthesize.
Title: Re: RayBlaster feature requests
Post by: lih on February 12, 2013, 02:17:36 AM
I've been enjoying this synth immensely, and between it and Electra X, all my singers are really loving the Tone2 sound at my studio.

Couple features would really help my work flow when using many instances in a project, as I'm almost always creating new sounds with it.

a.  Rayblaster tends to clip easily requiring multiple lowering of the volume knob to keep it in check, and even then I'll think I have it set low enough, come back later and find its still clipping, but then my master volume is too low.  I would really love a brick wall limiter put it before the FX section.

b.  Probably been mentioned before, but Midi learn / cc support for automation would help workflow a lot.  I'm having to print audio and then automate the volume to keep my mixes tight.  Its a small thing, but would save me some precious time in the studio.

Anyway, kudos to you Markus for always pushing the envelope.  I could not make the music I make without Tone2 products.

Title: Re: RayBlaster feature requests
Post by: Burkuagh on July 28, 2013, 06:47:05 AM
The current methods in Rayblaster for transposing up and down octaves all change the tonal characteristics of the sound.  Rayblaster could really use something that works like transposing the incoming midi information in the way that it works on a controller keybord when you shift it up and down octaves.
Title: Re: RayBlaster feature requests
Post by: Burkuagh on July 31, 2013, 05:10:50 AM
Also I would love drag-and-drop functionality for loading .wav files into the "Load Wave" sections on the oscillators.

Currently the mouse wheel will only let you scroll through the default set of waves that came with Ray Blaster.  It would be wonderful if it could be changed to scroll through the .wav files in the most recently opened folder rather than opening a windows file-selection folder.

And lastly it would be extremely useful if Ray Blaster would store the file name of the .wav that was resynthesized.
Title: Re: RayBlaster feature requests
Post by: Markus Krause on July 31, 2013, 08:37:20 AM
Hello Burkuagh,

Drag & drop is already included. I don't remember if it also supported on the Mac, but i just successfully loaded a wav to the RayBlaster OSC on on my PC. You must drop it in the middle of the OSC window.

The factory waveforms are stored in VstPlugins/RayBlaster_waves. You can add/delete/modify the content for your personal needs. RayBlaster updates the listing of the directory when you load the plugin.
RayBlaster works well with very short, percussive samples.

Cheers!
Title: Re: RayBlaster feature requests
Post by: Burkuagh on August 01, 2013, 07:45:46 AM
Drag-and-drop only works on "Load Wave 1" for me.  Is there away to drop a .wav file on the "Load Wave 2"?
Title: Re: RayBlaster feature requests
Post by: Markus Krause on August 01, 2013, 08:39:20 AM
Usually only wave1 is used in the sounds. That's why drag&drop is limited to it. I will examine if i find a comfortable way to support a more detailed drag&drop for a future update.
Title: Re: RayBlaster feature requests - LPF section after sound engine
Post by: rez_azel on August 04, 2013, 05:46:39 PM
I like the resynthesis feature. But I think the fact that, if you resynthesize complex waveforms, the formant knob let's you only control the pitch but not the cutoff, dramatically limits the versatility of Rayblaster... (the damp and lo cut buttons are not suited at all as LPF replacements). PLEASE include at least a traditional lowpass 12 db if you ever consider an update... Thank you!
Title: Re: RayBlaster feature requests
Post by: Burkuagh on August 14, 2013, 04:13:58 PM
I would love some utility functions added for the mod matrix.  Matrix slot numbers next to each line just fort the sake of ease and clarity, mute buttons for each slot so you can toggle them off and on without having to lose your values or settings, move up and down for organizational purposes, And I would love some ways to control multiple parameters with single controllers without having to, something like a destination "all following slots" or "matrix 1-5", "matrix 6-10" ,and "matrix 11-15", or page 1, 2 or 3 or w/e would be a lot of fun to play with.  Of course I would love these for all of your synths not just ray blaster.

Just some thoughts. 

Also a swap FX order would be handy.
Title: Re: RayBlaster feature requests
Post by: AnalogSignal on December 24, 2013, 10:14:01 PM
After programming a lot of Rayblaster patches, I have some requests. I think they have been mentioned before but I'd like to add my vote:

1. Display the name of the Wave file when loading a patch.

2. Replace Patch - Instead of hitting Save and picking the same filename and confirming overwrite, I would like a one click way of doing this.
 
3. I'm constantly watching out for clipping. It would be very nice to have a built-in limiter to prevent this.

Actually I am wondering if clipping really happens internally or is it just warning that it is outputting more than 0 db which could cause clipping externally?

Great synth. I hope it is updated in the future.
Title: Re: RayBlaster feature requests
Post by: Markus Krause on December 27, 2013, 10:21:09 AM
Hello,

the 'clipping' display is just a warning. It has no effect on the sound. It's purpose is to inform the sound designer that a sound could be too loud.
Title: Re: RayBlaster feature requests
Post by: AnalogSignal on December 27, 2013, 10:26:46 AM
the 'clipping' display is just a warning. It has no effect on the sound. It's purpose is to inform the sound designer that a sound could be too loud.

Thanks! Good to know.  :)
Title: Re: RayBlaster feature requests
Post by: exmatproton on February 02, 2015, 11:14:23 PM
Since the last comment is over 120 days old:

Is midi learn coming to the rayblaster??
Title: Re: RayBlaster feature requests
Post by: Markus Krause on February 06, 2015, 10:16:32 AM
It is possible that we will add midi learn to the next update.
Title: Re: RayBlaster feature requests
Post by: exmatproton on April 26, 2016, 01:01:21 PM
It is possible that we will add midi learn to the next update.

Well, it is have been for more then a year. Is Rayblaster getting some proper MIDI learn function?
Title: Re: RayBlaster feature requests
Post by: Markus Krause on April 26, 2016, 03:27:40 PM
Hello Exmatproton,

After the Icarus release we'll first have to update the Mac version of Nemesis to v1.1, because this one has higher priority.

For the Icarus engine we have also re-developed the Midi learn feature. Please take a look at this one and give us some feedback if it works as expected for you. If everyone is happy we can adopt the concept for RayBlaster.

Best Regards,
Markus
Title: Re: RayBlaster feature requests
Post by: exmatproton on April 26, 2016, 05:49:06 PM
Hello Exmatproton,

After the Icarus release we'll first have to update the Mac version of Nemesis to v1.1, because this one has higher priority.

For the Icarus engine we have also re-developed the Midi learn feature. Please take a look at this one and give us some feedback if it works as expected for you. If everyone is happy we can adopt the concept for RayBlaster.

Best Regards,
Markus

Hmmm. i think it is kinda weird i'll have to buy or demo Icarus, in order to get midi learn on Rayblaster. It is such a nice synth. It is getting way to little attention, IMHO.

And if what people don;t like the midi learn function in Icarus? Will Rayblaster's midi learn have to wait untill the midi learn function in Icarus is good (enough)? Weird....
Title: Re: RayBlaster feature requests
Post by: Markus Krause on April 28, 2016, 05:36:21 PM
There seems to be a missunderstanding. Sorry about beeing not precise enough with expressing myself.
So far you and another customer are the only persons who requested Midi learn for RayBlaster. If i implement this feature exclusively for you, it's half of a day of additional work for me (Please note, that I don't get paid for this). If i spend time i want to make sure that you're happy with the result. That's why i ask you to take a look at Icarus if you like the new midi learn method. You don't have to buy anything - just take a look and give me feedback. This should make sure that i don't waste time and it should also make sure that you're happy with what you will get in the next update.


Please do also note the last update:

November 2015 RayBlaster (PC) has been updated to v1.1

Enhancements:

- Windows 10 and Windows 8 compatibility
- Enhanced stability
- Enhanced compatibility
- More easy installation
- Several other small enhancements
- Updated standalone version
- Polished some graphics

Changes:

- Less aggressive mouse focus by default

Bug fixes:

- Fixed a rarely appearing crash


Download links:

https://www.tone2.com/update/Tone2_RayBlaster_PC_32bit.zip
https://www.tone2.com/update/Tone2_RayBlaster_PC_64bit.zip
https://www.tone2.com/update/Tone2_RayBlaster_Mac.pkg
Title: Re: RayBlaster feature requests
Post by: exmatproton on April 30, 2016, 01:16:43 AM
There seems to be a missunderstanding. Sorry about beeing not precise enough with expressing myself.
So far you and another customer are the only persons who requested Midi learn for RayBlaster. If i implement this feature exclusively for you, it's half of a day of additional work for me (Please note, that I don't get paid for this). If i spend time i want to make sure that you're happy with the result. That's why i ask you to take a look at Icarus if you like the new midi learn method. You don't have to buy anything - just take a look and give me feedback. This should make sure that i don't waste time and it should also make sure that you're happy with what you will get in the next update.


Please do also note the last update:

November 2015 RayBlaster (PC) has been updated to v1.1

Enhancements:

- Windows 10 and Windows 8 compatibility
- Enhanced stability
- Enhanced compatibility
- More easy installation
- Several other small enhancements
- Updated standalone version
- Polished some graphics

Changes:

- Less aggressive mouse focus by default

Bug fixes:

- Fixed a rarely appearing crash


Download links:

https://www.tone2.com/update/Tone2_RayBlaster_PC_32bit.zip
https://www.tone2.com/update/Tone2_RayBlaster_PC_64bit.zip
https://www.tone2.com/update/Tone2_RayBlaster_Mac.pkg


Thank you for explaining these details.
Title: Re: RayBlaster feature requests
Post by: exmatproton on June 10, 2016, 02:31:32 PM
I tried the beta of Icarus:

Please consider adding the midi learn function from Icarus to all Tone2 synths. It works and it would be a shame if Rayblaster in particular won't get this feature.
Title: Re: RayBlaster feature requests
Post by: Markus Krause on June 10, 2016, 05:56:08 PM
Hello exmatproton,

your request for Midi learn has been noted.

Best Regards,
Markus
Title: Re: RayBlaster feature requests
Post by: exmatproton on June 11, 2016, 03:52:35 PM
Hello exmatproton,

your request for Midi learn has been noted.

Best Regards,
Markus

Nice! + props on Icarus btw. Some great tools in there to shape the sound!
Title: Re: RayBlaster feature requests
Post by: rez_azel on September 30, 2016, 11:09:54 AM
Just a small request/idea for this fantastic sound creation tool:
(just in case nobody else requested this yet)
The patch names font size should automatically resize,
so longer files names fit in the display / are displayed fully and not cut of left and right. Would be nice :)

Title: Re: RayBlaster feature requests
Post by: Encore on August 08, 2017, 04:32:33 PM
Hello,

my request is not linked to RayBlaster  in particular but to - ALL -  your VST synths in general but as RayBlaster is my preferred one, at the moment, I am posting here... ;o)

I am currently sorting all my presets in order to arrange them by type of sound (Bass, Leads,etc) and reduce the number of sub-folders in the xxx_sounds directories as some third party libraries of presets are mixing all their sound together in the same directory. In order to do this, I needed to listen each sound before moving it in the most appropriate directory.
So I am opening the synth side by side with a file explorer and move each preset in the appropriate sound directory after listening it from the synth itself. It is a fastidious work but not a big deal compared to the result.

While doing this I remarked that when dragging a FXP preset over the synth, the mouse cursor is changing to a "+" sign so I started to think : "Great ! I can drop the FXP directly to the synth to change its current preset !" ...but unfortunately it is not the case. (I am using MS Windows 10 64bits, so I do not know if this is the same for the MAC.)

Do you think it could be feasible to support this drag & drop feature for FXP presets please in a generic way in all your synth ?
Even in a particular zone of the synth if it is too complicated to make the whole GUI "FXP-drop-sensitive": i.e. the browser/preset selection rectangle zone which is usually existing in all your VST synth...

I though it would be "simpler" to implement this rather than asking you to implement a way to move sounds directly form the synth browser between sound folders/categories for - ALL -  your VST synths as each synth preset browser could be implemented in a different way internally I guess.

Thanks in advance for your answer.
Best regards, Eric
Title: Re: RayBlaster feature requests
Post by: Markus Krause on August 09, 2017, 04:17:01 PM
Hello Encore,

RayBlaster2 already supports drag&drop for sample import. If you drag&drop a wav file to the oscillator's waveform display it will load it.

Drag & drop for fxp files is currently not supported, since noone asked for this so far. We will examine if it is possible to include it in a future update.

Best Regards,
Markus
Title: Re: RayBlaster feature requests
Post by: Encore on August 14, 2017, 01:43:03 PM
Hello Markus,

 thanks a lot for your answer.
Hoping someone else will ask too for this feature.

Best regards, Eric