Hacker News new | past | comments | ask | show | jobs | submit login

My goal is to get Avid Pro Tools 7 working on bare metal ROS. Partially successful attempts thus far: install is going smoothly, but the software doesn't launch. I get the nostalgic Blue Screen of Death and usually end up re-installing the entire OS. I assume it is a driver issue since PT of that era (2007-ish) requires a dedicated audio interface (the Mbox).

But I need PT a few times a year, so I'll keep trying.

I can also state that compared to version 0.4.7 (the first one I tried, iirc), the current non-nightly build 0.4.13 ran way more smoothly for me, at least on the GUI side. Issues with mouse stalling are gone, etc.

The "EPIC WIN!" threads on the ROS forum [1, 2] are fun to follow. Based on that, the OS seems to be quite usable for a range of cases.

I also liked the "What's the point?" threads [3, 4]. My respect to the developers for taking the time and patience to explain.

All in all, I keep hoping and installing new versions. I like how clean the system feels -- or, maybe this is the case with many systems when you don't bother to add Internet connectivity. Without wifi, every OS feels quiet and calm.

Greetings to ROS devs!

1: https://reactos.org/forum/viewtopic.php?f=2&t=10972&start=12...

2: https://reactos.org/forum/viewtopic.php?f=2&t=20185

3: https://reactos.org/forum/viewtopic.php?f=2&t=19782&start=60

4: https://reactos.org/forum/viewtopic.php?f=2&t=20031&start=30




Unfortunately, I was not able to find any bug-report related to the Avid Pro Tools 7 in the bug-tracker https://jira.reactos.org/

Filling a bug-report is the important first step to have your software working in ReactOS


True, I haven't filled a report yet; will look into this next time, probably when ROS 0.4.14 is released.

Pro Tools, at least in its early versions, tends to show its moods even on a well-tuned Windows system. So I was almost sure that it won't run in ROS out of the box. I was actually surprised to see it installing so smoothly. My guess is that the driver for the audio interface (Mbox 2) needs some attention.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: