All times are UTC+02:00




Post new topic  Reply to topic  [ 328 posts ]  Go to page Previous 111 12 13 14 1533 Next
Author Message
PostPosted: Wed Dec 10, 2014 3:33 am 

Joined: Sat Oct 25, 2014 4:53 pm
Posts: 3
Quote:
I would rather want password for presets.
And Bypass maybe?!


Top
   
PostPosted: Wed Dec 10, 2014 8:23 am 
User avatar

Joined: Thu Oct 25, 2012 3:22 pm
Posts: 237
Location: Poland
Quote:
Quote:
I found something strange on Linux version, something like dc offset and subcarrier leak only when composite clipper enabled.
Don't use Hilbert mode! In fact, based on the last info that I have from manufacturers of car radio's, don't use SSB at all... because the biggest manufacturer in the world doesn't support it anymore in their latest chipset...
I normal stereo mode with advanced clipper also occurs.

_________________
Urban Junglist


Top
   
PostPosted: Wed Dec 10, 2014 11:41 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
I would rather want password for presets.
Do you really mean password protection (so someone with the password could view all the settings) or do you mean that you want to be able to give someone a preset without letting them see or change the settings? (load an encoded preset and while it's loaded block saving or viewing/changing settings)? Or do you mean that you want to stop people from changing settings but not from viewing them?


Top
   
PostPosted: Wed Dec 10, 2014 11:52 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
Quote:
Question: Is anyone using Band Coupling in the multiband compressor now? If not I could just as well remove it again... But my initial very quick test did seem to give an improvement to the sound when I coupled bands 1+2 (better/nicer bass).
I use, actually testing it. But i really dont like how it kills MB meters and makes those peeks on them when they are not there.
Hm.... if you set all to 100% all the meters do the same and that seems to be correct. If I couple band 1+2 by setting the same settings for both they also do exactly the same thing. So they do appear to show the actual behavior for each band.

It does behave incorrectly when using limiting though: Limiting is shown in the band which causes limiting to occur, but it affects all bands via this coupling and also the shown levels for all bands (so the colored bars go down more when limiting occurs, the white dotted bar that comes down is only shown in the band which causes it).

Anyway, what about the sound?


Top
   
PostPosted: Wed Dec 10, 2014 12:16 pm 
User avatar

Joined: Tue Mar 17, 2009 2:56 pm
Posts: 4231
Quote:
Quote:
I would rather want password for presets.
Do you really mean password protection (so someone with the password could view all the settings) or do you mean that you want to be able to give someone a preset without letting them see or change the settings? (load an encoded preset and while it's loaded block saving or viewing/changing settings)? Or do you mean that you want to stop people from changing settings but not from viewing them?
If it's password protected, then not be able to change or view settings. However some settings should be possible to change, like Advanced clipper, MB range, EQ...

Coupling.. Yes i noticed that compressors reacts whenever limiter(s) kick in. I still think that's wrong. At some point i can see B1 compressor kick fast and back for 6dB wich is ofcourse not true.
Tried it to use to "calm" some bands when big range occures, seems it helps.

_________________
control point
control point2


Top
   
PostPosted: Thu Dec 11, 2014 1:25 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
There was something wrong with the 752-014 DSP and VST versions; if you have problems please re-download them (links are updated and now point to 752-014A)


Top
   
PostPosted: Thu Dec 11, 2014 1:42 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
Quote:
Quote:
I would rather want password for presets.
Do you really mean password protection (so someone with the password could view all the settings) or do you mean that you want to be able to give someone a preset without letting them see or change the settings? (load an encoded preset and while it's loaded block saving or viewing/changing settings)? Or do you mean that you want to stop people from changing settings but not from viewing them?
If it's password protected, then not be able to change or view settings. However some settings should be possible to change, like Advanced clipper, MB range, EQ...
I want to start with the password protection as it is now (with some improvements); if that works password protected (or actually, I would prefer completely unreadable) presets would be the next step. So basically: You make a preset and export it to an unreadable format. If someone loads that preset, they can't see or edit the settings. But they can save them, which would then also need to be in an unreadable format. Because this is all a bit tricky let's start with this 'simpler' protection in this version, if that works flawless I can create the preset protection later. (Depending on how long it takes to finish 7.52 I might even add it in anyway... but not now).

There are some problems with this though, among others that if you use a VST plugin you could use the VST interface (which shows every parameters as a float value) to convert it back to a normal preset. So either I must make these presets unavailable in VST plugins, or circumvent using the VST interface, or I need to completely rewrite how VST parameters are saved (there are other methods which I don't currently support), but that would in turn make it impossible to automate things through the VST interface.

Beside this, without a proper encryption method, I can write a preset to a file such that it's hard to read by saving it in binary mode, but it's always possible to reverse engineer the storage format and to decode it. So if for example you want to sell presets I'm not sure if this protection would be enough.

Anyway, enough reasons to not 'rush' towards a solution but to take some time to think about what's needed.
Quote:
Coupling.. Yes i noticed that compressors reacts whenever limiter(s) kick in. I still think that's wrong. At some point i can see B1 compressor kick fast and back for 6dB wich is ofcourse not true.
Tried it to use to "calm" some bands when big range occures, seems it helps.
Well actually the compressors don't react - but the displayed value contains both compressor and limiter. And (and I'm not sure if this is good) if you use band coupling the limiter behavior is coupled also. Actually that IS probably good if there's not much band coupling to avoid sudden big effects in small frequency ranges. But if you use a strong coupling between bands it makes far less sense and might be wrong.

If that's indeed the case, that would mean that I actually need to redesign how the clippers work...


Top
   
PostPosted: Thu Dec 11, 2014 5:59 am 

Joined: Sat Oct 25, 2014 4:53 pm
Posts: 3
GUI Crashed if the window is at this size and click multiband tab.
(Hans, i send you the error log)
Image


Top
   
PostPosted: Thu Dec 11, 2014 11:08 am 
User avatar

Joined: Thu Mar 22, 2012 9:53 pm
Posts: 29
Quote:
Question: Is anyone using Band Coupling in the multiband compressor now? If not I could just as well remove it again... But my initial very quick test did seem to give an improvement to the sound when I coupled bands 1+2 (better/nicer bass).
Yes, I always adjust band coupling.

Edit: Ahhh wait, I didn't spot the seperate 'band coupling' tab yet. That gives some extra control over the multiband compressor's behaviour. Yay!
Trying to figure out how it works though.

Edit 2: First quick listening impression is that you can do very nice things with it. Lowering band 1, 2 and 3 (of 6) to +/- 85% coupling (auto switch off, norm function off) adds a bit of the fat 'French touch' to the low end.

Edit 3: Added screenshot. Is my interpretation correct if I say that:
#1: Band 1 is coupled 3% to band 2? Or is it the other way around: Band 2 coupled 3% to 1?
#2 and #3: Band 3 coupled 1% to band 2 and 2% to band 4

I would also like to know what extactly happens/ is adjusted when I lower the coupling of its own band (the 88% of band 1 and 2 is relative to what?). Bands 1 and 2 are reacting much faster.

p.s. notice the visual glitch.


Attachments:
ScreenHunter_40 Dec. 11 11.48.jpg
ScreenHunter_40 Dec. 11 11.48.jpg [ 209.93 KiB | Viewed 5437 times ]
Top
   
PostPosted: Thu Dec 11, 2014 3:36 pm 
User avatar

Joined: Tue Mar 17, 2009 2:56 pm
Posts: 4231
You are using it wrong. You want all that slides at 100% always, but other band (more then 0%) to follow choosen band.
hmm.. hard to explain :D

_________________
control point
control point2


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 328 posts ]  Go to page Previous 111 12 13 14 1533 Next

All times are UTC+02:00


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited