thcilnnahoj's Forum Page

Forum Replies Created

Viewing 15 posts - 496 through 510 (of 815 total)

← 1 2 3 … 33 34 35 … 53 54 55 →

January 3, 2010 at 21:00 in reply to: 2.23 #17192

thcilnnahoj
Participant

@UncleAge wrote:

btw, what do you use to make the gif’s ?

I record with BB Flashback and do the rest (cropping, frame rate reduction and exporting as GIF) in VirtualDub.

I just noticed today that if audio processing (gain/pan faders) is disabled on child tracks of a VSTi-holding group track (a drum sampler in my case), the pencil tool (or double-clicking with the select tool) will create a MIDI event instead of an audio event as usual… previously, I’ve always created MIDI events on the group track and then moved them over to the child tracks – I wish someone had told me earlier! 😛

January 2, 2010 at 20:16 in reply to: 2.23 #17188

thcilnnahoj
Participant

“Sir Bugalot” has another fiendish bug’s head on his lance to serve as trophy on the walls of King Fixalot’s castle! 😆

There’s a selection/key focus problem concerning tempo and marker events.
In this example GIF (245 KB) I try to select and delete a tempo event with the DEL key on the keyboard whilst different editors have focus.

– First with focus on the arrangement editor – works fine.
– Then with focus on an “empty” embedded editor – here the tempo/marker event doesn’t become the active selection but still gets deleted, probably since there’s nothing else selected in the empty E.E..
– Focus on the embedded editor – works fine as well.
– And lastly, focus on the mixer. The event is not set as the active selection here either, and so it actually deletes the focus track in the mixer instead! :o)

January 2, 2010 at 10:02 in reply to: Arrangement snap settings stored per profile #17185

thcilnnahoj
Participant

Sounds good. I’ll wait patiently! 🙂

January 2, 2010 at 10:01 in reply to: 2.23 #17184

thcilnnahoj
Participant

Tiny aesthetics thing: If the track name is longer than the mixer strip is wide and it gets cut off, there is always still a little padding space on the left side, but not on the right.

December 31, 2009 at 12:46 in reply to: 2.23 #17180

thcilnnahoj
Participant

A few last things to throw on the pile to burn at year’s end… 😉

– Alt-B does not work on a track that hasn’t been bounce-enabled beforehand. It only recognizes ‘B’ in this key combination and starts rendering the whole track instead of only the punch range.

– Bouncing tracks that have no effects naturally leads to an empty track being created to hold the bounce event. However, this track is still labeled “Effect” (greyed out) in the mixer, even though “use name of device assigned to track” is automatically selected for bounce tracks in the track properties, and thus the track would actually be named “Bounce.”
It’s a little weird like this – I can’t think of a reason the mixer/rack selectors shouldn’t use the track name setting… Are names on effect tracks even used anywhere at the moment (apart from unhidden effect tracks, which you said are on their way out)?
A different suggestion, but perhaps conveying too much not-so-important information, would be to color tracks on which bouncing is set with the bounce color as well whenever bounce playback/recording is activated. :-k

– If you load a device setup from the project templates menu while you’re on the arrangement page, the arrangement is closed and you’re thrown back to the project page. The arrangement is still active (and maybe even playing) though – just the tab has disappeared.

– Is there a reason for the velocity buttons in note editor, point type buttons in curve editor and channel select buttons in sound editor to be aligned to the left instead of to the right?

December 30, 2009 at 15:52 in reply to: 2.23 #17174

thcilnnahoj
Participant

As it seems Frits is concentrating on bug-fixing right now, I’ll have a try and put this one up again, as I think it went under in whatever thread it got posted originally:

Auto-assigned audio inputs will become mute as soon as there’s an effect track added, caused by the moved fader position in the chain…? If I move the fader down to the bottom track it works fine again.
I don’t quite understand why this would disable the input, since I can move the fader wherever I want and still get a signal from a directly assigned input. In any case, I don’t think this is intentional.

Like I said, I’m not entirely sure it’s a bug, but “fixing” it would help me out a lot!

December 27, 2009 at 11:54 in reply to: Preview 2.24: Embedded plugin editors in the rack #17163

thcilnnahoj
Participant

I finally took a look at beta 7 today, and apart from the fact that it’s still awesome, I’m not exactly lovestruck by the new mixer options buttons. 😉 I’m not a fan of such vowel-omitting words… To me, “src” will always be “sample rate conversion” first and foremost!

