Jump to content

Bapu

Members
  • Posts

    95,764
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by Bapu

  1. 45 minutes ago, azslow3 said:

    ReaCWP tries to put clips with "all goodies" specified in Cakewalk (sec/beat, clip, offset, loop, etc.). I went throw DAWProject documentation and all that is possible to specify. But what is the "right" way to do that is unclear. Unfortunately, unlike in Cakewalk and REAPER, where "track with all related parameters(->lane)->clip with all related parameters" is hard to interpret wrong (since that is logical and follows what users see and do...), DAWProject introduce different hierarchy of containers, without precise specification how it should be build (at least at first look, all provided with the specification examples are "too simple").

    PS. I hope DAWProject is not going to be another "VST3" (where no-one knows how to implement many things "right", not even if the "right" way exists...). Triggering endless incompatibilities...

    Jürgen said he reported the "problem" to Presonus. He has my example to work from if he needs to make any adjustments to his code.

  2. On 11/6/2023 at 1:56 AM, azslow3 said:

    If you give an example to Jürgen (the author of ProjectConverter), he can probably understand the reason quick (since he knows exactly what and how is converted, so he can guess what from that can be incompatible).

    Jürgen sent me a 'pre-release' to test of what I suspect will be ProjectConverter 1.1.4

    Works perfectly with all the audio converted.

    One small note about ReaCWP.  If I don't bounce to clips all the tracks then ProjectConverter starts any clip at 1:1 regardless of its actual timeline position.

    The 'workaround' is to insure all tracks have their start at 1:1 or 'consolidated' as it is sometime referred to before sending it through ProjectConverter.

    FWIW, ReaCWP does create the Reaper project with small clips ( non consolidated) in their proper place, so maybe this is yet another 'bug' in ProjectConverter which I will report to Jürgen.

  3. I turned 11 when The Beatles arrived in America for the first time on my birthday, 7 Feb 1964. I was already stoked by them as I saw a B&W film clip of them on the Jack Parr show a few days/weeks earlier saying they were coming to America and IIRC he predicted they were going to be huge. 

  4. Roughly 5% of the Beatles are clunkers for me. Yellow Submarine, tops that list. Till There Was You is wasted air space. Some days I like Octopuses Garden, other days, nah! Blue Jay Way I will skip/turn off/change station.

    I saw Ringo's All Star Band with Jack Bruce one year. Even Jack could not save YS, I went to the loo.

    I am a proud near constant Beatles Channel listener on SiriusXM when I drive, unless I'm testing a mix of a song I'm working on.

    • Like 1
  5. On 11/6/2023 at 1:56 AM, azslow3 said:

     

    1) Please for VST/state in question save .vstpreset (state file) in REAPER and load it in Bitwig. Does it loads correctly?
     

    2) If you give an example to Jürgen (the author of ProjectConverter), he can probably understand the reason quick (since he knows exactly what and how is converted, so he can guess what from that can be incompatible).

    1) I need to test that still.

    2) I gave  Jürgen the example and he found a condition of "mix slahes" in the filenames. He said he will give me a test build tomorrow.

     

    Strange that the mixed slashes are ok in Bitwig but not Studio One, but he's the developer.

  6. 1 hour ago, pwal said:

    imho the beatles thing is better than the stones thing, and two of those beatles are dead already, but i don't rate either haha

    On both band's songs that Macca plays on, the bass could probably be done by any player with only a year of experience. Run of the mill bass playing is what I heard. I can finally say that I'm a good as Macca (on those two songs).

  7. 15 hours ago, Bruno de Souza Lino said:

    I can give you a few:

    - Workflow based around and makes use of terminology that only people that have worked with tape machines are familiar with.

    - Keyboard shortcuts are hard coded to your keyboard layout. The program is not smart enough to detect you don't have a US keyboard and you manually have to change it in the settings on top of manually remapping conflicts for shortcuts you'll probably never use.

    - Unnecessary separation between stereo an mono plugins that often generates unnecessary duplication on modern plugins which can tell which signal they're receiving. This is on par with how Waves still makes plugins.

    This one is a pet peeve of mine:

    - The demo song which is specifically made for Intro has more tracks than Intro can open.

    - 1980's archaic infrastructure with a 2000's paint job

     

     

    Disclaimer, I have a perpetual license for Pro Tools with three more years of maintenance.

  8. 18 minutes ago, Bapu said:

    Really? Where? How?

    The reason I ask is when I use ReaCWP to open a new .rpp and then use ProjectConverter to write the .rpp to DAWProject format,

    That DAWproect file opens in Bitwig and pretty much works (some VSTs come over with odd states compared to the original).

    However, the DAWProject file opens in Studio One but no audio clips are present, all the tracks/folders are there though.

    @azslow3 
    On further testing this *only* happened with a ReaCWP created .rpp. If I use ProjectConverter on a .rpp fully created from scratch it loads with all audio clips in Studio One and of course Bitwig. This would indicate that there is something about how ReaCWP created the .rpp and passed that off to Project Converter that boinks up Studio One but not Bitwig.

×
×
  • Create New...