2.3.2beta 3405.1344elcallio wrote:Your posted image is very tiny and does not say which build this is.
New beta build - now with big UI
-
- KVRAF
- 10310 posts since 2 Sep, 2003 from Surrey, UK
-
- KVRAF
- 10310 posts since 2 Sep, 2003 from Surrey, UK
... Big pic: http://i.imgur.com/viNWiMA.pngEvilDragon wrote:Oooh! I like these!DarkStar wrote:Sneaky FRs:
-- the ability to tint an individual Group
-- the ability to hide the sample names in the mapping panel
Hiding sample names should be in Setup (a persistent option), and tinting would be EXTREMELY useful, I think!
-
- KVRAF
- Topic Starter
- 2399 posts since 27 May, 2005 from Stockholm
Please re-run with newest build. I cannot say if I've noticed anything like you describe, but its worth checking if its already fixed.DarkStar wrote:2.3.2beta 3405.1344elcallio wrote:Your posted image is very tiny and does not say which build this is.
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRAF
- 10310 posts since 2 Sep, 2003 from Surrey, UK
-
- KVRAF
- 10310 posts since 2 Sep, 2003 from Surrey, UK
My first steps into reskinning: a modified "large" skin:
http://i.imgur.com/viNWiMA.png
-- smaller font size
-- shading for selected Group(s)
-- frames for non-selected Group(s)
-- the Groups do overlap, for velocity fading
Next step is to make the Mute and Solo buttons smaller
http://i.imgur.com/viNWiMA.png
-- smaller font size
-- shading for selected Group(s)
-- frames for non-selected Group(s)
-- the Groups do overlap, for velocity fading
Next step is to make the Mute and Solo buttons smaller
-
- KVRAF
- Topic Starter
- 2399 posts since 27 May, 2005 from Stockholm
Meh. SDK update. I've updated the RC5 builds. They should now run on XP again. But _please_ bear in mind that I _will_ drop XP support completely in the next major version.mccy wrote:Newest builds at least since 2.40rc3 don't work under Reaper WinXP. Any Idea why?
"InitializeCriticalSectionEx" not found in Kernel 32.dll
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRian
- 527 posts since 25 Aug, 2006
O.K. 1000 Thanks!!! It's just very fair, that you announced that. I allready have a second HD with WIN7 running on the same machine, but in fast projects I don't risk anything (but updating TX16WX ). So I know that my WIN7 Install makes sense... Audio setup has grown for years, so a change allways takes lot of time and then suddenly I find something which I didn't plan to use but has to be updated under WIN7 or does not work or whatever...
-
- KVRian
- 527 posts since 25 Aug, 2006
When working in "run as" dedicated or seperate Mode tx16wx beta does not work. (bitmap missing)
Some bridging 32 message message is shown.
Seperate or dedicated Mode makes sense to not overload RAM (in my experience).
(Tested with WIN 7 32 in REAPER)
Some bridging 32 message message is shown.
Seperate or dedicated Mode makes sense to not overload RAM (in my experience).
(Tested with WIN 7 32 in REAPER)
-
- KVRAF
- Topic Starter
- 2399 posts since 27 May, 2005 from Stockholm
Pardon me, but what is ""run as" dedicated or seperate Mode"?mccy wrote:When working in "run as" dedicated or seperate Mode tx16wx beta does not work. (bitmap missing)
Some bridging 32 message message is shown.
Seperate or dedicated Mode makes sense to not overload RAM (in my experience).
(Tested with WIN 7 32 in REAPER)
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRist
- 268 posts since 14 Oct, 2013 from San Francisco Bay Aea
From the Reaper manual:elcallio wrote:... Pardon me, but what is ""run as" dedicated or seperate Mode"?
14.25 Specifying VST Plug-in Run Mode
Within the FX Browser you can right click over any VST plug-in to specify your preferred mode for running that individual plug-in. Your options are natively, as a separate process, as a dedicated process, or as whichever of these has been specified as the default in your preferences. This option can be used to help quarantine REAPER from the effects of any plug-in that you suspect may be causing performance and/or stability problems.
-
- KVRian
- 527 posts since 25 Aug, 2006
But they are not only for problematic plugins... Especially memory-hungry samples can be handled much smoother in my case. I need these modes, when plugs eat up much ram, so that windows can take care of a single one and not as a 'reaper-package'. I can use much more samples before reaper becomes instable that way...
Martin
Martin
-
- KVRAF
- Topic Starter
- 2399 posts since 27 May, 2005 from Stockholm
Could you be more specific as to what does not work? "Some bridging 32 message message is shown" is not a very helpful description.mccy wrote:When working in "run as" dedicated or seperate Mode tx16wx beta does not work. (bitmap missing)
Some bridging 32 message message is shown.
(Tested with WIN 7 32 in REAPER)
I noticed one incompatibility, but I doubt it is what you are referring to. In any case, there is a new build up.
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRian
- 527 posts since 25 Aug, 2006
reapers dedicated/seperate process options:
I found out, that the main problem with reaper was the combination of dedicated/seperate process and the embed ui option. In that case reaper shows no gui at all with beta versions. When I let reaper open tx16wx in its own ui - window everything seems fine, but when moving that window reaper does not react anymore. I have to close tx16wx before being able to do anythting else.
Tested again with win8 tablet: Only problem there is the embed bridged ui option, which is not really important for me. So there is just the above problem in win32 left.
I found out, that the main problem with reaper was the combination of dedicated/seperate process and the embed ui option. In that case reaper shows no gui at all with beta versions. When I let reaper open tx16wx in its own ui - window everything seems fine, but when moving that window reaper does not react anymore. I have to close tx16wx before being able to do anythting else.
Tested again with win8 tablet: Only problem there is the embed bridged ui option, which is not really important for me. So there is just the above problem in win32 left.