Thinking about an alternative solution:
Wouldn’t it be possible to drop the gradient background from the icons, just leaving the ring and letters on a transparent background – then they could be reliably dyed with any and all colors. As I said before, it’s not just a problem affecting the mixer buttons… Take a look at the rack selectors with the Nightfall theme, for example:

About the photographic icons (XLR/MIDI connectors, headphones) – did you try to dye them completely with the text color? I don’t think losing little details in lighting would make those little images less discernable, or pretty. Maybe it doesn’t work for the different cable connectors… that’d probably have to be sacrificed. :-k

December 24, 2009 at 09:57 in reply to: Something nice for the embedded zEq plugin #17154

thcilnnahoj
Participant

Do you mean it should only take one click to enable/disable bands? Otherwise Santa (oder besser das Christkind) already made your wish come true, I’d say. 😉

If you read on a bit:

@Zynewave wrote:

Beta4:

Made several changes to the appearance and mouse actions of the zPEQ editor:
The embedded rack and mixer editors will not show the parameter fields, but will instead show a popup with info for the band closest to the mouse cursor.
The curve is drawn centered around 0dB.
Moving the mouse in the display will highlight the nearest band handle.
Double-click the background to enable the next unused band.
Double-click a band handle to disable the band.
Right-click to show a band type menu for the nearest band.
Click to drag frequency and gain of the nearest band.
Alt+Click to drag the Q value of the nearest band.

December 24, 2009 at 09:46 in reply to: Preview 2.24: Embedded plugin editors in the rack #17153

thcilnnahoj
Participant

Let bugs be bugs for a while and enjoy the festivities. 😛
Merry Christmas from me too!

December 23, 2009 at 06:10 in reply to: 2.23 #17145

thcilnnahoj
Participant

I noticed I’m still having problems with waveforms not being displayed right after importing audio files. I don’t have a good way to reproduce it, but it seems to happen mostly with very short files when I’m zoomed out a bit.
Also, when you change the sample rate in the sound properties, the waveform isn’t updated until you scroll, zoom, etc.

This seems to be a tiny bug as well: Sequences shorter than 4 beats are zoomed to the exact length of 4 beats in their respective editors when you use ‘Zoom Full Range’ or double-click the navigator.

December 22, 2009 at 07:07 in reply to: 2.23 #17142

thcilnnahoj
Participant

Very weird bug this time: When there’s an active bounce playback on the master track and there’s an automation track present in the arrangement, then looping will be kind of broken. 😮
No problems without any automation tracks or bounced files playing on other tracks than the master.

Please see example GIF (775 KB) and try for yourself. the play cursor will return to the loop start even if loop mode is deactivated long before the cursor reaches the end.

Another tiny one: If you click on a bounce button while holding Alt+Shift (don’t ask me why :wink:), the keys (and thus the slide tool) will “stick” if you release them during the bouncing process.
Same thing happens when you use Alt+Shift or Ctrl+Shift on any buttons that open a menu – that includes selector buttons. Since most menu buttons can be right-clicked now too, it of course happens with both mouse buttons!

December 22, 2009 at 06:11 in reply to: Preview 2.24: Embedded plugin editors in the rack #17141

thcilnnahoj
Participant

@Conquistador wrote:

Here is some info on anti aliasing…(with more to the left of the screen in the link on fonts)…

http://msdn.microsoft.com/en-us/library/dd183433(VS.85).aspx

Had a problem getting this link to work but paste into your browser to see the full article.

It looks like in theory it might help Frits with Podium (from a developers perspective). Its a guess of course as I am no expert in this area but this info from the link looks like it might help???

“You can adjust the appearance of text by changing the contrast value used in the ClearType algorithm. The default is 1,400, but it can be any value from 1,000 to 2,200. Depending on the display device and the user’s sensitivity to colors, a higher or lower contrast value may improve readability. To change the contrast, call SystemParametersInfo with SPI_SETFONTSMOOTHINGCONTRAST. The following code sets the contrast value to 1,600.”

Maybe something like that can be adjusted in Podiums code or exposed to a user to change in a more simplified way. ❓ ❓ ❓

