Jump to content

Glenn Stanton

  • Content Count

  • Joined

  • Last visited

Community Reputation

323 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. i keep a printed cheat sheet of my buss/track color scheme (small squares with color, RGB#, name of buss). i only have about 30 busses so the groups of them are similar that if my overall template doesn't solve it, i can create a new custom version. although i tend to just use the main templates and trim out what i don't need rather than try to create new versions with track templates (and hopefully someday buss templates!)
  2. yeah! then you get the best sound from your 8-bit crusher distortion analog-defect reproduction VSTs! 😛
  3. triangle or square wave setting on the synth oscillator(s). sine waves can be hard to hear so the triangle and square wave harmonics will likely be more noticable with lower volume levels...
  4. my first thought would be the power rectifier tube is fritzing, or the power supply caps are on the way out. doubtful it's the transformer. one option would be to swap out the four (4) tubes for a new set. if you'd don't have electronics repair skills - then take it to a proper shop for repair because changing out components can make things worse if not done correct - product choice and installation etc.
  5. it's not the format, it's the option of players on the iphone. if you connect your iphone to your PC, you can directly copy files between them (with the correct drivers) and then install another player which can access those files and play them. otherwise bow in obedience to Apple... 🙂
  6. maybe create a MIDI clip with notes at each velocity - 1, 5 ,10, 15, 20, 30, 40, 50, etc. if it's a sample based VSTi, it's likely a limit of the sample scaling used, if it's synthesized, maybe some velocity range is imposed to create "realism". perhaps a pure synth set to square or triangle tone would show/sound correctly.
  7. just to summarize - we're asking about the 64-bit engine - on or off - with regards to how it impacts the rendering of 1) the mixing process, 2) the export out file? maybe @Noel Borthwick can clarify but my understanding is the 64-bit engine processes using 64-bits versus 32-bits in-CPU/in-memory and then depending on your project word size, would store the results by either truncate? or dither? or as @Milton Sica notes - we don't really know what's going on 🙂
  8. or go to the display menu on the lower left and select the options you want and save the workspace(s) if it's not global (i think it is)
  9. it's likely that few people would notice single vs double float processing - i believe in the old forum someone had done some tests with reverb tails tapering more nicely on the double float but it was also specifically testing for it versus what it would be in normal material. since the 64-bit option has been there in SONAR and CbB, i always have it checked. i'm perfectly comfortable using 64-bit processing 🙂. i just don't use any type of float when processing overnight fed fund currency swaps 😉 as a note, i generally export either 48K or 44.1K @ 24-bit, no dither WAV. subsequent processing via Ozone 9 which may or may not use double float to render 44.1K 16-bit WAV and MP3.
  10. i'm thinking the #2-3 is akin to "bounce to track" effect where the (apparently temporary nature of the gain control) is effecting the level. my guess - the soft synth output is being written to a temp memory queue or temp file while recording it and so its acting like a clip input, it has that level adjustment, but once done, the proper clip file is written, it's written as unity gain as noted. so when recording it from a patch point, which is receiving the gain variations, it does actually record that. my guess is we need an updated flow diagram 🙂 and/or perhaps letting the gain level work on inbound audio regardless of source... (which is likely what the majority of folks would expect).
  11. as a note: the original joking around by the Bakers (per Noel and some others) was calling it WASABI... it may have been an internal name by Microsoft as well...
  12. yes, not surprising [cough. cough] competition with [cough, cough] paid products is [cough, cough] heating up... 😉
  13. dealing with intricacies of MIDI often require some details... the OP seemed happy with the original response - use automation. now they're at the point of finding the optimal or alternative MIDI CC which do this best...
  14. oh, did any one notice the VoS plugins are (being) updated to 64-bit? a minor issue to download. a lifetime to enjoy. i love the baxter EQ and density ones!
  • Create New...