I can follow the most points of view here when changing my point of view. No bitterness about this topic (but maybe 'bout that creamware-issue - they'd deserve a better place in audio-equip worldwide - even if their software is not bugfree until today and wasn't with version 1.0).
In any way (even with official made private-fun-freeware) the consumer is the king and I personally will do my best to avoid any problems for any user especially when I hear of any problem (when I don't hear and for myself experience no problems I'm not able to correct anything) which occures & therefore will title all futuredevices not tested to the max as betas, which should avoid the problem of someone thinking: 'Hey, this device looks like it should fit my needs for this and that and I'll use it live without testing myself.'
It's good to communicate these things! From my first impression it would be just more helpfull to discuss a specific case while I see none until now, because I do feel responsible for what is happening with things I make public.
Martin
Betâ devices section !
I wouldn't exactly call it bitterness ...a little bit defensive possibly.
I actually agree with some of the points being made here. Especially regarding multiple threads for one device which can be confusing, but given that the devices section has been like this as far back as I can remember, I have to say that I find the timing of this discussion a little odd.
To be honest I think it would be better to see the devices section cleaned up (spam & newbie OT posts removed).
I actually agree with some of the points being made here. Especially regarding multiple threads for one device which can be confusing, but given that the devices section has been like this as far back as I can remember, I have to say that I find the timing of this discussion a little odd.
To be honest I think it would be better to see the devices section cleaned up (spam & newbie OT posts removed).
who whatfor know bugs spezificationes (ranges of controls . .)
time is money
no time for testing or searching forums to find an answer the developer could give with a few words;
i ask myself is "he" not willing to invest a little bit more time on his babies;
sorry - ?
i would be proud of my devices and telling everyone with a txt file what they can or not included in download;
and i see this with free or share or commerzial SW exept the devices section here(not all!)
so please finnish them and im sure more customers will use;
and thatfor they are made dont?
just my side of view
greetings
time is money
no time for testing or searching forums to find an answer the developer could give with a few words;
i ask myself is "he" not willing to invest a little bit more time on his babies;
sorry - ?
i would be proud of my devices and telling everyone with a txt file what they can or not included in download;
and i see this with free or share or commerzial SW exept the devices section here(not all!)
so please finnish them and im sure more customers will use;
and thatfor they are made dont?
just my side of view
greetings
Here is a suggestion for how to make things more transperant to us lucky people, who get to use your (the developers) very nice creations.
1) Keep a nice version history in post one - not only in the thread.
2) Let the latest version be downloadable from post one
3) If there is a reason to keep older versions awailable, it would be nice to have all those versions awailable in post one too. If a device evolves into having siblings in parallel, the names could reflect the new direction of the device.
4) Update the title of the thread, so I tells wich version is the latest.
5) If you want to bump a thread to tell us, that something has changed/happened, you can just make a post with the contend "Updated - see post one for details."
It is mainly a question of procedure. It is not much of a difference to edit the first post instead of spreading the info throughout the thread, but it makes it much easyer to keeps a hold of things for us - the lucky ones.
1) Keep a nice version history in post one - not only in the thread.
2) Let the latest version be downloadable from post one
3) If there is a reason to keep older versions awailable, it would be nice to have all those versions awailable in post one too. If a device evolves into having siblings in parallel, the names could reflect the new direction of the device.
4) Update the title of the thread, so I tells wich version is the latest.
5) If you want to bump a thread to tell us, that something has changed/happened, you can just make a post with the contend "Updated - see post one for details."
It is mainly a question of procedure. It is not much of a difference to edit the first post instead of spreading the info throughout the thread, but it makes it much easyer to keeps a hold of things for us - the lucky ones.
There's some great comments here & I'll do my best to keep things more organised & better explained.
The devices that sharc & I have posted are indeed mostly beta releases, as we plan to improve them based on combinations of our own ideas & also the ideas & suggestions of anyone testing the devices & commenting or giving feedback based on their impression & or expectations/desires. I think that's a very valuable process which any developer contributing their free devices can benefit from. That said, 2 or 3 of the simpler modular modules I've made are actually finished in their own particular form & that's something which is misrepresented by me having called them beta v.01. That's something we'll need to look at
The devices that sharc & I have posted are indeed mostly beta releases, as we plan to improve them based on combinations of our own ideas & also the ideas & suggestions of anyone testing the devices & commenting or giving feedback based on their impression & or expectations/desires. I think that's a very valuable process which any developer contributing their free devices can benefit from. That said, 2 or 3 of the simpler modular modules I've made are actually finished in their own particular form & that's something which is misrepresented by me having called them beta v.01. That's something we'll need to look at
***** suggestion (not to make fun of anybody - more showing, how I imagine i would fare myself, if I got into something even close to advenced in SDK )*****
Hi all, I made this compressor device. I hope, you like it.
Version history:
3.1pink: I found, that I liked pink better, so I made a pink version. The functions are identical to the version 3.1 device
3.1: I changed the realese range from 60s to 20s. Many people responded, that they didn't need a 60 second release and would rather have finer adjustments.
3: All parameters are now MIDI controlable.
2.1 Bug found in the preset list. All presets would be saved with the name SMASH.
Bug fixed.
2: Now this device comes with a preset list.
1.1: Device could no longer be loaded as an insert. This is now fixed.
1: Added soft knee function. The device should be fully functional now. It does not have automation and presets because I have not found out how to make those yet. Anyway, I will probably leave the device as is.
0.4: Numbers in attack text field did not correspond to the mouse over values. Fixed. Anything more to add to a final version?
0.2: Attack added.
0.1: First attempt. What do you think about it?
This device is called Boot, because I want to make a realy violent compressor, wich could realy squeeeeze the shit out of anything comming through it. Also I wanted something with it's own foot print (pun intended), so I added a tremolo with BPM control to the side chain. The tremolo curve can be sine, inverted sine, saw up, saw down, square ... or even random for realy spaced out effects. Tell me, what you think about it.
###### PICTURE ######
###### Download 3.1pink ######
###### Download 3.1 ######
###### Download 3.0 ######
Hi all, I made this compressor device. I hope, you like it.
Version history:
3.1pink: I found, that I liked pink better, so I made a pink version. The functions are identical to the version 3.1 device
3.1: I changed the realese range from 60s to 20s. Many people responded, that they didn't need a 60 second release and would rather have finer adjustments.
3: All parameters are now MIDI controlable.
2.1 Bug found in the preset list. All presets would be saved with the name SMASH.
Bug fixed.2: Now this device comes with a preset list.
1.1: Device could no longer be loaded as an insert. This is now fixed.
1: Added soft knee function. The device should be fully functional now. It does not have automation and presets because I have not found out how to make those yet. Anyway, I will probably leave the device as is.
0.4: Numbers in attack text field did not correspond to the mouse over values. Fixed. Anything more to add to a final version?
0.2: Attack added.
0.1: First attempt. What do you think about it?
This device is called Boot, because I want to make a realy violent compressor, wich could realy squeeeeze the shit out of anything comming through it. Also I wanted something with it's own foot print (pun intended), so I added a tremolo with BPM control to the side chain. The tremolo curve can be sine, inverted sine, saw up, saw down, square ... or even random for realy spaced out effects. Tell me, what you think about it.
###### PICTURE ######
###### Download 3.1pink ######
###### Download 3.1 ######
###### Download 3.0 ######
About making a beta forum: One persons 0.9 would be another persons 2.2 ... would be a third persons 0.013alpha. I don't think it would really make a positive difference to have the devices spread more. I think structure and transperancy would fix it big time.
And once again: Thanks to all third party developers - both those of you making € versions and those of you making free devices. Your work is highly apreciated.
And once again: Thanks to all third party developers - both those of you making € versions and those of you making free devices. Your work is highly apreciated.
The way sharc & I see it is that as long as beta devices are labelled as being such in the thread title, then there shouldn't be an issue. If you want to download & try out or properly test a beta release & comment back to us on it, then great!! If you don't want to try the beta versions, then what's stopping you from just not downloading them?
Posted: 28 Feb 2007 22:20 Post subject:
--------------------------------------------------------------------------------
btw, I wouldn't recommend taking a beta release (from ANY platform) that you haven't personally tested in-depth & use it in a live set.
-----------------------
thats why these devices dont find its way to the desktops free or not;
isnt THIs sad?
doesnt this make bitterness to a developer if his devices arnt used?
even when there are 10000 downloads?
i understand the ballplaing thing but arnt my wishes (and they were wishes not critik) sort of?
i dont understand reaktion;
-------------
once again PLEASe make them complete before starting a new one;
good vibes from vienna
--------------------------------------------------------------------------------
btw, I wouldn't recommend taking a beta release (from ANY platform) that you haven't personally tested in-depth & use it in a live set.
-----------------------
thats why these devices dont find its way to the desktops free or not;
isnt THIs sad?
doesnt this make bitterness to a developer if his devices arnt used?
even when there are 10000 downloads?
i understand the ballplaing thing but arnt my wishes (and they were wishes not critik) sort of?
i dont understand reaktion;
-------------
once again PLEASe make them complete before starting a new one;
good vibes from vienna
I consider myself very fortunate to have joined this forum, and platform. " This Thing Of Ours", is unequaled in every sense. So I am w/ the developers in any decision they make, 4 their time is really our money being saved. BTW, MYCYRRANO's Tube EQ has already been beta tested by me, to a small degree, any updates would be a bonus, as it already serves it's purpose 4 my project rather obesely. Check out the examples in the device thread.
Since that post I have routed my hardware analog tube echo to extend the audio chain into the STM1632. These recent devices from Shroomz / Sharc, and MYCYRRANO shall go down in infamy.
I think I will go Masterbeta some more.
I Am Getting So Fat, I Will Need My Own Zip Code,
Since that post I have routed my hardware analog tube echo to extend the audio chain into the STM1632. These recent devices from Shroomz / Sharc, and MYCYRRANO shall go down in infamy.
I think I will go Masterbeta some more.
I Am Getting So Fat, I Will Need My Own Zip Code,