These options will not make it any better, though… :-k
You can set all these parameters yourself (system-wide) with this Microsoft tool. I found a piece of information that speaks of a control panel entry giving access to these options that’s already built into Windows 7 from the start – maybe you could try to look for it and test it for yourself.
My guess is that Reaper uses different font rasterization/smoothing types in different places, maybe even circumventing Windows’ settings.

December 21, 2009 at 06:05 in reply to: Preview 2.24: Embedded plugin editors in the rack #17136

thcilnnahoj
Participant

@Zynewave wrote:

Beta 6 is up. Minor changes and some bug fixes. I think I still need a couple of days working through all the bug reports.

It’s hard to test though if we don’t know what to check for! 🙂 Are you taking on bugs related to changes in 2.24 only, or the ones reported in the releases forum too?

@Zynewave wrote:

@thcilnnahoj wrote:

Question: Since the selected embedded parameters remain the same across different arrangements, I assume they stored within the project (or the device definitions) then. If so, would it be possible (without too much trouble on your end) to export such a parameter list setup to reuse in other projects?

The two flags for rack/mixer embedding are stored in the properties of the parameter object. I could add two check-boxes to the parameter properties dialog, but I don’t think that is necessary. If you save a track template then the flags will be included. The embedded flags will be recalled if you load the template into another project, unless that project already has a definition for the plugin.

Hmm, okay, that’s at least workable. But there’s no way then to import them into existing projects other than merging them or deleting devices and reimporting them via track templates, which I reckon would not be advised!

December 21, 2009 at 05:55 in reply to: Preview 2.24: Embedded plugin editors in the rack #17135

thcilnnahoj
Participant

@Conquistador wrote:

Screenshots as promised… 😉

This is with ClearType on. Reaper IMO has much clearer text compared to Podium here. I really do not know why Podium looks much less clear compared to Reaper :-k

Podium is on the left and Reaper is on the right. Look at the “Fabfilter Timeless” text for the inserts.

But if I switch off ClearType…can you spot the difference between the two applications “Fabfilter Timeless” text now? I can hardly tell them apart…below…

Podium is far sharper than the first image now that Cleartype is off and matches (maybe even goes further than) Reapers text for clarity in the second image. Quite a difference and quite easy to see IMO with those screen shots.

So Podium it appears benefits clearly from having anti aliasing disabled for certain areas (inserts on tracks and mixer strips) but anti aliasing is very helpful elsewhere in Podium that is why I think adding some kind of option to disable anti aliasing for the Insert, Source and Input buttons (just for the tracks and mixer strips) will solve this problem.

I hope that helps.

But Reaper’s fonts are not anti-aliased at all in either of your screenshots, CQSD. Are you sure ClearType has an effect on Reaper in your setup? The “fast text rendering” option turns it off completely for me. Though I must say it was quite buggy when I tried it just a few moments ago…

Just for fun, here’s another comparison between the two programs’ fonts in various places, with and without anti-aliasing. Magnify it in your favorite image editor. 🙂
They’re identical at larger sizes, but the smaller ones make you wonder if it’s the same font, really. I’m far from an expert on this either… From the look of the small anti-aliased fonts, I prefer some letters in Podium (especially w), and others in Reaper (lowercase L).
The other thing that’s easily noticeable is there are no color fringes in R.’s mixer fonts (they’re very well present in other places, though.) As far as I know, there’s no rendering option that would do this in ClearType.

All the screenshots I could find of Samplitude were taken with anti-aliasing disabled in Windows, so I can’t tell if the mixer fonts would still be the same if you turned it on. (Off-topic: It looks like visual consistency is not one of Samplitude’s high points anyway. Check the custom grid/snap boxes and tab buttons(with forced AA), but also default Windows dropdown menu boxes and buttons used in other places (using Windows’ AA settings) in this screenshot. :?)

December 18, 2009 at 19:36 in reply to: Preview 2.24: Embedded plugin editors in the rack #17114

thcilnnahoj
Participant

Oh yeah, I see it works a little differently than I expected. I thought double-clicking somewhere would enable the band closest to the clicked position instead of the first unused band. No worries… I’m glad I decided not to get Fabfilter’s new Pro-Q as it would’ve been rendered quite obsolete with this update for me. 🙂
Nothing can beat the mini-EQ displays integrated in the mixer, and using it is so much quicker now, too!

Viewing 15 posts - 496 through 510 (of 815 total)

← 1 2 3 … 33 34 35 … 53 54 55 →